scook

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.

IIRC, there was a notice up for several weeks about scheduled maintenance happening today.

Try setting StopEngineOnASIOPanelOpen to true in Preferences > Audio > Configuration File

Ok fine bye

So a user cannot do this. It is a feature request for the developers. As you know, there is a dedicated area on this forum for feature requests. IIRC, someone already submitted this request.

Not that easy to do and maintain across updates Read about skinning bundled plug-ins here In short, plug-ins using images in folders are easier to re-skin and the skins persist after updates. Those without image folders like Sonitus do not easily lend themselves to re-skinning.

Yes, it is a time-limited demo. When the demo expires, the editor and most of the note detection algorithms are turned off. However, monophonic audio-to-MIDI and tempo detection continue to work. To use Melodyne beyond the trial period as a Region FX and have polyphonic support requires purchasing a license from Celemony. Review this page for the features supplied by each version.

Re-install it. BA keeps track of what it has installed and disables those options once installed. To reset the install option requires deleting a registry entry The key is in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Installers I cannot tell you the exact Melodyne key because I did not install the Melodyne trial. It should be pretty easy to determine which is the Melodyne key by looking at the data in the records.

Audio-to-MIDI by drag and drop depends on the Melodyne VST3. If the Melodyne Region FX (which also uses Melodyne VST3) is available the audio-to-MIDI and tempo detection features should be too. If Melodyne is not installed, a trial version is available as an add-on. Use "Install Addons..." on the BA menu shown below to download and install the Melodyne demo. When the trial expires, monophonic audio-to-MIDI and tempo detection will still work; the editor and advanced algorithms will not.

Plug-ins do not take up much space; samples and audio loops do. Before moving anything, consider reviewing the disk usage on C. Many installers to not provide a way to install VST3 plug-ins anywhere except the recommended "C:\Program Files\Common Files\VST3" folder. IIRC, some DAWs require VST3 plug-ins use the recommended folder. CbB does not but does have some special rules about scanning the default VST3 folder. Directory junctions are the best method for relocating folders from C to another drive. Once moved and the junctions are setup, no additional changes are needed to tell programs where to look for data because as far as the programs are concerned the data has not moved. Here is an example of how to move the "Cakewalk Content" folder. If there are legacy SONAR installs in the folder, Cakewalk Content can be fairly large. To relocate "Cakewalk Content" to the D drive 1) Using Windows Explorer move "C:\Cakewalk Content" to D:\ 2) Open a command window as administrator and type mklink /j "C:\Cakewalk Content" "D:\Cakewalk Content" Directory junctions work for moving almost anything and they are very safe. No registry edits, no uninstall/re-install and moving folders is easy. If plug-in folders must be moved here is the process to move the "C:\Program Files\Common Files\VST3" to "D:\VST3" 1) Using Windows Explorer move the VST3 folder in "C:\Program Files\Common Files" to D:\ 2) Open a command window as administrator and type mklink /j "C:\Program Files\Common Files\VST3" "D:\VST3"

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.08.html#1294603

may want to update the subject in the OP

a useful bit of information for u-he and Cakewalk support

I have no idea what u-he uses to test their plug-ins but I have just installed, scanned, loaded, played and removed v1.2.1 rev 3898 VST2 of this plug-in using CbB 2021.01 build 101 on Win10 Pro 20H2 build 19042.804. Successfully running a plug-in in another DAW may be as meaningful as successfully running other plug-ins in the DAW that cannot run the plug-in.

By default all synths that can send MIDI data including Jamstix have "Enable MIDI Output" turned on. I suppose one could confirm the setting. After adding Jamstix to a project with an instrument or audio+MIDI track pair, it should be automatically available as an input in the drum synth instrument or MIDI track. If you see Jamstix audio output, you are looking in the wrong drop down. Here is a video using the steps detailed above

When reporting this to support@cakewalk.com, in addition to providing the steps to generate the crash, please include the dump file. See

It's not a myth. Cakewalk always records the signal at the track input. Since plug-ins come after a track's input, the effected signal is after recording. So, to record a signal after plug-in processing it is necessary to place a track after the FX rack. Patch points and aux tracks may be used for this purpose. Create a new track and set the output of the track with effects to the new track using a patch point or Create an aux track and use it as the target of the track with effects. Still may be a good idea to record the original track while recording the effected track, just in case.

Often this type of behavior is related to the Zero Controllers When Play Stops setting. Note: this is a per-project setting. To change this setting for future projects make sure the modify the project template(s) used to create new projects.

I cannot reproduce any difference between clips starting at 0 and a wav export. To test, I created several tracks containing audio data all starting at 0 Then exported a mix of the tracks. Reimported the mix, flipped the phase of the mix and bounced all the tracks. The bounce completely nulled out. If there were any differences between the export and original tracks, the bounce would not null. Mp3 is another story. It is not a suitable format for exchanging project data.