VP16 different builds can't open problem for .veg projects

ram17 wrote on 9/3/2019, 7:32 AM

I had a tag team with 2 studios for a collaborative project, we divide the workloads, we all have the same copy of files & folder structures etc, they send me .veg file materials for trimmed clips & text but when I send back my edited .veg file to the two of them, they can't open mine for them to check.

From what they said, there's an error popping up when opening my project, we have all installed a Vegas 16 but I'm b424 they're both b361. I can open their projects from 361 but they can't open mine from 424. So, can I ask if it's just us or are we missing something here or is it really mandatory to update to the latest build nowadays (if its true then it's annoying especially to collaborate or pass an ongoing/finished work even with the same VP version with different builds) Correct/enlighten me if I'm wrong. Thanks

Comments

j-v wrote on 9/3/2019, 8:21 AM

The last build had 41 new features and bugfixes, so I think it might be possible you did things that were not in 361 or were still bugs in 361. To me it looks very possible that 361 has some problems with vegs made in 424.

rraud wrote on 9/3/2019, 9:03 AM

From what they said, there's an error popping up when opening my project,

I don't suppose the collaborators stated the error message. Ask them to be specific.

ram17 wrote on 9/3/2019, 9:52 AM

@j-v well even just a simple test project I've sent like this with just 2 texts on the timeline from b424 can't be open, so I don't know what changes (aside from stated bug fixes) are implemented in higher builds that would affect even with as simple as this to work in lower builds

ram17 wrote on 9/3/2019, 9:54 AM

@rraud it is like this, tried also launching their VP16 b361 in admin mode but still can't open projects from 424 even simple project just like above

j-v wrote on 9/3/2019, 10:10 AM

That error message said not that Vegas has a problem with the veg, but with reading it at the location where it is placed. So maybe they have to change the place (folder) from where they try to open it.

ram17 wrote on 9/3/2019, 10:26 AM

@j-v thanks for the suggestion but still no luck, they tried to move tests projects (its 5 simple test .veg file with only text involved from b424) for 3 different internal hdd around the pc with b361 & reopen it still same error (launched VP16 normally & in admin mode).

Sylk wrote on 9/4/2019, 6:29 AM

@j-v well even just a simple test project I've sent like this with just 2 texts on the timeline from b424 can't be open, so I don't know what changes (aside from stated bug fixes) are implemented in higher builds that would affect even with as simple as this to work in lower builds

Hi @ram17

First, try rather an empty project.

Next, try to save project to a secondary or external drive instead of your "C:" drive, and send this file.

Dexcon wrote on 9/4/2019, 6:45 AM

@ram17 … surely the obvious answer is for those with b361 to update to b424 - it's free. After all, they've updated from the 3 previous builds of VP 16 to get to b361 if they've purchased VP16 from the original release build.

ram17 wrote on 9/5/2019, 1:04 AM

@Sylk thanks but not working either

ram17 wrote on 9/5/2019, 1:27 AM

@Dexcon well I know it's the only way, so the conclusion here is build updates are COMPULSORY in VP if you're working with others with different builds but same versions. Very different like other NLE softwares like FCPX, PPro, Hitfilm & Resolve. I guess Magix is doing it to push us to use updates, I know updates are good but not all & it is a trial & error, it can mess up a rock solid stability of a software especially for us whose editing is our bread & butter.

Sylk wrote on 9/5/2019, 2:07 AM

@ram17 Not sure that issue is about the different builds. It could be related to the authorized users.

Try this:

Open the file properties from explorer. Security tab. Click "Modify" button

Next window, Click "Add" button

Next, (1) type "everyone" (not sure in english), (2) click "Check name" button, if valid it underline it, (3) click OK

Next, you'll see "Everyone" added in list of users. Be sure it selected and check all "Allow" checkbox.

Apply and close.

Send this file, and pray awaiting feedback.