New glitches and weirdness - has anyone encountered these? (Update: big thanks to Noel B!)

I've had a very bad and totally non-productive day with X1....   (Again....)
 
I posted on another thread about major malfunctions on setting a MIDI clip's start time and those responding couldn't replicate them.
I've now hit two really bizarre audio ones, and I just wanted to check if anyone else had encountered them before I resort to a complete reinstall of X1 in desparation (in the forlorn hope that will fix things...).
 
(1) Non-destructive fades not working:  When I drag the little triangle to make a fade slope at the start of end of a clip, the playback gives silence where the sloped fade line is, i.e. at the start of the clip instead of a fade in there is silence and then an abrupt start of the audio when the and of the fade line is reached (or complete switch off at the end of a clip where a fade out slope line starts).
 
(2) Process/Apply Effect/Gain: Select a clip to increase or decrease its gain.  Whatever I select from the popup the result is a correct change to the left half of the stereo but total obliteration to zero of the right half.  And no, I haven't meddled with the sliders.  (NB: I have another DAW with Sonar X1 to build 242 and this works ok, so....)
 
Thanks for any input.

Bump.
Sorry, can someone please check these for me?  Behaviour No.1 (non-destructive editing) is so fundamental I can't think it's really broken - that it must be something on my install.  No. 2 I think is a genuine bug, but again I really need to know if it's not, before I report these two to CW.
Many thanks.

Both those things work as expected for me. I have X1b 246

For info, I've reported both of these as bugs to CW, since I obliterated Sonar X1 and did a full reinstall in a last-ditch attempt at banishing them, to no avail.

The trouble is they are both intermittent and despite trying various things I can't arrive at a single set of circumstances that guarantees they will happen.  This is a real pain as having these features buggered up like this (especially the fade in, fade out one) makes Sonar X1 such a pain I just can't trust it.  I hope the CW techincal people can replicate it or I'm pretty well doomed to a permanent return to 8.5.3...

Skyline_UK


I've had a very bad and totally non-productive day with X1....   (Again....)
 
I posted on another thread about major malfunctions on setting a MIDI clip's start time and those responding couldn't replicate them.
I've now hit two really bizarre audio ones, and I just wanted to check if anyone else had encountered them before I resort to a complete reinstall of X1 in desparation (in the forlorn hope that will fix things...).
 
(1) Non-destructive fades not working:  When I drag the little triangle to make a fade slope at the start of end of a clip, the playback gives silence where the sloped fade line is, i.e. at the start of the clip instead of a fade in there is silence and then an abrupt start of the audio when the and of the fade line is reached (or complete switch off at the end of a clip where a fade out slope line starts).
 
(2) Process/Apply Effect/Gain: Select a clip to increase or decrease its gain.  Whatever I select from the popup the result is a correct change to the left half of the stereo but total obliteration to zero of the right half.  And no, I haven't meddled with the sliders.  (NB: I have another DAW with Sonar X1 to build 242 and this works ok, so....)
 
Thanks for any input.

As far as the 2nd 0ne-I use the process>apply effect\ gain all the time. Never seen issues like that. Stereo or mono tracks

Noel Borthwick, CTO at CW, and his team have tracked these issues down, and I just wanted to publish a thank you to them for taking such a personal interest in my very obscure but crucial issues.  (AVX protocols anyone??  No, me neither...)  No doubt the fixes will appear in the next QF.
 
Personal email support like this from Noel (over last weekend also) is much appreciated and to me demonstrates CW's commitment to quality.  As some of us say in tbe UK: I speak as I find.

Thanks Noel! 

Mine isn't fixed as such.  CW sent me special SONARPDR.EXE builds asking me to test them for the two audio bugs I was getting.  They tracked the problem to certain circumstances where Sonar is using Intel AVX instruction sets in Windows 7 SP1, (I didn't have the bugs before SP1) and as far as I know it's restricted to DAWs with Sandy Bridge processors.   I assume the full fixes will be included pretty soon in a patch or maybe even a 'X1c' roll up of patches and Quick Fixes.  

Hi Skyline.  Have you found a fix to your clip fade problem yet? I'm having the exact same problem with my Sonar X1b 64bit where as soon as I apply the clip fade the sound cuts of completely wherever the fade starts. I've been trying to fix it for over 2 months now.  I have also contacted CW about it and then suggested to do something with the configuration file which didn't work.  I've reinstalled X1 twice now and for me it only happens after the X1B update.  Here are 2 other things I've found out about this problem on my machine:

1)-It doesn't do it on the 32bit X1 even with all the updates.

2)-This one is interesting, It only does it on a bounced clip or track.  So for instance if I just record audio from my keyboard into Sonar the clip fades work perfectly. But if I 'bounce to clips' that same track then the clip fades start muting the track instead of fading it. Also this means all my soft synth audio that I 'bounce to track' don't work with the clip fade.

I've even put the same exact clip on the same track but in two different layers and bounced one to clips and left the other one alone and it still mutes one and not the other with clip fade even though they both have the same clip fade on them. 

I've read all your posts about this and some have suggested it's a UK thing but I'm in California so I guess it's not that.

Thanks for the response Skyline.  I do have a Sandy Bridge processor. I have the Intel Sandy Bridge i5 2500k @ 3.3 GHz.  So I guess that's it then. I sent Noel a message so hopefully he can help me out as well.

AVX is only supported in win7 Service Pack 1 so maybe either put off installing SP1, or possibly roll back?

ner, they don't have to use bleeding edge technology if they don't want to