David Baay

Too many cooks serving too few customers. 😜

Ripple Editing should also address this workflow.

PC keyboard ‘X’ toggles aim assist. Alt+X toggles the position display. The Now Cursor misdraw is a bug. Tabbing away from CW and back can sometimes cause and/or correct this as can opening/closing Preferences.

Best option is probably still to use a 3rd-party app that supports export to text. Or get familiar with CAL scripting.

Because too many users work around issues without formally reporting them with a demo project so the Bakers have a chance to fix something if the cause isn’t external.

Try moving a Volume control all the way to 0 during playback. If your setup is as described, I guarantee all the drums will be silenced, and if you look at the fader for the drum channel in the TTS1 UI, it will be all the way down. If that track is not the last one, the volume will come back up to the level of the last track when you restart playback

Time Offset is intended to compensate for synths with a slow response or attack. If the MIDI events are early or late in the timeline they should be moved to correct timing by any of the many methods, depending on the situation. This is especially important for to have the staff view display correctly.

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.

I have a first-generation MOTU MIDI Express XT that still works fine, but I replaced it with a MioXL because it was slow (MIDI RTL ~11ms). The MOTU had fairly basic routing capability and was not hard to master. The mioXL can host USB and LAN connections as well as MIDI DIN, configured by an app, and I had to write an extensive 'usage' doc for myself to translate the manual into terminology and that made sense to me and keep track of the configuration. The problem with hardware solutions is that the project then becomes dependent on the hardware being available and configured correctly and that can fall apart when you migrate to a new machine or add some other hardware to your system, but they are a necessary evil if you use old hardware synths and controllers with only DIN connectors.

Though you may not be using it, the Yamaha-Steinberg installer likely installed the Generic Low Latency driver. Check is there's a key for it under HKEY_LOCAL_MACHINE\SOFTWARE\ASIO in the registry and remove it if found.

All that's needed initially is a one-to-many patch point solution, like audio patch points, where you would output a MIDI track to the patch point and it would appear as an Input for other MIDI and Instrument tracks. Eventually MIDI 'Sends' could be implemented for additional flexibility but that's not essential. CodFN42's MIDIChFilter fits the bill but forces you to have a dummy synth track assigned to its output which partially defeats the purpose of having fewer tracks to deal with (though it can be hidden). It also adds another plugin to your synth rack that could otherwise be invisible if the feature were built-in. And I've recently discovered an issue with using MIDIChFilter in Project Templates that makes it not an ideal workaround. I've asked the Bakers to look into this as it could cause problems with other MIDI OUT-capable VSTs.