Comments

Spot|DSE wrote on 7/13/2004, 12:44 PM
You must be somehow either deleting the .sfk files, or changing out drives?
Vegas NEEDS the graphic files for you to see, so it builds the peak files. If you are deleting the .sfks somehow, Vegas will need to redraw them every time you load.

.sfk-Sony Grafik file.
RichMacDonald wrote on 7/13/2004, 1:22 PM
Known but wierd issue.

http://mediasoftware.sonypictures.com/forums/ShowMessage.asp?ForumID=4&MessageID=234084

From Sony:

-----
The problem is that Vegas uses local time format for comparing the .sfk files (value is stored internally in the file) vs. the last modification date for the media file. When you changed your clock, the time stored in the .sfk file no longer matched the file time for the media file, so the peaks file was rebuilt.

Local time is used for validation of the peaks file because legacy win16 did not provide a means for obtaining UTC (it's like GMT). Changing this will be tricky because existing applications would continue to use local time for this validation. We will look into correcting this problem for future application upgrades

------------
That was in Dec 2003. Do a forum search on "sfk" for a full history.
Arco wrote on 7/13/2004, 1:31 PM
Gee, I'm not changing anything, not even shutting down the computer....

e
eheh wrote on 7/13/2004, 6:25 PM
It can happen if the .sfk cannot be written to the folder the video footage is in.
For instance, it can happen if you do not have windows write permissions to the destined folder. The video can be used because it is read only.
SonyTSW wrote on 7/13/2004, 11:20 PM
The peak file regeneration problem mentioned by RichMacDonald was fixed in Vegas 5.0. You should not longer see new peak files being rebuilt when you change your timezone or there is a switch between Daylight and Standard time.

That said, if you do happen to load those media files in an older application (such as Vegas 4.0), it will rebuild the peak files if the clock changed.
Miles-Thatch wrote on 12/2/2023, 11:13 AM

It's nearly 2024 and this is still an issue.

RedRob-CandlelightProdctns wrote on 12/2/2023, 12:09 PM

I've found when I turn on/off legacy decoding, it rebuilds peeks, but only once when I make the toggle. Otherwise it's working OK for me .. can't think of reasons it'd keep doing this, although the permissions theory that @eheh mentioned seems plausible?

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio

 

 

RogerS wrote on 12/3/2023, 9:30 AM

It's nearly 2024 and this is still an issue

I've never seen it (except for changing HEVC decoders), what triggers it for you?

Reyfox wrote on 12/5/2023, 8:42 AM

Another "me too". I've not seen it. I just opened a project with Smartsound music and of course audio with the video clips. No rebuilding of the peeks. Using VP21. I see in your Signature @Miles-Thatch that you are using VP18?

Last changed by Reyfox on 12/5/2023, 8:42 AM, changed a total of 1 times.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.5.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Howard-Vigorita wrote on 12/5/2023, 8:53 AM

I only see it happen when I change decoders in i/o. That's a bug too and if they ever fix it, it'll probably cure the problem all around.

I've also noticed a related quirk. When I change the setting in Windows/System/Display/Graphics for Vegas, it causes a change in the Vegas i/o decoder and all the audio files get rebuilt the next time I open Vegas. And then again when I put the i/o setting back and restart. So maybe the Vegas susceptibility to Windows is the culprit for the bigger problem.