frl
14th December 2009, 21:11
Hi all,
A while ago I spent ages trying to find a solution to batch encoding my DVDs to a format that my AppleTV would accept. I ended up putting together a script that encoded the video to x264 with AAC and AC3 audio muxed together using Crypto's mp4creator (as bundled with mp4muxer).
Since getting Quicktime 7.6 foisted upon my PC by iTunes, I've noticed that my encodes have gone a bit funny in Quicktime. It appears that the length of the video track is mutiplied by the number of audio tracks, so a 1 hour video with 1 audio track becomes a 2 hour video track. If there are 2 audio tracks, it becomes 3 hours, and so on. Watching the file in Quicktime shows that the video track seems to be on a loop!
I'm not hugely bothered by this so far, but my concern is that the next AppleTV update may bring in the same problem to it. I'm wondering - and this is where any input would be hugely appreciated...
a) has anybody else seen the same issue?
b) is there any software I could use to inspect the structure of the file to see why on earth quicktime might be getting it so wrong?
I can upload a sample if anyone is interested in the weirdness!
Cheers,
Chris
A while ago I spent ages trying to find a solution to batch encoding my DVDs to a format that my AppleTV would accept. I ended up putting together a script that encoded the video to x264 with AAC and AC3 audio muxed together using Crypto's mp4creator (as bundled with mp4muxer).
Since getting Quicktime 7.6 foisted upon my PC by iTunes, I've noticed that my encodes have gone a bit funny in Quicktime. It appears that the length of the video track is mutiplied by the number of audio tracks, so a 1 hour video with 1 audio track becomes a 2 hour video track. If there are 2 audio tracks, it becomes 3 hours, and so on. Watching the file in Quicktime shows that the video track seems to be on a loop!
I'm not hugely bothered by this so far, but my concern is that the next AppleTV update may bring in the same problem to it. I'm wondering - and this is where any input would be hugely appreciated...
a) has anybody else seen the same issue?
b) is there any software I could use to inspect the structure of the file to see why on earth quicktime might be getting it so wrong?
I can upload a sample if anyone is interested in the weirdness!
Cheers,
Chris