Rennie
26th February 2002, 16:08
My first question is. Do all the rules for a 700 mb rip apply to a smaller rip? (by that i mean the .20 bits/per pixel * frame and 65% compressibility test)
I have ripped several dragonball z dvd's now.
i wanted the filesize to be 200 mb per/episode (that's the same as the dvd, 3 episodes per cd)
now i also had to use deinterlace or else the rip would get interlaced as wel. my very first rip was 40 mb smaller than the desired filesize. how is this possible? i thought it calculated the bitrate by means of the filesize? (use gordianknot)
now my second question..
what is the reason of lowering the framerate?
the length of a dvd always stays the same. or else you get the same movies with different lengths. If the length stays the same that means that the number of frames has to decrease when you lower the framerate right?
now when in get to the second pass it gives warning that the number of frames counted is less than the original number of frames. so at the last moment it is going to correct that and change the bitrate (it always gets lower, because it wants to reach the desired filesize)
So why do i have to lower the framerate in the beginning and therefore decrease the number of frames when he is going to use the original number of frames anyway?
I have ripped several dragonball z dvd's now.
i wanted the filesize to be 200 mb per/episode (that's the same as the dvd, 3 episodes per cd)
now i also had to use deinterlace or else the rip would get interlaced as wel. my very first rip was 40 mb smaller than the desired filesize. how is this possible? i thought it calculated the bitrate by means of the filesize? (use gordianknot)
now my second question..
what is the reason of lowering the framerate?
the length of a dvd always stays the same. or else you get the same movies with different lengths. If the length stays the same that means that the number of frames has to decrease when you lower the framerate right?
now when in get to the second pass it gives warning that the number of frames counted is less than the original number of frames. so at the last moment it is going to correct that and change the bitrate (it always gets lower, because it wants to reach the desired filesize)
So why do i have to lower the framerate in the beginning and therefore decrease the number of frames when he is going to use the original number of frames anyway?