@support greetings, New Roon user. Had an iTunes library that I moved to my new QNAP TVS473e all-SSD NAS running Roon core. Moved the files by dropping the iTunes folder on my Mac into a monitored directory on the NAS. The Roon is playing to either: Roon Core on NAS -> Yamaha WCX-50 streamer -> M…

Hey @Neil_Carson Just reaching out to let you know we’ve just released an update that addresses this issue. Please update to build 339 and let us know if you have any issues. You can read more about the update here: [image] Roon 1.5 (Build 339) is Live! Software Release Notes …

Hey @Neil_Carson – Thanks for the detailed report! Based on your report it appears that you are experiencing the same behavior that we are investigating as mentioned by Greg above: [image] Build 334: AAC 24bit conversion - audio artefacts [Resolved B339] Support Build: 3…

Thanks @dylan and @Greg - I’ll give this a spin later today or tomorrow and will report back. Yes, it seems likely it will fix the problem, good :slight_smile:

I hacked the Roon server to include a copy of ffmpeg4 and add it to the path ahead of the built-in one; problem solved. Hope this sort of thing doesn’t happen often :wink: On to more experimentation - thanks @dylan and @Greg

@dylan Unfortunately, some tracks still have crackling on at high volume, it fixed most but not all. Going to pass on Roon for now… The software shows great promise but need to wait for it to be a bit more solid.

Thanks for giving that a try, @Neil_Carson , and apologies for the continued difficulties here. After updating FFMPEG, does this still happen for all endpoints? Or just a specific endpoint? Thanks, Dylan

All endpoints, but it’s a function of the song. Most songs play just fine after going to ffmpeg 4, but I have one that still distorts like before

Thanks - I’ll give it a spin when I’m back home later in the week :slight_smile:

Hi @dylan , works well - thanks so much, just purchased my membership :slight_smile:

iTunes import, some songs crackling

Support

Greg (Greg Stratton) August 4, 2018, 4:32pm 2

Hi Neil,

This is a known issue. You can try and update the ffmpeg file or wait for a fix that should be released in the near future. Can’t say exactly when though.

More information in this thread:

Cheers, Greg