Normalize Bug Sonar Platinum V 23-08-0 Build 30

As title suggests, I went to normalize some vocal clips in a song I`m working on and it really messed up. Did this video test to show what I mean.
 
Steps to reproduce: https://www.youtube.com/watch?v=f5tQxFQdXF4
 
*EDIT: (for reproduction)
For this test I simply opened a blank project, inserted an audio track then recorded some test vocals. *Crop recorded audio (not split just crop) after cropping, split them into clips, did some fades (although it makes no difference if you do that or not) selected them all to normalize and as you can see the results are in the video. 
 

Let's try a diagnostic. Make a copy of the project if it contains material you don't want to lose. Please bounce each clip to itself, try to normalize again, and report back with what happens. 

This was reported here in 2016-  http://forum.cakewalk.com/FindPost/3512358
Seems to be the same problem.

Rasure
If you bounce the clips after splitting, but still keep them as separate clips its works as expected. It seems to be when you just split them, then normalize. Odd. 

The clip is just a graphic representation of a piece of audio, not the audio itself. When you normalize a clip, it's pointing to the entire audio file containing that clip. So clips may be normalized to audio that you can't see. Bouncing the clip to itself makes it independent of the file from which it came.

I tested this by importing a 1000 Hz mono sine with a peak of -6 dB, and then duplicating it twice. I used Process -> Gain to lower the first clone to -7 dB, the second clone to -8 dB. I then selected all three and used Process -> Normalize to set them all to -3 dB, and then verified that they all do in fact now peak at -3 dB.
 
I tried selecting them three ways: selecting the track, ctl-click on each clip, and dragging a selection box around them. How they were selected made no difference.
 
I also tried normalizing to a lower peak, -10 dB, and that also worked as expected: all three clips peaked at -10 dB.
 
I then split the clips to see if that made a difference, as described above. It didn't.
 
I've run out of ways to test this. Whatever's going on here, it has to be data-specific. Want to send me a test project so I can try it on the same data?

I was able to reproduce the behavior in the video, but I also think I've found a workaround to avoid having to bounce each clip. It worked every time for me, can you please try it and confirm.
 

1. Crop the clip (beginning and end)
2. Bounce the resulting clip to itself
3. Apply trimming to the resulting clip

 
Now if you separate it into multiple clips, select all of them, and then normalize, it works...or at least it did here.

Anderton
I was able to reproduce the behavior in the video, but I also think I've found a workaround to avoid having to bounce each clip. It worked every time for me, can you please try it and confirm.
 

1. Crop the clip (beginning and end)
2. Bounce the resulting clip to itself
3. Apply trimming to the resulting clip

 
Now if you separate it into multiple clips, select all of them, and then normalize, it works...or at least it did here.

Thanks, still not right though. https://www.youtube.com/watch?v=oHHnIzz3onI it`s the cropping that does it.
 
@THambrecht yes it should be fixed.

Yeah it works if you apply Trimming, still needs to be fixed :-)
 

My projects are all too big for Cakewalk to reproduce.
I had the same problem today. Not only normalizing, rather "GAIN" is producing corrupt audiodata in the same situation. My project today has 46GB audiodata.
I had submitted a bug report with pictures (a few years ago) - but with no project to reproduce. I had already a few situations, where "apply trimming" and bouncing to itself no more helps.
 
 

Anderton
Well it's not going to get fixed within the next week, and if you follow my steps you don't have to bounce every clip individually...saves a lot of clicks.
 
Has anyone submitted a bug report with recipe to reproduce, or do I need to do that?

I couldn't find the the page to submit to, maybe move this thread to the Problem reports forum? 

We don't have bug reports. They were eliminated when support was re-imagined.