Re: [dvd::rip] consider frame range

Brian wrote:

> > Brian wrote:
> > > How does "consider frame range" work?
> > > Is that range used for space calculation, so maybe the credits doesn't
> > > fit on the CD afterwards?
> 
> > Yep, that's it.
> 
> Well I don't see the use of this option. If I write a CD with a movie
> file that doesn't fit, and afterwards I play it until this break, it's
> really hard to get the CD unmounted and out of the drive again.
> My laptop drive here even sounds like damagin and I can't do anything.
> Ok I don't use this option and want the file to fit on the medium.

Ok, some misunderstanding. If you check the "consider frame range" 
button the frame rate will be calculated based on the reduced number of
frames. Now when you hit transcode, just this number of frames will be 
transcoded, so everything should be fine. You get a transcoded movie 
with the credits cut off.

But if you calculate the bitrate with the reduced frame number, keep the
bitrate manually and transcode the whole movie, it most likely won't fit
anymore.

The use of this option is to distinguish two use cases for the frame 
range selection:

a) You select a frame range just for a quick test transcoding

E.g. you select a range of 500-1500, to see if the aspect ratio and 
overall quality is Ok etc. In this case you shouldn't activate "consider
frame range". E.g. the bitrate would be calculated for 1000 frames on a
700 MB disc, which is very high (resp. you'll get the max-limit of 
6000).

For the real transcoding you will delete the frame range, so bitrate 
calculation should be based always on the full length of the movie, to 
get proper testing results.

b) You select a frame range to cut off credits or something like that

In this case you want to use the frame range for the final transcoding,
not just for testing purposes, so bitrate calculation is based on the 
reduced frame number.

BTW: You find a somewhat shorter explantation of this feature in the 
docs:

  http://www.exit1.org/dvdrip/doc/gui-gui_transcode.cipp#gui_tc_bc_frame_range
  http://www.exit1.org/dvdrip/doc/gui-gui_transcode.cipp#gui_tc_gen_range

> Another point about size calculation: I figured out, that if I want a
> file to fit on a common 700MB CDR, I have to choose exactly 735MB, which
> results mostly in a 699MB file.

Hmm, these numbers look like a "kilo 1024 vs. 1000" problem, although 
all bitrate calculation algorithms are absoutely aware of this. So I 
tend to say "I don't believe you" ;) resp. "This depends on the material
and is a result of the usual size divergencies for dynamic bitrate 
encodings". But I'm not that arrogant, instead I'll check this twice, 
before I give a final answer ;)

Regards,

Joern

-- 
Think, before you code.
pgpBXVH30cw22.pgp
Description: PGP signature