Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,206

  • Joined

 Content Type 

Posts posted by TK.

  3. MIDIbox SEQ new frontpanel idea

    in MIDIbox SEQ

    Posted

    2 minutes ago, latigid on said:

    There is still space to the left of each 8*4 section -- my thought was to include pads for three (or maybe four) encoders/buttons, and make the PCBs roughly the same dimensions as LCDs/OLEDs. I would recommend only the left-most encoders be installed, in order not to have height conflicts in the middle. Then, as the original idea started, tracks, parameter layers and trigger layers would be accessed via encoders. Wouldn't the handling be better than a multi-mode 4th row?

    No, encoder are worse than buttons.

    Buttons can be operated almost "blindly", encoders require visual focus to the display and could sometimes select an unintended track if not operated careful enough.

    I noticed this on the MB808 frontpanel - no fun!

    Quote

    Wouldn't the handling be better than a multi-mode 4th row? Plus, it frees the 4th row buttons for currently unused or future functions. 

    I would prefer to select tracks, mutes, parameter and trigger layers with the 4th row

    By providing another button to select the bookmark (BM) function the user could store and restore any kind of other function (see documentation, bookmarks are very powerful, since they not only allow to switch to pages, but also to select tracks, mutes, etc...)

    Quote

    The "track encoder" would shift the "track group" in BLM mode -- I believe that's how it works for the current 16*4 BLM.

    Too waggly usage, not useful in live situations!

    Quote

    Buttons, or even a "data encoder" if the jog/shuttle isn't included, could then be put in the middle, or on the outside. In fact, the "jog/shuttle carrier" could be placed where it suits -- in the middle, on the side, or left out. But it was certainly my idea to include more buttons on this PCB. :) I will try to make the HW as flexible as possible, but it's very important to hear implementation ideas.

    For me such a big jogwheel in the middle doesn't look nice.

    Better to place it at the right lower corner, and some buttons below.
    Probably you've to provide an alternative frontpanel for lefthanded users

    Quote

    One thing I like about the current setup is it constrains track selection to one part of the interface. Using the GP buttons or 4th row is a nice implementation and very logical with 16 parameters, but makes one search across the whole interface for the correct track.

    Buttons should be labeled... by giving generic labels 1/A, 2/B, 3/C, ... users will quickly learn the position and sooner or later operate without focusing the labels anymore...

    Best Regards, Thorsten.

  4. how to send internal keyboard notes to MIDI OUT1?

    in MIDIbox NG

    Posted

    You are right, this is a documentation error: we are counting from left (USB1 is the leftmost digit)
    Meanwhile corrected at my website

    To the actual issue: are you sure that the MIDI output is working at all?

    You could test it with following terminal command: 

    ngr send CC OUT1 1 1 127

    This should send CC#1 with value 127 over channel 1

    Doublecheck with: 

    ngr send CC USB1 1 1 127

    to ensure that the command itself is working...

    Best Regards, Thorsten.

     

  5. MIDIbox NG Release + Feedback

    in MIDIbox NG

    Posted

    Hi Chris,

    I confirm that this can be confusing: encoders define a default matrix pattern, other events won't, hence no pattern is displayed.

    If you add "led_matrix_pattern=1" to EVENT_AINSER it will work

    With the next version all events will get this default assignment

    Best Regards, Thorsten.

  6. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    On 25.11.2016 at 9:31 AM, EsotericLabs said:

    Another small suggestion for the chord handling is as follows:

    I've to spend some thoughts about this.
    The request makes sense, but to ensure compatibility a new parameter layer type for this kind of Chord handling has to be introduced.

    This means that instead of only 32 chords in Chord1, and 32 additional chords in Chord2 mode, we would have up to 128 chords available - ideas how to fill the space? ;-)

    On 4.12.2016 at 8:31 AM, mongrol said:

    I'd like to request an item for the wishlist to help with Song composition.

    Added to wish list - makes sense, but will need some time to implement this

    On 13.12.2016 at 6:43 AM, v4 said:

    there is a bug in Transpose that can be reproduced by setting force to scale to Arabian for a track and hitting G# or A# in the Transposition menu. verified on two machines in 4.091 and the latest beta.

    I will check this with high priority

    On 14.12.2016 at 6:46 AM, lobit said:

       Im going to post this here only because Ive been dreaming of this  (modulate step trigger advancement from another track)

    especially interesting if you could not only advance but transpose with the modulator track

     sh101/jx3p style sequencing 

    Still on the wish list, but lower priority compared to other (especially easy to implement) requests

    On 17.12.2016 at 0:17 PM, latigid on said:

    Can support for jog shuttles be implemented?

    Could be implemented, but I have to experiment with this hardware before I can give a final confirmation

    Best Regards, Thorsten.

  8. MIDIbox SEQ new frontpanel idea

    in MIDIbox SEQ

    Posted

    I think that additional buttons will be required, maybe above the Jog Shuttle.

    They would allow to switch the keyboard into different modes, such as

    • 1 button to select the "normal layout", the 4th row (which is not available on Wilbas frontpanel) is used to select tracks
    • 1 button so that the 4th row is used for mutes
    • 1 button so that the 4th row is used to select parameter layers
    • 1 button so that the 4th row is used to select trigger layers
    • 4 buttons to switch to BLM mode and to select the 4x16 segment
    • maybe some spares if space is available

    Best Regards, Thorsten.

  9. 2*Quad/Octal I2C (IIC)?

    in Design Concepts

    Posted

    I remember that I ordered this chip some time ago to work on a Dual-MBHP_IIC_MIDI board, but I'm still unsure if it's worth to work on this. Implementation, documentation and support effort is higher than the benefit (at least at my side)

    Actually it would be nice if somebody else could implement an alternative solution, do all the required testing and give long-term support.

    Best Regards, Thorsten.

  10. The FPGASID Project

    in MIDIbox SID

    Posted

    I'm in contact with the designer.

    The good news: he plans a public release of all sources, which means that it will be possible to change the HW interface so that it can be directly connected to the core w/o need for serial shift registers! :happy:

    It might even be possible to use a bigger FPGA for the emulation of 8 SIDs, all connected to a single SPI which will be the best way how to control the SIDs from a MBHP_CORE_STM32F4 module.

    Best Regards, Thorsten.

  11. 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.

  17. 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.

     

     

  20. 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.

  25. 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.

×
×
  • Create New...