scook

Why not upload the file to a hosting service and post a link to the file here? I use GoogleDrive but OneDrive, DropBox or any file host will work. Or upload it directly here if you don't mind the file size affecting your forum file upload quota.

Instead on uninstall, try using the rollback installer provided in the product announcement. FYI, a simple uninstall does not remove custom setting as the registry and user directory are left untouched by the uninstall process.

The virtual keyboard controller was added in March 2015 to SONAR Platinum/Professional and Artist. Of course, this is still available in CbB. Prior to March 2015, adding a virtual controller to SONAR usually meant adding a virtual MIDI cable such as LoopBe1 and a third-party software keyboard (my favorite PC73 from ChordPulse is no longer available). For example, here is a thread about this from the old forum http://forum.cakewalk.com/Connecting-a-software-like-VMPK-Virtual-Midi-Piano-Keybaord-to-Sonar-Platimum-m3195394.aspx

Change the Edit Filter drop down (C in the image below) back to Clips

Make sure offset mode (I in the image below of the large Mix module) is not enabled. For more, see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Automation.13.html

The status of this product has not changed since 1 Mar 2019 The VST3 plug-in was only available to SONAR Platinum/Professional users.

Can't tell if this is about MIDI or audio. By default, MIDI requires arming a track, but it is optional, see Allow MIDI Recording without an Armed Track Still recording would not be based on track selection, it depends on input settings.

Region FX work at the clip level. Which take lane the clip resides in does not matter.

CbB may still generate a minidump. See this for how to report dump files. If there is no dump, try temporarily setting ExceptionHandlingSeverity to 7 in Preferences > File > Initialization File. This may force a dump.

For patterns check out linked clips For mapping a MIDI controller to virtual instruments review ACT

Hello Rogerio. I tried to use Your scripts, downloaded both files into the same directory and when I run the main script I am getting such error: What am I doing wrong? The error indicates the file you downloaded is an html document not a CAL script. The link in Rogerio's post is to an old forum post. The link to the actual CAL script is near the bottom of the post Rogerio linked in his post.

It depends on the control. If the numeric value is displayed and editable such as volume or EQ settngs, double-click value in the ProChannel, Track Inspector or Console view channel strip to edit the value.

Turn off Always Echo Current MIDI track

Yes, don't select one. There is no requirement to have a track selected. Edit > Select > None will clear the current selection.

I doubt anything has changed since @Noel Borthwick wrote in http://forum.cakewalk.com/XP-services-that-can-be-safely-turned-off-m1238330.aspx but as Noel noted later in the thread I have also read a couple of posts where users posted better results after tweaking for background process. Might be worth testing on a case-by-case basis.

For devices not designed to work together it is not worth the effort if it can be done at all. There are manufacturers who design their interfaces to work together. This is done at the hardware level and at the driver level. IOW, the devices share a common clock and communicate with the DAW using the same ASIO driver. AFAIK, there are no manufacturers who design their interfaces work with hardware from their competitors. To use the M-Audio device with the Focusrite device requires figuring out a way to share a common clock and a WDM or WASAPI driver. There is no ASIO driver that supports both M-Audio and Focusrite devices. It is possible to have to M-Audio and Focusrite devices connected to the DAW but in ASIO driver mode, only one device will be available at a time.

Look at GeneralMidiSMFs in TTSSEQ.ini

Windows Magnifier

The only way CbB produces MIDI from audio using drag and drop relies on a Melodyne VST3 plug-in. The plug-in must be in the VST scan path and should show up in the "Sort by" plug-in lists shipped with CbB. There must be a licensed copy of Melodyne installed, a functional trial of Melodyne 5 bundled with a recent version of CbB or a timed-out trial of Melodyne 4 bundled with older versions of CbB. Prior to Melodyne 5, the trial version of Melodyne 4 shipped with CbB continues to perform monophonic audio-to-MIDI and tempo detection after the trial period. The other methods of audio-to-MIDI creation in CbB, audiosnap and drum replacer, do not use Melodyne.

Dragging audio to the timeline does not create MIDI note data, it creates a tempo map. Dragging audio to a MIDI or instrument track creates MIDI note data. Both of these processes rely on Melodyne.

The drum replacer is also available from the Cakewalk Installer. Except for access to BandLab and CbB remote authentication, there is no need to mess with Bandlab Assistant.

The current project sample rate is determined one of two ways. If there are audio clips in the project, the sample rate is read from one of the audio clip file headers. All audio clips in a project have the same sample rate. If there are no audio clips in the project, the sample rate is read from the "Sample Rate" setting under "Default Settings for New Projects" in Preferences > Audio > Driver Settings The transport module shows the current project's sample rate and the Record Bit Depth that will be used the next time some audio is recorded. See the answer to 1 for where the sample rate comes from. They don't have to match but it may make things easier if they are set the same. Windows may be set to 44.1 or the DAW to 48 take your pick. There is practically no difference between the two. As noted in the reply to 1, in projects that have no audio clips the sample rate is read from preferences every time the projects are opened. In projects that have no audio clips, the Render Bit Depth is what matters as it serves as the default in the export dialog, however; the actual bit depth used may be set in the export dialog. What bit depth should be used for export depends on how the export file will be used. If the export file is for playback only, select a bit depth compatible with the playback device(s). If the export file is going to be processed further (mastering?) use 32bit (or 64bit if the 64-bit Double Precision Engine is enabled and the mastering software can load the file). The current export dialog allows users to create tasks to export. Think of these tasks as the templates you need for projects going forward and update your custom project templates. Similar tasks may be added to existing projects too.

No, as long as there is no audio being recorded at all, it does not matter but it does not hurt to be prepared just in case they decide to record some audio. Audio from a soft synth will be at the project sample rate at the bit depth determined by the plug-in. When frozen, bounced or exported the Render Bit depth is used as the default with an option in the case of export to override.

May want to change the Record Bit Depth (currently 16) to be the same as the Driver Bit Depth (currently 24).