QNAP NAS: ffmpeg moving from 'User supplied' to 'System default' with no reboot nor service stop/start

[Chris_Bowie]

Roon Core Machine

QNAP 453 Pro

Networking Gear & Setup Details

Wired ethernet

Connected Audio Devices

Meridian 818/DSP8000XE

Number of Tracks in Library

Description of Issue

I have been using the user supplied ffmpeg option for years with my QNAP NAS, and generally speaking it has been working great.

After a recent update, I now find my MP3 audiobooks (stored on the NAS) or live radio stations (MP3 streams) stop working, and when I go into the Roon app on my QNAP NAS, the ‘ffmpeg: User supplied’ label has returned to ‘ffmpeg: System default’.

This happens sometimes within an hour or two of the server being rebooted, or if not rebooted, then if I stop the Roon service, then restart it, the user supplied version is used for a period of time, but then it reverts back to ‘system default’ without me doing anything.

Any ideas what could be causing this?

Many thanks,

Chris

[BlackJack]

Maybe the same as this one?

Ffmpeg changing from .exe to document

I just wanted to finish up this thread, just in case anyone runs across this and needs a solution. After looking here on the forum for answers and getting on the phone with Qnap support I found out this. The most stable way to have your Roon core on a flash drive plugged into your NAS as an external drive is to plug the drive in and format it from the NAS. I no longer see this drive in my Mac Finder but it’s ability to talk to Roon and to the NAS works perfectly. I have had no problems what so…

[Chris_Bowie]

Thanks - I have formatted the external drive as NTFS from the QNAP app and recopied over my files and have restarted the server - let’s see how it goes!

[Chris_Bowie]

Sadly that has not fixed the problem - has reverted to ‘System default’…

[BlackJack]

Then I suggest you contact QNAP support like the OP from the thread linked above did so they can (maybe) help you find out what software changes your file or file attributes.

Note: It’s not Roon that changes the file (attributes) on your NAS as far as I’m aware.

@Ffmpeg changing from .exe to document

I no longer see this drive in my Mac Finder

This possibly is the solution, at least for the OP from the other thread, as it seems its Mac computer was responsible for the unwanted changes to the file on the share. Maybe you can find another way to prevent your computer from accessing and changing files from your Roon Server installation on the NAS? Maybe something simple as marking the file as read-only?

Note: There is no need for the Roon Server installation to be on a share (accessible from other computers) I can think of.