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!!!
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.
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 . 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.
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.
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)ā¦
Enable the QNAP Club repository in the App Center (if not already done)
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.