nope, no love. At least not in bitwig – I reported this issue to their forum a while back when running the previous version 1.0.10 (just upated to 1.0.11)
From the report in terminal it seemed like an issue where bitwig was trying to run the 64 bit plugin within a 32 bit pluginhost. According to bitwig – it is but only after the plugin fails within the 64 bit plugin host.
Previously it was failing in the 64bit host w/ an “undefined symbol error”
http://answers.bitwig.com/questions/873/on-linux-loading-64-bit-so-plugins?page=1#957
Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen