A channel control should do it with Mid/Side control. Essentially if you reduce the side volume it will be perceived to be more mono.  I use VSL Powerpan, although I think Sonar has a channel width tool which essentially will do the same.
 

I had the idea.
Only "Sound Forge" can open the files in the audiofolder. Because there is any unknown incompatibility with Adobe Audition and Wavelab with the SONAR-created w64-files. That only applies to recorded w64-files in the audiofolder.
So I created a batchjob in Sound Forge that opens hundreds of W64.files and resaves them (without doing anything) in the "right" format.
Now Adobe can read this "repaired" files and does a pan-normalize via batch-process.
Adobe also can trim the files at beginning and end. (Which has never done in SONAR since lightyears)
After that I can open the 14 projects in SONAR, name the clips, and automate-export them via clip-export.
In a few days the work is done, almost only with automation. Now the computer can do the work for itself the next days.
 
Mid/side Control or Limiting is a NoGo because this manipulates the audio data. The audio (Dynamik) must NOT be changed. The original can not be changed.

I may have missed something. Can your Audition open files >2GB and it was just not recognizing the w64 format?

mettelus
I may have missed something. Can your Audition open files >2GB and it was just not recognizing the w64 format?

 
Adobe Audition can open wavefiles larger than 2GB and also very large w64-files. In this case I have files between 5 and 6 GB (recorded in SONAR as w64).
The problem is, that SONAR saves the recordings in an incompatible format. It is w64, but incompatible to Adobe and Wavelab. But compatible to Sound Forge.
Than Adobe says "blockheader is not recognized". So I cannot open this files directly in Adobe. This was the point I opened the w64-files in Sound Forge and resaved them. Now Sound Forge "repairs" the file and the blockheader is recognized and Adobe can read this files as well as Cakewalk.
If this problem with the "unrecognized header" is up to SONAR or Adobe or Wavelab - is unknown.
 
 

Well here is a workaround. Configure Sonar to use Sound Forge as an external editor. This way you can jump back and forth between applications and save the final version through Sound Forge.
 

interpolated
Well here is a workaround. Configure Sonar to use Sound Forge as an external editor. This way you can jump back and forth between applications and save the final version through Sound Forge.

 
Thank you. The only thing we need an external editor is pan-normalize. All other things we do within SONAR.
Sound Forge is a very poor editor with very poor plugins. And has no funktion for seperate left + right normalize. We need Sound Forge ONLY to repair SONAR w64-files.
By the way is Wavelab the only real "pan-normalizer" that normalizes per RMS. I hoped someone has written a plugin that does the same as Wavelab.

With Sound Forge you select the right channel, the use normalize, it will normalize just the selected data (in this case the right channel).  Then select the left channel and normalize again.
 
There is no easy way a plugin can normalize audio.  VST plugins process a stream of audio, normalize requires access to the entire waveform.  A plugin normalizer would require some bizarre workflow and be very ugly at best.
 
 

msorrels
With Sound Forge you select the right channel, the use normalize, it will normalize just the selected data (in this case the right channel).  Then select the left channel and normalize again.
There is no easy way a plugin can normalize audio.  VST plugins process a stream of audio, normalize requires access to the entire waveform.  A plugin normalizer would require some bizarre workflow and be very ugly at best.

 
Thank you.
I know there is no easy way for a pan-normalizer-plugin. But there is after all a plugin for "dynamik normalising" which also needs access to the whole data. It normalises the data dependent on the volumen - great for dialogs. A pan-normalizer-plugin would also be never a live-effect. Maybe I need to hire someone.
I didn't knew this with Sound Forge. For the huge amount of data we are editing for radio broadcasts and film industry we need batch processes. And the batch-processor from Sound Forge has no way to pan-normalize. But the batch-processor has the possibility to load thousends of w64-files and re-save them to a compatible format for Adobe and Wavelab. At this point we do batch-processes with Wavelab or Adobe Audition. The two have just the most features for batch-processing.
The cracking point is: Sonar openes the outside-processed projects without any problem.
And SONAR is just the fastest editor and best software for the huge amount of data.
 
 

I could have sworn you could normalise by RMS in Sound Forge Pro. However I was told by others never to do this unless it was a final audio take.
 
Been a long time since I used it and miss the metering options that comes with it.
 

Nevermind