Twonky disappeared after fw upgrade

[Macuser007]

grantorinosport, can you please provide the information how did you manually install the Twonky to work with FW 4.3.3 build 0174? I would like to try on my TS-453 Pro with FW 4.3.3 build 20170516.

[dolbyman]

you download it from here:


http://www.twonkyforum.com/downloads/

[grantorinosport]

grantorinosport, can you please provide the information how did you manually install the Twonky to work with FW 4.3.3 build 0174? I would like to try on my TS-453 Pro with FW 4.3.3 build 20170516.

What Doblyman linked was exactly what I did. You just manually install the software once you download it. Once downloaded you can set it up, it's pretty much the same as far as I remember from previous Twonky.

Twonky (for me, anyway) is one of those packages that "just works" with very little input of monitoring from me. That, combined with better sorting options for large libraries than other programs out there, is what makes it an obvious choice (even with a $20 license fee) for me personally.

[AdamKH]

the 212 should work with with the x19 version

not sure if the x31 actually was upgraded to 64bit ... as the trail version works for 14 ..you can always try...

also the paid license runs on 3 devices ...so most people should have no issues ..even with several qnap systems

Thanks, for the linking. I will download and try.

I am not sure if the TS431 has gone to 64bit. I did not have Twonky on that NAS so the the CF64 compatibility package did not test for Twonky. The change log for 4.3.3 on the TS431 is unclear if it is running 64bit. (The CF64 compatibility package does not run on the TS-212 so I assume that it is not 64bit).

Edit: Checking the TS431 is an ARMv7 processor so that means it is a 32bit processor. 64bit option did not come until the ARMv8.

I have tried the QNAP DNLA Server and Media Streaming Add-on. That seems to work file on the TS-431 but I am having huge problems with it on the TS-212 which QNAP Support are looking into (constant 40% CPU utilisation and 45% RAM usage). It took 17 hours to index the music library of 35,000 tracks.

In addition on checking the DNLA stream on the TS-212 it seems that the Media Streaming Add-on/DNLA Indexing is not picking up the ID3 Tag information correctly. This is a carefully curated library of over 35,000 tracks managed by Helium and MP3Tag. Everything is contained in the MP3 Tag Metadata.

It is creating non-existent Genres or not picking up the Genre in the MP3Tag, not picking up the Composer, mixing up the track numbers with the disk number, not pulling thumb nails from the ID3 meta data, Also, it does not handle direct address M3U playlists etc. I cannot go through 40,000 tracks checking these (and I have another music library of 35,000 tracks) trying find out the errors.

I really don't mind QNAP dropping Twonky from standard support. That is their business decision. However, they have to provide a credible alternative, and they have to give reasonable de-support notice.

[AdamKH]

Installed Twonky on TS-431 and TS-454A using packages from link provided.
Very clean & quick install and indexes built quickly.
Just waiting now for QNAP support to explain why the TS-212 hogging CPU & RAM without any background tasks and why the QNAP standard DLNA packages cannot handle properly MP3 Tags... Then I will install Twonky on the TS-212.
Just crazy that after using Twonky free on QNAP for the last decade why the have decided to dump it. But then the same applies with Kodi which is a far cleaner, more efficient and elegant app than Plex.

[AdamKH]

I am a little bit lost here.

Yesterday, I installed Twonky on both the TS453A & the TS431. I added some folders to be indexed and it worked well.

Today, after powering up my laptop I logged onto both NAS drives and attempted to open the Twonky QPKG package. This failed to open on both NAS drives. The web page was not accessible and had an address of //192.168.1.1X:9000 (I think).

I had to uninstall Twonky on both machines and reinstall. I have now saved the settings web page in my browser and set the page to have an administrator password. That is fine as I am running fixed ip addresses for the relevant NAS drives but those addresses will change shortly and I may want to run dynamic ip addresses in the future.

Can anyone advise?

[dolbyman]

webserver issues maybe?

platforms are very different
arm 32bit vs intel 64bit

[karlegas]

I am a little bit lost here.

Yesterday, I installed Twonky on both the TS453A & the TS431. I added some folders to be indexed and it worked well.

Today, after powering up my laptop I logged onto both NAS drives and attempted to open the Twonky QPKG package. This failed to open on both NAS drives. The web page was not accessible and had an address of //192.168.1.1X:9000 (I think).

I had to uninstall Twonky on both machines and reinstall. I have now saved the settings web page in my browser and set the page to have an administrator password. That is fine as I am running fixed ip addresses for the relevant NAS drives but those addresses will change shortly and I may want to run dynamic ip addresses in the future.

Can anyone advise?

I have similar problem not access to the web page interface through port 9000, reinstall doesn't fix, firmware 4.3.3 vs Twonky 8.4.1

If was a webserver problem how change the port for Twonky? Twonky is running but I can change the settings.

[AdamKH]

Twonky on the TS453A and TS431 worked absolutely fine with no issues other than the Webserver issue (which I can live with for the moment).

However, on the TS212 it installed well on 4.3.3 (again with the Websever issue) and indexed quickly. However it quickly became CPU and RAM intensive. This resulted in the TS212 not being visible to Windows 10 File Explorer and on some occasions not being able to map a network drive using QFinder Pro. This is exactly the same issue that I encountered with the QNAP Media Streaming add-on which is currently under investigation.

It is likely that there is an alternate issue with the TS212 which is causing problems on that device as in idle (with no packages and no access) runs at 18% CPU utilisation and 70% ram usage.

For the moment I have worked around by only using two Twonky installs (one with 50,000 tracks on the TS431, one with 39,000 tracks on the TS453A) I ran the small music repository (5,500 tracks) using Plex on my Synology DS416.

With the QNAP DNLA Server/Media Streaming Add-on I found inconsistency in reading the ID3 Tags resulting in splitting of albums, reordering track numbers and generating invalid genres.

