• Content count

  • Joined

  • Last visited

Everything posted by TK.

  1. 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.
  2. 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.
  3. @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.
  4. 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.
  5. 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.
  6. 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.
  7. 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 ;)
  8. 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.
  9. yes Best Regards, Thorsten.
  10. MIDIbox SEQ V4 Release + Feedback

    Track information is stored in the bank files (MBSEQ_B1.V4 .. MBSEQ_B4.V4) in "compressed" binary format. You won't be able to decode them directly. But you could export a track as a preset, this will decode the binary and store in readable (and editable) text format. After edit just import back to take over the modifications Best Regards, Thorsten.
  11. I don't plan to change the theme, because I like it as it is. Please don't expect so many changes from my side - I spend my time to migrate to latest Juce version, that's all. Best Regards, Thorsten,
  12. MIDIbox CV V2 Concept

    (continued from ) It's funny that you ask for this today, because currently I'm planning the "full featured" control surface of the upcoming MIDIbox CV V2 application. In distance to MBCV V1 it uses the MBSID sound engine, optimized for the needs for a CV controller. It features two LFOs, ENV, ARP... per channel! And with a much higher update rate than MBSID V2 (I think that up to 5 kHz can be achieved when all modulators are running in parallel, by disabling modulators even higher frequencies are possible) -> even FM modulation is possible by using two LFOs in "fast" mode /edit: meanwhile the feature list has been enhanced by a second multi-stage ENV2, a modulation and a trigger matrix! The sequencers (bassline/wavetable) will be integrated later, so: they will be available as well of course! Here the current list of parameters: /edit: removed, since it's obsolete! I'm still a bit uncertain how to continue this project, because I think that without a good control surface it won't be usable in practice. The SCS (Standard Control Surface) (2x20 LCD + 4 menu buttons + SHIFT button + encoder) gives access to all parameters, but the usage is too cumbersome. Therefore I thought that I should start with a "virtual control surface" by using Lemur, and once I'm happy with it, I can translate it into hardware. ;) Any additional ideas? E.g. how would your "dream interface" for this project look like? Best Regards, Thorsten.   /edit: meanwhile we've a demo video! :-)  
  13. 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.
  14. MIDIbox SEQ V4 Release + Feedback

    This is what I tested: MIDI menu: Bus1 listens to Bus4 (but All would work as well) and Channel All; Mode: Jam Mixer menu, Page1 (MIDI Port): selected Bus4 In same menu, press SHIFT and GP9 (CC1) - this will allow you to configure the CC numbers sent by CC1 layer Event menu: one layer configured for CC, CC number could be configured but you can also leave it "off" - in this case the incoming CC number will be taken over during recording Enabled Live Record + Live function Back to mixer page #9 (CC1): turn knob to send CC, it should be recorded Best Regards, Thorsten.
  15. MIDIbox SEQ V4 Release + Feedback

    Yes, this is already possible: press MENU+Metronome button Best Regards, Thorsten.
  16. MIDIbox SEQ V4 Release + Feedback

    Good point! Intuitively I would send the CCs from the mixer, but I noticed that the forwarding path to the bus wasn't implemented. It's available now -> try this version: o the MIDI mixer can now send CC values to a bus. This especially allows to record CC changes (configure MENU->MIDI->Port accordingly so that it listens to the bus in Jam mode) Best Regards, Thorsten.
  17. MIDIbox SEQ V4 Release + Feedback

    Hi Jingo, thanks for the compliments! :) Note appears in PA: by default PA plays C-3 on all steps but gate is disabled, therefore you don't see this note. If you enter a note in PE first (intention is that you start with PA), the default C-3 note will be visible in PA. I've to check if this special case could be handled better, on the other hand somebody could have entered this note in PA by intention and wants that it will be played together with the note in PE To the arps: whenever the sequencer is started and no arpeggio pattern has been entered, a C major chord will be played. If you don't want that no notes will be played if no chord is entered, disable the "hold mode" with MENU->Mode, GP9 Best Regards, Thorsten.
  18. MCAN

    Alright, this is now much better to review, I just need to enter "meld branches/mcan trunk" and get a nice graphical diff + merge function. Some first observations: mios32_can.h and mios32_can_midi.h define types which are not in the mios32_* namespace, which could collide with types defined at higher SW layers. Therefore please add the mios32_ postfix to all types which are visible in these header files how to you handle collisions? If two cores send a frame with the same ID concurrently, the arbitration will pass and the remaining frame might collide (e.g. due to different data being sent). The CAN nodes won't automatically re-send the frames. This situation could be avoided if you ensure that each core sends unique IDs, e.g. bring source and destination node into the ID. I guess that you considered this for extended frames, but this format isn't enabled by default... you should do this. mios32_can.h: MIOS32_CAN_VERBOSE should be optional (#ifndef MIOS32_CAN_VERBOSE) and disabled by default you can change the copyright notice to your name (I'm not the creator of this part, you are! :) Best Regards, Thorsten.
  19. MCAN

    First google hit: I just tried: svn copy svn+ssh:// svn+ssh:// it works: You then set MIOS32_PATH to branches/my_activity (resp. the name of your branch directory) instead of trunk Note that this branch looks like a complete copy, but actually it's only a reference on the server, which we will delete once we are happy with the changes and merging has been done. Your changes are still documented in the history. Best Regards, Thorsten.
  20. MCAN

    Hi Bruno, alright, I see... many changes ;) I won't be able to sort this out the next two weeks due to limited time. Would it be possible that you create a minimal update branch until then which is easier to review? This would simplify the work at my side. Once you did this, you could add your local changes again to the official version (they should be taken over separately) Best Regards, Thorsten.
  21. Midibox_ng_manual

    Hi, that's fine! :) The original sources of can be found in the mios subversion repository: You could just send me your edits, and I could upload them. If you (or somebody else) is doing changes more frequently, and don't have access to the repository for direct access yet, I could give permission. Publishing is still in my hands (means: if something is wrong, I would correct it). Best Regards, Thorsten. 
  22. MCAN

    Hi, what has to be done to support MCAN? (at the interface layer...) Best Regards, Thorsten,
  23. Hi Thomasch, I'm not working on it; motivation is low since AU/VST development is so cumbersome and I've the original device... If anybody else has the motivation & programming skills, he is welcome to take over. Best Regards, Thorsten.
  24. In the last weeks I re-implemented the MIDIbox SID sound engines in C, so that it is possible to run MBSID on a STM32 core, but also to emulate it accurately on a Mac or PC. The AU/VST gives you the possibility to try some MBSID patches before building the hardware. The sound isn't so fat like on the original, the filter sounds weak and there are a lot of aliasing effects when higher frequencies are played... but probably you will like it anyhow. The AU/VST is based on Juce, Dag Lem's reSID is used for SID emulation, and the part of my MBSID code is to control the SIDs with the possibilities described in the MIDIbox SID Manual. Download (current version 0.2 from 2014-09-28) AU (for MacOS): (64bit AU which works with Logic Studio 10) VST (for Windows and Linux): Known issues: - only the first preset sound bank with 128 sounds is available. No possibility to access the sound parameters yet. - no access to CCs, NRPNs, SysEx yet This will be added very soon, so that it is possible to automate parameter changes, and to edit complete patches with Rutger's editor (Java), or Nils' editor under Windows - the VST doesn't work with Logic 5.5 under Windows - the AU requires MacOS 10.6 or higher - only 64bit supported anymore - only a single instance can be opened! To support multiple instances it will be required to implement the MBSID code in C++, but this will also increase the memory consumption which is bad for the STM32 build. I will evaluate the separation in classes later. Best Regards, Thorsten. P.S.: big thanks to Philetaylor for building the VST under Windows - it wasn't straightforward!
  25. MIDIbox SEQ V4 Release + Feedback

    Yes, drum labels are stored at the same place which is normally used for track names (a memory limitation...) However, feel free to try this out: o It's now possible to customize the list of labels which are used during track/pattern name and category and drum selection. After booting the new firmware, following files will be created in the /PRESETS folder: TRKLABEL.V4P, TRKCATS.V4P and TRKDRUMS.V4P Edit these files with the MIOS File browser. Uploaded changes are immediately taken over. - TRKLABEL and TRKCATS: are used in MENU->EVNT, "Trk Inst.", "Edit Name" page (Use GP15 to select the Preset) - TRKDRUMS is used on the same page when a drum track is edited (instead of a track name we configure instrument names) Special treatment: TRKDRUMS.V4P also maps MIDI notes to the drum labels. Whenever a new preset drum is selected, the drum note will be changed accordingly. This allows you to fully customize drum maps. The first 16 drums are taken by default whenever a drum track is initialized, and the remaining drums in the list can be optionally selected to replace on of the 16 drum instruments. - TRKLABEL and TRKCATS are also used when a pattern is saved Best Regards, Thorsten.