David Baay

Probably not the cause, .but as a best practice I recommend you change the track input to the specific port and channel that your keyboard is on. I also did a quick test, and had no trouble getting sustain while playing live, with several different presets. Which preset are you using?

It's Shift+C here, but I thought I had customized it.

Looks like your display doesn't have high enough resolution to display the full height of the Inspector, and one view has the pane scrolled to the top, hiding the volume widget. I believe 'C' is the default binding to show/hide the Control Bar which will make a little more space for the Inspector. You might also want to click the Full Screen button at the upper right next to the Workspace selector.

Slip-stretching will use whatever algorithm you have selected in Clip Properties for Online Rendering - Elastique by default. Groove-Clip looping uses the Groove-Clip algorithm which is less CPU intensive and can give better, worse or comparable results, depending on the audio content.

Yeah, I suspected something like that. You might try setting a non-zero BounceBufSizeMsec=<0 to 350> in AUD.INI (Edit > Preferences > Audio - Configuration File). I've had this set to 20 for many years to help avoid rendering issue like this, and I do use some high-PDC plugins at Mastering, including Izotope stuff, though not RX9, specifically.

I can't see that anything is configured incorrectly, but I can't reproduce the issue either. Can you share stripped-down copy of the project?

I will not have time to look at the project for a while, but I can tell you from some of what you described that a key to getting this to work as expected in this use case is ensuring that the Follow Option is 'Auto strech' before you enable Follow Project. There may still be issues, but that will address a lot of them.

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!

Yeah, I can imagine Snap to Zero Crossings would affect duplication as well; I just meant your video isn't showing duplication; it's showing slip-editing.

I don't see how your video relates to Duplication, but that looks like maybe you have Snap to Zero Crossing enabled...? EDIT: Oh, I see you discovered that. .

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.

I'm seeing a few unexpected behaviors that might be contributing to the problem: - When you first change the Edit Filter in a track form Clips to Notes (a.k.a. inline PRV), there is no flyout menu to allow selecting to show controllers. - After changing the Edit Filter to Notes, you can open it again and get the option to select a controller for editing. - The MIDI tab in the track view has an option to Show Controllers, but it isn't available until you've selected a controller in the Edit Filter, - Only controllers that have been selected in the Edit Filter are available to check/uncheck under Show Controllers; you have to change the Edit Filter to each controller type one at a time to make it available in the Show Controllers list. - Once you switch the Edit Filter back to Clips, you're back to square-one with showing controllers. I don't do a lot of controller drawing/editing (mostly recorded in real time) or use the Inline PRV so I'm not sure when any of this might ever have been working as expected, but it seems like it needs some attention. I would expect the Show Controllers menu to be available any time, regardless of whether the Edit Filter is set to Clips or Notes, and to be able to select to show any or all controllers without ever having to select them in the Edit Filter.