Hay kvcd,

thanks for the tool and the work you poored into it :!:

Can I asked of something though, ..cause I'm confused slightely.

Are we talking about mencoder encodes, or ffvfw encodes or both ??
I ask, because I have my encodes stating 224 (bviewer shows 112) and I
thought that we all fixed it in a prior thread :!:

Also, I noticed that this FORUM is captioned as ffmpeg/ffvfw/ffdshow
I was wondering, if mencoder should be "strong" on the end their ??
..or what do you think.. :roll: since we are all also testing mencoder
out and stuff.

* Is it worth to add a MEncoder FORUM, or
* should we string MEncoder at the end of ffmpeg/ffvfw/ffshow/MEncoder

Or, is it still uncertain about MEncoder's abilities, and as such, needs more
testing ??

Just some things to think about :roll:

Cheers all,
-vhelp

Hi marcellus,

Try NetFirms:
http://www.netfirms.com/hostingbasic...4fa8b84e2a1812

-kwag

Any :!:
The tool will patch any valid .m2v Video Elementary Stream. But remember that the current version will only patch for DVD compliancy ( 112 in BV, 224KB actual size ) They are all based on ffmpeg, so I guess this is a right place :) Sure. Doing it right now :D

-kwag

regarding this FORUM 's change.. ..
Excellent :!: :!: .. I see you too quick to draw :hihi:

Hay, I just finished D/L'ing your lates tool. I found an old .m2v file that I
encoded w/ MEncoder and bviewer displays it as 208. So, your app will be
tested now :!:

I'll let you know the results. (after I back it up, for future VBV testing)

OT: I'm still working on my GUI, and hope that I can have something out
by TGIF - - so please keep your fingers crossed, but no promises :hihi:
-vhelp

update..

I just finished testing my test clip. Under bviewer, it is still showing vbv of 208 !!

So, maybe I missunderstood.. that it will still show the old vbv number ??
but will work in DVD apps that require compliance ??

-vhelp

You did open a .m2v, right :?:
Because I tried it on about 20 different .m2v files, and all patched properly :!:
But I tested .m2vs created with TMPEG and ffvfw. I'll try a quick encode with Mencoder now.
BV should display 112 after the patch.
If you got another value, then it means MEncoder is TOTALLY screwed up in the structure it creates, because I'm following the MPEG-2 protocol specifications with exact offset target for the place to modify the VBV value.

-kwag

Yes kvcd,

I use an .m2v file. My source is from an MEncoder encode. So, I think you
are right (in your hunch) that mencoder could be screwed up in it's MPEG-2
specs and things :roll:
And, that probably explains why dvd2avi will not open any mencoder encodes :!:

Pfew!! I'm glad its not your app then :lol:
Let us know what your results are anyways, w/ your test encode and mencoder :!:
-vhelp

Hi vhelp,

MEncoder is screwed up, but not in structure :lol:
Rename your .m2v produced by MEncoder to .mpg, demux it with TMPEG, and now run VBVPatcher against your new .m2v :cool:
The problem is that the header that MEncoder creates, is not an elementary video stream.
Once you rename the encoded .m2v to .mpg and demux it, the demuxed file does have the correct header, and then VBVPatcher works :D

-kwag

regarding your recommendation for deMUX'ing ...

is it because mencoder is still adding in an audio (though blank) stream to
it, even if you tell it not to ??

Yes, its very strange indeed.

Thanks, I'll give your suggestion a try w/ my test clip we just talked about.
-vhelp

BINGO !!

...it worked. I wonder why mencoder is adding in padded_stream to
the mpeg file :roll:

Hmm.. I wonder is there.. hmm... I'll be back on a thought that came to me :idea:

For those that weren't following, below are the steps to patch your vbv 's
(those encode done w/ MEncoder only)

* open TMPG
* File/MPEG tools
* select the TAB: de-multiplex
* select browse, and choose Select ALL FILES *.*
* find your .m2v file (if you named it .m2v as I do) and select it
* then, double-click the [x] video_stream 0x00 and give new name.
....I put an "_" (ie, 5_enc.m2v now becomes _5_enc.m2v) and select save.
* then, your finished w/ TMPG.
.
.
* now, open kvcd's VBVPatcher v0.1 and open your revised Source .m2v file.
* then, click patch it!! and you're done.

To test your VBV result, just open inside bviewer and observe the VBV :!:

Hope I got it all down right for you all :lol:
Cheers,
-vhelp

