David Baay

See the videos linked at the bottom of this post by John Vere for an analysis of the alternatives to the no-longer-included TTS-1 and no-longer supported GS Wavetable:

If you have 'Use ASIO Reported Latency' enabled under Preferences > Audio > Sync and Caching, that should largely be compensating for the input latency. There's always some additional unreported hardware/firmware latency that needs to be compensated by entering a value for Manual Offset, bbut this is usualoy on the order of only 30-50 samples - approximately a millisecond. Normally, I would recommend using the Centrance Latency Checker to find the actual RTL, but since your output and input devices are using different drivers, that's not going to work. First, make sure that your Record and Playback Timing Masters are referencing the correct drivers and note the ASIO Reported Latency in samples (sames as Total Roundtrip reported on the Driver Setting page). Then disable latency compensation temporarily and re-record playback of a clip with a single sharp transient - like a single Metronome click - with the mic right up against a monitor. Change the Now Time readout to samples and use the Now Cursor positioin to count the number of samples from the source transient to the uncompensated recorded transient; this is the Actual Round Trip Latency. Subtract the Reported RTL from that Actual RTL figure, and that's what you need to enter for Manual Offset in samples. Enter the offset, re-enable compensation, and try re-recording again.

It's not necessary to set Input channels or controller transmit channels, only the forced output channel ("C" widget in the track/inspector).

That's my go-to for a GM hardware synth.

I see OBS Studio in you taskbar. Does this issue persist if that's shut down?

If you save the "template" as a project file , you can effectively get that result by dragging the project file into an existing project from the Browser. You could even create a dedicated folder for such "template projects" in your Content folder. I have used this method to update pre-audio MIDI projects by dragging them into a new project started from an appropriate project template.

Better yet... Don't do that! You'll get a more musically satisfying performance by leaving some of the variation that results from eyeballing (or earballing) an approximate match to a target velocity. Mathematically perfect regularity is the enemy of musicality.

There seems to be some confusion here about Track Templates vs. Project Templates. You save a Project Template by File > Save As and changing the file type to Template which generates a .CWT file from which you can start a whole new project. What you want is a Track Template which can be generated either by Export > Track Template or by right clicking the selected tracks(s) and choosing "Save as Track Template", both of which which generate a .CWX file that can be used to Insert tracks into an existing project.

Step Sequencer clip? You can’t move part of an SS clip.

You’ll need to insert a dummy MIDI event at time zero in each track - something innocuous like CC123 or CC64=0.

CW should import the initial patch change to the Patch widget and put it back In the file on export.

Probably more about syncing controller events or cues to real time; ticks are finer resolution than ms at any tempo above 62.5 bpm anyway. Best alternative is to keep the Now time visible in the desired mode. From, Thru and Selection times can be changed to SMPTE in preferences and maybe seconds as well - not sure about that.

I meant do all the controller manipulation within CW. But if some non-MIDI data need to be added, then CAL can’t help.

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.