I am out of options and coming to the experts here to help. I unchecked it, changed the Device Media Receiver Type to Sony Bravia, and no luck. I figured that maybe the software is overriding my selection because that box is checked. Then I noticed there is a checkbox checked on that device settings screen that says "Enable sharing for new media receivers automatically". I go back to the device setting and it was set back to "Generic Media Receiver". Here in lies the issue, when I hit save, the Twonky Server doesn't show up still. So, clearly, I thought, that's the problem, lets see if Sony Bravia is in the drop down and voila, it was. I checked the profiles at ip:9000 (in Settings -> Security -> Devices) and noticed that the BRAVIA KDL-40NX711 (my bravia TV model) shows "Generic Media Receiver" under Media Receiver Type. In the video section, the Twonky Server does not even show up. In the photo section, it shows the Twonky Server and I can play those videos. In the audio section, it shows the Twonky Server and I can play those audio files. When I go to the menu on the TV, there is an audio section, a photo section, and a video section. The 2nd is a Sony Bravia TV and that's where the problem begins. A blue ray player which plays my audio, video, photos perfectly. I have a MBL and installed the latest version of Twonky 8.5.1. Thanks for the instructions here, followed it step by step and it works great except in 1 scenario. Okay what a great site and still alive after so many years. Clearly I have made a mistake somewhere along the line and if you can spare the time to get me back on track I'd really appreciate it. Out of interest I took a look at the contents of the Twonky folder, which contains just one file: So I'm guessing my installation is faulty. bash: /etc/init.d/twonky: No such file or directory I tried the stop Twonky command to see if Twonky actually is running and got this response: If I use this IP address with the 9000 port I get an error page 'refused to connect', even if I am logged in to the user interface. The MBLD does not respond to the browser command you provided: yourip:9000. I have carried out all the steps with the greatest care but do not have Twonky running. I consider myself an above-average user of IT and am happy enough with MS-DOS command line interface so, although I have no experience of Linux, I reckoned I could have a go at following your guide. When I first bought the MBLD, it had the Twonky server built in, but it disappeared after a firmware upgrade and now only offers DLNA, so I'm guessing my drive is suitable for this reinstallation of Twonky server. Have found my way here after frustration of not being able to get music files on my WD MyBookLiveDuo to serve up in track order via either a QED UpPlay Stream or a Yahama WXAD-10 streamer, rather than alphabetical order. I am still running twonky on trial and won't buy it if this issue keeps happening.ĭoes anyone else have the same experience and if so, any way to overcome it? If I leave it for a while (overnight) then the same thing will happen. When I do a 'twonky restart', the web page will immediately load and I will see everything running again. When I ssh into MBLD, and run 'twonky status', it will show that twonky is running. It doesn't time out and it doesn't come back with a 404 error. Then I come back after a while (I have not actually tested how long but so far overnight will cause this problem already) and when I try accessing the twonky server at port 9000 - the web page will just be waiting for respond. I will start twonky and the web server running at port 9000 will work. I am not sure if its caused by the device going to sleep though. I have a similar problem as howgie above. My MBLD DLNA now works again with this hack. Agreed and thank you Dav-M for such a wonderful guide.
0 Comments
Leave a Reply. |