Two Pesky Problems: Melodyne & Roland Octa-Capture

1. Yesterday I started having a problem which I believe is related to Melodyne Editor...I can't access any project files which use Melodyne unless I start them in safe mode and disable the Melodyne module. If I don't do this, Sonar shows me a message stating that the Melodyne module (Melodyne.vst3) has failed, and Sonar then crashes.
 
I spent quite a while on the phone with tech support today. The technician suggested I uninstall all of my C++ files, then download new  C++ files and reinstall. I did that, but the problem remains. Then (of my own accord since it was after hours for tech support) I uninstalled Sonar X3 completely, and reinstalled Sonar X3, then updated to X3d. Still no progress. I have the latest update from Melodyne.
 
2. My Roland Octa-Capture audio interface is intermittently not being recognized by Sonar (both before and after the Sonar reinstall). I uninstalled the OC driver, then reinstalled it. Still no good. I've tried unplugging it and plugging it back in, turning it on and off, etc...mostly no good, although sometimes Sonar does see the device. The unit tells me it's online, but usually Sonar can't see it. Most of the time Windows sees it, as evidenced by the sound one hears when plugging in or turning on a USB device, but Sonar can't see it. Occasionally Sonar does recognize it and tells me it wants to add the device,  but after I agree, Sonar generally still doesn't see the OC. I check in the Preferences/Audio Devices, but no devices are shown.
 
For some reason today the Windows Media Player, which I have always had set to use the computer's onboard speakers, started using my Yamaha studio monitors. This means it was accessing the OC, and I thought maybe the WMP and Sonar were fighting over the OC driver. So I switched the WMP back to its original setting (using the onboard speakers), but Sonar still can't see the OC.
 
I don't know if these problems are related. Also, I use Adobe CS6, and yesterday I applied updates to several programs in that suite. Maybe something in those updates screwed with Sonar? Who knows?
 
I'm using Win7 (64 bit) Home Premium SP1 on an Acer 7551-7422, QuadCore, 2.20 GHz, 6GB of RAM.
 
Thanks for any help you can offer.

You say these problems started yesterday... It might be worth rolling back your system with System Restore to two days ago -- or whatever the earliest available time there is to restore.
 
Of course, if you do this, the downside is you will lose all of the updates and changes you made since yesterday.   If it works though, you'll at least be better off, and can experiment with System Restore to figure out what changes caused the problems.  (I suspect this started with the Adobe updates.  Ideally, there will be a restore point just before those you can go back to). 
 
In theory, you can undo any system restore, so if it doesn't work, you can return to the present state (such as it is).

I am having a similar problem with a Roland Studio Capture and X3d - Sonar simply doesn't "see" the Studio Capture. Have tried same remedies, usually rebooting the Studio capture does the trick but oh the tedium.

@Robert:
 
I followed your suggestion, but Sonar still finds the Octa-Capture only intermittently. And I'm actually not sure that wasn't the way I had the sound settings all along.
 
Thanks for your suggestion.

@Bristol:
 
I did not manually change/delete any registry keys when I uninstalled Sonar. I think this will be my next step. I plan to uninstall X3, delete the keys, and reinstall. However, this time I will update only to X3c, and see if things are OK. Then I will apply the X3d patch and see if that introduces any problems.
 
Thank you.

I had the same problem with Sonar not seeing my Studio Capture driver.
It started when I forgot to turn on the unit before I opened Sonar.
Somehow the driver got corrupted. When I re-installed the Studio Capture driver, the problem went away.
 
 

I believe the Melodyne problem is now solved, thanks to Cakewalk Tech Support.
 
The theory is that Melodyne had become corrupted, which I apparently fixed by reinstalling the program. The technician had me start a new project and use Melodyne, which worked correctly, so this seems plausible. However, my existing projects were still referencing the corrupted .dll file.
 
So we opened an existing project in safe mode, disabling the Melodyne module, and then did a manual scan of my VST folders. This ended the reference to the corrupted module, and Melodyne then functioned correctly within the existing project.
 
My previously existing Melodyne changes are all gone (at least in the one project I've checked), so I will have to recreate those...a hassle, but much preferable to the alternative.
 
As for the Octa-Capture,it started working properly about 45 minutes before I got on the phone with Cakewalk. Go figure.
 
Thanks to everyone who volunteered suggestions. Much appreciated.