msmcleod

To manually add a tool to the "Utilities Menu" 1. Open RegEdit 2. Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Tools Menu\ 3. Right click on "Tools Menu" and select New->Key 4. Name the key with the name of your program (e.g. Sound Forge 12 ) 5. Click on the new key you've created, and add the following string values:

You can still use SoundForge or any 3rd party editor, it just requires adding the tool to the registry, or using @scook's utility to do it for you: Acon Digital's Acoustic v6.0 Basic Edition is free, and works well: https://acondigital.com/downloads/ You can find it under the "Old Versions and Discontinued Products" section:

The TempoMapDecimationResolution setting within Cakewalk.ini changes the granularity of tempo changes, but the default actually is every 16th note: https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=Tempo.15.html Ignore the title of the topic in the docs... actually only the last two ini variables affect importing old projects. The TempoMapDecimationResolution affects all projects.

This quantizes the start of an audio clip, not the audio within the clip itself. As @Will_Kaydo says, it is possible to quantize parts of the audio using AudioSnap, but this is largely a manual process to get all the transients in their correct place (depending on the audio material), and is nothing to do with the Quantize dialog.

Quantize only works on MIDI clips. Melodyne can quantize audio, but you need the Editor or Studio editions to deal with polyphonic material.

IIRC this was a bug in a previous version, which was saving the bus solo state incorrectly in the track template itself. You should re-save your track template.

That's mostly true in practice, but they aren't really that comparable. 16 bit and 24 bit are integer formats, whereas 32 bit and 64 bit are floating point formats. What this means is 16 bit / 24 bit have a fixed but limited dynamic range, but don't lose any precision over that range. 32 bit & 64 bit have a potentially wider dynamic range, but lose precision at the very extremes ( although those extremes are so extreme, it's not something to worry about).

It looks like you've got "Markers" included in your Copy/Paste special options, and the option to retain your Copy/Paste special settings when doing normal cut/paste is enabled. Try unchecking this:

I'm not seeing that here. Tempo changes are correctly being applied when exporting sections: Are you using any generative VSTi's ? If that is the case, consider freezing them before export. You should essentially follow the guidelines in the "To commit an arrangement" section ( page 469 of the current guide ).

@Will_Kaydo - it's working fine here. It's more likely the "Synth Property Page" checkbox has been unchecked in the Open Synth Properties at some point:

Which method are you using to insert the synth? I can't see how this would have been affected, as the change was restricted to the Replace Synth command.

@JayCee99 - looks like the culprit is Raum, particularly the one on the Vocals bus. Its plugin state is doubling in size every time it's saved. If you delete the 3 instances of Raum out of the project, the project file is 5MB again. The issue is definitely with the plugin. I'd recommend raising this with Native Instruments.

You could try deleting %APPDATA%\Cakewalk\Cakewalk Core\ctrlsurface.dat - it may have been corrupted when it crashed.

In many ways Groove Clip pitch markers are a poor man's chord track. It'll move pitch up and down, but what you cannot do is change from major to minor. It does work with both MIDI Groove Clips and Audio Groove Clips though. The thing you need to remember to do, within Properties / Groove Clip is: Turn on Looping Turn on "Follow Pitch" Correctly set the Reference Note e.g.: In this example, I've played a C triad in the MIDI track. The Pitch markers are set to C at bar 1, F at bar 2, and back to C at bar 3. The chord correctly changes to an F at bar 2, and back to C at bar 3.

Not in a standard release build. It's doubtful it would give much info in any case, as things such as loading samples is handled completely by the plugin. All Cakewalk does is ask the plugin for its current state and save it with the project. When the project loads, it passes that state back to the plugin. Its worth noting that the samples themselves aren't stored in the Cakewalk project. Normally plugins only hold the file path to the samples its using.

@jsg - can you PM me a copy of your project file so we can take a look?

As well as defining the instruments within your ins file, you also need to map which hardware MIDI port is routed to that hardware synth, e.g. below I have my Focusrite MIDI Output (all channels) routed to a Korg Triton: Once this is done, the Bank & Patch dropdown will match the instrument definition when a MIDI track is routed to that port.

Just use the one bundled with Cakewalk - it's got all of Azslow3's enhancements as well as mine.

A word of warning on this one though... this might work for simple templates, but track templates are deliberately a sub-set of a full project template and there's no guarantee this will always work. There's likely to be a bunch of stuff that will be ignored from the template that could be relied upon.

@Xel Ohh - Nice video. A quick tip though for inserting MIDI FX on Simple Instrument Tracks... when you switch to the MIDI tab, all the controls on the inspector (e.g. Gain (velocity trim), FX, I/O, Pan. Volume, MSR) are actually the controls for the MIDI track. So you can just drag your MIDI effect onto the FX bin in that tab, e.g.:

There are pro's and con's to both, 1. Opening the MIDI File, then adding your own Master bus Pros: Any tempo changes / markers in the MIDI file will be imported into the project If you've no hardware MIDI outs, TTS-1 is automatically inserted and wired up for you Cons: You have to create your own Master bus (and optionally Preview/Metronome buses) and re-route the outputs If you do have hardware MIDI outs available, you need to insert your own synth an route the MIDI tracks to it 2. Creating a project based on a template, and importing the MIDI Pros: Your Master/Preview/Metronome bus are there for you Cons: No tempo information or markers are imported when importing the MIDI file You need to insert your own synth and route the MIDI tracks to it.

Just tried saving a project with Sforzando + loaded samples - no problems here when re-loading it. I tried both with the plugin UI showing and hidden.

@Herbert Miron - The discontinuation of VST2 plugins only really affects Plugin manufacturers who didn't sign a developer agreement prior to 2018. Those who have a developer agreement signed before 2018 can continue to release VST2 plugins if they wish. What Steinberg's statement is saying is that new developers cannot release VST2 plugins - only VST3 ones. Also, as far as I can tell, this affects the releasing of plugins, not plugin hosts (such as Cakewalk and other DAWs). Cakewalk will continue to support VST2 plugins and has no plans to discontinue support for them.

Time to check out this thread: SONAR has been replaced with Cakewalk by BandLab (not to be confused with the BandLab web-based DAW). It's totally free, and is basically SONAR Platinum + around 2000 bug fixes / enhancements, and minus the 3rd party content.