• Content count

  • Joined

  • Last visited

Everything posted by TK.

  1. Reproducibility proven - great! :) Best Regards, Thorsten.
  2. MIDI over Bluetooth with ESP32

    Was worth a try: I used 200kHz and it works like 20kHz - don't see a big difference on the motor handling itself - but probably in an analog system: 20 kHz: 200kHz: The "noise" that we see here comes from the higher ADC resolution (faders are scanned at 12bit instead of 10bit) and messy ground on my vero board - this should become better with a PCB. But it doesn't impact the smooth movements. Of course, most interesting would be if it works so smooth like your 89MotionN:    At least I see a potential cost benefit ;-) Best Regards, Thorsten.
  3. Midibox Seq 'metronome'

    Hi Tim, there is a metronome function which sends MIDI Notes, by default C#1 on Beat and Measure to Channel #10 of the default port (a GM compatible sound module would output the typical metronome sound). This can be configured at the Options page under 17/33 I think that this is sufficient. By enabling the Audio DAC, MBSEQ would be unnecessarily (over)loaded by outputting the wavestream. There is also not enough RAM available for such a feature (the remaining RAM should be saved for future features) Best Regards, Thorsten.  
  4. MIDI over Bluetooth with ESP32

    At least I know that MacOS and iOS don't allow this. If I take the device with one computer, it appears as "offline" on the other (and vice versa). Seems to be intended, that only a point-to-point connection is allowed. Yes, there should be some kind of meter available, here a link to the driver documentation: Best Regards, Thorsten.
  5. EEPROM get's deleted when too cold??

    Hi Chris, the EEPROM is actually emulated in flash. I would assume: if it gets corrupted, very likely also the application couldn't be booted anymore. It's also very unlikely that the flash gets erased due to this "relaxed" temperature - this can't be the problem. Best Regards, Thorsten.  
  6. Calculating a Roland checksum

    I fixed the link, could you please try again?
  7. understanding the .ngc code

    Just use the MBNG app with this template: It supports the Mackie and Logic Control protocol. Best Regards, Thorsten.
  8. MIDIBox Discord Chat

    The "MIDIbox chat" link works at my side. Best Regards, Thorsten.
  9. Calculating a Roland checksum

    Hi, interesting: they are using a slightly different way to calculate the checksum. Actually "128-remainder" is problematic, because if the remainder is 0, it would result into an invalid value (128 is outside the 7bit range). So, I added ^chk_roland, and it masks the result with 0x7f to ensure that it will be valid. -> Best Regards, Thorsten,
  10. Yamaha YMF825Board (for "Makers")

    Interesting! Unfortunately it seems that there is no support for drum sounds, otherwise it would be a good OPL3 replacement :-/ Best Regards, Thorsten.
  11. MIDI over Bluetooth with ESP32

    Should be possible -> Good progress at my side: I'm now able to control motorfaders, and the accuracy is much better than ever before, because dedicated PWM outputs are used (which are normally intended to fade LEDs), clocked at non-audible 20kHz range. Some work is still required to get it compatible with MBHP_MF_NG, but maybe I can show the difference in 1..2 days via video. My test setup: a NodeMCU hooked on the MBHP_MF_NG board with a quick&dirty adapter board, communicating via Bluetooth (the MIDI sockets are currently not used - unfortunately ESP32 pins are not 5V tolerant) Best Regards, Thorsten.
  12. understanding the .ngc code

    It would be too much effort to provide a 1:1 compliant solution. Would it be sufficient if I provide new markers to address the display, and to set the Y position? (something like ^lcd and ^cursor_y)? Best Regards, Thorsten.
  13. 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.
  14. MIDIBox Discord Chat

    done - have fun! :) Best Regards, Thorsten.
  15. 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.
  16. MIDIbox SEQ V4 Release + Feedback

    @lp1977 MIDI file export should consider this option now, could you please try at your side? -> Best Regards, Thorsten.
  17. 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. 
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. 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.
  23. 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.
  24. 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.
  25. midiphy-cv-in-4ms-case1.jpg

    From the album TK: midiphy Eurorack CV

    Eurorack modules in 4ms Pod 40X case, 51mm module depth