Thanks for posting that procedure. I was able to use it in SONAR 8.5.1  (x64) to add Sound Forge 10 to my tools menu. (SF 10 is not native x64 go figure so it doesn't show up in SONAR's Tools menu)

On testing it works perfect. I can now select a portion of an audio wave in SONAR select Menu/Tools/SoundForge10 and the highlighted portion of the file loads into SF10 just as it works in SONAR x86.

SONAR UTILS doesn't work with the 64 bit version of SONAR if you have both 32 and 64 bit versions installed (Which I have)

that tip should be a sticky somewhere for SONAR x64 users as well.

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
 

Thanks Noel,
I've copied it for future reference but don't understand a lot of the additional info you provided.
Anyway its good to have a method to make it work seeing as SONAR x64 can't seem to do it automatically.

We used to use SONAR Utils but it stopped at version 3.? and doesn't support 64bit.

dantarbill

bitflipper


Yeh, that's not much of a clue. "Cannot create process" is about as vague as can be. I was hoping for a more helpful error message.

In your registry key, do you have the full pathname of the RX executable? Verify that it's correct: copy it directly out of the registry and paste it into the Run window and make sure the application starts.

If that works, next try appending the path of an audio file and try executing that from the Run window.

I've done all that.  RX with a filename on the command line opens the file the way you would expect.   Note though that when you start WaveLab from the command line with a filename as a parameter, it doesn't open with the wav file open.  This suggests that there is part of the mechanism that I'm still missing.

It turns out that the problem I had with the WaveLab test was that it wanted the full path for the wav file.  So...both WaveLab and RX should act like WaveEditors and they both take a file on the command line.  Noel's documentation would indicate that ALL the secret sauce is in the registry.  Furthermore, a suitably modified copy of the WaveLab reg entry in...
 
HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Tools Menu
 
...should work just fine.  Yet, there is still the nebulous and unhelpful error.
 
Ahh...I FOUND it!
 
RX seems to need to have CurrentDirectory specified in the registry for it to find all the resources it needs.  It works now!  Thanks everybody (Noel in particular).

Thanks for that, Noel. That's the first time I've seen the Modal flag mentioned. I assume that was added to address a specific problem. Are there utilities that are known to require modal operation?

Oops, sorry, I wasn't supposed to ask any questions.

IIRC it was to solve the converse problem. When I did plugin manager integration I needed it to be non modal and added a bunch of new items to the tool options like the parent window etc.
Some of the tools menu settings have been around a *long* time - since the pro audio days or earlier, and dates back before my time at Cakewalk.

Dan, Its cool that it works now. Some tools require the current directory to be set.
You might want to post your reg settings for other users of RX. Also you could let Izotope know in case they want to self register this when RX installs. Sound Forge used to do this years ago.

Ummm... you do realize that iZotope RX runs as both standalone and plug-in, right? You don't need to use it via the Tools menu if you use the plug-ins.

Best,
Scott

--
Scott R. Garrigus - Author of the Cakewalk Sonar and Sony Sound Forge Power book series. Get Sonar 8 Power - Today! Go to: http://www.garrigus.com/  - http://www.musictechshop.com/ - http://www.cooltechshop.com/

Publisher of DigiFreq - free music technology newsletter. Win a free SoundTech Vocal Trainer Package, go to: http://www.digifreq.com/digifreq/

Publisher of NewTechReview - free consumer technology newsletter. Win a free i2i Stream Wireless Music Pack, go to: http://www.newtechreview.com/newtechreview/

garrigus


Ummm... you do realize that iZotope RX runs as both standalone and plug-in, right? You don't need to use it via the Tools menu if you use the plug-ins.

Best,
Scott

Yes...

...and no.

I realize that the RX tools can be used as VST plugins.  But...the most useful tools (like Spectral Repair and Denoiser) are a lot easier to use if you can see the context in RX itself.  With the Denoiser, it's a lot easier to see candidate "noise only" regions with the spectral display.  With Spectral Repair, the tool needs to see a whole region at once instead of just applying some sort of transform to an audio data stream.  When you instantiate Spectral Repair as a VST plug, it gives you this long list of instructions that is frankly unnecessary if you can just open RX with a tool copy of the region of interest.

Ah ha... okay, I see what you mean.

Best,
Scott

--
Scott R. Garrigus - Author of the Cakewalk Sonar and Sony Sound Forge Power book series. Get Sonar 8 Power - Today! Go to: http://www.garrigus.com/  - http://www.musictechshop.com/ - http://www.cooltechshop.com/

Publisher of DigiFreq - free music technology newsletter. Win a free SoundTech Vocal Trainer Package, go to: http://www.digifreq.com/digifreq/

Publisher of NewTechReview - free consumer technology newsletter. Win a free i2i Stream Wireless Music Pack, go to: http://www.newtechreview.com/newtechreview/