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.

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

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.

+1 to this.. I had a brown out a few years ago, where the AC went down from 240V to 50V. Three SSD's were destroyed by that.

If I were to pick my top two synths, it would be Omnisphere and Synthmaster 2.9. Both synths have a learning curve, but both also have a wealth of presets, so it's not too difficult to take a preset close to what you want then tweak it. They both have multiple synthesis types. No.3 on my list is Cobalt, which is a free VSTi similar to the Korg DW8000 / Kawai K3.

There's also Sonivox Orchestral Companion Brass, which has solo brass instruments, including a french horn. It goes on sale quite often ( I think I paid about £5 for mine), but I can't see any decent deals ATM.

^^^ This . Switch your driver mode to WASAPI within preferences, and see if the problem goes away.: Note there's two modes of WASAPI: WASAPI Exclusive: lower latency, but Cakewalk will have exclusive control over your audio device (i.e. you'll no longer be able to listen to YouTube etc when Cakewalk is using it). If this is an issue for your workflow, consider checking "Suspend Audio Engine When Cakewalk is Not in Focus". Also, not all audio devices support this mode. WASAPI Shared: higher latency, but the audio device will be shared with all other applications. You'll want "Suspend Audio Engine When Cakewalk is Not in Focus" to be unchecked in this mode. You may find WASAPI Exclusive is more suitable for recording real-time MIDI, or recording guitar/vocals when monitoring through FX. WASAPI Shared should be fine for everything else.

IIRC, MidiGuitar is very sensitive to ASIO buffer size and sample rate. It's been a while since I've used it, but it needs a minimum of 128 as a buffer size and it worked best for me at 48K. Any time I used it in a project, I'd delete it as soon as I had the MIDI conversion. But yeah, I stopped using it due to it being buggy and prone to crashes.

It's probably easier to just zip up the folder with your project in it, so we have both the project & audio files, then send that zip file to @Jonathan Sasor

@Mark Bastable - can you send a project that crashes as a bundle file to @Jonathan Sasor , along with a note as to which track you were trying to bounce? We'll look into it.

One of my favourites

Ah, that might explain it. I was running on my laptop at the time, which doesn't have an iLok.

FWIW I found Melodyne was unusually slow on the very first time when analyzing the audio for your clips - Cakewalk appeared to hang, but eventually recovered. I've definitely not seen it crash though. Can you post the crash mini-dump when it crashes?

@ManuelGuerrero - I've gone through the extract tempo process through the debugger. Melodyne is telling Cakewalk it failed to extract any tempo information from the clips.

One thing I would add about choosing an interface, is think about what you might need in the next 2-3 years. I'm not saying spend a fortune on a 32 in / 32 output interface, but think about scenarios where: You might want to record more than just one or two channels Will you always be using VST effects, or will you be reamping via a real amp in the future, or might want to use external effects processing? So for example, something like the Scarlett 2i2 is a great interface, but you've only got 2 ins and 2 outs... and the 2 outs will invariably be connected to your monitors. The Scarlett 4i4 gives you 4 inputs and 4 outputs for an extra 30% - 40% of the cost. In general, you can't use more than one interface at once ( due to technical restrictions with ASIO / wordclock sync issues ), so if you do have to upgrade your interface your old interface will be redundant. One exception to this rule is interfaces that have an ADAT input. If you buy an ADAT converter, this will give an ADAT equipped interface an extra 8 inputs. The Scarlett 18i20 / 18i8 both have ADAT inputs. They're not cheap interfaces, but in saying that the Behringer UMC1820 essentially has the same feature set as the Scarlett 18i20 - i.e. 18 inputs (8 analog, 2 SPDIF, 8 via ADAT), 20 outputs (10 analog, 2 SPDIF, 8 via ADAT) - but is the same price as the Scarlett 4i4... although it's arguable that the Scarlett preamps are superior. Anyhow, all I'm saying is you might want to consider getting something slightly more than what you need now to save money in the future.

I can't find anything specific to articulation copy/cut/paste/delete, but I suspect the this behaviour was taken as a given, as there are several references to articulation selection - i.e. anything else within a track/clip can be selected, and then copied/cut/delete/pasted. The articulation events themselves essentially live inside their own MIDI clip on each track, so they're treated exactly the same as MIDI events in that respect. The only differences being: There is only one articulation clip per track You can only see Articulation events in the Events View and PRV Articulation Lanes (i.e. they're invisible on the clips pane ) During playback, articulation events are always processed before any MIDI events on a track

That should be plenty fast enough for low latency operation.

Just select the articulations and use CTRL + C / CTRL + V:

If you're just dealing with key switches, creating articulation maps should be trivial using the MIDI learn function. You just engage MIDI learn, press the key, name your articulation and repeat for each key switch. This is especially true if all the key switches are mutually exclusive (i.e. each key switch overrides all of the others). I appreciate that the base octave can be confusing as there's no standard here. Personally, I just ignore this and either look at the MIDI note number itself, or more often just go up and down the keyboard until I find the right octave and use MIDI learn from there. Where things start to get more complex is where you've got groups of key switches that aren't mutually exclusive. In this case you need to put all the key switches that override each other in their own group. Most VSTi's / Kontakt libraries are pretty good at colour coding these on a keyboard display to make these groupings more obvious, so you just create your groups to match what you see on the plugin/library. Not grouping articulations properly is the #1 reason why people think that chase doesn't work, and end up changing their articulations to "Full Chase". For the most part, you can ignore the transforms section unless: You're using a library that doesn't support key switches, in which case you can fake them by using a MIDI channel transform and organise your sounds to match the MIDI channels ( e.g. legato strings on Ch 1, pizzicato strings on Ch 2) You're using a transposing instrument (e.g. clarinet, saxophone etc) and you want the staff view to show what the musician is playing vs the actual pitch being heard, in which case you use a Key +/- transform. The VSTi uses velocity switching (e.g. Shreddage uses the lower velocity range for palm mute, the upper range for clean, and 127 for pitch squeal), in which case you can use a Vel +/- transform to force your performance to clamp to the velocity ranges you want.