Permanently building peaks

Piotr-Diszer wrote on 8/23/2021, 5:16 AM

Welcome. I have my projects and files on the file server. I use this server on two computers: work and home. after opening the project, instead of being ready to work, I have to wait several minutes for Building Peaks each time - so the kakby would be created on the computer and not on the file server. how to force Building Peaks site on portable file server? Interestingly, there are SFK files on the server - maybe the access path is broken?

Camera: Sony A7S3 4K - 50p 150 mB/s, Sony A7S 1080 / 50P, Panasonic GH5 4K / 50p, Panasonic GX80 HD / 50p, Gopro 8 4K 50p, Gopro9 4K / 50p, Mavic DJI Mini PRO 4K / 50p. Computer A: Microsoft Windows 11 Pro, Intel i7-9700K CPU @ 3.60GHz, Asrock Z390 Pro4, RAM 32GB, SSD NVMe M.2 Kingston 1TB, GTX1660i. Driver Nvidia Studio 531.41. Computer B: Microsoft Windows 10 Pro, Intel i7 4770, Ram DDR 3 32GB, Asus Z87A, Nvidia Geforce 1660Ti, SSD Adata 1TB.

Comments

RogerS wrote on 8/23/2021, 6:10 AM

If there is an sfk file in the folder where the media is, Vegas should use it automatically.

Piotr-Diszer wrote on 8/23/2021, 6:27 AM

This is also what I assumed when working on the project in two places - that all the necessary files are ready for immediate work on the project. But it's not like that. I have several folders with files because I work with film material from several cameras. After starting Vegas, the program continually rebuilds SKF audio for the video of one of the cameras, even though they are in its folder. as usual, the tech support from wVegas developers is in a mess - they registered my request, but for a week with no answer, it always ends with a collision with an iceberg. It's a pity - you can improve Vegas together. Are you also facing such a lack of dialogue from Vegas? Am I asking really too difficult questions in the era of moon and mars exploration?

Camera: Sony A7S3 4K - 50p 150 mB/s, Sony A7S 1080 / 50P, Panasonic GH5 4K / 50p, Panasonic GX80 HD / 50p, Gopro 8 4K 50p, Gopro9 4K / 50p, Mavic DJI Mini PRO 4K / 50p. Computer A: Microsoft Windows 11 Pro, Intel i7-9700K CPU @ 3.60GHz, Asrock Z390 Pro4, RAM 32GB, SSD NVMe M.2 Kingston 1TB, GTX1660i. Driver Nvidia Studio 531.41. Computer B: Microsoft Windows 10 Pro, Intel i7 4770, Ram DDR 3 32GB, Asus Z87A, Nvidia Geforce 1660Ti, SSD Adata 1TB.

EricLNZ wrote on 8/23/2021, 6:34 AM

My experience is that the sfk are only rebuilt if Vegas identifies a change?

Piotr-Diszer wrote on 8/23/2021, 6:38 AM

Thank you Eric, what's the change? The files are the same all the time, the disk is the same, the project is the same - only a server with files connected to another computer. With the computer at home, the project opens immediately. In my office computer, I have to wait 15-25 minutes for the project to be drafted by SFK. What could it be?

Camera: Sony A7S3 4K - 50p 150 mB/s, Sony A7S 1080 / 50P, Panasonic GH5 4K / 50p, Panasonic GX80 HD / 50p, Gopro 8 4K 50p, Gopro9 4K / 50p, Mavic DJI Mini PRO 4K / 50p. Computer A: Microsoft Windows 11 Pro, Intel i7-9700K CPU @ 3.60GHz, Asrock Z390 Pro4, RAM 32GB, SSD NVMe M.2 Kingston 1TB, GTX1660i. Driver Nvidia Studio 531.41. Computer B: Microsoft Windows 10 Pro, Intel i7 4770, Ram DDR 3 32GB, Asus Z87A, Nvidia Geforce 1660Ti, SSD Adata 1TB.

Dexcon wrote on 8/23/2021, 6:40 AM

I tend to agree with @Piotr-Diszer with rebuilding peaks. After getting VP19, I opened a VP18 .veg project to see how it would go in 19. It took ages for the project to open because VP19 rebuilt the entire (and lengthy) project's peaks even though everything being opened was in the very same project folders as used in VP18 with already existing SFK files. The project was not saved in VP19, but when subsequently opening the very same .veg project back in VP18, the peaks were built yet again.

In my experience, it's long been an issue that Vegas Pro (over many versions) that VP occasionally and randomly decides its necessary to rebuild peaks even though everything was fine when the project was last opened maybe only hours beforehand. Why it does that is inexplicable.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

RogerS wrote on 8/23/2021, 7:04 AM

I just opened old project created on a different computer in VP 12 and then 15 and it never said building peaks once the project was opened. It did take a minute to open the project - is it building peaks then? There is no message to that effect.

EricLNZ wrote on 8/23/2021, 7:16 AM

is it building peaks then?

@RogerS Have a look at the date/time of the sfk files creation and that should tell you.

 

Dexcon wrote on 8/23/2021, 7:17 AM

... is it building peaks then?

The way that I've seen that peaks are being built is in the progress bar in the bottom LH corner of VP - after loading the project, it then goes through a progress advice of "xx% of [event name]" for each event.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 20, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

RogerS wrote on 8/23/2021, 7:28 AM

Why didn't I think of that Eric : ) Okay, looking at the folder the newest .sfk is from 2017. My experience is the same as Dexcon- once the project is open it goes through and rebuilds them a file at a time.

So in 4 separate old projects created in VP 12, 15 and 17, where all the media and sfk files were stored together, VP 19 did not rebuild any peaks.

The mystery deepens.

Piotr-Diszer wrote on 8/23/2021, 7:35 AM

In my opinion, the date of the SFK files should be the project creation date, not its subsequent modification. After all, the date does not make sense, the decision of the Vegas program to associate SFK files with a video file should be made according to the access path excluding the date. And the Vegas user shouldn't worry about it at all - it should be a slot machine. vegas overwrites SFk files or saves them in some sfoim temporary folder? why such a complication - once the SFK was created, the access path and END OF THE SUBJECT. It should work but not.

Camera: Sony A7S3 4K - 50p 150 mB/s, Sony A7S 1080 / 50P, Panasonic GH5 4K / 50p, Panasonic GX80 HD / 50p, Gopro 8 4K 50p, Gopro9 4K / 50p, Mavic DJI Mini PRO 4K / 50p. Computer A: Microsoft Windows 11 Pro, Intel i7-9700K CPU @ 3.60GHz, Asrock Z390 Pro4, RAM 32GB, SSD NVMe M.2 Kingston 1TB, GTX1660i. Driver Nvidia Studio 531.41. Computer B: Microsoft Windows 10 Pro, Intel i7 4770, Ram DDR 3 32GB, Asus Z87A, Nvidia Geforce 1660Ti, SSD Adata 1TB.

RogerS wrote on 8/23/2021, 7:51 AM

That's how it appears to work here using external hard drives- created once when the media is first added to timeline and then stored with the media.

Is something different about network drives? Do your locally-stored SFK files also get rebuilt when you open a project? Did you rename the video files?

Marco. wrote on 8/23/2021, 8:10 AM

Also, you could check if these two settings of the internal preferences are still set to default (it's unlike they are not but ...).