Sure, try to explain it in more detail:
The problem with many operating systems is that you can't easily mix 32 bit and 64 bit code in the same process. As vst plugins are essentially dynamically loadable code fragments that will be executed in the context of the host process space it's normally not possible to host 64 bit plugins in 32 hosts and vice versa. Additionally each process has only a limited amount of memory
available, this "virtual address room" is 4 GB for 32 bit processes. For Windows those are further split, so your normal user application has only 2-3 GB at it's disposal. As host and plugin run in the same process they also share the same virtual address room, so if the host takes > 1 GB alone there are "only" 1-2 GB left for the plugin. (Due to various technical reasons often even less.)
jBridge tries to circumvent that by using a trick: It consists of two parts: a 32 or 64 bit vst plugin code that runs in the process context of your native 32/64 bit host and a separate 32 or 64 bit hosting process that can host a vst plugin itself. What jBridge does now is to forward data sent to the vst plugin to it's own hosting process and to send audio/midi output data from the vst inside this hosting process back to the plugin output running in the native host via shared memory. So you can run a 64 bit plugin together with a 32 bit host or use legacy 32 plugins in a 64 bit host. Additionally the plugin (now running in it's own process) has the full 2-3 GB user space memory at it's disposal (when it's a 32 bit plugin) or all remaining memory+swap space you might have in your system (for 64 bit plugins).
So in order to make this work you have two constraints:
1) the jBridge vst plugin is compatible with your host
2) the plugin you want to host inside jBridge has to be compatible to jBridge
Unfortunately the first point is not fulfilled with the EigenD 1.4.8 audio unit and jBridge 1.3.
That's where Bidule comes into play.
Bidule is (among other things) a vst/au host that is available as a stand alone version and a "sub host" version that can be run as vst/au plugin itself.
So each preset of the Bidule subhost can be a more or less complex setup of interconnected vst/au plugins, "building blocks" control logic (think "Max lite") etc.
As jBridge is not compatible with the EigenD audio unit but Bidule is, the following constellation is possible:
* Bidule is hosted in the EigenD audio unit (is compatible)
* jBridge is hosted in Bidule (is compatible)
* the 64 bit plugin is finally hosted in jBridge (is compatible for Kontakt 64 bit and Omnisphere 64 bit)
=> works
Regarding what is stored in the EigenD setup:
As with each plugin the current settings of the 64 bit plugin are stored as part of the vst chunk data by the subhost 1 (jBridge) which's settings are stored in the vst chunk data of subhost 2 (Bidule) which is forwarded to the native host (EigenD) when this requests all chunks for saving all vst parameters in the current "song" (in the case of EigenD: setup). (That's the way VST works so you usually find plugins in the state they were when reopening a saved project in a sequencer). So to cut a lengthy explanation short: All relevant data of Bidule, jBridge and the 64 bit plugin should be saved in the EigenD setup :)
Now all you have to do is to
* install jBridge
* install the plugin you finally want to host inside jBridge (e.g. Kontakt 64 bit, Omnisphere 64 bit etc.)
* register your plugins with jBridge via the registration "jBridger" tool that is part of the package. A tutorial can be found here: http://abtlog.wordpress.com/2009/11/05/deutsche-anleitung-fur-jbridge-unter-cubase-x64/ (the text is German but there are nice screenshots :) )
* install the 32 bit Bidule subhost vst and the standalone version (the demo does only work in standalone, so you need to buy the full version - it's very good price for value though)
* do a plugin scan inside Bidule standalone (under Preferences->VST). All jBridge wrapped 64 bit plugins should be recognized now.
* you can close Bidule standalone now, it was just necessary for registration
* start the "Plugin Scanner" inside EigenD and perform a scan. Bidule should be listed as a recognized plugin now
* load Bidule in one of the audio units (e.g. eigenbrowser hey audio unit 1 plugin browse)
* load the jBridged version of your desired 64 bit plugin inside Bidule
* configure the plugin as desired (load presets, change settings - whatever)
* configure the EigenD mapping as desired (e.g. parameter automation via yaw/pitch, breath pipe to midi cc 2 - what makes sense for the plugin)
* test whether it sounds and reacts as desired
* save the EigenD setup as a user setup
* close EigenD, restart it and reload your setup - everything should be in the state as you left it.
Have fun :)
Best,
Ferdinand