View Full Version : MeGui audio encoding via Command Prompt
jonathonsunshine
4th October 2008, 17:56
Howdy yall.
MeGui has a way of encoding audio by feeding an Avisynth script into a command line encoder such as NeroAacEnc.exe .
How can I recreate this purely through the command prompt ? (So i can use it in a batch file).
And by "recreate" I don't mean get the same result, I mean how can I do it the exact same way, or through the exact same processes that MeGui does, and WITHOUT using BePipe.exe.
Thankyou
tebasuna51
4th October 2008, 22:31
MeGui has a way of encoding audio by feeding an Avisynth script into a command line encoder such as NeroAacEnc.exe .
Not exactly. Send AviSynth output (with AvisynthWrapper.dll) to the STDIN input of the encoder. Don't make a command line to execute.
AviSinthWrapper.dll is used also in BeHappy, now with big precision output (32 bit float instead 16 bit int with MeGUI)
How can I recreate this purely through the command prompt ? (So i can use it in a batch file).
And by "recreate" I don't mean get the same result, I mean how can I do it the exact same way, or through the exact same processes that MeGui does, and WITHOUT using BePipe.exe.
What is the problem with Bepipe? Bepipe was created by Dimzon like AviSinthWrapper.dll, BeHappy and the MeGUI part to use AviSynth to recode the audio instead BeSweet.
If you want a command line to send the AviSynth output from a .avs file, you can use also wavi (.NET not needed):
wavi input.avs - | neroaacenc -q 0.4 -if - -of output.mp4
You can use also avs2avi.exe and SoundOut avisynth plugin to write a command line using AviSynth for recode audio.
jonathonsunshine
5th October 2008, 15:13
What is the problem with Bepipe?
There isn't anything wrong with BePipe, but that was an example of things that "would have the same result". Wavi is another example.
This thread is the "sister thread" to http://forum.doom9.org/showthread.php?t=141659 . I want to convert AVI files to ipod compatible mp4 files through a batch file. MeGui does it perfectly, but when I try to do it manually, with only the command prompt, I get the -2014 error, Incorrect duration, from Quicktime and iTunes.
As far as I can tell, the only step in the process that I cannot replicate through the command prompt is the audio encoding.
At 1st, I was using WAVI, and then feed the WAV file to NeroAacEnc, but I got the error, so I started using BePipe because I understood that it did "basically the same thing". But obviously, it isn't completely the same, because it doesn't work either.
Thanks anyway thou, I had seen a similar thread to this somewhere and the only response he got was, "Quicktime is a POS" use something else.
tebasuna51
6th October 2008, 02:45
After read the "sister thread" I'm sure the problem isn't the audio conversion. Is in the mux step.
Try use MeGUI to mux the streams obtained with x264 and wavi (best than bepipe) and see if is Quiktime compliant.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.