Can someone please help me.  What am I doing wrong here?   Why does the tempo map change the fade in behavior on an audio track? 
I probably have something stupid set or ???
 
All I did was import an mp3 (or wave doesnt matter) onto an audio track, then open the tempo view. 
(I was actually working on a different midi proj with audio etc and a tempo map - this is the simplest instance I could make to demo my question)
 
This is in X2a - does this happen to anyone in X3?
 

 
 
 

You're not doing anything wrong. The waveforms are screwy when there are tempo changes in X2. I haven't tried it in X3 yet...

Thanks - appreciate the reply - if you get a few seconds, can you just try it in X3 for me?  They probably have it fixed (hoping).

Nope - it's exactly the same in X3

I think this happens without tempo changes too - I remember seeing a lot of those kind of waveform glitches in projects with a steady tempo.

Has anyone submitted a bug report?  I could for X2a but there's no point as X3 is out - and I don't have X3.  This is pretty sad indeed.
 

Update - just downloaded and installed X3a and it's NOT doing the 'bug' that I an seeing in X2a.  Exact same project, works perfect in X3a (and X3b)!   At least for what I'm doing it's good - yeah  
 
Now if they could just fix CWBRN-17926 ....

This is something that we are aware of and are looking into. Thanks for the heads up on it!
-DG

Dan Gonzalez [Cakewalk]
This is something that we are aware of and are looking into. Thanks for the heads up on it!
-DG

So 20 months, new version with 5 updates and this problem still exists. See this thread.
http://forum.cakewalk.com...accurate-m3236603.aspx

mudgel

Dan Gonzalez [Cakewalk]
This is something that we are aware of and are looking into. Thanks for the heads up on it!
-DG

So 20 months, new version with 5 updates and this problem still exists. See this thread.
http://forum.cakewalk.com...accurate-m3236603.aspx

This is a confusing thread - sounds like it was fixed in X3a and X3b, and then broken again? Although JBaner suggested it was not actually fixed in X3? I don't know if a problem report was ever filed for this, I've never (knowingly) encountered it myself. But yes, 20 months when Cake seems aware of it seems like a long wait for a fix.