A few questions re: proxy editing, large video/project, and a weird blac preview screen problem (Windows PC – Vegas Pro 12)

[Blake Gibson]

Not sure how to make a post to threads without replying to someone, just wanted to update so far as someone will eventually have the same issue and be searching:

Did a batch render of all 240 clips to Cineform High from the original prores from vegas in lots of 100 clips each (2 lots of 100 and 1 of 40). Curious to see that some of the Videos didn’t play in Windows Media Player, but still had audio, meanwhile some were fine and played normally. I checked them out in Mediainfo and the ones that didn’t play all had a much lower bitrate than the ones that did: around 30mbps vs 100-120mbps.

I went back and checked a previous batch render I did of Filmscan 2. I checked each of the 240 videos in media info and made sure they played in WMP and everything was fine, consistent bitrates and all played, the only difference is I rendered in lots of 75 instead of 100. Weird. I went back and re-rendered the High batch again, this time in lots of 75 clips, re-checked each clip in mediainfo and made sure they played in WMP and all was fine and all consistent bitrates.

Only explanation I can think of is that even though Vegas appeared to be handling 100 clips fine, it was at the upper limits and struggling (meaning the fileiosurrogate was almost maxed out).. vegas must have just freaked out and weird inconsistencies happened.

Going forward I would do 50 clips at a time max.

[Norman Black]

[Blake Gibson] “I stumbled across this thread in my travels, it looks interesting, this guys basically found an app that lets you use more than 2gb memory on 32bit exe/dll’s… apparently it only works to get around the crashing during render issue in Vegas. I wonder if it would work for the fileiosurrogate.exe:”

Yes, you can try setting the large address aware flag on the executable (fileiosurrogate), for 3GB user space, but you have no idea what the result might be.

Many applications wrongly assume addresses above 0x80000000 (2GB) are system addresses. Even with Sony knows their fileiosurrogate application does not make any such assumptions, they have no idea what assumptions the quicktime code makes. It goes even further. Quicktime has no idea what assumptions the third party codecs, like DNxHD, might make.

It is most likely the case that everyones code does not make any silly assumptions about address range. You can try it, but the millisecond something does not work I would switch it out.

[Blake Gibson]

John, do you think using the smart proxy feature would help at all? I’ve rendered from prores hq to Cineform High and am just about to start editing.

I can always change them to proxies with smart proxy later on anyway can’t I? Don’t have to do that from the beginning?

[John Rofrano]

I thought the proxy feature was introduced in Vegas Pro 13.0 and you are using 12.0. Do you have a proxy option? If so, I think you can turn it on at any time and it should definitely help.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Blake Gibson]

Yeah vegas 12 has smart proxy, right click files in the project media tab and select “create video proxy”:

https://i58.tinypic.com/nl5tz4.jpg

[John Rofrano]

Awesome! I only have Vegas Pro 13.0 on my MacBook Pro so I couldn’t check. I would definitely use proxies to make your editing smoother.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[Blake Gibson]

Everything is going well so far, I’m about half way through a 3 minute video. Had Vegas open all day yesterday for 12 hours and didn’t have any issues. Still working from proxies from the cineform high files. Some clips had “difficult” effects too, EG: Gaussian blur and twixtor on about 10 clips (although I had to turn effects off periodically when doing real time play backs or else it lags). But no issues with crashing, just a lag when undoing a change (ctrl+z)

I’ll update once the whole thing is done.

I have another question though:

You know how you can make an effect globally apply to every clip in the project by dragging and dropping it onto the review window? Is there a way to exclude certain clips in this “global change”? I’ve tried locking the tracks I don’t want the effect applied to but it doesn’t work.

Any ideas?

Edit: I just figured out you can apply effects to individual tracks, so I can make new tracks for the clips I don’t want the effects applied to. I would still like to know if there is a way to exclude certain clips though

Thanks

[John Rofrano]

[Blake Gibson] “You know how you can make an effect globally apply to every clip in the project by dragging and dropping it onto the review window? Is there a way to exclude certain clips in this “global change”? I’ve tried locking the tracks I don’t want the effect applied to but it doesn’t work.”

No. Vegas Pro has the most options for applying FX of any NLE so here’s what you can do:

• Video Bus FX: You can apply FX at the Master Video Bus level and the entire project will have the FX applied.
• Track FX: You can apply FX at the Track level and any event on that track will have the FX applied.
• Event FX: You can apply FX at the Event level and just that event will have the FX applied.
• Media FX: You can apply FX at the Media level and any event that uses that media will have the FX applied.

One way to accomplish what you want is to apply the FX at the Track level and then move the events that you want the FX applied to onto those tracks.

~jr

http://www.johnrofrano.com
http://www.vasst.com

[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.

[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!