HANDBRAKE - the best video transcoder for Linux?

That’s what I’ve been trying to do. You need to set a delay double of what’s mencoder’s setting, in the other direction (yes, it’s a hack, and mencoder sucks for not allowing to disable it’s “smart” automatic delay). The result is, you still get a file where audio and video don’t start at the same time. Not good. Of course, supporting mkv natively would make these unsafe hacks unnecessary.

you want no delay? use -mc 0 which completely disables MEncoder’s internal synchronization but be prepared to get sync issues more than without it

Whoah, a but touchy on the subject, are we? :slight_smile:
I read that, and that behavior is not intended by the original specs. Also, check the doom9 forum, there’s lots of controversy on the subject.
The thing is, it’s not 100% defined. Which means, there are multiple ways to implement it. Which means I’m not going to use it because the tools may reject my file, or interpret it in a slightly different way, and they will be right.
Also, like you said, the other widely popular open-source program, VirtualDUB, does it differently. So, I’m not taking chances.

Yes, I’m a bit of touchy because it’s people like you who 1) have no idea on what they’re on about, 2) spread misinformation and 3) as others read it, they start to believe as many don’t take the time to check out correct sources, which in turn results in more spreading of misinformation and down the hill rolls the ball :wink:

Also, it doesn’t have to be 100% defined. The point is that the specs themselves do not prohibit this and obviously, if one would want to implement this, one should do it the right way and not the “brain-dead” way like VDub & co

Plus, it doesn’t have chapters, and I like chapters. So, mkv it is. At least it’s 100% defined, and not extended by third-party people in slightly different ways.

It sounds like you’re trying to make this whole argument into AVI vs MKV thread, which this whole thread never was about. Yes, AVI doesn’t support many things and never was intended to in the first place so that’s why other containers exist. You can just as well use dvdxchaps to dump DVD chapters and import them into MKV, which I do in h264enc

So, one moment you’re saying mencoder is the mother of all encoders, and then - that it’s bad?
Well, yes, it is bad. No, I’m not going to fix it. I have better things to do than fixing broken (beyond repair) programs. Like contributing to Avidemux, for example. You know, the encoder that already is in the 21st century.
The program cannot be good in the future, what matters is how good it is now. Saying you can’t blame a program for not having something (because someone need to fix/rewrite it) is just silly.

Wait what??? :confused:

Point out where I implied that mencoder is the mother of all encoders and is so good. Don’t put words I never said in my mouth, boy. If you have read the other thread of the OP, you would see yourself what I think about MEncoder and I’m not going to repeat it again. Fact is, for me mencoder has always done it’s job so there’s little reason to switch to something else. I might as well switch over to ffmpeg but don’t, mostly due to its lack of filters and direct DVD input. Also, I don’t like GUIs for encoding.

No, it is not silly. If one wants something, one should implement it. But since no one does want to do that but only moan how bad mencoder is and what it is missing, of course at present time it’ll lack much. What do you think? That you can just sit on your butt and mencoder will magically implement itself the stuff users want?

Will have to post twice as this forum complains in me including 6 images (where???)

So, are they playing the VBR mp3 audio interleaved in the avi file? Without any sync issues, proper seeking, etc…? If they don’t, I can’t blame them at all, since you can correctly implement the AVI specs and still not be able to deal with VBR audio.

Come on dude, you have no idea what you’re on about. I have an old Panny (Panasonic 1st generation DVD/DivX player) and it never had problems with mencoder AVIs + VBR audio, provided that one turns off OpenDML as it tends to choke on seeking which isn’t mencoder’s fault but the fact that the player doesn’t support OpenDML files at all. My 2nd generation Philips and my other 3rd generation Samsung also don’t have any issues

So, do you use any special recipes not mentioned anywhere? Or is it just a straightforward mkvmerge command? Sorry, I don’t have enough time to read 288K shell scripts.

The script supports exporting all of the encoding configuration, including muxing and audio encoding using external programs, to a file which you can inspect for yourself. All is in there

As for the sync issues, try this on some music video (the easiest way to check is to watch the drums with mplayer’s slowdown):

$ mencoder -vf yadif=1,harddup -ovc lavc -lavcopts vcodec=mpeg4:keyint=132:threads=2:vbitrate=1000 -fps 50 -ofps 50 -oac copy -dvd-device . dvd://1 -aid 0 -o test.avi -endpos 0:2:0

The command has been vastly simplified for demonstration purposes, of course.
Notice the ~150ms delay? That’s it.

