5.0b breaks scripts

johnmeyer wrote on 6/23/2004, 9:16 PM
In this thread:

5.0b and Neon

users report problems with Neon and 5.0b. They get this error message:

"Error: Object reference not set to an instance of an object."

I am getting the same error message with the "Batch GUI" script adapted from the Sony script of the same name.

It looks like 5.0b has introduced some scripting bugs.

Comments

Tapek wrote on 6/23/2004, 9:29 PM
yeah came across the same thing myself today, i uninstalled b then reintalled a and it works again....will be waiting for a fix before i update the machines here again.
jetdv wrote on 6/25/2004, 7:40 AM
There is a work-around:

Open Vegas, put anything on the timeline, choose "File - Render As", pick the MPEG2 format, press Cancel, and now the scripts should run.

Neon HAS been updated to work around this problem as well.
SonyEPM wrote on 6/25/2004, 8:10 AM
In 5.0b, some batch render scripts can break under certain orders of operation. We'll have a patch available soon, numerous script writers have provided updates to their scripts, there are workarounds.

Non-batch rendering scripts should all be unaffected by this bug (which is related to MPEG templates and is our fault).
johnmeyer wrote on 6/25/2004, 8:57 AM
Open Vegas, put anything on the timeline, choose "File - Render As", pick the MPEG2 format, press Cancel, and now the scripts should run.

I tried this yesterday, but it didn't work with the Batch GUI script.

numerous script writers have provided updates to their scripts, there are workarounds.

Since I write scripts from time to time, I would like to know what updates I could do to make the script work again. I have seen nothing in the script forum that tells me what to do, nor have I seen anything in the release notes. As for workarounds, see my paragraph earlier in this post.
Rosebud wrote on 6/25/2004, 9:34 AM
I tried this yesterday, but it didn't work with the Batch GUI script.

Try with Mpeg1, work for me.
johnmeyer wrote on 6/25/2004, 9:46 AM
I just found some advice over in the scripts forum. I added a try/catch to the enum section of the script to ignore the bad templates and move onto the next template. This solves the problem without having to do a workaround each time.