] [Thread Prev
Re: OT: eventide following clock
nope, still sucks. here's something bizarre that i've noticed...perhaps significant, perhaps not.
tempo is staying locked no problem. when the sequencer is not running then the modulation stays locked to the tempo and all is well and the eventide is doing exactly what i expect it to do. as soon as i hit play on the sequencer and start feeding the eventide midiclock, that's when shit gets outta sync. if i stop the sequencer then the eventide adjusts the modulation to re-align with the tempo. so, it would appear that something
about constant midiclock input is causing the problem. i dunno.
furthermore, increasing "retrig" to 10.0 cycles (range 0.0 - 10.0) slows the inevitable drift. funny, the manual states this is in percentages but the machine is in "cycles". maybe this changes per preset...i've not looked.
On Thu, Sep 23, 2010 at 4:36 AM, Simeon Harris <email@example.com>
yes, global is the one. try again with the new os and see if it's more stable.
On Thu, Sep 23, 2010 at 4:16 AM, james fowler <firstname.lastname@example.org>
i've tried both but let me experiment again. a lot of my testing was done prior to updating the os...and it's all kinda running together. i know global is what i want, but shouldn't program be overridden if the machine sees a new tempo? manual isn't quite clear enough...
On Wed, Sep 22, 2010 at 11:04 AM, Simeon Harris <email@example.com>
do you have tempo set to global, rather than preset?
obvious question i know, but i had to ask...
On Wed, Sep 22, 2010 at 3:12 PM, james fowler <firstname.lastname@example.org>
i don't think i have a clock issue. the actual tempo is spot-on (as indicated by the "tap" led) and programs like loop10 lock on and stay right with the sequencer. same thing in the particular patch i'm struggling with "multishift 2". the tempo is fine but t_rate when set to 1/2 notes is all over the place.