scook

The project sample rate shown in the transport module is determined by The default sample rate from preferences as shown in the image above IF the project has no audio clips. If the project has audio clips the sample rate is read from one of the clip headers. All audio in a project must be the same sample rate. The bit depth shown in the transport module is Record Bit Depth NOT Audio Driver Bit Depth. Audio clips in a project do not have to be the same bit depth. So, this value does not necessary reflect the bit depth of existing clips in the project.

I use the Windows Magnifier Windows+Plus = magnifier on Windows+Esc = magnifier off

That's pretty good Elements does not have spectral repair so the clean up is tedious and the results, in my case, are not as good. Acoustic Guitar METRONOME issue - File is 24bit 44.1 elements fix.wav update: link removed

%appdata%\bandlab-assistant \Downloads, however; BandLab Assistant deletes installers after running them The folder location is displayed on the BandLab Assistant Settings page. Click the gear in the upper left of BA to access the Settings page.

To add the plug-in to MIDI track input drop downs, select "Enable MIDI Input" in the VST2/3 drop down above the TH-U UI

Try enabling the keystrokes button above the plug-in UI. "J" in the image

If the plug-in supports CC control of volume then it can be done via MIDI. If not it will have to be done in the plug-in UI or in the audio track(s).

Volume is not a note property, velocity is. Volume is generally CC7. That said most drum synths have a way to adjust the volume of individual kit piece in the UI and many have a way to split out the different kit pieces to separate audio tracks adding another layer of volume control.

If Windows and CbB are sharing the same audio device make sure both are set to the sample rate.

Base Octave for Pitches

Virus scanner maybe? I add scanner exclusions for the DAW processes and where the DAW writes its data.

I can't tell from the snippet of the log if the dlls were scanned. This is the install path for the supporting files not the plug-ins. Normally these folders contain documentation, samples and images used by the plug-ins. Normally the plug-ins are not in these folders. This path should be removed from the scan path. The log also shows "C:\Program Files\Cakewalk" in the scan path. This user added path contains a lot more than VST plug-in dlls. It should be replaced with the default "C:\Program Files\Cakewalk\Vstplugins" to pickup the AAS player. My guess is "D:\Beats production sound kits" also does not contain VST plug-in dlls. If so, it should be removed. By default Studio instrument dlls install in folders under "C:\Program Files\Cakewalk\Vstplugins" That said based on this image the Studio instrument plug-ins are either in a user designated non-default location or were accidentally deleted.

If Studio Instruments are listed with the FX plug-ins, this is a scanning error. Often this is corrected by running a Reset from the VST Setting in preferences. I am not sure from the description if the tracks are getting setup properly. Try using the Add menu (see the "To create instrument tracks" section) until you are comfortable with how Cakewalk routes data.

I do not upload anything to the forum. For original material, my posts contains links to my imgur.com account (for images) and Google drive (for everything else). There is a way to manage uploaded files on the forum. On the PC version of the forum in the upper-right there is a menu attached to your username. One of the options on that menu is My Attachments. I have noticed when I accidentally upload a file such as trying to link an image from the documentation, there is a delete option on the attachment at the bottom of the post.

IIRC, this is true except for the Engineering FX Suite. The LP plug-ins were removed from this installer with the introduction of the LPhase series. Don't have the X3 versions handy to say for certain but the LP plug-ins may have been updated after X3. EngineerFXSuiteSetup_1.0.0.13.exe contains the last release of the LP plug-ins.

Don't use Kontakt so this may not be helpful. The piano and SI-Drums ignore the channel setting. I know Kontakt uses channels. Is it possible Kontakt is not listening for data on channel 10?

In ASIO driver mode only one ASIO driver may be used at a time. Deselect the current input and output device to make a new selection. If ASIO4All or any other generic ASIO driver is installed consider uninstalling it. There should only be one ASIO driver for each device and a generic driver appears as a second driver when a factory driver is installed.

Try this Record 1 Bar of the metronome Select the clip, open the Loop Construction View and in the LCV Click the Loop button Set the Slice drop down to "No Slice" Roll out the clip and try different tempos Instead of rolling out the clip, the Matrix View may be used to play the clip.

It is pretty hard to compare binary files like MIDI files by simple inspection. Text files are much easier to read and compare. Here is a website containing a couple of utilities to convert MIDI files to csv text files and back to MIDI. Here is the direct download link to the Windows binaries buried in the middle of the page.

I believe that does not indicate who's cost

Use a drum map or create a step sequencer template. A step sequencer template is an empty step sequencer pattern step up as desired. After adding the synth, set the output of the MIDI track to the drum map to configure the step sequencer. When using an instrument track, the drum map assignment is made in the MIDI tab of the track's inspector. Without a drum map loading a step sequencer template performs the same task but must be loaded for each instance of the sequencer. IOW, a drum map is a per track setting, a step sequencer template is a per-sequencer setting.

Yeah, my image above used TTS-1. Usually I just reply to "type in the number" but for some reason this time decided to look at the drop down before replying.

This is often caused by a combination of two settings. 1. Always Echo Current MIDI Track is enabled (the default). As a result, inputs set to None are automatically switched to "All Tracks > Omni" when the track is given focus. Instead of not listen for any MIDI data, the tracks are receiving all MIDI data coming from anywhere. Turning this option off in preferences and setting inputs to specific MIDI sources (such as a controller) are the solution. This has been the subject of a recent thread 2. One or more plug-ins have "Enable MIDI Ouput" turned on. Some plug-ins have the ability to generate or echo MIDI data out of the plug-in. When a plug-in has this feature, it is enabled by default. Turn this off if the feature is not needed. This may be done one of two ways Some methods of adding plug-ins show the Insert Soft Synth Options Dialog. "Enable MIDI Output" is near the bottom of the dialog. To change the setting of a plug-in already in a project use the VST2/3 drop down above the plug-in UI as shown in this image As a result of these two settings, tracks may be listening for MIDI data coming from anywhere and one or more plug-ins are sending data (along with any data coming from the controller).

It is pretty hard to have more then one copy of VstScan.exe install. So this means both X3 and CbB are most likely using the same scanner. Make sure to run the scanner from preferences NOT the plug-in manager. Check Windows Task Manager to see if VstScan.exe is running. If it is kill it. Then run a VST Reset from preferences with "Scan in Sandbox" and "Generate Scan Log" enabled. The second option creates a log in %appdata%\Cakewalk\VstScan.log If the scan fails to run to completion the log may show where the process stalls.