• Content count

  • Joined

  • Last visited

Everything posted by TK.

  1. MIDIbox SEQ V4 Release + Feedback

    Yes, this is already possible: press MENU+Metronome button Best Regards, Thorsten.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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. 
  8. MCAN

    Hi, what has to be done to support MCAN? (at the interface layer...) Best Regards, Thorsten,
  9. 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.
  10. 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!
  11. 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.
  12. MIDIbox SEQ V4 Release + Feedback

    Yes, it's well hidden ;) I just remember that I wanted to make the "preset labels" configurable, so that they can be selected from a list stored in a file (so that users can define their own labels without changing the firmware). Will work in this later today... Best Regards, Thorsten.
  13. MIDIbox SEQ V4 Release + Feedback

    Yes, this is already possible: MENU->Event, press GP8 ("Track Instrument") At the right side you can edit the track name (and category) Once you gave the track a name, it will be displayed on the edit screen instead of MIDI channel and port Best Regards, Thorsten.
  14. The first demo with the final midiphy MBSEQ V4+ design - the melody is recycled and re-arranged from an older (10 years old) demo; somehow I was in that mood ;-) Best Regards, Thorsten.
  15. Config File - Assigning F1~F4 b uttons

    Hi Andrew, these button assignments don't exist, you should get an error message while the file is read (btw.: no need to reset the device, the file will be parsed automatically after upload). You could assign F1..F4 to BUTTON_DIRECT_BOOKMARK1 .. 4 instead. Please do this assignment at the prepared placeholders (which are assigned to 0 0 by default), otherwise they could overwrite your change. Once done, edit the MBSEQ_BM.V4 file: set for Slot1: +Page EVENTS Slot2: +Page DIRECTION Slot3: +Page DIVIDER Slot4: +Page LENGTH In these slots, also change the remaining "+" parameters to "-" (so that the values won't be taken over when you are pressing a bookmark button) Best Regards, Thorsten.
  16. Thanks for the hint and sorry for the trouble! :-/ I corrected the statement in the .pdf file Best Regards, Thorsten.
  17. MIDIbox SEQ V4 Release + Feedback

    You are right that this is a useful function, please try it out: o New option 9/33 allows to unmute tracks on pattern changes Best Regards, Thorsten.
  18. MIDIbox SEQ V4 Release + Feedback

    Utility->GP15/GP16 Mutes/Unmutes all tracks at once (BLM works best in combination with the MBSEQ UI - better than inventing BLM shortcuts that we usually forget after 1 month...) The best way to get better control over mutes while changing patterns is the Phrase feature, especially if you use it from the beginning (e.g. store your pattern + mute + mixer map sets in Phrase slots via Song->Save&Take over patterns) Take care: this feature overwrites 1..4:A1..B7 depending on slot A..P) I should consider measure-synchronized Mute/Unmute for BLM as well (TODO) Best Regards, Thorsten.    
  19. MIDIbox SEQ V4 Release + Feedback

    I can add this to the wish list, it isn't so difficult to implement - but I know you guys, more people will request more assignable parameters, therefore I fear that sooner or later we reach the limits of assignable parameters and then a new concept will be required which is leading to much more implementation effort at my side. :-/ Best Regards, Thorsten.
  20. MIDIbox SEQ V4 Release + Feedback

    Happy new year!  Strange that I haven't noticed this during testing (maybe too much last minute code beautification ;) Here a new version: Best Regards, Thorsten.
  21. MIDIbox SEQ V4 Release + Feedback

    I added a new option (13/32) which changes the ALL button behaviour. In addition I changed the behaviour of the selection buttons - this works much better for me :) o Improved selection handling for midiphy frontpanel: - if you press&hold the Bookm/Step/Track/Param/Trigger/Instr/Mute or Phrase button, and then make a selection with SEL or GP buttons, the selection button will jump back to the previous function - if you press&release these buttons without a selection, the function stays active. Example: let's say the track selection is active. Press&Hold Param button, change to a new parameter layer, then release the Param button -> the selection buttons will jump back to track selection. If it's desired to permanently control the parameter layer with the selection buttons, just press&release the Param button. o New option 13/32 allows to change the steps of the current selected view only -> Best Regards, Thorsten.
  22. MIDIbox SEQ V4 Release + Feedback

    I remember that I never created new sequences on the RM1x and only used the preset patterns or sequenced the synth part with Cakewalk (a "DAW" running under Windows). And then I noticed that with a simple MB64 based sequencer I was able to work out interesting sequences much faster - this motivated me to add more and more features to the firmware, with the result that I created a dedicated sequencer with optimized UI - MBSEQ V2 was born: Best Regards, Thorsten.
  23. MIDIbox KB

    (need some time to think about the right connections) Best Regards, Thorsten.
  24. midiphy SEQ v4+

    Very good, you managed to finalize no. #3 :) Best Regards, Thorsten.
  25. sammichSID: troubleshooting [SOLVED]

    Hurray! :) Best Regards, Thorsten.