Can't open project between two computers

Dalton-Shotwell wrote on 6/9/2021, 1:05 PM

I run my version of Vegas Pro 16.0 on my desktop and my laptop. I have an external SSD hard drive with my video project on it. I began the project while it was plugged into my desktop then saved my work. Then I transferred the SSD drive to my laptop and was able to open up and load the same video project, no problem. I made one quick edit command on my timeline and saved it. Then I transferred my SSD with project back to my desktop, and now I am unable to load the project anymore on my desktop version of Vegas Pro. Instead I get a message that says 'an error occurred while loading the project file Show 1.veg. An error occurred reading the file. Make sure you have read access to the file/folder and that it is not corrupted.' This happens with any project I try to move between the two computers. What is going on here?
Been using 16.0 on both my machines for a while and they work great individually. I only encounter a problem when I am trying to take a project from one computer to the other - again, using an external SSD to hold all my project media/info. I was able to load on my laptop from my desktop, but projects won't load once I try to go back to my desktop after saving on my laptop.

Comments

Musicvid wrote on 6/9/2021, 1:33 PM

Load your *.veg.bak file by renaming it to *.veg

That's usually all it takes.

Former user wrote on 6/9/2021, 2:26 PM

I wonder if it has anything to do with where temp files are being saved on each computer? Just a thought.

studio-4 wrote on 6/16/2021, 7:01 PM

I'm about to have a similar workflow (i.e., desktop + laptop + portable SSD). I wonder if that did the trick?

asus laptop system specifications:
Asus 17.3" Republic of Gamers Strix G17 model: 77H0ROG1.
Ryzen 9 5900HX 3.3GHz (4.6GHz boost), eight-core CPU.
Nvidia GeForce RTX 3060 (6GB GDDR6).
32GB Crucial 3200MHz DDR4 (x2 16GB 120-pin SO-DIMMs).
512GB M.2 NMVe PCIe SSD (available second M.2 slot).

OS: installed on 7/1/2021:
Windows 10 Home 64-bit; OS version 20H2; build 19042.1052.
Windows Feature Experience Pack 120.2212.2020.0.

asus laptop installed applications:
Vegas Movie Studio 17 Platinum; version 17.0 (build 221); purchased via download 29 May 2021.
Microsoft Edge (default browser; no plug-ins).

asus laptop OpenFX add-ons:
BorisFX Continuum 2021.5 (subscription).
NewBlue Elements 3 Overlay.

HP desktop system specifications:
HP Z440 Intel Xeon E5-1650 v3 3.5GHz (4GHz-boost), quad-core CPU.
32GB DDR4 ECC RAM.
1TB SATA SSD.
AMD Radeon RX470 4GB
AMD Radeon R7200.

OS:
Windows 10 Pro 64-bit; OS version 20H2; build 19042.985.
Windows Feature Experience Pack 120.2212.2020.0.

HP desktop installed applications:
Vegas Movie Studio 17 Platinum; version 17.0 (build 221); purchased via download 29 May 2021.
Blackmagic Design Media Express 2.3 for Windows 10.
WinDV 1.2.3.
Microsoft Edge (default browser; no plug-ins).

HP desktop OpenFX add-ons:
FXhome Ignite Advanced VFX pack.
BorisFX' Stylize Unit 2020.5.
NewBlue Elements 3 Overlay.

cameras/VTRs:



Sony NEX-FS100 Super35 1080p24/50/60 digital-cine camera.
Sony NEX-FS700 Super35 1080p24/50/60/240/960 high-speed digital-cine camera.
Sony NEX-5R APS-C 1080p60 cameras (x3).
Sony DSR450WSL 2/3" 480p24 16:9 DVCAM camera.
Sony VX1000 1/3" 480i60 4:3 miniDV camera.
Sony DSR11 DVCAM VTR.

personal websites:

YouTube channel: modularfilms

photography/iighting website: http://lightbasics.com/

Video_flaneur wrote on 6/16/2021, 10:05 PM

Windows 10 can create a problem with certain laptops when swapping an external drive between computers, as I have learnt the VERY hard way. Some laptops are configured to save current configuration info to disc to enable fast startup. If the disc is removed (even after after a full shutdown) and returns from as second computer which has attempted to do the same thing then certain files become unreadable. The workaround going forward is to go to Windows settings on both computers and hidden under power management settings disable 'fast startup" but that does not recover the corrupted files.

This possibly is not the problem you are experiencing, but I post it as a warning to others who may lose hundreds of hours work through using external discs between several computers.

Laptop: Surface Pro 6: Windows 11 Pro Version 23H2, Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz   2.11 GHzIntel(R) Core(TM) i7-8650U CPU @ 1.90GHz   2.11 GHz; 16GB RAM, 1TB internal SSD
2 external monitors, 5TB external drive, wireless keyboard and mouse

(planning to upgrade to a more powerful graphics laptop when cashflows allow)

Vegas Pro 22 (Build 239); Vegasaur Toolkit 4.0.1; ProDad Mercall v.4; HitFilm Pro Version 2021.1; Acid Pro 11; Sound Forge Pro 18;

Colin-Kemp wrote on 10/26/2021, 10:30 AM

Desktop and Laptop using .veg files on a Synology NAS

 

When I save a .veg project to my NAS from my laptop, if I try to open that file from my Desktop I receive the following error:

"An error occurred reading the file. Make sure you have read access for the file/folder and that it is not corrupted"

 

I can still open the laptop created .veg file just fine from the laptop from the NAS location.

 

When I do the reverse, (create the .veg file on my desktop and save it on the NAS) I can open it just fine from the laptop.

I've played around with permissions but I am not able to get this working -- does anyone have a solution? This scares me as I feel if this laptop dies I lose access to all the projects I had created on it since I cannot seem to open the .veg files on the desktop PC.

I did just check and the Desktop is running Vegas 16.0 Build 307 and the laptop is running Vegas 16.0 build 424.

Is the issue potentially an incompatibility between 16.307 and 16.424 which has an unfortunate/misleading external error message?

Would 19.0 likely be able to open these files?

RogerS wrote on 10/26/2021, 11:09 AM

I doubt there is any difference between 16.424 and 16.307 but I would update the desktop to 424 regardless. Login to your Magix account and download it.

19 should be able to open any VP 16 project assuming the Fx used are available in 19 as well. Not saying this will solve your issue- sounds more like something with network permissions and access but that's beyond my experience.

Last changed by RogerS on 10/26/2021, 11:11 AM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.239

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7