Jump to content

TK.

Administrators
  • Posts

    15,246
  • Joined

Posts posted by TK.

  1. No, it probably hasn't been verified and therefore probably won't work after the changes for somebody else who requested changes for the virtual interface...

    Patience please, the issue is noted, I need to schedule a review & code changes at my side - which probably won't happen in the next weeks! I guess that you can life with this limitation...

    Best Regards, Thorsten.

  2. Hi Kazik,

    to 1) I added this request to the MBSEQ V4+ wish list - to make this possible, more RAM will be required which is only available for the MBHP_CORE_STM32F4

    to 2) this would require an interpolation algorithm, added this to the MBHP_CORE_STM32F4 wishlist as well (it will consume more compute power which should be available for this core - let's try it out!)

    Best Regards, Thorsten.

  3. I think it's related to a (known) limitation of the MBSID V2 system: during a patch change, the firmware has to read ca. 512 bytes from the bankstick, during this time a MIDI buffer overrun can happen if too many events are received.

    I fear that there won't be a proper solution for MBSID.

    On the other hand: due to the SID background noise, the usage of lower volumes shouldn't be preferred anyhow. It's better to lower the volume on the mixer.

    Best Regards, Thorsten.

  4. A scale editor is still on the Wishlist:

    ----------------------------------------------------------
    http://midibox.org/forums/topic/19701-blm-feature-requests/?do=findComment&comment=171522
    Scale Editor
    ----------------------------------------------------------
    

    it will probably be provided for MBSEQ V4+, since it will cause some additional RAM consumption.

    I guess that this will solve the request.

    Alternatively some additional scale entries could be provided for "flattened scales", but this approach would be less flexible.

    Best Regards, Thorsten.

  5. Quote

    On drum tracks can we have (2*64/2*128), so 64 steps long, 2 parameter layers + 2 trigger layers with 8 instruments?

    ok, I added this to the wish list

    Quote

    Also, when I change a drum track (128/2*128) parameter LayerA to CC, GPK10 doesn't let me select the CC number. It just shows "---"

    CCs are actually not supported for drum tracks, it's an error in the UI that it allows to select this.

    The pattern structure has no free space to store the CC numbers (because the appr. slots are already used to store Note number, accented and normal velocity)

    Therefore I added to the wish list, that the UI shouldn't display the CC selection

    Only solution that I see at your side: use another track to play the CCs
    I know it's cumbersome, but there won't be a quick solution to solve this

    Best Regards, Thorsten.

     

  6. The serial input of the WS2812 chip has to be connected to J4B.SC

    Quote

    is it possible to drive a rgb matrix ?

    I'm not sure if I understand your question correctly.

    Each WS2812 chip drives one RGB LED, by default you can connect up to 64 WS2812 chips, but it's possible to increase the number (with the drawback of higher SRAM consumption). See also http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fws2812%2Fws2812.c

    The WS2812 based approach is not based on a LED matrix, it's a serial chain of (cheap) RGB driver chips

    Best Regards, Thorsten.

  7. Hi,

    problem is understood, but it requires a firmware enhancement.

    I added following to the wish list:

    ----------------------------------------------------------
    Song Mode: when a new pattern is selected, it would be helpful to sync the appr. tracks to the measures, e.g. to reset the LFO
    Add option for this behaviour.

    Best Regards, Thorsten.

  8. It would be inexpensive if we could define a rule which simplifies the algorithm.

    E.g. let's say:

    • each instrument can be assigned to a group number x (x=0 for no assignment, 1..16)
    • on each step, the sequencer will only play the last instrument which has been assigned to the group, all other instruments assigned to the same group won't be played

    Due to the additional RAM consumption within the pattern storage space, such a feature could only be provided by the MBSEQ V4 Plus firmware, which requires a MBHP_CORE_STM32F4

    Best Regards, Thorsten.

  9. Quote

    Looking at the diagram for non velocity keyboards it wasn't clear which end was the bass end I also assume that that loop can extend to 128 notes  or you can make a second clone and scan seperately?

    yes, up to 2 keyboards can be scanned separately.

    Alternatively - since no velocity is involved - you could also scan the keyboards as a DOUT_MATRIX. Up to 16 matrices are supported.

    Best Regards, Thorsten.

  10. Yes, by telling the MBNG that a 8x8 DIN matrix is connected, it will scan the inputs and provide them for further event processing.

    In the cfg/tests directory you will find a lot of additional programming examples which might help: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2F

    E.g. this example shows the most simple way to send Note Events from a DIN matrix: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fblm8x8.ngc

    And when you compare this configuration with the detailed description under http://www.ucapps.de/midibox_ng_manual_ngc.html you will notice that there are much more possibilities - the example only gives you a starting point. 

    Best Regards, Thorsten.

×
×
  • Create New...