issue with WAV playback

Qbrick wrote on 7/8/2025, 7:50 AM 
General
Complete name                            : I:\output.wav
Format                                   : Wave
Format settings                          : PcmWaveformat
File size                                : 1.21 GiB
Duration                                 : 2 h 30 min
Overall bit rate mode                    : Constant
Overall bit rate                         : 1 152 kb/s

Audio
Format                                   : PCM
Format settings                          : Little / Signed
Codec ID                                 : 1
Duration                                 : 2 h 30 min
Bit rate mode                            : Constant
Bit rate                                 : 1 152 kb/s
Channel(s)                               : 1 channel
Sampling rate                            : 48.0 kHz
Bit depth                                : 24 bits
Stream size                              : 1.21 GiB (100%)

Hi!

I have a strange behaviour with a wav import. (On Audacity the same file is OK)
On Vegas when I zoom I can see a large rectangle (see image).

Anyway when I playback the wav on Vegas I can hear an high bad sound.

What happen?

Thanks!

Comments

RogerS wrote on 7/8/2025, 8:06 AM

Thanks for sharing mediainfo. Can you share what version of VEGAS you are using?

Could you share a fullscreen screenshot of VEGAS? It's hard to see what is what here.

Qbrick wrote on 7/8/2025, 8:16 AM

Thanks for sharing mediainfo. Can you share what version of VEGAS you are using?

Could you share a fullscreen screenshot of VEGAS? It's hard to see what is what here.

Thanks for support. I'm a legit user.

and with zoom on timeline.

On Audacity no problem.

Here a ZOOM dimostration of issue (only zoom on timeline used on this video):

PS

every single audio clip is a WAV file.

 

RogerS wrote on 7/8/2025, 8:51 AM

Thanks, I see it's VEGAS Pro 20 build 411.

The way you have your window customized I can't see things like audio Fx or buses. It does look as if the audio is clipping- there aren't any volume Fx at the bus or event level are there? If you hold shift and press the down arrow the display doesn't improve does it (shift plus up makes waveforms more visible, down less).

It's possible there is a bug with wav though I don't recall that with VP 20 or see anything in the release history. If you have a wave file others can try please upload it somewhere for testing.

rraud wrote on 7/8/2025, 11:56 AM

Hi @Qbrick, the audio event 'appears' to be severely clipped (peaks squared off) as @RogerS stated. Have you tried re-normalizing the event.. or disabling the event's normalization all together. Right-click the event and choose 'Properties' for the settings.

Qbrick wrote on 7/9/2025, 1:34 AM

Thanks for support!

Maybe I found the problem.

Does Magix Vegas manage a:

Input #0, wav, from '.\output.wav':
  Duration: 02:30:50.17, bitrate: 1152 kb/s
  Stream #0:0: Audio: pcm_s24le ([1][0][0][0] / 0x0001), 48000 Hz, mono, s32 (24 bit), 1152 kb/s

Here you can see what s32 means.

RogerS wrote on 7/9/2025, 1:46 AM

24-bit WAV? Yes, VEGAS supports that as far as I'm aware. Could you share a sample file that doesn't work for testing?

Qbrick wrote on 7/9/2025, 2:14 AM

To see/hear the issue:

  1. download for example https://www.dailymotion.com/video/x9jd8vc (via Video DownloadHelper for example)
  2. import in Audacity
  3. split from Stereo to mono
  4. select one track (for example left channel)
  5. export to WAV (mono; 48kHz; Signed 24-bit PCM) --> name: output_test.wav
  6. open Vegas Pro (20.0 b411)
  7. set 5.1 on audio settings (48kHz; 24bits; resample=Best)
  8. import the wav file (output_test.wav)
  9. zoom on beginning (1-2 seconds...)
  10. you can note the issue

RogerS wrote on 7/9/2025, 3:01 AM

I opened an audio file in izotope Rx, output it to mono 24-bit PCM and opened my oldest version of VEGAS still installed (21.208). I changed it to surround sound. I don't see an issue.

Hopefully others can test with VP 20.411.

Audio
Format                         : PCM
Format settings                : Little / Signed
Codec ID                       : 1
Duration                       : 15 s 962 ms
Bit rate mode                  : Constant
Bit rate                       : 1 152 kb/s
Channel(s)                     : 1 channel
Sampling rate                  : 48.0 kHz
Bit depth                      : 24 bits
Stream size                    : 2.19 MiB (100%)

 

Qbrick wrote on 7/9/2025, 3:03 AM

