Unable to re-open X2 after closing program - Windows Issue?

It sounds like you may have a driver that wont let Sonar close. Check in the Windows Task Manager and see if after you close Sonar its still listed.

None of that should be there after you close Sonar. It is a driver hang I believe. 

Forgot to ask:

You indicate X2.  Is that X2a or just X2?

If just X2, then I recommend you install the X2a update, IF you are running Windows 7 SP1 at a minimum.

Bob Bone

Sorry - I did not see it in his specs in the sig.

The remaining questions remain. :)

Bob Bone

robert_e_bone


Forgot to ask:

You indicate X2.  Is that X2a or just X2?

If just X2, then I recommend you install the X2a update, IF you are running Windows 7 SP1 at a minimum.

Bob Bone

I'm running Sonar X2a and Win 7 x64 SP1.

I'm very good at keeping my versions current. I've been a Cakewalk user since Cakewalk Pro 3.01 for Windows 3.1.  I've actually been a user of this forum long before 2010 (there was a format change back then and my old posts were no longer recognized). 

When I say "Sonar X2" I mean the latest version that's out (unless X2b has been out for a while and I'm totally oblivious to it...) I'm just using "X2" since this forum also covers X1.

KenB123


Maybe this thread might offer some insight:
 
http://forum.cakewalk.com/tm.aspx?m=2312689 

Thing is, after I manually closed SONARPDR.EXE, I still cannot re-open Sonar without a re-start.

@elsongs 

hmmm.... not sure if you have jBridge. if you do you could try this....
locate the used 32Bit Vst(s) and from the instrument's window, there is a VST properties button. open that and check "Load using jBridge wrapper". turn on and off the instrument from the instrument panel and the instrument should be loaded using jBridge instead of BitBridge from now. don't do it all at once, do it one at a time. check for stability issues.

i recommend this as i had an offending 32Bit VST which would work solely on its own in BitBridge but when combined with another, it will work until closing time. at close, i seem to experience the same as what you described. using the method described above, i am able to open the offending 32Bit VST (jBridge) and many other VSTs (BitBridge / jBridge) without issues after that. closing and opening other projects are all fine. 

BTW, i am still on X1(d).

hope this helps you.

robert_e_bone


What sample rate and buffer size do you have specified for your audio interface?
What sample rate is set in Sonar?

Both are set at 44.1. 

I am still wondering if this is something common between projects - some 32-bit plugin perhaps.  You indicate this happens about 60% of the time when opening Sonar, but your earlier response did not indicate if that was for new projects, for the same project, or for a mixture.  Please clarify on that.

It happens for both new and existing projects. Since most of my pre-X1 projects are pretty much unopeneable (they all used 32-bit plugins & some DXIs, all my projects were started in X1 and X2. I have an old copy of Sonar 7 32-bit used to open my older projects.

Also, your earlier responses did not indicate whether or not you can enter and exit Sonar properly without having a project open - please try that a few times and include the results of that. 

Most of the time I cannot exit Sonar properly. Last time I worked on a project (an existing project and started a new one), I was able to exit properly. It's not a consistent problem.

And, please try to open one of the projects that exhibits this behavior in safe mode, and do NOT let it load plugins, then exit, and post back with those results. 

I suspect either a sample rate mismatch or one or more 32-bit plugins causing these problems - from what I understand so far, or possibly an issue with the audio interface driver (although I do not see that one as likely).

Bob Bone

I'm quite sure it has to do with 32-bit plugin compatibility, even though most of the plugins I use are already 64-bit. If I had a sample rate mismatch, it would have been plainly obvious to me (sound glitches, etc).

elsongs

robert_e_bone


What sample rate and buffer size do you have specified for your audio interface?
What sample rate is set in Sonar?

Both are set at 44.1. 

I am still wondering if this is something common between projects - some 32-bit plugin perhaps.  You indicate this happens about 60% of the time when opening Sonar, but your earlier response did not indicate if that was for new projects, for the same project, or for a mixture.  Please clarify on that.

It happens for both new and existing projects. Since most of my pre-X1 projects are pretty much unopeneable (they all used 32-bit plugins & some DXIs, all my projects were started in X1 and X2. I have an old copy of Sonar 7 32-bit used to open my older projects.

Also, your earlier responses did not indicate whether or not you can enter and exit Sonar properly without having a project open - please try that a few times and include the results of that. 

Most of the time I cannot exit Sonar properly. Last time I worked on a project (an existing project and started a new one), I was able to exit properly. It's not a consistent problem.

And, please try to open one of the projects that exhibits this behavior in safe mode, and do NOT let it load plugins, then exit, and post back with those results. 

I suspect either a sample rate mismatch or one or more 32-bit plugins causing these problems - from what I understand so far, or possibly an issue with the audio interface driver (although I do not see that one as likely).

Bob Bone

I'm quite sure it has to do with 32-bit plugin compatibility, even though most of the plugins I use are already 64-bit. If I had a sample rate mismatch, it would have been plainly obvious to me (sound glitches, etc).

Well, none of us really have a clue as to how your projects are constructed, and sample rate mismatch seems to produce different random nuttiness, depending on some set of factors that does not seem to be consistent, so I thought I would ask.
Good luck, I'm out.


Bob Bone

Just saw your post, sometimes I have restart issues with X2a in Win 7 sp1 (64 bit) but usually only when Sonar crashes, it won't restart again.  I then go to task manager and click "end process" and shut down Sonar.exe from there. But then I have to wait for a few minutes until sonar actually stops.  I don't usually bother rebooting, it seems to restart fine.  Mostly the cause of the crash is a plugin.

But in your case, you should look at your audio drivers, and I'm not sure if you're using ASIO or other drivers, but for me ASIO seems to be the most stable, with my audio card.

The other thing which could cause instability issues is Video card drivers, they can be notorious especially if you're using dual monitors, sometimes things get screwy with that.  I found that xray view caused instability issues on my system so I turned it off in Sonar and never had problems with video drivers after that.

In terms of Jbridge I'd avoid it like the plague if it was me, I tried it and had nothing but problems, big crashes all the time. Went back to using bitbridge and those issues stopped. but to be honest I don't use many 32 bit plugins in Sonar 64x, I just find that some 32 bit plugins can cause stability problems in Sonar 64x.

And yes you'll find with bitbridge you can't use all your 32 bit plugins in Sonar 64 bit, they won't appear in plugin manager. 

I ended up biting the bullet and condensed my plugins down to the essential ones I use and got 64 bit versions and haven't looked back. 

jBridge is an optional, paid installer to run VSTs both ways. jBridge will allow 32Bit VST (older VSTs) to run in a 64Bit application (Sonar x64) and 64BitVST to run in a 32Bit application (Sonar x32). jBridge also has several more options to allow for stability issues by way of check boxes.  


do find the link to jBridge here. 

http://jstuff.wordpress.com/jbridge/

they have a demo version which you may download to see if helps.

Thanks for clearing it up for me. Hmmm. I'm a little hesitant to plunk my money down on something that's likely gonna be obsolete in the near future anyway. Who here remembers the DirectiXer plug-in wrapper? Eventually Cakewalk made their own wrapper, and then supported VSTs natively altogether, so the DirectiXer eventually became useless. I kinda have faith that future updates of Sonar X-- will address this, coupled with the fact that 32bit plugins will one day be totally obsolete.