Kylotan
Of course, as I've said in the past, Sonar shouldn't be second-guessing users and placing things at a different location like the Now time or whatever. If I haven't explicitly clicked on the timeline to say where I want something to go after the cut or copy operation, it should appear at the same time it was cut from when it is pasted.
I must admit I as well find a lot of these seemingly simple and rudimentary tasks to be overly awkward and complex in Sonar. I should not have to reference the manual for basics functions like copy/pasting (and that's just one example... I will avoid whining about automation yet again... lol).
I do understand why in this particular case (being handling of MIDI instructions) have so many layers of complexity. Without them a lot of power would be lost in how the data can be manipulated and managed but definitely, as you implied, perhaps there could be a system whereby a simple and logical default action/methodology is established for things like the topic of this thread. That being a simple Select, Copy/Cut and Paste move works how most would intend it to (all position/timing properties are retained and a duplicate of what has been selected just goes where it should based on the original data without any extra futzing).
If the user needs more advanced copy/pasta functions or wishes to insert to the Now Time or any of the bazillion other fancy things we may need they can start using modifiers or the "Special" dialogs (which could maybe use some updating if this is to work).
I get it though. It's hard enough to create a program that can perform all these tasks but it's WAY harder to design things to be user friendly enough to anticipate what MOST people would be attempting to do with such maneuvers.
Then there is the matter of changing things this late in the game which would inevitably disrupt many people's workflows. Still worth a shot... just as long as people are made aware of it and can customize the program to NOT have these user friendly simplifications overtake their workflows. But that again is another huge design/programming nightmare.
For Sonar though... if they want to have a broader appeal to the average musician and beat out the other guys this IMO is exactly the direction the team should be taking. Make it less awkward/cumbersome to perform general tasks in all commonly used areas without sacrificing complex functionality and I think people will be more likely to warm up to Sonar.
A perfect example, for me, of how the Cake team has really simplified an entire aspect of production is the "Inspector" and "Prochannel" concept. Just being able to mash "I" on my keyboard and having access to all sorts of crap I'd otherwise have to dig for and futz with is a huge bonus. I hardly ever have to use standalone plugs in the Bin/Rack and even then I'm actually preferring just using an FX Chain PC module instead so I can tweak things much more easily. I also think the new Comping stuff, although definitely a jewel in the rough, is another idea (once understood) that simplifies things (instead of constantly having crop, fade, mute/unmute crap one step at a time).
If they could get a bit more lucidity in some of the other areas (okay... gonna take a swipe at automation again... but seriously it needs work) and continue to refine the areas already noted I would be quite happy. I'm also not finding these "performance" improvements doing anything for me. Quite the opposite actually since X3 so maybe it's time to finish the surgery, stitch up the patient then focus on some workflow enhancements.
Of course Im just a rabid "fanbois" so what do I know. lol
Cheers.