I gotta problem here.

Just viewed my first full encode in bitrate viewer. Q-Curve is a straight line, average is exactly 2.0 and that's great. But... :?

I got Bitrate Peaks of 14.363kb/sec :!: :!:
I'm pretty sure that my DVD Player won't play these scenes am I right? How can I make the encoder to stay under 8000kb/sec at the peaks.
But damn the movie looks great... :mrgreen:

EDIT: In fact I see now the bitrate also drops under 300kb/sec in some scenes.

:lol: We have a new record there :-)

I think you're right.

The min/max bitrate setting is one of the issue Kwag asked to Milan, but didn't have receive an answer yet.

We need to write a "Bitrate Clipper/Trimmer" utility :mrgreen:

-kwag

I'm actually trying to use the Blur-Part of the MA script for this.
(thanks inc!) :wink:

Hello: Excuse me, why cbr. I don't find out nothing in the other thread. (I think I'm a Poor english team member too)

Because CBR with with codec is actually VBR. If you have a look at the screenshots from bitrate viewer in the other thread you can see that the bitrate varies alot, it isn't constant 8)
With CBR, we are able to adjust the Buffer Size and the final size easier and the quality is higher due to higher bitrate variation.

ehr,Guys?
My Q curve still looks like a sawblade...
Could someone help me with it?
My settings match Kwag's at the begining of this sticky.
I'm running ffvfw from 2004.
Thanks

What means sawblade? I clear interval of zig-zag or just arbitary up'n downs?

(pic maybe?)

More "moutain landscape" than "regular zigzag" nor "heartbeat".

You see the yellow line il all your posts ? The green one is like that !

Phil, did you try once to change EVERY quantizer to the same value like

min: I =2 , P=2, B=2
max: I= 2, P=2, B=2

:?:

What do you think ? :-D

I even changed the "macroblock" part (the one that is greyed by default).

By the way it's not very a problem because when I set min=max=2 for instance, the value is always UNDER 2 and never OVER. So the minimal quality I ask is never bypassed.
But as I told, this behaviour mask a serious problem in the codec that we have to solve if we want to continue to share our experience on this.
What is the value of comparisons between Kwag results and mine if the behaviour of the codec is completly different on its PC and mine ?

Beacause I repeat : I NEVER HAD a constant Q curve like you have.

Note : ASAP I will DL the common sources proposed in an other thread to see if I can reach the same results a yours or Kwag's on the same video.

I totally agree cause if for example the curve gets down on dark or plain scenes ..... thats the reason why blocks do come out on surfaces.
Do a try on a movie with underwaterscenes and watch on these scenes the bitrateviewer curve ... I think it will fall down.
Watch my statements in there according to that workout sample "emotion.mpg", but thats only IMHO. :wink:

I don't want to use interlaced also. That's why I didn't DL this source as soon as I saw that, even before your first post about that :-)

I've never touched this. I use default value and mine Q-Curve is flat. Try set it back to dafault, or reinstal ffvfw (it's only sugestion, i don't know is this will work).

I didn't mentioned but I have that on my 2 PCs and the second one didn't have any codec installed before.

BTW, I dropped for a while this codec, results are too poor comparing to the efforts and I don't have the time for the moment.

...sad to here that, your help is very apreciated :(

I've a problem. Why can't I set in the field "Encoders" only Xvid & uncompressed?

How can I set it to MPG-2?

Would love to show you guys but I don't know how to post a pic... :oops:
I guess I need some web space but unfortunately I don't know where to get some. I mean free...
I must say that I already uninstalled both ffvfw and ffdshow and reinstalled both...
Same results.
Don't know what to do. I thought it would have somehow something to do with PAL sources.
But you don't experience this problem, do you Inc?
Cheers

Now I've installed the right ffvfw but I can't save a video. VDUB is in progress but the results are around 20kb 8O and not playable what i've done wrong?

Hi rds_correia,
it has definitely nothing to do with PAL as we both haven't had this problem.
Have you tried different sources :?:
Maybe your registry entrys got screwed up, but i recommended this also to Phil and he said that this appeared on his clean second pc.
Or maybe it's the bitrate viewer (as i don't trust it always) :?:

Hi EM, you have to set up an output file (not the avi). See Kwag's screenshots. After VDubMod :wink: has completed you demux your file with TMPGEnc.
Hope this helps. If not, please post what your doing step-by-step.

I have done all in the screens of kwag but he doesn't describe the output option. How I have to set it?

You have to set it in the codec/compression settings(Output).

I'll give it a try.

YES, thx, It runs, now! :D

I'm sorry to hear that. believe me you, I understabd trials w/ ffvfw :roll:

About that sawtooth/zigzag Q you are having problems with. I was always
under the impression that you want to have the Q be as close to the sources
bitrate path as possible 8O I must be pretty domb then. Because at the
moment, I can't seem to stop my Q from being straight (flat-line) looking.
I mean, it's not curved or zigzag (like I assumed its suppose to be) 8O.

I'll post a pic shortly of what I'm on about K ?

As to the emotion.mpg clip. It's a pretty high-quality source file.
1920 x 1088 resolution. Its pretty blocky in various areas, no thanks to the
limited bandwitdh for such a large resolution. But, you won't notice it when
you encode it anyways :wink: It's all gone!! Must be an dvd2avi glitch when
you preview the emotion.mpg clip.

