Encountering a large difference between
BD to mobile, and
File to mobile,
for Main-movie encode.
6 hours vs 2 hours (File to mobile being the quicker)
Only dealing with Main-Movie (example ... Cars)
Windows XP (32 bit)
Quadcore Q6600, at 2.4ghz, with stock 8800GT gfx card.
Attempted encode: 1024 x 462 (or therabouts).
Why? Width of the Ipad screen.
Initial tests look excellent ... haven't tested a more
generic size, allowing the ipad to scale ... I'm assuming
a realtime scaler will be weaker than what I can do in
a multi-hour long encode ... at least till I verify otherwise ... as I say, I love the look of the tests so far.
Some further encoding info:
Two pass.
Stereo sound (128, or 160)
no subpics
Size target - 1500mb
I tried doing BD to Mobile directly from the Bluray-drive ... the encode time estimate was something like 14 hours.
Ripped to HD, and tried BD to Mobile from the hard drive.
The rip took about 40 minutes.
The encode time estimate was around 6 hours.
No ... I didn't let it complete ... so I suppose it's possible
it's just a very innacurate time estimate, although I did
give it maybe 20 minutes, to try to rule that out.
Tried File to Mobile from the same hard drive directories,
(this time, directly selecting the file, from inside the
STREAM subdirectory)
The encode completed in approx 2 hours.
The encode options, in all cases, are pretty much identical ... although their is some minor difference in the audio kbps choices available (after selecting stereo).
Assuming it is the same encoder, for all 3 cases,
why the huge time difference?
I'll assume the first case is just a bad idea, encoding
directly off the drive, apparently it isn't caching enough
ahead to memory/file to smooth out the conversion speed.
Probably a good idea to check the rip, before converting
anyhow.
Still leaves me puzzles about why I'm seeing such a large
difference between
BD to mobile, and
File to mobile, for just a Main-movie encode.
BD to mobile, and
File to mobile,
for Main-movie encode.
6 hours vs 2 hours (File to mobile being the quicker)
Only dealing with Main-Movie (example ... Cars)
Windows XP (32 bit)
Quadcore Q6600, at 2.4ghz, with stock 8800GT gfx card.
Attempted encode: 1024 x 462 (or therabouts).
Why? Width of the Ipad screen.
Initial tests look excellent ... haven't tested a more
generic size, allowing the ipad to scale ... I'm assuming
a realtime scaler will be weaker than what I can do in
a multi-hour long encode ... at least till I verify otherwise ... as I say, I love the look of the tests so far.
Some further encoding info:
Two pass.
Stereo sound (128, or 160)
no subpics
Size target - 1500mb
I tried doing BD to Mobile directly from the Bluray-drive ... the encode time estimate was something like 14 hours.
Ripped to HD, and tried BD to Mobile from the hard drive.
The rip took about 40 minutes.
The encode time estimate was around 6 hours.
No ... I didn't let it complete ... so I suppose it's possible
it's just a very innacurate time estimate, although I did
give it maybe 20 minutes, to try to rule that out.
Tried File to Mobile from the same hard drive directories,
(this time, directly selecting the file, from inside the
STREAM subdirectory)
The encode completed in approx 2 hours.
The encode options, in all cases, are pretty much identical ... although their is some minor difference in the audio kbps choices available (after selecting stereo).
Assuming it is the same encoder, for all 3 cases,
why the huge time difference?
I'll assume the first case is just a bad idea, encoding
directly off the drive, apparently it isn't caching enough
ahead to memory/file to smooth out the conversion speed.
Probably a good idea to check the rip, before converting
anyhow.
Still leaves me puzzles about why I'm seeing such a large
difference between
BD to mobile, and
File to mobile, for just a Main-movie encode.