Jump to content

srmaietta

Members
 View Profile  See their activity

  • Posts

    73

  • Joined

  • Last visited

  • Days Won

    6

 Content Type 

Posts posted by srmaietta

  1. Option page

    in MIDIbox SEQ

    Posted

    Alternately, one could just write them as a list in the wiki or “user manual” for people to have?  I’m fine with scrolling the list, it’s rare that I do these days anyway..

  5. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    On 3/21/2024 at 11:24 AM, k2z3k0 said:

    hello 

    did anyone tried HUMANIZER fo CC values?

    i have NOTE track with one layer of CC ,but when i turn VEL/CC in HUMANIZER it doesnt do anything 

     

    bests

    Confirmed over here, no humanizer being applied to CC’s. 

     I tried with an empty track sending layer A as CC on buss 1, and another track listing to buss 1.  The listening track was responding to the cc’s, but humanizer did not effect the CC’s.

    Then moved the cc to layer B (usually the velocity layer) and still no changing of CC’s sent. 

    steve

    • Like 1

  9. Nth1 &2 layers “empty” options..

    in MIDIbox SEQ

    Posted

    Would it be possible to eliminate the “empty” options in the Nth1 and Nth2 parameter layers?  We go through 16 encoder clicks before getting to the first useful command “Mu 1”.

     I think it has something to do with modulo result of zero (?)  idk …?

    Perhaps these useless options could be removed from the list of nth options.?  Lots of rolling the encoder to get to the  “good stuff”, and there’s already a lot of options in there to go through!!

    thanks

    -Steve

     

  10. LFO steps not matching track divider

    in MIDIbox SEQ

    Posted

    On 2/23/2025 at 5:34 AM, TK. said:

    Yes, makes sense as an option.

    It's now available in the LFO page ("ClkDv"), please try it out: http://www.ucapps.de/mios32/midibox_seq_v4_098_pre5.zip

    Best Regards, Thorsten.

    Thorsten, the new LFO setting ClkDv is nice, great how the lfo stays locked to the track even if one changes the divider!!

    but perhaps not working as correctly as it should. Seems as if reset is happening before the final step is played.


    My simple setup: A 16 step track set at divider of 1/4 notes, all note A-1.  I haveset the LFO to Saw, Steps to 16, Rst to 16, and ClkDv on.

    The notes rise up for 15 steps, but resets to base note at step 16.  
    Musically, Seq is resetting the lfo before activating the note transpose for the step.

    ~steve

  11. LFO steps not matching track divider

    in MIDIbox SEQ

    Posted

    When setting the steps in the LFO page, it always refers to 16th note steps, even if your track is set on quarter or eighth notes, etc.

    It makes sense to me that the steps specified in the LFO settings match the divider setting so it’s easier to create an LFO of the desired length.
     

    -Is there a reason this cannot be configured to represent actual steps of the track one is editing?    

  12. Control Parameter Layer cc40 direction odd behavior

    in MIDIbox SEQ

    Posted · Edited by srmaietta

    On 2/22/2025 at 9:50 AM, TK. said:

    This was due to a quick&dirty implementation at the place where information about the events are assembled.

    It's now a bit less dirty -> http://www.ucapps.de/mios32/midibox_seq_v4_098_pre4.zip

    Best Regards, Thorsten.

    TK -seriously. YOU DA MAN!!!  
    —This now works just like I’d expect—
    Your amazing machine lives on and still is at the very top of the list!

  16. Control Parameter Layer cc40 direction odd behavior

    in MIDIbox SEQ

    Posted · Edited by srmaietta

    Playing with ctrl parameter layer and I’m noticing something that seems not right, and I don’t think it’s user error. (Bug? Fixable? Code architecture limitation?)

    I set up a single 16 step track with ascending scale of notes, on a new clear project to verify this.

    I set up parameter layer D to ctrl, cc40 (track direction) and put in 0000000551111111.

    This is forward x7 steps, random step x 2 and backward x7.

    —When I play the track from the edit screen the forward steps are randomly scattering forward and backwards.  The backwards set of steps always seem to work correctly.

    —When I play the track from any other screen (track direction screen as shown in video) the CC assignments seem to work correctly.

    please watch the video to see what I’m talking about.

     

  19. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    3 hours ago, Rio said:

    Hello steve,

    Is it possible for you to make your own binary from the sources? I have written a fix for quantized live recording in the past...  you could try the code changes/snippets which it affects. Let me know if you would like to try it out.

    Oh, you mean a possibility of an exact "unquantised recording". Of course, my suggestion doesn't fit there. 

    greetings,

    rio

    Up for any ideas!

  20. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    Hello!  
     

    I know this has been brought up before, but I’d like to revisit the idea of “unquantized live recording”.

    currently the quantize percent basically shows how far off one can be before dropping a value in the current step/prev step.  So it’s locked to a hard step position.  I know we can up the resolution and track length to kinda sorta work within the system.  But that is not ideal for a number of reasons.

    An idea: when recording midi, if we have the delay parameter assigned on a track, and have quantize set to 0%, it will then drop the played note wherever it was played within the delay parameter resolution.

    Perhaps a new track format needs to be set up, or perhaps it is a parameter to toggle in the menu.  
     

    I have no idea if this is at all possible from a programming / code base perspective.  But no truly unquantized recording is one of the only missing things of our mighty Seq 4!!!!!  
     

    Thanks for reading!

    Steve

  25. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    On 8/5/2021 at 4:16 AM, clddstllr said:

    Thanks, very helpful! I could have a go at a cheat sheet, that one does not exist yet for the v4+ and should be quite helpful for starting a new journey.

    Deepness is a fantastic attribute for a tool, if it can be unlocked by intuition :cheers:

    Here's a simple "cheat Sheet" I made up a while ago and keep handy.  May be a good starting point for folks.

      I add notes to it, go experiment, and then revise the cheatsheet. . 

    ~Steve

    Seq4+RefSheet.rtf

×
×
  • Create New...