Twonky Media Server Download Full Version
Janne Evers
Standard version: Allows consumers to share media by enabling consumer electronics (CE) manufacturers to integrate Digital Media Server (DMS) and Mobile Digital Media Server (M-DMS) capabilities into their devices for non-DRM protected audio, video and photo media types to supported devices. It is available as a standalone server (end user installable) or an embedded server.
As for the updated profiles, I suspect that you should be able to extract them from the Twonky 8 install package, and copy them into the Twonky 7 directory (profiles are just simple XML). I discuss this possibility, and where they need to be placed in the FAQ: have you read it yet?
You may need to be IN the twonkymedia-7 directory (or what ever directory is correct on the v2.x firmware) when you using the wget command and unzip the files otherwise the files may be unzipped into the wrong directory/location.
I deleted all the files into the twonky directory, and lunched the wget command within the same directory.
The new files were into the right directory.
The problem is after the reboot of mycloud
Since someone at the Twonky forum obviously thinks they know how to compile for a v2 firmware MyCloud, it might be worth asking on the Twonky forum. Or searching here for how to install third party software onto the Gen2 MyCloud.
Need to do the same. Would you provide simple instruction for someone who has no idea of SSH? How to login via SSH?
How to copy paste file to twonkymedia-7 folder?
Appreciate really simple guide
Did it using terminal on my mac.
However I have most likely Gen2 devise as my firmware starts with 2.11.142. Can you confirm if this is right assumption?
If yes, is there any way to upgrade Twonky to 8.x on my device? Twonky publish this software version so they assume this is possible. I just do not know how. Simple step instruction would be highly appreciated.
Anyone know of any unoffical ways to upgrade Twonky on the WD MyBook Live. In my conversations with Twonky, they too told me about the updated Twonky server, but the list of upgrade links they send me did not include Western Digital, nor were there any instrucctions on how to perform such an upgrade anyway.
Summary:
My Sony BlueRay BDP-S370 is DNLA certified to play external files. I was successful playing a number of video files, including .m4v when I had a Western Digital MyBook plugged into the BlueRay via USB.
Western Digitial has also communicated that have no intent on updating Twonky on their devices and are fine to be selling a product with an outdated third party software that may make their hardware not perform as advertised.
WD Customer Service/Staff has been AWFUL addressing this issue up until this point. All they simply need to do is supply a firmware upgrade with TwonkyMedia Server >= 6.0.30. I was planning to return my MyBook Live device, but I thought I would try to upgrade the TwonkyMedia Server on my own first. I successfully upgraded from 5.1.9 to 6.0.32 today using the following version:
You should be able to verify that TwonkyMedia Server 6.0.32 is up and running at this point by pointing your browser to the TwonkyMedia Server config page ( http://:9000/config) or by going to the MyBook Live UI and viewing the settings page for TwonkyMedia (Settings > Media > Twonky > Status). Either page should show the TwonkyMedia Server version as 6.0.32.
This version of TwonkyMedia Server requires a license after the 30-day trial period ends, but at least you have that amount of time to evaluate it. I downloaded this version because I had problems streaming MKV video files from my MyBook Live device to my Samsung LED TV. I verified that this version resolves that issue.
I am not sure you understand how difficult it is to release software. Moving to a major release like twonky 6 (assuming it even passed our tests) requires quite a bit of effort -including certification testing (DLNA, Microsoft, etc.) , system testing, and compatibility testing in order to have the highest quality release.
Are we happy with Twonky 5? For the most part it is been reliable and bug free. There are always newer software stacks and services that we are looking at for this as well as future products. We definitely are looking at these moving forward.
One last point, we do not endorse nor will we support user modified changes to our product. You are on your own if you go and make changes like this to your My Book Live and most likely you will void your warranty.
Just give us the choice to upgrade/not upgrade Twonky. That may be an option in Twonky UI. So if you got some problems with upgraded Twonky, you always can reflash to original FW and get 5.1.9 Twonky again.
Tried it with Internet Explorer, Mozilla Firefox and Linux Shell wget command. Always an empty page is returned. Via google I could find that this is the case when twonky configuration parameter enableweb=1 is configured instead of enableweb=2. With enableweb=1 only localhost (here Linkstation LS-WXL) is allowed to access twonky configuration webpage on port 9050.
1. Linkstation with firmware 1.24 and 1.26 comes natively with twonkymedia 4.4.19_e2. with this twonky version access of webconfiguration on port 9050 is working. It is installed in directory /usr/local/twonky
2. Beneath twonky version mentioned above, firmware 1.24 and firmware 1.26 contains some very secret mechanism to do an automatic update of twonky to version 5.1.1. To do this, there is a program /usr/local/sbin/majishanzu which downloads twonky 5.1.1 from a https secured buffalo server using private certificates.
This new twonky 5.1.1 version is installed in directory /usr/local/twonky-alt. This majishanzu tool can be started manually, too. You will then see that /usr/local/twonky-alt will be created containing twonky version 5.1.1.
After this, the atomheartmother and initdx process is running, but mediaserver is not running. It seems that out of some unknown reason atomheartmother and initdx (probably two monitoring processes) could not start new twonkymediaserver process.
4. Downgrading back to firmware 1.24 does not work anymore if you are one of the "lucky" ones where twonky autoupdate mechnism has already started. After downgrading to version 1.24 in linkstation webconfig media server page, you will then always get an error box telling "During firmware update media server could not be updated. Connect to internet and restart mediasserver." This is because the "majishanzu" autoupdate tool tries to download twonky 5.1.1 from secret buffalo server. But there it only finds version for firmware 1.26 which can not be installed in firmware 1.24. In /var/log/message one can see error messages that firmware is too old / not matching.
I have a QNAP NAS TS 209 SII running a Twonky media server (Version 6). I've password protected the web server where the Administration's page is exposed. I Have also a Twonky media server running at the port 9000 which uses its own web server and NOT the apache one.
Not really a plugin but close enough Had to try it out. Install is really for Fedora and most of the guides I found for installing on Debian were for version 6. Here is what I did to get it working (haven't tried transcoding yet and still playing).
I agree with your likes and dislikes. I would add to the likes the fact you can view by date. This shows me items recently added and most likely to wathc. I would add to the dislikes that transcoding is not easy to configure (haven't done it yet). I don't understand why they don't have an Ubuntu/Debian installer.
I agree. My past experience with transcoding has been bad. I tried twonky in the past running under WinXP Quad core and the clients struggled to stream the movies because the server could not keep up...and these were only DVD VOB files..i.e. Standard Definition. So for me Trancoding is a non-flyer on my HP-N40L microserver which has low-spec AMD dual-cores. There's no way they can transcode HD on the fly AND stream simultaneously. May be the new s/w is a bit more efficient...may try it.
Please also keep in mind that above manual prepared for x86 architecture as my system runs on OMV 2.2.5 i386 due to lack of powerful hardware. So if need x64 architecture, please download media server and library file in first step accordingly.
Glad to hear, that's what I've found reading on the topic. A few screenshots from the twonky server interface. IP's blocked, but the twonky server sees the control 4 ea1 control via its mac and ip address. What else could I share that would be helpful?
It is a westerndigital mycloud NAS, with Twonky from the factory. I'm not sure if it can be updated to a newer version. There is no options to turn on SMB1 in this version of Twonky. Do you use Twonky on a Synology NAS?
TwonkyMedia server (TMS) is DLNA-compliant[1] UPnP AV server software originally offered by TwonkyVision GmbH. TMS runs on Linux, macOS, Microsoft Windows, iOS, Android and QNX operating systems. TwonkyMedia server can be used to share and stream media to most UPnP AV or DLNA-compliant clients, in addition to non-UPnP devices through the HTML, RSS, and JSON supported front ends. After the PacketVideo acquisition of Berlin-based TwonkyVision GmbH by 17 October 2006,[2] Twonky was renamed PVConnect in November 2007,[3][4][5] but the name was changed back to TwonkyMedia server by 7 January 2010.[6][7][8] Corporate parent NTT DOCOMO sold PacketVideo NorthAmerica and Europe to Lynx Technology on 10 May 2015 and PacketVideo Japan exactly one year later on 10 May 2016 transferring the Twonky product line to Lynx, renaming TwonkyMedia Server to Twonky Server.[9][10][11]
I pulled down the file and put it on the flash, but where is the "go script"? I see one in /var/tmp and another in /var/log, I don't see one specifically on the flash drive when I look at it through windows.
b37509886e