I opened an audio file in izotope Rx, output it to mono 24-bit PCM and opened my oldest version of VEGAS still installed (21.208). I changed it to surround sound. I don't see an issue.

Hopefully others can test with VP 20.411.

Audio
Format                         : PCM
Format settings                : Little / Signed
Codec ID                       : 1
Duration                       : 15 s 962 ms
Bit rate mode                  : Constant
Bit rate                       : 1 152 kb/s
Channel(s)                     : 1 channel
Sampling rate                  : 48.0 kHz
Bit depth                      : 24 bits
Stream size                    : 2.19 MiB (100%)

 

Thanks! Try with a 1h 30m+ mono audio file.

Dexcon wrote on 7/9/2025, 3:52 AM

In VP22, I rendered a 2h 10m project to a 24 bits 40 KHz mono .wav file:

In Vegas Pro 20 b411, the audio properties were set thus:

... and the timeline layout set similar to yours.

As you can see, I am not getting the timeline display issue that you are experiencing.

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

Qbrick wrote on 7/9/2025, 5:23 AM

The problem is both VP20 and VP22.

Both have the same audio project settings:

Steps:

Open VP20 and load the WAV, then zoom on timeline:

Close VP20, (rename the WAV file so the VP22 does not use the .sfk file generated before)

Open VP22 and load the renamed WAV, then ZOOM on timeline

Same issue..

On Audacity the file is OK:

And:

the same file, converted to WAV (via Audacity) is OK. So there is a problem with WAV import into Vegas...

Same WAV imported on Davinci Resolve is OK:

 

Dexcon wrote on 7/9/2025, 5:34 AM

Sorry, but unable to repro in either VP20 or VP22 using the same properties settings as you've uploaded, the panner in the track header having all 5 speakers active, and also renaming the audio file for VP22.

As a further test, I took the 2h 10m .wav file and re-rendered it in Audacity (3.7.4) and loaded the Audacity rendered .wav into both VP20 and 22. Again, no display issue at all with the waveform on the timeline.

Perhaps try re-rendering the .wav file in Resolve to another .wav file and then see what happens to the DR render in VP.

Last changed by Dexcon on 7/9/2025, 5:58 AM, changed a total of 2 times.

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 7/9/2025, 8:30 AM

I opened an audio file in izotope Rx, output it to mono 24-bit PCM and opened my oldest version of VEGAS still installed (21.208). I changed it to surround sound. I don't see an issue.

Hopefully others can test with VP 20.411.

Audio
Format                         : PCM
Format settings                : Little / Signed
Codec ID                       : 1
Duration                       : 15 s 962 ms
Bit rate mode                  : Constant
Bit rate                       : 1 152 kb/s
Channel(s)                     : 1 channel
Sampling rate                  : 48.0 kHz
Bit depth                      : 24 bits
Stream size                    : 2.19 MiB (100%)

 

Thanks! Try with a 1h 30m+ mono audio file.

Just share a problem file, this is too difficult to replicate.

Qbrick wrote on 7/9/2025, 9:20 AM

Sorry, but unable to repro in either VP20 or VP22 using the same properties settings as you've uploaded, the panner in the track header having all 5 speakers active, and also renaming the audio file for VP22.

As a further test, I took the 2h 10m .wav file and re-rendered it in Audacity (3.7.4) and loaded the Audacity rendered .wav into both VP20 and 22. Again, no display issue at all with the waveform on the timeline.

Perhaps try re-rendering the .wav file in Resolve to another .wav file and then see what happens to the DR render in VP.

try with my wave please --> https://www.swisstransfer.com/d/ba5193e8-fe6c-4d61-9bd1-5312003f4a0a

link valid until: 08/08/2025 16:06 GMT+2

Dexcon wrote on 7/9/2025, 9:37 AM

Thank you for uploading the original audio media.

In Vegas Pro 20 b411, no problem:

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 7/9/2025, 9:58 AM

The file seems to be okay with 22.250.
Tested on my laptop (see signature).

Looking at the file properties as expected it is opening with wav plug:

Plug-In
  Name: wavplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 22.0\FileIO Plug-Ins\wavplug
  Format: Wave (Microsoft)
  Version: Version 22.0 (Build 250)
  Company: MAGIX Computer Products Intl. Co.

Last changed by RogerS on 7/9/2025, 10:00 AM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.250

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

john_dennis wrote on 7/9/2025, 10:40 AM

I tried the problem file in Vegas Pro 21-315 and 22-250 with other 5.1 and stereo files and could not reproduce the issue.