I don't think this sounds like an Ult. S problem to me. I would be more inclined to think that it's along the lines of a problem either loading or rendering one of your files.

Can you put more details into how the render fails?

Have you tried rendering the file that fails by it self?

Unless you're getting an error message regarding Ultimate S, I am suspect of whether it's actually Ult. S causing the problem.

But most definitely contact VASST.
ultimatesupport<a/t>vasst<d/0/t>com

That's their tech support email. ( with obvious adjustments for abbreviations ).

Dave

I have had the same problem using Sony's built in batch render script. I think it's a vegas problem.

rocky

The files render fine by themselves, and the first file always fully completes it's render and then Vegas crashes hard.

Does anyone know of any batch render tools that actually with Vegas 10?

bigrock,

can you please give us more details as to what is happening...

please answer the following questions:

What file types are you trying to render?
What formats are you rendering from?
What formats are you rendering to?
What is the length of the render?
What is the crash message that you receive?
Have you tried using the built in Vegas batch render tool?

This kind of information is very helpful when trying to help you.

I have used Ultimate S pro batch render and Vegas Pro 10 w/o problems, which makes me inclined to believe that this issue is specific to what you're trying to do. Perhaps system resources are being taxed during a batch render and Vegas isn't handling it well? I really have no idea, and no-one really will, until we can get a look at the information that I requested in this thread.

Thank you.

Also, are these system specs still accurate?

System #1
Windows Version: XP
RAM: 512mb - 1gb
Processor: Intel Pentium 4, 3gHz
Video Card: Nvidia 6800GT (ASUS)
Sound Card: Creative Labs Audigy 2 ZS
Video Capture: http://bigrockies.com
CD Burner: Pioneer
DVD Burner: Pioneer
Camera: Sony HC-3

Vasst is a big time bug with vegas 10. Surprised more have not noticed, Vasst crashes on me at least 3 times a day taking Vegas with it. I work with Vegas 8 hrs every day. Luckily there is a workaround that works for me and may for you. Make sure external monitor button is off when using Vegas before using the vasst plug and no more crash. This is the buggiest Vegas version I've ever experienced. Suprised version D hasn't hit dload.

> Vasst is a big time bug with vegas 10. Surprised more have not noticed, Vasst crashes on me at least 3 times a day taking Vegas with it

This is the first I'm hearing of any problems. Did you contact us (VASST) about it? If you don't contact us, we can't help you. We would be happy to try and recreate any problems that you may be having and fix them if it's with our software. But first, you have to tell us about them.

~jr

VASST

> I am trying to render 16 veg files in Vegas 10 Pro using the Ultimate S 4 Render function to automate the process. It renders the first one correctly and then Vegas crashes everytime. Matters not whether I am 32 or 64 bit. Latest versions of Vegas and Ultimate S are installed.
> Ideas?

Well... my first idea is to contact us at VASST and see if we can recreate the problem. Only then can we try and uncover what might be causing this. It is probably fastest to work directly with us via email so that we can perhaps get copies of your project files and recreate the problem in house.

~jr

VASST

Bigrock, I get exactly the same behavior using the built in batch render script. The first file renders fine and then vegas hangs. All the renders work fine when run manually.

rocky

I think I may have solved the problem. The crash seemed to be related to an api call from Vegas to the sound drivers. I reloaded those drivers and rebooted. So far I have done a single veg render in the Ultimate S Render Tab, and a two Veg render. Both worked fine.

So I have queued up 17 different vegs and it is running the renders now. We will see how it performs but I am optimistic it will be successful.

Vaast guys I would have contacted y'all but my account was locked out (which has been corrected now by your staff). Looks like we might be ok which will save me some time.

> Vaast guys I would have contacted y'all but my account was locked out (which has been corrected now by your staff). Looks like we might be ok which will save me some time.

Glad you got it figured out. You can always send an email to ultimatesupport (which is documented in the Readme file and User's Guide and the About Box) and we will answer your email regardless of your account access. We're here to help. ;-)

~jr

VASST

The queue of 17 veg renders completed without issue. The problem is fixed.