Maybe it's the position, but what worries me, is that the flaw shows randomly :!:
If I loaded the .avs again, and went straight to the frame, sometimes it didn't show :!:
So it's reproduced not at the exact place, but randomly. And that really worries me :?

@All,
Also, I still insist that we won't be able to remove Gibbs ( mosquito effect ). This is a function of "Motion Estimation" inside the encoders. No matter how much we filter the input, there will always be sharp edges and movement in a picture, and there's no way to fix that unless the bitrate is cranked up way high. Any mosquito filtering would have to be done at the output (output stage of the encoder).

-kwag

kwag, have you already eyperimented with the MPEG2DEC3.dll included filters? There are some de-blocking and de-ringing post-processing filters included...
read the help file, it seems to be very interesting! :wink:

Hi Jellygoose,

Yes, but the post-processing would be "post" on the avisynth filtering, which would be "pre" (input) to TMPEG :)

-kwag

:roll: :oops: sure you're right...
however, they might help a little... maybe... 8)

Hi Kwag!

Sorry :oops: , but how can I change this, if I'm using TOK :?: :(

LaBomba

http://www.kvcd.net/forum/viewtopic.php?t=4316 :wink:

-kwag

Kwag, as allways, :D

Thanks a lot!

LaBomba

I'm getting a really wierd error when I'm loading the latest script into ToK. I get a Kernel32.dll error. But if I load an older script first and then load the latest one everything works 8O ?!
Any ideas?

@kwag

How were you able to get such a high CQ value for "Red Planet" - and at that resolution?! I've just been experimenting with "Red Planet" and the only way of getting near your CQ value is to drop the resolution down to 480x576! At that resolution I got the CQ up to 65,446 (with ToK of course! :wink: ) But if I go for 704x576 the CQ drops to almost half that number! Can it be so much difference between 23.976fps (I'm guessing you encoded the NTSC version?) and 25fps? I mean it's only 1 frame difference per second... Please, kwag, I need your help :cry: .

EDIT: Is it safe to use the PAL to NTSC conversion in ToK? If I convert my PAL movie to NTSC(Film) I should be able to raise the CQ, right?

Hi audioslave,

You have to remember that it's not only one more frame, but it's also 67,584 more pixels per frame :!:
(704x576 - 704x480 = 67,584) and that's a HUGE difference.
So go for 528x576 :wink:

-kwag

Hi kwag,

Thanks! I knew I missed something... Of course, you're right - as always 8) ! I guess I'll have to settle for 528x576 if I'm gonna be able to fit this sucker onto one disc :wink: .
BTW Do you have any idea on my problem with ToK and the new script (read previous post)? I'd be thankful if you could help me out on that one.

EDIT: Do you think I could lower the max bitrate to 2000 on a 528x576 resolution encode? Think I read somewhere that you've tried that?

I wouldn't do the conversion. That usually ends up in problems :!:Yes you can try that. With the new motion adaptive script, it should make the high action scenes blured, and the encoder will see a softer picture and the result is less blocks. Do a file prediction with ToK and set your MAX bitrate to 2,000. Once you get your CQ from ToK, encode an small action scene of Red Planet with that CQ, and see how it looks :)

-kwag

@kwag

Okay, I'll keep away from the conversion. I'm running ToK with the lowered max. bitrate (2000) as I'm typing this.

Predicting...... DONE!

Looks great to me! And guess what - the CQ got up to 63,618 :D . Thanks man! You're really are the greatest!

Remember that the CQ curve changes, because you lowered the MAX bit rate. Now encode some action scenes, and see if they look good to you. If they do, you're all set :D

-kwag

So, I've tested a few action scenes and I really don't see any differnce between 2,000 or 2,500 for max. bitrate. I'll give it a try with max. bitrate at 2,000 :wink: ! I'll start the encode right away then I'm going to bed. It's 01:40 a.m. here in Sweden now (yawn)... Good night and thank you for all your help!

-audioslave