David Baay

Referencing a copy of the same file with a different name in a different location worked fine for me. There is no need to Search; just change to the directory where the desired file resides, select it, and okay the warning that the name is different. Then Save As, being sure to uncheck the "Copy All Audio" option in the Save dialog. You can save over the exisistng project name, but I generally recommend to add a filename suffix when making changes like this just to keep everything straight, and allow going back to the original project if anything goes wrong.

The best way to replace one file with another would be to rename the currently referenced file and copy the desired file into the project audio folder, giving it the name of the original file. That said, renaming/removing the file and telling CbB to reference a file with a different name from a different location should work so long as that file is identical to the first in format and length, and you re-save the project with the new references. I'll have to do a quick test to confirm success or failure.

This isn't completely clear to me. Can you share a before and after example of a MIDI clip that's been corrected manually? It might also help to understand how you got in the situation of needing such a script to understand all the conditions that might be encountered in the input. CAL scripts can only process events one at a time in sequence so it takes a lot of recursion to recognize and process multiple notes as a chord. If this is a one-off problem that you need to solve that you will never encounter again, it might ultimately take less effort to fix it manually than to write script to do it.

You need to select all audio clips and enable Audiosnap and Follow Tempo in Autostretch mode in Clip Properties before making any tempo changes.

Assign the Input of the EZD track to the virtual MIDI Out presented by Jamstix. If you don’t see one, you might need to enable MIDI Out in properties of Jamstix. You will also likely need to split the EZD Instrument track and assign the MIDI Output to an appropriately configured Drum Map to translate the note numbers and output to EZD. Also it sounds a bit like you might have the VSTis inserted in FX bins rather than in the Synth Rack which is not ideal.

Does sound graphics-related and will therefore not be familiar to any user who isn’t on very similar hardware. I don’t really have any good ideas myself.

The spreadsheet reveals the sound source is TTS-1. A synth track is an audio track with input from a soft synth rather than a hardware input; it is effectively the same as a recorded audio track in terms of how audio is rendered, clocked and streamed to the analog audio output of the laptop. As I said previously, I can't imagine how you would have tempo variation from that setup without audio distortion/pitch changes unless there are tempo changes in the project or the MIDI is not in sync with the timeline everywhere.

If I'm understanding, you need to Arm the track for recording: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Recording.12.html

Glad to help.

You likely have the View option set to Show Controller Pane but have closed it at some point. Drag the Controller pane divider up or toggle it open by the button at the bottom left og the PRV. If you want to work with velocity tails in the Notes pane, uncheck Show/Hide Controller Pane and make sure Show Velocity is checked in the Notes menu (only available if the Controller Pane is not shown). It may also be that you have Show Velocity on Selected Notes Only checked, and don't have anything selected.

I ran into this a while ago when I started using Pianoteq and wanted to experiment with release velocity. I was mystified about why it wasn't working with Pianoteq as VSTi until I tried the standalone instrument. Given that more and more instruments are implementing advanced control of articulations, I think the Bakers need to look into implementing at least basic echoing and recording - if not display and editing - of release velocity for keyboards/controllers that send it.

I I haven't used it much but just did a quick test and am not seeing any impact on existing content of a relatively light project with Neutron on just 6 tracks and one bus, but the UIs for the Neutron instances themselves are slow to open and they open with a flicker as do other iZotope plugins.

Does this mean MIDI is driving an external hardware synth with no soft synths in the project? Given that you're using a laptop and don't mention an external MIDI interface or other hardware, I would think you must be using soft synth in which case it's not really possible to have timing issues without also having audio distortion or some sort. Or are you possibly outputting the MIDI to the laptop's onboard "Wavetable" synth (let's hope not!). In any case, if these are somehow 'pure MIDI' projects with no soft synths or other audio track content as Mark mentioned, I would suggest a third option for keeping the audio clock active: Enable CbB's audio metronome for playback, output it to a bus, and mute the bus. Usually just having the metronome set to 'Audio' in preferences is enough, but having it actually active on playback can be helpful in some instances.

Ah, okay. I wouldn't have encountered this since I continue to use either Groove Clips or Copy-Paste with Repetitions for this purpose. I never embraced Duplicate. ;^)

You can change all Outputs of multiple MIDI tracks to the same port by Quick Grouping just as you do for audio track ouputs (i.e. select all track and hold Ctrl while changing the ouput of one), but you have to use the control in the track pane; last time I checked, quick-grouping the Outputs of MIDI tracks via the Inspector doesn't work. Incidentally, for various reasons I recommend dragging old projects into a new template and then dragging clips from original tracks to new tracks as necessary. AMong other things, this ensures that your project has all your preferred preferences and bus routings and avoids potential problems with old projects, especially if they date to the pre-audio era of Cakewalk. (I started with Cakewalk for DOS in 1988).

I'm curious what the use case is for this.

The display of the "Comp" clip in the parent of an audio track is optimized for Comping where the signal from only one lane is unmuted in any given area, and the muting/unmuting is controlled by "promotion" with the Comp tool as reginaldStjohn suggested. In your case, the clips aren't "Comped"; they're 'layered' in sound-on-sound mode. In that case, the clips are shown layered in the parent; it can be a little unpredictable which layer is on top, but in my experience, the clip in T1 tends to take precedence. If you were to swap the clips between lanes, you would see the muted section in the parent track.

Hmmm... Okay, yes I can replicate that. I was not aware of Ctrl+Alt+Spacebar.

Are you playing the keyboard using Local Control or by echoing MIDI through a track in CbB back to the keyboard? If the latter, raise the MIDI Volume to 127 to ensure CbB isn't lowering the volume via CC7 messages. Then check what the track meters and numeric indicators show for peak level when the track is armed to record and you play some big, high-velocity chords with a piano sound. You should be able to clip the signal. But if you reset the meters and play a quiet, monophonic line it may well be down around -18dB or less. It's possible to zoom out the scaling such that a lower level signal like that will be nearly flatlined. Double-click the dB scale between the track and clips panes to reset it to default.

I kind of like this idea except that it violates the convention that a grayed-out object isn't available and can't be changed, which could be confusing to to noobs. The parens around the value are enough for me but need be replicated in the Inspector.

I'm not seeing that. Just to clarify... Shift+Spacebar (not Ctrl+Alt+Spacebar) is the default binding for Audition, and it depends on having some selection made - usually a measure or more in my workflow. Alt-Tabbing away from CbB is not causing the selection to be lost in my case so Audition still works when I come back to it. Are you generally seeing selections lost when you Alt-Tab away?

I agree although I saw another post recently requesting that Delete not be at the top of the FX bin context menu, so different users have different opinions about this.

I mostly use keyboard shortcuts for these operations in CbB, but so far as I know, this change in Windows Explorer does not affect context menus within CbB or other applications...?

Oops. You've reminded me that a change was made some time ago that broke/eliminated the previously default bindings of Tab and Shift+Tab. To have this work now, you have to custom bind Tab to 'Audiosnap Go to Next' and Shift+Tab to 'Audiosnap Go to Previous' in the Global context. This works in the PRV as well, incidentally which is where I use it most. And if you don't select a note, Tab and Shift+Tab will still move the Now time, but won't audition the the note.

I'm a pretty old dog, and I pretty rapidly got used to the new cut/copy/paste/rename/share/delete icons.