Hours of work on a Nested Timeline gone because Vegas "Pro" 19 can't find and/or save some streams, whatever that means. The resulting file is simply blank. This half-baked program is killing me. It might be time to start looking at something that is genuinely Pro. Sorry for the rant.
Instead of ranting, you could try asking for help with your issue... perhaps someone here knows how to fix it.
Thanks, but there is no fix. I can see the zero kB files in the folder with the nested timelines. In fact, after restarting Vegas Pro, to be on the safe side, the project cannot even be opened anymore. I had to revert to yesterday's version. Although, that can possibly be fixed by deleting the screwed-up nested timeline files. I'll give that a try, save me this morning's work at least.
Editing is hard enough as it is without having to deal with multiple serious bugs in what seems to be a premature program release.
any .veg.bak backup file exist of these nested project files?
Yes, with the same time stamp. I am too scared to open it.
Ok, try open that Don's first interview fixed into Barnie.VEG.BAK - if you need to, Duplicate first this project file (standard copy-paste file in Windows' File Explorer), so you still have backup.
Just File>Open then go select this .VEG.BAK file.
the .sfk or sfap0 are other required data for project purpose.
I always avoid Nesting in VEGAS. The whole system/functions its not mature enuf in my opinion.
With a nest you can open the individual projects that are nested, no? Make sure all media is online and accessible to Vegas (hard drives are plugged in, not full, etc.)
Neither the Veg nor .bak file are 0KB in your image.
sfap0 files are just proxy ones- you could delete them and have Vegas rebuild from the main project.
For projects that can be easily broken down into sections/chapters then nesting is the way to go. Your learning experiences seem to reflect mine. Note what appears to be going wrong, then follow a few tutorials. Maybe overkill but I created new folder to take 'named' 'nested' veg files. Likewise set up auto saves.
Once through the learning curve you will not look back.
The .sfk files are built when you see VEGAS saying "building peaks for X file". It is the waveform on your audio that you see. The sfap0 files are your proxy files. So, deleting those or losing those doesn't do anything other than make VEGAS create new ones when the project is reloaded. It's the .bak and .veg files that actually contain your projects.
In your fault module shown on the crash report, it lists so4compoundplug.dll as the fault. Try this, go into options and file-i/o tab. Do you see "enable legacy decoding" checked or unchecked? Switch it to whatever it isn't currently for both AVC and HEVC. Usually you never want to touch this (the legacy decoders can't do 10 bit, among other things), but in case of bugs, they leave this option in place to help you work around the problem. If you do have legacy decoders already checked, good chance that also is your problem, because as I said, you usually don't want to use those.
In your fault module shown on the crash report, it lists so4compoundplug.dll as the fault. Try this, go into options and file-i/o tab. Do you see "enable legacy decoding" checked or unchecked? Switch it to whatever it isn't currently for both AVC and HEVC. Usually you never want to touch this (the legacy decoders can't do 10 bit, among other things), but in case of bugs, they leave this option in place to help you work around the problem. If you do have legacy decoders already checked, good chance that also is your problem, because as I said, you usually don't want to use those.
Thanks. I have to deliver tonight and the system runs stable, so I will leave it for the moment. I will just avoid certain things that seemed to have caused issues before and look at changing settings when i am in an experimental mood. This is the fileIO tab, by the way.
Turn off the legacy HEVC decoder, see if that helps. If not, turn both on.
Turn off the legacy HEVC decoder, see if that helps. If not, turn both on.
Turning it off made it worse, but turning both on seems to have done the trick. I couldn't even put more than one dot in the envelope of the audio track and Vegas would crash. Now I can manipulate the volume as I please. The 15 min. movie rendered perfectly. Thanks a ton!