Hi Folks,
 
I've got RX 3 set up in my registry as a WaveEditor for SONAR. It works fine, except for an error message that I get every time I select it from the Utilities menu:
 
"The currently selected session data folder cannot be used. Open preferences, and choose a new session data folder."
 
Oddly, the warning seems to mean nothing as, if I click "OK", it loads the clip in RX, allows me to edit it, and sends it back to Sonar when I'm done. No issues.
 
What's also odd is that it doesn't seem to matter what folder I have defined for this purpose in RX. I keep it set to a folder on my audio drive to keep C: clean, but I get the message even when I revert back to the default folder on the C: drive.
 
So, it doesn't actually prevent it from working. The error message is just annoying to click through every time I want to send something to RX. Has anyone else encountered this and found a fix? Any insight will be greatly appreciated.
 
Thanks,
Ben
 

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

Good thought, but unfortunately that's not it. Typically, I don't run Sonar as an admin, because doing so prevents me from being able to drag .wav files in to it, but I tested it as an admin to see if that would do the trick and... no go. Same error message. Thanks, though, scook!

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

They're written to the "currently selected session data folder" the message says can't be used, which, the way I have it configured, is D:\RX Data. That's part of the reason it's frustrating; there doesn't actually appear to be any issue with using that folder - or any other folder, but, regardless of which one I have it set to, I get the message.

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.

Thanks for the tip, scook. I tried D:\RX_Data instead, but that didn't resolve the issue. Perhaps, you're right, I'll have to contact iZotope. Anyway, thanks for the suggestions.

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.

Turns out there is a easy solution.  Sonar supports a RegionFlag setting in the Tools menu.  Didn't show up on Google searches till I knew what I was looking for but there is this post that better documents the Tools menu:
 
http://forum.cakewalk.com/FindPost/1850413
 
So just add a DWORD RegionFlag 0 into your RX tools menu registry and no more error in RX4 on startup.
 
 

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