I would like nero AAC codec for VirtualDub, but I don't know exactly what is it there?
Look at the attachment below, there is no AAC ACM Codec in the Select box, so I need it to be easy for me converting AAC audio like MP3 Lame.
I try download fccHandler AAC ACM Codec, but this codec can only decode AAC, it does not work for encoding.
Could anyone help with this to support..? Thanks in advance!
+ Reply to Thread
Results 1 to 20 of 20
Last edited by Leo99; 21st Aug 2013 at 13:06.Leo99
You need to use the external encoder feature in Virtualdub 1.10.0 and later to use the Neroaacenc.exe. If you are using aac then I assume you want to create x264 mp4. Here are the encoders that you would use to create an x264/aac.mp4...
Encoder Set MP4_M
Video Encoder: 264 M
Audio Encoder: Neroaac
File description: mp4
File extension: mp4
Type: Video Encoder
Program: C:\Tools\x264.exe (or the path to your exe file)
Command Arguements: --crf 18 --preset medium --tune film --demuxer raw --input-csp i420 --input-res %(width)x%(height) --fps %(fpsnum)/%(fpsden) -o "%(tempvideofile)" -
Output Filename: %(outputname).264
(place a check mark in first three boxes)
Type: Audio Encoder
Program: C:\Tools\neroAacEnc.exe (or the path to your exe file)
Command Arguements: -q 0.50 -ignorelength -if - -of "%(tempaudiofile)"
Output Filename: %(outputname).aac
(place a check mark in first three boxes and under Audio tab, check Wav file and Bypass compression)
Program: C:\Tools\MP4Box\MP4Box.exe (or the path to your exe file)
Command Arguements: -add "%(tempvideofile)" -add "%(tempaudiofile)" "%(outputname)" -fps %(fps)
(check all four boxes)
...or you could download the text file in this thread and change the extension to vdprf and load that in the external encoder.
I have posted a VDPROF file on Budmansite.com that is set up for MP4 (single and dual pass), Mpeg2, and FLV (AVC/AAC) that you can import into VirtualDub (1.10.xx +). You WILL, as DarrellS has pointed out, have to change the Program line in each Audio, Video and Multiplexor line to the correct location of the YOUR External Encoders since mine will not be the same path as yours.
Program: C:\Tools\x264.exe (or the path to your exe file)
I gave you props in the other thread but I was in a hurry here. I still haven't gotten around to getting VP9 working and until x265 implements stdin or ffmpeg implements x265, we won't be able to get that working either. I did get Mencoder working with the help of Selur. Something the experts at Virtualdub forums couldn't get working. Have you found anything better for mpeg2 than ffdshow? I only found one CLI encoder that supposedly supports stdin but I couldn't get it to work. I did find this command line for ffmpeg that is supposed to be better quality, IDK.
-f rawvideo -s %(width)x%(height) -r %(fpsnum)/%(fpsden) -i - -vcodec mpeg2video -target ntsc-dvd -me_method epzs -threads 4 -g 45 -b 5800000 -bf 2 -trellis 2 -cmp 2 -subcmp 2 "%(tempvideofile)"
DarrellS, Thanks for the better quality format script. I added it to my VDPROFs and reposted it at https://files.secureserver.net/0sou9GKxPLkcGw. I didn't see too much difference but it did correct my aspect settings. Also this will allow a Progressive (Yours) and an Interlaced version (Mine) in case users want to choose. The output is shown below for:
-f rawvideo -s %(width)x%(height) -r %(fpsnum)/%(fpsden) -i - -vcodec mpeg2video -target ntsc-dvd -bf 2 -b 8000k -dc 9 -flags +ilme+ildct -alternate_scan 1 -top 0 "%(tempvideofile)"
-f rawvideo -s %(width)x%(height) -r %(fpsnum)/%(fpsden) -i - -vcodec mpeg2video -target ntsc-dvd -me_method epzs -threads 4 -g 45 -b 5800k -bf 2 -trellis 2 -cmp 2 -subcmp 2 "%(tempvideofile)"
Thanks again to DarrellS for your settings.
@DarrellS: Sorry late reply, So nice script, OK I will try and will ask again if something problem later.
I use VD 1.9.11 'cause my OS 32-bit. Sadly this neroaacenc does not supported by VD as internal plugins. A simple idea as valuable input for the officals SourceForge.
Anyway, thank you for the tricks, DarrellS.Leo99
Thanks also @Budman1, I think using x264 I do not quite understand its syntax script, but the way shown by Darrells it seems easier to follow..right?Leo99
I'm using XP Pro 32bit and 32bit Virtualdub. You need version 1.10.0 or newer (the experimental builds which I use 1.10.4-test11). With the .vdprof file, you just load it into the external encoder with the Import button. All the encoder sets are already made up. You'll need to download all the command line encoders or like Budman mentioned, most of them are in Selur's Hybrid program. You'll need to go into the external encoder and change the file path to the CLI encoders or make sure you place them where they are in the vdprof file. We're here to help if you run into problems.
Virtualdub site and a guide here so people don't have to dig through threads to try and find out how to use the external encoder. Maybe Videohelp can create a new Virtualdub section with all up to date stuff.
DarrellS, ow thank you very much for your fine accomplishment! This is one terrific posting and very details for a beginner like me. Yes you right, in version 1.9.11 there is no External encoders menu, so I was confused before.
Much appreciated and it's very helpful, I will try it and report then...
Last edited by Leo99; 25th Aug 2013 at 23:05.Leo99
DarrellS, yes I agree. I've tried to post the VDPROF and a VirtualDub DOCX that explains what I've found in several places. The problem is when others have to change the Encoders path for their computer setup. I'm trying to write an install that will just ask where their encoders are, check that they are all there and modify the script accordingly so they can just import. Harder than it sounds. LOL
I think that's why they suggest C:\Tools. I know other programmers suggest C:\Tools (you have to create it of coarse) to store their encoders and stuff also. Obviously there are some encoders that need to be in their program folder (or the dlls that they depend on in the same folder as the encoder).
I like the idea of the installer. I've seen that in a few other programs where you tell the installer where the codecs or other programs are at. Even a zipped Virtualdub file with everything needed and instructions would be nice. It would easy to transfer everything to a newer build with just copy and paste.
I know Avery doesn't want to add (and update) all the codecs because of licensing issues but somebody could. Selur has most of the encoders you would need in his Hybrid program folder. It would make it easier for new users than having to try and change all the paths in their vdprof file. That alone, scare most new users away. It's the main reason that newbies use Handbrake or AviDemux since they don't have to hunt down and install all the encoders.
If they knew how easy that the external encoder feature was to use once they had it set up, I think a lot more people would use it. Even most experienced Virtualdub users on here seem to be afraid to try it out. I try and mention the external encoder to everyone that states in their OP that they use Virtualdub and are looking for help. At least they already are familiar with Virtualdub so the hardest part of the learning is done. All they have to do is just follow a few guides. Most of the work has already been done by others. I didn't know anything about CLI encoders before I starting using it but I'm learning a lot and am probably more interested in CLI encoders than anything else
I just wished more of them supported stdin because there would be no limit to what file types you could create.
The modded versions used to be more popular than Virtualdub itself. There's no reason that people couldn't create newer modded versions. A lot of the programmers that lived on the Virtualdub site in the early part of the century seem to want nothing to do with Virtualdub today. I have a hard time over on the Doom9 forum where all those guys hang out now. Virtualdub seems to be a sore topic over there for some reason. I think ego may have gotten the best of them. I don't know what happened to fcchandler either. I hope he just went into hiding for a while to take a break but I fear the worst. He has been the biggest contributor to Virtualdub the last few years and it wouldn't be the same without all his work.
I think Avery has some big changes planned for the external encoder in the next release. He hinted in two or three threads and he's been pretty quiet lately so he must be pretty busy working out the kinks.
Wonder how much trouble I could get in if I created an installer with all complete... Only thing is it might be hefty for some:
24.50 MB FFmpeg
13.70 MB External Encoders
6.06 MB VirtualDub (1.10.3)
8.24 MB Plugins (I have tons)
52.50 MB Total all included with VDProf to import. I understand it's sometime tricky to distribute, even freeware software, so ...
Personally I use VirtualDub all the time now that it can encode in other formats it has a ton of features other converter/editors lack. Not sure about the Doom thing but I've heard about their attitude about a lot of subjects... from a lot of places...
Does anyone know the criteria for distributing Open Source software and Freeware that is not open source? The installer should be pretty easy to set up since nothing has to be installed except to a location and accompanying Uninstall software. I already have 2 creators and of course the free one that comes with Windows. I'd be willing to go ahead if permissions for every Encoder and filter does not need to be obtained separately. I have written several programs that contain Open Source and when I inquired they simply said I must include the source code with it. Don't know if that's the same for all of them.
Hybrid program Which is 236 MB. All the essential encoders and supporting dlls are around 50 MB.
Selur would probably be the guy to ask about the encoders since he has those encoders in his free program. Avery wouldn't have a problem but it wouldn't hurt to ask in the Virtualdub forum. There are a few that you can't distribute like fdkaac or neroaacenc but there are substitutes. ffmpeg has a few encoders as you know. If they would implement a few more then you wouldn't need many.
The file sizes I gave above are for most of the external plugins, only MP4Box (for MP4), encoders (Neroaacenc, X264, Mp4 Box) FFMpeg (no FFProbe or FFPlay) and VirtualDub itself. This allows me to run all video files in VirtualDub and convert to MPeg2, FLV, and MP4 file types so far with AVC, AAC, MP2, Mpeg2 formats. Guess I could create the installer and anything I couldn't distribute, make a popup that says go here and download this and put it in C:\tools folder.
Not very pretty sure, just a rough guess.
Would not it be a lot easier running everything in cli mode (if possible?) and write down your own script to trigger others in a particular sequence? Most of of time we normally deal with pretty much same settings.
Last edited by enim; 29th Aug 2013 at 14:28.
Hopefully when we get everything straightened out we'll be able to get a Virtualdub External Encoder thread pinned to the top (or a Virtualdub thread with all input plugins and external (CLI) encoders) with a guide on how to set everything up.
My vdprof file is listed in the link above with links to the threads on the Virtualdub forum. Not sure if the vdprof file (it's just a text file that you need to add .vdprof to the end) will post here because it is huge. In case it doesn't, here is the link... http://forum.videohelp.com/attachments/19316-1376255110/08-11-2013.txt
and the links to the Virtualdub threads with guides and support...
The text was too long to post. Here is my latest. Change .txt to .vdprof and import in External Encoder. VC-1 and WMA Professional 5.1 don't seem to be doable and waiting for stdin for x265 and vp9 or for ffmpeg to implement the encoders...
You'll need to change the location of the encoders to where they are on your PC. If you don't have them then you'll need to download them.
Sorry DarrellS, I can't use Osmo4.exe either Classic or New UI, I have to debug this appl cause the MP4Client.exe has encountered a problem and need to close! I don't know what exactly wrong.. Trying to understand the command line parameters, but still confused too.. no talent for me. So, I decided to use the ready programs just like Hybrid or SUPER to solve it.Leo99