:!: But ONLY For MEncoder :!:
MPEGs created with ffvfw or other true elementary streams, don't need to be demuxed. Just run VBVPatcher and "sock-it-to-it" ;)

-kwag

I am not sure if I missed something, but mencoder can produce the right VBV buffer size using a command-line paramenter, so there's no need for patching VBV buffer later... No?

I missed it as well. :?

Didn't this work? I didn't test it yet, will do it now.

http://www.kvcd.net/forum/viewtopic.php?p=64002#64002


Bilu

Thanks a lot Kwag!
I will sign-up and transfer my files ASAP.

marcellus

Hya all,
VM your absolutly right.
Mencoder is not the problem :arrow: ffvfw is the real problem.
But then in ffvfw we can choose "raw frames" for output and it produces correct M2Vs inside the standard.
With mencoder I haven't found any argument that added to the "-noaudio" produces M2V.
So even if I name my encoded video YYY.M2V I will still be producing an MPG file.
That's what was bugging vhelp.
And that's why I downloaded bbtool19 that comes with bbdmux which will demux our MPG :arrow: M2V.
I could have used tmpg to demux the file right from the begining of testing.
But I just wanted to make sure that if one day we could come up with a GUI for mencoder we would have all the needed tools without having to have tmpg installed.
C ya

Easy buddy.
I can assure you it is working.
We just have to put some things down in the paper and probably come up with a sticky for Kwag to post.
More, I advise everybody to check the thread bilu has just posted if you are having difficult times with vbv under mencoder.
Cheers everybody

I agree with Vmesquita (and I got no probs with the right VBV Buffer sizes afterwards).

According to the TmpgEnc demux workout ....

You easely can add to the commandline a "demux&safe the elementary m2v & delete the first output mpg" at the end so everything goes automatically! Thats also what I like on that commandline workouts.

By this after the process you get the right m2v elementary stream on your hd ... but bbdemux has to be installed to do that, so TmpgEnc is not needed.

@Karl
Works like charm 8) Of course for first header as it should be for now. While I have not my own standalone, I can't test this, but I know that this file is still incompliant "mutant" file :lol: I'm trying to find pattern of the header. If you already know this, tell me, so I won't be inventing wheel for second time ;)

:arrow: NOTE
VBV patcher probably won't work with TMPG video files, while TMPG adds header of its own "encoded by TMPGEnc (ver. xxxxxx)". Maybe this header is no problem, and for sure we don't need to use this tool for TMPEG files, but keep that in mind.


