David Baay

It can be shortened to: - Ctrl+A - Alt+A - Clip Follows Project But it's best to check the follow mode first.

Selecting a range by right-clicking a meter overrides the default you have set in Options. Reselecting that default (or a new one) should reset any meters that have had the default overriden. Working here.

Yes, if you don't set an output channel, Cakewalk defaults to sending controllers from track widgets on channel 1.

EDIT: Re-read the OP that it can be off the grid either way, so it's not Snap Offset Another possibility: Snap to Landmarks enabled, and aligning with other MIDI notes/clips...?

How many measures is that? I think Step Sequencer has a limit of 64 beats = 16 measures of 4/4.

As an example, here are the channel assignments for parts in the 4-layer Indie Drone.st3m. They should all be channel '0' to work properly in ST4: <MultiPath>/Volumes/BACKUP/IK Multimedia/SampleTank 3/Multis/Syntronik/J-60/Indie Drone.st3m</MultiPath> -<Part0> <MIDIChannel>0</MIDIChannel> ... -<Part1> <MIDIChannel>1</MIDIChannel> ... -<Part2> <MIDIChannel>2</MIDIChannel> ... -<Part3> <MIDIChannel>3</MIDIChannel>

I assume you're talking about input monitoring latency; is that right? Can you share the project file with no plugins and no audio files?

Yes, Audiosnap and Groove/REX clips are incompatible. But you can have a mixture of Audiosnapped and Groove-Clipped audio in the project. I didn't think this was probably relevant of the OP, so didn't mention it. And you need to be sure to set the Follow Option to Autostretch before enabling Follow Project. The other modes will immediately try to fit the the clip tempos to the project, and usually not do a good job because the clip tempo maps are wrong. Otherwise, so long as you haven't messed with clip Timebases or are other timing/stretching related settings, it should work pretty consistently. Crashing is not something I've encountered before, but I don't use it a lot.

Make sure you are set to Snap To, not Snap By. Easy to miss in the PRV because it only shows when you have the resolution pick list open.

Sounds like you set the experimental 'Aggressive' ThreadSchedulingModel=3 in AUD.INI (Preferences > Audio > Configuration File) that was introduced as an option in the 20.01 release. It was not enabled by default, and many have reported similarly bad results from trying it. Steadily increasing latency was one of the symptoms. Unfortunately, some made the change, and then didn't recall having done so by the time they discovered problems.

The Tempo Ratio function you might have read about went away a long time ago with the introduction of support for audio since stretching was not supported at that time, and it never came back. You can manually change the project tempo and MIDI will follow, but audio will not by default. To have the audio follow the change both visually and musically: - Ctrl+A to Select All (doesn't matter if MIDI clips are included) - Go to Clip Properties in the Track Inspector, and expand the Audiosnap section. - Click to check the Enable box. - Set Follow Options to 'Autostretch' - Click to check the Follow Proj Tempo box.

Assuming individual tracks are not hitting 0dBFS when their input Gain and output Volume controls are at 'unity' (i.e. 0.0 - no gain or attentution from what was recorded in the .WAV file), check the level on the Master bus. The levels on individual tracks may be okay but sum to clipping on the Master. Cakewalk provides essentially infinite mathematical 'headroom' for summing inside the box, but the D/A converters on the soundcard/interface will be clipping if the Master bus is peaking above 0dBFS. You can pull the input gain on the Master down, but it's best to lower output Volume faders on the individual tracks.

+1 to everything Steve said, except I think he meant to label that last link 'PDC button'. ;^) The latency is primarily on the audio side of the process, and the onboard GS Wavetable Synth will have ~50ms of extra latency vs. a soft synth like TTS-1. I recommend uninstalling ASIO4ALL, and using WASAPI Exclusive mode which should allow you to get the buffer all the way down to 3ms for a simple project (Preferences > Audio > Driver Settings > Buffer Size).

I'll have to do some more testing to confirm, but it seems PDC can have an effect. Disabling two instances of LP plugins and one of Transient Shaper eliminated glitching in one project I checked, and disabling only two of them had no effect. PDC had to be completely eliminated to eliminate the glitch in this case. Also, since timeline-seeking is involved, the OP might want to check the setting of 'Set Now Time with Full Restart' in the Track View Options menu. Having this enabled can cause glitches in manual timeline-seeking.

See View > Grid Resolution > Follow Snap Settings in the PRV menu.

With four bars showing in the PRV, 8th notes are quite large, even on my laptop. 'Fine-tuning' 8th start times/durations is pretty easy at that zoom level. I must be missing something...?

Could be done pretty quickly with a little batch scripting, but I think we should make IK Dev do it.

Cool. Let me know when you're done re-saving them all, and I'll ping you an e-mail address. ?

Sweet. Resisted the urge to pick up bx_oberhausen at $49.99, but taking another$25 off put it firmly in no-brainer territory.

Yeah, makes me wonder if saving changes from ST3 would not have broken the authorization. I didn't stop to look and see what was in the modded files to make them so much larger.

@Noel Borthwick what should we expect when using plugins that induce a lot of PDC?

Checked out loading multis in Syntronik. Turns out part of what I was missing is that you have to click in the center of of the browser/selection field within the Multi Panel. If you click on the layers icon at the left end, you get no dropdown - not very intuitive. So I can see and load multis, but the ones I edited in Sampletank to set all layers to channel 1 and re-saved now throw an "Instrument not authorized' error for each layer in Syntronik. I found a thread referencing this on KVR, but it implied this would only happen if you edited the individual instruments and/or changed names, and tried to share it with another user. I didn't change anything but the channel assignments, so it's not really clear what's going on here, but I'm guessing that reinstalling the relevant sound set will fix it. Fortunately I only modded a handful of multis. Not cool that making such a minor edit breaks the authorization. No crashes here, yet, but IK not making a really good first impression on me, otherwise. EDIT: Extracted the Syntronik_Multis.zip file, and manually copied just the 4 affected .st3m files back over my significantly larger, modded ones, and Syntronik is happy to load them now. EDIT 2: Just out of curiosity, I manually modified the MIDI channel tag for the second 'part' in the XML-style .st3m file using a text editor (note that part and channel numbering starts at 0), and it loads to Sampletank with the correct behavior, and still loads to Syntronik as well.

If using onboard sound as an audio interface, make sure the Input/Source in the soundcard's mixer applet is set to something like 'Mic/Line In' as opposed to 'Stereo Mix' or 'What U Hear' which will record from the output so you capture everything being played back.

So opening a project from the other PC breaks MIDI input functionalty in all projects that were working after re-install/update? That's pretty weird. And you've confirmed it's an input problem not an echo problem - you can't record any input with a track set to omni? Check Preferences > MIDI > Playback and Recording to ensure Notes and Controllers are enabled for recording at a minimum. And Driver Mode is MME, not UWP? What does the MIDI device config look like on the other PC? I would compare the TTSSEQ.INI files between the two machines, and look for changes to it that might be happening between re-installing and opening the project that breaks things.

Thanks abacab, I figured it might be something like that. Still finding my way around the UIs, and haven't been through the Syntronik manual yet. Thanks for confirmation on the layer-channeling issue. Will have to ping IK about that.