consumer

@latigid on I'm excited to see the new sequencer as well and will certainly buy a kit as soon as it's available. This looper project though... It's just the bee's knees. I might be savvy enough to build a prototype PBC, if you offered one to me: At the very least, I could let you know the pitfalls that an idiot might expect in building one ;)... Actually a big element of my job is technical writing, so I could probably truly assist in helping to develop the build manual: Give me a schematic, some nod at the idiosyncrasy of the BOM and a PCB and I could pump that out. ...If you wanted. No pressure... The very second that you guys feel comfortable releasing it into the wild, I'll take three!! (and I bet I'll feel like that's one too few). I'm loving what you're doing. As my thesis professor used to say, "Keep going", dugan

I have nothing significant to add to this discussion, but I want to follow this thread and I am extremely eager to see this project progress: I have essentially only used the MBSeq4 that I built in this capacity - as a looper, but I found it a bit cumbersome for the task - Please understand, I'm not criticizing the MBSeq, but instead my ability to navigate using it for the task I ask of it. It does so much more than I need of it that my small mind gets lost in the options. I built a MidiRex in an attempt to simplify, but then found it not nearly as dynamic as I'd like, especially after I'd been spoiled by the MBSeq. This appears to me to be the Goldilocks solution to the workflow that I desire. I am really, really excited to see this project move forward. Best wishes & highest regards, dugan

I'm glad you got yours working, too Gerhard! It's a testament to TK's incredible knowledge that he solved this issue with conjecture alone. You and I should update the wiki's blacklist and/or whitelist with our interfaces so the next cats who come upon this are less blind than we were. -I think TK is going to update the LPC17 page to indicate that some USB/Midi interfaces will behave better with the workaround he provided. Just to confirm against better minds than my own: Removing the 220 Ohm resistor only adds ca. 2.5mA to the Midi Out signal path and should not be deleterious to most/any equipment connected to it, correct? Thanks!! dugan EDIT: Gerhard- The kludge is only so that your Midi/PC interface works with your PC & MIOS Studio... You only need to bridge R26 if (for some weird reason) your Midi Out isn't working with your other Midi hardware... in my case Midi Out always worked with my midi hardware, just not with MIOS Studio. ...If it is confirmed (by folks smarterer than me) that there is nothing deleterious about removing R26 (&r21) you can if you like, but I see no reason to do so if it's communicating with the equipment that you want it to. You already have MidiOut 1 & USB to talk to MIOS Studio, there's no reason to have 3 ways of getting Midi Out messages to MIOS Studio... I think... TK (or another genius): The R21 / R26 resistors are only there to rectify the signal to ~5mA if the initial voltage was 5v, right? Cheers!

TK (and Gerhard!), I removed R21 and installed a bridge and the MIO interface now communicates with MIOS Studio exactly as it should. Thanks!

Hi! I was having the exact trouble Gerhard describes. USB is/was working perfectly. But when powered from a wall-wart with a MIO iConnect the MIOS Application is not recognized, MIDI In works fine, but MIDI Out does not work at all. When I switched interfaces to my Scarlett 2i4 everything works perfectly. The thing that threw me off track is that the MIO iConnect plays perfectly with my sammichFM (among others), so I didn't stop to consider that the interface was the issue- I assumed my soldering skills were at fault. Apparently it is one of these interfaces that does not recognize 3.3v, only 5v that TK describes. I'll update the white and blacklist with my findings. Best of luck Gerhard!! -dugan

Very nice design Smokestack! Any more direction on hardware that you can offer?: -What standoffs did you use to mount the Core? What hardware did you use to 'sammich' the enclosure together? LCDs? You'd mentioned a diagram in your first post that would illustrate these things; any progress on that? (I could put it together for you if you PM'd me a hand sketch...everybody's busy ;) Have fun.

Thank you both for your responses. That was my assumption, but sometimes it's best to ask the sages. Wilba, I understand your metaphor and completely intend to add heatsink compound at a later date, but hoped that the lack thereof would not stop me from testing voltages, software testing, etc this evening. As I understand it the tab of the 7805 is connected to ground; I was simply inquiring as to whether or not there was any possibility that omitting the compound (for now) could cause some bridge between GND and +5 or !!!Vin. Logic and my faith in the amazing design capability of Nils & Wilba tell me 'no', but that's an awfully expensive assumption to only verify through continuity tests and not against the knowledge of this friendly community. :) Lesson learned. Have fun!

Subquestion: Is the non-conductive heat sinking compound completely necessary? -Some is coming to me in my next order from Futurlec, but who the #C.C@ knows how long it will take to reach me... Ah, Futurelec... Thank you!

Great tip, thank you woolsey!

Howdy, So over my gluttonous holiday weekend I started, and got reasonably far along with knocking together a control surface PCB for the MBFM in KiCAD. It's pretty rigidly based upon TK's control surface; right now the controls correspond to exactly to the MBFM_DIN_Default and MBFM_DOUT_Default pdfs. I've selected the PT-10 case and the circuit board dimensions correspond to PacTec's recommended dimensions. The enclosure may change if I find something totally awesome while stumbling through the internet. I'm hoping to integrate this into Wilba's sammichFM base PCB (BTW; you're covering the Midi, Power & Audio IO, right Wilba?) I haven't really begun routing it yet, just a few test runs with KiCAD's autorouter. I also likely haven't finished placing components either. And I likely haven't abandoned the notion of changing cs_menu_io_table.inc and cs_menu_enc_table.inc to find a more polite layout. Clearly this project is half-cocked, possibly even one-quarter-cocked, but I'm submitting it to this bright bunch for your amusement and use. The package should be pretty self-contained; all parts and footprints are in their own libraries and opening the .pro file should find them, but if you're missing something let me know. If you see something totally wonky please tell me. Same goes for if you see anything that only a genius would notice that would solve all my problems. Ok; Have fun! dugan MBFM_CS_2010-11-29.zip

This still open? -I added my name to the wiki page. Rock!

findbuddha, I greatly appreciate the effort you've put into this. I'd like to help to further this project by designing a compatible Ponoko case. I have a couple questions though: Did you take into account Wilba's suggestions found : Do you agree with them? -If so I think I can pretty quickly modify the dimensions of cutouts to be more "Ponoko sloppy." Anyone out there have suggestions about the case dimensions, especially depth? As I begin to mock it up in SketchUp things are pretty tight with Wilba's suggested minimum clearance for height. -Attached is a very first pass of the 19" version in SketchUp; a massing model++ simply to get a feel for it. More to come. Thanks everybody, you are all constantly inspiring!! WilbaSEQ_19_100812.zip