• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral


About TK.

  • Rank
    MIDIbox Guru
  • Birthday 11/17/1972

Contact Methods

  • Website URL

Profile Information

  • Gender Not Telling
  • Location Germany
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.  
  7. 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.
  8. 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.
  9. 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.
  10. @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.
  11. Yes, 64bit only. The MacOS build should show the same functionality and robustness like 2.4.6, therefore you won't miss anything on your older computer :) Best Regards, Thorsten.
  12. MIDIbox SEQ V4 Release + Feedback

    You can achieve similar things with the duplication Fx, see (search for Fx Dupl) It isn't so flexible like this app, but at least you can define the number of channels (= voices) + the first channel. Either select alternate or random channel mode. Works also well with echo Fx btw :) -> mbseqv4_demo_dupl_fx.mp3 Best Regards, Thorsten.
  13. This was a long journey - jumping between three computers to ensure a consistent reproducible build state in the repository (which is now hosted at Github) Please try: MacOS: Linux: Win10 64bit: Best Regards, Thorsten.
  14. yes Best Regards, Thorsten.
  15. 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 ;)