Suddenly Roon on Qnap hangs when playing m4a files

@Rory_Norman and whoever else is having this issue. @crieke tested with custom ffmpeg and indeed this was the problem. I guess a solution is on the way :slight_smile:.

2 Likes

Thanks. Looks like our problem is part of a broader one that has been plaguing people for a month or so. Maybe a lot of people will be cheering when we get a solution.

Hmmmm

same issue here

i have QNAP core

AAC radio streams do not work

also AAC streams from tidal do not work

i dont have any local ac files, only flac and mp3 these work perfectly fine

i need to restart the endpoint (Naim uniti atom) to stream something else whenever this issue occurs

lets hope a qnap update solves this indeed

Same problem here! This cannot be… just wait it out… How can a simple update mess up half of the library?! I am seriously considering to just drop Roon. Listening to music should be relaxing. You pop in a track and it works every single time. It cannot be hitting play and worry about if any of the recent update caused compatibility issue with 1 piece of technology within the dozen that make up the music delivery system. This completely spoiled the whole music listening experience.

Honestly, I rather go back to the trusted CD player. It is totally reliable. It plays full range of sound and not having to worry about flac, and any sorts of file conversion issue, NAS, etc. etc. It is $10 without any of the grief. If I want music everywhere I just go with Tidal and let them figure out this BS maintaining different format of the music file. What a joke! Since when listening to music requires any of these hassle!!!

1 Like

Just an update, The support representative from Qnap said that he’s transferring the data to R&D to fix - they are aware of several issues opened in this forum because of this problem. Not sure how long will it take.

I guess it’s a legal issue that prevents Roon from distributing ffmpeg themselves.

FYI @goat, @Tony_Tsai, @Rory_Norman and @crieke.

2 Likes

Thank you Haim for initiating this conversation with Roon and t-shoot.

Well this has nothing to do with Roon…
Its a qnap issue in their latest firmware

Apple had similar issues going on with s huge osx update, all audio software was impacted for a month…

Microsoft also did something similar when suddenly after a windows 10 update the media pack was not ready and roon wouldn’t start… Also on that case all audio software was impacted…

I guess that’s what we get when updating always directly to the newest version…
(But as an it guy, I also always want to check out the new stuff)

Well, there’s also another way to look at it. If you totally depend on some component that is so vital to your application and is not considered to be hard core system stuff (like file systems, memory management etc) you could either write it yourself, or if there’s an existing component available you can include it in your distribution - of-course there are legal implications and you might need to reach an agreement with the developer of this component. At least on my mac there are several music converter (free and commercial) who redistribute ffmpeg.

Having said that, The only real complaint I have to Roon support is that they didn’t give the impression that they are really looking into it. @nuwriy did ask for details after a couple of days but a simple response that says “I got you’re input, please allow a few days to investigate” would give me much better feeling that someone is handling this. Maybe they did look into it, but they didn’t say anything - from my point of view they could have just missed my answer :frowning:. The first time I felt that someone is really taking care of it is when @crieke joined the discussion (and thanks again).

Regardless of all the above, I hope we will have a solution soon (either by Qnap releasing a fix or Roon including ffmpeg).

I had the same problem, in a different thread.
I temporarily fixed it by updating ffmpeg.


It would be good if Roon gave the impression of taking this seriously - even though it only impacts QNAP users this time and we are a small subset of users.

3 Likes

Hi everyone,

I just wanted to let everyone know that we are looking into this with QNAP. We can’t provide any specific timelines just yet, but as soon as we have more information we’ll be sure to let everyone know.

Thanks for your patience and understanding while we work with QNAP to get to the bottom of this.

-Dylan

5 Likes

Thanks for letting us know.

Thanks @Bart_Maguire that was very useful. I have now fixed it too, although I copied the new ffmpeg file in place of the old one, rather than update the PATH.

Here are the detailed steps to fix it (command line knowledge required)…

  1. Enable the QNAP Club repository in the App Center (if not already done)

Instructions here… https://www.qnapclub.eu/en/howto/1

  1. Go to the new repo in App Center and install ffmpeg - this will install version 4.3

  2. Open a SSH (putty) session

  3. Find where the current version of ffmpeg lives, mine (v3.3.6) was installed here…

cd /usr/local/medialibrary/bin

  1. Rename it to ffmpeg_OLD

mv ffmpeg ffmpeg_OLD

  1. Go to the location of the new version

cd /opt/ffmpeg

  1. copy it into /usr/local/medialibrary/bin (or wherever your original ffmpeg was located)

cp ffmpeg /usr/local/medialibrary/bin/.

  1. Restart the Roon Core

  2. Hopefully should now play AAC files. If you have any issues, rename ffmpeg_OLD back to ffmpeg again.

It looks like the QNAP installed version of ffmpeg has been compiled with most of the decoders disabled so hopefully they will fix this soon.

6 Likes

Have fix it too, thank you!!!

1 Like

Confirm this appears to fix the AAC live radio stream issue as well.

1 Like

This also solved the same problem for me - thanks.

Come on QNAP - given the fact you actively promote Roon core capabilities of your NAS products, you should be doing better than this

3 Likes

Big thanks to your detailed guidance, helped me to make it work again.

2 Likes

Daniel,

This is brilliant!!! After MONTHS of seeing half of my library gone into crap this finally is the solution that fixed it!!! Need some UNIX background in order to execute this solution though … not for the typical users. I still don’t get the relationship between Roon and QNAP. Isn’t this something they should be working it out together? It seems QNAP couldn’t care the impact of their change to downstream/depending users. And Roon doesn’t care to make this solution more accessible to the population of Roon users on QNAP platform. User suffers. It’s pretty sad.

Thanks again Daniel.

Tony.

1 Like

I believe it’s a qnap issue. Roon can’t distribute the codecs, which is why they need to also be added manually to a Roon ROCK build.

@Tony_Tsai, @ged_hickman1 - I believe there’s now a more permanent solution (until Qnap fixes the issue):

Roon Server on QNAP QTS 4.5.1 Situation - Roon Software / QNAP/Synology NAS - Roon Labs Community

Thank you, that worked!

1 Like