Forum

I downloaded it for a try and can't even get it to load.

oh forgot to say Snow Leopard - no Lion on this machine and not likely for a while.

Yeah, it looks like it would be really nice and I'd love an AU acoustic sound. It takes a bit of setup to change some stuff like bend changing the string type, but after that, it was nice.

But I can't play for more than a few minutes between crashes. Maybe they'll put out an update to it.

Here's Geert playing 'Wish You Were Here' using the OT sample set, in case you haven't heard it before. It's a very good sample set for the acoustic guitar. I think physically modeled guitars are the future, but they've got a little way to go yet before they are as good as that.

Something you also might want to try is to ensure that the MIDI data sent to the plugin is decimated in the global settings of the Routing Matrix (http://www.eigenlabs.com/wiki/1.4/Routing_Matrix/).

I've seen other plugins crash due to the high data throughput from EigenD to plugins when no decimation is active.

I tried running it standalone first and still had an issue with it crashing relatively quickly. I'm going to try modifying the midi data sent next, but as a new owner, I admit to being overwhelmed at times with some of this stuff ;)

I do wish there was better documentation. I'd much prefer written stuff to the video stuff. The videos are great, but when you want to search for how to do something specific, there's nothing that beats the written word.

If it is crashing running standalone, the problem is likely with the audio unit and not EigenD. It might be worth sharing your frustration with Shaky Guitar?? After all, the only interaction is MIDI.

Have you tried running it in Garage band and/or logic to see if it is stable in that setting?

@snoltan - AU's and VST's run in the same process as EigenD which means that if they crash then it always crashes EigenD and appears as such (and depending on the problem it might even cause EigenD to crash at some random later time too as an errant AU can break all sorts of things). We, as an AU or VST host, don't get any say in this matter, any bad behaviour by one can bring down EigenD and there is little we can do about it. Technically the onus is on the AU author to write their program to behave well and there is no protection for the host program (EigenD in this case) if they do not.

There are a lot of less well written AU's out there (which is to be expected really, especially in the non-commercial free ones) and there is sadly a limit as to what we can do about that. We haven't actually seen a situation for some time in which we've made a hosting error. This is not to say that that isn't possible, it's just that the interface isn't really that complicated and we got most of the bugs out several years ago. In the last year every problem we've had reported has turned out to be an issue with the AU or VST rather than EigenD.

EigenD does represent a mildly different runtime environment for AU/VST's than many DAW's. Not in any sense that it obeys different standards but it does use threads in a different way to say Logic, which can tickle bugs in peoples AU's. We have seen just this in a number of different situations in the last couple of years. As far as you're concerned this is of course irrelevant, it's just broken and that's annoying, but it does mean that there are limits as to what we can do to fix it. And it's worth bearing in mind that quite justifiably many AU/VST authors don't test their products against EigenD, they just pick one or maybe two major DAW's and use those.

I'd love to be able to host AU's in a nicely sandboxed, robust way that meant EigenD didn't crash when they do. Unfortunately the performance hit you'd have to take to enable that is huge, and until computers get a whole load faster, it's just not practical.

John