Discussion Forums > Technology

A/V sync problems with selfmade MKVs... Help?

<< < (3/3)

iindigo:

--- Quote from: nstgc on January 14, 2010, 01:58:10 PM ---
--- Quote from: iindigo on January 11, 2010, 01:55:48 PM ---
--- Quote from: nstgc on January 10, 2010, 12:38:10 PM ---Also try this: --default-duration 0:30000/1001fps

--- End quote ---

I fail to see how this will help when the --default-duration argument is being ignored totally, but if you insist I'll try it anyway
--- End quote ---

What I was thinking was perhaps it didn't like the "1:29.970fps" you specified earlier. I found that some programs don't like it when you use decimals and preffer expressing it as a fraction. MEncoder is like that. I know that you aren't using MEncoder, but I figured I'd throw it out there.

--- End quote ---

Ahh ok, thanks for explaining.

I found out what my problem was... I was inserting the command in the wrong area (I think) of the commandline string. Either way, I managed to get what I needed with a command quite similar to the ones fizzmaister posted (thanks, by the way - even if I didn't use those this time, they make great examples for future endeavors!).

nstgc:
For future endeavors I would suggest MKVtoolnix-gui. It gives you the command line. I About a year and a half ago I wrote some scripts which ripped, encoded, and muxed DVDs. While MEncoder was pretty strait forward I found the muxing to be problematic. I used the GUI then copy and pasted the command line code into the script. Given that for anything longer then half an hour had a tendency to have the audio cut off (but the original, separated audio stream was fine) probably indicates that I shouldn't have completely relied on a GUI however. Still, its nice to start with something like that then fix it later. At least for me. You, iindigo, are using a Mac so you may not be a complete amateur like me though.

Just a suggestion.

iindigo:
Ahh yeah... usually when the option is available, a GUI is nicer than the commandline (especially when the commands used are longer than most English sentences). As mentioned before, however, only really old builds of mmg (the MKVMerge UI) exist for the PowerPC (yes, I'm still stuck on a machine from 2005) and won't run properly. All newer builds have dropped support for PowerPCs entirely and will only run on Intel-based Macs, and thus I'm pretty much stuck with the CLI version whether I want to be or not :P

It's not that bad, though... I've become pretty accustomed to the command line over the past decade, so it's nothing new to me.

Navigation

[0] Message Index

[*] Previous page