Error Message with iZotope RX 3 as WaveEditor in SONAR X3

Don't have RX to test, maybe it is a permissions issue. Is SONAR running as administrator?

It may be instructive to determine where the RX3 waves are written since "The currently selected session data folder cannot be used."

I suspect this will need iZotope support intervention. I have not used an iZotope product from the Tool menu but have used a variety of other products from several different vendors without a problem. Something to try is a session directory without spaces in the name.

Did you ever get a response from iZotope on this?  I'm having the exact same problem.  I've done a little digging though and now understand why it's happening (and why it isn't fatal).  When you use Sonar's tools menu to launch a WaveEditor it passes some arguments to the other app.  Here's what it's passing to RX 4 on my computer
 
"D:\Apps\iZotope\RX 4\win64\iZotope RX 4.exe" "C:\Users\matthews\AppData\Local\Temp\Tool copy 3 of Audio Event.wav" /REGION:0,1559383
 
That bit at the end is what is causing RX 4 to give the error.  It thinks "/REGION:0,1559383" is a filename and tries to make a session with that as the session folder.  Except you can't make a directory (or file) with a colon in the filename.  So that fails and RX4 reports the error.  But the real wav file works just fine and that's why it continues without an issue.
 
So there are really two bugs here.  Sonar shouldn't be passing that region argument to the WaveEditor.  Perhaps there is an option to control that?  The documentation on the Tools menu in Sonar is kind of weak.
 
And RX 4 really shouldn't treat that argument as a filename and try and make a session with it. 
 
I'm thinking the best answer may be a batch file/mini-exe that Sonar runs that strips off the region argument and then launches RX4.  The batch file will cause a window to flash though, so I might just do it with a tiny C program.

Ah, fantastic. That's been annoying me for ages.

Glad it helped.  RX4's full interface hooked to Sonar is actually very slick and works pretty well.  The connect and other methods work too, but the full deal easily launched from Sonar is not to be under estimated. 
 
Cakewalk really needs to put the complete documentation on the Tools menu somewhere public.  Maybe even add a tool to Sonar to let user's edit the tool menu.  Documentation that only exists in an obscure forum post is not really good support.

msorrels
Glad it helped.  RX4's full interface hooked to Sonar is actually very slick and works pretty well.  The connect and other methods work too, but the full deal easily launched from Sonar is not to be under estimated. 
 
Cakewalk really needs to put the complete documentation on the Tools menu somewhere public.  Maybe even add a tool to Sonar to let user's edit the tool menu.  Documentation that only exists in an obscure forum post is not really good support.

There's been a knowledge base article for a few years now.

https://www.cakewalk.com/...e-to-SONARs-Tools-menu

I never used a wave editor with Sonar (at least not in the last 10 years).
 
Is this basically like the ARA with Melodyne and V-vocal?
 
In other words, do you select a region, edit it, and then the region is updated?
 
If that is the case then why is there ARA?
 
Hope its not a stupid question.
 
 
 

msorrels
The KB article doesn't document ANY of the various Types supported by Sonar nor any of the other options (like this one necessary to turn off the sending of a region flag to WaveEditor entries).
 
 

I understand what you say and realise it needs an update. I just wanted to point out that the information was not only located in some obscure forum thread as had been stated. Cakewalk have documented this function in their Knowledge Base articles for many years, though having re read the linked thread again, clearly it's very abbreviated to provide just a basic function.
Sonar has provided this feature for as long as I remember. In much earlier versions of Sonar even in the ProAudio days, the function was provided in the Utilities menu.

You obviously are much more computer savvy than I am (explain it better than me) why not put in a feature request to update the current Knowledge base with the info that Noël provided in that thread. I think for the masses this kind of feature is not on most people's radar, though I agree it should be better documented in a more accessible place.

There has been discussion on the forum about creating and updating docs for use of advanced functions and techniques. This would qualify for sure. Provided by and for the user base as well as updated by us.

If you already have RX4 setup in the tools menu then just add info as per this instruction that was given in post #9 above.

msorrels
"So just add a DWORD RegionFlag 0 into your RX tools menu registry and no more error in RX4 on startup."

If you're not sure refer to the linked article on how to add a DWORD to the current registry entry you have for RX4.


Correction. Please substitute Utilities for Tools.

Sorry I thought you already had RX4 added to your Tools menu. It's the Tools menu at the very top of Sonars main screen. And no it isn't there until you manually add it.

You need to do a registry edit to add a program to a sonar's Tools menu. This enable you to select a track or audio selection for editing in an external program, in this case RX4.

if you're OK doing a registry edit then follow the step by step process outlined in the knowledge base article I linked to in post #14 and add the info from the last line I gave you in the previous post.

If that's beyond your skills let me know and I'll write it out for you. It's a good thing to learn. Make sure to do a registry backup as per the linked article.

You also educate yourself and read the whole thread linked to in post #9.

Correction. Please substitute Utilities for Tools.

mcdonalk
Excuse my ignorance, but should I already see RX4 in a "tools" menu, or do you mean the "utilities" menu? I am not aware of a "tools" menu, other than the panel in the control bar that is used to select the smart tool, etc.

 
You're correct, it's under the Utilities menu.

I believe that I have implemented the registry changes properly. RX4 is now an option in the "utilities" menu, and when I select an audio clip and select RX4 from the "utilities" menu, the audio clip opens in RX4. However, I now have the following problem:

a) When RX4 is invoked in the above manner, a warning is repeatedly displayed: "audio driver error: selected audio device cannot be opened. Please make sure it's not in use by another application ..." This happens whether or not "share drivers with other programs" is checked in the audio preferences.

b) If I attempt to play the clip from within RX4, the same warning occurs, and no sound is heard, although I can hear the Sonar audio track when it is played.

What should I try next?

I just use MME inside RX4 and let Sonar own the ASIO drivers.  It's not ideal but I don't really care much about latency in an audio editor.  But that combo might not work with every interface (I'm using a first-gen Focusrite Saffire).
 

Man, the answer was in a post from Noel from 2009! I didn't even realize those additional arguments existed.
 
I have been using Audition for a while now from the Utilities menu, and SONAR passes it the actual wav beneath the selected clip. Simple launch from Utilities, (destructive) edit, save, close; and SONAR recognizes the file has been altered and prompts to reload it. (The additional directory with RX3/4 referenced above is a bit confusing to me based on what I have seen Audition do. I do not have "temp audio" lying about from these edits.)