Hi
 
I have Sonar X3 on an Windows 7 64Bit System.
 
I have an Alesis QX25 and an M-Audio Oxygen 61. Both have Controller functions, like knobs, fader and Transport-Keys.
 
But i can't assign them. The Keyboard itself runs, and via MIDI-Learn i can assign VST-Instruments. That is all OK. The Keyboards are conected via USB.
 
Now i had Sonar run in 32Bit mode, and there it is no problem to assign that controller Keys. But back in 64Bit Sonar, its gone, and can't be choose like i do in 32Bit mode.
I Run the programm "as administrator", but don't help.
 
When i use the 32Bit Version some instruments dont appear, and the VSTs by IK Multimedia are "not installed" the programm says (by the way: the program lies). So i must use the 64Bit Version :(
 
Maybe someone can help, what to do, that the Keyboards run in 64Bit Mode.
Specially the Alesis QX25 has no drivers. So it can not be an driver-problem (like I say: in 32Bit mode everything is fine - OK, just the thing, that i cant asign the "record" button - the "midi learn" question doesn't pop up, when i click on it, but that is another question).
 
Thank you for help
Andreas, germany

Hi Andreas -
 
Wie geht's? I'm running X3 64 in Win 7 and connect an Akai Pro MPK 88 to Sonar 64 bit via ACT. It (usually) works well. Did you set up an ACT device? One thing that happens to me from time to time is that the ACT ports are "forgotten" by Sonar. I have to set them up again. Usually this fixes things for me. To check this click on ACT Midi Controller in the Command Bar and in the pop-up ensure the in and out ports are set correctly.
 
Here are a couple of links that might help:
http://forum.cakewalk.com/Anyone-used-Sonar-ACT-on-the-Oxygen-88-Doesnt-work-for-me-m2715198.aspx
http://forum.cakewalk.com/Help-setting-up-MAudio-Oxygen-88-with-Sonar-X2-m2765296.aspx
 
You also mention some VSTs are missing in 32 bit Sonar. When you are running in 32-bit mode, if your VSTs are 64-bit they won't load in Sonar. Also, I think the VST scan settings are separate for the 32-bit and 64-bit versions. Compare your VST scan folders in 64 and 32 bit and make sure they are the same. Try rescanning in the 32-bit version. Sometimes when you install a VST you must install the 32-bit and 64-bit versions separately (run the VST install again and choose 32 bit).
 
If you really must run 32-bit Sonar and you have 64-bit VSTs, I've had success with jBridge (http://jstuff.wordpress.com/jbridge/). jBridge allows you to load 64 bit VSTs in a 32 bit host. It can also sometimes work better than BitBridge at loading 32 bit VSTs in 64 bit hosts.
 
Hope you get it sorted out,
 
- Dave
BTW, by German is not very good. Ich habe ganz alles vergessen. :-)

Hi
 
As I Say: In 32Bit Mode i can assign the Oxygen and Alesis to the DAW-Functions and they are saved for the next session. If I try it in 64Bit Sonar (as Admin) the would even forgotten, if i close the Preference-Window (or when I click on OK).
 
I have all VST-Instruments in one Big Folder on an faster harddisk. But most of the installations has VST32 and VST64 DLLs, that i install in their Own 32 an 64 Folders.
 
But the IK Multimedia VSTs won't be loaded, after I have choose them once in 64Bit. Maybe they would be change in 64Bit and can't load again in 32Bit??
If I started them as "Stand alone", they work great..
 
You can Find an Video, how i try to assign the Oxygen when you look in Youtube after this title:
Try to choose my oxygen 61 in Sonar X3 as an controller 
And i do the same steps in 32Bit, and they work!

That is really strange. I ran both 32 and 64 bit X2 and didn't see any of the issues you are having, either with ACT or with VSTs. I'm only running X3 64 bit now, so maybe a change in X3 is part of the issue?
 
Have you been able to get any help on the M Audio forums?

No, but the problem isn't the M-Audio Keyboard, because it dosn't work with the Alesis Keyboard too.
So, when you say, you run the X2 and have no Problem, it may be an problem with the X3. But am I the only one in the world who runs the X3 with Controller Keyboard in 64Bit?? Can't belive it ..
Maybe there is one little thing i didn't recognize :D
 
 

I only have the 64 bit X3 on my system and it works without issues with my Oxygen keyboard (although all of my settings were lost when I installed the upgrade).  Not a 64 bit problem, but possibly a problem with dual (32 and 64 bit) installs?
 
 

It is the Steam-Edition and both Editions where installed.. First i start the 64Bit Edition. But its Helpfull, that it works at you.
I don't think, that you so something "specially", that it works..? Maybe i do an clean new install...

I have Sonar off of Steam. I am running W7-Ultimate 64. I am experiencing the same issue with 64 bit Sonar ACT as the OP describes. I am using Akai Max25 and Akai MPD26. 32 bit seems to work as intended, with no issues; but I would like to work in 64 bit.

If you two users who bought SONAR from Steam are both experiencing this ACT problem, you should report this to Cakewalk. It is apparently a problem with the Steam versions.
 
Concerning the VST issue, 32bit and 64bit VST and VSTi should be installed to separate 32bit and 64bit folders. Then, a user should open each version of SONAR and using the Cakewalk Plug In Manager Utility or the Unified Preferences View (UPV), add the path of those two folders in the VST Scan Folders section. That would be under File>VST Settings in the Unified Preferences View. Under the VST Scan Options section, initially, select Re-scan Existing Plug Ins, and do the scan.
 
After that the plug ins you scanned should be visible in both versions of SONAR. Note that some 3rd party plug ins may only have a 32bit version or only have a 64bit version. In that case, the plug in wont show in both versions of SONAR, unless it is a 32bit version and you have added the path to the 32bit version plug ins to the VST Scan Folders section (under File>VST Settings UPV) in SONAR x64. And in that case, the 32bit plug in will be run with BitBridge (or you can choose jBridge to run 32bit plug ins, if you have jBridge) in SONAR x64, .
 
If you do the above, you should see all your installed plug ins.

Thank you thomasabarnes, I have done as you suggested re submission of problem report to cakewalk