![]() |
Show all 9 posts from this thread on one page |
VCDQuality Forums (http://www.vcdhq.com/forum/index.php)
- SVCD (http://www.vcdhq.com/forum/forumdisplay.php?forumid=20)
-- Be Cool *WS* *PROPER* - DVDRIP - Flush (http://www.vcdhq.com/forum/showthread.php?threadid=62941)
Be Cool *WS* *PROPER* - DVDRIP - Flush
lol 
Tried to proper myself with first untouched footage from the first CTP release 
Besides the fuckups they (Flush) made they didnt even make it compliant in bitrate coz if u make sure it doesnt go over max bitrate for svcd it will give u an undersized CD3.
Thus in this case CTP knew what it was doing. Besides.. their 2 CD rip looked better than my 3CD undersized :P
"Flush" this down the toilet 
My advice : we've seen enough propers and repacks by now for this movie anyway, coz frankly : it sucked monkeyballs.
Yes they need to know how to correctly make a SVCD in order to proper one. hehe
it's pretty possible to fit this onto 3 full cds without violating standards, just gotta use 74 instead of 80min. while you're ranting about svcd standards, go actually read them and check on centropy's video bitrate...
quote:
Originally posted by narrf
it's pretty possible to fit this onto 3 full cds without violating standards, just gotta use 74 instead of 80min. while you're ranting about svcd standards, go actually read them and check on centropy's video bitrate...
and what about centropy being below standards with their bitrate? i'd prefer too high over too low ... even tho its not a great movie 
Coz above max bitrate for svcd will choke some standalone players.. thats why there's a standard 
Otherwise there wouldnt be a max bitrate now would there ? 
indeed, hooray for standards.
those standards also require 1750kbit+ video bitrate ... centropy fails to provide that, dont they?
on a sidenote ... centropy's be cool svcd also peaks above 2756kbit total bitrate, e.g. right at the beginning during the roaring lion ... so both might cause a few problems on some older standalones.
but then again, noone criticises centropy for that, right? 
quote:
Originally posted by narrf
indeed, hooray for standards.
those standards also require 1750kbit+ video bitrate ... centropy fails to provide that, dont they?
quote:
on a sidenote ... centropy's be cool svcd also peaks above 2756kbit total bitrate, e.g. right at the beginning during the roaring lion ... so both might cause a few problems on some older standalones.

quote:
but then again, noone criticises centropy for that, right?![]()


centropy's peaks at about 2900 video if i recall that correctly, so just like 90+% of the scene SVCDs they violate the max 2756kbit.
i use the very same program, it has a nice display of the peak bitrate ... look at it 
then ... yeah, centropy didnt sign the svcd rules. did flush sign? i doubt it, they just popped out of nowhere.
my final note in the last post didnt apply to you ... it more likely applied to "the scene", e.g. the nukers on vcdquality who didnt nuke it for violating hardware SVCD standards ... which is their job if i'm not much mistaken.
i personally like most of centropy's work, but every time i see some group get nuked i wonder why noone nukes centropy for the same reason, since they have violated the exact same thing.
their hitchhiker svcd ts ... bad audio mix, they apparently only used the center channel, resulting in missing effects (very noticeable in a scene where they wonder about a dangerously sounding ... sound ... which doesnt exist in the release). still, vcdquality didnt nuke (cuz its centropy?) ... but that's a different release, i dont wanna slide off-topic 
so, back to the release itself, my personal final verdict:
both releases violate hardware standards, so i cant play any if i have a bad standalone.
which would i watch? ... not the one with subpar bitrate and visible quality issues, thats for sure.
| All times are GMT. The time now is 06:15 AM. | Show all 9 posts from this thread on one page |
Powered by: vBulletin Version 2.3.0
Copyright © Jelsoft Enterprises Limited 2000 - 2002.