Note that until you restart it, the Twonky config page will still be on the previous port (ie 9000) only after you restart it will it appear on 9001 I then restarted it from the Twonky settings page (under advanced) and I had to then put the below into my browser to find it. In my case, my NAS is on 10.10.10.20 and thus I put the below into a browser's address bar:Īfter hitting enter, you get a mostly blank page returned it just shows the new port (in my case, 9001) The DMS (UPnP server) functionality seems to be useless currently.I just installed the QPKG version and tried the RPC method (as that saves faffing about with the config files) on the latest QPKG version (7.0.13) and it worked fine (and I know it works with all previous versions). With firmware 0.5.35 the device does not offer any UPnP/DLNA service for streaming all the functionality (except the device announcement) is realised in another standard outside of UPnP. This device seems to be based on the Astra reference platform and similar to Triax TSS 400, Schwaiger MS41IP and Zinwell ZIM-1800. UPnPlay is using a invalid service declaration and is not supported by eezUPnP.These clients are referred by users as not supported (not acting as UPnP renderer):.Toshiba 37XV733 (works with WAV and MP3, no OGG).Philips SLA 5520, Philips NP2500 (there are problems in combination with Twonky server).but why? Both versions are using the same code base!)
0 Comments
Leave a Reply. |