help improve work flow?: vegas->huffyuv->x264

[rookandpawn]

i am working with .veg (vegas project) files and rendering the video to AVI (custom->ffdshow->HuffyUV) and the audio to Sony MP4.

Then I write a one line avs script for each AVI video avisource("foo.avi"), read it into megui, set my options, and queue up a whole bunch of two-pass jobs and output the AVI into MP4 AVCRAW and get a series of .264 files.

Then I select MP4 muxer and mux each .264 with its MP4 audio stream to get a .mp4 (FYI my audio always ends a bit later than the video stream, outgoing fading music effect so i wanted separate files to prevent alignment problems)

THen i use mkvmerge or yamb/mp4box to join end to end these series of MP4 files into one big MKV or MP4.

1) So the bottle neck i am noticing is Vegas->HuffyUV. Is the FFDShow tryouts always using the author's latest build of HuffyUV? Its taking upwards of 15 minutes for a 3-4 minute video to go to HuffyUV. I have to do this for each .Veg project.
The vegas render regions -> batch render script does not do custom encodes. Is that changeable?

2) After I batch up the AVI->264 (AVCRAW) jobs, i then have to be there so i can select the now present .264 file to mux with the already present mp4 audio stream in megui. Isn't there a way to specify a mux job into the queue with a video file that does not exist?? Is this time to stop using megui? and start writing .bat files and specifying my own x264 options?

3) i love using vegas but these .veg files seem to severely restrict the possibilities of using all these other tools..
for instance why not a .veg -> huffyuv program? i imagine its
very complicated?

:thanks::thanks:

[mitsubishi]

In meGUI, once you set up your video, rather than clicking "enqueue", click "AutoEncode" at the bottom.
A window will pop-up. Set your container.

Then check "add additional content".
Hit "queue".
Now you can choose your pre-prepared audio.
Hit "go" to queue it all up.

You can even set target size on the auto-encode window rather than using bitrate calcutor.

If you had set up an audio encode on the main screen, this be included in the mux automatically, so make sure that bit is clear (Hit "X" button to clear)

[akupenguin]

Is the FFDShow tryouts always using the author's latest build of HuffyUV? Its taking upwards of 15 minutes for a 3-4 minute video to go to HuffyUV.
What is "author's latest"? ffhuffyuv is part of libavcodec, just like all the other codecs in ffdshow. It's always up-to-date with whatever the last time is that ffdshow synced with libavcodec svn, which is pretty frequent compared to the rate at which a simple codec like huffyuv changes.
I have no idea why yours is slow, but it's not normal. ffhuffyuv can encode SD at more than 300 fps here.

[BlackSharkfr]

Vegas is a non-linear editing software, not an encoding software.
The bottleneck isn't the encoding process but Vegas's rendering engine.

it's just like if you put a super intensive pre processing avisynth script before your encode. FFDS is rendering slowly just because that's the speed at which it gets the frames.