Warning during compilation DVDMAestro: Max. bitrate exceedeed

[Areku]

Hi!

Today I got a warning I never got before in DVDMaestro...

Once compiled, one warning appears telling me the maximum bitrate was exceeded.


Since it's a warning, how much important is it? What does it mean actually? How come the files were parsed without problems then?

Thanks!

[Nogami]

It's just a warning that some players might not be able to handle the bitrate at a specific location (or locations).

I've had that error pop up occasionally and it was never a problem.

[auenf]

run the m2v file thru bitrate viewer, see what the peak is, it CANT exceed 9.8mbps when you add the bitrate of the audio file(s) as well.

the reason why it isnt picked up when parsing is that the 9.8 limit includes the audio, and the m2v file by itself would only pick up an error on parse if its over 9.8.

Enf...

[Areku]

It's horrible!!

Even the mpv itself! Not need to put it on my set top player...

Something weird went on with CCE!

It's the first time after 6 months that I see such nastiness!

The movie is "Los Otros" the one by Alejandro Amenabar starring Nicole Kidman.

From the half of the movie to the end I can see, when movement is on the screen, big macroblocks covering the part that moves, along with heavy flickering. The parts that don't have motion are clear though...

Why does this happen now?

I've been using Robshot's method since the beginning, with 40 successful movie compressions, all of them using 2000 as avg bitrate and 0/9800 range...

IDeas?

Tu!

[Nogami]

I've been using Robshot's method since the beginning, with 40 successful movie compressions, all of them using 2000 as avg bitrate and 0/9800 range...

Remember, the bitrate includes the audio track and any subtitle tracks you might add...

If the encoder spikes up up to 9800kbps on a complex scene and you add an audio track at 160kbps (for example), you'll go over the limit. Infact any additional audio or subtitle track would go over the limit.

I usually set my max bitrate around 9000kbps and I've never had a problem. The quality increase from 9000 to 9800 is marginal anyway. Leaves plenty of room for subtitles and audio.

[Areku]

Nice trick!

I now recall SiC suggesting the same a while ago and couldn't remember why he did ;)

Thanks!

[Arky]

Hmmm... I seem to remember one of our members saying that older versions of Maestro were less fussy about high bitrates than the later builds are. Can't remember who said it, or which builds they were referring to, though (and yes, I have done a lengthy forum search!). Anyway, I dredged this up, during my searches - perhaps it might be informative, perhaps not...


http://forum.doom9.org/showthread.php?threadid=20589&highlight=bitrate+maestro


Arky ;o)

[Ragornette]

I got this problem with 2.915a and win NT4 but someone said it has the problem with 2k also. (I went to win2k and everything was fine)
Try another version or try on another OS. I assume your bitrate is ok but maestro has trouble. If you have 2199a, try it but the new projects aren't compatible with old version of the software.

Hope it will help

Ragornette

[Areku]

It actually seems a problem with CCE since the MPV is already corrupted, not just the VOB Maestro complains about.

[Areku]

Woah!

There's more on this issue, see:

I checked integrity of original VOBs: they were ripped fine.
I checked integrity of STREAM PROCESSED (with smartripper) VOBs: they were processed fine.

I checked integrity of the mpv resulting from RobShot's method with CCE and 0/9800 as min/max bitrates AND an avg bitrate of 2600.

Why? Because a friend of mine succeeded with the SAME movie on a very SIMILAR computer under the SAME operating system and SAME CCE version.

Now I get errors on the video stream and he does not.

From minute 38 to the end of the footage, as I explained, anything that gets into motion gets disturbed by flickering lines and squared blocks, while the things remaining unanimated display fine.

Any other ideas?

I might try lowering the max bitrate to 9000 but I think it wont make any difference since it's an error on CCE, not on DVDMaestro.

Ideas then?

[Arky]

PURELY FOR THE PURPOSES OF UNDERTAKING A "PROCESS OF ELIMINATION", have you tried compiling the project with an older build of Maestro? Have you at least checked that you and your friend are using identical builds of Maestro, or is he/she using an older build?


Arky ;o)

[Areku]

Why do u keep bothering on Maestro?

I said the MPV resulting from CCE is ALREADY damaged ;)

[auenf]

some cracks for maestro break weird things, like mpeg importing.

Enf...

[Areku]

This ain't funny guys, I'm talking seriously! ;)

Forget damn Maestro! Plz! ;)

[Arky]

who's being funny?

Auenf & I are being absolutely serious. But if you don't want to believe us then that's just fine - do your own thing, we won't stop you. As I said before - I am only operating from the viewpoint of eliminating all possible variables, in a logical fashion, rather than simply assuming there can only be one cause, and still failing to find the solution.

Good luck.


Arky ;o)

[Areku]

Don't missunderstand me, BUT take the time to reread my past messages...

I'm complaining about the fact that the encoder itself which is a step which has N-O-T-H-I-N-G to do with Maestro is already messing the SOURCE file/Video asset(.mpv) that I would import LATER on Maestro.

So:

a) I don't even open Maestro (yet) to realize video asset is corrupted already.

b) It's NOTHING related to the "crack" on DVDMaestro.

c) It's NOTHING related to the DVDMaestro version.


It's simplier: for an unknown reason I'm trying to determine with your aid, someone else CAN encode without problems on a very similar equipment and someone else (me) can not.

Now, ideas?

;)

Thanks.

[auenf]

if its an encoding problem, then drop all your bios settings to the slowest, or 'fail safe'.

Enf...

[Areku]

Er.... wdy mean?

[slk001]

Just for the record, the MAXIMUM BIT RATE for a DVD is 11.08 Mbps. Of this, the MAXIMUM BIT RATE for the video portion is 9.8 Mbps, and the MAX BR for the audio portion is 912kbps. The BR for the substreams is not substantial (40kbps?).

[Areku]

That's ok, I never had any problems at all with Robshot method bfore, after 40 movies this is the first that behaves weirdly. Moreover using the same settings than my friend, I get video corrupted and he does not :-?

[ulfschack]

I got that warning too. But I used TmpgEnc at 6000 avg VBR, 9000 max. Come to think of it I haven't checked with bitviewer if this is violated somwhere in the stream.

I burned it anyway and it looked to play fine, and it wasn't until yesterday I noticed stuttering in the end credits.

I should go home and check the stream. Maybe TmpgEnc isn't all that exact about complying to the specified bitrates?

cheers

[Arky]

Just out of interest, what does Scenarist make of the file, if you try to import it as an asset..? Normally, Scenarist seems to be slightly more critical of source files than Maestro. If Scenarist offers up no complaints then that would be intriguing.


Arky ;o)

[Areku]

Arky,

Now, really, please... C'm on ;) U really read the stuff? ;)

What's the deal with Scenarist, Maestro or whichever the authoring program you use... who careas about it, if the asset I'd import into Scenarist IS ALREADY corrupted?

I really doubt Scenarist would fix it first :-??

I assume lowering the max bitrate to 9000 MIGHT solve the problem, but then, why my friend succeeded using 9800???

[auenf]

Originally posted by Areku
I assume lowering the max bitrate to 9000 MIGHT solve the problem, but then, why my friend succeeded using 9800???

did you use the EXACT same .vaf file?

Enf...

[Areku]

Obviously not but we're using the same computer, the same movie, the same CCE version, ...