In this instance a 32bit sequencer will work in a 64bit OS but then all the plugin's you
install will need to be the 32bit versions as you can't run a 64bit plug in inside a 32bit
sequencer.
If you had a 64bit specfic plug in then by bridging it you would be
able to run a 64bit plug in, inside of your 32bit host.
This also applies in
reverse, so if you have a plug in you really have to be able to use but only has a 32bit
version available, and your running a 64bit sequencer for (example) memory requirement
reasons then it'll let you use those older plug in's.
Additional bonus - if
your using jBridge (not sure on other bitbrige solutions, never had to do it, sure someone
here knows) it'll run the plug in, inside it's own memory allocation, taken from the
unused memory pool outside of the sequencer allocation. So if you have a 32bit sequencer
and you've choose to bridge your large libary playback tools using it (VSL/EW/Kontakt)
giving you access to far larger banks without having to migrate up and risk loosing some
of your older plug's.
The's a more indepth article to be found @
http://www.soundonsound.com/sos/nov10/articles/64-bit.htm by some odd
chap who appears to know his beans.
--------------------
ScanProAudio & 3XS Audio Systems
ScanProAudio Blog