Jump to content

TK.

Administrators
 View Profile  See their activity

  • Posts

    15,199

  • Joined

 Content Type 

Posts posted by TK.

  2. DOUT Matrix question

    in MIDIbox NG

    Posted

    Sorry, my fault.

     

    It should be:

    DOUT_MATRIX n=1   rows=4   sr_dout_sel1=4  sr_dout_r1=3  
DOUT_MATRIX n=2   rows=4   sr_dout_sel1=4  sr_dout_r1=5
DOUT_MATRIX n=3   rows=4   sr_dout_sel1=7  sr_dout_r1=6  
DOUT_MATRIX n=4   rows=4   sr_dout_sel1=7  sr_dout_r1=8

    Does this make more sense? ;)

     

     

    2) Do you mean EVENT_LED_MATRIX entry has a 16 step pattern?

     

    no, I mean that

    EVENT_LED_MATRIX id=1..16 are assigned to DOUT_MATRIX id=1

    EVENT_LED_MATRIX id=17..32 are assigned to DOUT_MATRIX id=2

    EVENT_LED_MATRIX id=33..48 are assigned to DOUT_MATRIX id=3

    EVENT_LED_MATRIX id=49..64 are assigned to DOUT_MATRIX id=4

     
    each id controls a column (LED bar)
    You've only 4 LED bars per DOUT_MATRIX, accordingly only id=1..4, id=17..20, id=33=36, id=49..52 are relevant, the others can be ignored.
     

    Best Regards, Thorsten.

  4. Display options

    in MIDIbox NG

    Posted

    This is relieving! :)

     

    Could you please check, if display 16 is working correctly with this app: http://www.ucapps.de/tmp/mios32_test_app_lcd_ssd1306_LPC1769_131201_1.zip

    It has been compiled with new gcc and "relaxed SER streams" - same infrastructure that I used for the MBNG build before.

     

     

    NOTE: I still have 100ohm resistors in series with the D0 D1 and DC lines between the two 8 OLED display boards.

    Should I attempt with them removed?

     

    Yes!

     

    Best Regards, Thorsten.

  7. Display options

    in MIDIbox NG

    Posted

    @KUI: here a new version for testing: http://www.ucapps.de/mios32/midibox_ng_v1_027_pre6.zip

     

    It has been compiled with the new GCC compile. I gave the serial shift at J15 and J28 a little bit more time in the hope that this helps.

    In addion, the SCLK will now be available at J15A:E and J15B:E

    Means: you get an additional clock driver "for free" which could be used instead of a buffer (if really necessary)

     

    If this still doesn't help, please also try out what happens if the core is powered off for at least 5 seconds, and then powered again.

     

    Best Regards, Thorsten.

  9. DOUT Matrix question

    in MIDIbox NG

    Posted

    Ah! Sorry, I picked up the wrong example.

     

    This is a better one: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Ftpd.ngc

    (it tests the TPD, which consists of two 8x8 duo-LED matrices, driven by DOUT_MATRIX n=2 and n=3)

     

    As you can see, each DOUT_MATRIX has 16 EVENT_LED_MATRIX entries, regardless of the number of rows.

    In order to ensure individual access, I would propose to define 4 DOUT_MATRIX items:

    /edit: corrected DOUT_MATRIX assignments.

    DOUT_MATRIX n=1   rows=4   sr_dout_sel1=4  sr_dout_r1=3  
DOUT_MATRIX n=2   rows=4   sr_dout_sel1=4  sr_dout_r1=5
DOUT_MATRIX n=3   rows=4   sr_dout_sel1=7  sr_dout_r1=6  
DOUT_MATRIX n=4   rows=4   sr_dout_sel1=7  sr_dout_r1=8

    you should be able to control the LED bars with:

    EVENT_LED_MATRIX id= 1 type=CC  chn= 1 cc= 16  led_matrix_pattern=1
EVENT_LED_MATRIX id= 2 type=CC  chn= 1 cc= 17  led_matrix_pattern=1
EVENT_LED_MATRIX id= 3 type=CC  chn= 1 cc= 18  led_matrix_pattern=1
EVENT_LED_MATRIX id= 4 type=CC  chn= 1 cc= 19  led_matrix_pattern=1

EVENT_LED_MATRIX id=17 type=CC  chn= 1 cc= 20  led_matrix_pattern=1
EVENT_LED_MATRIX id=18 type=CC  chn= 1 cc= 21  led_matrix_pattern=1
EVENT_LED_MATRIX id=19 type=CC  chn= 1 cc= 22  led_matrix_pattern=1
EVENT_LED_MATRIX id=20 type=CC  chn= 1 cc= 23  led_matrix_pattern=1

EVENT_LED_MATRIX id=33 type=CC  chn= 1 cc= 24  led_matrix_pattern=1
EVENT_LED_MATRIX id=34 type=CC  chn= 1 cc= 25  led_matrix_pattern=1
EVENT_LED_MATRIX id=35 type=CC  chn= 1 cc= 26  led_matrix_pattern=1
EVENT_LED_MATRIX id=36 type=CC  chn= 1 cc= 27  led_matrix_pattern=1

