David Baay

Synth/version unavailable…? How long ago was it frozen?

Interesting, but doubtful the OP went that deep. I had hardware synths with GM modes that sounded better so never used It that much.

I had the same thought, but don’t think it’s possible; drums are strictly channel 10 for GM compatibility.

TTS1 has 4 stereo outs that can be used as 8 mono outs with instrument channels panned hard left and right, but it’s not possible to separate drums. When you have multiple MIDI tracks driving TTS1’s drum channel, the MIDI Volume level of the last one will override the rest. The only way to mix kit piece levels in TTS1 is using MIDI ‘Gain’ which is actually Velocity Offset.

Show all track controls, select all drum tracks and hold Ctrl while changing the Output of one - or use the Output control in the Track Inspector. This assumes they are either audio tracks or Synth/Instrument tracks, of course.

Yes, I’m sure this is what DeeringAmps meant when he wrote ‘send’. Try this first; it’s the conventional approach.

Based on the orginal post and title I made the istake of assuming the Q25 was a drum contoller with onboard sounds. Appears it's just a class compliant controller keyboard with no driver as John noted. So nothing special is required to used it, and MIDI latency won't necessarily be that terrible even without a dedicated driver. My guess is the OP's issue was more likely due to plugin delay or audio latency - as scook suggested - than to poor MIDI performance.

No that's the legacy Cakewalk purchase page that is no longer viable. Sonar is now subscription-only, and there's only one tier that is now the equivalent of Platinum in terms of features but has less bundled plugin content: https://www.cakewalk.com/sonar But you should not be having trouble with multi-track freezing unless one of the tracks in your selection is in a state that doesn't allow freezing (e,g, archived or no MIDI events). If each track/pair will freeze by itself, all selected tracks/pairs should freeze successfully. I don't kow why sjoens was seeing inconsistency.

An audio interface of some sort would be needed to monitor/record the Q25's onboard audio through/into Cakewalk, but used as a MIDI controller to drive a drum VSTi in Cakewalk as the OP suggested, nothing else is needed; it would just be a USB-MIDI controller in that case.

So far as I know, the mouse wheel is the only way to scroll the Inspector. In addition to using Full Screen mode as suggested, you can quickly toggle the Control Bar closed/open by the default shortcut 'C'. You might also consider removing less frequently used modules from the Inspector by the Display dropdown at the bottom. But ultimately, CbB/Sonar really need a little more vertical resolution; 1200 is sufficient.

Dragging out a selection of multiple clips will get you one file per clip, whether separated by time, tracks or lanes of a track.

And just FYI for posterity, Sonar has since added an Absolute Time offset (milliseconds) option to the Time+ setting in the Inspector which is easier to use than the articulation-based offset if you just need one fixed value for a whole track.

+1 And do it in a second lane of the track and then bounce to clips if you want to combine notes and controllers. FWIW, I'll add that I find my pedaling in actual performance has the pedal being released just after the barline (or any chord change), producing a little overlap on chord changes. Here's a pair of up/down pedal controllers quantized to the 1st and 3rd 32nd (120 and 360 ticks) after the bar and configured as a MIDI Groove Clip. Groove Clip - Sustain Down 120, Up 360.mid

If the project timeline isn't synced to the Karaoke track, the simplest solution may be to apply Drum Replacer to the Karaoke click and replace it with whatever drum sample you want to use. If the timeline is already in sync, you can simply change the Metronome to MIDI mode, and ouput it to Juno. You'll have a little latency due to the MIDI OUT and monitoring the Juno through CbB, but it should be tolerable if your ASIO latency is low.

I see where you're coming from but I think track-to-track routing with a patch point model makes more sense for consistency with the way audio distribution works, and because it means each synth would have a MIDI track (or MIDI half of an Instrument track) in between it and the source that can be used for synth-specific Velocity and Time Offsets, MIDI volume and pan contro/automationl, MFX inserts, additional MIDI events, etc. And regarding Input Echo, this gives you the option of interrupting MIDI to one of the synths without disconnecting it.