Please He!p - Rendering to QT No Longer Works

Skevos_Mavros wrote on 10/23/2003, 12:46 AM
Hi all,

This is probably something really simple, but I can't see it. I'm working on editing some vox pops segments for a pilot and as I complete each segment I render a small Quicktime to email to the producer. The last few days I've stumbled across a problem that I haven't come across before. Vegas will no longer render Quicktime files at the same settings that I used to use only a week ago. It gets to the 10% mark and then gives me the following error:

>The error message I get

Yet there is plenty of room on all three of my drives (from 3 to 40 gig), and I get this error message regardless of which drive I try to render to. The first time it happened I restarted Vegas and it went away, but now nothing will work. All other render options (AVI, Real, etc) work fine. Here are the things I've tried:

. restarting Vegas
. restarting Windows
. updating Quicktime (no updates required)
. exiting the Quicktime system tray app
. starting a new project and rendering a single generated media with my settings

I've also tried changing settings in the video tab of the Vegas settings for the render. Some Quicktime settings seem to work (such as Vegas' 100K preset), but I can't see which of my settings are the ones that stop QT from rendering. Here are Vegas' 100K settings that work:

Vegas 100K Quicktime video settings

Here are my settings - what am I missing? Is it significant that the Streaming tab is blank? Is that normal?

My Quicktime video settings

Thanks in advance for any solutions, advice, tips, procedures, rituals, superstitions - anything that will let me render with these settings! It used to work!



Skevos Mavros
mavart@mavart.com
http://www.mavart.com

P.S. For those that noticed the "farting" reference in the first screen shot, I'm actually editing vox pops of people telling us when they first openly farted in front of their wives/husbands/partners. Yes, the crew actually asked that question, and almost everybody answered it, and now I'm editing those answers.

The things we do...

Comments

Skevos_Mavros wrote on 10/23/2003, 7:53 AM
To answer my own question... Since no one else did... :-)

Hmm, looks like it was the 12.5 frames per second setting. Seems there are some combinations of frame size that don't work with the 12.5fps setting, though I'm still experimenting.

Is this a Quicktime issue or a Vegas issue? Will need to keep twiddling.
Sid_Phillips wrote on 10/23/2003, 10:50 AM
Skevos:

Any particular you're rendering to 12.5 fps? Why not just 12 or 13?
thrillcat wrote on 10/23/2003, 1:05 PM
Judging by the term "vox pops," I'd venture to guess he's rendering PAL, of which 12.5 fps would be the NTSC equivalent to 15 fps...
Skevos_Mavros wrote on 10/23/2003, 1:34 PM
thrillcat said:

> Judging by the term "vox pops," I'd
> venture to guess he's rendering PAL,
> of which 12.5 fps would be the NTSC
> equivalent to 15 fps...

Correct. I wanted the frame rate to be half of PAL, but 12fps will do if it works. The odd thing is I'm sure 12.5 used to work! But I don't have time to run a series of tests. It's 4:30am here, and the last segment for tonight is edited and rendered and sent! :-)

And is vox pops peculiar to English and/or Australian speakers? (I'm the latter). Interesting.



Skevos Mavros
mavart@mavart.com
http://www.mavart.com
thrillcat wrote on 10/23/2003, 1:47 PM
Vox Pops is a term that I've only heard from Austrailian crews I've worked with. In America, people tend to call it MOS (Man on the Street) or bytes. Not that MOS is the industry standard, it came out of the news business...but in fact, to alot of people it means Mitigate Out Sound, which can make it quite confusing.

Still, when I read the term Vox Pops, the little voice in my head automatically pronounces it with an accent. ;)