scook

More flexible MIDI routing would be nice. Until that time. Here is a method for sharing MIDI data hosted in one track across multiple tracks that does not rely on linking, copying or recording the same data multiple times. Add an instrument track with a synth plug-in that sends MIDI data such as Code FN42 MidiChFilter, NoteMapper, or VeloScaler. Then use the plug-in from step 1 as the input for all the instrument and MIDI tracks needing to share the data. Modify the data in the instrument track created in step 1 and all the tracks in step 2 respond to the change.

The controls shown in the track view depend on the workspace setting and track control drop down (image below)

It is no different than any other MIDI controlled plug-in that manipulates audio data. Create an audio track with input set to the appropriate audio source and enable input echo Drop the xils vocoder plug-in into the audio track FX rack Add a MIDI track with input set to your controller, input echo enabled and output set to the xils vocoder The setup may benefit from adding a compressor before the vocoder in the audio FX rack.

This or bounce+archive (+disconnect for synth) to ensure access to the audio and save custom presets by project or take note of factory presets used in the project notes and when possible, save installers. KORG leaves installers on disk after install so, they make it easy to backup installers. KORG is new to VST3 and they have struggled with their first attempts. Might be best to use the VST2 plug-ins for a while longer at least until their VST3 release notes are clear of showstoppers such as lack of persistent presets.

Like the page says at the bottom - "Login to get your personal offer"

As a rule, all audio should ultimately pass through the master bus and the master bus should be the only source of audio data coming out of the DAW to the main monitor inputs of the audio interface.

Since the introduction of VST settings in X-series preferences, scanning and setting scan preferences in the Plug-in Manager has been discouraged in favor of using preferences. The plug-in manager supports a subset of the VST settings available in preferences and is intended to be used with older Cakewalk products that do not have VST settings in preferences.

Yes, tracks or lanes, mute is not solo. This is the process This is how take lanes work in the PRV. The PRV works at the track level. Instead of take lanes for MIDI consider using separate tracks.

Soloing a track does not mute clips; it causes the DAW to ignore non-soloed data. Muting clips is a separate per-clip function and is the only function that works with "Hide Muted Clips."

To have more than one plug-in UI open at a time read the Recycle Plug-In Windows section on this page.

CbB no longer includes the Melodyne 4 Trial Version and BandLab no longer distributes the Melodyne 4 Trial either through BandLab Assistant or Cakewalk Installer. If you did not retain a copy of the Melodyne 4 Trial installer there is no way to install it.

A VST Reset: clears the VST Inventory in the registry then runs a VST scan The VST Inventory contains information about the plug-ins gathered by the scan along with has some parameters that users can set. The VST Inventory contains all VST2/3 plug-ins scanned whether they passed or failed the scan. This is why plug-ins that failed to scan may be listed in the scan log. The VST inventory is used by the DAW, along with registry entries created at install time for DX plug-ins to create plug-in lists bundled with the DAW.

Make sure HKEY_LOCAL_MACHINE\SOFTWARE\ASIO in the registry only contains an entry for the Behringer UMC 204. If there is an entry for RealTek, delete it.

There is no need to ever change a plug-in from an FX to a synth. If an FX plug-in can use MIDI data, open the VST2/3 drop down in the plug-in standard header to turn on "Enable MIDI Input". When an FX plug-in has "Enable MIDI Input" turned on, the plug-in will appear in MIDI track output drop downs.

Try enabling "Input Echo" the button right of Record in the instrument/MIDI track header.

May need to use WASAPI Exclusive driver mode with RealTek to adjust the Mixing Latency Buffer Size. This may help with distortion.

This is the first thing a VST Reset does before re-scanning plug-ins. Aside from the time it takes to run, a VST Reset is an easy way to fix most VST scan issues. When running a VST Reset, it is a good idea to enable "Generate Scan Log" just in case the Reset does not clear up the problem. The log may be useful as a diagnostic aid.

Cakewalk by BandLab

The solution is as old as the Digidesign interfaces pre-dating CbB by years. I am sure that read about the issue and solution on the old forum.

By default, CbB will "Enable MIDI output" for any synth plug-in capable of sending MIDI data. Jamstix4 likely has "Enable MIDI Output" enabled. If this is the case, any instrument or MIDI track input set to omni will receive the MIDI data from Jamstix. If the track has input echo enabled, the data from the Jamstix track will play. Track one in this image shows input echo has been automatically set because Always Echo Current MIDI Track is enabled in preferences and the input was likely set to None prior to giving the track focus. As a result, track one is now setup to play the data in the Jamstix track. Here is a similar thread

It is not a bug. The Console View has a function to show/hide the ProChannel in the Console view for selected track(s). The Track View does not have a ProChannel to display so there is no show/hide ProChannel function for the Track View. The image in the OP shows the Inspector left of the Track View. The Inspector contains a ProChannel and there is a default global binding CTRL+I to display the ProChannel for the track that has focus. Because this is a global binding it works in both the Track and Console views. This function is not exposed for re-binding. Currently there is no way to re-map CTRL+I in the DAW. Here is a similar discussion

How would I use these; is there a particular Cakewalk folder where I would place them? Or is there another method... (noob but learning! ? There is a brief explanation of how to install the ARP presets on my Goggle page.

see my reply in your thread

install the driver and update the firmware (if necessary) https://zoomcorp.com/en/us/digital-mixer-multi-track-recorders/multi-track-recorders/r8/r8-support/ It is very common for ASIO drivers to work at a single bit-depth, usually 24 bit.