SONOS not playing specific files

@trumpy81 No luck. I’ll check it tomorrow but for some reason an album that I imported yesterday which wasn’t working yesterday is working today. I’ll check tomorrow and see if the album I dropped in today is working.

@Volts are there any concerns around DMCA and sharing a sample file? Is there a way to put the engine into something like a debug mode to see what it’s doing when it analyzes and imports the media?

@trumpy81 is there a way to manually kick off the maintenance jobs that would have run overnight?

@trumpy81 oh, I was under the impression that there were system-wide maintenance jobs that ran nightly. I’ve done analyzed the album or dozen or so times with no change. I’ll see if anything changes tomorrow.

@trumpy81 but that doesn’t give me instant gratification. :slight_smile:

Just updated it which should run starting less than 10min. Fingers crossed.

1 Like

Analysis for an item can be forced with ./Plex\ Media\ Scanner --analyze-deeply -x --item 12345.

But I’m not sure what it takes to run the Scanner from the CLI on Synology. It might just be LD_LIBRARY_PATH like Linux. Dunno.


PM a link to a file, if it happens here I’ll compare and try to reproduce it on a shareable file without a licensing issue.

That doesn’t trigger Deep Analysis for video files. I wish it did. I’d have to check … does it for music?

For videos Deep Analysis happens during maintenance. (Or can be forced via the CLI.)


But the Dance would remove any Deep Analysis info that had previously been performed, at least until it was performed again. That would be informative too.

It’s working now about 25min after the adjusted maintenance window started. The metadata in the file info XML are also filled in with a bunch more information. Below is a comparison of the before and after.

@trumpy81 odd. I manually analyzed it at least a dozen times. Why would it take maintenance to actually trigger the files to be analyzed?

I even tried creating a new library with just that one album and it failed there as well.

I think the Deep Analysis / requiredBandwidths issue was resolved in 1.24 and higher.

  • (Analysis) Bitrate analysis was sometimes incorrect when file contained image attachments (#12882)

The sample .flac you sent includes an image attachment.

I tested with 1.23.6. Deep Analysis of your sample file results in this:

<Media id="407809" duration="458706" bitrate="863" audioChannels="2" audioCodec="flac" container="flac">
<Part accessible="1" exists="1" id="434976" key="/library/parts/434976/1628546301/file.flac" duration="458706" file="/path/to/file.flac" size="51386717" container="flac" deepAnalysisVersion="4" hasThumbnail="1" requiredBandwidths="2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,2147483647,2147483647">
<Stream id="965134" streamType="2" selected="1" codec="flac" index="0" channels="2" bitrate="863" albumGain="-7.32" albumPeak="0.950775" albumRange="4.149579" audioChannelLayout="stereo" bitDepth="16" endRamp="-16.66 0.11;-14.54 0.31;-10.72 8.61;-8.54 11.11;-5.63 12.41;-1.67 15.81;0.09 15.91;3.33 16.31;6.29 27.01;" gain="-7.32" loudness="-10.68" lra="4.15" peak="0.950775" requiredBandwidths="860,860,860,860,860,860,860,860" samplingRate="44100" startRamp="-51.00 0.00;-39.91 2.70;-29.81 5.30;-23.81 6.60;-20.64 7.00;-17.60 7.50;-14.78 8.40;-11.56 10.00;-8.60 10.60;-5.78 20.00;-2.99 25.00;0.21 31.60;3.20 37.50;6.25 57.20;" displayTitle="FLAC (Stereo)" extendedDisplayTitle="FLAC (Stereo)"> </Stream>

In particular, the Part requiredBandwidths values are wrong.

With 1.24, it now produces accurate data.

<Media id="407809" duration="458706" bitrate="863" audioChannels="2" audioCodec="flac" container="flac">
<Part accessible="1" exists="1" id="434976" key="/library/parts/434976/1628546301/file.flac" duration="458706" file="/path/to/file.flac" size="51386717" container="flac" deepAnalysisVersion="5" hasThumbnail="1" requiredBandwidths="3023,3023,3023,3023,3023,3023,3023,3023">
<Stream id="965134" streamType="2" selected="1" codec="flac" index="0" channels="2" bitrate="863" albumGain="-7.32" albumPeak="0.950775" albumRange="4.149579" audioChannelLayout="stereo" bitDepth="16" endRamp="-16.66 0.11;-14.54 0.31;-10.72 8.61;-8.54 11.11;-5.63 12.41;-1.67 15.81;0.09 15.91;3.33 16.31;6.29 27.01;" gain="-7.32" loudness="-10.68" lra="4.15" peak="0.950775" requiredBandwidths="860,860,860,860,860,860,860,860" samplingRate="44100" startRamp="-51.00 0.00;-39.91 2.70;-29.81 5.30;-23.81 6.60;-20.64 7.00;-17.60 7.50;-14.78 8.40;-11.56 10.00;-8.60 10.60;-5.78 20.00;-2.99 25.00;0.21 31.60;3.20 37.50;6.25 57.20;" displayTitle="FLAC (Stereo)" extendedDisplayTitle="FLAC (Stereo)"> 

After upgrading it might be enough to wait; I think Plex will see the “old” deepAnalysisVersion and upgrade analysis during maintenance.

Or you could Dance all of the files.

Or I searched my database for items with 2147483647 and forced a refresh for them manually.

@trumpy81 @Volts

thanks for the detailed analysis and help on this. my takeaway is that I’ll just chill and be patient next time. :slight_smile:

thanks again!

1 Like

Wow! Thank, I enabled everything in scheduled tasks, changed the time and waited. Everything works now, all my flac files play on Sonos.

My server is whatbox and Plex plays inside the Sonos app.

All working now for me, I hope it stays that way!

May I install now 1.24.1.4931?

Thank you so much. Works perfectly.

1 Like

I have the exact same issue and there is nothing wrong with the FLAC files. Readding the same FLAC files (with different meta data) creates the issue. Meaning the formerly added FLAC files are working fine and the newly re-added files (only having different album-interpret) are not played by Sonos. There is a bug in PLEX introduced to handle the scan of FLAC files. which should be fixed.

@Volts I think the issue is created by a bug introduced in the scan library files functionality which is not correctly analyzing new scanned files with the FLAC format (MP3 is still working fine). There are 3 options to fix this for the standard users (not going to CLI):

  1. Fix the “scan library files” to do the FLAC file analysis correctly.
  2. Fix the analyze functionality that the data is correctly build up for FLAC files.
  3. Add a deep analyze web interface point to initiate the workaround manually per scanned music
    Nevertheless it is functionality which worked before and was broken with an update.

Share a sample?

@Volts you can create the files yourself (with the latest PMS version):

  • stop maintenance (or run them only during the night)
  • take any FLAC file you want and add it to your file structure of a library
  • do scan library files for the music library
    If you do not have a FLAC file, use fre:ac to rip a music CD.

Can you restate the problem you’re experiencing and how to reproduce it - what happens in bullets 4, 5, 6, … after adding a FLAC file to the library?

@Volts for some years I ripped my CDs with fre:ac in the FLAC format. I copied them to the file structure of my music library on the Synology NAS (DS218+) and initiated then via the webinterface the “scan library files” function. Afterwards I corrected some meta data if necessary. Then everything was usable via Sonos (with the PLEX module/plug-in). Since the implementation of PLEX 1.24.4.5081 this process did not work anymore. With PELX 1.23.3.4707 everything was fine. Sonos did bring the message that the connection was closed by the Plex server. A deep analysis (marked in the maintenance job) could fix this over night, but that is not was you want. It should directly work after the “scan library files” functionality. The same workflow is still working with mp3 files (without deep analysis). Only the FLAC files (I tested FLAC 1.2.1 and 1.3.3 - thus it is independent from the FLAC version). Thus for me clearly somewhere between plex 1.23.3.4707 and 1.24.4.5081 the “scan library files” functionality is not building up correctly the analysis data for FLAC files anymore. Please look for the difference between those versions.

Just raised a new issue (FLAC file bitrate not calculated when file imported to library) that looks like this problem is still occurring (I didn’t see this issue before I posted). Hopefully an easy fix for Plex now it’s clear what the problem is!