[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Date Index][Thread Index][Author Index]

Re: OT: eventide following clock

the sequencer is in bidule and doesn't send clock per se.  in bidule things lock together with "sync" and in order to get midiclock out you have to use a module called "sync to midi clock" which generates clock info.  so...yes, the eventide is getting clock and only clock.  when i do give it more info it seems to be able to handle cc messages without fucking up further, ironically enough.

- jim

On Fri, Sep 24, 2010 at 9:41 AM, Simeon Harris <simeonharris40@googlemail.com> wrote:
is clock the only thing the sequencer is pumping out? if it's sending out other midi data, like notes and cc data, then i can imaging the eclipse would have problems


On Fri, Sep 24, 2010 at 1:18 AM, james fowler <twostroke@gmail.com> wrote:
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.