scook

The project templates supplied by Cakewalk may be overwritten without notice with a later update. The only way to prevent losing custom templates is avoid using the template names supplied by Cakewalk or create a custom location for project templates. The template path is specified in preferences. The Cakewalk supplied templates update the default location only.

The image is set in the notes browser IIRC, it is a little fiddly with project templates. The image area does not get written when the template is created but will when the template is updated.

Drum map presets are not plug-in instruments that appear in the plug-in browser Here is the documentation about drum maps. It saves a lot of typing. The Studio Instrument Suite (including SI-Drums) is a separate install performed from the Install Addons... option found in the menu to the right of the CbB Open button in BandLab Assistant. Once installed and scanned, the plug-ins will appear in the plug-in browser.

Open a project then open preferences with the project open, see if this make a difference

I used this string in Google site:forum.cakewalk.com Lexicon MX 200 There are a few detailed posts about users setting it up like this one http://forum.cakewalk.com/FindPost/1577372 There are a couple more in the thread This post is about the MX300 http://forum.cakewalk.com/FindPost/2958074 There were a few from 2005. Can't believe it is worth the effort but it is one way to spend a long weekend.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x2011A

Search the old forum. There are a few threads about setting it up. The VST plug-in is for controlling the hardware. The audio routing is handled like any other external hardware.

https://help.cakewalk.com/hc/en-us/articles/360021858293-What-happened-to-Cakewalk-SONAR-What-happens-to-everything-I-paid-for-

No, auto-save is not a per-project setting. The Project section on the preference screen contains the settings stored in the project.

To set the sample rate for new project use the File > New dialog and make sure to add an audio clip before exiting the project.

Yes, I hope everything gets fixed to every ones satisfaction too.

Yes, an audio interface can only run at one sample rate at a time.

Suspend Audio Engine When Cakewalk Is Not in Focus but sharing the ASIO driver should not be a problem with most Windows programs as they do not use the ASIO driver. Most use regular Windows drivers. Those programs that can use the ASIO driver usually may be set to use Windows audio too. This eliminates the need to share the ASIO for most users. As a rule web browers do not need access to low latency ASIO drivers unless they are being used for applications like web-based DAWs. They run fine using regular Widows drivers. Only a few support ASIO drivers.

This could all be avoided if drum synth plug-in developers added the appropriate information to their plug-ins. There is an opcode available in the VST specs that provides for assigning names to notes. The old Cakewalk Session Drummer, the BFD series and now Sitala appear to be the only plug-ins whos developers bothered to do this. Implemented this way the note names in the DAW are synced with the plug-in. Add a kit piece/swap out or rename a drum in the plug-in, refresh the DAW and the new names appear in the step sequencer and PRV Notes Pane no instrument file or drum map needed. Since most plug-in developers choose not to add this feature it up to the DAW developers and users to work around the missing data. If the goal is a better way for Cakewalk to associate instrument names with notes making alternate note names in the Notes pane persistent across sessions seems like a more direct solution - request logged some time ago.

Don't have the unit and have no experience with one. I would not consider it as my primary DAW interface because it is battery powered and class compliant (IOW no manufacturer supplied ASIO driver).

If you want to use FreeG at least get the 64bit version directly from Sonalksis If loudness monitoring is important, Insight 2 is on sale for $39 at Plug-in Boutique. Melda Production's MFreeFXBundle includes 64bit loudness meter and spectral analyzer plug-ins. While free, they also offer a licensed version with a few extra features. The license is current on sale for $30. For a free alternative to the gain control in FreeG consider Blue Cat's Freeware Plug-ins Pack II

intellectual property

There are not a lot of direct audio inputs on a PC and none of them are designed for DAW use. There may be a line in or mic in that could be used but the results won't be that great. Kind of defeats the purpose of having a $300 direct box. If the goal is to connect a guitar or microphone to the PC for recording in a DAW and the Torpedo C.A.B. M+ can be exchanged for an audio interface, it may be a good idea to do so. You need an decent audio interface more than a device like the Torpedo C.A.B. M+ to work with a DAW.

Cakewalk MIDI import strips tempo out by design so the existing project tempo map is preserved but it is possible to copy tempo maps between projects. With the project to change open open the MIDI file containing exported tempo map in Cakewalk creating a new project make a time-based selection (it may help to open the tempo view) use Copy Special making sure to include Tempo Changes paste into the other project

It really does not matter which analog output you choose from the Torpedo C.A.B. M+, it needs to go into something that digitizes the signal and sends it to the PC. This device is commonly caused an audio interface. There are some that look like a 1/4 to USB cable but I would budget at least ~$100 for a entry level interface rather than going the cable route.

Usually I/O is presented in pairs where Input 1 are interface input channels 1+2 Input 3 are interface input channels 3+4 Output 1 are interface output channels 1+2 Output 3 are iinterface output channels 3+4. and so on. A audio track input drop down looks something like Left 1 Right 1 Stereo 1 Left 3 Right 3 Stereo 3 where Left 1 is input channel 1 on the interface Right 1 is input channel 2 on the interface Stereo 1 is input channels 1+2 on the interface Left 3 is input channel 3 on the interface Right 3 is input channel 4 on the interface Stereo 3 is input channels 3+4 on the interface Outputs are setup the same way.

There is no point is capturing the whole screen when the error message is a tiny window in the middle of the screen. Just capture the error message and post it. With the error message in focus, ALT+Printscreen and paste into Paint or any image editor and save. The result looks something like this: or edit the full screen down to the error message before posting. It is much easier to read this way. Thanks. Also may want to use meaning subjects when posting. Instead of "Error Message" something like "Audio Setup Help needed" or "Audio Playback Decide Not Found" would make more sense. What audio interface, driver and drive mode (ASIO, WASAPI Shared/Exclusive, WDM, MME) are you using?

They do the same thing at different points in the signal flow. See the signal flow diagram The gain lowers the signal before the FX rack and ProChannel. The volume lowers the signal after the FX rack and ProChannel. That said, I usually leave the volume at unity and adjust the input gain or make the adjustments at the bus/track level before the signal even hits the master.

Yes, see page 3 of https://dl.two-notes.net/downloads/QSG_CABM_+.pdf The mini-USB port on the device is for the Control Unit software NOT for sending audio to the PC see page 2 and 4 of the same pdf.

It does not matter if adding a track template or adding the drum map to an existing project or project template. The Out Port assignments are all made following the same rule. Out Ports in a drum map are dynamically assigned to the track based on the MIDI output it is replacing. If there is no prior MIDI output assignment or the Out Port assignments become invalid, the DAW adjusts them so that the data has somewhere to go. IOW, the design requires a valid Out Port assignment, if possible, in drum maps used by a project. This is similar to the dynamic assignment of Omni when input echo is enabled on tracks that have no input assignment. Could there be a different way to handle this...yes. Is the current process inconsistent...no. That said, there most definitely is room for improvement in how MIDI data routes and PRV note pane labels are created, maintained and applied to projects. AFAIK, this has been on the to-do list for some time.