Asuming, we still can't build audio peaks individually...

i3ordo-r wrote on 1/25/2019, 3:51 AM

I have 6 audio tracks, i select and un-group the last one down, do "Rebuild audio Peaks"

BUT...

after many versions of Vegas...

It rebuilds all of them, starting from TOP.

Is this Community dead? Am I really the first person to mention this "oversight"?

Comments

Dexcon wrote on 1/25/2019, 4:25 AM

after many versions of Vegas...Am I really the first person to mention this "oversight"?

This is your first post, yet you've apparently had issues with the audio peaks rebuilding process over many Vegas Pro versions and have not raised the 'oversight' yourself on this forum in the past. Perhaps you are now the first person to raise the issue as others have not considered it as much of a problem as you do.

Is this Community dead?

If it were, the last post on this forum surely would have been weeks/months/years ago.

Nonetheless, making such a seemingly insulting comment is not likely to encourage others on the forum to help you.

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

i3ordo-r wrote on 1/25/2019, 6:04 AM

My intention is not "getting help", I am the one to "help".

Someone will visit this "post" with a similar search like "build selected audio peak" will come to this thread and learn this;

1: Stop "audio peak building" that starts after "video add"

2:Drag the "audio track" that you want to build the peaks for to the "top layer"

3:do "Rebuild audio peaks" and cancel when you get what you need.

Vegas is a program that lets users cross fade, slow/fast regions by dragging the mouse. It is identity is built upon simplicity, practicality.

 

vkmast wrote on 1/25/2019, 6:35 AM

@i3ordo-r thanks for clarifying your point and welcome to the forum.

rraud wrote on 1/25/2019, 10:01 AM

It's usually not necessary to rebuild the wave forms after the initial build (.sfk file). Even if the event is changed with an audio editor, it auto re-builds. I would not consider this an "oversite" .. or even an issue. The waveform rebuild has been the same as far back as I can recall and I am a user since Vegas was audio-only when Sonic Foundry initially released it.

No, this community is not dead, and is rather busy over on the video side and welcome to the community.

john_dennis wrote on 1/25/2019, 10:06 AM

Have you also mentioned this phenomenon to Samsung, Micron or Intel? It seems the way small files are handled on real disks is at the root of your aversion to building audio peaks. If building all peaks was instantaneous, would you still want the Vegas coders to give you selective rebuilding?

If you continue to think about things, you'll fit right in here.

i3ordo-r wrote on 1/25/2019, 7:07 PM

Have you also mentioned this phenomenon to Samsung, Micron or Intel? It seems the way small files are handled on real disks is at the root of your aversion to building audio peaks. If building all peaks was instantaneous, would you still want the Vegas coders to give you selective rebuilding?

If you continue to think about things, you'll fit right in here.


because of the clutter it produces on the same folder of ""source". Why would i want to have 6 SFK files for every video clip that i add? so Yes,

 

 

 

Dexcon wrote on 1/25/2019, 8:25 PM

… 6 SFK files for every video clip that i add ...

That does seem strange - I've never seen more than one .sfk file per video event over the many years that I've been using Vegas Pro (from VP10).

In my experience, VP automatically creates an .sfk file when a video or audio event is added to the timeline which is placed in the folder holding the video or audio event. No matter how many times I add the same event to the timeline, only one .sfk file is created in the relevant folder.

I just tested 'Rebuild Audio Peaks' on a test video event, and a new .sfk file was created, but it over-wrote the previous .sfk file - so there was still only one .sfk file for that event in the folder.

More than one .sfk file per event does not seem right to me - maybe another forum contributor has experienced this and can advise.

 

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

i3ordo-r wrote on 1/25/2019, 8:41 PM

… 6 SFK files for every video clip that i add ...

That does seem strange - I've never seen more than one .sfk file per video event over the many years that I've been using Vegas Pro (from VP10).

In my experience, VP automatically creates an .sfk file when a video or audio event is added to the timeline which is placed in the folder holding the video or audio event. No matter how many times I add the same event to the timeline, only one .sfk file is created in the relevant folder.

I just tested 'Rebuild Audio Peaks' on a test video event, and a new .sfk file was created, but it over-wrote the previous .sfk file - so there was still only one .sfk file for that event in the folder.

More than one .sfk file per event does not seem right to me - maybe another forum contributor has experienced this and can advise.

 

Per track ,one sfk. When you have a video that has like 3 audio tracks, you get 3 audio track (sfk) files.

 

Btw, it is nice coincidence that my second entry (that explains the work-around of the issue that no one vocally seems to care) NOT tagged as a "solution". Cause it is not. It is "arcaic", it does not solve the problem when there are multiple clips. The real solution is still at Dev's finger tips.

 

 

 

Dexcon wrote on 1/25/2019, 9:18 PM

Aaah! I see. If I understand correctly, each of your video events has multiple audio events, perhaps along the lines of one audio event containing only the L channel, another audio event containing only the R channel, and the others separately containing the C, RearL, RearR and LFE channels. If that is the case (or similar), then yes, there will be 6 .sfk files because there are 6 separate audio events regardless of the fact that they all relate to the same video event.

I recall that .sfk files were discussed extensively on the forum back in VP11/12 days, and I seem to recall that the conclusion was that there was no way to avoid .sfk files being created in the folder where the original events are located.

Yes, they are a nuisance from a clutter pov, but at least they are not very large in size.

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

i3ordo-r wrote on 1/25/2019, 9:22 PM

not in size but in pixels(screen space), but the real issue is time. any "OBS" or any other "live streaming" user that cares to rewatch/edit his/her own recordings would push this "change" i am sure. Maybe it s too early in the forum.