MNk
2nd February 2009, 00:23
Hello everyone,
I come to you for a rather technical question about using AAC encoding faac or neroAacEnc.
The goal is to encode an audio track in AAC 128kbit contained in a MOV or MP4 in a without having to extract it beforehand.
When I use MeGUI to encode the audio track contained in an MP4, simply:
1. Select the MP4 file, choose the encoder FAAC and select Raw-AAC for the format.
http://www.alexandrenest.com/faac/001.jpg
2. Put in the queue and start encoding.
http://www.alexandrenest.com/faac/002.jpg
It notes that during encoding, ffdshow is used to decode the audio and video, even if we agree that during this procedure, the video is useless.
http://www.alexandrenest.com/faac/003.jpg
It is therefore with a file. AAC encoder proper.
If we analyze the logs of MeGUI, it can be seen that before starting the encoding, it automatically creates an AviSynth script to decode the source file and encoding.
http://www.alexandrenest.com/faac/log.txt
Avisynth script
DirectShowSource ("C:\x264\myvideo.mp4")
EnsureVBRMP3Sync()
SSRC(44100)
Normalize()
return last
[b]Are attacking me now what is the problem.[/ b]
My goal is to create one .BAT automating the encoding of the audio, the encoding of the video track and muxer all in a MP4 container. The creation of a script prior AviSynth is mandatory and can handle as you wish, video and audio. It also, according to the source file, insert either DirectShowSource or by QTInput, etc ...
In short, my problem is that I can not encode the audio in the same MP4 using FAAC lines of code.
Example: 128-b faac.exe -mpeg-vers 4 -o "C:\x264\myvideo.aac" "C:\x264\myvideo.avs"
In a way, if I take the log created by MeGUI, I realize that the same AviSynth script and I run the same command line via a command prompt window, I get an error:
Could not open input file C:\x264\myvideo.avs
Yet if we try the script in AVSP, we see that the script is functional, video and audio are present, so no real worries that side.
After more than a night of searching all the forums, as doom9, etc... the only way that I imagine is that when you open the AVS script via the command line, it can not decode the source file. I infer that, because when MeGUI running this same command, the ffdshow icons appear, and there not.
I do not know if I explained my problem ... I guess for most people, this is Chinese, but all ideas are welcome.
Thank you in advance for all your answers,
Regards, Alex
PS : Sorry for my English, I'm French. :thanks:
I come to you for a rather technical question about using AAC encoding faac or neroAacEnc.
The goal is to encode an audio track in AAC 128kbit contained in a MOV or MP4 in a without having to extract it beforehand.
When I use MeGUI to encode the audio track contained in an MP4, simply:
1. Select the MP4 file, choose the encoder FAAC and select Raw-AAC for the format.
http://www.alexandrenest.com/faac/001.jpg
2. Put in the queue and start encoding.
http://www.alexandrenest.com/faac/002.jpg
It notes that during encoding, ffdshow is used to decode the audio and video, even if we agree that during this procedure, the video is useless.
http://www.alexandrenest.com/faac/003.jpg
It is therefore with a file. AAC encoder proper.
If we analyze the logs of MeGUI, it can be seen that before starting the encoding, it automatically creates an AviSynth script to decode the source file and encoding.
http://www.alexandrenest.com/faac/log.txt
Avisynth script
DirectShowSource ("C:\x264\myvideo.mp4")
EnsureVBRMP3Sync()
SSRC(44100)
Normalize()
return last
[b]Are attacking me now what is the problem.[/ b]
My goal is to create one .BAT automating the encoding of the audio, the encoding of the video track and muxer all in a MP4 container. The creation of a script prior AviSynth is mandatory and can handle as you wish, video and audio. It also, according to the source file, insert either DirectShowSource or by QTInput, etc ...
In short, my problem is that I can not encode the audio in the same MP4 using FAAC lines of code.
Example: 128-b faac.exe -mpeg-vers 4 -o "C:\x264\myvideo.aac" "C:\x264\myvideo.avs"
In a way, if I take the log created by MeGUI, I realize that the same AviSynth script and I run the same command line via a command prompt window, I get an error:
Could not open input file C:\x264\myvideo.avs
Yet if we try the script in AVSP, we see that the script is functional, video and audio are present, so no real worries that side.
After more than a night of searching all the forums, as doom9, etc... the only way that I imagine is that when you open the AVS script via the command line, it can not decode the source file. I infer that, because when MeGUI running this same command, the ffdshow icons appear, and there not.
I do not know if I explained my problem ... I guess for most people, this is Chinese, but all ideas are welcome.
Thank you in advance for all your answers,
Regards, Alex
PS : Sorry for my English, I'm French. :thanks: