scook

Enable Input Echo on the track. It is the button to the right of Record.

I have not seen any mention of the reference guide in a language other than English. @Morten Saether is there a French version of the reference guide.

This is the worst performing driver intended to be used when nothing else is available. I believe the Komplete audio 1 has a manufacturer supplied ASIO driver. See https://support.native-instruments.com/hc/en-us/articles/360001194217-Installing-the-ASIO-Driver-for-KOMPLETE-AUDIO-1-2-6-MK2-Windows- For devices that do not have an ASIO driver the WASAPI driver modes a the second and third choices for Win10.

MIDI import is primarily used to bring MIDI clips into an existing project. The import process strips tempo info out of the MIDI file. Use File > Open to open full MIDI performances. If there is no MIDI output device selected in preferences when opening a MIDI file, TTS-1 will automatically be added and setup to play the file. Opened this way the file is ready to play and is a good way to see how a file is routed to a synth. Make sure when saving for the first time to change the file type to a Cakewalk project in the File > Save As dialog. By default, open MIDI files save as MIDI files and MIDI files do not retain plug-in assignments or other non-MIDI data. A simple instrument track and MIDI track may drive one synth. The classic way to use the same MIDI data with multiple instruments is duplicate the MIDI track using linked clips, however; there are other ways. For a while I used a "master" MIDI tracks and connected it using a LoopBe1 virtual MIDI cable to a series of other simple instrument and MIDI tracks to drive multiple synths. Recently it occurred to me to set up the master track using a simple instrument track and a plug-in capable of sending MIDI (such as CodeFN42 NoteMapper, VeloScaler or MIDIChFilter) to perform the routing instead of a virtual MIDI cable. Adding a synth to the FX rack is the old method of synth routing. It still works (for a single synth) but should be reserved for synths that operate on an audio stream such as a Vocoder. Traditional synth plug-ins should use a simple instrument track or one or more MIDI tracks for the synth input and one or more audio tracks with their inputs set to the synth instead of placing the synth in the audio FX rack. Not sure I understand. Do you want to map the notes in a MIDI track to multiple instruments like a drum kit? There are two basic track types in CbB: audio and MIDI tracks. A third track composed of a MIDI track input and audio track output exists too. It is called a simple instrument track. In order to use a Synth plug-in, it must have at least one audio and one MIDI track OR a simple instrument track. The tracks may be added at any time. There are a variety of ways to add synths to a project. Here are some of them Add Track menu. For info about this method see midway down this page http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x18A8C Drag and drop from the plug-in browser Insert synth option in the upper right of the synth rack Insert in the main menu Right-click in the track view header area All of the methods have options to add tracks. Tracks may also be added at any time and routed to synths as needed. In the track context menu are options to make instrument tracks from existing audio and MIDI track pairs routed to a synth and split instrument tracks into audio and MIDI tracks.

CbB always records the signal at the track input. CbB has no control over audio levels coming into the DAW. This level must be set before the DAW. Plug-in effects are not recorded as they are applied after the track input.

From https://www.meldaproduction.com/MDrummerDrumEmpire2020/installation

Directory junctions are a good and safe solution. They work when relocating folders for practically any application. All the sfz engine synths developed by RCG and Cakewalk store the sample paths in the registry. But rather than mess with the registry, I have recommended directory junctions for years. The sfz files used by the synths all use relative paths to their samples.

