Unless Sonar decided to redesign to Console view upside down, Im not switching anytime soon.
I do like to see what's out there (for other DAWs). But the time spent learning a new DAWs features and work flow is time I could be working on a new project. See what I mean ?
 
In other words, Sonar would have to totally bobble a new release/update to the point where I couldn't complete simple tasks, features that I use every day and it would have to be multiple not just one thing.
I guess I fall under the fan boy title. But in reality, im just a guy trying to make music.

I have also experienced the lagging issue (named "limping phenomenon" in luna004's YouTube video) when you have a lot of CC automation data. I assume it's performance intensive, but maybe that part of the code could be optimized a little? (Maybe also implement a "thin-out automation" feature?)
 
I would love some more focus on MIDI instead of another comping improvement... :)
 
Maybe we could compile a wish-list?

Anderton
The data being collected is very basic, mostly relating to OS, amount of memory, CPU, whether 32 or 64 bit, time spent in the program, and plug-ins. It will be a while, maybe even quite a while, before analytics gets more granular. 

Bummer!! I was hoping my 100s of hours fiddling with Audiosnap over the past few months was giving them some good input. But sadly apparently not. 
 
gabo

cyberzip
I have also experienced the lagging issue (named "limping phenomenon" in luna004's YouTube video) when you have a lot of CC automation data. I assume it's performance intensive, but maybe that part of the code could be optimized a little? (Maybe also implement a "thin-out automation" feature?)
 
I would love some more focus on MIDI instead of another comping improvement... :)
 
Maybe we could compile a wish-list?

There is a CAL script already in existence to thin out controller data

Bristol_Jonesey
There is a CAL script already in existence to thin out controller data

Ah, you're right Bristol_Jonesey! Thanks for the reminder.
 
Actually, even as I wrote it, something in the back of my head tried reminding me of that CAL script... :) Could be built into the GUI though for easier and fast access!

Yes it's actually called "Thin Controller Data.cal"
 
All the .cal scripts are accessed from the Process menu

I rarely use Midi but when I do I immediately record it to an audio track and delete the midi track.
That probably doesn't help the guys that want to constantly tweak their CC's.  But it helps conserve CPU.
Mark.

To be semantically correct: Since I am on Lifetime updates I'll only leave SONAR when I cease to exist.
 
However, I will stop using SONAR when it ceases to work for me, which is highly unlikely.
 
I dabble with two other DAWS (Reaper and Studio One Pro 3.x) but for tracking, editing and pre-production SONAR is still my favorite. Starting this year mixing and mastering will be done in Harrison's Mixbus32C as soon as they fix a bug with UAD and Plug In Alliance base plugins. It's not a major bug but a painful annoyance.

JohanSebatianGremlin
Shrug. I use lots of automation. And I much prefer working with envelopes and I much prefer those envelopes have as few nodes as possible.
 
If someone can actually hear the difference between my two-node fader moves and someone else's two hundred-node fader moves, well let's face it, that person was never going to like my music anyway. 

Post of the week.
 

bapu
Starting this year mixing and mastering will be done in Harrison's Mixbus32C as soon as they fix a bug with UAD and Plug In Alliance base plugins. It's not a major bug but a painful annoyance.

+1 here for at least mastering with Mix Bus.  I haven't tried mixing with it...I don't know it as well as SONAR.
But for mastering, just the default settings adds that "special sauce" analogue sound.