Sailor55

Wow! A lot has happened since I've been away. Many thanks to everyone who helped get to the bottom of this. Much appreciated. - D

Thanks... Will do. - Daniel

Also, thanks Colin. I wasn't aware 2024.12 was available. I was using 2024.11. I've just updated to 2024.12 but the problem (as shown in my video above) still persists.

If the note pane is open (it doesn't matter how much, as long as it's not completely closed), then the effect disappears. That being the case (like before), the workaround is to just open the note pane slightly. Still, its a bug, and it shouldn't be happening.

I reported a bug last month where, when using a Drum Map, the velocity lane shrunk horizontally when the drum map itself was expanded vertically. That was fixed in the last version, but... now it seems to have returned in a new form. When you click on any existing note (to move it or to sound it), each time you do it , the velocity lane shrinks vertically until it disappears. As before, this does not happen if the midi keyboard lane is open, even a tiny bit. Please see video. Anyone care to confirm? Screen Recording 2024-12-10 132206.mp4

IMHO, moving to another DAW would be an enormous pain. If one is proficient at the many features of CbB, then moving to Cakewalk Sonar is completely painless. I actually found it to be a positive, enjoyable experience. My advice... get a year's subscription and don't look back.

I occasionally have this problem too. I am always able to fix it with Ctrl-Alt-Del and then simply cancelling the "sign-out/change user" window that pops up. When the Sonar screen returns the cursor behaves normally again. Don't ask me why. Magic.

Thanks. I have submittet a bug fix request.

When using the scroll wheel to widen or narrow a drum map midi track (horizontally), the velocity window (if opened) will concurrently narrow (vertically) until it disappears. This happens regardless of the method used to zoom horizontally. But... if you open the keyboard midi window too, no matter how little (as long as it's not completely closed), this behavior stops. I don't think this is intended.

I was a CwB user from day one. In order to get Bandlab Sonar, I paid full price for a one year membership on Aug 31. I've never once received any offer from Bandlab (either before or since) for any discount whatsoever. I'm not complaining. Just saying. I'm quite happy with the product.

Agreed. I accepted reality about two weeks ago and moved up to the New Sonar. I quite like it. No looking back. - Dan

Good suggestion, but it makes no difference, pre or post. I think you are correct. It was wrong of me to think the bus was somehow sounding "through" the guitar track. In order for the the guitar track to be soloed, its effects must also function or it isn't truly a solo . In order for that to happen the vocal bus must be 'active' too. That means you will hear it through the master. I guess it's unreasonable to expect Sonar to know that when a track's effect is side chained to a bus it should be aware to also mute the bus (and yet, still feed it to the side chain) when the track is soloed. I think the mystery is solved. The use of aux tracks is probably the best the way to go in these situations. My thanks to you both for helping me to think this through and improve my understanding.

The vocal bus output goes to the master bus which outputs to my Focusrite Scarlett 2i4 interface.

When the track is muted the bus is still heard even though the track itself does not sound. Very strange. The only way to stop the bus coming through the track is to reassign the send to "none" or else to delete it. Lowering the send volume to -inf and even disabling the send will not stop the bus from sounding through the track. You can't even stop it by disabling the effect to which it is sending. Thanks for clarifying this. It is very useful to know. Since there are two or three ways to overcome this issue, it's not really a showstopper, but as far as I'm concerned you should be able to send from a buss to an effect input on a track. I don't think you can 'send' to a normal track anyway. When you go to insert a send, normal tracks are never offered up as a destination. You only get the option of aux tracks, patch points or side chain inputs to effects.

That certainly makes sense to me. But in this case, I wasn't 'sending to a track' (from a buss) so much as I was sending to the side chain input of an effect on a track. The Waves C6 side chain input is intended to control compression of a specific band. And in fact, it actually does do that. However, it baffles me as to why that should also route the send through to the track output as well.