David Baay

I suspect the keyboard does not have an input that supports a continuous pedal.

You're in the right place with the event filter. You don't need to change the Value sliders, it should remain all yellow to pass other controllers. The CC# should just have a single black bar in the center with both numbers reading 64. The programming is a little buggy, and can make it hard to get right. You also have the second part right except that the pedal doesn't generate MIDI messages, it just switches the keyboard input open and closed; the keyboard generates the messages.

The only automatic quantize is called Input Quantize. There's a button and a resolution setting for it in the Track inspector for of every MIDI track and on the MIDI tab of an Instrument track. It's unlikely it got enabled by accident.

Good call, Dave. You won't regret it. I went without a real piano from 1988 until just a few years ago when a friend made me an offer I couldn't refuse on a Yamaha G3. I have it tuned yearly, but it's now overdue by about six months, and sounding a little wonky in places (spoiled by the always-perfect tuning of digitals). The good news is that tuning still only costs about $150 around here. I love playing and improvising on it, but when I come up with something new, I have to run upstairs to record it . Micing it up properly would be too much of an imposition on the aesthetics of the living room so I have not tried to record it seriously, but I have occasionally used a digital camera to capture a quick video with sound. Have fun!

Affects all projects? Does it matter where you are in the timeline? Using ASIO driver mode? Have you verified that rollback fixes it? EDIT: If it's affecting all projects, and rollback doesn't fix it (likely not), you might try executing 'Reset Config to Defaults' in Preferences> Audio > Configuration File.

Ooh, Nice one!

If start times are in weird places because the MIDI was recorded without a click, you can use Set Measure/Beat At Now to put the start time exactly on a beat before copying. It won't affect the timing before or after the Set point, but you can undo it after the copy if necessary. When I'm working with unquantized MIDI (almost always), I frequently snap just the first note of a section to the measure to make editing easier which might also work, depending on the circumstances.

If you need all or most of the clips, and they're going into a totally new project, I second Steve's approach. If you only need one or a small subset of clips from the source project and/or you're copying to an existing project that has other content already, the easiest way I can think of is this. - Enable snap to Landmarks in the target project with only the Now Time selected and disable snap to musical resolution. -Select the source clip and copy (Ctrl+C) the start time from the Select module in the Control Bar. - Hit G in the target project to get the Go To Time dialog, paste (Ctrl+V) the start time and Enter. - Drag the clip from the source project to the target (or copy-paste it) and it will snap to the Now time. Obviously this is a bit painful if you have a lot of clips to copy, but that's the best I can come up with off the top of my head.

That would have come up eventually. You are not the first to get caught out by punch. ;^)

Interesting; is that relatively new? I don't recall having access to the MIDI Out of an instrument track previously, and did not think it would ever be allowed since changing it (or assigning a Drum Map that outputs to the wrong port) could break the Instrument track.

I've mostly switched to instrument tracks as well, but always recommend noobs start out with separate tracks to learn the concepts of routing MIDI and audio to/from the synth rack, I/O ports and channels, MIDI vs. audio automation, velocity vs. volume, etc. For those who have never worked with a hardware synth, I think it would be really hard to get a good understanding of all this stuff without having access to separate MIDI and Synth tracks. And being able to split Instrument tracks can help when trouble-shooting "no sound" issues. Also, it occurs to me that under the current implementation it's not possible to apply a Drum Map to an Instrument Track.

i agree with the terminology that a Synth Track is an audio track with a synth assigned to the input, but the icons for Synth and Instrument tracks have been reversed since X1. Back in in SONAR 7 before Instrument tracks were introduced, the Synth Track icon looked very much like the current Instrument Track icon. When instrument tracks were introduced, the MIDI port was added to the icon to indicate the new track type, but this got mixed up when Skylight was introduced in X1. I reported it, but could not get the gatekeeper at the time too acknowledge that it was wrong and forward it to the devs. Swapping these icons is the one change that I make to the default Mercury theme because it's always bugged me that they're backwards.

I think it has always have been the case that PRV notes use the track color regardless of a custom clip foreground colors. You should be able to get back to having everything in sync by selecting the entire project and checking Use Track Colors box in Clip properties.

Cakewalk includes a 32-bit VST-bridging component called Bitbridge that is automatically invoked when a 32-bit plugin is loaded (instrument or FX). It has some quirks and limitations that can be overcome by using the inexpensive 3rd-party 'Jbridge'.

Agreed. This thread is a goldmine for more advanced users, especially anyone working with a device like Maschine.

All of my pieces start out as improvs. Most end up gaining more structure (sometimes over a period of months or even years) and benefit from it. But sometimes the original really can't be improved. In this case I prefer the purity/simplicity, tone and imaging of the first one. The detuning is very cool. Well done!

Confirmed. Have not seen this before; must be relatively new...? Clicking anywhere in the Track View before focusing a track will also fix the problem.

- What keyboard, and how is it connected (USB or MIDI DIN)? - What sound source (VSTi, hardware module, keyboard synth or - heaven forbid - onboard GS Wavetable synth)? - What audio interface, driver mode and buffer size?

To be more precise about 'continuous output', it's really variable resistance of a potentiometer in the pedal that is converted to a digital value by an A/D circuit in the keyboard/controller, and that digital value is in turn used to generate MIDI controller messages. A standard switch-style pedal can only present two resistance values - infinite when it's open, and something near zero when it's closed. (Different pedal and controller brands use different conventions for which pedal position is open, and whether open or closed generates 0 or 127, but that's beside the point.) The important thing to understand is that the keyboard/controller will only generate 0 or 127 from a switching pedal, so you would only be able to select min and max cabinet speeds. The trick is to drag the min and max histogram sliders for the CC number past each other in the MFX UI to create a 'hole in the middle" that excludes CC64. Understand the MFX operate on the output of the track so this will not prevent CC64 from being recorded but will prevent it from being echoed or sent on playback from that track. HOWEVER... I just realized your synth needs to see these messages in order for the 'learned' function to work. So what you probably need to do is use a MIDI Mapper MFX to change the controller message to something to which the synth doesn't already respond, and have the rotary function 'learn' that controller. Actually, it's likely that the rotary function is already programmed to respond to some specific controller by default that you can map to. I forget whether a mapper is bundled with Cakewalk. If not, I think Tencrazy has one, and other free ones are probably also available.

Melodyne not installed? (free version can be installed from Bandlab Assistant).

Meh... I'm holding out for 'Read My Mind'. Until then, I'm sticking with Cakewalk. But, then, since I'm mostly my own 'Client' maybe it would work...?

A major shortcoming of this is that only the start time is locked. The content of a MIDI clip will always follow tempo changes unless they are made using 'Set measure/Beat At Now' which may or may not be feasible, depending on the situation. I have long wished to be able to lock the Absolute duration of a MIDI clip as well as the Absolute start time.

Are you saying you have a new clip starting at bar 24? If so, make sure Audiosnap enabled on it. Check the Audiosnap and Groove Clip sections of Clip Properties in the Inspector. If the clip is a Groove Clip, it will have to be bounced-to-clip before Audiosnap can be enabled; the two features are mutually exclusive. Yes, it is a long-standing bug that the state of Clip Tempo Mapping is not saved. Reported many times - not sure why it doesn't get attention. P.S. I prefer using Set Measure/Beat at Now for this and many other reasons - more precise, more flexible, more predictable, and is typically just as fast or faster then editing Clip Tempo Maps once you get the hang of it, making good use of keyboard shortcuts.

Ah, so it is.

Yeah, you would think, but the MIDI tab doesn't display an MFX bin as your screenshot shows... unless I'm missing something?