Yes, I tried it many times and can’t notice any delays while watching that will produce unpleasant experience. In fact just now I bobbed a music video to 50fps, remuxing it to mkv with h264enc and it looks and sounds pretty decent to me. I used very fast options as my main PC is pretty slow when using mcdeint. You can get it from here: http://neutrino.dynalias.net:8080/JLo.mkv

Yep, used it, didn’t like it. Apart from being dog slow (like, unusably slow), it didn’t have any real perceived quality improvement compared to yadif=0.
Anyway, now that I’ve been doing yadif=1, I’m never going back.

Suite yourself, maybe you can’t see the difference (much). Others have confirmed that it can be beneficial

Of course mencoder handles them. It just does that incorrectly. :slight_smile:
The question is, does the
source -> mencoder’s “cleverly fixed” avi -> mkv
chain produce mkv with A/V sync? I’ve yet to get a definitive answer.

For me it does, and I’ve encoded hundreds of DVDs and am pleased with the avi -> mkv sync. If it doesn’t do it for you, use something else. No one is pushing it in your throat

Of course it happens, I’ve seen it. Are you sure that every time you download it, it’s going to produce correct files? I sure as hell am not.
Anyway, advocating a releaseless development isn’t going to get you anywhere. One has to make releases for the users to rely upon, otherwise it’s a support nightmare for both the users and the developers (in this case, the developers choose to ignore it), and I’m not talking about the code quality either (you know, feature freezing, testing, critical bug fixing, etc… phases).
Basically, every commit introduces a possibility of breaking everything in a slight way, because there is no mandatory separation of bugfixes / feature improvements. Having a proper release cycle mostly avoids that.

MEncoder doesn’t change at all, and pyramidal b-frames are well defined within x264 so how is it not going to produce “correct” files when neither of those things change?

Preach to the developers, dude. It has worked for them for many years and they surely don’t going to change it now due to some random person complaining on this forum how they should do it or not. Before something is fixed / committed, it gets quite a testing so they don’t blatantly apply patches which can break a lot of stuff. Every now and then, Diego puts out a release on the page of MPlayer. Do you think that this “stable” release does not have any issues? Think again.

Sure, blame the users :slight_smile:
Check the command posted above and tell me what is it that I’m doing so VERY wrong.

Anyway, my Avidemux has just finished encoding a file, time to start another one. :slight_smile:

I didn’t blame the users and you’re just twisting my words here. It is reasonable to assume that it could be a user error. This however is not a fact or confirmation that it’s always the user at fault and both mencoder & mplayer have their issues, and all other software in existance too

Also, stop trolling. If you hate mencoder so much, DON’T USE IT AND THERE’s NOTHING TO DISCUSS

PS: and yes, I’m a long time member of doom9.org and spend virtually each day in there

Umm, you’re confusing the b-frame-introduced delay with mencoder’s automatic sync. They have nothing in common. The delay I’m talking about is on the container level of the output file. -mc 0 has nothing to do with it.

Sure, whatever. So, how would a person like me, who obviously “has no idea what he’s talking about” know whether that one guy’s site is correct? Why should I trust you, or that site, at all? Maybe it’s you who “has no idea…” and all those other people are actually correct?
You know, like this one: Home of AVCutty ? Or maybe this: DivXLand.org - Video Troubleshooting Guide ?

As for the defined part, yes, it has to. If there is more than one way to do it, it’s a broken spec, that’s all.

OK, now you’re confused. All I said was that I prefer to mkv to avi because it supports chapters and has a no-hack VBR implementation. That’s why I use it (and use tools that natively support that). But you seem somehow offended by that. Whatever.
And yes, that’s exactly how I import chapters to mkv.

Well, the “never had problems for years” somewhat implied that.
Also, you’re somehow confused about the nature of this thread, and my reasons for posting here. I’m not trying to make you switch to anything, I couldn’t care less. I’m merely listing the problems I had with mencoder, the developers’ unwillingness or inability to fix them, and saying that Avidemux works better in the end.
Somehow, all this really offends you. I’ve no idea why.
That “boy” part should get proper attention from moderators, too.

You do know that Avidemux has a scripted/CLI version, right?

That doesn’t make the slightest sense. So, if some program (say, NetBSD) doesn’t implement a feature (say, a SATA driver), then I should fix that instead of switching to a better alternative (say, Linux)? And I should never state the reasons why I switched? Check your logic circuits. :slight_smile:
You know, people don’t have infinite time to fix everybody else’s code. If someone calls himself MPlayer developer, it’s his/her responsibility to fix it. Otherwise, he/she should stop calling himself/herself that and declare the project dead. It’s that simple.

Come on dude, you have no idea what you’re on about. I have an old Panny

So, your 3 players support it, therefore all players support it. Nice reasoning.

Yes, I tried it many times and can’t notice any delays while watching that will produce unpleasant experience.

If you can’t notice that, doesn’t mean it’s not there. I mainly encode music concerts and believe me, I can hear 40ms desync. And 150ms is just way too unwatchable for me.
I’m not the only one who sees it: Gmane Loom

You can get it from here…

You’re kidding me, right? The only guide there is their lips. You wouldn’t be able to tell the desync in that file even if you tried.

MEncoder doesn’t change at all…

There’s lots of other stuff in that binary, like, you know, filters, decoders (sure, some are part of ffmpeg, but they are using its SVN, which has essentially the same issue)…

For me it does, and I’ve encoded hundreds of DVDs and am pleased with the avi -> mkv sync.

Well, you’re making an objective thing subjective. There’s no “for me” here, it’s either in sync, or it isn’t.

It has worked for them for many years.

Heh, as evidenced by every second email on their lists being “use the SVN”? I’m not going to complain to them, I’m done. Moved away. If they don’t know that their development model is only hurting their project, it’s their problem, I don’t care anymore.

Do you think that this “stable” release does not have any issues

Two words: development phases. First there is a feature merge window. Then there are lots of fixes. Then there are fixes. Then there are critical fixes only. Then the stable release comes out. If something is still broken, each patch is reviewed and released separately. You know, like Linux, glibc, gcc, KDE, GNOME, and virtually all of the big software.
The “develop as you go” model will never get you the same quality.

I didn’t blame the users and you’re just twisting my words here. It is reasonable to assume that it could be a user error. … both mencoder & mplayer have their issues

So, the “Obviously, you’re doing something VERY wrong” part could have been targeted at mencoder, and not me, the user?

You know, I’m tired of this useless conversation, already wasted too much time with it. I conveyed my original view - that I had issues with mencoder (listed above) and that now I’m a happy user. That was my goal.
I’m not interested in further degradation of this thread into AVI vs MKV, mencoder development model, mencoder bugs or any other flame war (while being insulted by a complete stranger). I’m out.

Then fix it and STOP COMPLAINING WHILE AT THE SAME TIME DOING NOTHING YET BLAMING THAT IT IS NOT RIGHT. Hypocrisy much?

Sure, whatever. So, how would a person like me, who obviously “has no idea what he’s talking about” know whether that one guy’s site is correct? Why should I trust you, or that site, at all? Maybe it’s you who “has no idea…” and all those other people are actually correct?
You know, like this one: Home of AVCutty ? Or maybe this: DivXLand.org - Video Troubleshooting Guide ?

As for the defined part, yes, it has to. If there is more than one way to do it, it’s a broken spec, that’s all.

Maybe then I should point you to this Lair Of The Multimedia Guru » AVI and B frames and this Lair Of The Multimedia Guru » The AVI container file format site, which say the same thing and this is coming from Micheal’s mouth (hint; main dev/maintainer of ffmpeg and VERY skilled person). But oh, wait, you won’t believe it either just so you can convince yourself that you’re right and others are wrong.

No, it is not “broken spec”. It is brain-dead way of putting stuff where it doesn’t belong at all, simple as that. The VDub guys were in the past embarrassed and fixed it, afaik

OK, now you’re confused. All I said was that I prefer to mkv to avi because it supports chapters and has a no-hack VBR implementation. That’s why I use it (and use tools that natively support that). But you seem somehow offended by that. Whatever.
And yes, that’s exactly how I import chapters to mkv.

No, I’m not offended at all :slight_smile: I also use MKV but AVI -> MKV intermediate step is also good for me and don’t have problems with that eaither

Well, the “never had problems for years” somewhat implied that.
Also, you’re somehow confused about the nature of this thread, and my reasons for posting here. I’m not trying to make you switch to anything, I couldn’t care less. I’m merely listing the problems I had with mencoder, the developers’ unwillingness or inability to fix them, and saying that Avidemux works better in the end.
Somehow, all this really offends you. I’ve no idea why.
That “boy” part should get proper attention from moderators, too.

“never had problems for years” does not imply globally that others won’t. I personally never had problems but if others do, they should use something else. It’s simple as that.

You do know that Avidemux has a scripted/CLI version, right?

