Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,246

  • Joined

 Content Type 

Posts posted by TK.

  1. MIDIbox SEQ new frontpanel idea

    in MIDIbox SEQ

    Posted

    43 minutes ago, latigid on said:

    I assume that WS2812B will use too much memory? That would be an easier way to do it if there are decent mounting strategies. There are also newer APA102 LEDs that run over SPI (clock and data) -- easier to manage?

    WS2812B is possible for V4+, but the LEDs consume so much power that the device can't be supplied from a USB cable (strongly recommended todays!)

    Best Regards, Thorsten.

  7. MIDIbox SEQ new frontpanel idea

    in MIDIbox SEQ

    Posted

    Encoders are important for fast parameter changes with a single hand.

    Here an alternative idea for a FP layout:

    mbseqv4newfp.thumb.png.a7a2caf925061c97f

    However, a potential issue with the adafruit pads is the spacing between the pads: it doesn't allow to add labels

    But labels are essential for intuitive usage!

    Best Regards, Thorsten.

     

     

  10. OLED displays

    in MIDIbox SEQ

    Posted

    Hopefully it will be possible to find a more detailed datasheet.

    Maybe it isn't related to current draw, but to a configuration option.

    This is based on speculation, but worth to check (because I've no other idea): according to the website this display supports different protocols such as 6800, 8080 and SPI.
    The 8080 protocol is required, if 6800 is selected instead, a short circuit would happen between the parallel connected data busses during read operations, and this could cause a malfunction (e.g. core reboot)

    With some luck you will find some bridges on the PCB which show the configurable options on the silk screen.

    Best Regards, Thorsten.

  15. CAN bus not working

    in MIDIbox SID

    Posted

    So, you mount the 4 PICs of the non-working board into the other board, and CAN communication is working there? This is an important information!

    Concerning continuity checks: remove the PICs while checking it.
    Compare with this interconnection diagram: http://www.ucapps.de/midibox_sid/mbsid_v2_communication.pdf
    And this schematic: http://www.ucapps.de/mbhp/mbhp_core_v3.pdf

    Expectations:

    • pins #36 of the PICs (RB3) are directly connected together.
      They should show continuity to each other.
      No continuity to ground (Vs)
      No continuity to 5V (Vd)
      But should show 1k resistance to Vd
    • pin #35 of the PICs (RB2) should show
      No continuity to ground (Vs)
      No continuity to 5V (Vd)
      continuity to pin #36 only if the negative probe is connected to pin #35, and the positive probe to pin #36 (due to the diode)

    Results?

    Best Regards, Thorsten.

  16. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    Synced pattern changes should work again with this version:
    -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre7.zip

    Background why this happened: last week I analyzed the stack usage and found out, that in worst case a stack overrun could happen while playing MIDI events or operating with the CS. I gave the appr. tasks more memory, and reduced memory for the pattern handler. By doing so, I overlooked that during a pattern change more memory will be allocated than expected.

    With the last changes the pattern task became obsolete, giving more memory for the other tasks (and a bit more memory for additional features :)

    I hope that with pre7 everything is working like before (or even better ;-)

    Best Regards, Thorsten.

  18. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    1 hour ago, u-link said:

    Wow, that was quick! Thanks a lot, I will try it out asap, hopefully tomorrow. You are of course right, if you use groove patterns for velocity control, you want to keep it. I never did that up to now. What about keeping velocity control, but automatically ditching swing for non-standard (ie: non-16ths) sub div? While I am not sure I understand your suggestion correctly, I don't think it would do the trick. Imagine two tracks with different sub div sending to the same receiver, this would still lead to flams, no?

    You've to enable the "sync to track" option for both tracks, and they have to run with the same divider, then it will work! :)

    Here the new version:
    -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre5.zip

    21 minutes ago, EsotericLabs said:

    for drum tracks, there are 1024 bytes for parameters and 2048 bits for triggers , is that correct? Less instruments allow longer parameter and trigger patterns, is my understanding correct?

    You are right, I corrected the max. trigger layer lengths of the two additional drum modes that you introduced accordingly in pre5

    Best Regards, Thorsten.

  19. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    Alright, here some updates:
    -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre5.zip
    /edit: corrected to newer link 

       o new drum configurations: 4*16/2*64, 4*16/1*128, 4*16/1*256

   o new track mode configuration option: "Note"
     Allows to specify, if the transposer should take the last or first
     played note (previously it always played the last note)

   o individual steps of CC, PitchBender, Program Change and Aftertouch
     layers can now be disabled so that they won't play.
     Turn the encoder to the rightmost position (value 128)

     Also the init value has been changed: for these layers, the steps
     are now disabled by default.
     For CCs please change the init value by yourself in the UTIL->OPT
     page (option #12: Initial CC value)

   o new behaviour of CLEAR button in recording mode:
     it clears the selected step only (not the entire pattern).
     During live recording it will clear the "played" steps so long the
     button is pressed.

   o new CC functions which can be configured in MIDI->ExtCtrl.:
     o Play/Stop: allows to assign the PLAY button to a CC
     o Record: allows to assign the RECORD button to a CC

    @EsotericLabs: thanks a lot for testing!
    G1T2 was playing the last note of the note stack. Since G1T1 played a chord into the transposer but, it was off the root note.
    In the new version you are able to specify that the first note should be played.
    Select Track #2, change to the MODE page and press GP button #9

    @u-link:

    - request #1 implemented (I also needed it ;-)
    - request #2 was already implemented (there is a BUTTON_RECORD and LED_RECORD option in the MBSEQ_HW.V4 file, please update your file according to the templates under hwcfg/*)
    However, Play/Stop and Record can now also controlled via CC (e.g. to control these functions from a foot switch)
    - request #3: implemented (yes, it makes sense)


    - request #4: statement & question:
    I'm using custom groove patterns to vary the velocity, here I would like to control each 16th
    In addition, since groove patterns can be applied globally, you want to define them independent of the track divider

    However, what I could add is an option which allows to synchronize the groove pattern to the track step instead of the global step. Would this satisfy your request?

    Best Regards, Thorsten.

  21. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    Alright, the problem with the chord display was, that it actually always displayed a label based on the first layer (and not the selected layer). This is fixed now.
    -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre3.zip

    I also added the support for 4 parameter layers in drum tracks.

    The implementation wasn't so difficult.
    Would be nice if you could help testing (also the other layer modes to ensure that I haven't corrupted something)

    Best Regards, Thorsten.

  22. OLED-Display MTC und Status

    in MIDIbox NG

    Posted

    Hat wohl noch gefehlt - hier eine neue version: :happy:
    -> http://www.ucapps.de/mios32/midibox_ng_v1_036_pre2.zip

    Die digits lassen sich mit %L darstellen

    Hier ein Konfigurationsbeispiel - die bereits vorhandenen EVENT_LED_MATRIX konfigurationen muessen um fwd_to_lcd, lcd_pos und label erweitert werden: 

    # Following example shows how LC digits could be displayed on a LCD with the events above
# notes:
# - replace the EVENT_LED_MATRIX configurations above by the new ones with lcd definitions
# - change lcd positions by locations which are not used by other text messages yet!
#
# EVENT_LED_MATRIX id=33 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 64  syxdump_pos=10:0  fwd_to_lcd=1  lcd_pos=1:14:1 label="%L"
# EVENT_LED_MATRIX id=34 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 65  syxdump_pos=10:1  fwd_to_lcd=1  lcd_pos=1:13:1 label="%L"
# EVENT_LED_MATRIX id=17 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 66  syxdump_pos=10:2  fwd_to_lcd=1  lcd_pos=1:11:1 label=".%L"
# EVENT_LED_MATRIX id=18 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 67  syxdump_pos=10:3  fwd_to_lcd=1  lcd_pos=1:10:1 label="%L"
# EVENT_LED_MATRIX id=19 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 68  syxdump_pos=10:4  fwd_to_lcd=1  lcd_pos=1:8:1  label=":%L"
# EVENT_LED_MATRIX id=20 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 69  syxdump_pos=10:5  fwd_to_lcd=1  lcd_pos=1:7:1  label="%L"
# EVENT_LED_MATRIX id=21 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 70  syxdump_pos=10:6  fwd_to_lcd=1  lcd_pos=1:5:1  label=":%L"
# EVENT_LED_MATRIX id=22 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 71  syxdump_pos=10:7  fwd_to_lcd=1  lcd_pos=1:4:1  label="%L"
# EVENT_LED_MATRIX id=23 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 72  syxdump_pos=10:8  fwd_to_lcd=1  lcd_pos=1:2:1  label=":%L"
# EVENT_LED_MATRIX id=24 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 73  syxdump_pos=10:9  fwd_to_lcd=1  lcd_pos=1:1:1  label="%L"
# 
# # status digits
# EVENT_LED_MATRIX id=39 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 75  syxdump_pos=11:1  fwd_to_lcd=1  lcd_pos=1:2:2  label="%L"
# EVENT_LED_MATRIX id=40 led_matrix_pattern=LcDigit  type=CC chn= 1 cc= 74  syxdump_pos=11:0  fwd_to_lcd=1  lcd_pos=1:1:2  label="%L"

    Mit lcd_pos legst Du das display und die X/Y Koordinaten fest, und mit %L wird ein Logic Digit ausgegeben.

    Gruss, Thorsten.

     

  23. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    Great idea to use such a track to transpose/arpeggiate other tracks :)

    I'm surprised that a note layer is required to play a chord. I also can't reproduce the chord display issue at my side.
    Could you please send me an example pattern where you notice this?

    You can store the pattern into a file from the EVENT->Pattern page

    Best Regards, Thorsten.

  24. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    This was related to a stupid mistake that I introduced during the last changes before pushing the release button :-/

    Here a new version:
    -> http://www.ucapps.de/mios32/midibox_seq_v4_092_pre2.zip

    Meanwhile I also added a more detailed description to the ChangeLog: 

       o new parameter layers for track specific root note and scale

     Root selection strategy: if Root is assigned to any parameter 
     layer of a track, the layer can either select the global root 
     selection ("Glb") or set the root note for each step explicitely.

     The global root selection is configured in the FX->Scale page,
     it's either "Keyb" (for MIDI keyboard entry) or C, C#, ... B

     The local root selection is C, C#, ... B

     Notes and Chords will be transposed accordingly if the track is in
     Normal mode (and not in Transpose or Arpeggiator mode)

     Similar for Scale: it can override the globally configured scale
     of the FX->Scale page for each step.

    Best Regards, Thorsten.

×
×
  • Create New...