[SOLVED] Apparent X3 Upgrade to Platinum JP Fail on Win10?

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.

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..

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.

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.

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

Found that my Win 10 upgrade defaulted me back to hiding some folders and file types. Deleted aud.ini but no help. Updated display, monitor, audio interface drivers. Still no fix. Will report back here once I go through tech support.
 
Thanks for the help...good folks here.
 

hey Dok.....no, when aud.ini is removed there is no need for me to set up audio device again. The device and all i/o seem to be picked up automatically when Sonar is brought up after a reboot. Otherwise, if I attempt to load an existing project which hangs Sonar and then exit out, if I restart Sonar without rebooting all audio device settings and i/o will be blank with Sonar warning there is no audio device.
 
Will look for/delete asio4all......thanks!!

nothing special happens when i delete aud.ini and restart Sonar. Absolutely no change in start-up behavior or otherwise. Sonar acts AOK and completely normal until I load an existing project which freezes it up ("Sonar is not responding"). Is there a way to load a project without activating the associated plugins? I've found that some existing 'minimal' projects will load and play in Sonar Platinum just fine, but most will freeze Sonar such that I can't tell what plugins are being used in these projects.

Phone support should be open in about 40 minutes. Type up a ticket (if you haven't already) and give 'em a call.
 
Seriously you won't regret it. Also ask them to send you an email with details on the solutions they figured out so you can reference them (and they may come up with more stuff after you hang up).
 
They're really good at this crap and decent conversationalists too (unlike most tech/customer support drones... well and these dudes ain't drones).
 
Cheers.
 
Edit: I seriously think you're just gonna be chasing your tail here on the forum with this particular problem. Might as well just get it from the horse's mouth and get on with creating.

Dupe

The current 64bit version of M-Tron Pro works OK for me in the current SONAR on Win10. Are you using the 64bit version of the plug-in?

I am running 2.1.0.0 modified 18 Jan 2013
If you are running a 32bit version, SONAR will tell you by adding (32-bit) to the plug-in name in all the plug-in lists. Also the plug-in is shown in green in the browser. By default, 32bit plug-ins loaded by BitBridge do not display the standard VST header.