David Baay

Sure. An old but useful trick I still use it occasionally. One thing to be aware of in your process: Tab to transient depends on Audiosnap transient detection which can be a bit variable, and the current algorithm usually places markers a couple milliseconds into the attack of the transient. This works well enough for adjusting musical timing based on where a listener would hear the transient 'hitting' rhythmically, but I would not depend on it 100% for precise registration of samples.

See post 23 in this old thread for how to set up CAL files to allow "nudging" the Now Time at any desired tick resolution with keybindings: http://forum.cakewalk.com/fb.ashx?m=1365944 You'll need to calculate how many ticks in 500ms at your current project tempo as 8 x Tempo (e.g. 800 ticks at 100bpm).

We're talking about a physical mod wheel on a controller keyboard, right? In most cases, moving the the mod wheel in the synth UI will not generate MIDI output that can be recorded, and it would require a special setup to captuer and route it correctly if it did. So, assuming we're talking about a physical mod wheel, recording modulation events and getting them to control the desired synth parameter are two different tasks. If you're not able to record modulation events from your keyboard at all, it has nothing to do with what synth the track is driving or whether MIDI learn is working. And you don't need to set up a controller lane in advance to record controllers from a physical mod wheel on a keyboard/controller. Assuming you can record MIDI notes from your keyboard, then port and channel assignments are correct, and the only thing that would prevent controllers being recorded would be that the box to enable recording of Controlllers in Preferences > MIDI > Playback and Recoridng has been unchecked (it's enabled by default). If it's checked, you don't even need to have a synth set up to arm a MIDI track and record notes and controllers. Then, when you double click the MIDI track to open it in the PRV, and show the Controller pane, the mod wheel events will be displayed automatically. So the first task is to get recording of controllers working, and then we can worry about whether the synth is responding to them as expected.

You can't apply a different tempo to an individual MIDI clip, but there are various ways to stretch/compress a MIDI clip to effectively play slower or faster within the context of the project tempo. There aren't too many different ratios that are likely to work. If a 70-80 bpm clip sounds like it should work with your 120bpm track, then it's likely you need to double its length after importing it to be effectively 60PBM. You can do this by Process > Length. But without hearing what you're working with that's a wild guess.

Not lane-muting, clip-muting. Everything you decribed is consistent with clips being muted. Comp recording automatically mutes takes as they're superseded by newer ones. Clicking a take with the Comp tool in the lower half clip will 'promote' that take and mute others in the same time range. Or you can use the 'k' shortcut as mentioned to unmute any or all takes in the case that you want sound on sound playback. I'm not completely understanding your description of the different problems you're encountering , but i don't think you're encountering a bug. I think you must need to understand the tools. A screenshot might help clarify what you're seeing. Or share a copy of the project with the MIDI drums.

If the performance was recorded without a metronome, the tempo is going to be more or less variable over time, This procedure will fit the project timeline to the MIDI with tempo changes calculated for you: – Drag the clip to align the first downbeat note to the nearest bar line (i.e. 1:01:000 if it starts on a downbeat or 2:01:000 if there are pickup beats). – If isn’t starting at 1:01, snap the Now time to 2:01 and use Set Measure/Beat At Now (Shift+M) to pin down that point as the reference for subesequent timeline ‘Sets’. – Start playback and stop the transport at the downbeat note that should be hitting the 9:01 barline. Tab/Shift+Tab to the beginning of that note, and SM/BAN that point to Measure 9, Beat 1 (or Measure 10 if the first downbeat is at 2:01). Cakewalk will change the previous tempo to make the beat fall on the specified absolute Now time, and insert a matching tempo at that point to serve as reference point for the next Set. That tempo is the average for those 8 measures though there will likely be some variation within it that you can address later. - If there was a pick-up measure, go back and set the first pickup note to the appropriate beat or fractional beat (decimal, not ticks), and change the initial tempo to match the tempo between that point and 2:01. – Go through the rest of the clip using a combination of playback (spacebar), Ctrl+PgUp/Dn for previous/next measure and Tab to MIDI notes to put the Now time on downbeat notes at 8- or 16-measure intervals, and ‘Set’ those beats out the the last downbeat or the point where a decelerando starts if there is one. (Note: If the rhythm doesn’t consistently have notes on downbeats, you can set a different beat or even a fractional beat somewhere else in the bar). Once you get the hang of using the shortcuts, this goes pretty quickly. – Enable the playback metronome, and listen through the clip, setting additional points as needed to further tighten up the timeline to the MIDI clip. Understand that SM/BAN is entering tempo changes to make the timeline fit the MIDI. MIDI event start times and durations will be recalculated to preserve the absolute playback timing of the original performance at the new project tempos. Open Views > Tempo to see the tempo map being created. – If you find that you’ve made things worse at some point, always Undo your way back to the last ‘Set’ before the mistake was made. Deleting a tempo will cause the timing of the MIDI to change, which you don't want. - It’s best to do a periodic Save As with a new project name suffix at regular intervals so you can easily back up to a ‘good’ state if needed later on. I usually do these progressive saves with something like “Rough Set Thru 33;01” appended to the name to know where I left it. - Once you have the timeline aligned to the MIDI throughout the performance, you can edit the tempo map to smooth the variations or delete all but the first to completely flatten the tempo and/or quantize to tighten up the performance.

I've never seen that before which makes me think it's related to UWP driver mode for MIDI. If so, try changing to the default MME mode under MIDI > Playback and Recording. So fas as I know, there's no performance or functional advantage to using UWP mode with hardware connections. It's main benefit is supporting Blutooth. My old multiport MOTU interface driver only exposes a single port in UWP mode, and there ar eno errors reported, but it doesn't work.

It's been a long time since I messed with ACT, but if you're using a single MIDI port for both Control Surface and keyboard controller functions, I think you need to distinguish which channels are intercepted by ACT, and which are available for musical/performance data input to tracks. As it stands, it sounds like ACT is intercepting all channels.

Not sure exactly what this means, but you can do all of the following: - Have a single track record and echo MIDI from multiple input ports (choose Omni or see 'Manage Presets' option in the MIDI Input pick list). - Have multiple tracks record and echo from the same MIDI port (pick the same Input port for both tracks - with or without differentiating channels). - Have different tracks record and echo from different ports, exclusively (pick a different port for each track's Input - with or without restricting the channel ). What does this mean in terms of where exactly you run into a problem? Can't see the device in Preferences > MIDI> Devices? What is the device, and are you using MME or UWP driver mode for MIDI interfaces? FWIW, I've had a problem that started with the last major Win 10 update that I have to power up my MOTU USB MIDI interface after booting. If it's powered up during boot, Windows shows the driver loaded, but no application sees the driver.

It's not the physical cable that imposes the restriction; it's the MIDI communications protocol, itself, and, indirectly, the data rate of the serial PC ports over which it had to operate. Only 4 bits were allocated to specify a channel. 4 bits let you count from 0 to 15 in binary; hence 16 channels. Since binary 'word' lengths are restricted ot 4-bit 'nibbles' or 8-bit bytes, the choice for developers would have been between 16 channels and 256 channels. The approximately-1-MIDI-message-per-millisecond data rate of a serial port would make it impossible to get acceptably good timing when pushing anywhere near 256 channels of data through a single port. Even 16 channels can be too much if there's a lot of controller data being pushed along with basic note on/offs.

Seem to be having ongoing miscommunication. I said exactly the above in my first post. But if that setting is overriden by changing a track directly (or by importing a track template or possibly other means), the discrepancy will persist until you re-select or change the setting in options which resets any overrides.

Yes, I understand. What I'm saying is that it's expected behavior that you can have a difference between the default range setting for new tracks in meter options and the actual range of a particular track. And there are several ways to get a project into that perfectly valid state. Using track templates would be another. Without knowing the history of the project, it's impossible to say how the difference arose, but just that fact that there's a difference doesn't mean anything is wrong.

Ah, yes, 'Previous Take' in this context means 'previous recording'. You have to restart the transport in between takes.

Healing requires clips to be perfectly abutting, and MIDI will often have gaps between events. Comping workflow is optimized for audio. MIDI is more easily 'comped' using a conventional copy/cut/paste approach. Mute Previous Takes works with MIDI, but requires having Auto Punch enabled as shown the video.

Working as designed, I think, unless you're sure you never changed the individual meter scales by right-clicking...? Or maybe started the project from a template with overriden scales. Capturing that in a Workspace might also be expected behavior.

As an oldtimer, you may be more comfortable setting Workspace to 'None'. Then each project will retain its own layout and settings as you're used to.

So should there also be checkmarks next to Insert Audio Track, Insert MIDI Track, Insert Instrument, etc. when one of those objects already exists in the project? Having a checkmark next to a repeatable function just because it's been used once doesn't seem especially intuitive to me. If I want to see sends in a collapsed track, I show the Inspector.

Sounds like clips are muted. They'll be grayed out, but solo will override clip muting. Muted events will be excluded from a bounce. Hotkey 'k' will toggle muting of selected clips.

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?