bugfight

ah ok, it sounds like if building a new seq, these should be on the main panel, and only users with existing v2 seq would want to put them on the extension. just to be clear why i asked this: i am planning to build an extension module and connect it to the main seq with say a db9 connector, carrying only the din/dout signals. sounds like if other folks follow this and want the track group buttons on the extension (i think only makes sense for existing v2 seq), they will need to add these... i suspected this was too expensive, sounds like the 20ms would be fine though. when pressing several buttons at once, the lag would be <number of simultaneous buttons> * 20mS, right? thanks for the infos!

I have a few questions about the SEQ duo matrix, before the sparkfun pcb thing gets serious 1. what is the function of the 4 "extra" buttons on the left? 2. are the extras single leds? 3. do the extras have their own shift registers, (so 4 pins are left unattached)? 4. does/will the seq software implement the debounce feature from the duo example? ok, that's enough q for now...

hehe i like "the thing" references to buggery aside... agree about monome requiring a pc... seems tk's duo example app can be customized quite easily, so there's your app. while it might be cool to have a "standard" bankstick patch format, that would of course limit the variety of things you can do, but that's another topic altogether...

as i mentioned earlier, these are from gold phoenix. if a pcb run happens (likely i think), i will probably use another house that does ENIG. gerber sharing is not a good idea for reasons expanded upon elsewhere.

excellent!

hehe cimo=king of hijack... anyways, the thing is ready to plug into the seq, which i haven't built yet. all that remains is making a panel and working out a good way to mount the buttons to it. i will also make a monome-like thing (duome?) it uses dual leds, common cathode just like tk's. i think there may be enough interest to do a small pcb run...

this really belongs in a pm or email

who got an f on their bit test cause they skipped it??

akkk, 3 levels of politeness for everything, i wouldn't live through it...

awesome! lol etc etc me too woohoo and so forth

hmmm what model? some of these wind up with ac at the tip. there is also the issue of ESD on some irons...

sorry, mb-fm is low priority for me, especially since i have to wait for cut resistor lead kits...

that will work too... but i wasn't suggesting a new pcb, you could put the cathode leads together...

i don't know about jimp, but i got mine at a surplus house near me and they are "normal" red and green inverting the buttons is not trivial. for one thing, you would have to use pull-down resistors instead of pull-ups ie connected from pin to gnd instead of from pin to vdd have you considered using two 3mm leds?

i can't believe you would just up and change your nickname like that...

aren't the fm dacs floating point?

The Tough Coughs As He Ploughs the Dough http://www.langston.com/Fun_People/1993/1993AEU.html

but is Schrödinger alive or dead? "dBLive" suggests alive but how can we know?

i do like this idea. now i wanna hear it...

other than the obvious irony of all that... huh? what? *whack* p.s. it was edited only for content and to fit your television set

what? what are you talking about?? *whack*

round pegs in square holes, kitten huffing, mass hysteria! looking good, dB

or better: control volume and feedback with the "extra" aout channels

ugh

try this (off the top of my head): void J5_DOUT_Set(unsigned char oct) { PORTAbits.RA0 = (oct & 0x01) && 1; PORTAbits.RA1 = (oct & 0x02) && 1; PORTAbits.RA2 = (oct & 0x04) && 1; PORTAbits.RA3 = (oct & 0x08) && 1; PORTAbits.RA5 = (oct & 0x10) && 1; PORTEbits.RE0 = (oct & 0x20) && 1; PORTEbits.RE1 = (oct & 0x40) && 1; PORTEbits.RE2 = (oct & 0x80) && 1; } != 0 might be better than && 1, have to look at asm output... (maybe could even do without the && 1 at all)