Rasure
*Something not right with aux tracks...

 
Yes, and in a way that's hard to pin down. I get weird behaviour using external inserts on a track that has its output set to an Aux track. Solo buttons don't behave correctly in some situations where Aux tracks are somewhere in the routing. Sorry that I can't be more specific.

Rasure
*Automation sometimes doesn't work.

 
I often find that bus automation stops working. Sometimes it works on some clips while not working on others. Closing the project and re-opening always puts it right again.

change the view to audiotransients has the problem, that a lot of the markers are not at the right position(the threshold has nothing to do with this problem),
In percussive material it really should not be any problem. So I first have to delete all wrong markers or drag them to the correct position before i can quantize the snare. That takes so much time

With regard aux tracks, could it be possible that you don't have input monitoring enabled on them? You need to have that enabled to hear them. Got me a few times. An example of poor design rather than a bug though - it's really counterintuitive and almost certain to cause confusion among people who, quite reasonably, presume that an aux track should be heard straight out of the box without having to enable anything. 

sharke
Well all I can say is that I hope they take their time and don't feel pressured by the market or the Cakewalk community or anyone else to resurrect Sonar ASAP. I'd love to see them start something from scratch, helped along the way by the inclusion of Sonar's good parts. 

Oh now, sharke, I know you can say more than that  
 
But seriously, Amen; I couldn't echo your sentiments more. I do get the sense that Meng/BandLab have the right combination of deep pockets AND good vision to see something like this through in a good way. So for me at least, there is hope and a great deal of interest.

sharke
Another example is the fact that hitting the "show automation lanes" button when no envelopes already exist automatically creates a volume envelope which takes control of the volume fader whether you want one or not,. When I suggested that hitting this button should result in an empty automation lane in this scenario, I was told that it was not possible for an automation lane to have nothing in it.

If that's the case, surely the easiest thing would be to popup a confirmation dialog at that point - or even better a dialog asking you what sort of envelope you want... with a cancel button.
 
M.

msmcleod

sharke
Another example is the fact that hitting the "show automation lanes" button when no envelopes already exist automatically creates a volume envelope which takes control of the volume fader whether you want one or not,. When I suggested that hitting this button should result in an empty automation lane in this scenario, I was told that it was not possible for an automation lane to have nothing in it.

If that's the case, surely the easiest thing would be to popup a confirmation dialog at that point - or even better a dialog asking you what sort of envelope you want... with a cancel button.
 
M.

I think the easiest and most logical behavior would be for an empty lane to appear, ready to be populated by whichever parameter you choose from the dropdown. I'm pretty sure that's how the vast majority of people would expect it to work. 
 
That's if they want to retain Sonar's basic automation functionality of course. Doing a ton of automation in Reaper really opened my eyes as to how much better it can be. A button brings up a huge window showing every possible parameter possible to automate, from basic mix controls to all of your plugins and synths. Each plugin's parameters can be collapsed if there are too many and you want to get them out of the way. Every parameter has "visible" and "arm" checkboxes, and when you click "visible" on a parameter it creates a lane for it. So you can select all of your automation parameters in seconds with just a few clicks. Compare this with having to click the "+" button and scroll through a huge menu list just to create one lane in Sonar. And in the Reaper automation dialog you can choose to show all active lanes or hide all of them, or choose which ones to show on a lane by lane basis. Then you can resize them all independently of each other. It works so well that when I go back to Sonar's automation now I get incredibly frustrated. 

msmcleod

sharke
Another example is the fact that hitting the "show automation lanes" button when no envelopes already exist automatically creates a volume envelope which takes control of the volume fader whether you want one or not,. When I suggested that hitting this button should result in an empty automation lane in this scenario, I was told that it was not possible for an automation lane to have nothing in it.

If that's the case, surely the easiest thing would be to popup a confirmation dialog at that point - or even better a dialog asking you what sort of envelope you want... with a cancel button.
 
M.

 
I am always peeved when someone says something is "not possible" to implement in software. The devil is in the details, though. For example, somebody may have started the lane count with an increment of zero, so that the first lane was "harcoded" and hence tough to resolve as an empty count. (There are stable workarounds for this too, of course.)

Question are your waves plugins cracked or not current version?

I used to have this problem until I went legit with Waves and afterwards plugins losing their settings stopped happening to me.

ONE used to be able to CTRL+CLICK+DRAG IN/OUT to STRECH an audio clip...no more.
 
ONE sad...
 
as it was shall it be again?
 
YES ONE!