Its not very often I rant but... (X2)

I thought cakewalk would have learnt from the X1 experience. Its becoming increasingly hard work to get things done quickly in X2. These are just some of the random issues I experience on a daily basis in X2 and to be honest Im losing my patience!
 

• Crashes when auditioning loops from the browser
• Crashes when setting loop points during playback
• Freezing then unfreezing softsynth sometimes resets Pro channel settings, you wouldn't know to look at them, but you can hear it.
• Inserting softsynths doesn't always load the one you select, using replace synth fixes this
• Pro channel FX chains randomly loses their learnt knob functions - Reloading the FX chain fixes this until the next time it happens
• Now time marker disappears after editing in PRV
• Pro channel modules become unresponsive, in other words they are still engaged whether they are turned on or off
• General graphics oddities

I have experienced crashes when auditioning loops, but not for a while. 

My alphatrack works fine. I'm not having trouble with crashes. I get dropouts when my processor can't keep up, but that's expected. Disabling FX on tracks I'm not using helps with this. By passing FX during recording removes the problem entirely. My PC is a little week. I use a 6 year old laptop with a dual core.

Yeah....

Slowdowns for sure...

I have many graphics oddities here as well.... and it's not the machine as X1 is running cleaner and 8.5.3 runs even better...

For me the slowdown is in all the losses... It's nice to get new things but not when the loss outweighs the gains (for me)...

Lanes are horrible for me. The lack of range to the zoom control is making editing very difficult. I don't have great eyes anymore. when loop recording, they force me to constantly re-fill/size the screen as the new takes are off-screen. Changing from track to take requires way too many extra clicks and is needed constantly due to how little screen real estate is left with all the X-waste... As talked about when X1 came out. The new UI occupies far more space for fewer controls and tracks... Now Lanes takes that a big step further down that path... They leave the "track" area in the clips pane empty/wasted and can't be made small enough to fit much on the screen... Comping a track with many lanes has become a very difficult chore. Moving clips between Lanes and/or other tracks? <sigh>... I could rant on as the Lanes are not a welcome item in my life. A major step backwards so that my mute/solo buttons can be bigger? Bad trade!

The many gfx oddities are difficult as well. It took me many days to get used to the lack of visual change when muting/unmuting clips. I press the appropriate control and nothing changes until the mouse moves off hovering on the clip... Extreme jitter when clips are dragged/copied... PC modules disappearing/re-appearing... Meters in TV not working for higher numbered tracks (confirmed and related to hidden/archived tracks)...

Why does Audiosnap continue to operate even after all such attempts have been disabled? I try AS, give up and undo all the work... when I next open the song, I get the AS messages regarding "Processing Audio"...

If only they would release the PC modules as VST so that I could go back to 8.5.3 and return to a more comfortable work environment (for me)... I have no benefits directly related to the X changes other than the PC modules... There are a few more keyboard commands which would just as easily been added to 8.5.3 and what else? Everything else is about the new gui which does not help me... I use some of the new tools because I'm forced to find ways to use X1 (such as screensets)...

I was looking forward to the new auto-zoom and and smart snap only to find that they get more in my way than not so they remain disabled...

I could go on...

Keni

The only issue raised by the OP that I see regularly are the graphics issues - there's some weird stuff going on, certainly in the prv, and to a lesser extent, Track view.

I did have my first crash since the quick fix last night, but I'm pretty sure it was to do with a less than optimal Pentagon Installation

That's it! I hereby declare all our Sonar whoas are due to the local power grids. DIRTY POWER is the culprit! Your level of dirt may vary from mine.
 
Most of us experience a variety of Sonar glitches un-reproduceable by users in different regional locations.That's because each area has it's own power generation, right? They all use different methods to make that power. ie: oil, coal, water, wind, nuclear waste  (my favorite), and so on. Then there's the wires, transmission lines, relay stations, etc. all made, installed, and maintained by different companies with different philosophies and agendas.
 
We're not all on the same grid which means we're not all on the same page when it comes to software bugs. 
 
Sure you can blame things like different system configurations, corrupted installations, out of date drivers, bad clusters, unevenly parsed memory modules, and good ol' user error, but the bottom line is you get out of something what you put into it. Where does it all start? In this case... dirty power!
 
Case closed! 'Nuff said! End of story! My work here is done!
 
Curious how many of us are using power conditioners or regulators on our systems? I'm not.
 
 

I blame it all on global warming. Al Gore told me so.

Still waiting for the meters to be fixed & track lanes for me are just well.. I won't go into it.
I use a 600w backup & PL-PLUS DMC Power conditioner on my small setup & it's proved to be invaluable over the years.

soens

That's it! I hereby declare all our Sonar whoas are due to the local power grids. DIRTY POWER is the culprit! Your level of dirt may vary from mine.
 
Most of us experience a variety of Sonar glitches un-reproduceable by users in different regional locations.That's because each area has it's own power generation, right? They all use different methods to make that power. ie: oil, coal, water, wind, nuclear waste  (my favorite), and so on. Then there's the wires, transmission lines, relay stations, etc. all made, installed, and maintained by different companies with different philosophies and agendas.
 
We're not all on the same grid which means we're not all on the same page when it comes to software bugs. 
 
Sure you can blame things like different system configurations, corrupted installations, out of date drivers, bad clusters, unevenly parsed memory modules, and good ol' user error, but the bottom line is you get out of something what you put into it. Where does it all start? In this case... dirty power!
 
Case closed! 'Nuff said! End of story! My work here is done!
 
Curious how many of us are using power conditioners or regulators on our systems? I'm not.
 
 

I use an online uninterruptible power supply, one that uses both a rectifier and an inverter. In the USA utilities commonly deviate from 120 volts by up to 15%. Larger deviations occur during load switching and ground faults. Then there is reactive power and the effect it can have on critical electronics. imho an online UPS is an absolute necessity for a stable DAW.

I do use a UPS with surge and power filtering. So i cant blame the power.
Mind you we do get lots birds sitting on the overhead power lines outside our house!
I think i will get an air rifle to shoot them off, and see if the computer glitches go away!

"Now time marker disappears after editing in PRV" - Yes, that bugs the crap out of me.