scook

The key bindings for for Move Input Focus to Track/Bus Pane are global so they should work in both the Track and Console Views.

If you prefer, in this case, the MIDI track may be deleted after splitting the instrument track. Alternately when adding this synth to a project use any add method other than the Add Track menu and select only the "First Audio Output" from the "Insert Soft Synth Options" dialog. No need to add the MIDI track to the project.

Adding an additional audio track is not necessary. Right click in the instrument track header in the track view and select "Split Instrument Track" to gain access to the underlying audio and MIDI tracks. This audio track is setup to record the synth audio output. In this case the MIDI track is not being used for anything other than a way to get the synth positioned before the audio track input.

Yes, it is possible. Here is one way... Add a virtual MIDI cable to CbB (the "missing" interconnectivity) I installed LoopBe1. While not as flexible as LoopMIDI, it does not have the latency that LoopMIDI introduces. Add LoopBe1 as MIDI input and output device in CbB preferences Create the project Add audio and MIDI tracks to a new project. Set the MIDI track output to LoopBe1. Add the Step Sequencer to the MIDI track. Open the Matrix view and add samples to a couple cells in different columns Matrix View MIDI learn Click on one of the columns in the Matrix View and set to MIDI learn. Click the steps in a row in Step Sequencer. A couple of notes should be enough to teach the Matrix View column. Repeat for each column using different notes in the Step Sequencer Now the fun begins...clear the step sequencer and start programing the Matrix View using the step sequencer. Enjoy Note: LoopBe1 is defined as both a MIDI input and output device, take care to avoid creating a MIDI feedback loop. If LoopBe1 detects feedback it will mute its output. The may be re-enabled by clicking on the LoopBe1 icon in the Windows notification area. One thing to help avoid creating a loop is disabling Always Echo Current MIDI Track in preferences.

Synth plug-ins that generate audio without MIDI data be recorded using synth audio recording.

AFAIK, they call different functions. All plug-ins may be bypassed in the FX Rack. This is implemented in the DAW itself. The bypass button in the plug-in standard header is linked to the VST3 host bypass function. This must be implemented by the plug-in and is only available in VST3 format. Unlike the DAW plug-in bypass, the VST3 host bypass may be automated. IIRC, because this may be automated, it does not cause PDC to be recomputed like the DAW plug-in bypass options.

This error occurs when trying to bounce a MIDI track without selecting the associated audio track.

TTS-1 is GM Do you really need a drum map for it? The instructions I posted were specifically for creating an instrument track from an audio+MIDI pair where the MIDI track used a drum map. This has nothing to do with bouncing a synth. The process of bouncing a synth is the same with or without a drum map. Select the instrument track or audio+MIDI track pair and bounce.

Yes, if you downloaded the file today, by definition it is the current production release. My point was issues with the current production release should be posted in the thread dedicated to the release.

By design, files with a .dll extension are not scanned in the dedicated VST3 folders. Manufacturers should not install plug-ins with a .dll extension in the VST3 folders. The .dlls in these folders are consider support files not plug-ins. Only files with a .vst3 extension are scanned in the VST3 folders.

please read before posting It would have been nice had @2017 Laup followed up on this thread.

ASIO4ALL is a wrapper for the WDM drivers already installed on the PC. This is how all "generic ASIO drivers" work. True ASIO drivers are supplied by the hardware manufacturer written exclusively for their hardware.

the best place to report problems with the current release is... the current release thread. For 2021.01 the thread is

I don't have Kontakt but when I read in a Kontakt thread, it leads me to suspect the Zero controllers When Play Stops setting in the project. Based on previous threads, some Kontakt instruments go silent when this setting is enabled.

Yeah, those are completely unrelated to the error. Maybe it would be best to work through record issue first.

Doubt this is driver related. Possibly trying to write to compressed folder, an area marked read-only or anti-virus/malware is blocking file creation. Are there errors associated with this. If so, are they the same as the one posted? If not, what are they?

The exact wording of the error message or better still an image of the dialog often helps.

Always best to specify the year/month and build of the release (the current release is "2021.01 build 98") rather than referring to "this version". Freezing a track, turns off the PC and bypasses the FX rack. This has always been the case and it has always been possible to turn on the PC and enable the FX rack for additional processing but this practice is pretty dangerous. Accidently thaw the track and post-freeze processing is lost. If a frozen track needs additional processing, a safer way to do this is copy audio from the frozen track and archive the original.

Very similar to Why start another thread about essentially the same subject? You could have added the system details to your original thread. Although, I doubt the additional info would have changed the replies.

Yeah, as long as you have access to a 9 year old version of SONAR Producer.

Workspaces are not dependent on the project topology; screensets are.

Inputs set to None will change automatically to All Outputs Omni or External Outputs Omni when input echo is enabled. Which one depends on whether any plug-ins are generating MIDI data in the project. This is normal operation. Disabling Always Echo Current MIDI Track will prevent this from happening just by giving a track focus. MIDI track outputs default to the first output in preferences.

It is in the staff view http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Notation.30.html http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x20259 http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=0x2025E

It is possible to trigger all 128 notes using the virtual controller but it is necessary to use the Oct Dn/Up arrows on the right side of the controller to switch octaves. That said, to get the Drum Kit to fit in the range provided by the virtual controller or to make it easier to play certain kit pieces, it may be necessary to re-map some notes. This may be done using the Transpose MFX or a drum map. MIDI notes 7 through 11 trigger pattern play in SI-Drums (part of the SI-Drums documentation mentioned above),

Each instrument in SI-Drums has a dedicated MIDI note assignment. These assignments are in the documentation (click in the UI of the plug-in to give it focus then F1 to bring up the help) and also in kit pieces at the bottom of the UI where one may set the instruments to audition. Also there are two velocity layers for each piece triggered by clicking low or high on the instrument images. The keys on the virtual keyboard are not velocity sensitive. They all send a set velocity based on the velocity arrow keys on the virtual controller.