I'm neck deep in a pretty large project for a local Non-Profit. The client supports adults with developmental disabilities and I'm getting towards the tail end of acquisition of the content I need to start editing.
As most regulars know, I've gone back and forth with trying to use Vegas Pro in its various iterations with little success on the stability front and have resorted to doing my paid work with PPro CS6 but the program is getting a little long in the tooth and given I'm not willing to pony up to Adobe's Ransomware, It's also started giving me problems with randomly corrupting project files and if it weren't for the auto save feature, I'd be in serious trouble due to some of the recent short deadlines I've been facing on some of my projects. But I've stuck with CS6 only because I know it the most. Having said that, the last couple of very small projects I've edited with VP13 v453 have worked well. These projects were mostly audio slideshows and working with the audio was a joy in VP13 compared to Adobe's tools.
Having said that, this current project is pretty large with separate sections for each of the 4 areas the Non-Profit does within their organization. I'm use to working with multiple sequences within PPro and given that Vegas Pro works on a per project basis I'm looking for advice on managing assets, separate timelines or "sequences" and getting the very best I can out of my footage. Material is being acquired via Olympus EM5 MkI Mirrorless cameras (which shoots a fairly compressed AVCHD codec) with dual sync audio recorded to my Tascam DR-05 audio recorder. I'm using PluralEyes 3.5 to sync all interview material first before doing anything else and renaming clips outside of any NLE. I normally do this when I've edited in PPro and it's worked well so far in managing larger type projects.
Now that you know the background - what's the "best" way to manage/organize a project of this scope to edit with Vegas Pro? I dread the idea of using PPro given how much audio is entailed on this project, and given the recent challenges of corrupt project files (in addition to eating up system resources) but I do know how it works pretty well but I'd prefer not using if at all possible.
Maybe I can get it right this time around with Vegas Pro...
TIA,
Cliff
As most regulars know, I've gone back and forth with trying to use Vegas Pro in its various iterations with little success on the stability front and have resorted to doing my paid work with PPro CS6 but the program is getting a little long in the tooth and given I'm not willing to pony up to Adobe's Ransomware, It's also started giving me problems with randomly corrupting project files and if it weren't for the auto save feature, I'd be in serious trouble due to some of the recent short deadlines I've been facing on some of my projects. But I've stuck with CS6 only because I know it the most. Having said that, the last couple of very small projects I've edited with VP13 v453 have worked well. These projects were mostly audio slideshows and working with the audio was a joy in VP13 compared to Adobe's tools.
Having said that, this current project is pretty large with separate sections for each of the 4 areas the Non-Profit does within their organization. I'm use to working with multiple sequences within PPro and given that Vegas Pro works on a per project basis I'm looking for advice on managing assets, separate timelines or "sequences" and getting the very best I can out of my footage. Material is being acquired via Olympus EM5 MkI Mirrorless cameras (which shoots a fairly compressed AVCHD codec) with dual sync audio recorded to my Tascam DR-05 audio recorder. I'm using PluralEyes 3.5 to sync all interview material first before doing anything else and renaming clips outside of any NLE. I normally do this when I've edited in PPro and it's worked well so far in managing larger type projects.
Now that you know the background - what's the "best" way to manage/organize a project of this scope to edit with Vegas Pro? I dread the idea of using PPro given how much audio is entailed on this project, and given the recent challenges of corrupt project files (in addition to eating up system resources) but I do know how it works pretty well but I'd prefer not using if at all possible.
Maybe I can get it right this time around with Vegas Pro...
TIA,
Cliff