David Baay

Yes, by design for people without hardware; originally you wrote "people with hardware". That's what I was correcting

I think you mean for people with NO hardware MIDI devices connected.

Yes, the FX button also operates as a bypass/override. There has been a lot of virtual ink spilled over the arguably unintuitive and inconsistent labeling/lighting/functionality of these and other buttons in the Mix module. If we're lucky, the new Sonar will revise the iconography at least.

CbB is loading TTS-1 because the GM/GS Wavetable is not longer supported in CbB so its MIDI port is not available and you have no other hardware MIDI ports available. If you don't want to use TTS-1, you'll need to get an external hardware GM sound module or a multitimbral keyboard synth with a GM mode.

Yes, as the documentation shows, the button is to "Override" PDC on "live" (input-monitored) tracks. Note also that you can only override PDC on an input-monitored track if the PDC-inducing plugin is not on that track or in its path to the output.

Ooh, good one!

Most likely due to Inadvertent imbalance of the separate L-R level controls on the "Main Out" hardware bus in the Console (drag the splitter at the far right to the left if you don't see it). You can double-click to reset them, and then click the Lock button to keep them together. EDIT: I always recommend exporting just the Master bus, anyway, because having a send to a secondary hardware out for any reason (e.g. a headphone mix) will get you in trouble with the two outputs being merged with Entire Mix.

Quick-grouping should work with freeze buttons. Ctrl+A to select everything, then Ctrl+click a freeze button.

Did you re-install the MOBO Chipset drivers? I haven't built a system from scratch for quite a while so maybe Win10/11 take care of this for you, but it used to be SOP for a fresh O/S installation.

... And I'm going to glom on to every CbB-is-flaky-unintuitive-and-unpredictable thread and write "This Happens to Me Too!!! And what's more , it does this other entirely unrelated weird thing when I mis-use it instead of reading my mind and doing what I want rather than what it's designed and documented to do based on the change I made to Preferences and promptly forgot about".

Not sure why you want to have two identical lanes of notes, but the behavior you describe would only happen if the clips are Linked (as indicated by fine dotted lines around the perimeter) which may be your default for Editing > Drag and Drop in Preferences. Right-click one of them and choose Unlink > Independent.

The only way you get overlapping notes like that is by editing or bouncing. It's not possible to record overlapping notes in single take from a controller unless it's sending on multiple channels and you're not restricting the input channel. If they are the same duration and 100% overlapping I can see you wouldn't be able to avoid selecting both by lasso as the whole purpose of lasso is to select everything in the time and pitch range the lasso encompasses, regardless of whether it's visible or not. In any case, I don't think it's reasonable to expect the DAW to be accomodate a situation that you can only get into by user error, and I'd be very surprised if lasso works differently in some other DAW. EDIT: Ironically the "merge" feature being requested here would actually make this scenario of overlapping notes and the resulting editing challenges more likely.

Not sure what you mean by "marking" or "stacking"...? Can you give a specific example? EDIT: All this discussion about editing should really be taken to a new thread since this FR is about recording.

If you show lanes, you get a composite clip in the parent track, and the unwanted lane/clip/overlap creation when editing is likely due to having Non-Destructive MIDI Editing enabled in Preferences > Customization > Editing.

Not sure what you’re getting at. OP is asking for takes to be merged into the same clip. Once you do that there’s no easy undo in a lot of cases.

Only one lane in the track? If you can strip down a copy of the project to just that track and still reproduce it, you might share that so we can try it.

Resave your Workspace without it.

Yes, the documentation makes it clear that Dim Solo operates at the track/bus level.

I haven't checked for a while, but I believe it's still the case that CbB renders mono synth outputs 3dB higher than live playback. In that case, you need to freeze the synth before final mixing (kind of a best practice in any case). I tend to use stereo synth outputs for everything to avoid this, but if you use independent outputs from a drum synth, those will tend to be mono so it's necessary to freeze in that case. If you mix the drums in the synth and only take the stereo "Master" output (or Master plus separate stereo room and overheads) you can avoid this. EDIT: I re-checked this and confirmed mono synth tracks still gain 3dB on freezing, but not on bouncing/exporting; the level of mono tracks is correct in that case. So this would not account for the OP's issue as I thought it might.

Custom keybinding and that key is sticking on your keyboard? Not sure how else that could happen or how it would only affect some project files.

Check the the Event List view for NRPN messages and delete them or click the VST2 dropdown at the top of SI Electric Piano, go to Plug-in Properties and enable "Do Not Intercept NRPNs". Incidentally, an Instrument track is a combined MIDI and synth Audio track so you can drop the MIDI right in the Instrument track and get rid of your separate MIDI track.

CZ V is working as expected here; not even really seeing a significant delay in drawing the UI. This is with onboard Intel video on my laptop. It also has NVIDIA RTX that I don't normally enable for CbB, but I could try it. I would agree this is likely an interoperability issue between the OP's specific graphics engine and the way Arturia has implemented some feature. Hard to say who's at fault. First step would be to try it in another DAW on the same machine.

So if you just disable the Sonitus Compressor or the Mystique Tape Saturation plugin, which one is silencing the Master bus output? I'm thinking maybe you have the Compressor set to monitor the sidechain input, and there's nothing there.

In my experience, clips that are exactly 2 beats long or a multiple of 4 beats with strong beats on quarter notes get looped properly with no intervention. If they are some other whole number of beats long or have a lower or higher-frequency of strong transients (e.g. a slow kick/bass pattern or a fast arpeggio or percussion pattern) you generally just have to correct mis-guessed Beats in Clip value. The only time I see things really get screwed up is if the clip isn't trimmed to a whole number of beats and/or the timing of clip is radically out of sync with the project tempo to begin with. I'd be interested in seeing examples of clips that don't Groove correctly and aren't readily corrected by trimming and adjusting the Beats in Clip value.

Quoting myself here, I have to retract this statement. As I posted on the Pianoteq forum, it seems the difference I was hearing and measuring was mostly due to FX in CbB differentially reinforcing the more prominent low-mid frequencies in the new voicing. In other words, my FX settings were already modifying the tone in same direction as the re-voicing.