scook

Do you know which algorithms are used when the trial expires? IIRC, there are 3 monophonic algos: Universal, Percussive and Melodic. Is it set up to automatically switch between them based on the clip or is it set to use one of them?

dumps compress quite a bit when zipped.

Not really enough information to go on. It may be plug-in related. Avoid using 32bit plug-ins. Here is some info on how to report crashes to support

The Melodyne installer from BA may still be on your machine. It should be in the Windows program list. You could try running a repair using it.

You have a full license for a commercial version of Celemony. It came with X3 Producer. It required creating an account at the Celemony site. The installer is available from your account on their site. The upgrade to Melodyne 4 Essential was free.

As a registered user of Melodyne (IIRC you have X3 Platinum), you should be using the installer from your Celemony account. The VST3 plug-in is used for Region FX. The default install path for the plug-in is "C:\Program Files\Common Files\VST3\Celemony\Melodyne"

The echo could be the result of enabling input echo on the track(s) in the DAW while also directly monitoring the mics in the interface. Turn input echo off when using direct monitoring. This may also solve the level problem.

this thread may help

http://helpcenter.celemony.com/hc-2/doc/melodyneStudio4/en/M4tour_PlaybackScrollZoom_studio?env=sonar#chapter-8

Try this from the main menu Edit > Preferences Make sure the radio button at the bottom of preferences is set to Advanced Click Configuration File under Audio Set UseHardwareSamplePosition to False Click the Reload Config Settings button

Yep, always been a freebie

Here are the instructions for a clean install. This will clean up the registry and let you perform the install as if it were the first time. If you have installed 3rd party plug-ins under either C:\Program Files\Cakewalk and C:\Program Files(x86)\Cakewalk consider temporarily moving the folders containing the plug-ins before performing step number 9.

The the data is not locked and the edit filter is set to Notes, it could be the tool selected. I mostly use the smart tool. That said, I think it is easier to work in the full Piano Roll View than the inline view.

In the track view to gain access to the notes in a MIDI clip change the edit filter ("A" in the image below) to Notes. This engages the inline piano roll view. When the edit filter is set to Clips, all operations are at the clip level. Or use one of the other MIDI views such as the Piano Roll View.

This points to a MIDI scale control. The MIDI scale is documented here The Audio scale is documented here

yes

Make sure to use one of the driver modes that can share a driver such as WASAPI Shared (in Win10), WDM or MME (always the last choice). set Windows and Cakewalk to the same sample rate. In Windows this is set in the audio device properties. In Cakewalk this is set in preferences for new projects and projects that do not have any audio clips. Projects that have audio clips get their sample rate from an audio clip header.

If this is in response to the suggestion to run a VST reset from preferences, there is no reason to avoid the process. A rescan is not the same as a reset. A VST reset clears and rebuilds the plug-in inventory in the registry. Platinum and CbB have their own inventories in the registry. The reset only affects the inventory of the DAW issuing the reset. Always run the scanner whether performing regular scans or resets from preferences. Do not run the scanner from the plug-in manager. If you do elect to run a VST reset consider generating the scan log.

The documentation has a New Features section at the top of the table of contents. There is also a "What's New?" option in the CbB main menu help that links to the current release notes and notes for all previous releases. By layout, I guess you mean the way the entire screen looks not the plug-in layout. Chances are a workspace is involved. These used to be called lenses. Either create your own custom workspace or set it to None.

Yeah, you will likely need a regular keyboard or pad controller to drive soft synths. FWIW, SI-Drums is velocity sensitive but most of the kit pieces have only 3 or 4 velocity layers. Until you get a proper MIDI input device, forget about clicking the plug-in UI with a mouse; use your PC keyboard and the virtual controller built into the DAW for real time input or enter the notes directly in the step sequencer, piano roll or staff view.

ACT is not used to send MIDI note data to a synth. ACT is used to control knobs and sliders on a plug-in UI. It may be possible use ACT to "play" the pads on a plug-in UI but I have not read about anyone using it that way. Synths like SI-Drums expect to receive MIDI data directly from the controller. This is done by defining the controller as a MIDI input device and setting the controller as the input on the synth's instrument or MIDI track. FWIW, I can find no reference to the drum pads on the R8 playing instruments in a DAW. It appears the device can act as a DAW audio interface and transport control only. That said, I have never used one and may have missed something in the documentation and my web search.

AFAIK, CUDA is not a solution for audio latency issues. The major sources of audio latency are The time needed by audio drivers to shuttle data between the audio interface and the DAW (audio buffer setting) The time needed for some plug-ins to see into the future in order to react incoming data (plug-in delay compensation) Although CUDA has been around for over 10 years, It would not surprise me if this were the case. . Not sure how much a DAW would benefit from it.

Here is a thread on how to report crashes and hangs In the interim, while it should not be necessary, you may be able to avoid hang on export by freezing or bounce and archiving tracks prior to export.

yes Exclude the ones in the shared folder path use the ones in "E:\Vstplugins64"

This has been suggested before on the old forum, this forum and other sources. AFAIK, this have never been recommended by Cakewalk or BandLab. I cannot recall if you have X3 Producer or a lesser version. The VX-64 Vocal Strip was bundled with X3 Producer. If you have Producer, restore the excluded plug-ins and use the X3 Producer version in your projects. The default location for this plug-in is C:\Program Files\Cakewalk\Vstplugins\Vocal Strip. Since you mention a "custom VST folder" I guess it may be there.