Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#10079 closed Bug Report - General (Fixed)

Problem Audio on Freeview HD BBC Channels

Reported by: JYA Owned by: beirdo
Priority: minor Milestone:
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no


AAC/LATM playback is broken when the stream change channels configuration (e.g. go from stereo to 5.1)

Samples exhibiting the problem:

As soon as the audio configuration change, further AAC/LATM decoding will fail with decoding error messages.

The problem is in FFmpeg and this problem was recently fixed upstream.

These two patches updates myth AAC decoder to a similar version as used in FFmpeg (some changes were excluded)

Attachments (2)

aacfix-0.24.diff (67.9 KB) - added by JYA 10 years ago.
aacfix-master.diff (27.1 KB) - added by JYA 10 years ago.

Download all attachments as: .zip

Change History (8)

Changed 10 years ago by JYA

Attachment: aacfix-0.24.diff added

Changed 10 years ago by JYA

Attachment: aacfix-master.diff added

comment:1 Changed 10 years ago by JYA

Owner: set to beirdo
Status: newassigned

comment:2 Changed 9 years ago by Github

Fix AAC/LATM playback for streams with changing config

Refs #10079.

Signed-off-by: Gavin Hurlbut <ghurlbut@…>

Branch: master Changeset: b289778325e7a52995f6e5b37fce7f76e92d60aa

comment:3 Changed 9 years ago by beirdo

Milestone: unknown0.24.2
Resolution: Fixed
Status: assignedclosed
Version: UnspecifiedTrunk Head

Committed to both 0.24 and master.

comment:4 Changed 9 years ago by mythtv@…

Some recordings still seem to exhibit the problem, at least on 0.24. Here is a 40M sample that played in mythvideo, goes silent after the first minute or so of playback, and then continues silent, yet the same file with a chunk cut off the front, plays correctly.

My guess was that adding a comment to this closed ticket was the best way to report this. Appologies if that's not the prefered way.

comment:5 Changed 9 years ago by mythtv@…

Sorry. False alarm. Ignore Comment 4. It was just confusion due to an 18-day-old release not including 2-month-old changes, plus somehow the corresponding source package including the changes when the binary didn't. Now that I have built from the source package, the problematic recordings work correctly.

comment:6 Changed 9 years ago by stuartm

Milestone: 0.24.2

Milestone 0.24.2 deleted

Note: See TracTickets for help on using tickets.