200e

sorry, yeah i said that wrong originally, "advance" mode is not the
appropriate one, "stop" mode is.

blip blip blip

On Thu, Mar 27, 2008 at 5:49 PM, JB <ringmodulator@gmail.com> wrote:

>   no, set the steps for stop if you wish to advance by external pulses
> (not using the internal clock)
>
> 2008/3/27, tmeade1974 <tmeade1974@yahoo.com <tmeade1974%40yahoo.com>>:
>
> > So if you set the 250e to Advance mode and apply a pulse at the
> > Start/Advance input, the sequencer will advance to the next stage
> > every time it receives a pulse, regardless of any time setting you
> > have set. I don't have it in front of me but that "should" be the
> > "default" setting on the 250e, ya?
> > --tom
> >
> >
> >
> > --- In 200e@yahoogroups.com <200e%40yahoogroups.com>, "soma_studios"
> <john@...> wrote:
> > >
> > > Hey y'all,
> > >
> > > Forgive the noob question, but I'm trying to get my head around the
> > 250e stage selection
> > > behavior... From what I gather below, it should be possible to
> > advance the sequencer one
> > > stage per incoming clock pulse (assuming none of the
> > adv/sust/enble/stop functions are
> > > selected for that stage), or no? It seems that whenever a pulse
> > arrives at start/adv, the
> > > internal clock begins advancing as well...
> > >
> > > Thanks much
> > >
> > > John
> > >
> > >
> > > --- In 200e@yahoogroups.com <200e%40yahoogroups.com>, "ezra buchla" <
> ezra.buchla@> wrote:
> > > >
> > > > with midi, you can use the pulse outputs from the 225 note busses to
> > > > clock the 249e, 250e, or 291e in "advance" mode. i've used this a
> > > > lot... since each stage of each sequencer can be assigned logics
> w/r/t
> > > > incoming pulses, this allows for much richer behavior than just
> > > > syncing to a clock (which, again, we still plan to implement; the
> 249e
> > > > in particular already has a bpm data structure...).
> > > >
> > > > you could also use an analog pulse as a clock. any voltage with a
> > > > (>=10v) -> (<10v) transition will work as long as the voltage source
> > > > and the 200e share a ground.
> > > >
> > > > as for midi out, we're working on it and considering different
> > > > interface options. the strongest idea so far is to be able to
> > > > individually assign 225 busses to input or output CV, but this
> > > > requires some new GUI programmming. the wiring is all there already.
> > > >
> > > > -eb
> > > >
> > > >
> > > >
> > > > On 2/14/07, jon schatz <jon@> wrote:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Wed, 14 Feb 2007, ezra buchla wrote:
> > > > >
> > > > > > since there's some speculation, hey
> > > > > >
> > > > > > neither 200e sequencers currently respond to midi clock, but
> > this is
> > > > > > on the intended feature list for both. (i think that means the
> > > > > > firmware is technically "alpha.") 249e firmware development
> > will be
> > > > > > slower since there won't be any more of the hardware.
> > > > > >
> > > > > > MIDI out is another intended feature (the 225 is sired for it);
> i
> > > > > > don't think any of us has specifically considered clock out
> > but it's a
> > > > > > fine idea and it could be done if there's enough interest.
> > > > >
> > > > > hi ezra/everyone,
> > > > >
> > > > > how do you sync up your sequencers to external gear?
> > > > >
> > > > > thanks,
> > > > >
> > > > > -jon
> > > > >
> > > > > "There are no differences but differences of degree between
> > different
> > > > > degrees
> > > > > of difference and no difference."
> > > > > - James, William. "Subjective Effects of Nitrous Oxide." Mind.
> > 1882; Vol 7.
> > > > >
> > > >
> > >
> >
> >
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
>  
>


[Non-text portions of this message have been removed]