PS You can enter the key via the Twonky web interface ( ) or if you are as lazy as I am, you can RPC your new key into Twonky via entering the below command (though with a valid key) into your browser, then hitting the enter key: I also updated my TS-219P and as expected, the Qnap supplied (ARM) version of Twonky was not disabled by the 4.3.3 update (though curiously, it didn't show as being running on the 'my apps' page, but it was all working okay I've just shut down the 219, so next time it's up, I'll see if that status has changed on the 'my apps' page). It all seems to behave itself (no high CPU issues, or the likes) and I already had a few Twonky 5 keys from the olden days (when I used to discuss issues directly with the Twonky engineers) so I applied one and it all worked as expected (and I installed a slightly tweaked music tree changing the artist container to an albumArtist container).Ĭuriously, when installing the tree I noticed the installation directory is now called 'TwonkyServerEU', but everything else appears to be just as before (other than it now requiring a key).
I have just updated my TS-453 Pro and yes, Twonky didn't work, so I did a search and found the Twonky NAS build pages are still on the go, and indeed, the later ones seem to include various Qnap builds, so I removed the Qnap Twonky package and installed Twonky 8.3 (for my Qnap, it was the 'Qnap x86-64 package') from their site.
0 kommentar(er)
