msmcleod

Offset Tempo map works on the node selection - so make sure you have them all selected. You may find them easier to select from the tempo inspector.

Can you reproduce the issue? If so, can you send a copy of your project before the issue arises to @Jonathan Sasor along with instructions to reproduce?

VST3's should only ever live in C:\Program Files\Common Files\VST3 , and there should only be VST3 files in that directory. SF2 files are not virtual instruments, they are multi-samples in SoundFont format. You need an SF2 player to use them (such as Sforzando, TX816W etc)

If you're using a Workspace, save it after re-ordering your control bar modules. Don't save over the factory ones though - give it a new name else it'll be overwritten when you next update.

This was useful in the early 90's when people were migrating from older sequencers. For example, I used Music-X on the Amiga before moving to Cakewalk which had a resolution of 192 ticks per quarter note. I spent most of my time in Music-X's event view, so being able to set Cakewalk's ticks per quarter note to 192 made the transition much smoother when using Cakewalk's Event View., until I slowly changed my workflow to use Cakewalk's other features.

You can change the time base to Absolute time on an arranger track by track basis. So all sections within an absolute time track will keep their absolute time position and length regardless of tempo changes. To change the time base of an arranger track, either use the arranger track context menu, or click the time base icon in the arranger track header:

You might want to try @scook's CbB Tools - in there is a utility to populate the Utilities menu. It's towards the bottom of this page: https://docs.google.com/document/d/1eiVH_I1clbbRtWFh4-3Mo7HANjCxR8SwqHJtYXy19gw/pub

This is basically what the CAL script is doing.

Ok, this one seems to work: ; Bounce MIDI to Track (do (int nTrk 255) (EditCopy40 TRUE FALSE FALSE FALSE) (EditPasteToTrack From 1 0 TRUE FALSE FALSE FALSE nTrk) ) BounceMIDI.CAL

I had to delete it - it doesn't work Looking into it.

It's more likely that you're not selecting the whole track before doing bounce to clip(s) - in other words, you're just selecting the top most clip. [EDIT] - Actually, it could be this setting:

As long as you did things one track at a time, it's likely that they're just on top of each other and the top most clip is obscuring the ones underneath. It definitely works:

When using the smart tool, you can use CTRL + SHIFT to stretch the clip to make it shorter:

@Noel Borthwick's fix was a generic one for both extra ports appearing, and ports being missing from updated VSTi's, so the fix in EA should equally apply to those as well.

Bounce to Tracks only works with audio. AFAIK there's no one stop way of doing this. What I've done in the past: 1. Create a new MIDI track 2. CTRL + SHIFT + Drag each MIDI clip on to the new track ( CTRL for copy, SHIFT so the start time is preserved when dragging ) 3. Select the new track by clicking the track number (make sure this is the only track selected) 4. Right click on the clips and "Bounce to clip(s)" Although I guess you could create a CAL script to do it.