David Baay

I have never encountered a case of "no sound" that couldn't be resolved by identifying the specific root cause and addressing it directly. Replacing a synth or track is just incidentally addressing the root cause by setting eveything to defaults and re-initializing the synth. Though there are a truly astounding array of possible causes of "No Sound" that sometimes make the brute-force solution more attractive than taking the time to troubleshoot properly, I will mention one of the the most insidious and confounding possibilities which is that RPN/NRPN messages in third-party MIDI have silenced the synth output which can be addressed by re-loading the synth by the Bypass/Power button in Synth Rack and enabling 'Do Not Intercept NRPNs' in properties and/or deleting them from the MIDI clip using Select > By Filter.

That is not typical and most likely due to some specific plugin that is misbehaving or possibly some other configuration or hardware/firmware/driver issue that needs to be addressed at the source. And whereas the root cause would likely also affect earlier releases of Sonar and CbB, it doesn't belong in this release-specific feedback thread; you should bring it up in a new thread on the Sonar subforum or report it to Support for troubleshooting assistance. I know of only a few very specific situations in which a project will not start smoothly from 1:01:000, mostly involving the use of hardware synths though I have encountered issues with some VSTs for which other solutions are possible aside from moving the start time to 2:01. Likewise the suggestion to provide some "pre-roll" or alternative measure-numbering functionality to address bonafide cases where starting playback at 1:01:000 is not viable does not belong here; it belongs in the general Feedback Loop subforum where it has been proposed and discussed before.

I did a quick test here and it seemed to be working as expected. When you're not hearing the preview, verify there's signal on the Preview bus. Are you soloing anything when this happens?

Running the tranport triggers Sonar to re-calculate and apply plugin delay compensation.

A partial seleciton has always been dark to differentiate it from a fully-selected clip and has always been a little difficult to see. I just checked back to SONAR platinum, and it was pretty much the same in the Mercury theme. If anything the contrast of a partial selection might have improved slightly. When you split out the section, the clip becomes fully selected so it's light again.

@Tim Cappello Easiest way to get this sorted will be to share the project file. You can strip everything but drum-related tracks and buses out of a copy, and only the project file is needed. PM me if you don't want to share with the world.

But did you open the .CWT file directly to edit it or did you create a new project from the template then try to Save as type: Template with the original template name? The latter approach will not work unless you use a new template name.

No, because you're trying save from a project file to an existing template. Starting a new project from a template and attempting to save over an existing template file will not save the changes; you have to save it as a new template with a new name. If you want to modify an existing template, you need to open the .CWT file directly by browsing to it, make the change and save it. Quirky, yes, but it's always worked this way.

I haven't tried using the free tier with an unsubscribed Bandlab account so don't know what the expected bahavior is with regard to the countdown, but nothing survives a cold boot so I'm guessing that either the countdown is only triggered after some minimum time has passed since the last use or some registry key is not getting set properly when the Sonar process is killed. I would guess the root of the problem is some interoperability issue with the Focusrite driver - e.g. Sonar waiting for a reponse to its request to close ports.

Just to be clear, how are you judging that performance has changed? The only thing I can think of that could have affected performance would be Sonar replacing Sonitus plugins with the new "Core" VST3 versions that might (?) have been removed on rollback. If the affected projects are using Sonitus, try disabling 'Replace if Possible...' under Preferences > File > VST Settings > VST3 Migration with the update installed.

If the new note is more than about 5 beats later than the end of the previous note (and thus the existing clip boundary), Sonar will create a new clip. To avoid this, drag the clip boundary out to where you want to start adding notes.

See 'Record Bit Depth' under Preferences > File Audio > Data

Nothing will get 'fixed' if the Bakers can't reproduce your issue. Are you saying you don't get the double-arrow cursor to drag the pane open? FWIW I also had an issue that the scale pane being closed by default when opening an existing project with Workspaces set to 'None', but just re-saving any project with the pane open sorted that for all projects (and new ones from templates).

There's never been a 'grab-handle' for the scale pane; you just need to hover at the left edge of the PRV notes pane until you see the double-arrow cursor, then click and drag.

For the record, I verified it will not open in 8.5, either.

Meaing it's not available to be checked in Preferences > MIDI > Devices ? Verify Driver Mode is MME under MIDI > Playback and Recording.

Microsoft Support thread on multiple mouse driver instances causing problems. https://learn.microsoft.com/en-us/answers/questions/4083226/i-have-multiple-hid-compliant-mouse-drivers-showin Easiest solution might be too leave them both in place but disable one.

I'm not seeing a problem with dragging either the velocity hotspot on the upper edge of the note in the notes pane or the velocity 'tail' in the controllers pane or Shift+dragging notes around to constrain pitch or time. I have to think something is going on with your mouse/driver. If you're using a wireless mouse maybe change/charge the battery. Do you still have CbB installed and it's working normally?

Working as expected here, and I'm not aware of any setting that would affect this. But the dimming might be a little more subtle than in CbB, depeding on the your color scheme, the track color and the size of the waveform. I do recall it being a little more obvious in CbB with the Mercury scheme.

I don't see why that would be an issue; just leave Volume at 0dB. If you want higher level into the Maximizer use Gain. If it's after some other FX in the bin and you need to control Input level to it put an empty FX Chain ahead of it as msmcleod suggested. Anotherr option not mentioned is to put it in a Prochannel FX Chain, and set the Prochannel to Post FX Rack. Lots of ways to skin this cat without having another routing option that 99% of users will never need.

Choosing left or right gives you one side of the stereo pair. It's just Sonar's default labeling. In Preferences > Audio > Drivers You can enable to show friendly names like Mic1|Mic2 (double-click to edit and use the pipe symbol between the two input names).

Sonar now has Cakewalk ZIP format which can save Audiosnap transient markers and editing. Historically I just used normal zip files. For your legacy bundle files, if you weren't aware of having done anything with Audiosnap, you probably didn't lose anything except Audiosnap being enabled on some clip(s) which initially just performs transient detection without altering anything.

https://legacy.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Playback.19.html See especially the section titled Mono audio clips may be increased by 3 dB in certain scenarios

Try setting Disk I/O buffers back to default (256kB I believe) or even down to 128. I've never had to go over 256 even when using an HDD for audio instead of SSD.

I was just going to ask what's controlling the tape sync when you posted. It seemed likely that was the culprit rather than the EI latency being variable.