Jump to content

latigid on

Frequent Writer
  • Posts

    2,524
  • Joined

  • Last visited

  • Days Won

    149

Everything posted by latigid on

  1. We're just about ready for launch of the new SEQ v4+. This thread serves as a proper introduction, you can also ask questions on hardware etc. I first became aware of the SEQ around 2008. This was about the time of the migration point of V3 to V4 and the Wilba design. I finally got my hands on a Wilba front panel in 2012 and I was rocking the hardware soon after. Around the end of 2016 I felt there was room for improvement. a number of my TL1100 buttons were failing on my unit there was still no "standard" case available, also the rear panel was not well defined the PCB supply situation was (IMO) non-transparent and confusing for new users I had ideas about hardware changes What started as a simple question morphed into a multi-page idea thread. It was clear that the idea of incorporating a 16x4 matrix was not feasible from a software perspective, but it at least catalysed the idea towards a flexible "selection row" and other handy features. i liked the idea of mechanical keyswitches for their quality and very reasonable price. I then worked on a concept of illuminating these, finally settling on a misused superflux LED through a Matias switch. It became clear that a "complete solution" would require redesign of all of the boards, so I spent the winter of '16/'17 doing that. This entailed sourcing hardware items such as high-quality OLED displays, Matias switches and keycaps, a new Core breakout board etc. I periodically checked in with @TK. to confirm the right direction for the hardware (matrix routing and button features). Without saying, the SEQ platform is an incredible piece of work and TK. deserves a lot of credit and praise. From the start, I was in contact with @AdrianH about potential case designs. He has taken all board outlines and done the CAD work himself. I think you will find the case an excellent solution to cramming a lot of hardware inside while keeping the panels clean. Peter @Hawkeye is the co-partner of MIDIphy. He handles the business side and also webdev. Perhaps more importantly, he is a very enthusiastic builder and documenter of all the designs. Normally I will do a test version, but the product photos and demos are usually his. I have spent endless hours discussing and debating/reasoning with him and there is always a positive and fruitful outcome. Hats off to you! So: thanks for all of your interest so far. The aim is to provide you the best opportunity to build your very own SEQ. Andy --- Video Build Tutorials --- --- MIDIbox NG Downloads (for testing) --- SEQ_L.NGC fluxtest.ngr
  2. latigid on

    SEQ v4+

  3. Will do. Current focus is on the SEQ v4+, LoopA etc. Best, Andy
  4. Really great to see your project come to fruition. Congrats!
  5. It's been said many times, but the DAC chip is often non-linear. For example, my channel 1 is unusable as a CV source as I can't get a linear response across the whole range no matter how I calibrate. It's not clear if this is a typical defect in the chip or whether certain channels are damaged during hand soldering. The other channels are fine :).
  6. Part of the standard EAGLE libs. Best, Andy
  7. Case protos are in (thanks @Hawkeye for the pics!) This means we won't be in time for spring, but with luck it won't be too long before the project is ready to go. Best, Andy
  8. Well then. The ability to reroute single-channel poly info to MPE across 16 channels of a port would be cool and a good use of all of those MIDI ports! ;)
  9. MPE has now been standardised: https://www.midi.org/specifications-old/item/the-midi-1-0-specification Anyone keen to write MIDIbox drivers for it ? ;-)
  10. http://ucapps.de/mbhp/mbhp_core_v3.pdf http://ucapps.de/mbhp/mbhp_iic_midi.pdf http://www.midibox-shop.com/quadIIcMIDIR2.html Have fun! Andy
  11. What Core version? J4A is the I2C port.
  12. There they are! Many thanks!
  13. Again, the email notifications are not being sent...
  14. This was a great project to do, as Peter had a clear concept in mind from the start from his previous prototypes. We spent several weeks discussing the possible hardware features and figuring out how we'd source the parts. The hardware design took about a month or so, sped up by the fact that I was reusing some of the SEQ hardware elements. The initial tests were fine, although getting the boards stacked was a puzzle of headers! All sorted now. Peter is one of the nicest and most enthusiastic people I know. He's being modest (as usual). The case design he did himself 100%, I even made him extract the SVGs from the PCB gerbers! The software, although built on a very solid base provided by TK., took lots of extra work, especially coding the display, various bug squashing etc. Good work all around!
  15. and does it work? Did you save/store the changes then reupload _NG?
  16. I received a short update from Adrian that he had an unexpected callup. Things are still in progress and we'll update as soon as we know what's what.
  17. Looks to be the correct one. The supply is +5V as noted a few posts above, so no changes needed to the BOM. You will have to upload the bootloader hex and change the display type though.
  18. http://ucapps.de/mios32_bootstrap_newbies.html >> LCD Type
  19. Hehe, LoopA proto is just out of shot :). Nice sounds and arrangement!
×
×
  • Create New...