Hello!

Hello!

Still rather new to the Eigenharp, but having a blast learning what I can put into it! Got a Tau some time ago. I’ve been experimenting with VST’s and saw mention of Native Instruments’ Kontakt and Reaktor 6 players. When I have Eigend search them out, though, they come back as failed plugins. I’ve seen this happen with a couple other VST’s I tried out as well. I saw something on the other forums mentioning that Eigend maybe doesn’t support 64-bit plugins, so that’s my best guess on why it doesn’t work. Anybody have advice on how to troubleshoot failed plugins or get them working?

0 thoughts on “Hello!

  1. Right, the Windows build is currently 32 bit only. Best bet is to send out MIDI and use another standalone host / DAW to host your plugins. (Would even make sense with 32 bit plugins when using several CPU intensive plugins that together tend to run into the single-core CPU limit. Because EigenD runs everything audio related in one thread and thus doesn’t make use of several cores – some hosts can)

    Like

  2. sorry, been busy recently… not been on here much.

    64 bit, yeah its a bit problematic since it requires the eigenharp drivers to be compiled for 64bit, and I dont have access to the windows drivers source code.

    but I have experimented and had working, a version of eigend using ‘user land drivers’ , which is probably the way to resolve this issue

    as for hosts, yeah I think alot of us use in conjunction with DAWs, Gig Performer using either midi or osc as a ‘bridge’ , the other option is Vienna Ensemble Pro (but its quite expensive, but very good) … the advantage of these opens is as Ferdinand said, it gets your DSP onto a separate core, which really helps performance.

    you can get to work with most daws, though some have specific MPE support which is useful… if you don’t have a preference id say perhaps demo’ing Bitwig as a starter

    Like

Leave a comment