scook

Feel free to use the themes I create as you wish The same goes for everyone When publishing a theme using borrowed elements it would be nice to add a credit in the theme's description but it is not necessary.

They are stored in the registry HKEY_CURRENT_USER\Software\Cakewalk Music Software\ActiveMovie\Presets

There are a couple of ways to convert audio to MIDI Dragging an audio clip into an instrument or MIDI track is the most direct. Click OK when the message on the left in the OP is displayed. This will create a regular MIDI clip. To open a MIDI clip in the step sequencer use the Convert MIDI Clip(s) to Step Sequencer... function in the Track View Clips menu.

It is one reason I only brought 3 themes from Platinum and have not created any new ones.

That's it - instrument tracks have an audio and a MIDI tab (T in the image below) Here is the CbB help for the Snap to Scale section (N in the image above) http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Inspectors.3.html#1239113 The CbB help pages are not indexed so searches on the old Cakewalk site only show SONAR results. Usually changing the product in the url to Cakewalk will open the current help page.

Themes in OP updated for 2020.04

Fortunately we have a list of all the changes for 2020.04

If the session was started with a user theme it might be a good idea to switch the Mercury or Tungsten then restart CbB. Old user themes mess up the the Inspector tabs in 2020.04.

Actually the old image is wrong. It shows a hybrid of the pre 2020.04 and current tabs. There is no Square-A tab in the old theme.

Not old, an emulation or a plug-in but a good source for http://www.websdr.org/

Thanks for the heads up

Announcement here Arranger track PC presets and a rollback option (just in case)

Great an EA release with a rollback option. FYI, user themes may not work with 2020.04 until updated For now stick with Mercury and Tungsten

There a two themes included with Cakewalk. The theme is set in preferences There are a few user created themes in this part of the forum

Make sure only the track being recorded has input echo enabled. I turn off Always Echo Current MIDI Track in order to have better control over which tracks have input echo enabled. Also some plug-in have the ability to generate or pass through MIDI data. It is a good idea to turn this off when it is not needed. For those synths that have this option, it is enabled by default. To review and set "Enable MIDI Output", open the plug-in UI and click the VST2/3 drop down above the UI. This image shows a plug-in with the option enabled. Please avoid creating multiple threads on the same subject.

This is not how the program works. By design, turning on input echo requires an input other than None on instrument and MIDI tracks. To that end, tracks set to None change to Omni when input echo is enabled. This is why I turn off Always Echo Current MIDI tracks and assume manual control of both the input drop down and input echo. Feel free to file a feature request.

Or build it into the project templates All my project templates have a bus after the default (aka master) bus.

The default "Entire Mix" is essentially "What you hear" - IOW all tracks and buses that point to the mains. As you know, the Export dialog also permits exports from the master bus or any track or bus.

Not a bug, I explain why later in the the thread linked above (note: monitoring icon = input echo)

Actually @Craig Anderton in CbB I route the master bus to a "final bus" which routes to the hardware output. Sonarworks would go in the final bus FX rack. It does not affect exports because exports are made using the master bus. There is no need to change routings for export. New tracks are always automatically added to the master bus because it is still the default bus. Of course, this routing assumes the headphones use the same main ports as the master bus. If the headphones can monitor different hardware ports, instead of a "final bus" a send on the master can do the same job.

In addition to using the Quad Curve EQ in the Inspector ProChannel, the plug-in is available in the console view

I do not use Sonarworks but if I did, I would create a bus between the master bus and the hardware outputs. Add the plug-in to this bus and always use the master bus for export.

Not a bug. Maybe this thread will help explain