If the project works at a given buffer size (I don't mess the queue) and fails at a smaller size then the project is too complex for the PC at the lower buffer size. Using the existing hardware there are two ways to deal with this: make the project less complex by bypassing plug-in, freezing or bouncing and archiving tracks, creating a temporary mix track and archiving everything except the track being recorded OR do not monitor the instrument being recorded from the DAW, use the direct monitor feature on the interface (the input/host knob in the Komplete 1 is for mixing the direct signal from the interface and the rest of the audio from the DAW).

The DAW is not receiving any notification from the Session Drummer about missing samples. The DAW launches the plug-in and if the plug-in loads OK that is all the DAW cares about. If the plug-in has problems finding samples, that is a problem the plug-in has to resolve. It does so by writing a log and throwing up a message. When it comes to audio clips in the project, using per-project folders in their default location under the project file makes projects completely portable as the project stores clips with relative path names. Using non-default locations for per-project audio folders or failing to import clips into a project causes the DAW to refer to the files using absolute path names. This can be a problem is one moves things around.

The DAW has no idea if Session Drum is sample based or if the program loaded by Session Drummer is missing sfz files or samples. The plug-in issues the load failure messages. It would be up to the plug-in to search for missing parts of the program. Given the samples could be anywhere or no where at all, depending on the size and number of disks attached to the PC it might take quite a while for an exhaustive search.

The DAW has no idea if a plug-in uses samples or not

WASAPI Shared runs at a fixed buffer size. In this case, the slider is disabled. The slider should be available WASAPI Exclusive, MME and WDM modes. Whether the slider works for ASIO is up to the driver. Some manufacturers support buffer size requests from the DAW. Some do not. This feature was added in CbB 2019.11,

Here is what Preferences > Audio > Configuration File looks like. Again this is an "Advanced" setting so make sure the Advanced radio button is selected at the bottom of Preferences. Yeah, directly connecting a mic to the interface is a good idea.

The driver appears to be old. I checked the Focusrite site and the current driver is 4.65.5 https://customer.focusrite.com/en/support/downloads?brand=Focusrite&product_by_range=551&download_type=software It would be nice if someone familiar with Focusrite gear would join in. @Jonathan Sasor what do you think? But this may no be the issue. One think to do is validate CbB plays back normally. Add an audio clip to a new project and test it. May also want to play the recorded clip directly from the project audio folder using different software and see if the clip still distorts.

Maybe support can help support@cakewalk.com aside from that I know of one thread remotely similar

There are so many ways to customize CbB it is difficult to know exactly what a user sees on their screen. That and word choice can make problem solving challenging.

Here is an image of a MIDI track and a simple instrument track first set to Clips then set to Notes. AFAIK both support clips and inline PRV. At least until the simple instrument track is frozen.

Are you sure about this?

The default edit filter setting for new tracks is Clips. Unlike Cakewalk projects, MIDI files cannot retain edit filter settings or any non-MIDI data. Opening MIDI files results in new track creation every time. It is possible to use quick groups to change edit filter settings on selected tracks. Select the tracks, hold down the CTRL key and change one of the selected track's edit filter. The other selected tracks will change too.

A few releases ago, BandLab started providing rollback installers. This is a good way to toggle between the current and previous releases but there is no rollback to 2018.05 so options are limited. Especially if you did not retain the 2018.05 full installer. The easiest way to keep older versions live while keeping current is using Cakewalk Launchpad. This was one of the motivations for the tool. It is available on my Google page. After unzipping Cakewalk Launchpad into a folder on your PC, run the program and run Quick copy from the File menu. Then run BA to update CbB. After the update both the current version and the older version(s) are available to run from Cakewalk Launchpad. Switch versions using using drop down in in the bottom left of Cakewalk Launchpad then run CbB from the File menu. That said, trying to use versions older than 2020.04 along with 2020.04 and newer has issues. There were changes made to the resource files that cause some problems. The safest way to switch between versions older than 2020.04 and newer versions is backup and restore. Or uninstall and reinstall if the full installers are available.

According to http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.43.html the suggested action is Contact support with recipe/project file. The email address for support is support@cakewalk.com In addition to the project file and the step used to get the failure (plug-in names would be nice), they will likely want to know about the hardware, audio interface, OS and version of CbB being used.

It might help to provide hardware details. All we know at this point is a preamp model going through some Focusrite interface. It seems strange that the information to the right of the slider in the mixing latency section of Driver settings reports 256 sample buffers but the ASIO info below that show values more in line with 512 sample buffers. I believe some Focusrite devices have large safety buffers but have no first hand experience with their hardware. Still the difference between the two sets of numbers does not look right to me. What does the Focusrite ASIO client report? I was under the impression Focusrite supports adjusting ASIO buffers from the DAW, however; the Buffer Size slider is disabled. This indicates the driver does not support the feature. In addition to the supplying the interface model, it may help to know the driver version.

Is Focusrite the device shown in the Record Latency Adjustment section of Preferences > Audio > Sync and Caching? If this page is not visible in preferences, click the Advanced radio button at the bottom of the preferences window. Is there more than one driver shown in Preferences > Audio > Devices?

LICEcap What I see is a continuously changing tempo in the transport module. My guess is this is playing havoc with the plug-in. Tempo synced plug-ins need a steady tempo. Given the current tempo map, tempo synced to host may be a bad choice. Could set the tempo to an average of the tempos or smooth out the tempo changes in the Tempo view. Changing tempo using tempo synced plug-ins can cause audio glitches as the plug-ins sync to the new tempo. This may be avoided by using clip based effects and a steady tempo in the clip or aux tracks/buses with the plug-ins at fixed tempos switching between the tracks based on the current tempo.

I am pretty sure @bitflipper does not use Pace protected software.