Yes I know (duh), but I don’t use it since mencoder is enough for me. If and when mencoder starts doing some totally insane stuff which blatantly violates every single spec out there or constantly messes stuff with very noticeable effects to the point of not being able to “normally” watch something (eg, major sync issues, distorted pictures, severs spec violations, etc), I’m not going to switch really. Unless they kill it completely and it’s gone or in such a state that it’s useless.

That doesn’t make the slightest sense. So, if some program (say, NetBSD) doesn’t implement a feature (say, a SATA driver), then I should fix that instead of switching to a better alternative (say, Linux)? And I should never state the reasons why I switched? Check your logic circuits. :slight_smile:
You know, people don’t have infinite time to fix everybody else’s code. If someone calls himself MPlayer developer, it’s his/her responsibility to fix it. Otherwise, he/she should stop calling himself/herself that and declare the project dead. It’s that simple.

My logic circuits are just fine, it seems yours are constantly messing up and making their own version of what I said.

If you are committed and want to use NetBSD, have the skills and time to implement it, then there’s little reason not to do it. Instead of wanting to use it, having the skills and time, yet only moaning about it that no one fixes or implements it. There’s a huge userbase of MPlayer out there and only 3 MPlayer developers, one of which is not really a dev but cleans up stuff and pushes other’s patches and maintains it (Diego). The other two are not that skilled to fix each and every thing. Even Reimar has problems in understanding some very deep stuff, from coding point of view.

Again in two replies :\

So, your 3 players support it, therefore all players support it. Nice reasoning.

You forgot my user’s players too and all other players who also don’t have problems either.

If you can’t notice that, doesn’t mean it’s not there. I mainly encode music concerts and believe me, I can hear 40ms desync. And 150ms is just way too unwatchable for me.
I’m not the only one who sees it: Gmane Loom

I never claimed that mencoder doesn’t introduce delays. I only said that i don’t notice this. If you can with your alien ears :wink: then like you do, don’t use it.

You’re kidding me, right? The only guide there is their lips. You wouldn’t be able to tell the desync in that file even if you tried.

Yes, apparently I’m kidding you and you didn’t even download the file so I’m taking it off.

Well, you’re making an objective thing subjective. There’s no “for me” here, it’s either in sync, or it isn’t.

The fact that an objective thing is made subjective not always makes it false. If this was true, then you shouldn’t encode at all since what may look good to you may look like cr@p to someone else. Fact is, the delay is so tiny, that i can’t tell the difference between a file with the delay present and a file without the delay. So for me it is “good” and since i can’t tell the difference, either will do.

Heh, as evidenced by every second email on their lists being “use the SVN”? I’m not going to complain to them, I’m done. Moved away. If they don’t know that their development model is only hurting their project, it’s their problem, I don’t care anymore.

Good for you then :slight_smile: I don’t know why you argue with me on this, since it wasn’t my decision to develop like that and not put “stable” releases. Like I said, devs are responsible and since you tried (which I can’t really verify from here unless you post links and somehow prove it was you who wrote them), I have not much to say about it… Either like it or don’t. Personally it doesn’t bother me but if it bothers someone else, there are alternatives like you have found.

Two words: development phases. First there is a feature merge window. Then there are lots of fixes. Then there are fixes. Then there are critical fixes only. Then the stable release comes out. If something is still broken, each patch is reviewed and released separately. You know, like Linux, glibc, gcc, KDE, GNOME, and virtually all of the big software.
The “develop as you go” model will never get you the same quality.

See above :slight_smile:

So, the “Obviously, you’re doing something VERY wrong” part could have been targeted at mencoder, and not me, the user?

You know, I’m tired of this useless conversation, already wasted too much time with it. I conveyed my original view - that I had issues with mencoder (listed above) and that now I’m a happy user. That was my goal.
I’m not interested in further degradation of this thread into AVI vs MKV, mencoder development model, mencoder bugs or any other flame war (while being insulted by a complete stranger). I’m out.

I always assume first that it may be user error, given the amount of options mencoder supports, its not very clear documentation and the amount of user errors I’ve seen and continue to see.

Also, you brought it up and I REPEATEDLY STATED MULTIPLE TIMES that if mencoder doesn’t do it, use something else. I also never claimed that mencoder is God and all should use it. You tried to put that into my mouth (though I use different words to formulate it)

Yes, I agree, the convo is useless so lets just stop it here as I won’t be replying anymore

JFYI, I’m currently keeping an eye on their commits and making releases when appropriate (i.e. not when there are only MacOSX or Windows GUI related changes ;-)).

Latest SVN revision 2815 is already there (currently building): PackMan :: Package details for handbrake

pbleser: THANKS. :slight_smile: