Opened 15 years ago

Closed 14 years ago

#6878 closed defect (fixed)

Timestretch with AC3 passthru results in broken playback

Reported by: anonymous Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: MythTV - Video Playback Version: head
Severity: medium Keywords: ac3 timestretch passthru
Cc: Ticket locked: no

Description

Playback breaks badly as soon as I try to activate timestretch while playing a video with 5.1 AC3 encoded audio, with digital passthru enabled. Sound output is badly stuttering or just digital noise, and video skips forward at high speed (even if timestretch factor < 1).

Playback log shows that video is skipping because A/V sync believes video is always behind audio, and no amount of dropped frames allows it to catch up.

Attached log from mythfrontend -v audio,playback.

Attachments (1)

mfe.log (80.3 KB) - added by anonymous 15 years ago.
mythfrontend -v audio,playback

Download all attachments as: .zip

Change History (4)

Changed 15 years ago by anonymous

Attachment: mfe.log added

mythfrontend -v audio,playback

comment:1 Changed 14 years ago by robertm

Status: newinfoneeded_new

Can we get a retest with .23? Things have changed significantly and this issue may have been resolved.

comment:2 Changed 14 years ago by skd5aner <skd5aner@…>

I am not the original reporter, but this behavior was exhibited for me in many versions prior to 0.23. After upgrading to .23-fixes, this seems to have resolved almost all of my timestretch w/digital audio issues I had seen. (note: I do see the occasional new isue related to timestretch of playback of digitial content, but I believe this to be a seperate issue related to the new code).

I obviously would defer to the original submitter of the ticket for further comment if it resolved their issue, but I figured it would help to let you know that my tests showed this issue to be resolved. I was assuming that since the original submitter is anonymous, you might not recieve timely feedback.

comment:3 Changed 14 years ago by robertm

Resolution: fixed
Status: infoneeded_newclosed

Closing as apparently fixed-- original submitter, if you think this is not the case, follow up on the dev list for a quick discussion and if we all agree it can be reopened.

Note: See TracTickets for help on using tickets.