12/24/2023 0 Comments Twonky media server qnap![]() That default ini file is used (by vendors) to populate vendor specific default entries (like the paths to standard media folders, or to set a custom port, etc basically, anything they want to customise in the above settings list) but anything that you initially entered yourself (custom media paths, or the likes) will be lost and thus have to be manually re-populated via the Twonky web interface. When it does that, it also adds any pre-set defaults that were stored in a default ini file. When you do that, it looks for that ini file and if it doesn't exist, it re-creates one. That will show you a page message stating something like 'Server restarting' (thus confirming that it has accepted the RPC)Īs that Qnap instruction states, yet another way to remove the password is to simply delete (or if concerned, rename) that entire ini file and restart Twonky. Note 2: If you wish, after changing the ini file you can simply restart Twonky via another rpc option (to save having to access the Twonky web interface): Note 1: If you don't like using vi, another way to edit the file is to copy it to a share, then change permissions (so you can edit it) then use the text editor on you PC to change it, then save it, pop it back where it should be and change the permissions back (not even sure that last part is important it is only a Twonky ini file). So you can now SSH in and navigate to the above file, but rather than just deleting the entire file, you could use vi (or equivalent) to delete just these two entries (well, deleting only the parts to the right of the two = signs, thus ending up looking like my own ones), then re-starting Twonky will force it to read that ini file and thus it should no longer be password protected. So obviously, in my case the file I want to edit (or delete more on that below) is actually /share/CACHEDEV1_DATA/.qpkg/TwonkyServerEU/appdata/twonkyserver.ini Inipath=/share/CACHEDEV1_DATA/.qpkg/TwonkyServerEU/appdata Can provide access to device remotely if required.Code: Select all ininame=twonkyserver.ini Since that time network was not modified, switch was not changed ot updated, TVs did not receive any firmware update.Īppreciate your help. Once again - my last long term usage was couple months ago without any single disruption. I tried to simulate the message by skipping and "time searching" on TVs - it goes off after several skips - for some reason the TV is not able to reconnect to get more data. PC appears in the list rarely, since it is able to cache the episode completely and returns to QNAP only when switching to the next one. That minute is most likely the cache size of the unit itself. Later on same happens to second TV - gone from the list, then in a minute - stops with an error. Important point ot notice, is I was watching page where I can see the list of connected mediaplayers, so before disconnection the TV disappears from the list, second one remains, then in a minute TV gives the error and stops playing. System log is fine, no restarts, Twonky logging file is bulky but I was not able to find anything criminal there as well.Ī bit more to add: when running 3 sources simultaneosly - two TVs and VLC player on Mac, the stream outage is not simultaneous: TVs stop playing in different time, now worked 30 minutes (strange time), then one went off with "Twonky media NAS is unavailable" message. Performed disk cheking and samba file transfer performance check - everything is fine. Disable built-in TM 6.x, insatalled from QPKG one 7.x - startup, rescan of library, same issue. Tried to downgrade to 3.7.1 - same result. Network is clean, tried direct connection with crossover cable - no succes, same behavior. Ping does not interrupt when playback stops, server is fully responsive, port 9000 still open and I can restart the movie in couple minutes, when server becomes available for TV again (TVs and server are wired). ![]() It stops after several minutes of playback, showing the message "server is unavailable". My twonky sporadically stops streaming on Samsung TVs, since I have 3 of different models I proved the behavior to be the same on all of them. Not sure it is somehow connected with firmware upgrade, but started appearing after it. ![]() I have the same problem on TS-459 Pro, firmware version: 3.8.0 Build 20121114. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |