Unable to format audio channels using 'AudioChannels', with a value of: '6'


#1

Sonarr version (exact version): 3.0.0.266
Mono version (if Sonarr is not running on Windows): 5.14.0.177
OS: lsio docker
Debug logs: probably not required? I have trace logs saved and can upload if you want.
Description of issue:

The event log gets hammered with Unable to format audio channels using 'AudioChannels', with a value of: '6' or a value of 2 or some such entries:

I cleared logs and enabled trace and left it running, since so far I haven’t been able to divine what triggers this message or where it comes from.

14k entries since I cleared logs/events about 6 hours ago, see screenshot!
I think it’s the same ones over and over again on a schedule…

So here is the first occurence of the message in trace logs:

18-11-10 11:10:16.6|Trace|Http|Req: 184783 [GET] /api/Episode?seriesId=127
18-11-10 11:10:16.6|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Warn|MediaInfoFormatter|Unable to format audio channels using 'AudioChannels', with a value of: '6'
18-11-10 11:10:16.7|Trace|Http|Res: 184783 [GET] /api/Episode?seriesId=127: 200.OK (81 ms)
18-11-10 11:10:16.7|Debug|Api|[GET] /api/Episode?seriesId=127: 200.OK (81 ms)

Normal trace for the same api call with different seriesId:

18-11-10 11:10:17.2|Trace|Http|Req: 184784 [GET] /api/Episode?seriesId=121
18-11-10 11:10:17.3|Trace|Http|Res: 184784 [GET] /api/Episode?seriesId=121: 200.OK (19 ms)
18-11-10 11:10:17.3|Debug|Api|[GET] /api/Episode?seriesId=121: 200.OK (19 ms)

I know, I know, link to logs… :slight_smile:
Hear me out please?

I did that first api call with the warning myself and saw that for 8 episodes in the response, this is the mediaInfo piece of the json response:

"mediaInfo": {
        "audioChannels": 0.0,
        "audioCodec": "DTS",
        "videoCodec": "x264"
      }

“0.0” hmmm… :thinking:
For other episodes, the audioChannels are listed as 5.1 for example.

I disabled “Analyse video files” years ago, but this database was inherited from my v2 install, and that option was probably enabled for a while back then.

At first sight I don’t see this behavior for series that were added / files downloaded more recently, since they wouldn’t have the mediainfo because the option is disabled.

Any way to do a cleanup? I suppose I could delete the series in sonarr and add them again so I get rid of the old mediainfo in the database?
Delete entries in the database? (I’d rather not muck around with that)


#2

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.