Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,247

  • Joined

 Content Type 

Posts posted by TK.

  1. Midibox Drum Sequencer

    in MIDIbox SEQ

    Posted

    Finally!!! :)

    I will look into the velocity issue soon

    The board that I built some years ago is still functional and I typically show it to MIDIbox HQ visitors as one of the unknown projects that the community started but never released :)

    Best Regards, Thorsten.

  3. CV and Gate/Trigger/ Setup - AOUT port no dual gates out

    in MIDIbox SEQ

    Posted

    This was a translation error in the code, it's fixed now (and enhanced by a new feature! :)

    http://www.ucapps.de/mios32/midibox_seq_v4_095_pre12.zip 

       o AOUT: Channel 9..12/13..15 now set the gate pins #1/3/5/7 as documented (previously it was #1/2/3/4 due to a code translation error)
     New: gate pins #2/4/6/8 are now set whenever the velocity is >100.
     This way the pins can be used as an accent trigger

    Best Regards, Thorsten.

  4. Seq V4 Gate Outputs - Gate, Slide, Accent like in SID V2?

    in MIDIbox SEQ

    Posted

    This is a very clever idea, thanks for this!! :cheers:

    For those who want to try it out - it's now available in following preliminary release:
    http://www.ucapps.de/mios32/midibox_seq_v4_095_pre12.zip 

       o AOUT: Channel 9..12/13..15 now set the gate pins #1/3/5/7 as documented (previously it was #1/2/3/4 due to a code translation error)
     New: gate pins #2/4/6/8 are now set whenever the velocity is >100.
     This way the pins can be used as an accent trigger

    Best Regards, Thorsten.

  8. Starting up the dual manual organ

    in MIDIfication

    Posted

    To 1) yes, you've to add a SD Card.
    If you haven't purchased the SD Card socket yet, you could also use a common Mini SD Card adapter as available in super markets. See also the bottom of this page ("Alternative Adapter for MBHP_CORE_STM32F4 module): http://www.ucapps.de/mbhp_sdcard.html

    2) programming is similar, but parameters have to be entered into the .NGC file.
    See also following page: http://ucapps.de/midibox_ng_manual_ngc.html
    Search for "he keyboard command"

    3) see kb_2.ngc and kb_6.ngc/kb_6.ngr example configurations

    Best Regards, Thorsten.

  10. MIDIbox NG Release + Feedback

    in MIDIbox NG

    Posted

    I noticed that the last release was done 2 years ago, although many preliminary versions have been created meanwhile.

    Therefore it's now officially available.

    From the ChangeLog: 

    MIDIbox NG V1.036
