Erratic waveform displays in main track when using comping

First, I love the Comping feature in X3 -- Speed comping is fantastic.
 
But something is very strange.  Audibly, everything is working as expected.  But the waveform displayed on the main track seems to have about 30dB more than it should and it looks like the track is clipping, even though it isn't.  There seems to be some kind of scale problem here.  My hunch is that it is a bug where the various comping lanes are being summed for display purposes, although they are not being summed for the audio output.
 
Has anybody else observed this?
 
It isn't a crisis.  The feature produces the desired results, but the display is just a bit alarming.

cparmerlee
First, I love the Comping feature in X3 -- Speed comping is fantastic.
 
But something is very strange.  Audibly, everything is working as expected.  But the waveform displayed on the main track seems to have about 30dB more than it should and it looks like the track is clipping, even though it isn't.  There seems to be some kind of scale problem here.  My hunch is that it is a bug where the various comping lanes are being summed for display purposes, although they are not being summed for the audio output.
 
Has anybody else observed this?
 
It isn't a crisis.  The feature produces the desired results, but the display is just a bit alarming.

 
Could you post a picture of what you mean? I'm taking a look at it right now and just want to be sure as to what the issue looks like exactly.

FastBikerBoy
A large waveform in the comp track would suggest there is more than one audible clip at that point in the lanes. That's what I'd check, remember it will still display unless the clip itself is muted. i.e. if the lane is muted it won't sound but will display.
 
That's where I'd check.

What you are describing may be exactly what is happening, but that's not what I would have expected.  When comping, the feature automatically mutes all the lanes except for the chosen clip.  So they are not "audible", meaning you hear only one lane's worth of audio and that is not clipping.  But the main track's waveform display seems to sum the other lanes and that loops like it is clipping.  But it isn't completely predictable -- at least no pattern I have been able to discern.  (With software there is ALWAYS a pattern, even if the pattern is not obvious,)

Dan Gonzalez [Cakewalk]
Could you post a picture of what you mean? I'm taking a look at it right now and just want to be sure as to what the issue looks like exactly.

 On that particular project, I did revome all muted clips and then flattened the comp.  At that point, the display looked right.  In other words, I would not expect the main track's waveform to change at all when you issue the "remove muted" or "flatten" commands, but it definitely did.  I would have thought the main track's waveform would always correspond with "What U Hear", so to speak.
 
I went back to an earlier version to reproduce a screen shot.  This somewhat contradicts my theory in a previous post as the clipping values sometimes start in the middle of a segment.  Notice where the time cursor is.  At that point, it appears the volume is much louder, and distorting.  But in fact, there is no such change in the sound.  The sound is as one would expect from looking at the T4 clip.  I should be clear here, there are only two take lanes.  I had already deleted T1 and T2.  You are looking at the entire track.

I wonder if the WOV files could be coming into play...   If you clear the picture cache does the track redraw the same?  
 
This is assuming, of course, that the comps are handled the same way - no idea since I don't have X3 yet.  
 
 

I've noticed this too.
 

May have nothing to do with it but... I only recently started actually using my X2 install and in the 1st project I started I got half way through before I noticed that even though my asio settings were for 24-bit, my tracks were being saved in 16-bit. I found the setting (in "preferences/folders" somewhere?) and reset to 24 bit. A while later I noticed that everything recorded prior to the switch was clipped at -6db. I opened in sound forge just to be sure and saw the same thing. Damn, lost all my work I though. Re-recorded my tracks and then noticed a funny thing... the original tracks weren't displayed as clipped anymore. 
 
So, any chance you changed your folder/wav file resolution settings (figure a lot of people might since they will be fresh installs of x3).... just a stab, but weird to see someone having near the same issue I just had with x2.

CareyLetendre
I've noticed this too.
 

 
That one is what I'd expect to see. All of the take lanes have audible clips in them. The comp take at the top is showing the sum of those lanes.
 
EDIT: Doh...... sorry Brundlefly, I'm duplicating your post. NOte to self...... read whole thread before posting.

Dan Gonzalez [Cakewalk]
I'm currently taking a deeper look into this issue. If you guys have a step by step or a formula for reproducing this in a brand new projects then please share so I can get a concrete understanding of this. 

For the others who are interested, I sent Dan the project that produced this problem, and it is similarly misbehaving for him.  But I cannot recall the exact sequence of things that produced the problem.  I'll lay out some things that are a little out of the ordinary with this project, hoping that one of them might trigger a thought or two:
 
1) The project was created under X2.  It was MIDI-only under X2. I recorded the audio track after upgrading to X3.
 
2) When first recording, my project was in sound-on-sound more.  I changed to comping mode after I had already created 2 take lanes.
 
3) After recording my takes, I didn't follow the recommended speed-comping procedure at first, as this was my first use of the comping feature.  I tried to promote phrases using the mouse.  I believe by that time, I was already seeing the strange waveforms.
 
4) At one point, I used the split tool when I probably shouldn't have.
 
5) After I figured out the recommended work flow for auditioning the takes, I breezed right through it, but the damage was already done.