dmbaer
Danny,
I tried to duplicate your issue but faced a set of challenges. I reinstalled ARC 1 (latest version freshly downloaded) making sure I installed both 32 and 64-bit versions. I got two dll-s placed in the expected locations. The install seemed to do what I instructed.
At first, when I ran Sonar, ARC showed up in the menus as "ARC (32 bit)". Indeed, when I inserted it into the master effects bin, my task manager showed a new application (Arc) that started up. It almost certainly it was getting the 32-bit version being executed. But all my other IK 64-bit plug-ins showed up correctly.
So I tried to re-order the VST scan folder list so that the 64-bit VST folders came first. It appears that cannot be done. Next attempt was to rename ARC.dll under Program Files (x86) to be ARC-32bit.dll. Now, after a VST reset, VST rescan and machine reboot (that appeared to be required to get this all to work), I finally am seeing ARC without the "(32 bit)" qualifier in the Sonar menus. Also, the task manager does not show a separate application when I insert in into a project. Finally!!!
So, at last I have something that should duplicate your setup. And Sonar does not crash when I open a project with ARC 1 in it. Thank goodness for small favors.
But this makes me question the judgement of the CW developers. If you're running 64-bit Sonar, would it not make sense to scan 64-bit VSTs first? Or, why not allow the user to specify the order of the directories in the scan list? As is, it seems one cannot have both a 32 and 64 bit version of the same VST installed, or you're always going to get the 32-bit version recognized. There may be a very good reason you'd like both on hand, but you'd rarely want the 32-bit version used when running it in Sonar.
Very puzzling.
Hi David,
Thanks for the reply...and Merry Christmas by the way. :) A few things might have confused you in my last post, so I'd like to clarify a bit. I have two ARC issues. You won't be able to duplicate my issue unless you run the versions I speak of with the correct versions of Sonar.
Issue 1: ARC 1 not keeping corrections relies on any version after 1.1.1 to present using any version of Sonar per my post above. Version 1.1.1 works perfectly in all versions of Sonar until X2.
Issue 2: Crashing only occurs in Sonar X2 or X2a with ARC 1, version 1.1.1.
As for the VST thing you mention, you should never see ARC exe running in task manager. Somehow, the ARC exe for the correction procedure was included in your VST scan is what I believe happened there.
As for the other VST issue between 32 and 64, this happens when we include our 32 bit plugs in our 64 bit scan due to some of our plugs being needed in bridge mode. So if you have 32 bit plugs of the same product that are being scanned along with your plugs in the 32 bit folders that may NOT be 64, Sonar is going to wonder what the deal is as it will see both dll's.
The fix for this is to not include any 32 bit plugs that you have 64's for, in your 64 bit plug scan. This way Sonar will always open 64's when you run it. How it knows to differentiate between stock Sonar plugs and 64 Sonar plugs is a bit mind boggling, however, I have seen a few 32 bit Sonar plugs in a 64 project. This usually happens to me when the project I brought into Sonar 64, was created using Sonar 32. It's hit or miss though really. Most times the 64's all load up, but I so see 32's showing up from time to time.
I want to totally go 64 bit, but some of my 32 bit plugs haven't been revised to 64 bit...and as I said before, I have a few Dx plugs that I still use. So for me, I'll always need some of my 32 bit plugs to be bridged. What I have started to do though (which has helped leaps and bounds) is to remove all 32 bit plugs that have 64 bit versions from my VST scan folders in Sonar 64. This way if 32's show up, they will be there because they are supposed to be bridged....not by accident.
One thing I've always done is keep all my VST plugs in one folder for 32, one for 64. When you install dual versions 32/64 of the same plug and include the 32's in your 64 plug scan, you're bound to see issues. So anything that I have in 32 bit that is also 64, I remove out of my 32 bit folder and into another so it is not included in the 64 bit plug scan yet all my other 32's that are not 64 that can be bridged, will still appear.
Hope this clarifies a few things. :)
-Danny