EDIT: :( I also want to be a moderator :(

Hay guys..


No NO no NO no. don't mis-confuse me. I first thought that it was not
settled w/ mencoder producing VBV buffers w/in DVD spec (ie, 224/112)
So, that is why I jumped in here on this, w/ respect to mencoder and I
was the one that provided an example file that I did in my previous days
w/ mencoder (still water behind my ears) and gave kvcd an example of a
.m2v file that bviewer was showing as 208 :!: I was using this as an example
to work out the kinks in kvcd's new tool.
.
.
As for myself, I have ben making vbv of 224 (112 in bviewer) since I can
remember (pobably early this week) and have no problems w/ making it,
I think :roll:
.
.
There fore, I'm sorry if I bugged anyone on this issue. Like I said earlier,
I had thought that the VBV in mencoder was settled in another thread. I'm
not sure I have it all down (in my head) as to the exact vbv setting in my
GUI's param string setup, but as long as mine works as such, I'm not going
to ruffle any feathers :lol:

I will re-visit that thread that bilu posted (now page 6) just to be sure I got
it straight, less I want another ass-kicking by rds :wink:

@ rds,

yes, I agree w/ you on this. I'd like to incorporate such features, but I did
not catch on w/ this tool you mention (I must be slipping) regarding bbtool19
and it's demux tool. Where can I get that demux tool, so I can quickly test
it out in my gui - please :?:

Yes, I definately want to rule out TMPG as another exhaustive step in the
process :!: :!:

-vhelp

Hi vhelp :D
No more ass kicking I promisse :wink:
Get bbtool19 here http://www.doom9.org/Soft21/Vobtools/bbtool19.zip
C ya

Sorry rds,

doom9 gave me a "do not LEECH" warning message, and won't let met D/L :!:

:screwy: I don't get it though :confused:

:hihi:
-vhelp

Just to see if I got things right:

You're saying that Mencoder is creating an MPG header instead of an M2V header even when using the -nosound parameter.
Headers are not like M2V and so you can't use it.

My noob question:

What can't you do with the stream with the header produced by Mencoder?

From the man page:
From the mencoder -of help output:

Bilu

It is not m2v file with mpeg header, but MPEG file =m2v video + audio (AFAIK empty or fake, or even without audio; probably last type). You have to demux this type of stream.

Why? What process needs it demuxed? Can't you just select video from a stream for that process?

Sorry, I'm in early stages :oops:

Bilu

After encoding with MEncoder you get MPEG file (m2v+no audio), but it is still mpeg file. For mux (bbmux) with your prefered audio (zB. MP2 from BeSweet), you need pure m2v video stream. Ok?

Bilu[/quote]

Hi bilu,
I believe system stream format is different than elementary stream format.
We all want it to output elementary instead of system.
Notice it's called mpeg instead of m2v.
Hopefully I'm posting it accuratly.
Cheers

Duuude,
You're only noob if I'm a super noob :lol:
But still you can't mux an already muxed stream.
An mpeg stream has already been muxed opposed to an m2v.
We need an m2v to mux the audio in the end since we're not doing audio with mencoder.
That's why.
Cheers

@ Hydeus,

That was my thinking and assumption too, when talking w/ kvcd previously,
when we were debugging the patcher tool. That it was not an "single" stream
but rather a mixed (but kaka) stream, and that it might be an faulted audio
stream that got left behind (what's left of the code snip) in mencoder's final
U/L to us all. Maybe this developer (a nice guy) probably didn't finish w/
guttin out the bad code or something :roll:

The reason I concluded w/ this analigy was because we are able to de-MUX :confused:
the source :!:
That, to me, means that TWO streams are at play here. And, when you bring
in the .m2v (or whatever you guys/gals calls it) in TMPG, it leaves a blank
[ ] padd_stream in our mists :roll:

-vhelp

Sorry,
I forgot doom9 doesn't accept it...
Just use www.doom9.org. Push the download button on the left pan.
Scroll down to the vob tools.
There it is in the 1st place or else hit "show all vob tools" if you still can't see it.
Cheers

Hi vhelp,
I don't know if I understood you right but you must remember that ffvfw was doing the same thing when we were using output as MPEG1 instead of Raw file.
So maybe it's a libavcodec thing and not just a slack of code that they didn't finish.
I wish mencoder would have raw file mode so we could forget about demuxing it...
Cheers

Is it everytime 0xe0 ?
Or would this be better?
And then rename stream.dump to movie.m2v, of course ;)

Note: this would mean using mplayer -dumpvideo using the mencoder result stream as source.

Bilu

Arg..

I give up. doom9 just won't let me in. But, thanks anyways.. I'll research
an alternative method - sorry pal.

-vhelp

Thx Rui. Exactly my point 8)

Don't know bilu, but all clips I tested yet were ok with 0xe0.
I think I tried that and it didn't work. Something about not being available for mpeg2 if I recall it.
But I could be wrong.
Be a sports and try it it too.
Please tell us how it went. That would help us all alot.
Cheers

http://www.doom9.org/software2.htm

Goto to VOB Tools. It's the first in the list. Use Open instead of Save.
Doesn't work with Opera, just with IE. Maybe with Mozilla... ;)

Bilu

Ahh. it's working now - thanks bilu :lol:
-vhelp

Offtopic:
@rds_correia
I didn't manage to make any progress with the hosting. Even with netfirms the images are unreachable, they spit out a message that they don't alow direct linking and so on. :evil: :evil: :evil: :evil:
As a workaround I made this html page with information croped from original post so you can find my settings.
http://marcellusvcd.netfirms.com/settings.htm

Good luck with your test! :wink:
marcellus

@ Marcellus
Sugestion: lower the number of B-frames. It lowers file size (dont ask me why) and speeds up encoder. This is Incredible way. I've go 1b frame.

Great.
Hey those BV pics look really nice.
Now I'm gonna give it a go.
C ya

Hi Hydeus
Well, I ended up with the value of 4 because that way I noticed that the quantization stays lower at the same bitrate setting (at least in my tests). When I increased the B value even more the quantization goes even lower but the image tends to be uglyer and messed-up.
I noticed myself the speed increase with less B frames and I explain it by the fact that probably the algorithm to produce a B frame is more CPU intensive than for a P frame.
bye
marcellus