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: Quote:
Quote:
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.
|
Quote:
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?
|
Quote:
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 |
Quote:
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 |
Quote:
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 |
Quote:
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 |
Quote:
Or would this be better? Quote:
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)
|
Quote:
Quote:
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 |
Quote:
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. |
Quote:
Hey those BV pics look really nice. Now I'm gonna give it a go. C ya |
Quote:
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 |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.