It's probably very usable in a DAW, where you don't care about a few extra milliseconds of latency, but we do and so far we haven't been able to figure out how to remove that issue. This is seriously complicated and has implications for latency that lead us to think it's not a great idea in a live performance system. Several companies out there (Bitwig, jBridge) are attempting to solve this problem by running the VST's in a separate process, so that 32bit VST's can be supported from a 64bit application.

We do discuss this fairly frequently in the dev team and the last time we did the consensus was 'wait a bit yet'. I'm more minded just to switch to 64bit only when the time is right to be honest, and I'm not convinced it is quite yet. A lot of our players use plugins that are still 32bit only, so it a change that means we'd have to support two complete different releases for, which is a lot of work, work that will just detract from other developments. We may, now that the number of 64 bit VST's has increased substantially, introduce a 64bit EigenD at some point., but bear in mimd that you cannot run 32bit VST's jn a 64bit host so it's a binary choice.

This means that it can run 32bit VST's but not 64bit VST's.

Hi Nik EigenD is a 32 bit application at present.

Jbridge not implement cando