Bizarre proxy phenomenon

JoeAustin wrote on 7/29/2019, 10:37 AM

I have several big video projects underway. Two are in 4K, and proxies were a must. I've encountered something very strange. I was a bit shocked when some of the new timeline clips appeared to be from a previous project. I chose view in media pool from the timeline, and confirmed that I did import the right clips. For a portion of the clips, vegas somehow grabbed the wrong proxy files. Part of this problem is no doubt the idiotic problem with Sony Alpha cameras that restart the clip counter every single time. Thanks Sony. You really need to take a lesson from Panasonic's playbook.

Anyway, I know which project they were from, and deleted the Sfvp0 files from that folder, and assumed VP15 would just rebuild them in the new project. Nope! Still there. I have six drives on the system, and they could be elsewhere, but I thought Vegas kept proxies to the same folder as source videos?

I tried swap, and no good. Any other way to force a rebuild? Or to confirm within VP where the proxy is?

 

 

 

 

Comments

Musicvid wrote on 7/29/2019, 10:41 AM

Which Vegas version? This one hasnt shown up in some time.

You might have to ditch the project and start fresh.

It's still best to store only one project and assets per folder.

JoeAustin wrote on 7/29/2019, 10:57 AM

VP15

And to clarify, each project IS in its own folder, and the media from each camera it a separate sub folder.

 

j-v wrote on 7/29/2019, 11:18 AM

...., and deleted the Sfvp0 files from that folder, and assumed VP15 would just rebuild them in the new project. Nope! Still there. I have six drives on the system, and they could be elsewhere, but I thought Vegas kept proxies to the same folder as source videos?

Yess, each videofile in a seperate folder and from another project will make its own swap0 file aside of the source file in its own folder, also if there is a swap0 file of exactly the same sourcevideo in another folder.
I tested this and if you don't believe I can try to show you.

 

Last changed by j-v on 7/29/2019, 11:19 AM, changed a total of 1 times.

met vriendelijke groet
Jan

Camera : Pan X900, GoPro Hero7 Hero Black, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W10, i7 7900 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home, version 1903 build 18.362,295 CPU i7 7700HQ, 16 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 15,16,17 and VMS PL 15,16 are installed
Both Nvidia GPU's have driver version 431.86 Studio Drivers
TV      :LG 4K 55EG960V

Dutch video tutorials for beginners

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

john_dennis wrote on 7/29/2019, 12:14 PM

Warning! Warning! Warning!

This may be considered heavy-handed, but just before you start the project fresh, try this FAQ.

JoeAustin wrote on 7/29/2019, 12:28 PM

@john_dennis

You know, as it took the same measure to fix other Vegas strangeness on more than one occasion, this sounds like it's worth trying. Especially if it saves the time cost of building new proxies.
 

Thanks John.

 

Thanks John.

 

Howard-Vigorita wrote on 7/29/2019, 9:32 PM

I think you got it right. The proxy is in the same folder as the media, same name+'.sfvp0'. You might have the wrong folder. If you right-click on the media in the media bin, the path is on the 1st line of the properties screen.

Laptop: Dell XPS15-9570; i7-8750h 32gb (integrated Intel UHD-630 & Nvidia GTX-1050Ti)
Road: Intel NUC i7 8809g 32gb (integrated AMD VegaM 4gb graphics and Intel HD630)
Workstation: i9 9900k 32 gb (Sapphire AMD Radeon VII 16gb graphics and integrated Intel UHD630)
Workstation2: e5 1650v4 128 gb (Sapphire Nitro+ RX580 8gb graphics)
Workstation3: i7-980X 24gb (Sapphire RX480 4gb graphics)
currently Vegas 16, testing Vegas 17