· I'm having trouble with Roon ARC
· Other
I have an M4A file with AAC audio that plays fine on Roon, but ARC gives a "Corrupt media" error when it tries to play it.
I really don't think this is relevant, but I have a TP-link router and my Roon server connects to it via a Linksys Ethernet switch.
Hi @Dylan_Forbes,
Thank you for the report.
In the screenshot above, where did you initiate playback for this track? Was it from an Album page, a Downloads list, a Playlist, etc.?
We can see the failure event in diagnostics and have escalated to the appropriate development team. Please stand by and we’ll respond as soon as possible with further context and any workarounds available.
Hi Connor!
Thanks for the response. This was from an album page.
Thanks for letting us know @Dylan_Forbes!
Are you able to reproduce this no matter where you initiate playback? Our QA team has yet to reproduce the same issue in house, but we have a ticket in to continue to test and investigate.
If you remove the track from your downloads in Arc, and re-download it over stable wifi, do you experience the same issue?
Removing it from downloads doesn’t fix the issue, sadly. Streaming the track from my server and playing it as a download (after redownloading) both give “Corrupt media”.
I added the track to a playlist and played it from there. It gave the same error. Hope that helps!
Hi @Dylan_Forbes,
Thanks for your patience. If you’re willing to provide a copy of the offending .m4a file via this uploader, we’ll use that to reproduce the issue internally. There’s a chance this will expedite a fix significantly since this issue is specific to certain .m4a encoding.
Was this file originally in another format?
Hi Connor!
Thanks for getting back to me. I have uploaded the file.
I got it a long time ago, but I believe it was extracted from a video downloaded from youtube. I imagine I used something like
ffmpeg -i video.mp4 -map 0:a -c:a copy out.m4a
to get the audio stream from a local video file, using whatever version of ffmpeg was available in 2011 or so, but I can’t say for sure.
Hey @Dylan_Forbes,
Thanks for sending that over! Our team wasn’t able to reproduce this on the first attempt, but we’ve created a ticket to continue the investigation.
I don’t have any immediate next steps to share, unfortunately, but we will follow up with more information as soon as our team has it to share. Thanks for your patience in the meantime! 
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.