PDA

View Full Version : SHREK Error - Bitrate should be less than 9800000


recoil47
16th January 2006, 05:14
I've ran this 3 times with the latest versions of the Big 3 tools and I keep getting this error when I try to import into Scenarist.

Info -----------------------------------------
Info Start Importing
Info ------ Reading script ------
Info Importing MODIFIER VERSION
Info Importing Data
Info Importing VTS1_Assets
Info Importing VTS01_1
Info Importing VTS01_2
Error C:\DVDRIPS\OUTPUT\VTS01\VTS__01_V002-NO-CCE.P.16~9_1.M2V
Error : Bitrate (9801600) should be equal or less than 9800000.
Warning : Number of SequenceEndCode is 0.

Error Importing failed

How do I fix this?

Zeul
16th January 2006, 09:29
What version of CCE are you using? Bitrate errors seem to be occuring of late as the newest builds of CCE are released.

recoil47
16th January 2006, 13:33
2.7.01.05

This is the first DVD that I have come across this on. No other issues with all other backups running this CCE version.

Angelus
17th January 2006, 05:00
that's weird if it happened on a no-cce asset. I think what I've done in the past with this type of error is to encode the no-cce asset at a lower bitrate (like 4000 with a max of 9000 or whatever). It's helped me in the past

mpucoder
17th January 2006, 07:03
Not so weird, I have many examples of >9800 bitrate. Of course that isn't the real bitrate, only what is stated in the sequence header. Just change it with ReStream or DVDPatcher, first header only is all that is needed to make Scenarist happy. MuxMan doesn't care what the value is.

Trahald
17th January 2006, 15:26
yeah.. its almost always that 9801600 value.. i guess its that studio and whatever software they use that does that. its kinda silly that scenarist goes by that since no matter what the bitrate in the header is, it will still fail on sources that are truly are overbitrate in the actual stream.

newjack
21st January 2006, 20:21
Not so weird, I have many examples of >9800 bitrate. Of course that isn't the real bitrate, only what is stated in the sequence header. Just change it with ReStream or DVDPatcher, first header only is all that is needed to make Scenarist happy. MuxMan doesn't care what the value is.


I have tried to use ReStream on a video with which muxman had given me error of "excessive bitrate", however even though lowering the maximum bitrate it has not worked.
my project consisted of adding a DTS track to a DVD (Big3-CCE) that contains 2 tracks AC3 Dolby surround.

mpucoder
21st January 2006, 23:02
Changing the headers will not work with MuxMan since it does not rely on that value. If the mux fails it is due to either a problem (there have been a few bugs which gave that error - try 0.15M later today when the webpage is updated) or the bitrate really is too high at some point.
Changing the headers is only required to fool Scenarist if the maximum stated bitrate exceeds 9800.
Adding DTS usually results in a bitrate problem as it is a very high (for audio) bitrate encoder, and if the bit budget was already nearly used up, there is no more.