Hey y'all. Since many of us are intimately familiar with handbrake and converting of files, I wanted to pass on a problem I have to see if anyone else has replicated and resolved it.
In both cases, I'm using the standard handbrake appletv profile, so 2500 kb/s and adding a turbo'd 2-pass and manually selecting the audio track.
Converting regular SD material on Windows XP will go like this:
- start with an avi
- convert to video_ts with WinAVI
- convert with handbrake to m4v (mp4) for AppleTV
This process works like a charm on everything from tv shows through to multi-hour movies, and high bitrates and large file sizes, and everything looks great.
Converting 720p material on Windows XP will go like this:
- start with a mkv
- convert to video_ts with WinAVI
- convert with handbrake to m4v (mp4) for AppleTV
This process works, however, the first 5-10 minutes of video will appear choppy, after which it smooths out and looks perfect.
So, analysis: it's not bit rate, or frame rate, as neither would smooth out. I don't think it's load on the system, it's a core2duo 2.66 overclocked to 3.4 with a gig of ram - a regular movie can be converted in this process in about two hours including the 2nd pass. I suppose it could be a codec issue, but the files play fine locally before conversion.
Any guesses?
N....
In both cases, I'm using the standard handbrake appletv profile, so 2500 kb/s and adding a turbo'd 2-pass and manually selecting the audio track.
Converting regular SD material on Windows XP will go like this:
- start with an avi
- convert to video_ts with WinAVI
- convert with handbrake to m4v (mp4) for AppleTV
This process works like a charm on everything from tv shows through to multi-hour movies, and high bitrates and large file sizes, and everything looks great.
Converting 720p material on Windows XP will go like this:
- start with a mkv
- convert to video_ts with WinAVI
- convert with handbrake to m4v (mp4) for AppleTV
This process works, however, the first 5-10 minutes of video will appear choppy, after which it smooths out and looks perfect.
So, analysis: it's not bit rate, or frame rate, as neither would smooth out. I don't think it's load on the system, it's a core2duo 2.66 overclocked to 3.4 with a gig of ram - a regular movie can be converted in this process in about two hours including the 2nd pass. I suppose it could be a codec issue, but the files play fine locally before conversion.
Any guesses?
N....