Yahoo Groups archive

200e

Index last updated: 2026-04-28 22:38 UTC

Thread

Lead time for 200e modules?

Lead time for 200e modules?

2007-07-24 by code842

has somebody from the list ordered and received any 200e modules since 
fall 06 or so? what was the approximate lead time, guys?
tnx

Re: [200e] Lead time for 200e modules?

2007-07-24 by JB

i have. in my case it has differed from 1 week to 6 months. sometimes
they have a stock sometimes they seem not to. Contact them and ask
specifically about whatever you are
planning to order. Large systems obviously takes some time to put together
as well, i'm not sure if they have a stock of cabinets.

johan


2007/7/24, code842 <code842@yahoo.de>:
>
> has somebody from the list ordered and received any 200e modules since
> fall 06 or so? what was the approximate lead time, guys?
> tnx
>
>
>
>
> Yahoo! Groups Links
>
>
>
>


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

Re: [200e] Lead time for 200e modules?

2007-07-24 by ezra buchla

hi

there have indeed been many modules shipped since fall 2006.

wait times are long at the moment because of several projects:

- fine tuning the 222e optics and firmware (it is very very close); this is
holding up several systems
- redesigning the cabinet latches; this is holding up a couple systems
- firmware updates for other modules. we have several new firmware releases:

- - 291e v8: bug fix (now properly stores sequence modes in presets);
autonomous preset.
- - 225e preset v4: autonomous preset override.
- - 210e v6: new feature: push knobs to toggle gain between unity and zero;
button debouncing is greatly improved; autonomous preset.
- - 261e v3: bug fix (pitchbend+225 crash condition)

the 210e and 291e can now store 1 preset autonomously: when no 225e is
present in the cabinet, the remote enable button acts as a save button and
the LED acts as a "state not saved" indicator.

we're also working on some MIDI bug fixes, which will likely affect the
261e, 225e, and 281e, as well as adding the autonomous preset feature to
other modules. so if you send your cardset in for updates it may be a little
while before you get it back.

we're also working on some new modules and other devices.

so, i apologize for the inconveniently long waits. as usual, we are trying
to make this highly complex instrument as functional and reliable as
possible.

-eb

On 7/24/07, code842 <code842@yahoo.de> wrote:
>
>   has somebody from the list ordered and received any 200e modules since
> fall 06 or so? what was the approximate lead time, guys?
> tnx
>
>  
>


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

Re: [200e] Lead time for 200e modules?

2007-07-24 by Chris Muir

At 8:10 PM +0000 7/24/07, code842 wrote:
>has somebody from the list ordered and received any 200e modules since
>fall 06 or so? what was the approximate lead time, guys?

I ordered a few modules to expand my 200e early this year ( one each of 261e, 281e, 292e). It took about six-eight weeks, if I remember correctly.

I agree w/ Johan that the cabinets are often the stumbling block.

Llike all small operations with a lot of different modules, when they go out of stock on specific modules it often takes a while before they do another run of them.

-C

-- 
Chris Muir           | "There are many futures and only one status quo.
cbm@well.com         |  This is why conservatives mostly agree,
http://www.xfade.com |  and radicals always argue." - Brian Eno

Re: [200e] Lead time for 200e modules?

2007-07-24 by Stewart Moroney

There was talk of updates to the 249e and 250e for midi clock etc,  
they still happening?

"we're also working on some new modules and other devices."

Don't tease, tell us more....

On 24 Jul 2007, at 21:33, ezra buchla wrote:

> hi
>
> there have indeed been many modules shipped since fall 2006.
>
> wait times are long at the moment because of several projects:
>
> - fine tuning the 222e optics and firmware (it is very very close);  
> this is
> holding up several systems
> - redesigning the cabinet latches; this is holding up a couple systems
> - firmware updates for other modules. we have several new firmware  
> releases:
>
> - - 291e v8: bug fix (now properly stores sequence modes in presets);
> autonomous preset.
> - - 225e preset v4: autonomous preset override.
> - - 210e v6: new feature: push knobs to toggle gain between unity  
> and zero;
> button debouncing is greatly improved; autonomous preset.
> - - 261e v3: bug fix (pitchbend+225 crash condition)
>
> the 210e and 291e can now store 1 preset autonomously: when no 225e is
> present in the cabinet, the remote enable button acts as a save  
> button and
> the LED acts as a "state not saved" indicator.
>
> we're also working on some MIDI bug fixes, which will likely affect  
> the
> 261e, 225e, and 281e, as well as adding the autonomous preset  
> feature to
> other modules. so if you send your cardset in for updates it may be  
> a little
> while before you get it back.
>
> we're also working on some new modules and other devices.
>
> so, i apologize for the inconveniently long waits. as usual, we are  
> trying
> to make this highly complex instrument as functional and reliable as
> possible.
>
> -eb
>
> On 7/24/07, code842 <code842@yahoo.de> wrote:
> >
> > has somebody from the list ordered and received any 200e modules  
> since
> > fall 06 or so? what was the approximate lead time, guys?
> > tnx
> >
> >
> >
>
> [Non-text portions of this message have been removed]
>
>
> 



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

Re: [200e] Lead time for 200e modules?

2007-07-24 by ezra buchla

the 250e may support midi clock soon. although, i don't necessarily see the
benefit of it considering the many options available with pulses from the
225 and the various pulse logics in the sequencer.

249e code is officially retired from development... (sorry) but maybe some
interested party will take on the monstrous task of rewriting it.

i can't really say more about new products (it's up to the boss...) just
that we're keeping busy busy busy.

-eb


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

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.