[mythtv] Broken AV sync after mythtranscode

Geoffrey Hausheer mythtv0368 at phracturedblue.com
Wed Jan 4 01:15:01 UTC 2006

On 1/3/06, Taylor Ralph wrote:
> I did run into an A/V sync issue with another
> recording that started right after a deleted
> commercial. Due to time and hard drive constraints
> (large HD file and I was away on vacation) I had to
> delete the file. In the future I'd like to help debug
> these situations. So I have a few questions.
> 1. Does your code provide alerts if it detects that
> the source material has sync problems?

No.  If you run with higher verbosity, you can get some info, but in
general, this isn't something that is easy to display concisely.

> 2. Do you print out the commercial cut points in the
> log so the problem can be reproduced from the command
> line using the mpg.old file?
Not unless you add some verbosity.  I could easily change this though.
 I'll make it pront by default.

> If so, how do I do this?
you would run mythtranscode -i <file.mpg.old> -o tmp.mpg -l "start-end
start-end start-end"

> Or better yet could you print out the exact command
> needed to reproduce the results in the log?
I'd rather not do this.  It ties the code too tihtly to mythtranscode
(I build the same code as a standalone app too, which takes completey
different arguments)

> 3. Does it help avoid sync issues if the cut points
> are moved to keyframes?
Nope.  No reason to do this.  If it works on a keyframe and not
somewhere else, it is a bug.


More information about the mythtv-dev mailing list