Hey folks,
Got a pretty bad situation here that has me stopped dead on the tracks. Not sure where else to turn, and the sequence of events has me puzzled....
 
1. Sonar X3 Producer on Win 8.1 was working just fine.
2. Upgraded to Win 10 Home was successful. No issues. Checked audio i/f for new Win10 drivers...all good!
3. Ran X3 on Win 10 for a few days. Loaded/played existing X3 projects as always. No issues.
4. Upgraded X3 to Platinum Jamaica Plain via the command center. Reboot.
5. Platinum JP started. Automatically detects audio device (Roland Studio Capture) and assigns in/outputs.
6. Can create a new Sonar project no problem, but....
7. Will not load any existing X3 project. When attempting to load, no error message....just stays in 'input inhibited' mode forever.
8. Only way out is to X out of the Sonar main window.
9. Once out of Sonar and then restarting it, it will not recognize the audio device. No way to recognize it unless the system is rebooted.
10. And the kicker.....X3 now behaves exactly the same way -- cannot load existing projects, and failure to recognize the audio interface once an existing project attempts to load.
 
Would really appreciate any ideas from the collective Sonar thinktank.

I would try removing and reinstalling the audio interface drivers.

First try...

Update your audio interface firmware and drivers. Might as well do the display driver whilst you are at it (what is it? I can't see signatures here BTW).

Secondly delete AUD.INI (google for details),. You may need to do it for each Sonar version.

Cheers..

scook/Dok....went thru the complete uninstall and reinstall of audio i/f drivers (Roland Studio Capture) last night, but no help there. Dok, I'll try to kill aud.ini tonight to see if that helps. Display driver is for HP Envy 32. I'll check that out too. Never would think display driver could do what's happening but will try anything.
 
Thanks!!

Honestly after reading your OP, this seems worthy of a call to tech support. Type up all the details you've posted here, all your system specs and anything else you can think of and send it through the email tech support portal on the Cake site. This should generate a support ticket number. Call them tomorrow during support hours and reference that ticket so whomever answers the phone can pull it up on their screen. If you are in the US the call is toll free.
 
This really does not sound like the type of issue I'd guess on/poke at all willy nilly. You seem to have done everything right and this issue sounds way beyond garden variety. You paid for support and this is the type of thing it's there for. You may even be helping the Baker's/community if this is some weird bug/conflict hidden inside JP.
 
Good luck.

So you are running the latest Roland drivers and system update?

The updated display driver probably won't do anything with your issue, but with windows 10 updating it is generally a must, just make sure you do a minimal install. Ta.

Beepster....appreciate the advice and believe i'll need to go that route. Interestingly, I did go down in the studio not long ago thinking getting rid of aud.ini would be easy enough. But the system believes there is no such file present. After investigating, there isn't even a directory folder where aud.ini is supposed to be located.

Just do a search for aud.ini on the C drive in windows explorer. Deleting this has resolved a lot of odd audio issues with win10 upgrades.

And see previous post..

Search might not find it - it didn't on my laptop.
 
Try looking here:
 
C:\Users\Your Name\AppData\Roaming\Cakewalk\SONAR Platinum

Well you may need to unhide system files first.