~~~~~~~~~~~~~~~~~

   o new .NGR script command: send_seq (see cfg/test/seq* examples)

   o added new MIDI event types: Clock, Start, Stop, Cont

   o added new meta events to control a MIDI clock divider:
     MClkSetDivider, MClkDecDivider, MClkIncDivider

   o added new .NGC file configuration parameters:
     MidiClkOutPorts and MidiClkInPorts

   o new LCD format character '%L' allows to display logic control digits
     (MTC and status digits)

   o added new .NGR commands SET_KB_TRANSPOSE and SET_KB_VELOCITY_MAP.
     The configuration example can be found under cfg/tests/kb_6.ng*

   o encoder absolute mode: negative ranges are now handled correctly

   o .NGR LCD command: %d outputs the ^value

    Best Regards, Thorsten.

  12. Record replacing notes...what did I do?

    in MIDIbox SEQ

    Posted

    Probably I found the problem, please try this version:
    -> http://www.ucapps.de/mios32/midibox_seq_v4_095_pre10.zip

    Whenever the "step edit" feature was used in EDIT page, the played notes remained in the queue and then overwrote notes during live recording.

    Now they should be properly erased.

    If the issue happens again, open MIOS Studio and enter "dbg_record" in the MIOS Terminal.
    This should give you a list of played notes - and maybe help to understand the problem (and to give me more information :)

    However, probably you won't need this debug option anymore if the bugfix is working as intended.

    Best Regards, Thorsten.

  13. Aout_NG Not working on midibox seqv4

    in MIDIbox SEQ

    Posted

    Great that this helped at your side! :)

    But for the records: currently I'm not able to reproduce this issue.

    The test procedure:

    • turn on MIDIbox with unconfigured AOUT module
    • in CV page selected AOUT_NG module
    • exit CV page (so that this setting will be stored)
    • power-cycle MBSEQ
    • -> AOUT_NG properly configured and working
    • can be repeated with multiple power-cycles: AOUT_NG properly configured and working

    Best Regards, Thorsten.

  16. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    On 16.1.2018 at 10:05 PM, jzurd0 said:

    Another suggestion for future releases that could be interesting but not sure about it's complexity:

     Auto-fill steps while in DRUM track mode,

    Let's say you press GP3 button (fill start) for two seconds, that would invoke FILL mode ( "FILL" flashing above the steps), without (or not?) releasing GP3 press GP11 (fill end) to set the end of the steps to be auto filled: steps 3 to 11. 

    Ok, added to the wish list.

    I guess that this could be useful for common tracks as well.

    On 19.1.2018 at 11:37 PM, Rio said:

    upps.. since my last update (from svn rev.2551 to rev.2561) my SEQ switched (always) after booting to the option 'JAM' instead "T&A" on the following page

    Should be fixed now:
    http://www.ucapps.de/mios32/midibox_seq_v4_095_pre9.zip

    2 hours ago, jarvis said:

    Disregard that question - I figured it out. This sequencer keeps amazing me!

    If anyone else hasn't figured it out:

    On your target track (the one with the notes you want to play), open the mode menu. Set mode to 'normal', select a bus, and change STrg to 'on'.

    On your 'step' track (the one to advance the steps of the target track), open the event menu. Select the bus you specified for the target track. Now any steps you enter in edit mode will cause the sequencer of the target track to advance a step.

    :cheers:

    A frequently requested feature, meanwhile even mentioned in one of Oozitron's tutorial videos :)

    Best Regards, Thorsten.

  20. MIDIbox SEQ new frontpanel idea

    in MIDIbox SEQ

    Posted

    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.

  24. Midibox_NG and kb_transpose

    in MIDIbox NG

    Posted

    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.

     

    On 5.1.2018 at 4:17 PM, Cristiano said:

    Furthermore, I would like to send transposition request to another device (for the third keyboard), but I am not sure of how to do this, and how to capture that information on receiver.
    I suspect having to use Registered Parameter 2 setting (https://www.midi.org/specifications/item/table-3-control-change-messages-data-bytes-2), sending three CC (101 : 0, 100 : 2, 6 : transposition + 64), but NGC cc directives processing allow to send only one CC per event. On receiver side I do not know how to retrieve this registered parameter.

    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.

  25. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    10 hours ago, k2z3k0 said:

    1.

    When Copying DRUM track,could PASTE include also Parameter layers settings in "Only Steps" mode?

    I've noticed that this is the case with NOTE track,

    I thought this can be handy for DRUM track also

    Alright, parameter layer assignments are copied now:
    http://www.ucapps.de/mios32/midibox_seq_v4_095_pre6.zip

    10 hours ago, k2z3k0 said:

    I understand that view for editing DRUM track after changing parameter layer alway reset tu drum instrument view after pattern restarts in order to keep it always on top,

    maybe an option between toggle/momentarly PLayers buttons and screen behavior

    Can now be done with this update.

    press&hold EDIT button, and select the "Par View" (which is the 303 view for common tracks) - this will keep the parameter layer view.
    Btw.: Trg and Layer view are now supported for drum tracks as well

    9 hours ago, k2z3k0 said:

    could Transposer and Arpegiator settings in MIDI menu be saved with Session?

    The port assignment wasn't recovered correctly, should work now.

    Best Regards, Thorsten.

×
×
  • Create New...