Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Message

RE: [analogue-sequencer] Stooged P3 panel is an option. Interested?

2003-12-09 by Frank Vanaman

Hi all--

I'd be provisionally interested as well.  A couple thoughts: $100 (or a bit
more) would be OK with me, pricewise.

The MOTM grid is all well and good, but not at the expense of having to
remote the pots from the PC boards or change the button spacing. My vote
would be to maintain the spacings for controls as set up on Colin's boards.
I'd also prefer to have the 9 button matrix under the display so that the
function keys line up!

The last thought is this: what kind of switches/buttons is everyone that'd
be interested in having a Stooge-P3 planning on using? I've opted for the
funky square buttons (except for the two mode select buttons) like the setup
shown on the main page of the Yahoo pages, so if everyone else opted for the
round buttons, then I might have to opt-out.

Frank

-----Original Message-----
From: Dave Magnuson [mailto:resfreq@hoohahrecords.com]
Sent: Tuesday, December 09, 2003 10:22 AM
To: analogue-sequencer@yahoogroups.com
Subject: Re: [analogue-sequencer] Stooged P3 panel is an option.
Interested?
>
>He told me that a 10 unit wide P3 panel is possible, and
>that they can even help with the layout (the changes needed
>to make the P3 fit the MOTM grid, tickmarks around the
>buttons, different led holes, whatever, graphics, etc.)
>

I'd be interested in a Stooge panel if you can get enough interest (and the
price drops a bit).  Exceeding $100 is a bit much for me, but a *little
under $100* and I'd be able to afford it.

You mentioned making the P3 fit the MOTM grid:  Do you think that's
absolutely necessary?  It obviously wants to look very similar to the
style... but the P3 is going to look considerably different than the
average MOTM module.  Not too many of Paul's SynthTech modules have an LCD
display :)

Attachments

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.