David Baay

Drum maps aren't just about labeling notes, they can remap the output channel of each event (as well as note number and port). Assuming the different articulation presets are assigned different channels in the synth, a drum map could help with that. But you would need to write the different articulations in different octave ranges of the track, and the loss of easy duration editing with the notes moved to the drum pane of the PRV makes it not a very practical solution. Using separate tracks with appropriate forced output channels assigned is probably preferable overall. Once you have it all worked out, you can consolidate by embedding the channel assignments in the events, and moving them to lanes of a single track.

Have never paid much attention to this. But, yes, CA-2A shows single, 32-bit signal path marks.

Incidentally, I found that I didn't have to first create a fade to reproduce this. I guess it is unexpected that a single click slip-edits the track when clicking with the context menu open whereas it would normally require a click and drag. Workaround (and probably a best practice) is to exit the context menu using the Esc key instead of by clicking.

Can only repro that here if the Edit tool is active, in which case it's not too surprising. Does not happen with the Smart tool.

Edges of the clips must be perfectly abutted to the sample. If the clips or their boundaries have been moved (other than moving the split point itself) it might not be possible to heal the split.

IBe sure to click in the lower half of the clip where the Comp tool is showing.

Appears to be something going on with the Clip Gain automation. Deleting the automation eliminates the problem, and after re-creating the clip automation, nudge from the keyboard continues to work as expected. If you can re-create the condition from scratch, you should report it to the Bakers. Even if you can't, they might be able to see where the problem is in this project file.

Bounce the selection to a new track named Master Bounce that routes directly to Main Outs, and group that track's mute button in opposition with the Master bus. Always maintain that track's position as the last track in the project. Whenever you need to do another export/bounce, start by selecting the Master Bounce track and clicking the clip to define the time range, Then Shift+click the first track in the project to select the same range on every other track, and export/bounce with Source = Buses, and only the Master Bus selected. The Master Bounce track is both muted and not routed through the Master bus, so it won't be included. I usually bounce to a new track, and then drag that clip to a new lane of the Master Bounce track and solo the lane. That way, 'masters' are saved with the project, and I can toggle the track mute to A/B between the bounced mix and the live mix on the Master bus to verify everything rendered correctly. I can also toggle between different master bounces, using the lane solo buttons.

Do have an un-modified copy of that frozen project somewhere? That would probably be a good one for the Bakers to look at.

Yes. Inadvertently left out to click "with the Comp tool" as mentioned in the other post.

Replied to that thread. I'm either not understanding or not seeing a problem.

This sounds like expected behavior when the track's Edit Filter is set to Clips. Haven't double-checked the beahvior, but make sure the Edit Filter is set to Automation. EDIT: I interpreted "selects the envelope itself" to mean "selects the clip itself. Also, I just checked, and lassoing individual envelope nodes works as expected here if the Edit Filter is set correctly.

Totally agree. In fact, I deliberately used snap to landmarks precisely because the MIDI wasn't quantized. Helpfully CbB remembered the last-specified musical snap value, so I could set that at the desired resolution (16ths for demo purposes though a higher frequency might be more appropriate in practice to give 'smoother' transitions), and then disable it and have the first and last event aligned to the note boundaries with the intermediate controllers drawn at the musical resolution.

Posted in your other thread: To 'heal' a split, select the clips on either side, and Ctrl+click on of them. You might want to enable snap at an appropriate level of precision to prevent 'duplicate' splits.

Select the clips on either side of the split, and Ctrl+click one of them with the Comp tool.

A. He's already said he doesn't like working in the PRV. B. I think he prefers the precise alignment and perfectly linear slopes of automation envelopes (the curse of making music with your eyes instead of your ears, and becoming too enamored of the graphical and numeric perfection that computers make possible IMHO). But it is possible to achieve that kind of precision in the PRV controller pane with relative ease, using the Line drawing tool and Snap to MIDI Landmarks.

Hmmm... I think you must have some non-default keybindings in addition to having an undocked Track Inspector. Just undocking the track inpector does not cause that to happen here. Splitting Notes to Clips Using Tab and S

Just noticed your signature indicating you're on Win 8.1. This is such an unusual symptom, I suspect it's an O/S compatibility issue; there have been a few others with Win 7/8

In my experience, the Now cursor movement tends to look a little fuzzy/shaky at higher tempos and/or zoom levels. The oldest version I still have installed is X2, and it looks no different than the current release.

Speediest workaround to split notes to clips: - Set 'Selection after single split' in Preferences > Editing to 'Right portion'. - Select the clip - Alternately type Tab and S as fast as you can to split your way through the clip.

The whole purpose of clips is to be able to treat a group of notes as a single object. If you need to edit/process individual notes, you can do that in the PRV or Event List.

If you're copy-pasting between multi-lane tracks, that's possible. Since pasting was made 'lane-aware' relatively recently, I believe Paste into Existing Clips is only applicable when copy-pasting from one single-lane MIDI track to another with lanes not showing. But the option won't be grayed out in that case; it just may not work as expected if the tracks aren't single-lane tracks. Theoretically it should be possible to make it work if multi-lane tracks have a one-to-one correspondence of tracks, but that's a wrinkle that probalby wasn't considered. 'Paste into Existing' predates the introduction of multi-layer/lane tracks.

Are you sure you have MIDI in the paste buffer? The only time I see that is when the paste buffer has an audio clip in it.

Paste into Existing Clips applies only to MIDI.

What made you suspect that copying the project might have some effect? Is it on a different drive or just a different location on the same drive? If you watch disk and CPU usage in Windows Resource Monitor, does the crackling project show higher usage in either?