i'm getting flamms (quick double hits on various pads) plus timing on the hits is very very loose (lots of drift) PLUS geist is just completely getting lost at times (as in it'll jump around say 2 1/2 beats for a sec, then jump back, then maybe crash. or not.)
the flams and timing thing seems to be inherited from guru, i had some of the same exact problems with it - however geist is actually worse! (ie. it actually crashes pro tools, etc)
i've got huge buffers set, optimized my system for protools properly, etc. i've been running pro tools for 10 years already, and while i love guru, and suspect i would love geist, i have to say it's odd that this is still a problem after having years now to fix it. i'd let it gobefore because for various reasons i had switched from HD to m-audio soon after i got guru, and it was never a problem under that particular combo. now i'm thrilled to be back on my HD system, and i was hoping that upgrading from guru to geist would fix the timing and flamming problems, not exacerbate them.
please please please tell me there's an easy fix for this! if it helps i've been thinking of upgrading to 10.6 and protools 9, but i'd have to renew my waves bundle as well, so we're talkin about 100's of bucks to fix something that, until i bought geist, wasn't broke.
Hmm. I'm unable to reproduce that with Pro Tools 9.0 and OSX 10.6.6, and never experienced it with Pro Tools 8.0.4 on 10.6.2 either.
Things to check:
Check you've not got some sort of midi feedback loop going on.
Check you've not got midi data coming from Pro Tools going into Geist, whilst Geist at the same time plays its internal patterns - that could easily create flamming.
Try changing your buffer sizes and making some comparisons between them in terms of performance.
Try disabling any PDC you might have enabled in the project.
Failing that, if you can use Jing (www.jingproject.com) to make a demonstration video so that the issue is much more clear to us, that would be helpful.
tbh i didn't even know i had pdc on - i thought that was something they only brought in on pro tools 9, i was surprised to see the option there. its at the bottom of the options menu, and is either checked on or off. it was checked before, now it's off.
i've been messing with it now for an hour or so, and so far no crashes or noticeable drifting in the timing of the hits. thought i heard a flam or 2 early in the session, but i haven't noticed one in a while...
btw, if i do upgrade to pt9/osx10.6, i'm looking forward to using that (new?) function where they delay compensates for all the various plugins (ir-l and linEQ spring to mind, the lag on both is driving me nuts), hope i wont have to turn it off!
ok, so geist is now running better, but not perfectly. there's still occasional flam (about once a minute or so?) plus a fair amount of drift on the timing of the hits (ie. timing is not rock solid, individual hits move around by random amounts of milliseconds, making the beats sound pretty sloppy)
this is similar, once again, to running guru on HD as opposed to protools m-audio powered.
any advice for getting geist running perfectly with pro tools 8.0.4 on osx 10.5.8? again, i'd rather not have to spend hundreds of dollars on upgrading osx, pro tools, and waves all at once (given my current financesthis would be difficult to do)
is there a best/recommended setting for protools playback engine? any other settings/fixes i could try for fixing the drift/occasional flam?
also, just for the record, i'd like to hear an "official" answer as to whether or not i'll be able to use geist with ADC in pro tools 9.
I have noticed that I get alot of (#-9xxx) Errors with PT9.0.1 when using Geist even when the overall CPU usage of the project is quite loat at aroun 28% @ 512Buffer Size (23ms Latency, lower is not possible with Geist in order toavoid those 9xxx Errors )
The only way to reduce :(maybe by 5%) the errors seem to not use the built in sequencer.
I really hope they improve this.
BTW I have also noticed those double hits when manually triggering the pads by playing midi notes on my system.
Quite rare but definitely there.
so does anyone from fxpansion want to address these issues with me, or can we just leave it as read that fxpansion is not actually compatible with protools and should be avoided if that's what you compose on? i'm still waiting for an fix and/or answer regarding
a) how to fix the continued poor timing and flams from geist on pt8/osx 10.5 and
b) an answer as to whether or not i'm going to be able to use pdc/adc if i spend several hundred dollars upgrading to PT9 and OSX 6
ps. i have no interest in signing up for www.jingproject.com, but hopefully the above mp3 is enough to demonstrate my problem to you. let me know if there's something else you need from me!
i've started a support ticket, #30934, and sent a sample preset via that ticket/email, but for the record the problem manifests itself every time, not just on one particular preset. thanks for your help and i'll post up the results of our troubleshooting here later