ProChannel ACT Mapping in the Console View doesn't work since X3 which was the last version where it worked.

No

dappa1
I sure there was mention of new code. New flagship so this post is really irrelevant.

 
If you read the stickies the new owners are asking for input from forum members. It doesn't hurt to ask and now is the time to make the changes. If they do base the "new DAW" on the old Sonar coding it would be a shame to carry over any bugs and quirks. 
 

What "they" really have to do is to fix the timing issues.
Audio files are not recorded on the beat as it should.
The ASIO drivers reported latencies are off.
I know many users, including myself, reported problems with audio beeing recorded off beat due to latencie errors.
That and the quantisation. Quantise is a huge downer for me.
When I record midi in Cubase I never have problems with quantising.
But in Sonar I have issues with the quantise function.
It seldom quantise the notes in a musical way. Cubase does and Sonar dont.
Thats the two most imortant "bugs", issues "they" have to fix. In my book.
Other than that. Nothing but praise to Sonar.
Except the missing tuner and tap-tempo up front.
 
 

Cactus Music
1- Crashing after so many midi edits unless you keep saving
2- Setting that do not stay put and have to always be reset every time you start a new project. Example - Opening a midi file to make a new project. The  Lens is ignored and you have to re arrange your pages,
3-The export setting do not stay as you set them. Everytime you export you have to make changes. ( see# 7 )  
4-Bugs in the track templates that will randomly insert a new Master buss. I'm never sure what will be part of a saved template. 
5-Automation can make a huge mess of things and needs a complete overhaul 
6- COPY/ PASTE of even the simplest midi track results in random weirdness that cannot be explained.  
7- User preferences should be set in stone and we should not have to keep resetting settings like Comping. I don't use comping yet it keeps being reset to this and I keep having to change it back to Overdub. There are many more settings that we should be able to set in preferences once and forget. There are many setting that should be but are not included in preferences, like the Export settings.  
 

I have had my pan law setting randomly changed in projects many times and it was a huge PITA as I wondered what was different about my mixes. I've also had my snap magnetic setting changed on many occasions and that's also hugely frustrating. Like plugin settings, Sonar should ALWAYS preserve settings that the user has specified. The same applies to any software program really - if it's messing with your work and your preferences without you touching it then it's a turkey.

richardskeltmusic
Having taken advantage of the Studio One offer over christmas so I can take a valid reality check - what really has come into focus is how often I accepted Sonar crashes, and the biggest of all was the weird mis-alignment problems I had when loop recording.  I still am puzzled that I seemed to be the only win 8/steinberg UR44/SPLAT owner who had those problems but there you go..... S1.3 doesn't give me that grief.

I logged bugs to do with looping misalignment that were never addressed and I suspected it had something to do with some core engine functionality that would have taken a big rewrite to fix. The looping issues have nothing to do with your interface and didn't just affect recording. Automation becomes misaligned when looping as well.

PRV filter settings are not saved with the project.
In most of my projects, I have several instances of PRV docked in the undocked multidock, each with a different filter applied. When I open a project, the different PRV instances all look identical and display the same instrument, i.e. the one that was displayed last before the project was closed. I also have one particular screenset dedicated to midi drums. When I open it, the PRV doesn't show the drum map until I set it up again.
 
This issue is a showstopper for me. It's the main reason that I ended up reverting to an earlier release. I've been sticking with 22.11.0.111, which has fewer problems.

With all these bugs I can see why Sonar went the way it did.

dappa1
With all these bugs I can see why Sonar went the way it did.

 
 
I have to be completely honest, im not sure why you haven't been banned again (along with your IP).
You seem help no one and only troll users on this forum.
 
 
 

Biggest one for me is the MIDI arpeggiator causes playback to hang for about 10-15 seconds before starting to play. Not all the time, but often, especially in large projects. Whenever I use the Sonar arpeggiator (the one in the Inspector, not the MFX plugin) I pretty much bounce MIDI clips and then turn the arp OFF so that it gets Sonar working properly again.

Not sure they had a working bug tracker any more. There is certainly the problem reports forum for anyone to see.