• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral


About TK.

  • Rank
    MIDIbox Guru
  • Birthday 11/17/1972

Contact Methods

  • Website URL

Profile Information

  • Gender Not Telling
  • Location Germany
  1. midiphy SEQ v4+

    Without a model of the IC an academic discussion isn't possible. Simple measurements would help to understand the internal circuit. Best Regards, Thorsten.
  2. midiphy SEQ v4+

    This isn't correct, see also the SN74HC595DR datasheet: Output drive current is 6 mA, which means in other words: you've to add an internal resistance of ca. 800 Ohm to the calculation. This could be doublechecked by clamping an output to ground, and measuring the current draw while the pin is set to logic-1. Best Regards, Thorsten.
  3. midiphy Eurorack Expander Modules

    That's the reason why I haven't listed J10A/B in my requirements list - it's just important to have a standard control surface (SCS), otherwise applications won't be re-usable. The 6 buttons + encoder could also be connected to an on-board DIN SR, connected to J9 as the first SR in the chain. Would be happy to evaluate it. Best Regards, Thorsten.  
  4. AINSER configuration (Aftertouch)

    Yes, I think it's only a display problem in MIOS Studio, I should change this to a decimal value. Best Regards, Thorsten.
  5. midiphy Eurorack Expander Modules

    Must-have requirements: STM32F407VG (1MB flash) SCS with 6 buttons, 1 encoder and 1 GLCD (so that we can also use the display as a scope) 1 MIDI IN, 1 MIDI OUT USB Device SD Card SRIO (J8/9) J19 for AOUT 50mm depth HP doesn't matter as long as it still fits into the Pod40X case together with the Expander modules Optional: up to 3 additional MIDI IN/OUT (could also be provided as an optional module) USB Host 4 on-board LEDs Audio-DAC Potential extension modules: SRIO based encoder/ledring modules AINSER64 module (with at least 8, but maybe 3x8 INs?) - inputs should be buffered, protected and maybe also amplified and level-shifted for +/- 5V Such a module could also cover MBNG for script based processing. Best Regards, Thorsten.
  6. midiphy Eurorack Expander Modules

    @Antichambre very nice! Does it provide J8/9, J10A/B and J15A? (For J15A the pins for GLCDs with serial interface might be sufficient) @latigid ondepth >50mm isn't suitable, it won't fit into my case; I guess that this limit is considered by most Eurorack modules. Best Regards, Thorsten.
  7. midiphy Eurorack Expander Modules

    A downstripped MBHP_CORE_STM32F4 module in Eurorack format would be nice-to-have as an alternative solution to the Euroreceiver - maybe with a SCS (6 buttons, encoder, display) - this would allow to run MBCV which gives us a lot of LFOs, Envelopes, sequencers, modulation matrices, etc. Best Regards, Thorsten. 
  8. midiphy Eurorack Expander Modules

    Modules in 4ms Pod40X case - fortunately fitting w/o modifications :)   Best Regards, Thorsten.
  9. midiphy-cv-in-4ms-case2.jpg

    From the album TK: midiphy Eurorack CV

    Eurorack modules in 4ms Pod 40X case, 51mm module depth  
  10. midiphy-cv-in-4ms-case1.jpg

    From the album TK: midiphy Eurorack CV

    Eurorack modules in 4ms Pod 40X case, 51mm module depth
  11. Fortunately no problem to support negative values :) Please try this version: Best Regards, Thorsten.
  12. In this particular case you could also "set ^section 2", it should do the same (because ^section 2 follows ^section 1, no jump required) Best Regards, Thorsten.  
  13. Hi, there is currently no way to declare custom variables, but you can use the storage of any unused event instead. E.g. let's say you don't use LED:1000, then just use it to store your value. Best Regards, Thorsten.
  14. As mentioned by Christian, there was no special reason why assigned DIN and DOUT SR #9 to the DIO function. I thought this might be better in case you would like to add more physical SRs in future, no need to change the IDs again until you reach #9. If you don't like this, you could also use SR #3, but not SR #1 or SR #2, because these positions are already allocated by the scan matrix. Btw.: the most simple way to find out the hw_ids is to enter "set debug on" in the MIOS terminal, then trigger the buttons and observe the debug messages in the terminal (doesn't work with LEDs of course, but if you know the button position, you can easily conclude on the LED position) Best Regards, Thorsten. 
  15. Make NG listen to all banks?

    Hi, I'm surprised, all events should listen to incoming MIDI messages, regardless of the bank. Best Regards, Thorsten.