scook

There may be an issue with v2 of Launchpad I am checking now.

There are only two files regularly involved in the copy process, the cw130auto.dll in shared utilities and the version needed for CbB. Launchpad first checks if CbB and cw130auto.dll are the same version If they are, the program starts CbB If not, the program looks for an appropriate version of cw130auto.dll in its backups If it cannot find an appropriate version of cw130auto.dll it returns an error message If it does find an appropriate version, if necessary, it make a local copy of the cw130auto.dll and attempts to overwrite the copy in shared utilities. If either copy fails it returns an error message The program attempts to resync on exit and always make sure the exe and dll agree before starting CbB. That said, there is always a chance the program could fail and leave the current CbB out of sync with the cw130auto.dll. This is why if one chooses to use Launchpad, they should always use it or at the very least run production from it to verify everything is in sync when encountering problems running outside of launchpad.

You best bet, if you ever use Launchpad, is always use Launchpad. It verifies cw130auto and CbB version info before launching CbB. Running the current version of CbB before exiting Launchpad is a good way to double check everything is OK to run outside of Launchpad.

Lauchpad is the tool I wrote for running CbB. Launchpad checks if cw130auto.dll is the correct version for CbB before starting CbB. If it cannot find the correct version, it displays an error message and won't start CbB. If the currently installed version of CbB is run outside of Launchpad it may fail if "Restore cw130Auto.dll on exit" is not enabled. This option insures the current cw130auto.dll is saved to the shared utilities folder when Launchpad is shut down.

5db is an unusual value start simple freeze just the synth by itself make sure the instrument track interleave is set to stereo

When running in ASIO mode to change devices in Cakewalk preferences both input and output devices must be deselected before a new selection is possible.

Thanks again for the input v2.0.5 released Tools Editor CmdArgs now available for Generic type only Table heading font size issue fixed VST Inventory filter on empty value now possible with filter string set to nul, "" or '' Fix bug on VST Inventory table refresh when escaping from filter Updated help and pdf

Drag and drop conversion of audio to MIDI (and tempo detection) uses the Melodyne VST3 plug-in. This was one of the featured added when ARA support was added to SONAR, The results do depend on the source AND the Melodyne detection algorithm. The trial version of Melodyne bundled with CbB reverts to monophonic support only when the full version trial expires.

Split the clips as needed

Yeah, I was trying to keep the table from being too busy but I will populate all cells now that columns may be hidden. For now to retrieve all non-VST3 plug-ins search for *dll in the Filename column I see the last minute addition of single key hot keys in VST Inventory is a problem too. They will be removed in the next release. Thanks

Thanks The confusing thing about the previous thread was the separation of Args a registry entry specifically mentioned for the Generic type and CmdArgs which had no similar type restriction. I noticed the the plug-in manager example but did not read that as suggesting CmdArgs was exclusively for Generic type. I will update the Tools Editor to restrict CmdArgs to the Generic type too.

From the "1/4" comment it appears you may be trying to install Add-ons with the Core. Try installing just the Cakewalk Core first. Then try installing the Add-ons. after the Cakewalk Core is installed and activated.

From what I can tell, it appears that Cakewalk is not sending CmdArgs. The Tools Editor is adding CmdArgs to the registry. I can't recall ever having an occasion to validate whether the optional entries do anything at all. If the records are written to spec, what Cakewalk does with the data is out of my control. The information about this process comes from a post @Noel Borthwick made in the old forum. Direct links to the old forum don't seem to work any more but the direct link is http://forum.cakewalk.com/FindPost/1850413. It now resolves to the OP. Further down in the thread is Noel's post I did not ask any questions about the info provided just used it as the basis for capturing and writing the data to the registry. Not sure if the feature is supported. This would be a question for Noel and BandLab.

This should be a separate thread but the short answer is yes, using Remote Control or ACT

The entries above the separator are a most recently used list stored in HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core\PresetMRU\{59137CAB-F9AA-4354-81C7-4F68292A785F} Deleting all the entries will remove them from the drop down and prevent the list from being created or Leave it there, it is harmless

Years ago, the standard way of adding synths in SONAR was placing them in the FX Rack. This method is still supported but should only be used with synths designed to work on audio data such as a Vocoder. Any plug-in, effect or synth, in an FX Rack that uses MIDI data needs an additional MIDI track routed to the plug-in for its MIDI data. The current method for adding most synths does not place them in the FX rack but instead uses the synth rack to host the plug-ins and uses an instrument track or audio+MIDI pair to transmit data to and from the synth.

Thanks for the feedback. The image is a new version of Tools Editor released yesterday and updated today. Yeah, it sounds a little clunky given Audacity does what one would expect of a DAW and not an audio editor. But if someone is determined to use it as an audio editor I guess it's good to know it can be done.

Not just hardware BTW. IIRC, LoopMIDI does not like UWP. I have not tested recently though. Since testing I have changed machines and not bothered to install LoopMIDI.

This was a complete rewrite so I did expect some issues although a couple of these should have been caught before the initial release. Thanks again. I really appreciate the feedback. Please feel free to post any other issues, requests or questions.

@Jim Hurley v2.0.4 - fixes missing drop down in upsampleeditor Should be available now on Google Thanks

Yeah, there is no DAW selection box in the main UI between File and Add. I will take a look at it.

No argument about better menus but do you have that many drum maps? CbB includes quite a few but. at least in my case, I can't use most of them. Instead of clearing out the default drum map folder though, I use a custom location, copying the few needed from the default location and adding several custom ones. Doing this significantly reduced the display and because they are in a custom location there is no chance of getting overwritten with a CbB updated.

BA uses the registry to keep track of what it has installed. It stores the data in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Installers If it finds a record there, the Add-in is disabled. Remove the record and the option will be available. Can't give you the exact record name because I did not install the Melodyne bundled with CbB. Inspect the data in the records and it should be clear which one is associated with Melodyne.

Older devices may not support UWP

v2.0.3 should be available now Fixes to upsampleeditor export and load Thanks again