[AdamKH]

......
Today, after powering up my laptop I logged onto both NAS drives and attempted to open the Twonky QPKG package. This failed to open on both NAS drives. The web page was not accessible and had an address of //192.168.1.1X:9000 (I think).

I had to uninstall Twonky on both machines and reinstall. I have now saved the settings web page in my browser and set the page to have an administrator password. That is fine as I am running fixed ip addresses for the relevant NAS drives but those addresses will change shortly and I may want to run dynamic ip addresses in the future.
Can anyone advise?

I have similar problem not access to the web page interface through port 9000, reinstall doesn't fix, firmware 4.3.3 vs Twonky 8.4.1

If was a webserver problem how change the port for Twonky? Twonky is running but I can change the settings.

I contacted Twonky support on an issue with my Synology and I was advised that not being able to access through port 9000 is because I had enabled Sonos Support which means that Twonky uses port 10243 in order to spoof Sonos into thinking it is accessing either Windows Media Player or Rhapsody servers.

Switching that option off resulted in a Twonky Server restart and access via Port 9000 worked again.

Simple.

I used to have Sonos as my main device for Networked Music but I was an early Sonos user and there was a limit of 32,000 tracks and there was limited memory in the Sonos devices so you could not have long track names (a problem with Opera tracks). To get around that I used a Philips Stremium hard wired as an external input to a Sonos unit and ran Twonky on a QNAP NAS for my modern music. I changed from Sonos to HEOS recently as the old Sonos equipment (10 to 12 years old) was slowly dying and HEOS supports DNLA plus Bluetooth. I needed to be able to connect Android & iOS devices as a source of other streaming inputs of music and for guests (in party mode). Sonos without Bluetooth fails in this.

For music playback the HEOS is as good as Sonos and more flexible allowing more DNLA server connects and Bluetooth connects. Unfortunately, the HEOS app on iOS and Android is not as good as the Sonos App but only because it lacks (a) the ability to fast forward through the current track that is playing, (b) it does not show the next track in the display, (c) it is not possible to create external M3U playlists and (d) there is no Windows App.

Sonos is good but Sonos do not understand music sharing in a social environment. I don't want guests to have to download the Sonos app in order to play music on my networked sound system whereas Bluetooth gives them full opportunity albeit at slightly lower quality (which does not really matter at a social event where the music playing is ancillary to the social gathering).

I only have one Sonos unit left operating and have a HEOS unit in the same room so I am not losing anything by dropping the Sonos/WMP/Rhapsody spoofing in Twonky.

[tseln]

@TonyG_qnap
I see things the way you do. At least here in Germany we have a right to features announced at sale time, even in a later firmware. I am really angry as qnap dlna server is really slow at indexing files and even worse documented. I need an option to alter the output mime type for ogg vorbis in my server in order to make my Onkyo reciever work. Twonky did that quite nicely by a device specific xml file. There are such device specific xml files in qnap dlna server too, but there is no way to find out if there is a way to configure this and how.
Oh and support was really "helpful": wanted me to mail in all support data which takes quite a time for a problem completely evident and unrelated to any malfunction. I certainly won't buy a Twonky license as I paid for it with the qnap initially. A TS-469 pro is not a cheap device in it's device class.
Anyhow it's real bad behavior towards the customer to just take away important features by an update one is forced accept because of major security risks if omitted. I hope somebody takes this to the courts and sours them their ignorance. Next time I change devices my choice won't be qnap, that's sure.

[dolbyman]

I am sure the box of my sisters Phillips 3D TV said YouTube on it (bought in Germany), that hasn't been working for years (no updates from Phillips and YouTube dropped support for old API's) pretty sure there is no class action lawsuit for this (as there are no class action lawsuits in Europe anyways)
To fix all of this I bought her a compute stick and she is a happy camper with a full blown Windows10 on her TV.

Moral of the story: Read the fine print, every manufacturer covers their behind, to remove any feature without notice or justification. And you agreed to them on purchase/install

The original post was deleted but I was the first to announce my displeasing with QNAP when they removed the free twonky license

viewtopic.php?f=213&t=127787&p=580637

I haven't updated my (non internet exposed) NAS ever since so I still have the free license, but If I had to, I would buy twonky in an instant, trouble free operation is not worth the trouble

[wooff]

I have QNAP TS-212, and twonky media was working fine for several years...
I tried internal DLNA server - but it has problems with subtitles and is slower. I also tried plex, but it is very slow and has problem with some video formats and subtitles )-:
So, I want a new (last) firmware because of security ... And I want twonky because it simply "works". Unfortunatelly, it goes against each other.

How to use twonky on Qnap TS-212 ? Was anybody already success?

Is there a way how to get a twonky licence key from running qnap with tronky? (before firmware upgrate - to use the same key and not need to buy one?)

[Toxic17]

Is there a way how to get a twonky licence key from running qnap with tronky? (before firmware upgrate - to use the same key and not need to buy one?)

Do you not think we would have suggested this if it was possible?

There is only 2 options.

1. buy the $20 license and use the latest Firmware and the latest Twonky.
2. dont buys by a license, go back to unsupported and vulnerable firmware, and use the twonky that comes with it.

Simple really.

[mjl]

Is there a way how to get a twonky licence key from running qnap with tronky? (before firmware upgrate - to use the same key and not need to buy one?)

Do you not think we would have suggested this if it was possible?

There is only 2 options.

1. buy the $20 license and use the latest Firmware and the latest Twonky.
2. dont buys by a license, go back to unsupported and vulnerable firmware, and use the twonky that comes with it.

Simple really.

Option 3: Qnap starts being nice agian to their costumers and arranges the license for us.
Option 4: buy a synology and hope they are better