Twonky can't even handle MM playlists, which end up needing export, and for autoplaylists, the server just crashes. Not only that, but it would save having to have a second database, one of which seems to require a rebuild more frequently than it should. Internet & Network tools downloads - Twonky Server by PacketVideo and many more programs are available. MM's library shows no hick-ups and allows for a lot more customization that would be nice if it could serve my upnp system. Download twonky media server windows 10 for free. But Twonky's own DB is limited, and it breaks down with my library (which is only at around 15,000 tracks). How is MM really doing anything?Īt the moment, my system really isn't any different (except I my Computer is the server rather than a NAS). and then you are just choosing your music from that Twonky DB (i.e the Twonky Server). i.e Twonky is just scanning your music after you have used MM to organize your files. So how exactly are you using MM? It seems to me you are just creating a second database. The rest of the time I just stream and stream and stream with NO pc turned on. Only when I get new music or edit what I already got I use MM and let Twonky rescan. I use Mac Minis with Twonky Media Server, works fine for me and may hit all. Both clients (UPnP like Twonky) are controlled with a remote. It has great media center capabilities as well as streaming to Xbox and. I stream from the NAS to the clients around my appartment by the means of Twonky (see below). The tech team needs to flag this with the product development guys.Kos wrote:Erhhh. In this case the bug isn't acceptable and should be fixed. You buy these devices and plug them in and they should work, you shouldn't need to know how DLNA works etc. This is a consumer grade product so most users expect to be able to plug and play without the need for any knowledge of how it actually works. I found no settings tinkering works for this problem. If your TV uses wifi and isn't cabled to the switch you may find this still doesn't work. Connect the switch to the Vodafone Connect Router then connect all your devices to switch instead. The temporary fix as mentioned by others is to buy a cheap switch, you can pick them up for £10 or less. The permenant solution is for Vodafone to fix this in a firmware upgrade. For those that have said they can still access the content from a PC the reason is that you're using a different method of connectivity, not DLNA. The Twonkymedia Confguration file lives at: /etc/config/twonkyvision-mediaserver6.ini Inside this file you will find the following: Code: Select all Port of the http server httpport9000 The following command should give you the desired results: Code: Select all /bin/sed -i -e 's/9000/6000/g' /etc/config/twonkyvision-mediaserver6. There appears to be an option to disable this in the Vodafone Connect Router interface but disabling it does not actually turn it off. The DLNA server it uses is called Twonky. Instead it responds back with it's own DLNA server called Vodafone Station. Your TV, Amp and games console act as a DLNA client and scan the network for DLNA servers which they would normally pick up however the router is not passing the DLNA requests between the built in network ports. Check your manufacturers details and look for the DLNA logo, if it's there then this is the problem. You may not be aware that your devices uses DLNA but it probably does just like the mentioned devices in this thread. When connecting a device that uses a DLNA server to send media to other devices like your TV, Amp or games console to the router directly it will not work. It seems to be called this because in other countries like Italy they use the same/similar router but call it a Vodafone Station. The Vodafone Connect Router broadcasts on your network as a DLNA server called Vodafone Station. It is a bug and Vodafone need to resolve it in firmware. Someone from the Tech Team needs to forward the issue to the product development guys.įor anyone else who finds this question this is what I have found. When I introduce a seperate switch I can see the packets reach the Plex server and then see it respond. I was able to packet capture the source and destination and could see that the DLNA discovery packets hit the router but are not forwarded to the other device. I did some testing with a Plex DLNA server connect into one port and a PC connected into the other. (4.1.3 -> 4.2.2) After reboot, it came up with no more Twonky Server, but only the QNAP DLNA server. I decided to do my yearly maintenance and run the firmware update on the QNAP. I had twonky media server running and it worked great for all the Rokus around the house. The reply I put in the other thread is below. I have been running a Qnap 239 ProII for a few years now.
0 Comments
Leave a Reply. |