No
If it's an action movie, you only have two choices: Either use a lower resolution and put it on one disk, or go for KVCDx3 (or even 704x480(576) ) but target for two CD's. With the new script and techniques, you should be able to put just about any movie on two CDs. No need for three

-kwag

OK, that's what I guessed... I did just that - targeted the movie for two discs and got a CQ value around 63 (I don't remember exactly)... But hey, to fit a movie onto two discs ain't too shabby. Especially when it look almost identical to the DVD!

That clip kwag, that clip... AWESOME!!!
I guess I'll have to start all over with my encode as soon as I get off work. It'll be SO worth it!
I'm amazed at how fast things are moving and changing on this forum. Who would have guessed that a VCD could look this good - ever!

VCD What's that

Sorry if I offended you kwag! What I meant was KVCD - of course!

Just kidding

Makes me wonder, how much time we can really get now with KDVD and this script, and also KVCD ULBR (or LBR )

-kwag

@kwag
Have you slept at all last night? You must have been up testing and tweaking, right? I went to bed at 2 p.m. and when I logged on this morning I saw the goodies! Great!

I really didn't get that much sleep last night. So here I am, in bed typing in my iBook via wireless 802.11b network
And now I'm going to bed. Let the scripts rest (for some centons)

Have fun!
-kwag

Sweet dreams, kwag!

Kwag my friend,
something is wrong with my sample in the new script.
( June 5, 2003 @05:45GMT )
i got CQ70,297 in 480x480 but the image is very "smoked"(blurred)
and with big staircases in thin lines....
with 704x480 the CQ is too low.


"sniff"

Hi Jorel,

strange...I did a view samples on 5 different movies and different
resolutions, and they all came out sharp as a knife (maybe almost a little
to too sharp for my eyes)

and hey Jorel don't "sniff", I'am sure the master himself will lend you
a helping hand...

regards, ***mfb***

No mention of negative values being blurs!

Using Subtract, I saw that T < 0 blurred more until T=-1 but then made no further differences no matter how negative I made it.

Is it just luck / bugs that make T<0 blur the image?

I know I found out because I thought it would, and indeed it did
I couldn't use BlockBuster(blur) because it didn't blur enough. I also tried another filter ( forgot now which! ), but only scaled in steps of 1, so that was a no no. So asharp used "in reverse" made our day Another nice "Feature"

-kwag

hehe some day i really must install VC++ and write that MotionAdaptiveLumaBlurWithNoBugs() plugin

LOL
That's a good one

-kwag

While you're at it, please write a "AvoidMosquitoesAroundCartoonBorders()" filter

Just made a minimal change to the script:

Changed asharp(2,4,0.25,hqbf=true) to asharp(2,4)
Changed MergeLuma(blur(0.1)) to MergeLuma(blur(0.2))

The result is sharper picture and lower file size.
Apparently "hqbf" method is still not very well optimized.
Also speed increased 5 seconds for every minute.

-kwag

Hi kwag...

I made thousands of samples today, and the script got better constantly... still haven't tried the VERY latest script ( ) with asharp(2,4) and MergeLuma(0.2)...
However, as the picture quality gets a lot better, there's still one scene in my movie, where I think Blockbuster noise would REALLY help a lot...
It's a very dark rain scene, and DCT blocks show up, and ugly artifacts all around the fast-moving rain-drops... this doesn't seem to get better, but in case worse, the more we apply sharpening...
any suggestions?

__________________
j3llyG0053

Hi Jellygoose,

Last night I played for about 2 hours, integrating BlockBuster(noise) into the script. I was able to make the variance adaptive , but at 704x480, BlockBuster really doesn't help
This was confirmed a long time ago by SansGrip, and I can confirm the same thing. Somehow, TMPEG's CQ mode can't "see" the noise correctly. You can see the noise clearly by loading the .avs in Vdub, but in TMPEG it's almost gone, and you have to use very high value for variance which then spoils the picture. So we have to find another way to deal with that

Edit: I know this shouldn't make a difference, maybe it does!, but could you code that scene with a higher MIN bit rate and see if the DCT blocks dissapear This is something I've had on on my queue list to try, but haven't got to it yet

-kwag

I'll give that a try right now, thanks for the tip kwag!

Edit: However, since it was last tested a long time ago, I'd like to give that a try too! remember CQ_VBR did beat CQ a long time ago too... TMPGEnc has changed maybe, so if you don't mind sending me the part of the script with adaptive Blockbuster variance, I'll give it a shot!

__________________
j3llyG0053