scook

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.

On 3/12/2021 at 10:10 AM, Resonant Serpent said:

For something as critical as downloading/installation, having a 1/4 just flashing with no other feedback is woefully inadequate.

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

Quote

This information is not published or supported so don't ask too many questions
 
External tool configuration info is stored under HKEY_LOCAL_MACHINE here:
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Tools Menu. 
There are three categories of tool types which are supported:
Generic - these are normal tools that are not project data context sensitive
WaveEditor - tools that operate on project data such as wave files
SysxEditor - Tools that edit sysex
 
Common tool arguments:
 
ExePath  - This is the fully qualified path to the tool executable. Type=String
MenuText - name of the tool as appears in menu Type=String
Type  - Tool type <Generic, WaveEditor, SysxEditor> Type=String
StatusBarText - [Optional] expanded text that appears on status bar when the tool is selected in menu Type=String
Modal  - [Optional] If the tool should open its window modally blocking access to SONAR while running <0/1> Type=DWORD
CmdArgs  - [Optional] command line arguments such as switches passed to the tool if any. Type=String
    The following special arguments are expanded:
     - /ParentWnd$ this is the window handle of the application frame
     - /VSTInventoryRegKey$ this is the key to the VST inventory
   
CurrentDirectory- [Optional] The current directory in which the tool should execute Type=String
HelpFilePath - [Optional] Path to the help file for the tool if any Type=String
HelpFileTopic - [Optional] help file topic ID. Topic ID to be loaded from help file Type=DWORD
  
 
Generic tool specific arguments:
 
Args  - [Optional] specific expanded line arguments when the generic tool Type=String
    works on the SONAR selection and takes a file name such as a wave file
    The following special arguments are expanded:
    $(FILE)  - the fully qualified file name of the wave from the selection
    $(FILEBASE) - the base file name of the wave from the selection

Generic tool example:
[HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Tools Menu\Plugin Manager]
"ExePath"="C:\\Program Files\\Cakewalk\\Shared Utilities\\PluginManager.exe"
"MenuText"="Cakewalk Plug-in &Manager"
"StatusBarText"="Run Cakewalk Plug-in Manager"
"Type"="Generic"
"Modal"=dword:00000000
"CmdArgs"="/ParentWnd$ /VSTInventoryRegKey$"

WaveEditor tool specific arguments:
 
ShortFileName - <0/1> [Optional] Instructs tool to use short (8.3) file names for wave file argument. 
                           if the tool requires short file names on the command-line Type=DWORD
RegionFlag - <0/1> [Optional] Expands to pass "/REGION:<start>,<duration>" to the tool on the command-line. 
                    Some wave editors like SoundForge used to use this format where the region specifies the
                    start and end of the selection to be edited in samples Type=DWORD
 

 post edited by Noel Borthwick [Cakewalk] - October 17, 09 4:06 AM

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.

4 minutes ago, murat k. said:

We need this kind of feature in Drum Maps too.

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

Ok, just a minute

Great

Thanks again

Ok, Google finally refreshed.

I believe v2.0.2 addresses the environment and upsampleeditor.ini errors.

After recompile, I could not generate the two other iniWrite $tbl errors. They may be related to the environment failure.

If they continue, please let me know which tools are throwing them I will take another  look.

Thanks for the feedback.

The iniWrite failure for the UpsampleEditor happens when no PluginUpsample entry  is present in Aud.ini

I'll need to add a check for that. That will take a minute.

Can you tell me which programs are throwing the other iniWrite errors?

Hmm, that should be a Windows environment variable

I will remove the code.

It is not needed any more

Give me a minute and I will post a new release.

No need to force the import to 24bit. Leave it at the original bit depth. The engine runs at 32 or 64bit based on the Double Precision Engine setting. The other setting to check is Render Bit Depth used for bounce, freeze and export. By default, it is 32bit. Any new recording uses the Record Bit Depth setting on the same page as Render Bit Depth.

Categories are stored in a SQLite database %appdata%\Cakewalk\Library\Library.db in the plugin_properties table

There are three sources for tags:

• The VST3 plug-in manufacturers
• The user through the plug-in browser
• Cakewalk when they initially created library.db

AFAIK, the only way to reducing the number of tags is directly manipulate Library.db.  

I like DB Browser for SQLite for SQLite db work.

What I find annoying with the category drop down is it mixes FX and synth categories in one big list.

User created layouts are not automatically maintained. This is one of the few reasons the plug-in manager still exists as part of CbB.