Death Race REPACK READ NFO TELESYNC XviD OPTiC--cgaurav

Death Race

http://us.imdb.com/title/tt0452608

Release Group: OPTiC
Release Name: Death.Race.REPACK.READ.NFO.TELESYNC.XviD-OPTiC
Release Date: August 27, 2008
Filename: opt-drr
Source: TELESYNC
Size: 697.22 MB | CD
Genre: Action | Adventure | Sci-Fi | Thriller
Video: Poor | XviD | 640x320 (2.00:1) | 881kbit/s
Audio: English | Direct | 128kbit/s | ABR MP3
Subtitles: None
Runtime: 1h 29min
IMDB Rating: 6.5/10 (1,740 votes)
RT Critics: 4.8/10 (101 votes)
Directed By: Paul W.S. Anderson
Starring: Jason Statham, Joan Allen, Tyrese Gibson, Ian McShane, Natalie Martinez

Ex-con Jensen Ames (Statham) is forced by the warden of a notorious prison (Allen) to compete in our post-industrial world's most popular sport: a car race in which inmates must brutalize and kill one another on the road to victory.

"Small READNFO" Part:
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 abroad cast 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 frame rate 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 frame rate 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 consistent pattern and guess what that gives you. Yup, jerky movement.Also, regarding proper size when referring 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). Thanks for Reading, and please enjoy your Feature Presentation.