By the way, this clip is Film based. That is, it's Telecined. I used my IVTC
method on this, and it came out great. So, don't worry about Interlace.
Just use your best IVTC method to week it out and get a great looking
encode from this short, test clip, though 38mb in size. I can't remember
how long it took, but I think it took like 1hour to D/L on my 56k dial-up..
not to get that mixed w/ Dialhot :P

But, I do have a quation on this clip though. Was it Fullscreen, or was it a
widescreen. I really couldn't tell because it's my first time dealing w/ such
a large resolution source file. However, I think I prefered my tipicle TMPG
encode quality better than my ffvfw encode. I'm still in the greay
area w/ encoding w/ ffvfw 8O. I think that kwag's ffvfw encode came out
much better than my ffvfw attempts. But, I suspect that it may be a "version"
difference. My version I'm using is Sept 27 2003 13:29:54 and I did
notice some items not present when comparing kwag's screen shot over on
the sticky, page 1.

-vhelp

Remeber Dialhot's problems about the Q curve :?:
Some of you may remember that I had that problem also, though I always found the codec was providing better quality than tmpg.
Ok, now that most of you dropped the codec and since I was in trouble with something else and I had to reinstall XP (I was promissing this for months...) :arrow: Guess what :!: Now I have a PERFECT Q line and I will do some testing just to check if the bitrate peaks above 9800Kb.
Cheers

That confirm that there is a big issue with this codec and untill we find it, it does not have any means to share the results of the tests.

Agree with you Phil, since now I ONLY leveled with anyone else that was doing ok with the Q curve.
As I said I'll run my own bitrate peaks tests to see if it's ok to use it for KDVD because if it's higher than 9800kb...
Just to share with you that I should have other problems that were preventing me to experience what other posted here such as Kwag or Inc.
Cheers

ok. Let me see if I get this straight..

A wavy Q line is bad, but a flat-line Q is GOOD ??

If flat-line "is GOOD", then just where should this line be ??

* below bitrate values ??
* above bitrate values ??
* dead center of bitrate values ??

Assuming your given encode went like this, with following bitrates:
* 900 - - 7800, and Average bitrate @ 3200 (our dead center)

For what it's worth, my Q's are always flat-line, using DVD rip as my source!
And, I always thought that this type of Q was bad, and that the Q should
always be wavy and matching that of the bitrate wave.. as if riding the
wave :wink: 8O

I don't know if I understand correctly this "Q" thing, but a little help would
be appreciated :P
Thanks,
-vhelp

No it's not THAT the problem.
The problem here is that everyone is trying to use ffvfw and give results to all. BUT... I'm damn sure that there is "something'" external to the codec that modify deeply the results. And as long as we don't find it, there is no way to compare test done by everyone !

When some have flat curve and others don't, you are comparing citrus and orange. For sure they won't have the same taste :-)

I agree with you phil! Did some tests on 2 pc's With exactly the same codec configuration both on WinXP. Same ffvfw builds, same source (even from the same network drive en exactly the same ffvfw config. With this the sample on pc1 was 21.628KB, on pc 2 18.544KB! Avg. Bitrate of the pc1 file is about 200 higher than pc2 file.... with same q value.

When I encode the sample again and again on the same pc, the size and bitrate stay (approximatly) the same.

I really think there is an external factor influencing this codec, also becease if I encode this sample with tmpgenc on both pc's, the filesize is (approximatly) the same.

Tinus

Thank you :!: You understand now why I decided to let this codec on the side for a while.

Still no news about Milan ?

FFVFW and Mencoder are all based on FFMPEG's code, which still has its problems :roll:

That's why I started this thread about the FFMPEG development status, I think we should still focus our attention here:

FFMPEG status on MPEG-2 encoding
http://www.kvcd.net/forum/viewtopic.php?t=8835


Bilu

Hi Bilu,

I agree with that, but FFMPEG has some serious issues on the stream, which render the muxing useless.
That apparently has been fixed in ffvfw, because I can mux every ffmpeg produced stream, without any underruns or overrruns.
Not so with ffmpeg :roll:

-kwag

Well, you got me interested on how much FFMPEG bugs are already corrected in FFVFW... :wink:

A good place to look:
http://cvs.sourceforge.net/viewcvs.py/ffdshow/ffvfw/

Bilu

Yes, I've been all over the CVS repository, and I bring up a question: The most recent modifications to the CVS files, were ~4 months ago. So who did the subsequent builds we're using :?:
Where are the sources for ffvfw that we got here: http://www.ligh.de/software/mirrors.phtml :?: :?: :?:

-kwag

Hey Kwag,
I could be mistaken but i think it was Dano that told us that the latest builds available were produced by a guy by the nick of Athos.
Rings a bell :?:
Maybe he moved on with Milan's work since he hasn't been around for months.
But then maybe i am only mistaken.
Cheers

Have a look here for Athos builds:

http://forum.doom9.org/showthread.php?s=&threadid=42710

Bilu

how i can save a m2v, m1v?
 

I ¡m trying the ffvfw in virtualdubmod 1.4.5.1 and Virtualdub-mpeg2, i opne the avs /avi file but the final file it's an avi!!!
How i can save with vdub-mod-mpeg2 in m2v or m1v?
Thanks