ACCESS TWONKY MEDIA SERVER HOW TO
ACCESS TWONKY MEDIA SERVER INSTALL
ACCESS TWONKY MEDIA SERVER ANDROID

ACCESS TWONKY MEDIA SERVER INSTALL

Now, where’s that MiniDLNA install guide again…? Shame it doesn’t seem to support NTFS disks, which might limit the video file support (4GB FAT32 limit). Life is too short to spend it massaging poorly designed and implemented software… I could buy a SATA to USB interface and plug it into my Technicolor 582n router, and get all the facilities offered by the WD M圜loud. Maybe time to do as others have, and rip open the WD M圜loud, pull out the disk, and use it in something more reliable. Why do I seem to be beset by rubbish software? Maybe I should read reviews before going out and buying a cheap NAS. When it refuses, and simply skips through the tracks in the album one after another., not making a squeak on the audio. All looks good, with the file structure and metadata categories all nicely populated. I’ve just tried to access the recreated Twonky server database with MediaConnect on the iPad.

ACCESS TWONKY MEDIA SERVER ANDROID

Maybe I’ll just ditch Twonky (as it seems appallingly slow to serve media so much so that MediaConnect on the iPad and MediaMonkey on Android both timeout, Kinsky on the PC is more patient) and go install MiniDLNA in its place:

Users shouldn’t have to resort to root access to the server operating system, nor destroy files to fix problems. Systems shouldn’t be corrupted by sudden loss of power, or they should recover on their own. Or discuss the issue with PacketVideo Corp, and come up with a user-friendly solution. I’d suggest adding a ‘trash & burn all Twonky settings & database and re-start from fresh’ button, as neither Twonky or the WD Dashboard were able to fix this problem. ini file, I obviously had to re-do all the Twonky settings.įor any WD employees monitoring these forums: This has stopped the error as Twonky starts up, and it appears to be re-building the database correctly again.

LOG_SYSTEM: upnp_multiuser_load : load user-db from ers: failedīy this time, I was getting somewhat fed up with rubbish software that cannot sort itself out, so I did a trash & burn on all the obvious configuration files It still seemed to be having trouble.Īfter much experimentation, I enabled loging in Twonky’s dashboard, and found that it had stopped reading the twonkyserver.ini file, reporteing an error, identical to the one found here:

But there was a db directory, so I moved that and db.info into a backup directory, and re-started Twonky. Si I installed PuTTY, shut down Twonky, enabled SSH access, logged in to the Linux as root, and found that there was no twonky.db as suggested. Now, coincidentally to the upgrade, or the power cycle, the Twonky server started playing up, reporting an error 400162.Īfter trying the usual suspects of shutting Twonky down, re-building, re-scanning, re-starting, etc, to no avail, I found this suggestion: It was okay, but I spotted a pending firmware upgrade, so I installed that and let it re-boot again. On re-booting, the NAS took a while, so I used the Dashboard to see what was going on. I foolishly unplugged my 4TB M圜loud last night, in order to sort out power leads etc.

ACCESS TWONKY MEDIA SERVER HOW TO

4: I think I’ve finally figured out how to get Twonky working in a stable fashion, so I’ve written up my findings in a

Access twonky media server