EVENT_LED_MATRIX id=49 type=CC  chn= 1 cc= 28  led_matrix_pattern=1
EVENT_LED_MATRIX id=50 type=CC  chn= 1 cc= 29  led_matrix_pattern=1
EVENT_LED_MATRIX id=51 type=CC  chn= 1 cc= 30  led_matrix_pattern=1
EVENT_LED_MATRIX id=52 type=CC  chn= 1 cc= 31  led_matrix_pattern=1

     

    Best Regards, Thorsten.

  10. MIDI Clock Unstable on MIDIO128

    in Design Concepts

    Posted

    Thanks for the files!

     

    This was a simple bug: the MIDI clock was output at 384 ppqn (inherited from the original MIDIbox SEQ V4 code), but a .mid file can have it's own ppqn rate which was ignored.

     

    It's fixed now, please try this version: http://www.ucapps.de/mios32/midio128_v3_017_pre1.zip

     

    Please note that the REC1.MID file won't output a proper clock whenever the song is looped, because re-loading from SD Card takes some time at which no MIDI clock event is sent.

     

    Best Regards, Thorsten.

  11. MIOS Studio. Upgrade from 2.2.x -> 2.4.6. LPC17 Not recognized?

    in MIDIbox Tools & MIOS Studio

    Posted

    Could it be, that your core is assigned to a different device ID?

    This would explain, why it won't be found via Query.

    It's also a plausible reason, because the storage file of the device ID number has been changed between MIOS Studio 2.2 and later versions.

     

    So: try different IDs, push the Query button after each change to check if the core will be found.

     

    Best Regards, Thorsten.

  13. MIOS Studio. Upgrade from 2.2.x -> 2.4.6. LPC17 Not recognized?

    in MIDIbox Tools & MIOS Studio

    Posted

    Maybe the bootloader update left some artifacts in the MacOS setup.

     

    What happens if you:

    • remove the J27 jumper (don't use bootloader mode, so that the MIDIbox NG application with it's 4 USB-MIDI ports is active)
    • start the Audio-MIDI-Setup of MacOS (e.g. search for "audio-midi" with Spotlight)
    • disconnect the core module from USB
    • delete the interface in the Audio-MIDI-Setup
    • connect the core module to USB again

    Thereafter re-start MIOS Studio and select the first MIDI IN/OUT of your MIDIbox NG

    Is the Query working thereafter?

     

    Best Regards, Thorsten.

  14. DOG CLCD Display Problem

    in MIOS programming (C)

    Posted

    Hi Robin,

     

    there is no special configuration required in the application, but you have to configure the dedicated DOG CLCD mode in the bootloader

    set lcd_type CLCD_DOG
    If this doesn't help, then try out a different cursor map.

    Because the cursor position handling is different from common CLCDs.

     

    E.g. what happens with:

          u8 cursor_map[] = {0x00, 0x40, 0x14, 0x54}; // offset line 0/1/2/3
      MIOS32_LCD_CursorMapSet(cursor_map);
    And what happens with:
          u8 cursor_map[] = {0x00, 0x10, 0x20, 0x30}; // offset line 0/1/2/3
      MIOS32_LCD_CursorMapSet(cursor_map);
     

    Best Regards, Thorsten.

  15. Track Position Display 8x16 Duo LED latest?

    in MIDIbox SEQ

    Posted

    Finally I got it working and ordered the panels :)

     

    Solution:

    - I'm using Inkscape under Linux (running in a virtual box)

    - Ilmentator sent me a .svg file

    - this file has to be modified with a text editor, otherwise Inkscape can't load it: remove xmlns="&ns_svg;"

    - do the required modifications (frame around the elements & create a bottom panel)

    - upload the new .svg to Formulor

     

    Best Regards, Thorsten.

  16. Display options

    in MIDIbox NG

    Posted

    Hi Klaus,

     

    thanks for the offer, but I fear that this won't bring new insights.

    There seems to be something special if connections are directly routed on a PCB (e.g. w/o J15 & J28 sockets between OLEDs and LPCXPRESSO module).

    It's maybe possible to compensated this via software, but I've to analyze this on my bench.

     

    Best Regards, Thorsten.

  18. Software swapping encoder pins?

    in MIDIbox NG

    Posted

    Ok, understood the problem: the .NGC file parser was too restrictive - I released a mbng_file_c.c change in the repository which allows swapped pins, and which should raise an error message on unsupported pin combinations.

    Please help to test this (critical) change - we've to avoid that valid pin combinations are refused by the parser due to a potential programming error!

     

    Best Regards, Thorsten.

  24. MIDIbox SEQ V4 Release + Feedback

    in MIDIbox SEQ

    Posted

    I could easily add a key combination which allows to do this.

    The copy function would have to store the layer was active during the capturing.

    The paste function would have to be combined with another key to transfer the previously selected layer only - maybe SELECT+PASTE?

     

    Best Regards, Thorsten.

×
×
  • Create New...