• Content count

  • Joined

  • Last visited

Everything posted by TK.

  1. understanding the .ngc code

    Could you please provide a link to the details? Here an example how text messages can be received and forwarded to a LCD: EVENT_RECEIVER id= 1 \ type=SysEx stream="0xf0 0x11 0x22 0x33 0x44 ^cursor ^txt" A more complex example (defining individual cursor positions) in the Logic Control Template: # LCD Messages # Note: we use ^txt56 instead of ^txt, so that the cursor will jump # to the next line after the 56th character has been reached # Use map=1 to map the cursor positions over a 2x80 LCD EVENT_RECEIVER id= 5 \ type=SysEx stream="0xf0 0x00 0x00 0x66 ^dev 0x12 ^cursor ^txt56" \ range=map1 # X cursor positions are defined in MAP1 # spread message over two 2x40 LCDs MAP1 2 3 4 5 6 7 8 \ 12 13 14 15 16 17 18 \ 22 23 24 25 26 27 28 \ 32 33 34 35 36 37 38 \ 42 43 44 45 46 47 48 \ 52 53 54 55 56 57 58 \ 62 63 64 65 66 67 68 \ 72 73 74 75 76 77 78 If this doesn't work for you, I might add an firmware enhancement - but in this case I need concrete information about the content of the SysEx string. Best Regards, Thorsten.
  2. MIDIBox Discord Chat

    done - have fun! :) Best Regards, Thorsten.
  3. Winter time is DIY time - and this year I decided to explore the capabilities of the ESP32 platform. There might be synergies with MIOS32, but I'm very sure that I won't fully integrate this Microcontroller into the MIOS32 ecosystem --- this hasn't been considered 10 years ago when I started with the 32bit platform, and it would take too much time to make everything compatible (with many compromises - e.g. no native USB support, and we know that this is important for best performance!) However, I think that ESP32 is a pretty good companion device to a STM32F4, hence potential candidate for future MIDIbox enhancements. E.g. the NodeMCU ESP32 available at Reichelt for 10 EUR supports Dual-Core (!) @240 MHz with WiFi and Bluetooth, 512k RAM, 4MB external Flash, incl. USB programmer on PCB - compare this with a PIC18F*! ;-) I started with Bluetooth, and the result can be found here: This so called "BLE MIDI" service should work with any OS which supports this protocol. So far only tested on MacOS and iOS... but it should also work with Linux and Win10. This will be the basis for further experiments at my side - I'm able to communicate with the device via MIOS Studio. :-) (however, application download has to be done with the ESP32 ecosystem - means: the appr. based bootloader) In future also a WiFi connections as demonstrated in Pedalino might be possible, but I'm not there yet - focus is on the application itself, knowing that the MIDI interface options won't be so fast like known from the STM32F4 based platform. E.g. how accurate can we control a Motorfader with the PWM LED outputs of a ESP32?  If it works, it could be connected like a MBHP_MF_NG module via traditional UART based MIDI to a MIDIbox NG. And will it be possible to control a SRIO chain? Might be interesting for a future BLM16x16+X with (only) optional WiFi and Bluetooth connects. Best Regards, Thorsten.
  4. MIDI over Bluetooth with ESP32

    No, I won't have the time for a fully adaption to MIOS32, especially considering incompatibilities, missing resources and last but not least, potential additional user support which I can't give thereafter. And concerning bootloader: the native solution of the ESP32 ecosystem is working well, no real need for an adaption. Therefore I provide the projects "as is" and independent from MIOS32 - but you will find some things known from MIOS32 later, and the projects will be somehow integrated into the MIDIbox platform - but please don't expect so much "flawless compatibility" that we know from MBHP_CORE_STM32/MBHP_CORE_LPC17/MBHP_CORE_STM32F4... Times have changed, today powerful DIY platforms are already available, so that it makes sense to adapt to the workflow of the corresponding users - I'm flexible and see the possibility to reduce efforts at my side ;-) Best Regards, Thorsten.
  5. 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.
  6. MIDIbox SEQ V4 Release + Feedback

    @lp1977 MIDI file export should consider this option now, could you please try at your side? -> Best Regards, Thorsten.
  7. understanding the .ngc code

    Hi, finally found time to go through this thread... ;-) First of all: the SysEx string contains an "illegal" value: 0xE0 Values >= 80 should not be sent, because they will be interpreted as a new MIDI status. Second: you could simply toggle between the two values 0x10 and 0x01, and insert it into the SysEx string via ^val: EVENT_BUTTON id=1 range=0x10:0x01 button_mode=toggle type=SysEx stream="0xf0 0x00 0x01 0x16 0x10 0x18 ^val 0xf7" Best Regards, Thorsten. 
  8. MIDIbox SEQ V4 Release + Feedback

    @lp1977thanks for the information! Problems are understood and fixed in: @sis.tmjust tried at my side, it works! (and sometimes I'm surprised what can be done without special consideration in the sources ;-) assign track to CV in LFO page, set the ExtraCC# to 16..23 16 will send to CV channel #1, 17 to channel #2, etc - which means: with the CC number you can address the CV channel you would like to use as LFO output Best Regards, Thorsten.
  9. Hi *, this thread informs you about the latest release, and gives you the possibility to write down your feedback (bug reports, questions about existing features, suggestions for new features, etc...) MIDIbox NG is in beta state! Not all planned features are implemented, but the existing functions should (hopefully) work stable. The latest build for MBHP_CORE_STM32 and MBHP_CORE_LPC17 can be downloaded at: -> List of planned/implemented features (press refresh button in your webbrowser to display the latest state): -> Documentation (in progress): Hardware LCD Hardware First Steps .NGC Configuration File .NGL Configuration File .NGR Configuration File Standard Control Surface The complete Documentation ;-) Best Regards, Thorsten.
  10. 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.
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. midiphy-cv-in-4ms-case1.jpg

    From the album TK: midiphy Eurorack CV

    Eurorack modules in 4ms Pod 40X case, 51mm module depth
  16. 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.  
  17. 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.
  18. 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.
  19. 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.
  20. 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. 
  21. midiphy Eurorack Expander Modules

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

    From the album TK: midiphy Eurorack CV

    Eurorack modules in 4ms Pod 40X case, 51mm module depth  
  23. Fortunately no problem to support negative values :) Please try this version: Best Regards, Thorsten.
  24. 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.  
  25. 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.