• SONAR
  • Tools menu - After New Install I can't get any Audio Editor to work
2016/11/04 12:36:52
Bassman002
HI:)
 
Before the new Install I've had GoldWave and Audacity in the Tools Menu and they worked! 
 
Now that I have manually typ3ed them in in the Registry, they appear in the tools menu but:
 
GoldWave does not get the audiofile, normally it is written to C:\Users\(MyName)\AppData\Local\Temp
but there is no file when I open the Editor....
 
I've tried with Cakewalk External Encoder Configuration Utility, but then there is no entry in the tools menu
Sonar Utils doesn't work anymore in Win 10/64
Audacity gives an error after trying to open it with a wavefile in Sonar, not an error, but a help window opens with command line parameters and nothing more..
 
So what is going wrong???
 
Entries in the RegEdit:
Key GoldWave
Strings
ExePath, MenuText, Type
 
The same with audacity
 
OK, I have to sleep over it, maybe that helps:)
 
Thanks,
Bassman.
 
2016/11/04 13:02:06
scook
When editors do not get the clip it is usually because the Type field in the registry is wrong. The type should be WaveEditor all one word, no spaces.
 
I wrote a utility called SONARToolsEditor to help get the entries correct. It is on this page, the direct download link is https://app.box.com/s/urr6cb9bq343vp8r6uin2yta2tr8cqyo
 
The external encoder utility is for adding command line audio encoders not tools like wave editors. SONARToolsEditor is designed for adding wave editors and other programs to the SONAR Utility menu
2016/11/04 13:18:56
Bassman002
@scook
WaveEditor is the entry in the registry!
 
Just finished working....I'll give your Editor a try tomorrow morning
 
thank you very much:)
 
Bassman.
 
2016/11/05 14:42:00
THambrecht
Thats the working entry for WaveLab -  maybe that helps:
  
[HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Tools Menu\WaveLab]
"ExePath"="C:\\Program Files (x86)\\Steinberg\\WaveLab 6\\WaveLab.exe"
"MenuText"="&WaveLab"
"StatusBarText"="Edit with WaveLab"
"Type"="WaveEditor"
2016/11/08 07:00:19
Bassman002
Hi:)
 
GoldWave works, audacity not, same entries....doesn't matter GoldWave is OK for the moment!
 
Thanks!
2016/11/08 09:51:08
msorrels
To get external wave editors to work correctly with the command line arguments you may need to add another key:

RegionFlag REG_DWORD 0
 
This stops Sonar from passing in the selection information on the command line with the filename. 
 
By default Sonar passes the selection info in a format mainly Sound Forge supports, unless you add the RegionFlag. It's the secret to getting iZotope RX to work without an error/warning as well as a number of other wave editors.  There are a bunch of threads on this. 
 
For some wave editors the only bad result is an error message but the editing seems to work (the editor gives an error for the extra selection but still loads the file) but some editors the command line error is fatal.
2016/11/09 00:59:17
Bassman002
@msorrels
 
Nice:) That works for Audacity!
 
Thank you!
Bassman.
 
2016/11/09 08:15:02
msorrels
I should point out scook's excellent menu editor supports setting this flag as well.  The option is at the bottom "Region Flag".  You need to set it to "No" rather than "Do Not Set" since SONAR defaults this to yes.  Some wave editors may support this method of selecting a region of the wave file though, the only one I know for sure is Sound Forge.
 
Here is an example of my config for iZotope RX 4:

2016/11/09 11:38:44
dlion16
help! i tried using this to add sound forge, and now sonar won't start. hangs on the splash screen. suggestions?
2016/11/09 11:41:06
dlion16
sorry, got ccleaner to fix registry.
 
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account