03-27-2011 07:31 AM
After the update (thanks by the way for figuring out how to do it), how does it work if you want to get the licence for the 6.0.32 Twonky? Is there simply a licencing option on the Twonky UI or do you have do a new installation? I haven't done the update yet but will probably do it if the licencing is easy.
Another disappointed WD customer who found out the MKV-streaming is not working and that WD couldn't care less.
There's a license option in the UI. Just go here to purchase a license:
And then enter the registration key they will provide you (probably via e-mail) using the TwonkyMedia Server config page:
I haven't done this step yet, as I am waiting for my 30-day trial to expire...
03-29-2011 12:56 AM
Not sure what I am doing wrong here. I was trying to do the update as per instructions, but after restarting the Twonky the version shows the same old 5.1.9. If I reboot the MBL after this the Twonky won't work at all. To get it back working I need to set the twonky_dir=/usr/local/twonkymedia-6.0.32 back to twonky_dir=/usr/local/twonkymedia-5. Couple notes:
I'd appreciate any help you can provide.
03-29-2011 06:28 AM
I've never put my hands on any version of linux. Never done a command :x
So.. Is it possible to create a clone from my wd system to a virtual machine so i can test the upgrade?
03-29-2011 01:11 PM - edited 03-29-2011 01:31 PM
Just to add to my previous message. After doing the update as ggartrelle advised, the Twonky won't start at all after restarting it from MBL UI or by rebooting the drive. If the restart is done by using "restart server" button on Twonky UI (if the server is already running), it seems to restart the server but no changes are done i.e. the version remains the same 5.1.9.
I also tried changing the /usr/local/sbin/writeTwonkyContentDir.sh to /usr/local/sbin/writeTwonkyContentDir.sh.old as adviced here:
But this either doesn't make any difference. The Twonky 6.0.32 won't start when the server is restarted. Re-editing the twonky_dir=/usr/local/twonkymedia-6.0.32 in share-param.sh back to twonky_dir=/usr/local/twonkymedia-5 and restarting the server brings the Twonky back alive.
Any ideas? Would really like to get this working...
I think I just realized where the problem is. I might have copied the share-param.sh to share-param.sh.orig, not to share-param.orig as advised (really need to get a pair of new eyes). I will check this when back home.
03-29-2011 11:45 PM - edited 03-30-2011 12:05 PM
Ok got it working now. The problem was that I hadn't updated the file rights.
But anyway, mkv-streaming is still not working. My Samsung TV just says "video codec not supported". Yet I can perfectly stream mkv wirelessly from my laptop and play mkv via USB.
03-30-2011 10:01 AM - edited 03-30-2011 10:15 AM
can you please tell something more about the 'updating the file rights'? I had the same problem - twonky doesn't start
update: finally it's running
04-21-2011 12:54 PM
I pulled this from their site, gotta love it!
As a service to our customers, we have older versions of TwonkyServer (previously known as TwonkyMedia server) available for download or purchase. Before purchasing or downloading these versions, you should be aware of three things:
04-27-2011 02:33 PM
I'm another disappointed WD customer -tired after dozens of emails and changing lots of things, with no effective answers from Twonky or WD-. I can't stream my videos on my Sony KDL-40EX700 using my NAS My Book World. After several emails to Sony and WD, I've realized that the solution is to upgrade to Twonky 6.0. I've installed a PS3 Media Server in my PC and I can stream perfectly almost all my videos from the NAS to the Sony TV. So, no Sony fault and WD/Twonky fault. We need the Twonky 6.0.
Please WD, pimp our NAS!!!!! -joking-
05-02-2011 12:29 PM
I partially agree, but recently, only after two days of ownership encountered a bug with Tronky 5.1.9 where the database somehow self-corrupted and Twonky Media Server refused to start. WD's first level support would be to factory reset the drive which is utterly crazy when all it required was to manually erase two files under Linux's bash shell.
What I found out throws back at you the statement "For the most part it is been reliable and bug free".
I am not such a guru at this but would it not be easy to have Twonky 6 in there but have additional options in a future firmware update that would allow a factory reset of individual software components within the NAS? For example, say I decided to do something stupid under the root shell under a twonkymedia folder that renders it totally broken for some script to remove the installed twonky media server and reinstalled it as if from factory WITHOUT resetting or formatting anything else. Same with the iTunes server, the Samba server, etc.... It's not rocket science.
In a matter of fact I've used the SSH access to Linux to tale a copy of every configuration file I can find so if something screws up a configuration file the I can, at least, manually copy back a previous valid configuration file hence no need for me to unnecessarily format the entire drive.
This is all simple common sense and it seems mad that the only opton available is to do a full format or a quick format. Just makes no common sense at all.
I've replaced a Lacie NAS because the WD NAS allows Linux root access so I can at least fix problems. I personally have no desire to install any additional software on it. The Lacie has a simple factory restore that was 100% effective and DID NOT lose any files. Why can't Western Digital do the same?
I wouldn't characterize us that way. You are "assuming" many things when you make comments like that.We did an extensive evaluation and testing of twonky. Decisions were made that it was too unstable and had way too many issues to ship in a consumer product.
In fact, we will have a firmware update in the next quarter that will have some exciting features...
I would temper your criticism a bit going forward.
Edit - I wanted to add some color to this thread for you all:
The misconception in this case is twofold: 1. It is very easy to change the firmwareon the units. 2. Because changing the firmware is so easy then WD isn't changing it because they don't care.
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.