[Ben Longden]

Tried rendering the project firstly to an .avi file first? Then re-render that file to MP4.

Doing this means it can do all of the plugins and corrections work and simply put out a .avi file, before spending processing power converting to MP4.

Just makes things less complicated for the processor..

Ben

Do unto others…

[Ben Longden]

Thanks for this… Ive been wondering how to do that…. One more question; How would you make the glint fade in and out?
Doing it as a separate clip just gives a cold cut.

Ben

Do unto others…

[Ben Longden]

For a faster workflow, use Vegas for the capture (ingest) process.

Open Vegas, then select the import function and se the camera icon. This opens up Sony Video Capture 6.

Unfortunately this next bit is not designed well. To select WHERE you want to park the files, Click Capture, then capture preferences, then DISC MANAGEMENT. In here, create the folder you want and where you want.

Then use the prompts to ingest the files.

The advantage of this is that once ingest is finished, and you close capture, ALL of the clips appear in the media pool ready for placement on the timeline.

Saves me a few minutes each time.

Ben

Do unto others…

[Ben Longden]

The saga gets better, and I’m thinking DVDA is the villain….

After finally rendering the 530 JPGs to an .avi file, I went back and tried to render that .avi into an MPEG2 file for 1) burning to DVD-ROM and also 2) to DVDA for a DVD.

As soon as I pressed GO, it came up with the same blasted error message. Not enough memory.

Something made me actually look at the HDD real estate available. An alarm bell went off, as I had 50GB left on the C drive. So I hunted down the temporary but permanent files that DVDA makes after each job, and mercilessly nuked them.

I now have nearly a terabyte back on the C drive, and needless to say Vegas is rendering to any format with ease.

Moral of the story is to purge the DVDA files regularly….

Ben

Do unto others…

[Ben Longden]

Thanks for the quick replies, Guys.

I’m not 100% convinced its a PC issue. I do acknowledge that the PC is dealing with some huge numbers, and this may be the problem.

When Vegas 6 was first released, a client wanted a 400 image slideshow done. I shot that one with the same camera, same PC and applied Ultimate S to do the transitions and pan-n-scan.

It did work, flawlessly and rendered to .avi in less than an hour.

How many pix in the current problem were used?
All 530 (1.96Gb total), with six titles produced in Vegas. The final product is 720×576 SD widescreen PAL.

Thoughts?

Ben

Do unto others…

[Ben Longden]

Rendering is indeed a dark art… so much so that even the Sony Vegas 9 BOOK ignores it…

The big thing is to make sure the preferences in Vegas are the SAME as in DVDA. That is, it defaults to NTSC 4×3, and you need to make sure its set correctly.

Once done, all will be better.

For some strange reason, I have found a better result on screen (and no-one can tell me why) if I render in Vegas to produce a .avi file, and then place THAT in DVDA to burn to disc. Its simple and effective.

I have used the render to DVDA file in the MPEG2 options and found this to give the second best visual results. Actually I was doing things that way for years until “working in the lab, late one night, my eyes beheld a mysterious sight”… and I accidentally dropped an .avi file into DVDA.

“Bu%%er”, I thought. “It will take ages” especially after the accidental render to .avi was pretty fast. The time taken wasnt much different from the MPEG2 render… and then I noticed the crisper vision. So now my workflow has changed. Clicking on the “interleave every frame” ensures fx such as glint and light rays are smooth, and Vegas does not have to recompress any of the existing .avi files on the timeline.

Besides, the less a file is changed, the less damage to the vision quality happens..

2.2c inc tax.

Ben

[Ben Longden]

In the render section, use the .AVI template, and make sure it fits with your current project settings (like NTSC/PAL, 29.97 or 25fps, 16:9 or 4×3 and screen pixel sizes).

For me, I use the standard PAL DV widescreen template (Im in PAL land and shoot widescreen 720×576)

For the video quality, check the “best” box.

The acid test is when rendering an “untweaked” avi clip, is to see the words “recompression not required” in the preview window.

If you get that, all should be well with the world. Reapply your tweaks, and render.

HTH
Ben

[Ben Longden]

John,
When I first used Vegas and DVDA, I followed the ‘render as separate vision & audio files in DVDA’ path and got a lot of coasters, so I looked at the alphabet soup deep in the ‘advanced’ settings and noted they were identical to that of rendering directly to an MPEG2 file.

Until the other day. I accidentally sent an .avi file out of vegas into DVDA, and the result was spectacular and sharp.

I then experimented and did a render using the DVDA template in Vegas (with audio stream attached and two pass render, and it was also razor sharp.
Doing the render with identical bitrates as a standard MPEG2 was laden with mosquito noise and motion artifacts.

The frustrated techie in me wants to know why.. can you help?

Cheers,
Ben