If you are reading from a slow drive, the read rates will not exceed that source drive's speed capability to read. If the source files are already on the NVMe drive, should not be slow.

If you are reading from a slow drive, the read rates will not exceed that source drive's speed capability to read. If the source files are already on the NVMe drive, should not be slow.

The source files are already on the NVMe.

Are you sure that the drive speed is bottleneck? When these files were of normal SSD/HDD were they opened fast in VP?

May be the footage you using cannot be decoded fast on your system for some reason? You should play with GPU acceleration decoder options or the "so4 thing". You may think about providing some details about your footage or providing link to small sample.

Are you sure that the drive speed is bottleneck? When these files were of normal SSD/HDD were they opened fast in VP?

May be the footage you using cannot be decoded fast on your system for some reason? You should play with GPU acceleration decoder options or the "so4 thing". You may think about providing some details about your footage or providing link to small sample.

Good idea on supplying a sample. Will do soon. I am dealing with mp4 files that have three audio layers. The drive speed is certainly not bottlenecked as it is barely using any of its potential speed. Hardly any of my pc components are really being utilized when the peaks are being formed etc. it was a very slow process on the HDD/SSD that’s what prompted the NVMe purchase to begin with. I need to do a comparison and time how long it takes from the HDD/SSD versus the nvme. I’m thinking there is something about the file that VEGAS does not like/cannot handle properly making this a software issue. I have read, for example, that wav files are almost instantly loaded versus other formats.

I am pretty sure the drive speed is not the bottleneck. I have done tests on my system with reading from HD, NVMe ssd to and from in all combinations, and even created a RAM disk for a while to experiment drive speed. The conclusion in my case with my typical media files (usually from RX10 mark 3 or gopro), it did not make much of difference.

I suppose if my theory is correct, it probably makes more of difference (and see your transfer speed go up) if you use filetypes (for example lossless intermediates) which are not codec compressed or only lightly compressed, those files are typically extremely large in size, but do not require much decoding overhead (CPU and/or GPU workload), but due to their large size benefit more from fast disks and interfaces.

Your disk transfer speed readings are not only capped by it's own HW limits, but the readings will further drop speed if your CPU has not finished decoding the file he is working on...

When dragging and dropping, does Vegas do anything in the background like building peaks or building proxies after you drop the new media on the timeline? By default, it will automatically start building peaks.

When dragging and dropping, does Vegas do anything in the background like building peaks or building proxies after you drop the new media on the timeline? By default, it will automatically start building peaks.

This is what happens with just a 16 gig mp4 file with 3 audio tracks. Notice the read speed on the NVMe drive. Uber slow. I'm thinking this is a software issue and Vegas does not like to load compressed audio.

Look in the bottom left corner, where it says "building peaks". It is drawing the waveform peaks for the audio waveforms, which it then stores in a separate file. This is why the read speed is so slow, it has already loaded the video, but is doing a separate process on the audio at that point in time. You can actually start editing before that process has finished, but if you need to use your waveforms to sync or anything like that, you'll want to wait for the process to finish. Once the waveforms have been drawn and the .sfk files that contain them have been saved into your project media's folder, you will not have to do that process again. It's only on the first import.

This process won't be sped up by buying faster hard drives, unfortunately.

Yeah. I know once it does it the first time you don't need to do it again. Just hoped it would have hastened the initial load time. Oh well! Thanks for the help.

+1 Frosty!

OP needs to look "DOWN" to see that all his Audio Peaks are being created. There is no problem with his drives, processor, GPU...it is the AUDIO being DE-COMPRESSED so you can see all those "wonderful & glorious" waveform peaks that help us to ensure our Audio/Video is synchronized.

I have two ThreadRipper systems, one with an AMD 1950x/Radeon VII, the other AMD 2920X/RTX 2070 FE. When I "slap" any of my GoPro's or AX-53 straight to the timeline, just like the OP's video, I Have To Wait! Been like that since using Movie Studio Platinum 12 Suite, 13, 14, 15, and now 16 Suite; did it with Vegas Pro 12 Suite, 13, 14, and 15 Suite (no Vegas Pro installed since rebuilding 1950x system due to PSU & Motherboard issue from leaking AIO). Did that when I was on Intel platforms, with 3930K, 5820, 5930K, 6800K. So it is not inherently limited to only certain "Brands".

@Bryan-Vahey

Just be patient! Nothing wrong with your drives/CPU/GPU. It will be "faster" opening project and media on second and subsequent loads. Remember though, if you add another file of the type you showed the first time to the Media Bin, it will do the same thing.

Sorry, you both posted while I was still typing. 🙂

+1 Frosty!

OP needs to look "DOWN" to see that all his Audio Peaks are being created.

I know that was what was happening... I just didn't know the process could not be sped up with a faster [NVMe] drive.

I haven't noticed significant improvements with CPU upgrades either, TBH... the audio mostly has remained the same over the years, even though the video codecs have become much more complex, but the amount of time I spend building peaks seems to stay the same for as long as I can remember.

Maybe they could implement a system that gives us a rough waveform that we can only zoom in on so much until it is done building peaks, and as it progresses, it lets us slowly zoom in more and more. I know DAW's do not make you wait to build waveforms, so there has to be some way to either speed this up or eliminate the need for it.

I just built a new Ryzen 9 3900x, Geforce 2070 plus, NVME system. It is wicked fast at rendering, but the 'building waveforms' process doesn't seem any faster than with my older system. It works, but it doesn't seem that Magix has coded this module to take advantage of newer systems ... sound like a feature request.