TK.

Administrators
  • Content count

    14,895
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About TK.

  • Rank
    MIDIbox Guru
  • Birthday 11/17/1972

Contact Methods

  • Website URL http://www.uCApps.de

Profile Information

  • Gender Not Telling
  • Location Germany
  1. MIDIbox SEQ V4 Release + Feedback

    A frequently requested feature, meanwhile even mentioned in one of Oozitron's tutorial videos :) Best Regards, Thorsten.
  2. MIDIbox SEQ V4 Release + Feedback

    Interesting, I wasn't aware of this! This issue is now fixed here: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre8.zip And I also added a reset function to this page :) Best Regards, Thorsten.
  3. MIDIbox SEQ V4 Release + Feedback

    Thanks for the information! This was caused by an unintended stack overflow It should be fixed in following version: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre7.zip Best Regards, Thorsten.
  4. Midibox_NG Event NoteOn lost

    Thanks for the inspiration - I will try this soon! :) Best Regards, Thorsten.
  5. MIDIbox SEQ new frontpanel idea

    I'm still unsure, if for me as a right-handed person it would be better to have the wheel section at the left side. There are situations where I want to quickly switch between selection groups (such as between track and parameter layer selection) while changing steps with the right hand. In this case, it's actually better if I could switch with the left hand. Best Regards, Thorsten.
  6. Zero Circuit

    No spam! I always enjoy your music :) Best Regards, Thorsten.
  7. MIDIbox SEQ V4 Release + Feedback

    Thanks!  Best Regards, Thorsten.
  8. You can find the API to access the LEDs directly under: http://midibox.org/mios32/manual/group___b_l_m___s_c_a_l_a_r.html Best Regards, Thorsten.
  9. Midibox_NG and kb_transpose

    Hi Christiano, very nice first posting with so many detailed information! Welcome on board! :) Actually providing a proper solution for keyboard transpose (and velocity map) changes was still on my TODO list. It's implemented now, please try this version: http://www.ucapps.de/mios32/midibox_ng_v1_036_pre4.zip A configuration example (for a single keyboard) can be found under: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_6.ngc http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_6.ngr As you can see, I preferred to use .NGR commands instead of meta events, because we want to change parameters of an event (KB:1) instead of a physical device (KB) I tested this with a Fatar keyboard (donated by FantomXR! :)) - works fine! I can even change the transpose value with the SCS encoder while playing some keys, the corresponding note-off events are matching so that we won't get hanging notes.   We've many solutions for this case 1) the most simple: I could increase the number of supported keyboards from 2 to 4, because I think that especially for organs the slightly increased latency (a couple of uS, not more!) doesn't really matter. This would mean that you could control all keyboards from a single core 2) for reacting on a single CC number multiple times, just define EVENT_* with different IDs Best Regards, Thorsten.
  10. MIDIbox SEQ V4 Release + Feedback

    The port assignment wasn't recovered correctly, should work now. Best Regards, Thorsten.
  11. MIDIbox SEQ V4 Release + Feedback

    Ok, the CC values are now configurable in the options page (item 20/26) http://www.ucapps.de/mios32/midibox_seq_v4_095_pre4.zip Pitch/Program Change/Aftertouch are now sending as well, but note that these are channel events and not key specific events. Which means, that only the first drum instrument can change the values, the remaining instruments won't send such MIDI events. Best Regards, Thorsten.    
  12. MIDIbox SEQ V4 Release + Feedback

    Alright, so please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre3.zip This turns your MIDIbox into a MIDIbox SEQ V4+ :) For the V4+ variant CCs can be assigned to drum track layers. The CC number is statically assigned: the first assigned layer will send CC#16..C#32, the second assigned layer CC#33..C#48, etc. depending on the drum instrument. I tried this with the MIDI automation of StylusRMX, and it works there. Best Regards, Thorsten.
  13. MIDIbox SEQ V4 Release + Feedback

    @k2z3k0 and @u-link: are you already using the STM32F4 core? In this case I might be able to provide configurable drum CCs as an option for MBSEQV4+ @k2z3k0: I'm surprised that the screen isn't updated immediately in your case, I've to check this! @u-link: drum track transpose: good idea! I will check this And thanks for starting a cheat sheet! :) @slo: there is a third pointer which is the "song position", currently not displayed in the menu page, but only in the song page. I've to check & document, how this works together with synchronized mutes/unmutes. Best Regards, Thorsten.
  14. The required source code change isn't so difficult, but I can't provide this as a generic solution to everybody since it generates some overhead at my side (people ask for documentation, more comfortable configuration, special options, etc). So, for your particular case, the SEQ_MIDI_ROUTER_Receive function has to be enhanced: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fcore%2Fseq_midi_router.c By something like: if( port == UART0 && midi_package.event == NoteOn && midi_package.velocity > 0 ) { int offset = 14; if( midi_package.velocity <= offset ) midi_package.velocity = offset+1; midi_package.velocity = (127*(midi_package.velocity-offset)) / (127-offset); } This would apply the linear curve to all notes received via MIDI1 (UART0) Best Regards, Thorsten.
  15. MIDIbox SEQ V4 Release + Feedback

    Happy new year! :) I just tried the random generator, (still) works fine at my side - need more input. Concerning CC layer in drums: technical problem is, that there is no place to configure the CC number: - the memory area which is usually used to configure the CC number is allocated by the Note number of the drum instrument - but even if I would introduce dedicated memory locations for the CC number, I've no idea where to place the configuration item - the EVENT page is completely allocated. :-/   The only possibility that I see is to provide pre-configured CC numbers for drums (such as CC#1 - Modulation Wheel) - but I'm sure that people will ask for more flexibility sooner and later for good reasons, so that the actual problem won't be solved. Best Regards, Thorsten.