We definitely don't have the same eyes and I understand why I can't love this encodere.

FYI, Marty's anti-rad jacket on the second snap is supposed to be yellow. A plain, uniform, bright, yellow tint. Not this undefined grainy green-yellowish things you can see on mencoder output :puke:

Same (but less visible) for the color of the terrorists' pickup on third snaphot.

I'm currently DL the sample... stay tuned !

Edit: Okay, let's go for a quick comment !

Grainy, grainy, grainy. :puke: :puke: :puke:
Look at Marty's face when he closes the DeLorean's door (sec 6). Look at his jacket when he is driving and his arm just after (sec 16 to 18 ), look at the terrorist faces also.
In one words : ANYTHING is like if a sand strom passed in front of the camera while they were shooting.

Note: I only speak about the bad things. "forgetting" the good ones (for instance there is absolutly no mosquitoes despite the resolution and target size and only few pixelated part). But personally I can't really stand watching a whole movie like this. The only idea that comes in mind watching that is "this video need a GOOD denoiser" :!:

Phil,

I think you haven't seen the original VOBs :!:
They are worse :!:
I'll post a screenshot, so you can compare, and then maybe you'll see the difference ;)

-kwag

Here's your answer Phil ;)

Original Anamorphic VOB:
Edit: Talk about a BAD quality DVD :?

http://www.digitalfaq.com/archives/i...2004/06/12.png

4:3 Letterboxed KDVD:

http://www.digitalfaq.com/archives/i.../2004/06/9.png

Edit: I think mencoder filters are doing a pretty damn good job :)

Second comparison:

VOB:
http://www.digitalfaq.com/archives/i...2004/06/13.png

KDVD:
http://www.digitalfaq.com/archives/i...2004/06/11.png

-kwag

Whoaow. You definitely need the THX-labelized PAL release then :-).
This source is AWFULL :-D
Okay, mencoder did "what it could" on that, I have to admit.

Just to know : how many underflows error message for the whole movie ?
And time to encode ?

Yes it stinks :lol: None. Zero. Nada :D

The next code was not my final mux. That's the mux I did with an MP2 audio I had already encoded at 44.1Khz. The sample you download has 44.1 audio,
My final mux was with AC3 audio. :)



-kwag

@kwag
Well, I don't know how you do it but I'm still getting underflows! :cry:
I'm using the setting you posted a few pages earlier...

BTW Where can I download the MEncoder version you're using?

Yeah and this points out one of the weakness of mencoder I already mentioned during my very first attempt with it : the internal filters of mencoder can't handle quality of sources in the same range we use to do with avisynth.

There is only ONE denoiser implemented in mencoder and it's easy to understand that you can't fix all situation with so few. It's like if avisynth script were limited to Deen or Convolution3D. Mencoder misses also a good temporal only filter.

I meant the VOB stinks 8O
The encoded sample looks MUCH better :!: Sure, but it's not bad at all :)

-kwag

Yes Kwag, the images you post are impressive.
They're from KDVD, aren't they?. I see you use maxrate=5000, what's your maximum bitrate for this KDVD?.

I ask because I tested your command-line, with a DVD source and for SKVCD output, and yes, the filter chain really clean nice the film, but with a maxrate=2500 I get peak of 4014 in BitrateViewer :( .

I posted here, in this same thread some questions I have about your mencoder parameters, but I'm afraid you missed that post.
What's going wrong?, is it the source?, is it that I encode at 704x576 (used noise=2th)?.
How, do you think, can I control those too high bitrate peaks?.
Thanx for your help.

DVD source (VOB) -> KDVD No.8,000Kbps. You can see that in Bitrate viewer. 8O SKVCD at 704x576 :?:
Didn't you just said you encoded for SKVCD output :?: I have no Idea. I think it's a PAL issue, because I don't have any problems on NTSC.

-kwag

I had understood ;-)

But a correct avisynth script would have done this better. That's what I wanted to say.

Note : I find your script lost a LOT of details in the bald skrull of the guy on the left (don't remember his name) on the third snap. Marty's face is correctly denoised but this is done with too much sacrifice.

Fortunally ! But what can you do with this source that bumps this unique filter out of its limits ? Nothing.
But with avisynth...

Remember, these are still test parameters.
I'm not done with the filter chain yet ;)

-kwag

I know, but if everyone just say :jawdrop: in front of your snapshots you will start to think that they are right :-)

Well, any volunteers to try it with AviSynth :?:
I'm pretty sure the difference will be minimal, and the encoding time to achieve at least the same, will be much longer.
It's a fact that mencoder's internal filters are much faster than AviSynth. So for me, I'm very pleased with those results, just as they are :!:
Can they be improved :?: Of course :!:
Is it worth it :?: Of course :!:
But there will be a price to pay, which usually turns out to be "time".

-kwag

Don't make me laught :rotf:
You admitted yourself that the new line dropped the speed by two ! This added to the 2pass encoding I'm sure you have now an encoding time longer than tmpgenc !
I already have this with a coding line issued from packshot and it doesn't use sab :!:

Encoding time under mencoder : 6h per pass
Encoding time under tmpgenc : 10h :!:

With all your filters you gave a long kiss goodbye to the speed benifit and you know it.

You can do the test on BTFF by yourself. Reinstalling tmpgenc does not take so long ;-)

Is the MA avisynth script and mencoder really that slow?
Is the quality better than with tmpgenc?
If it's only a bit slower you could just use that because waiting 12 hours for an encode or 14 isn't that big a deal :P

Speed is a relative notion, as you said just after.

We are not talking about mencoder vs tmgenc. We are talking about mencoder internal filters vs avisynth ones. If I put on the side the biggest problem (for me) of mencoder - that is the birate peaks and the buffer underflow - and focus only on the filter problem, I'm not againt using mencoder here BUT with an avisynth script as input.
But in this case, the question to know if tmpgenc will be faster or not is not even needed to be asked :-P

Waiting 14h insteed of 12 to obtain the result you see in the snapshot above + not be sure to have a stream readable on your standalone (Kwag said he didn't have any underflow on this but I put that on the luck as this is clearly an issue that nobody control completly)... THEN this is a big deal ;-)

OK, if SKVCD just refers to 480x576 (PAL), I don't know how to call it.
What I mean is I'm encoding mpeg2, 25 fps, 704x576 res, with maxrate=2500 and avg=1230.
:( :cry:
So, just nothing to do about it, isn't it?.
It's sad not having to do nothing to sort it out.
Even more, when all my previous tests (3 DVD sources, 2 AVI sources and a home made film: my older son) went OK without a problem. And suddenly, in my last 3 DVD sources, this :!: .
:(
I hope you find a way for PAL users...

I asked if the quality is better because tmpgenc is faster and it would be a waste of time encoding it in mencoder then wouldn't it
unless the quality is better.

I definitely sure that with the "old" method (avisynth + tmpgenc) you will have a really better result on sources like this version of back to the future AND you will have a quicker result.

For the speed, my experiences have already proved that. For the quality, only a direct comparison can give the answer.