Jump to content

lukas412

Programmer
  • Posts

    269
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by lukas412

  1. On 12/16/2016 at 7:21 PM, latigid on said:

    No. The displays are hard up and that's the minimum spacing (check on Wilba's).

     

    No, at least not from me. Rubber pads are not aligned properly and are too small to put an RGB LED underneath, let alone the whole top layer is exposed copper pads. Maybe with a 4-layer board, but then you're back to costs going up. 200 Matias switches are 40 GBP or so, 16 adafruit pads are 5 USD. So about the same price. It's non-trivial to get pads and encoders on one board due to vertical spacing (milling needed). No real space for legends on the front panel, unless you have (special silicone glue) stickers as TK suggested.

    Anyway, thanks for your input.

     

    The switches make it for me. This is looking so good. Thanks for all this work.

  2. 3 hours ago, oozitron said:

    Request for a Roland TR-909 feature:

    On many drum machines, you can enter 16 Closed HiHat (CH) notes, then switch to Open HiHat (OH) and add a few notes.

    When the pattern plays, every step that has both a CH *and* an OH note will only play the OH.  And if you remove a OH note, the CH note is still there; the CH notes aren't removed, just temporarily "over-ride muted".  This makes pattern-building / experimenting / jamming much easier.

    Hope that makes sense...

    LOVE MY MIDIBOX SEQ V4!!!!

    Andrew

    This would be awesome. 

  3. 17 hours ago, latigid on said:

    Keep 'em coming! 20 would be a good number if possible, because I'm sure some will drop out as circumstances change. 

    Depending on how much time I have I can consider stocking some of the components/hardware, no promises though. For now it's definitely on for the BLM PCB, miniCore PCB and machined case.

    Great to hear! I would be in for all parts if it happens.

     

  4. MBSEQ is currently not able to delay individual MIDI clocks, but since this isn't the first time for this request, I added it to the wishlist

    It could be, that this feature won't be available for the LPC17 based build, since this firmware is running out-of-memory.

    Best Regards, Thorsten.

     

    This is my most wanted feature for the mbseq. Thanks TK!

     

  5. Glad that it's working :smile:

     

    I don't like the special pattern selection page, although it would be a nice-to-have function.

    It leads to a deep menu hierarchy, but the MBSEQ user interface wasn't made for this.

    E.g. there is no standard way to come out of such a page (all GP buttons are allocated... so it couldn't be a soft function).

    And everything which isn't standard, means that I've to overwork some parts of the firmware.

     

    So: I would only add this if there are strong reasons (or if I would use such a function by myself ;-)

     

    However, you probably haven't noticed yet that pattern editing is already possible: just press the SELECT key in this subpage.

     

    Best Regards, Thorsten.

     

    I can see the technical issues here, but honestly the best part of note repeat on an mpc is the ability to switch the resolution on the fly to create rolls. I can't see how you could do that the way its implemented now. Could we maybe get the ability to assign the patterns to a cc so we could switch them with a controller?

  6. Wow very nice analysis. I know crap about music theory, but I do generally get less than desirable results when I start fussing with transposing chord tracks that are forced to scale. Now knowing how they are working I can see why and can maybe change the way I work with them, but that being said knowing I will generally need to know all the notes in a scale it seems a more daunting task. Very curious to hear TK's response to this one.

     

    thanks,

     

    Luke

  7. This is not related to a bug, it's a configuration issue.

     

    In order to use VelN and VelA, you need a second trigger layer which controls the accent.

    So, "T" must be 2*64 or 2*128, there are only two configurations for this.

     

    In addition, you've to ensure that the parameter layer doesn't control the Velocity (set LayA to Roll or something else - on a freshly initialized track it's Roll)

     

    I think that I should hide VelN and VelA (and print a warning instead) whenever these parameters have no effect.

     

    Best Regards, Thorsten.

     

    Ah ok I see. Would it be possible to just have these set the velocity as well? If not I think hiding it would reduce some confusion.

     

    thanks,

     

    Luke

  8. Took a closer look at this today. Seems that some drum track types do not work. The only two that work for me are:

     

    64/2*64

    128/2*128

     

    In the other track types the VelN and VelA do not change the value.

     

    thanks,

     

    Luke

     

    Now I am seeing that in the tracks where i could change the value Vel was not a parameter layer. As soon as i change the layer to Vel the encoders stop responding. 

  9. In v4.084 in drum mode, encoders for VelN VelA no longer function. Please let me know if there is any other info I can provide. 

     

    thanks,

     

    Luke

     

    Took a closer look at this today. Seems that some drum track types do not work. The only two that work for me are:

     

    64/2*64

    128/2*128

     

    In the other track types the VelN and VelA do not change the value.

     

    thanks,

     

    Luke

×
×
  • Create New...