Jump to content

gresade

Members
 View Profile  See their activity

  • Posts

    5

  • Joined

  • Last visited

 Content Type 

Posts posted by gresade

  1. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    So if I want the datawheel push button to act as "shift" which was formerly called "select" (kind of like "Enter")
    I would replace

    BUTTON_SELECT  M8A  7

    with

    BUTTON_SELECT  M8C  2

    and could use the the select-Button (M8A 7) somewhere else, e.g. for UNDO or another unassigned function to use the Button labeled "shift for something else?

     

     

  2. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    I would like to use the push function of the datawheel to act as the shift function. I think that would make sense. Not assigning the push of the datawheel to anything is a bit of a waste.
    Without digging into the sourcecode, is it possible to assign this via the Hardware config .V4 file, or do I need MIOS (I didn't use this yet)?

    The Button of the datawheel is defined to the corresponding µC input, but how to assign it to the "shift" function? 

    #                    SR  Pin
BUTTON_ENC_DATAWHEEL M8C  2

    Or is there a better assignment than the shift function?

  4. USB Host support for MBHP_CORE_STM32F4

    in Design Concepts

    Posted

    On 10/26/2016 at 2:29 PM, eptheca said:

    Hi, when I connect my GM5 I can only see and use 4 MIDI IO's

    USB1-4

    How can I find and use the 5th?

    I run 0.88

    I've got the same thing happening, when I attach the GM5 I can adress the first 4 ports, not the 5th.

    Looking at: https://github.com/midibox/mios32/blob/master/apps/sequencers/midibox_seq_v4/core/seq_midi_port.c

    The enumeration goes until "USB4" at several places, the enumeration of the USB ports looks like a static definition. There is no "MIOS32_USB_MIDI_NUM" like for IIC it's MIOS32_IIC_MIDI_NUM. I guess it could be hacked to get more USB ports, but then also the flags-words (for mute seq_midi_port_multi_enable_flags etc.) will need to be adjusted and so on, like for the IIC ports. 

     

    I have also got an 8 in/out interface from ESI that is recognized where I can use the first 4 ports, would be great to get access to 8... Then It would not be necessary to build more I/Os for the Midibox - and I can plug the Interface with all ports back to the computer without rerouting the MIDI Sockets. So run as a DAW and run same patch via Midibox plugging one cable only!

  5. midiphy SEQ v4+

    in MIDIbox SEQ

    Posted

    I want to extend my Midibox SEQ V4 with CORE_STM32F4 and V4+ firmware that is based on wilba CS frontpanel with midiphy PCBs. But I did not find schematics to check the connector pin signals, if they are compatible. From first sight it looks like it may be possible. Specifically I want to use:

    • RES-SD PCB to add a SD-card socket (this one is not super important)
    • MIDI8 PCB instead of using the longer-size 2xMIDI_IO
    • I2C PCB for 4 MIDI extra outs (I guess multiple of these boards could be used for more midi outs as described here: http://www.ucapps.de/mbhp_iic_midi.html ?)
    • LINETX PCB for the line transmission to eurorack extension
    • Eurorack modules (I read they should be compatible somewhere)

    Are the connectors on these boards compatible to the  CORE_STM32F4 connectors? Is there a documentation on the board schematics (especially the connectors pinout)?

    I will have to construct a backplate (drill holes etc.) anyways for all the conectors and only have one MIDI_IO with 4 ports for testing at the moment, so using the new and space-efficient midiphy pcbs makes sense for me, as I need more Midi outs etc. anyways and I am located in Germany, so ordering is easyer.

    Looking at the I2C PCB , there are 4 flat-cable connectors at the bottom at the board, what are they good for? I need more Midi outs, not ins, so maybe sticking with the MIDI_IO and using two I2C PCB to get 8 outs may make more sense (especially space wise), the Heidenreich case has not so much space.

×
×
  • Create New...