• Content count

  • Joined

  • Last visited

Everything posted by TK.

  1. Happy birthday to...

    Thank you! :) I'm too busy at this moment, but will have much more time for MIDIbox in December :) Best Regardsm Thorsten.
  2. Hi *, this thread informs you about the latest release, and it gives you the possibility to write down your feedback (bug reports, questions about existing features, suggestions for new features, etc...) The current MBSEQ V4 release can be downloaded from Please read the CHANGELOG.txt for latest changes Documentation: IntroductionHardwareFrontpanelInstallationTutorialsMenu PagesSessions16x16+X Button/LED MatrixOSC OptionV3->V4 UpgradeFirst Steps (not ready yet)Known issues and Troubeshooting tips (no known issues yet ;))  Best Regards, Thorsten.
  3. MIDIbox SEQ V4Lite

    This is a sneak preview of the upcoming MIDIbox SEQ V4 Lite, a new project which I'm developing together with Christian aka. CD Picture of the prototype (built by Christian): We are planning to create a PCB for the button/LED matrix, and a Ponoko-like case! :) Feature list: minimalized user interface without LCD. Buttons and LEDs are directly connected to the MBHP_CORE_LPC17 module (no DIN/DOUT modules required) 64 LEDs and 48 buttons reduced feature set, optimized for live/step recording -> MIDI Looper each function has a dedicated button only two sequences are available, you can alternate between these sequences, or play both together. it's also possible to enter a new sequence while another sequence is playing sequences have to be entered with an external keyboard in realtime or with the step recording function a sequence consists of up to 64 steps for notes - up to 16 note/velocity/length values can be stored per step (16 note polyphony) CCs and Pitchbender are recorded as well with 4x step resolution (64th) sequence length can be set from 1..64 steps (also uneven lengths are supported) note transpose via keyboard layers are auto assigned on incoming CCs, up to 19 CCs layers can be recorded into a sequence MIDI events are sent via MIDI, USB, OSC (ethernet) and optionally also via CV (AOUT/AOUT_LC/AOUT_NG) MIDI clock as Master or Slave; Tap Tempo function Copy/Paste/Clear/Undo function sequences can be stored/restored on/from SD Card Sounds like a simple sequencer project, but now the special gimmicks which are possible thanks to the mighty MBSEQ V4 engine which is running in background. :) On the recorded sequence, following effects can be applied: step progression parameters (steps forward/backward, repeat, skip, interval) Groove templates (step delay/velocity/note length changes) e.g. for Shuffle, Swing, velocity modulations, etc... Echo Effects (!!!) Humanizer (randomization of MIDI events) different LFO effects on Note Pitch, Velocity, CC values Force to Scale with selectable root note Effects are stored as presets (important for live usage), and can be changed by editing configuration files on SD Card. The firmware is almost ready, but we will need some time for optimizing (while using it) to make it perfect! :) /edit: Video: /edit2: Vimeo Link (much better audio quality!!!): /edit3: prototype PCB is ready! :) More pictures later in this thread. /edit4: prebuilt binary now available under /edit5: project has been officially release; project page: Best Regards, Thorsten.
  4. 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.
  5. 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.
  6. The Ctrlr based panel for MBSID V2 is up&running, and I must say that it was really a challenge! But at the end it was less effort than programming this editor as a native Juce application because Lua scripting is sufficient (and fun!) - and we will get AU and VST support for free! The panel can be downloaded from this location:   Ctrlr can be downloaded from I tested this with Ctrlr_262f2710.dmg (version from 14. April 2014) under MacOS For Windows take Ctrlr_ac6a3185.exe edit hawkeye (in 2018): here is a current link to Ctrlr_ac6a3185.exe (needed for TK.'s panel) - thanks to goyousalukis for searching!   Some snapshots: Lead Engine OSCs: Bassline Engine OSCs: Bassline Sequencer: Drum Engine instruments: Drum Sequencer: Multi Engine: Release mail (with some technical background) to the Ctrlr community: Have fun! Best Regards, Thorsten.
  7. midiphy-cv-in-4ms-case1.jpg

    From the album TK: midiphy Eurorack CV

    Eurorack modules in 4ms Pod 40X case, 51mm module depth
  8. 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.  
  9. 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.
  10. 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.
  11. 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.
  12. 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. 
  13. midiphy Eurorack Expander Modules

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

    From the album TK: midiphy Eurorack CV

    Eurorack modules in 4ms Pod 40X case, 51mm module depth  
  15. Fortunately no problem to support negative values :) Please try this version: Best Regards, Thorsten.
  16. 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.  
  17. 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.
  18. 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. 
  19. 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.
  20. Yes, there is a conflict with the shift register assignments. Try this one: # now enable DIOs (0 = input / 1 = output) DIO port=J5AB emu_din_sr=9 emu_dout_sr=9 output_mask=01010000 # button events (DIN SR1 pins are assigned to hw_id=65/67) EVENT_BUTTON id=65 hw_id=65 type=CC chn=1 cc=16 range=0:127 fwd_id=LED:66 EVENT_BUTTON id=67 hw_id=67 type=CC chn=1 cc=17 range=0:127 fwd_id=LED:68 #EVENT_BUTTON id=65 hw_id=65 type=Meta meta=RunSection:1 button_mode=OnOnly #EVENT_BUTTON id=67 hw_id=67 type=Meta meta=RunSection:2 button_mode=OnOnly # LED events (DOUT SR1 pins are assigned to hw_id=66/68) EVENT_LED id=66 hw_id=66 type=CC chn=1 cc=16 range=0:127 EVENT_LED id=68 hw_id=68 type=CC chn=1 cc=17 range=0:127 Best Regards, Thorsten.
  21. Could you please post your complete .NGC and .NGR file? I will check it tomorrow... Best Regards, Thorsten.
  22. No, don't worry, outputs are protected against shorts internally. Just tried your configuration, it works after changing fwd_id=LED:3 to fwd_id=LED:2 (we always forward to a hw_id) RESET_HW # J5A PORT SETUP # J5.A0 -> octave up switch # J5.A1 -> octave up LED # J5.A2 -> octave down switch # J5.A3 -> octave down LED # now enable DIOs (0 = input / 1 = output) DIO port=J5AB emu_din_sr=1 emu_dout_sr=1 output_mask=01010000 # button events (DIN SR1 pins are assigned to hw_id=1/3) EVENT_BUTTON id=1 hw_id=1 type=CC chn=1 cc=16 range=0:127 fwd_id=LED:2 EVENT_BUTTON id=2 hw_id=3 type=CC chn=1 cc=17 range=0:127 fwd_id=LED:4 # LED events (DOUT SR1 pins are assigned to hw_id=2/4) EVENT_LED id=3 hw_id=2 type=CC chn=1 cc=16 range=0:127 EVENT_LED id=4 hw_id=4 type=CC chn=1 cc=17 range=0:127 As you can see, I also added "RESET_HW" to ensure that previous settings are undone. The LEDs shouldn't be dimmed. Best Regards, Thorsten.
  23. Trigger Outs - 4ms

    Pulse widths up to 10 mS are now supported, could be nice if you could try it out: Best Regards, Thorsten.
  24. MIDIbox SEQ V4 Release + Feedback

    Based on my experiences with MB808 the trigger width is crucial, therefore I can fully understand Andrews request that a digital option is desired. The "pipeline based approach" is working fine, we can now adjust the width from 0 (=off -> gate function) to 10 mS o DOUT_1MS_TRIGGER in the MBSEQ_HW.V4 file has been replaced by a configurable trigger width which can be adjusted in the CV Configuration Page with GP13 now -> It would be great if everybody could help to test this new firmware version, regardless if the new CV features are used or not (I hope that nothing else is broken!) I would like to create a final v4_096 release, because v4_095 is from last december, and it started to smell! ;-) Best Regards, Thorsten.
  25. MIDIbox SEQ V4 Release + Feedback

    Update to the 1ms delay: I could "pipeline" the triggers, this way we could get a cheap pulse stretcher. Is there the need for more than 4 mS (= 3 pipeline stages)? Best Regards, Thorsten.