VP16 ~ Warning: An error occurred while loading the project file...

Qoncussion wrote on 10/10/2018, 8:31 PM

I have several projects I am working on with multiple video and multiple audio streams in each. Every time I open any project in VP16 I receive two error messages regarding having to rename the "Main Timeline." Does anyone have any clue as to how to fix this? The entirety of all affected projects work fine, have all of their files - none are missing, edit and render perfectly. The error seems like a s/w bug.

Here are screenshots of the two errors. The first one is as it appears, then expanded with more detail.

^^ "Details" vv

ERROR #2

Comments

j-v wrote on 10/11/2018, 4:13 AM

I saw it a lot of times, but the first time I searched for that error but couldn't find anything and afterwards I click OK and go further without a problem.
For the developers: It happened most of the time with nested vegs from HEVC (GoPro) files and is followed a lot of times by the nasty "playback error".

Qoncussion wrote on 10/11/2018, 8:03 AM

I saw it a lot of times, but the first time I searched for that error but couldn't find anything and afterwards I click OK and go further without a problem.
For the developers: It happened most of the time with nested vegs from HEVC (GoPro) files and is followed a lot of times by the nasty "playback error".

My signature at the end of every video is a nested veg. I'll try it with no nesting and see if it goes away Ir doesn't cause any problems - that I can see, but program bugs like this, well, bug me!

j-v wrote on 10/11/2018, 9:23 AM

I think this problem is being caused by one of the new options of Pro 16: Storyboard Bins.
I don't use those storyboards and think I will never use that option but they are produced anyway, at least the one of the "main timeline", that is causing this problem with nested vegs.

I tried, but could not find any possibility, also not in Internal Preferences, to de-activate that storyboard function.

Maybe the Vegas developers can give that internal option in a product update or better to prevent this so-called error.

VEGASDerek wrote on 10/11/2018, 9:36 AM

It is an error we are aware of and should hopefully be gone in the next update. In general, this error is no need for concern.

j-v wrote on 10/11/2018, 9:57 AM

Thanks in advance Derek! 👍👌

In general, this error is no need for concern.

That's why I spoke about "so called"(error), because ignoring does not damage something.

Qoncussion wrote on 10/11/2018, 10:31 AM

It is an error we are aware of and should hopefully be gone in the next update. In general, this error is no need for concern.

Thanks Derek! What's the easiest way to check for new updates? Is there an option in VP16 that will do this?

Kinvermark wrote on 10/11/2018, 12:48 PM

It will get posted in the "News" section here along with release notes. Hopefully quite soon.

NickHope wrote on 10/27/2018, 7:44 AM

@Qoncussion @j-v Is this fixed in VEGAS Pro 16 Update 2 (build 307)?