Jump to content

latigid on

Frequent Writer
 View Profile  See their activity

  • Posts

    2,516

  • Joined

  • Last visited

  • Days Won

    147

 Content Type 

Posts posted by latigid on

  2. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Hello,

    Glad you liked the tutorial video! Peter deserves a lot of credit for these and he does a fantastic job. 

    One of the pin headers is a bit too long. We are looking to replace 929834 with the 929700-01-36-RK part. If you've already ordered, no problems, but you may have to trim the pins a little shorter. It might also work with a standard single-row male pin header of about 6mm in length. 

    Apart from that, I don't think there were too many changes in the last while.

    Agreed about your technique; I just put a blob of solder on there and cleaned it up after! (they are capacitors) 

    The ribbon cable, IDCs, screws, nuts, washers etc. will be done as a separate "BOM" attached somewhere else, such as the case. Work in progress!

     

    Thanks again for the feedback and good job on the PCBs so far.

    Best,
    Andy

    • Like 1

  3. Help troubelshooting button matrix please

    in MIDIbox SID

    Posted · Edited by latigid on

    Perhaps update the docu then? There's been no edits on the wiki page for over seven years and Wilba's been gone for five or six...

    Edit: okay, I've updated it. My comment was considering that if the issue had been noticed previously, it would've been nice to provide the info at that time... But yes, outdated doku sure is annoying...

    • Like 1

  4. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Peter's probably too busy to answer, but as he said above, he's filming the doku stuff now, which does take a lot of effort. We'd also need to place an order for cases. Other than that, everything is ready I think!

  6. dipCoreF4 and dipBoardF4, a compact Core.

    in Design Concepts

    Posted

    Isolate is a polygon parameter that automatically keeps distance to routed traces, drill holes and pads. I am very conservative with isolate (0.5mm/~20mil).

    Clearance is the distance between two routed traces, also related is the distance between copper and a dimension (edge of board or slot).

    Conservatism is overkill, but the more conservative, the less chance of something going wrong. E.g. imagine a piece of dirt or dust on the photomask. If the clearance is too low, the fault might manifest into the production and short or cut a trace. Just because the fab gives low min clearance rules, doesn't mean they're a target. 

    Just my opinion of course, please decide what's right for you.

  12. seqv4 songmode

    in MIDIbox SEQ

    Posted

    Hello,

    Check out the masterful SEQ beginners guide, particularly under "5.2.3. Save & Take over Patterns." This I think aligns with your idea.

    You may want to read about bookmarks, which are available as a related but different workflow controlling things like groups of mutes or the view type. Bookmarks are a selection-row mode on the midiphy.

    Best,
    Andy

     

    • Like 1

  17. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Thanks for the great feedback!

    I don't use solder paste myself, but it may be easier to work with once it's a bit warmer, so I've heard of leaving it in your pocket or so.

    You can find out about SWD programming here: 
    http://www.midibox.org/dokuwiki/doku.php?id=wcore

    The test-as-you-go idea is a good one; this would basically consist of checking SMT pins were not shorted together, that the +5V rail is good before applying power etc. There's not too much to debug especially on the I2C/MIDI8 boards etc. as they're quite simple. But a basic MIDI test would not be a bad idea.

    Best,
    Andy

  21. Waveshare Core

    in Design Concepts

    Posted

    Aren't the GPIOs used as LED outputs already at 3v3? So where are the current values derived from? E.g. the Res/SD board specifies 1k for each in the BOM tool. 

    ? don't really like giving resistor values for LED brightness, as it's always so subjective. Starting values, sure, but you can always season to taste.

  22. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Just now, rbv2 said:

    right.. twelve was said in the video.

    Again, I'm not sure where? Twelve ports maybe? Anyway, no bother :happy:.

     

    Just now, rbv2 said:

    it's certainly a bit exaggerated with the 16 ports but i'm using expert sleepers at the moment with 16 midi out and thought of a simple switch box that allows me to determine for each synth whether it gets its signals from the computer or the hardware sequencer without moving a cable.

    guess eight outputs will be enough anyway :P

    The SEQ v4(+) natively has four USB busses, each with the normal 16 channels. IIRC the USB-MIDI communication protocol is even enhanced over DIN-MIDI. So if your interest is interfacing with softsynths and hardware, that comes right out of the box!

    Of course for the synth dungeons, something like Bruno's moar16 would come in handy, but the "basic" SEQ can already do quite a lot.

  23. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Thanks for the kind feedback! 

    I'm not sure where you got 16 MIDI outs from? The max here would be 8 (MIDI8 + I2C). There is a possibility to use a second I2C with a firmware hack to gain 4 more, but for space and latency versions this wasn't included in the standard build. @Antichambre is developing a 16x16 MIDI expander but again it doesn't fit in here. Another thing I can think of is hosting a GM5x5x5 or the newer chip, but it's also not in the plan nor complete at the moment.

    Of course you have 8 outputs with 16 channels each, so plenty to work with using the 16 sequencer tracks. What was your plan with 16 MIDI outs?

    CV/gate would go through the DB-25 line driver. On the other end AOUT/DOUT modules are required (under development, some solutions already available).

    • Like 1
×
×
  • Create New...