David Baay

Appears to be working in general here. Can you give a specific example of where the meter changes occur, what you're moving from where to where and how the result differs from your expectation?

I think you must be remembering some 3rd-party keyboard app.

Yes, that Generic Low Latency ASIO Driver is a Steinberg thing - usually installed with Cubase, but I think some other audio softwares leverage it as well. As Mark said it's that 'aggregate driver' tying up your dedicated Tascam interface driver when it's enumerated on startup that causes the problem. The Steinberg driver is a known cause of issues in Sonar for this reason and needs to be uninstalled. I've never had it, but I assume that can be done through Windows Applications and Features. If not you can just remove its key from HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

Actually I undersold Mix Recall a bit; it can recall different bus and plugin configurations as well as their settings in addition to automation and more: https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.48.html

See the Mix Recall module. It can't change the content of a project, but it can the state and settings of EQs.

Feature requests belong in the general Feedback Loop subforum. This thread is for feedback/questions/issues specific to the 25.08 release.

Try: - Disabling the 64-bit Double Precision Mix Engine. - Bypassing all plugins via the Fx button in the Mix module.

From what souce... a hardware MIDI keyboard, Sonar's virtual MIDI controller or something else?

Yes, strange. I had already created a more recent AD2 track template but hunted up an old one on another machine dating to the Platinum era. It loaded fine as did a re-saved copy.

Did you verify AD2 actually isn't present in the Synth Rack or is it just that a drum map loaded incorrectly or has the wrong output assignment so the tracks are silent and/or clicking the synth icon in the track doesn't open the AD2 UI? If CbB and Sonar are referencing their own specific Drum Map folders rather than a common one, the drum map might be wrong/missing.

There have actually been a number of issues over the years that were locale-specific. This could definitely be one.

Yes, notes/waveforms automatically take on the color selected for the track while the background remains dark by default. You can uncheck Use Track Colors in clip properties and set custom foreground (notes/waveforms) and background clip colors independently of the track color. The foreground will initially be assigned the current track color.

I also generally insert tracks and buses by right-click; they are always inserted above/ahead of the currently focused track/bus.

What interface and driver mode? If onboard audio with WASAPI Shared, try WASAPI Exclusive. Try Reset Config File in preferences. Sonar will back up AUD.INI and create a new default one.

Can't say I've ever seen that, and can't imagine what meaning or utility it would have. I'm gonna go with "glitch".

Yes, new feature for better visibility of looped clip boundaries. I was thinking to just initially exclude everything and see if that changes anything; if it does, you know the cause is some plugn(s). If not we move on to other possibilties. I'm wondering also if you temporarily disable all audio I/O drivers in Preferences if the project will open (notwithstanding Sonar's complaining of no audio devices, and Master bus ouput getting set to None - don't re-save it).

Is this happening with different projects? Certainly seems like the kind of thing that would be caused by a problematc plugin. Try Shift+clicking the .CWP file in Windows Explorer to open it in Safe mode and exclude any recently added plugins.

First things first: you should change "CbB" in the title (and "cakewalk" in the body) to Sonar.

Not seeing that here. For me it just pushes the previously focused bus and all buses after it one position to the right as you would expect. I can't think offhand what config setting might affect that. Could be related to the position and docking status of the Console; what's your diplay setup and window layout?

You're using Spacebar to play/pause? You wouldn't happen to be using a Focusrite Scarlett with the recently released - and apparently problematic - driver update...?

I can confirm that build 035 scrolls two tracks at a time when clicking the scroll arrows, regardless of track heights. I don't have CbB on this machine, but Platinum 17.10 goes one track at a time. Incidentally, would be nice of scrolling by mouse wheel could be made to 'snap' by one track at a time, keeping the top of each track registered with the top of the view. Neither Platinum nor Sonar do that.

Noel beat me to it.

It only happens at 1:01:000? If it doesn't also happen when starting playback further into the project, it's not the audio engine. What audio interface and driver mode? Did you maybe have a non-zero Fade On Start value set in older versions that was obscuring the click? Maybe share a simple demo project just to be sure it's not the project itself. Try disabling the 64-bit Mix Engine. Also try Reset Config to Defaults in Preferences > Configuration File. Sonar will back up your AUD.INI and replace it with a default.

No, playback basically stops as fast as it can wherever it is. I find Tab to transients/notes and Next/Previous Measure shortcuts to be pretty handy for getting back or forward to a note on which I intended to stop. I have the latter bound to single keys so don't have to hit a modifier.

Yeah, all bets are off when it comes to level consistency from live synths. Samplers/Romplers will generally be pretty consistent, depending on what internal FX are used, but anything that does 'real' synthesis or uses physical modeling is likely to be a lttle variable. And I second Jonesey's comment about digital clipping. When I first read it, I thought you meant -.5dB and had just left off the minus sign. It's common mix to -.3 or -.5 or less to allow a little headroom for intersample peaks and/or conversion to MP3 which can result in a clipped peaks if the source is at 0dB.