mp4chaps/iTunes having problems with b-frame movie duration

[GoogleCodeExporter]

What steps will reproduce the problem?
have an MP4 containing H.264 with bframes, and add chapters to it using mp4chaps

What is the expected output? What do you see instead?
the duration should be equal to the duration prior to using mp4chaps. It is in 
Quicktime/VLC, 
but in iTunes the duration becomes much longer than the original duration.

Please provide any additional information below.
this will only happen with movies containing bframes
"clean" versions of the sample files are available at http://public.me.com/jpo, 
and also "chapped" 
versions of the files that exhibit the problem

Original issue reported on code.google.com by refulgentis@gmail.com on 15 Dec 2008 at 4:05

[GoogleCodeExporter]

If bframes.m4v is the "clean" version before using mp4chaps then please make a 
cleaner version available that does not contain any chapters since bframes.m4v 
already contains a chapter and a different playlength of audio (00:01:00.693) 
and 
video (00:01:00.560).

Original comment by u.pollae...@gmail.com on 15 Dec 2008 at 6:08

[GoogleCodeExporter]

upping two more files currently
bframes - only av.mp4 gets rid of the chapter track, my apologies, I didn't 
realize the preset I was using for 
encoding automatically added chapters, this cleaner file still exhibits the 
issue. Unfortunately this and every 
other single sample I could give you have different audio and video track 
lengths so I also uploaded
bframes - only v.mp4 - exhibits same issue, but the incorrect duration is ~90 
minutes when mp4chaps is used 
on it as compared to ~48 minutes for file with audio and video tracks.

Original comment by refulgentis@gmail.com on 15 Dec 2008 at 6:17

[GoogleCodeExporter]

Which revision of mp4v2 are you using?

Original comment by u.pollae...@gmail.com on 15 Dec 2008 at 6:39

[GoogleCodeExporter]

I was using 158, I will try a clean checkout of 159 to confirm

Original comment by refulgentis@gmail.com on 15 Dec 2008 at 6:44

[GoogleCodeExporter]

No need to use 159, the result will be the same.
The reason is the recalculation of the movie timescale which seems to disturb 
iTunes.

Original comment by u.pollae...@gmail.com on 15 Dec 2008 at 6:50

• Changed state: Accepted

[GoogleCodeExporter]

trunk@160 contains a fix that does not recalculate movie header timescale and 
duration for video files

Original comment by u.pollae...@gmail.com on 15 Dec 2008 at 8:06

• Changed state: Fixed