• Content count

  • Joined

  • Last visited

Everything posted by TK.

  1. 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.
  2. MIDIbox SEQ V4 Release + Feedback

    You are right, it would be better to make this function optional. Please try this version: It's switch #9/29 in the options page Best Regards, Thorsten.
  3. MBBLM on iPad via Lemur

    Today I got my first experiences with Lemur for iPad and I must say that this software is really a master piece! :) In distance to TouchOSC the controllers are fully programmable with an easy to learn script language. And in distance to OSC it's also possible to work with MIDI at low-level -> means: at bit basis (e.g. a MBSID Editor is feasible)! :) Within a couple of hours I was able to implement a complete BLM16x16+X emulation: The user interface feels much better than the Juce implementation, and due to the easy to use Lemur Editor it's possible for everybody to customize the user interface! :) So, if you own an iPad, and already bought Lemur, just install this template: Thereafter start the Lemur Daemon for a MIDI<->OSC connection, and on MBSEQV4 configure the BLM port (MIDI->Misc page) E.g. to USB3 like I did... This MIDI port can be select in Lemur as well: Now you are ready for having some Multitouch BLM fun! :) Best Regards, Thorsten.
  4. midiphy SEQ v4+

    Wow!  Best Regards, Thorsten.
  5. This was a nice challenge for the weekend: I implemented a driver for USB MIDI Host mode into MIOS32 for STM32F4 :smile: (LPC17 and STM32F103 don't support USB Host mode...)   Tested with following devices: CME X-Key: Waldorf Blofeld: MIDIbox (here MIDIbox SEQ V4L): Ploytec GM5x5x5 USB MIDI Host mode just replaces USB MIDI Device mode via the USB OTG socket. The update will be available with all future MIOS32 applications, it's always available without special configuration. A special USB Micro-B -> USB 2.0-A adapter is required to connect the MIDI device.   Such an adapter is for example available at Reichelt (DELOCK 83183) for 5 EUR:   Pluck this adapter into the Micro-USB socket of the STM32F4-Discovery board, reset (or power-cycle) the core, and MIOS32 will automatically switch to USB Host mode.     Limitations: - USB hubs are not supported, the MIDI device has to be connected directly. - USB based Power-Supply is weak (limited to ca. 200..300 mA), which means that it might be required to power the MIDI Device with an external PSU - the MBHP_CORE_STM32F4 module has to be powered from the USB debug socket   Please let me know if you are interested to beta-test this enhancement, I could provide a preliminary version of a MIOS32 application.   Best Regards, Thorsten
  6. Wow! I'm impressed!!! :) Best Regards, Thorsten.
  7. MIDIbox SEQ V4 Release + Feedback

    Development Queue overflow... %-) Your input won't get lost, but I think that I've to consolidate the ideas and request if still valid based on my proposals once I find the time to think about the implementation... @Rio: thanks! :) @beautyofdecay_ I added an experimental AOUT calibration feature:   o V4+ AOUT: support for AOUT channel calibration. In the CV configuration menu, turn GP ENC #7 until 0V/1V/2V/.../Max will be visible. Calibrate the offset of the target value with ENC #8. Each V has a dedicated calibration value which can be configured this way, the output will be interpolated accordingly. Note that with exiting the CV configuration menu the calibration values are stored on SD Card in the MBSEQ_GC.V4 file (-> CV_Cali <cv-counting-from-0>). You could backup/set/restore the values from there if required. To reset all calibration values: delete all CV_Cali items in MBSEQ_GC.V4, store the file and enter "reset" in MIOS terminal. Please try this version: Does it work at your side? Best Regards, Thorsten.
  8. MIDIbox SEQ V4 Release + Feedback

    The MIDIbox NG application has such an interpolation routine which could be re-used for calibration purposes in MBSEQ. However, I'm a bit surprised that a SW based calibration is required. Which AOUT module are you using? And how big is the deviation compared to the ideal curve within the 1V segments? 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. The octave enumeration isn't standardized. E.g. in Logic Studio 0x18 is C0, and as far as I remember, you can configure MIDI-Ox to print the same. No need to change (or to add an option) at my side. Best Regards, Thorsten.
  11. Really well done Peter and Andy! For me it's always a great honor when people pick up the MIOS32 code basis, and make something new out of it. Especially when it's useful for myself - I definitely need one! :) Best Regards, Thorsten.
  12. A solution will be available with v4.095 (changes are already in the repository): o OPTIONS page: new option "Print and Modify Steps w/o changing Gate". If enabled: note values will always be print regardless if they are played or not. Changing a note value won't automatically enable the gate Best Regards, Thorsten.
  13. Core32F4 J5a Encoder

    Just got a flashback: this is actually a known issue and I thought that I fixed this some years ago... somehow the change didn't find it's way into the repository. I updated mios32/LPC17xx/mios32_board.c, please update your repository Best Regards, Thorsten.
  14. MIDIbox SID V2 Patches

    I uploaded some bassline patches of "TK2 soundbank" that I created the last years, but never released (want to archive them :) Some demos (6 of 28 basslines): Best Regards, Thorsten.
  15. MIDIbox SID V2 Patches

    Followup to   Attached some bassline patches that I found on my second Bankstick. You already know the first ones from the remaining three ones were not published yet.   Some short demos: direkt link, 13 MB (feedback pot used on all patches, external Fx and EQs have been added to the audio path)   Update 2018-05-01: some new patches now released in SVN repository: Some demos:   Please add your own patches to this thread, regardless if Lead, Bassline, Drum or Multi A MP3 which demonstrates the patches is nice to have, but no must!   Best Regards, Thorsten.
  16. Interesting! If there is really a file limit, it could make sense to change the application so that it uses a dedicated directory for each bank Best Regards, Thorsten.
  17. connect mbhp_mf_ng directly to core32?

    There are good reasons why I decided to use an UART based MIDI interface for interconnections: universal approach, easy to setup from a (PC) and easy to connect to other cores MIDI messages are buffered via FIFOs, this relaxes the MIOS32 application requirement. E.g. it could prioritize the handling of other tasks and doesn't need to frequently poll for incoming messages to avoid information loss. By default the FIFOs are dimensioned with 64bytes, which means that we can bridge up to 20 mS no need to program special interface communication handlers -> less troublesome & no special knowledge required MIDI cable can be up to 10m optocouplers decouple the noisy MF voltage from the MIOS32 core, this improves EMC level-shifting 3.3V to 5V part of the physical MIDI interface So, if you are searching for alternative interfaces, they all have cons you have to learn how to program such interfaces. I won't have so much time to help you on this... you've to find your own way the MBNB_MF_NG firmware is programmed in assembly language which is difficult to enhance for people who never did this before all IO pins of the MBHP_MF_NG module are allocated, for a different interface you've not only program a new firmware, you also have to change the circuit Possible interfaces: SPI Cons: no programming example available for MIOS8 requires 4 IO pins (RC3, RC4, RC5, RA5) MBHP_MF_NG circuit has to be modified. But especially RA5 does hurt, since this is an analog input (actually a killer argument) no programming via MIDI possible anymore, you've to use a PIC programmer instead actually more valuable than MIDI ports, since only 3 SPI interface ports exist on a typical MIOS32 core. One (J8/9) is allocated for SRIO, another one (J16) for SD Card and Ethernet at 3.3V level, another one (J19) is free, but typically used for AOUT/AINSER, etc... However, if SPI, than you would either have to sacrifice J8/9 (-> no SRIO), or J19 (-> probably unusued in your application? But couldn't be used for all applications, so: only a dedicated solution for your purposes) MIOS32 core has to frequently service the SPI to avoid message loss programming will be much more complicated I2C Cons:  requires 2 IO pins (RC3, RC4) MBHP_MF_NG circuit has to be modified no programming via MIDI possible anymore, you've to use a PIC programmer instead MIOS32 core has to frequently service the I2C I2C overhead higher than for other interfaces, will slow down your application and/or result into message loss programming will be much more complicated CAN Cons: requires different PIC chip (e.g. PIC18F4685) requires 2 IO pins (RB2, RB3) MBHP_MF_NG circuit has to be modified MIOS32 core has to frequently service the CAN interface. Similar to I2C and SPI there is a high risk for message loss if this isn't done frequently programming will be most complicated compared to other interfaces Best Regards, Thorsten.
  18. Midibox Drum Sequencer

    Finally!!! :) I will look into the velocity issue soon The board that I built some years ago is still functional and I typically show it to MIDIbox HQ visitors as one of the unknown projects that the community started but never released :) Best Regards, Thorsten.
  19. MIDIbox SEQ V4 Release + Feedback

    @Rio: please try this version: o OPTIONS page: new option "Print Notes with transposed value". Enabled by default (due to change in V4.093), can be optionally disabled now. @goyousalukis works fine for me. Could you please check if TrgA is disabled? Use GP9 to scroll the page until TrgA get's visible. Then turn off the value to -- Best Regards, Thorsten.
  20. This was a translation error in the code, it's fixed now (and enhanced by a new feature! :) o AOUT: Channel 9..12/13..15 now set the gate pins #1/3/5/7 as documented (previously it was #1/2/3/4 due to a code translation error) New: gate pins #2/4/6/8 are now set whenever the velocity is >100. This way the pins can be used as an accent trigger Best Regards, Thorsten.
  21. This is a very clever idea, thanks for this!!  For those who want to try it out - it's now available in following preliminary release: o AOUT: Channel 9..12/13..15 now set the gate pins #1/3/5/7 as documented (previously it was #1/2/3/4 due to a code translation error) New: gate pins #2/4/6/8 are now set whenever the velocity is >100. This way the pins can be used as an accent trigger Best Regards, Thorsten.
  22. LoopA v2 prototype

    Well done! Nice entry project for people who want to check their SMD soldering skills before trying the new MBSEQ frontpanel. Best Regards, Thorsten.
  23. MIDIbox SEQ V4 Release + Feedback

    Will add an option for transpose value display and check the reported issue soon Best Regards, Thorsten.
  24. Seq V4 for the visually impaired

    Hi, concerning the displays: I remember that I added an option for 4 LCDs to the firmware for somebody who had 2x20 LCD modules which were bigger than the common ones: Picture was created 2010, not sure if such displays still exist Best Regards, Thorsten.
  25. In the last days I worked on a major MBHP_MF update, mainly triggered by Screaming Rabbit who gave me a big package of different Alps faders for free! :) Design Targets: find a solution to handle high-quality faders like Alps K faders with "coreless" motors find a solution for MBHP_CORE_LPC17 which doesn't deliver stable enough ADC conversion results due to the reduced 3.3V voltage range find a solution for MBHP_CORE_LPC17 which cannot handle touch sensors properly without heavy CPU load (resp. without an additional external device or microcontroller) find a solution which is compatible with PIC based projects for best usability find a solution which is DIY friendly and doesn't require additional gear (e.g. chip programmer) for something which isn't part of the MBHP yet find a solution which can be easily tested and troubleshooted (no need to learn new processes) Following circuit is the result: a dedicated PIC controller controls the motorfaders directly it can be accessed via MIDI (only) - this allows standalone usage, cascading (to chain multiple modules), and the re-use of existing infrastructure such as MIOS, MIOS Studio and MIOS Bootloader the module can either be connected to a PC directly, or controlled from a second PIC or STM32 or LPC17 (note that MBHP_CORE_LPC17 has a third and even a fourth MIDI IO port at TTL level so that the available two MIDI IO pairs are still free) native support of various protocols (e.g. PitchBender, CCs, even Logic Control and Mackie Control Emulation) support for 8 touch sensors instead of TC4427 I'm using L293D now - not at least because of the integrated diodes. due to the direct motor control connections, the PIC is now able to generate PWM with 50 uS steps for improved motor speed control while a motor is moved since the firmware is dedicated for this task, there was enough memory free to integrate advanced features, such as runtime-calibration and motor position tracing Two snapshots of the prototype - currently I've only tested the circuit with high-quality K Faders, which were not properly controllable with MBHP_MF_V1 Meanwhile PCBs are available (layout created by SmashTV - thank you!!! :) ) MIOS Studio got a new configuration tool: Especially the calibration is much easier now, not at least because of the new motor position tracing feature: Currently following modes are planned: [*] PitchBender Chn#1..#8 [*] PitchBender Chn#9..#16 [*] CC#07 Chn#1..#8 [*] CC#07 Chn#9..#16 [*] CC#16..#23 Chn#1 [*] CC#24..#31 Chn#1 [*] Faked Logic Control [*] Faked Logic Control Extension [*] Faked Mackie Control [*] Faked Mackie Control Extension There is no real need to add more modes, considered that MIDI events can be mapped on the host PC and/or from another microcontroller (like Core32) which uses MBHP_MF_V3 as a companion. By using Pitchbender events, the highest resolution (10bit) is available. More about this topic (e.g. test of different motorfaders) after holidays. :) Best Regards, Thorsten.