Jump to content

k2z3k0

Members
 View Profile  See their activity

  • Posts

    136

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by k2z3k0

  1. Remote pattern change and midi clock issue

    in MIDIbox SEQ

    Posted · Edited by k2z3k0

    hello 

    i have a problem with switching patterns via remote midi cc 112-115 and time clock.

     

    Mbseq and Octatrack (via TM-1 ,is Elektron made usb to midi interface for faster(10x) midi transmission ,Tubo mode is ON)  are connected to my computer via usb. 

     

    in my computer i am sending Mbseq midi clock and notes on channel 1 to play samples in Octatrack on channel 1,Ocatrack sample player is set to time stretch mode so dependent of midi clock

     

    Mbseq patterns are controlled via launchpad via MIDI in 1 ,i made it so that via top row buttons i can switch all four patterns ,sort of groups

    so under each of eight buttons i have set of four Mbseq patterns ,so e.g button 1 mbseq patt 1,1,1,1 ,button 2 mbseq patt 2,2,2,2 etc..

    i also can recall individual patterns with launchpad

     

    mbseq is set to

    -track sync steps per measure 32

    -patt change sync each 8 steps

    -pattern change sync on,

    -restart all tracks on,

     

    ok so i have simple pattern with break sample in time stretch mode ,

    when i am starting press constantly on my launchpad only pattern 1 button on my launchpad ,pattern is being recalled every 8th step as expected

    sample is playback as it should

     

    but,when i press my launchpad group button  to recall all four patterns on mbseq ,what happends is pattern is being recalled,but just when recall happends midi clock slows down ,

    and then comes back to normal when i stop pressing 

    and because sample that is played by OT is in time stretch mode,so dependent on midi clock this is why i can hear that,

    also if i recall independently two patterns i can hear that but little less then when all four are recalled

     

    i also checked with monitor and i am sending clear cc 112 ,113 ,114 ,115 so no extra garbage is getting there

     

    this situation does not occur when i turn off Turbo MIdi Tm-1,or when i recall only one pattern,or when i recall pattern from MIDIBOX it self via panel,

    or when sample is not in time stretch mode.

     

    i am attaching two example recordings,

    so you can hear what happends for your self,

    one is just wav from octa,other is from ableton

     

    -in octa example

    in the middle of first part i am starting to recall all four patterns constanly with Turbo Midi off,and sample is playing correctly 

    in the middle of second part i doing same thing but with Turbo Midi on,and clearly you can hear sample speeds down for a moment

     

    -in ableton example

    once im starting to recall all four patterns you can see that bpm counter is going from 154 to 147,and you can hear same playback speed is dropping

     

    so in conclusion

    1.i think is possible that midibox gets little wierd when more patterns are recalled and midi clock is getting bit flaky during switching ,however internal Midibox Info does not shows any drops ,CPU Load goes 10% higher

    2.maybe this is somehow regulated by 31250 midi bus speed and is not audible when using din 5 ,but becomes a problem when going over usb and bus speed is higher .

     

     

    thank you 

    bests

     

     

  2. Data Loss when Save ALL and changing Patterns via Midi cc#112-115

    in MIDIbox SEQ

    Posted · Edited by k2z3k0

    hello there

    i just experienced loss of my patterns data after i did SAVE and changed pattern via midi cc# 112-115

     

    i am controling patterns with external controller,so i pressed SAVE "Complete Session stored" ,and right after i changed one of the patterns via external controller,

    then mbseq hangs,and after reboot patterns where gone.

     

    maybe mbseq does not protects save operation and allows to execute program change via midi cc's ,thus leading to data loss ?

    i had backups so it was ok for me but i can imagine when one does not have 

     

    bests

     

  7. restoring seq_ui_button_state.FAST_ENCODERS from BM flag does not work

    in MIDIbox SEQ

    Posted · Edited by k2z3k0

    On 4/12/2024 at 9:11 PM, TK. said:

    How could I reproduce this issue? Could you please give step-by-step instructions?

    Best Regards, Thorsten.

    hello T

     

    ok so i am on http://www.ucapps.de/mios32/midibox_seq_v4_098_pre2.zip

    fresh new project

    1.make GLOBAL BOOKMARK #1 for DIVIDER with FAST ON,

    2.FAST is ON and CLOCK GP #2 scrolls fast,

    3.switch to EDIT page ,FAST is automatically turned off,

    4.recall GLOBAL BOOKMARK #1 ,FAST is ON BUT not working,CLOCK GP #2 scrolls normal 

    5.switch to EDIT page,turn on FAST,recall BOOKMARK #1 now FAST is ON and working


    in SEQ_UI.C  it says

    Quote

     

    s32 SEQ_UI_Bookmark_Store(u8 bookmark)

    {

      if( bookmark >= SEQ_UI_BOOKMARKS_NUM )

        return -1;

     

      seq_ui_bookmark_t *bm = (seq_ui_bookmark_t *)&seq_ui_bookmarks[bookmark];

     

      // note: name, enable flags and flags.LOCKED not overwritten!

     

      //bm->flags.SOLO = seq_ui_button_state.SOLO;

      bm->flags.CHANGE_ALL_STEPS = seq_ui_button_state.CHANGE_ALL_STEPS;

      bm->flags.FAST = seq_ui_button_state.FAST_ENCODERS;

     

    and to restore 

    Quote

     

    s32 SEQ_UI_Bookmark_Restore(u8 bookmark)

    {

      if( bookmark >= SEQ_UI_BOOKMARKS_NUM )

        return -1;

     

      seq_ui_bookmark_t *bm = (seq_ui_bookmark_t *)&seq_ui_bookmarks[bookmark];

     

      // should be atomic

      portENTER_CRITICAL();

      //if( bm->enable.SOLO )              seq_ui_button_state.SOLO = bm->flags.SOLO;

      if( bm->enable.CHANGE_ALL_STEPS )  seq_ui_button_state.CHANGE_ALL_STEPS = bm->flags.CHANGE_ALL_STEPS;

      if( bm->enable.FAST )              seq_ui_button_state.FAST_ENCODERS = bm->flags.FAST;

     

     

    i think there might be a bug somewhere,something missing

    it seems seq_ui_button_state.FAST_ENCODERS = 1 is turning FAST button LED on but not the FAST function when recalled from BOOKMARKS

     

    i also tried to use seq_ui_button_state.FAST_ENCODERS = 1 for example when switching to MIXER page so my encoders work fast in MIXER page,but same effect

     

     

    p.s.

    while i have your attention ,

    in HUMANIZER there is 2nd option VEL/CC ,should that humanize VELOCITY and MIDI CC messages from PARAMETER LAYERS of the track?

    cause when i set track with one CC param HUMANIZER does not humanize that CC layer

     

    thank you for your time

    best regards

    Kazik

  12. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted 

    hi 

did anyone tried that ?
i can make it work with 0..15 but not 127 for currently selected track




 o CC#99 (0x63 - NRPN MSB)
     Selects the Track which should be modified via NRPN
     Allowed values: 0..15 for Track 1-16, 127 to modify the current selected track

    seq_midi_in.c says

     

    case 0x63: // NRPN MSB (selects track, if >= SEQ_CORE_NUM_TRACKS, take the currently visible track)

        nrpn_msb = value;

        break;

     

  13. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted 

    hi 

did anyone tried that ?
i can make it work with 0..15 but not 127 for currently selected track




 o CC#99 (0x63 - NRPN MSB)
     Selects the Track which should be modified via NRPN
     Allowed values: 0..15 for Track 1-16, 127 to modify the current selected track

    seq_midi_in.c says

     

    case 0x63: // NRPN MSB (selects track, if >= SEQ_CORE_NUM_TRACKS, take the currently visible track)

        nrpn_msb = value;

        break;

     

  14. midibox cc implementation cc#99 channel select...

    in MIDIbox SEQ

    Posted · Edited by k2z3k0 

    hi 

did anyone tried that ?
i can make it work with 0..15 but not 127 for currently selected track




 o CC#99 (0x63 - NRPN MSB)
     Selects the Track which should be modified via NRPN
     Allowed values: 0..15 for Track 1-16, 127 to modify the current selected track

    seq_midi_in.c says

     

    case 0x63: // NRPN MSB (selects track, if >= SEQ_CORE_NUM_TRACKS, take the currently visible track)

        nrpn_msb = value;

        break;

     

     

  17. Random Generator and Initial Note number

    in MIDIbox SEQ

    Posted

    u8 base, range;
      seq_par_layer_type_t layer_type = SEQ_PAR_AssignmentGet(visible_track, layer);
      if( layer_type == SEQ_PAR_Type_Length ) {
      base = 16;
      range = ((par_layer_range[layer] >> 2) - 1); // -> +/- 16
      if( !range || range > 128 ) // (on underrun...)
      range = 1;
      } else {
      base = 0x40; <- WILL THIS DO THE TRICK?
      range = par_layer_range[layer];
      }

  18. Random Generator and Initial Note number

    in MIDIbox SEQ

    Posted

    hello everybody

    I noticed that when randomizing clean empty track LayA(notes) with value 1,(TrgAll),it makes  -1 / +1 deviations from 64 which is E-3.

    Now initial note for track is 60 (C-3) and this makes a bit strange situation ,that randomizer starts from other point then initial note value(60)

     

    Also i want to ask if there is a way to set default initial value(now 64,C-3) of notes,there is initial value for CC(option 24/33),maybe would be great to have one, also for notes.

    And maybe would be great if randomizer deviate starting from that default init value

     

    thank you in advance

    best regards

      Kazik

  20. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted · Edited by k2z3k0

    4 hours ago, Rio said:

    I was just wondering because in the "MIDI" config on the Jam Page, it has not yet been updated. Greetings.

    yes

    i suppose is just minor thing to straight out in code

    if you go to Menu -> Midi ->Transpose and Arp ,there yes you can set CHANNEL to AUTO

    BUT

    if you go to Utility -> Jam -> MIDI ,there you CAN'T set Midi channel to AUTO,instead is showing Channel #18

    but as i said i suppose is little thing to straight out

    we just need to wait and give careful and precise feedback

    and as always THANK YOU TK for your time

    i feel if this works out correctly it will be huge upgrade for live perfomance capabilities of MBSEQ v4.

     

     

     

    thanks for your time

      Kazik

     

  25. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    hello everyone

     

    While working with MORPHING(mbseqv4),i thought would be great to be able ,

    to have option that when called(puch button) leaves currently Morphed values and sets Morph back to zero

    This way you could quickly build patterns just from using Morph

     

    thank you for your time

       Kazik

×
×
  • Create New...