That error is almost always tied to your Quicktime installation. Do a search on these Sony forums..

Why can't a SCS engineer help with this? Is it my external drive speed? Is it a driver update? Clearly, I am not the only one having these problems and it is unacceptable that they won't help. Is is a program? A microsoft update? Is there a trick to correct it? How can Vegas be a "professional" software when so many of us long time users are suffering this problem? I have a client that wants only HD mov files and the DNxHD was a perfect fit. I cant' render anything QT and I love Vegas...it's really frustrating.

Cool your pipes. I understand your frustration, but this is not necessarily Vegas' fault.

Sony and Apple are competitors. Sony can't possibly keep up with everything Quicktime does to break its proprietary libs with Windows NLE systems. It's not just Vegas. That's why we all cooperate and try to come up with and share workarounds. The history of these repeated issues go back to 2009. Again, the search tool on these forums will enlighten and entertain.

BTW, did you try 7.6.2 yet?

Please don't mistake my rant as a stab at you or anyone else on these forums. I am a Sony Acid Pro user as well and feel completely abandoned by SCS, as do thousands of other Acid users, so when I rant on SCS, there is a back story.

I appreciate all of the support I get here. I did try 7.6.2. I also removed VP12 and reinstalled 11 and was able to render out to a DNxHD. Then I created a new user account and reinstalled 12 and it did not work and now the 11 doesn't render DNxHD. I removed all traces of 12, but it didn't help. I did render out a 30 sec spot to avi and rendered a mp4 on handbrake and uploaded it to my clients FTP. I am yet to hear how it looks.

I removed all traces of 12, but it didn't help

Here I had to reinstall V11as well.

Edit: ... after removal of the V12.

That's a lot of questions. The questions about SCS support...as far as I can tell it doesn't exist. If you need support you could try paying for it but given people's experience with free support I'd say if you *need* support then SCS products aren't a good choice. User-to-user forums are your best bet for lucky and/or informed guesswork.

Does SCS listen to support requests/product suggestions/bug reports? The answer seems to be Yes if you look at the readme files when new revisions come out. But their support is useless. While I suggest you always make support requests because they probably get counted, don't expect an answer. That way SCS can only meet or exceed your expectations.

So, how to deliver quicktime files to your client if Vegas can't encode them? You might need to try a two-step process. You could use the DebugMode Frameserver to make an AVI signpost file and then use a third party application to make the Quicktime file. Or you could render an intermediate out of Vegas and then do the same thing. If the Frameserver would work then that should be better, faster, and not use up disk space.

Rob

<edit>I just tried the Frameserver route but QuicktimePro couldn't do much with the AVI signpost file, at least within the 10 minutes I was willing to devote to it. The next option would be to find a decent intermediate that Quicktime can open and then render the DNxHD file straight out of Quicktime. Of course it'd be best if you could render the mov file straight outta Vegas...</edit>

Ritsmer, could you send me a copy of IOSurrogate from your working Vegas 11? I'd like to try something. My username at gmail will work.

Just had a look at Windows Task manager:

The module in use is FileIOSurrogate.exe *32
and it is started from C:\Program Files\Sony\Vegas Pro 12.0\x86
and taking up 31.708 K of memory.

Its version number is: 12.0.0.563.

I do not say if FileIOSurrogate was the source to my hangs and crashes but my experience was that after installing V12 I immediately got troubles with my good old reliable V11.
Un-installing V12 did not help.
Then I re-installed V11 and everything worked again.

Then -as a wild guess- I re-installed V12 (giving troubles again) and thereafter I reinstalled V11 once more giving a stable V11 AND a totally stable and reliable V12 too.
Have been using V12 for more than a month and a half after that - and not even got slight hiccup.

Other data: GPU assist=OFF, Max render threads 5 or 6 and Preview RAM 22 MB.

Have just mailed the file to you.
Edit: mails keep coming back - with and without 10 - pls pm me via my user profile so that I get the correct address.

Woops I forgot I changed my forum user name.
musicvid "at" gmail.

I just tried ritsmer's process, removed both 12 and 11, reinstalled 11 and changed the render settings to GPU - off and max threads 5 and preview 22 and DAMN if it didn't work. It was slower, of course, but I was able to render this project out to DNxHD. I even tried it twice to make sure it wasn't a fluke and it worked. I am afraid to reload 12. Is it still stable for you ritsmer?

@musicvid: got another "return to sender" :- ) from gmail - might be the dll needs to be renamed - but I hope that the other address works?

@Weldon: Yes - I have used it for more than a month and a half now.
If you reinstall V12 now troubles might return - but then just reinstall V11 and it works nicely again.

Btw: SCS support said about this:
“Our applications share some resources, including plug-ins and codecs. In this case, it is possible that reinstalling Vegas Pro 11 32-bit refreshed some of those resources for all three versions of Vegas Pro, especially if that was the first version you installed on the computer. It's also possible that another graphics utility needed a chance to update or reset.”

Once upon a time we could assume that versions of Vegas could coexist with each other. Seems like that's not the case, at least going back to VP10.

I had a similar problem with the Wacom tablet issue a year or two ago. I'd get crashing in VP11 and VP10. Uninstalling both and then reinstalling would fix one or the other but I think this was a case of VP11 affecting VP10. Anyway, it's another thing to look out for.

Rob

+1 comment made by rmack350 just above in thread.

Generally I operate a studio network on the basis of having VegasPro versions installed on seperated machines. Hence I have not experienced these issues first hand. But from all the comments I have seen over the years in this forum, I believe the comment he makes is right on.

There was a time in the development cycle of SCS that different builds and different versions were carefully managed to allow flow and overlap without issue. What happened with Version 10 development and subsequently it appears there has been so much experimenting and code manipulation that SCS is no longer able to give this smooth upgrade routing.

It was probably a miracle that Vegas versions didn't foul each other, but certain types of problems started with custom dialog windows like the OFX filter dialogs and, in VP12, the new Vegas Explorer window. In the VP11/VP10 example it was an issue of Wacom drivers crashing the OFX dialogs of VP11, and it bleeding over to VP10 because it also used OFX filter dialogs.

Anyway, it's a good idea to keep your Vegas installers and serials at least back to VP10.

In terms of installation order, the computer in front of me has Vegas 10, 11, and 12 (64bit) installed on it in that order. I've not uninstalled one before installing the next. I've not noticed any sort of trouble with Quicktime, and Quicktime is what I primarily use, but it's a relatively simple Raylight DVCProHD codec and I don't render much. Still, it makes me wonder if the problem arises due to uninstalling old versions, or maybe reinstalling old versions in a particular order...?

Einar,
Got it, thanks!