[Blake Gibson]

Thanks Wayne, That sounds handy I didn’t even know that was an option. I always go from Vegas to DNXHD then to Handbrake for web upload. Going straight from Vegas to Handbrake would be great.

[Blake Gibson]

Thanks for the replies guys!

Wayne Waag, thank you for bringing this up. Can I ask exactly what Debug Frameserver is and does?

Will all the scripts and plugins still work on version 13 as per normal? (Business as usual for version 13??) As in, will it still be Sony Vegas Pro 13 and not Vegas Pro 13? I do have a script I use sometimes that a guy on this forum shared with me to create markers on my timeline and another to batch export the clips as individual files (eg: importing 100’s of prores files causes vegas to crash due to the 32bit 2gb limit of the filesurrogate.exe – I can safely edit up to around 50 files, so I import them into vegas, 50 clips at a time and use the scripts to batch export them as cineform so I can re-import the 100’s of now cineform files and edit them properly)

I also use some plugns, mainly only use Magic Bullet Looks (for LUTS) and FilmConvert (for exposure and white balance), but there are potentially other OFX plugins that I might use.

I’m OK with using Vegas Pro 13 until the issues with 14 are ironed out, as I’m currently on version 12, 13 will be a welcome upgrade and step up anyway as long as everything works.

Thanks so much!!

[Blake Gibson]

[John Rofrano] “Yea, it’s extremely unfortunate that after a short period of time you can no longer edit your posts because I realized after that it doesn’t work but now that post is out there with bad information. :(“

Oh, right. So do you know what the story is then? Do we just not use the player and disable all browser plugins and hope for the best?

[Blake Gibson]

[John Rofrano] “It’s hard to say. There was a time when the ProRes decoder was a separate download and now it’s included so if you have that separate decoder installed, it could be causing the problem but you would think that the new installer would look for it and remove it? The whole “uninstall QuickTime” nonsense as done a lot of damage to people who blindly followed it. Sorry to hear you got caught up in it.”

Yeah I’ll look for a way to uninstall it this week at some stage.

I think the issue, for me at least, was how vague it was. There was no real exact “this is what causes the problem” that I saw or that anyone could explain. I read to just uninstall the player and that’s where my issues started.

Actually, I read you posted in another thread to just renamed the executable player file in the program files folder right? I did that and I could no longer open prores files, I had to reinstall quicktime for it to work.

[Blake Gibson]

Thanks John.

Do you think it’s because 7.79 comes with the Prores decoder and I have the prores decoder already installed? I can’t think of why it wouldn’t work for me. Even though I have the prores decoder I can’t find it to uninstall to test my theory. I would much prefer the newest quicktime than one that’s like 7 years old.

[Blake Gibson]

OK so I just installed and even earlier version of Quicktime – 7.6.92.0 and it worked!

Everything appears to be back to normal… it must have been 7.6 I initially used two years ago… Which makes sense because the next version, 7.76 was released in Oct 2014, but I initially installed it in Jan 2014 and 7.6 was released in 2009 with nothing until 7.76 in Oct 2014. I read that 7.76 comes with the prores decoder 1.0 and earlier didn’t which explains why I vaguely remember having to install it… but that doesn’t explain why newer version of Quicktime didn’t work…

So it works… but does anyone know why newer versions aren’t working? Should they?

[Blake Gibson]

Thanks guys, worked like a charm.

[Blake Gibson]

Hi Wayne, thanks for the response. I’ll try it tonight.

It was filmed in SD 640×480

[Blake Gibson]

Just an update, everything went really smoothly up until right at the very end, I would have to keep opening the project and crossing my fingers until it worked because i was getting some weird hardware/video card/open GL error (i don’t have the error on hand), even though it wasn’t actived in Vegas anywhere. It would throw up that error message then just close vegas, I managed to get it open a couple of times, it didn’t happen on any other project when i was troubleshooting.

I figured it was because of the FX I was using (twixtor mainly on some shots)But it eventually openeded up and I exported to DNXHD 185 10bit, which was slow but wen’t through without any dramas, as in the file surrogate was LOW and didn’t struggle at all.

Thanks for all the help!

[Blake Gibson]

Yep that’s what I ended up doing, thanks!

By the way, I did a few test exports to DNXHD and they worked fine, the file surrogate didn’t flinch and stayed at about 70mb. Weird, but I’m not complaining.