I was just wondering if there are any negative effects of using blockbuster for all my scripts, besides added "noise" and an increase in file size.

The reason I ask is I have backed up a couple of my dvd's, and I am having trouble with scenes that are all black, with text. This usually happens during the intro credits and the end credits, or when the movie is divided into "chapters", and the title of the next "chapter" in the movie is displayed. During these parts, the playback is fine, but the text is usually displayed in several locations on the screen, simutaneously. It is very annoying and is hard to read. This only happens on my standalone, and I have tried several other players, and tried raising my min. bitrate.

Well I used blockbuster for a fairly dark movie, and I noticed this stuttering or displacement of the text was gone during the beginning of the movie, and during the credits. I went back and used blockbuster on a documentary I had problems with previously, and now the problem is totally gone.

I still don't know if this is a fluke or not, but I am thinking about using it for every script to prevent any problems in the future. I am just wondering if there are disadvantages or ideas as to why I may only want to use it on dark movies or lower resolution backups.

Thanks

Do you mean a "ghost" effect?

__________________
Rui

No there is not, except to add too much noise (visible noise) if the parameters are too high.

Yeah, that is reported on some standalones. Nice to know that blockbuster is a solution to avoid this !

@rui
No, he does means a duplicate effect ! Some people reported taht yet. When you have a blck screen with a little part only that is white, this part is displayed in the four corners of the screen !

*g*
Never seen such effect.
Nevertheless I'll note that the solution is adding noise
Thanks Phil
Cheers

__________________
Rui

Something to do with a too low bitrate?

Not sure :

It would be very interesting to test. I'm not too sure the encoders can actually keep a certain minimum bitrate when there's just too little to quantize. Isn't that what Inc found when he played with his KeepMinBitrate function?

Yup! I never saw such a visual effekt of white typo on a black Backgr. but its a fact that also CCE doesn't keep the min bitrate setted in the options in some cases like libavcodec, thats why I did that keepminbitrate function.
I never had probs in DVDmode even bitrates go below 200kbit. But for some sensible players that function "should" work. But its nonsens if users say "in libavcodec my player cant handle very low bitrate scenes and with CCE I dont have Probs"... If you want to force the encoder directly to keep a min bitrate then this can be done eith TmpgEncs "padding" option. And also PeterCheats implementation to Libavcodec to keep the min Bitrate (also padding in here I guess).

Hey guys,

Thank you all for the responses. So far this "solution" is working for what I want to do, so I am happy again