] [Thread Prev
Re: OT: eventide following clock
ps - it was fine when i was passing clock straight to the eclipse, without any other midi activity going on. it was only when attempting to merge clock with pc or cc data that i had prolems
On Wed, Sep 22, 2010 at 2:59 PM, Simeon Harris <email@example.com>
i found i had problems with my t_rates with 4.0. incoming clock was so flaky that modulation rates set to a fraction of the global tempo were all over the place. i ended up setting them as absolute values. it was better with 4.1 though. it's like it's too over sensitive, or something. my D2, which i also had slaved to midi clock, was much less sensitive to small changes in clock value and was therefore more stable.
On Wed, Sep 22, 2010 at 2:52 PM, james fowler <firstname.lastname@example.org>
i was using 4.0 beta but had to fall back to 3.51 as the beta version did some really strange thing to a lot of the shifters, which i use the shit out of. so, i just got 4.01 and yes it is better but still not up to snuff. i'm surprised, really, as this is the first problem i've had with eventide in nearly a decade of using their gear.