TiTLE ..............: Death Race
TYPE ...............: TELESYNC
SiZE ...............: CD1*49x15
YEAR ...............: 2008
Video Bitrate .....: 881 kbps
Audio Bitrate .....: MP3 ABR @ 128 kbps
Resolution ........: 640x320
Cam Aspect Ratio....: 2.00
Subtitles .........: n/a
RATiNG .............: 6.4/10 (338 votes)
URL .: http://us.imdb.com/title/tt0452608/
Source Cleaned up and Repack now available. Download if you like.
The subject of NTSC CiNEMA needs to be addressed, it would
seem that there's some serious confusion about incorrect ivtc,
specifically on 29.970 fps source content, when it's filmed there
are naturally more frames present in a span of 1 second compared
to the projection equipment which runs at 23.976 fps, in this
situation you will experience some frames which are a combination
of 2 film frames. This is not a typical way of broadcasting and
thus there is no consistent pattern in where the dupe frames occur.
these are the only bad frames that are really present in the
recording. But, naturally some decimation is expected by everyone,
so if you want 23.976 fps as the end result than you can only
simply ivtc in this case, you never really have "dupe frames" to
work with. Due to flickering, changing lights, noise, etc., the
same frame filmed twice will not be 100% identical. That's why
it's nearly impossible to remove dupe frames when capturing a
broadcast by camera. It's decimated to 23.976, but keep in mind
you can't be sure if the removed frames are unique or the "dupe"
frames. The idea behind bitching "improper ivtc" is that you don't
want to waste bits on frames that are identical obviously - and
you want an encode that runs at the same framerate as the original
film. That's a great idea, but impossible to perfect when you're
capturing the movie off a cinema screen with a camera. This encode
runs at the correct framerate and has been treated as good as
possible with regards to dupe frames. I know what you're thinking
"go through all 141332 frames manually and delete those that are
dupes"? Bad idea. You can't just go randomly deleting frames since
there's no pattern in the presence of dupe frames on our source.
You'd had to be sure you remove those extra frames on every second
of footage. Since there's no pattern, you'll have to delete good
frames too and some times not in a consistant pattern and guess
what that gives you. Yup, jerky movement.
Also, regarding proper size when refering to resolution, honestly
this is the discretion of the encoder, based on the source you
have. The resolution is mod16 and AR is correct to the source.
Whining about AR just because it isn't 2.35, 2.5 1.77 or whatever,
doesn't make it a valid nuke reason. Given the source, this is the
perfect AR (2 vs. 2.006).