Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,247

  • Joined

 Content Type 

Posts posted by TK.

  6. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    V4.084 is now available for download: http://www.ucapps.de/mios32_download.html

     

    Changes:

    MIDIboxSEQ V4.084
~~~~~~~~~~~~~~~~~

   o the STM32F4 variant of the firmware supports USB Host mode!
     See also 

   o If Force-to-Scale is enabled, the edit screen shows the forced keys at the lower line.
     The original value is still displayed at the upper right line.

   o Live Page: FTS (Force-To-Scale) not applied on drum tracks anymore

   o Options Page: added new option which enforces Force-To-Scale for
     BLM16x16+X Grid Edit mode

   o Euclid Generator Page: velocities are re-generated automatically whenever
     VelN or VelA value is changed

   o the optional RECORD button now toggles between RECORD and EDIT page (previously it
     only switched to the RECORD page)

   o Song page: new action "Unmute all" will unmute all tracks and parameter layers

   o Mixer: in the UTIL->Options page it's now possible to define if CC1, CC2, CC3, CC4
     should be sent after or before the Program Change event.

   o NRPN MSB=127 allows to modify parameters of the currently selected track

    Best Regards, Thorsten.

  7. Lemur BLM

    in MIDIbox SEQ

    Posted

    The operation via USB is working fine, but I never tried it via the camera connection kit.

     

    Are you able to send & receive MIDI events from other iPad apps?

    If not: there is a general problem with the camera connection kit.

     

    Best Regards, Thorsten.

  8. QUAD IIc - Not Working

    in MIDIbox SEQ

    Posted

    No changes are required in any config file.

    IIC1*...IIC4* (the Asterisk) indicates, that the communication with the appr. IIC MIDI chips was failing.

     

    Please use the iic_midi diagnosis app for further debugging at the hardware side (connections, soldering joints, etc...)

    It can be found at the bottom of this page: http://www.ucapps.de/mios32_download.html

     

    Test procedure: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftroubleshooting%2Fiic_midi%2FREADME.txt

     

    Best Regards, Thorsten.

  10. MIOS Matrix

    in MIDIbox NG

    Posted 

    WARNING: unsupported parameter in DOUT_MATRIX n=1 ... sr_dout_row=1

    means: the sr_dout_row parameter doesn't exist.

    means: there is no shift register assigned to drive the rows.

    means: it makes sense to read in the documentation which parameter allows you to assign the shift register -> http://www.ucapps.de/midibox_ng_manual_ngc.html

    means: thereafter there is a higher chance that the LED matrix will work.

     

    Best Regards, Thorsten.

  11. MIOS Matrix

    in MIDIbox NG

    Posted

    Btw.: the EVENT_LED "trick" isn't understood at my side, it should work properly without.

     

    And if now even such a simple DOUT matrix configuration doesn't work at your side (it looks correct), something seems to be totally wrong.

     

    Could it be, that you are using an (old) .NGR script which may overwrite certain configurations?

     

    You've edited the right file, and always checked that MBNG didn't report any error or warning during the upload & execution?

     

    Or you are using a modified firmware build which causes such problems?

     

    Which core module are you using btw.?

     

    Best Regards, Thorsten.

  12. Upcoming MBHP_MF_NG module

    in MIDIbox HUIs

    Posted

    If you are not able to execute the Makefile, try to execute following command in the mbhp_mf_ng_v* directory directly:

     

    gpasm  -p p18f452  -I./src -I ./include/asm -I ./include/share -I ./modules/app_lcd/dummy  setup_mbhp_mf_ng_standard.asm

     

    Best Regards, Thorsten.

  13. STM32F4 Discovery

    in Design Concepts

    Posted

    Buy me a board, help to write the documentation and support the users who notice compatibility problems (e.g. missing or conflicting pins) with the recommended board, which is the regular STM32F407 STM32F4DISCOVERY

     

    I think that the "bigger" version is only interesting for a small number of persons who are aware of the compatibility issues, can handle that and write their own applications (so, people like you ;-))

     

    Best Regards, Thorsten.

  15. STM32F4 Discovery

    in Design Concepts

    Posted

    The STM32F401 is very limited, most major applications (such as MBNG, MBSEQ) wouldn't fit into the small flash memory.

     

    However, before you throw it away, you could send it to me so that I can provide (and test) a MIOS32 variant for this chip for the case that somebody want's to use it for less complex applications like MIDIO128

     

    Best Regards, Thorsten.

  18. MIOS Matrix

    in MIDIbox NG

    Posted

    The schematic looks correct.

    Maybe an electrical problem?

     

    Are you able to remove the button matrix from the remaining circuit?

    Then just connect the row selection signals (IC1 Pin 7, 6, 5) with the column inputs at IC2 with a cable, one after another.

     

    Each connection should trigger an individual MIDI event.

     

    If this doesn't work, connect an alternative DIN and DOUT module (or a MBHP_DIO_MATRIX if available) and check the same.

    This ensures that the matrix configuration is correct, and that you know where to continue debugging...

     

    Best Regards, Thorsten.

  20. multiple SSD1306 Displays

    in MIDIbox NG

    Posted

    MIDIbox NG supports only a single display type.

    It's too difficult to handle different types, dimensions and even graphic modes...

     

    Only exception: MIDIbox CV V2 - but I spent a lot of programming effort into this, and I'm using the SSD1306 only for special purposes (oscilloscopes)

     

    Best Regards, Thorsten.

  21. MIOS Matrix

    in MIDIbox NG

    Posted

    I had a quick look into the schematic.

     

    It looks like you are using 3 rows for the LEDs, and 3 for the buttons, right?

    In this case I would use row=4 for both matrices (DIN_MATRIX and DOUT_MATRIX), so that the row selection signals will be duplicated (visible at D0..D3 and D4..D7)

     

    This doesn't explain why the buttons trigger the events of 3 rows at once, but it might be a good starting point for debugging.

     

    Best Regards, Thorsten.

×
×
  • Create New...