Stereo/waveform/meter/buss problem in X2a

Author
vespesian
Max Output Level: -80 dBFS
  • Total Posts : 517
  • Joined: 2007/04/13 22:00:16
  • Status: offline
2012/12/29 01:52:14 (permalink)

Stereo/waveform/meter/buss problem in X2a

So far, kinda loving X2a - except that  I'm having this weird problem with stereo vs mono/waveform drawing/peak metering in any busses I use. I'll try to keep this simple. I often use a stereo bass buss which routes to a mono bass buss so that I can process/limit in stereo and 'mono-fy' the results. I've found in X2a however that :

a) The waveform readout of any stereo buss routed to a mono buss is graphically realized as a mono buss...and vice versa. In other words, stereo busses routed to mono busses read as mono - and mono busses read as stereo. I.e., the track/buss inspector button indicates one, and but the waveform indicates another. Which is not the biggest deal in the world - except..

b) The peak meter on said stereo buss is actually outputting the peaks on the mono buss - which makes the limiter I've been using on the stereo buss appear to do be nothing at all - lotsa clipping - even though the limiter itself itself displays gain reduction and no-overs (and I can hear it that it's working). It's a bit disconcerting, to say the least. I use Elephant, with heavy over-sampling (8x) enabled.

c) I know the original signal is stereo, because waveform preview and metering, act as they should on the original track ( in most recent case, using LuSH101 vst)

d) All this is occurring within track view - I haven't bothered with the console view yet..
 
I haven't had many issues with Sonar, and don't recall this happening in X1, although I remember having to 're-enable' stereo and mono states more often than I should have.

Anyone else experience something simuliar?

(i7 3770, 3.4, ssd 256, 2g HD, Win7, 16 g's, Ati hd 7770)




You're in an amazing state.

So stay there.
 

 
#1

0 Replies Related Threads

    Jump to:
    © 2025 APG vNext Commercial Version 5.1