hi rds,

thats what I wanted. Ta do them manually. Thanks.

But, what I really want to do is crop the traditional way. You know..

I want to do this all in MEn, not in any .AVS scrips or vdub either. I'm trying
to stear towards doing things under MEn instead

Now, given all that, lets try a given scenario, shall we

Say my source is 720 x 480. It's a 2:35.1 AR. I wanna:

* add 8 pixels to my left and 8 pixels to my right.


Then, I also want to crop (not in auto mode) my OWN assumed crop, of:

* 59 pixels off top, and
* 62 pixels off the bottom

This will give me a final resoltuion of 720 x 359.

When I encode this, I'd like to encode w/ new black PURE bars. To do this,
(assuming I'm not making Anamorphic encodes) inside vdub, I set my
resolution to T: 720, and my B: 359 and THEN, I tab down and set the remaining
res to a final 720 x 480. This may be clumsy, but has worked for me in many
of my projects.

However, if I was doing an Anamorphic encode, than I would not need to
black bar this, but, I WOULD need to resize this 720 x 359, into 720 x 480
I think I have to use the Scale param, but I'm not sure on how to use that
just yet

My next question, given the above cropping method, I"d like to have PURE
black, boarders, just like TMPG does. When you encode this, TMPG does
a perfect PURE black bars at top and bottom. So far, when I encode black
bars (top and bottom) under MEn, they are gray or washed out black. Very
awlful looking. I'm wondering if MEn is lacking this feature, or am I missing
a step in order for MEn to ducpilicate this perfect PURE black bars like TMPG

Thanks for any assistance,
-vhelp

@vmesquita

Nice work on the compiling

But the man page needs to be converted in some other way.

Probably I tried the same program as you before because I got the same result: all parameters converted to s

About everything else, I'll give feedback as time permits

Bilu

I just burned my first DVD-R incl. 2 mencoder encoded m2v streams.
The Streams where encoded during last week.

All m2v's I did (just in case) refixed using Restream and reseted the timestamps. Cause of some PTS... Errors during encoding.

Everything plays very fine! It looks awesome (all where TV captures at 704x576!). The second track got for 3 seconds a Bitrate blast up to 14000!! told by Bitrateviewer but it played fine So maybe that Bitrateviewer really gots a bug.

Well Im happy with mencoder and for shure its speed! And better Quantization/Bitrate behaviour compared to CCE and TmpgEnc.

Hi Inc.,
That's what worries me most: bitrate peaks.
I haven't seen them much, but I tried LOTR II right in the begining there is a scene with lot's of fire during more than 30s and I do have bitrate peaks above my vrc_maxrate of 6000 and some PTS SCR messages.
Though it didn't go above 9800...
Most my movies are medium action movies so I really cant test this.
I notice some blocks with still or very dark scenes.
Let's keep testing it.
Can you post your setting/arguments?
Thanks.

__________________
Rui

@vmesquita

On this version fractional fps like 29.97 or 23.976 don't work
Even when not specifying any -fps or -ofps parameter

Maybe something to do with this?
http://www.mplayerhq.hu/MPlayer/rele...-beta/contrib/

Or is it a bug from the current CVS build?

Anyway, tried the interlaced parameters to be able to compile an unchanged telecined NTSC stream and it didn't work - accepted the parameters, didn't provide the results

Also filmdint doesn't work as good as I expected - it's very, very bad on low-motion scenes. Looks like encoding with swapped field order.

Haven't tried any of the quality parameters, maybe they're the ones that will make this compile worth the trouble you had

At least we already know we can do direct CVS compiles whenever we want


Cheers,
Bilu

Hi all,
any comments to my tests with vmesquita's mencoder compilation? (previous page, in this thread). I'm worried about errors I'm getting... already burned a test to see in my standalone. I'll post how it looks.

@rds & inc,
I still didn't get any overbitrated (according to bitrate viewer) sample. The truth is I just tested with one film, choosing several slices. But I think I chose more bitrate demanding, and max bitrate I got was 7780, below my vrc_maxrate value of 8000. And in a particular scene the encoder raised Q to 5.47 in order to keep this maxrate (average Q of 2.17).
You could post your command-lines, and films and scenes/frames this happens (Rui, it happened to you in LOTR II at the begining, isn't it?).

hey guys..a visual problem with ffvfw (also MEmcoder, too I think)...

I like ffvfw, its motion estimation is wonderful!!!, however the blocks that it creates at low bitrate scenes is really a major drawback for me...(so far, no VBV issues, no bitrate peak issues)

Here is a first pass (MPEG KVCD notch matrix)...all the rest defualt settings...




These horrible block are diven me crazy...I have tried many different settings, but they will not go away...I tried min and max q at both 2, marcoblocks at both min and max of 2...Are you guys getting these blocks with Memcoder as well???

oh, I wish that we could create a post just for testing results...Everyone could post screenshots of recent tests...

That's strange since both qmin and qmax are set to 2

Have you tried any of this?

- Macroblock decision mode: rate distortion
- Allways try no motion
- Trellis quantization
- RD optimization for CBP
- Darkness masking

Give us your feedback.

Bilu

Still don't know what is it related to. I was thinking about the RFF fields of a telecined stream but it also happens with progressive I think

With telecine it goes like this:

1 duplicate frame(s)!
Unknown block type, possibly non-MPEG stream!

Just stupidity, they recommend doing 1-pass CBR only

Probably means that the VBV buffer specified in vrc_buf_size=1835 isn't full yet, which is pretty normal at the beginning.

Bilu

That pic indeed looks horrible. I'd just use a strong blockbuster line. However filesize will be higher, but I'm sure you'll like the quality.

play with this...

__________________
j3llyG0053

AARGH!!!

http://www1.mplayerhq.hu/pipermail/m...er/040240.html

So maybe like everything else (Avisynth ? ) the output should be done to AVI and then remuxed.

Bilu

Bilu

poerschr, you said you used ffvfw... are you doing any preprocessing (at the begining of tests it was advised to add noise with internal filters, through ffdshow)?
But I guess is the same as Jellygoose is advising you, and maybe faster, and easier to tweak it making use of avisynth...
About mencoder, I'm now focused mainly in high action scenes: to see how mencoder manages high bitrates without going over maxrate, to see how mencoder adjusts Q level considering scene complexity and bitrate available,... But I'll also take a look at slow dark scenes to look for those blocks.
Anyway, I'm aiming KDVD, that means bitrates between 300 and 5000 and average around 2000-3000, and I don't think I'll have any problem in slow dark scenes. AFAIK tmpgenc is still better for low bitrates... if your tests don't say the opposite, of course.

I don't know if I understood. Do you think that those "unknown block type" errors are related to the use of -of mpeg?.
Does it mean that -of mpeg is buggy, or that we're not using it in the proper way?.
What should we use then, -of avi (don't know it this exists, just an example), then demux (with VirtualDub for instance), take the stream (will it be an elementary mpeg2 stream?) and remux with our audio?.
And with avisynth, what do you refer to?, to the fact we have to use makeAVIS to feed mencoder, instead of avs script?.
We could also get in contact with mencoder developers...

That's exctaly what I tried to explain.
You just open FitCD and Moviestacker to get the proper figures from the resizing panel.
But you never use the avisynth script provided by those tools
Use the arguments that I placed on my post and make sure you select the VOBfile for input
instead of a fake avi or avisynth script.
The problem is I don't know how to tell mencoder to encode several VOBfiles for input...

So I took your figures into FitCD and got the following:
Crop=664x352
Resize=688x272
Now, I don't even care about saving any script with FitCD or MStacker.
Use the following arguments in mencoder in the -lavcopts argument:
:crop=664,352:size=688,272:expand=704,480:
Don't forget to change your input file to a VOBfile instead of the fake avi or the avisynth script.
Hope it helps.
Cheers

__________________
Rui

-of mpeg IS buggy. I mentioned Avisynth because once again (as we did with Avisynth) we're muxing from AVI (VFW) instead of MPEG sources.

Stay tuned for the next post

Bilu

GREAT NEWS: Interlaced / Telecined sources now work, both PAL and NTSC

Simple script for NTSC, not optimized for quality, 11 fps on a PIII-500.
Replace directories with your own.

No need for Avisynth deinterlace or IVTC to encode.
Progressive streams also work with these settings.
Most error messages disappeared

For PAL just replace 29.97 and 30 with 25.
30 was a workaround for NTSC to the vmesquita CVS build.
Needs both vmesquita CVS build and last Mplayer build.

Hope you get as happy with this as I did

Bilu

You see, bilu, I was waiting your post like a nice boy...
I don't know how you manage to get 11 fps (well, yes, maybe due to not using mbd, trell, cbp, vqsquish, and so)
Do we really need all these -fps and -ofps for PAL?. I encode without them and didn't get any problem...
I see you aren't already using -of mpeg, is it faster?. And I also see that default is output in .avi
...and this is the way to make use of mplayer to extract the video stream, isn't it?. I'm at work now, I can't test: is it fast as bbdemux?. And what about the stream, is it compatible (I guess yes since you used mpeg2video vcodec)
... I forgot MSDOS a little, is this just to rename the dump file to .m2v?.

willing to get home and test it, while... some feedback please.

Sorry, not needed for PAL, just for NTSC since the current CVS build doesn't support fractional (29.97) framerates. And with -noskip the duplicate frame messages are gone
Much more compatible with Mencoder developments. Interlaced encoding does work here. -of avi is default.
About the same speed IMHO.
Yep.


Bilu

Just tested with the "official" Mencoder port by removing the ilme parameter from the command line.

Doesn't work. It's really needed for interlaced and telecined encodes.

Bilu