• 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. Adding CS-line to AINSER8

    Additional notes: could be that you rely on 5V output - in this case change MIOS32_BOARD_PIN_MODE_OUTPUT_PP to MIOS32_BOARD_PIN_MODE_OUTPUT_OD, and add a 1k pull-up to 5V to this pin. And if J10A is already used for SCS inputs (standard), just take J10B.D0 (pin index #8) Best Regards, Thorsten.
  3. Adding CS-line to AINSER8

    Another modification in mbng_file_c.c is required where the number of CS lines is hardcoded (actually you should have seen the error message...) I put an example which works at my side into the demo/mbng_ainser_with_3_cs branch, see: Best Regards, Thorsten.  
  4. Adding CS-line to AINSER8

    You don't need to enhance mios32_spi, just control the additional pin directly from AINSER_SetCs E.g. let's assume that J10.D0 is unused so far, then add to AINSER_Init(): MIOS32_BOARD_J10A_PinInit(0, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); and to AINSER_SetCs: case 2: return MIOS32_BOARD_J10_PinSet(0, value); Best Regards, Thorsten.
  5. MIDIbox SEQ V4 Release + Feedback

    Unfortunately there is currently no way without a duplicated track. Background: the sequencer engine handles tracks which are sending to an internal bus (so called "loopback tracks") differently compared to common tracks: they are processed before MIDI events of "common tracks" are scheduled to ensure that transposers/arpeggiators get updated before they play the next note independent from the track order they have no timing information - MIDI notes directly processed without delay, note off, echo, etc that's also the reason why the "Duplicate" Fx doesn't allow to route MIDI events to Bus1..4 This approach solved many problems that we noticed in earlier MBSEQ versions (V1..V3), but it has the drawback that loopback tracks can't be used for sending "common MIDI events" anymore. Best Regards, Thorsten.
  6. MCAN

    Hi Bruno, yes, just try it and commit your change in a special branch (from master) - we can merge once we both are satisfied. By searching for defines like MIOS32_SYS_ADDR_SPI_MIDI (e.g. via "grep --rec") you can find the places which need to be modified. Best Regards, Thorsten.
  7. mb6582 fan.... Am I mad to unplug it?

    I unplugged the fan power cable at the same day I got my MB6582 from Wilba, and this never caused a problem ;-) Best Regards, Thorsten.
  8. MCAN

    Which values would you like to permanently store & change in the bootloader. I need names + sizes I will define those values in mios32_sys.h within the MIOS32_SYS_ADDR_BSL_INFO_BEGIN section -> As you can see, we can either define a block + confirmation value, or individual values + confirm. If you could predict today how many bytes need to be allocated, we could use a single confirmation which saves space for other future extensions (used for other purposes) Best Regards, Thorsten.
  9. MIDIbox SEQ V4 Release + Feedback

    Hi Peter, I'm resistent on this feature, because it will dramatically increase the CPU time and RAM consumption. We've up to 256 layers which could send CCs, and we would have to determine the target value when the start CC is played - means, we've to walk the steps until the next CC is found for each layer, this will consume some uS for each layer! The next CC could change while the sequencer is playing, this leads to special treatments at some places... In RAM we've to store the current, target and sent values for each layer, resulting into 3 * 256 bytes Best Regards, Thorsten. 
  10. MCAN

    We could reserve a bootloader location to make this basic_node number configurable without touching the source code. Similar the way I did for other "permanent" flags & values. Best Regards, Thorsten.
  11. MIDI Implemtation for EUCON

    Reverse engineering a protocol for private purposes is one thing, publishing the information another. In any case: please don't publish any specific information about this protocol in this forum, this could bring me (as the forum owner) into serious legal issues! Best Regards, Thorsten. P.S.: I haven't looked into this protocol because I don't like the license. Anything which can't be openly published isn't interesting for my projects.
  12. It's unclear if I should really spend some more time to work on this. If I understood @weasel correctly, he sees a path via Arduino based solutions which he would prefer. In this case my contribution wouldn't add any value... just follow him. Best Regards, Thorsten.
  13. Impressive work! The WS2812 driver was only a quick hack, I was already satisfied after it was working and haven't expected that somebody would ever drive more than 50..100 LEDs. It shouldn't be a big deal to optimize the memory consumption. There are various places in MIOS32 where I already used DMA double buffers (e.g. I2S audio output). Nothing needs to be explored, just translation :) Best Regards, Thorsten.
  14. Yes, each RGB LED will consume 48 bytes. With the latest changes up to 390 RGB LEDs can be defined, and you will get a proper RAM error message if there are too much, such as: /opt/gcc-arm-none-eabi-4_7-2013q3/bin/../lib/gcc/arm-none-eabi/4.7.4/../../../../arm-none-eabi/bin/ld: project_build/project.elf section `.bss' will not fit in region `RAM' /opt/gcc-arm-none-eabi-4_7-2013q3/bin/../lib/gcc/arm-none-eabi/4.7.4/../../../../arm-none-eabi/bin/ld: region `RAM' overflowed by 424 bytes collect2: error: ld returned 1 exit status Best Regards, Thorsten.
  15. Hi, STM32F4 was running out of memory - and due to an wrong linker file entry you haven't got an error after the 128k boundary of the "normal RAM" has been touched. However, this chip has some additional 64k as a so called "core coupled memory", which is located at 0x10000000 I changed the linker file and preload code to support this memory. In addition, in the MBNG application I moved the heap memory into this CCMRAM, giving us about 10k more space. Updates are available at github: I havent't checked if this has a new negative side effect, but at least MBNG is booting and RGB LEDs are working Best Regards, Thorsten.  
  16. MIDIbox KB

    This is a placeholder for the upcoming MIDIbox KB project. It's work in progress, some initial documentation can be found under It started in the one Fatar keyboard has already been successfully midified, some other (different types) will follow. :) If you've questions or suggestions for enhancements, just post them here. :) Best Regards, Thorsten.
  17. 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.
  18. MIDIbox SID Walkthrough

    The collection of problems reported in the last weeks, and the appr. solutions, can now be found here: This is a living document which will be enhanced in future Please let me know, if an important hint is missing Best Regards, Thorsten.
  19. MIDIbox SEQ V4 Release + Feedback

    Source code is here: Beat Light is controlled in src/seq_ui.c: (search for BEAT) The problem is understood - it appears on frontpanels with single colour LEDs (MEASURE not assigned).  However, a quick fix is easy: just replace SEQ_LED_PinSet(seq_hwcfg_led.beat, (seq_hwcfg_led.measure && measure_led_on) ? 0 : beat_led_on); by if( seq_hwcfg_led.measure != 0xffff ) SEQ_LED_PinSet(seq_hwcfg_led.beat, (seq_hwcfg_led.measure && measure_led_on) ? 0 : beat_led_on); else SEQ_LED_PinSet(seq_hwcfg_led.beat, beat_led_on); Untested code Please let me know if it works, so that I will bring it into the repo   Concerning mirrored Roll parameter: that's normal if the parameter layer is only 16 steps. It's due to a memory limitation - drum tracks can only store 1024 parameters, and they are partitioned over the number of drum tracks and parameter layers Best Regards, Thorsten.
  20. The workflow can be much easier: just clone the worktree, create a branch, commit into this branch how often you want, push to GitHub whenever you want to ensure that your work doesn't get lost (and want that other people can access your changes). There are various tools to display code changes between branches, between your commit, etc. also locally without the need for a webserver. E.g. I'm using "gitk", but there might be many others. But uploading to GitHub is preferred - not only for backup reasons, but also to allow later merging into master branch via pull request + review from my side. Best Regards, Thorsten.
  21. Hi, actually environment variables are "local" in your shell. Which means, if you open multiple shells you can set the variables to different values in order to work on multiple projects in parallel. Build objects are created locally in your app folder as well. Or you could create a small shell script which sets the variables before calling "make" - this way you could work from a single terminal. Or you quickly switch between the setups by sourcing one of the "source_me_*" files in the base directory: Of course, it's also possible to create different GIT clones which makes sense if you work in separate branches for each activity. Best Regards, Thorsten.
  22. Hi *, The MIOS repositories are now hosted at Github: This should improve collaboration in future, because branching in GIT is much easier. It's not possible to access the old subversion repositories via SSH anymore, in future changes can only be pushed into the new GIT repositories. There are tons of documentation how to use GIT on the web, therefore I won't repeat this here. ;) Just want to mention the general workflow: we use a simplified workflow without develop branch, so: master is the latest everybody who want's to contribute has to create a feature branch, e.g. feature/my_project once you are fine with your changes, create a pull request from your branch into master, and set me as a reviewer I will review your changes, and if they are fine I will integrate them into master meanwhile everybody is able to work with your changes by switching to your feature branch Currently we've only one branch: feature/mcan (from Bruno) How to contribute: create a github account (if you don't already have one) register your SSH key in the profile inform me about your account name so that I can add it to the midibox project now you can clone the repository with git clone ssh:// Within this repository you can create a branch with: git checkout master -b feature/<your-branch-name> You can commit changes with git commit . resp. "git commit" if you've indexed the files with "git add" before You can push committed changes to github with git push If you are working from a fresh clone, use "git checkout feature/<name>" to select your feature branch With "git branch -a" you will get an overview about the branches. There are also various GUIs available to display changes in your local repository, e.g. I prefer "gitk" Best Regards, Thorsten. P.S.: Wiki and ucapps documentation will be updated in some weeks once the new workflow is settled ;)
  23. 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.
  24. Hi, just would like to let you know, that I started to migrate MIOS Studio to the latest Juce version (5.4.3) - previously we used a pretty old one (I even don't remember the version number) which doesn't work properly with newer OS versions such as Windows 10. The hope is, that the update will solve these issues - if not we had no luck (I won't spend much debug effort there...) Best Regards, Thorsten.
  25. @Digineuralthanks for the info! I've to explore Dockerfile, it promises high potential :) @Phatlineunfortunately I don't understand the problem, I haven't provided the package as a "rar" file, and the binary works with various Linux installations that I tried so far. There seems to be something wrong with your OS installation (maybe you are using an expert system?), but I fear that I can't give you more hints. @Elektruckas long as you are the only Win10 user who has this problem with SD Card uploads I won't start to analyze this. MIOS Studio 2.4.8 is released now @ - let's see if additional users report problems; the legacy 2.4.6 files are still accessible from the same page to ensure that nobody is blocked by the progress (only 64bit systems supported anymore) Best Regards, Thorsten.