latigid on

Frequent Writer
  • Content count

  • Joined

  • Last visited

Everything posted by latigid on

  1. Troubleshooting midiphy SEQ v4+

    Please post your troubleshooting issues here and we will do our best to get everything up and running! The more info you provide, the better the answer can be formulated. What did you try so far? What wasn't working? Pictures, pictures, pictures!  
  2. Troubleshooting midiphy SEQ v4+

    Hi, These encoders should be decent, so I wouldn't think the encoder had gone bad. Rather, there might be an interconnection issue. The 9th encoder is connected to pins 4 and 5 of J1, so check that you get good contact there. If the pins don't reach far enough into the through-board header you might get an intermittent contact. Check all solder points too as you might have a dry joint etc. Best, Andy
  3. midiphy SEQ v4+

            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
  4. Sorry, didn't see your message as the notification settings were broken for a while. I can't say anything about Hauptwerk but you should be able to monitor debug events in MIOS Studio. I would try to diagnose the DIN/DOUT functions and matrices first at the hardware level. 
  5. Event_Sender, send all

    I'm no NG expert, but what is the exact event/ the parameters used? Do you set specific ports for example? Maybe post the config and somebody could help.
  6. Troubleshooting midiphy SEQ v4+

    Many thanks for reporting and I'm glad it works! Is the hub also connected to the computer and sending data that way? There is an OTG startup sequence where the devices have to decide who's the boss. Maybe things don't make it that far if there's too much going on with the datalines. Just speculation!
  7. midiphy Eurorack Expander Modules

    Hello, Peter made an awesome video (4k quality!) demonstrating the assembly of the following modules Euroceiver (line driver receiver in the rack), power distribution A1 Expander (AOUT based on MAX5500) D1 Expander (DOUTX1 for gates plus protection) D2/D3 Expanders (likewise for clocks and triggers) Feel free to use this thread for any discussion or troubleshooting. Have fun building your modules!     
  8. midiphy Eurorack Expander Modules

    Sorry, I managed to upload one twice. The quell PCB functions as a terminator, so you clamp unused inputs to 0V.  
  9. IMG-20200524-112838.jpg

    © 2020 latigid on

  10. midiphy Eurorack Expander Modules

    I recently designed Eurorack versions of DIN and AIN, still need to test but hopefully in the next few weeks,   @Antichambre maybe you should start your own thread as to not mix up things, thanks. Have fun! Andy
  11. IMG-20200524-111714.jpg

    © 2020 latigid on

  12. IMG_20200524_111705.jpg

    © 2020 latigid on

  13. IMG_20200524_111651.jpg

    © 2020 latigid on

  14. IMG-20200524-111642.jpg

    © 2020 latigid on

  15. midiphy Eurorack Expander Modules

    Not sure I understand fully. You adjust the trim pot to get the scaling as linear as possible, i.e. the trimmer should be set so each octave step is as close as possible to the target voltage. Then you use the SEQ encoders to finely adjust for each volt setting. The DAC can't drive negative bits, so there is a limit to the lowest setting. But the remaining octaves should be very linear. Did you already see @Hawkeye's video on the calibration procedure?
  16. midiphy SEQ v4+

    Sounds like it could be a software bug, in which case the following thread is the place for it:
  17. Troubleshooting midiphy SEQ v4+

    One other idea: you could try plugging directly into the 407v board (mini USB cable). Here is the schematic, maybe some of the jumpers are helpful?  
  18. Out-of-stock parts for midiphy BOM tool

    Some Mouser parts have longer lead times at the moment. Here's a few suggestions: 595-SN74HC595DR -> 595-SN74HC595D (just non-reel packaging) 490-SJ1-3535NG -> 490-SJ1-3535NG-BE (blue) 594-K104K15X7RF53L2 -> 75-1C10X7R104K050R 806-KCDX-5S-S2 -> reichelt Conrad CR1206-JW-331ELF SMD resistors just use a 220R or 71-CRCW1206330RJNEAC WP154A4SUREQBFZGW Kingbright LED, tricky to find a frosted one, but basically any generic CC RGB LED will do, or a bicolour 3-pin is fine but normally not available in "nice" green. *** Feel free to post your suggestions or if you can't find a part.
  19. Please post here if you find a Mouser part is out of stock or has a long lead time. Please provide: Mouser part number or URL Board or kit where it is required (Optional) replacement part suggestion Note that end-of-life parts might remain in the tool until the supply dwindles.
  20. midiphy SEQ v4+

    There's a few settings in the HWCFG to check e.g. (search "fast") # the speed value for GP encoders which is used when the "FAST" button is activated: ENC_GP_FAST_SPEED 3 # Auto FAST mode: if a layer is assigned to velocity or CC, the fast button will be automatically # enabled - in other cases (e.g. Note or Length), the fast button will be automatically disabled ENC_AUTO_FAST 1 # the speed value for the BPM encoder which is used when the "FAST" function is activated ENC_BPM_FAST_SPEED 3   Can you check if altering these changes things to your liking? Of course, some features might have been "broken" by hard-coding functions. In the Wilba SEQ version, there was one common fast button, no matter what encoder was pressed. In the v4+ we have all of the encoders on dedicated DIN inputs (matrix) to allow for different customisation. 
  21. Troubleshooting midiphy SEQ v4+

    The v4+ does nothing different to your previous method: the ID pin is grounded when in OTG mode and floating otherwise. Maybe check pin PA10 is correctly grounded on the wCore PCB/breakout? Cabling issue or missing contact through the 2x25 pinheader? Perhaps the value for R3 on the USB board is too conservative and 100R would be better.  
  22. Troubleshooting midiphy SEQ v4+

    Hi George, I'm not 100% on how it all works and could be wrong, but to my knowledge you shouldn't see any MIDI data on the computer from the slaved device plugged into USBA. So my first guess is that you should unplug the computer; you can't (or shouldn't be able to) have the SEQ as both host and slave at the same time. You could then check the SEQ MIDI monitor and route it out a different DIN port. Second thought is that the controller (which ones, so we can consider making a whitelist?) does not initialise properly. Best, Andy
  23. Troubleshooting midiphy SEQ v4+

    Green and gold! We're keeping track here:  
  24. Your connections are unclear; do you use the buttons in a matrix or directly connected to DIN pins? For direct connections, one common wire must be connected to 0V (ground), not to a digital input! Switches then trigger when the inputs connect to 0V. Matrix wiring is more complicated and you have to arrange the buttons and LEDs (electrically, not necessarily layout-wise) in grids.
  25. AOUT module calibration

    I suppose you mean an AOUT with MAX525? What app are you testing with? The SEQ has a calibration part too. But first, have you adjusted the trim pots to give a good scaling factor? The DAC with external reference outputs a voltage between 0-2.048V with graduations of 1/4096. The gain equation is also on the page.