5.0b and Neon

PAW wrote on 6/22/2004, 11:44 PM

Hello Gary,

I am getting an error with Neon after the upgrade to 5.0b

I get an error dialogue of "Object Reference not set to an instance of an object" which is pretty self explanatory ;-)

Anyone else getting this, I recenty had to reinstall Vegas so it may not actually be a Neon problem

Paul

Comments

Grazie wrote on 6/22/2004, 11:49 PM

Paul - Early adopter yeah? Serve yah right!!!

I guess Edward and Gary would have tested these out rigorously . .. You had to reinstall Vegas? Was the reinstall working wth Neon BEFORE your update to 5b?

Grazie

PAW wrote on 6/23/2004, 12:26 AM

Good point, I only did the reinstall a couple of days ago and don't "think" I had used Neon in the meantime.

I have reinstaled Neon as well but still with the same problem - I agree I think they would have seen this if it were a Neon issue but needed to be sure.

Paul

MarkFoley wrote on 6/23/2004, 6:44 AM

Getting the same error here also....

jetdv wrote on 6/23/2004, 8:09 AM

Paul, you need to e-mail me directly. I'll see what I can do to help you out.

jetdv wrote on 6/23/2004, 8:10 AM

I HAVE confirmed the problem with the 5.0b (build 160) release. I believe I have a workaround but you will lose the MPEG2 encoding option.

jetdv wrote on 6/23/2004, 12:34 PM

Vegas 5.0b has definitely introduced a quirk when going through the renderer template names. However, I have found a work-around that will let the original version of Neon work AND let you maintain your MPEG2 presets.

Start Vegas and put anything on the timeline. Go to File - Render As - pick MPEG2 as the format - press "Cancel". Now Neon will run correctly without the error.

jetdv wrote on 6/23/2004, 1:36 PM

Besides the workaround, I do now have a version that will run correctly under Vegas 5.0b AND show the MPEG2 presets.

p@mast3rs wrote on 6/23/2004, 1:39 PM

whats the url for that please?

jetdv wrote on 6/23/2004, 1:43 PM

Please e-mail Gary or me. Until we can get the new version to you, feel free to use the work-around I posted.

PAW wrote on 6/23/2004, 1:44 PM

jetdv sorry to not get back to you sooner, looks like you have worked this through, thanks for the quick response

Paul

Grazie wrote on 6/23/2004, 2:57 PM

Edward! You clever ole STICK! - Well done!

Grazie

johnmeyer wrote on 6/23/2004, 9:17 PM

I also get the same error with the "Batch GUI" script. I can't find a workaround. Is there a script change that will avoid this?

Spot|DSE wrote on 6/23/2004, 10:31 PM

John, rather than using the Batch Render GUI, do you have the Batch Render script showing up on its own? That one is working for me, but the GUI version (looks the same as the Batch Render) doesn't work in 160, but worked in an earlier version.

johnmeyer wrote on 6/24/2004, 7:06 AM

Spot said: John, rather than using the Batch Render GUI, do you have the Batch Render script showing up on its own?

I have just about every script posted on any of the various Vegas sites. I'll see if I can get by with one of the others. I have really come to rely on some of these scripts. so having 5.0b break them was not a good thing.