TK.

Which operating system? And are the USB MIDI ports of your MIDIbox still displayed by any other MIDI software? Best Regards, Thorsten.

Hi, status from my side: I created a board with 4 additional OLEDs today, and connected it in parallel to my first board (CS lines are uncritical, therefore this doesn't matter) I still get very stable display output, even when I'm using an extra-long cable to J15: Conclusions so far: - SCLK and SDA (D0 and D1) still uncriticial when 9 OLEDs are connected in parallel - I tested this with a "new gcc" build - the "new gcc" build leads to the same results on two different hardware implementations (KUI & Novski) I've still no clue what could cause such an issue :-/ How can I get direct access to the hardware? Novski: you are located in Switzerland, I guess it would be too expensive to ship your PCB to germany. KUI: where are you located? Best Regards, Thorsten.

I will check this soon! Best Regards, Thorsten.

I updated MIOS32_ENC, so that pins are swapped if an odd number is specified in the .pos item So: .pos = 0 or 2 or 4 or 6: works as usual .pos = 1 or 3 or 5 or 7: pins swapped Best Regards, Thorsten.

Your patches are so dammed cool! Finally somebody who considers the modulation capabilities! :) Do you allow me to provide your bank with the release package? Best Regards, Thorsten.

Yes, this is possible with some clever .NGR scripting! :) -> http://www.ucapps.de/midibox_ng_manual_ngr.html There is a special "set_rgb" command which allows you to set any ring to any colour based on any condition. Best Regards, Thorsten.

There is something special with your .mid files, could you please attach one to this posting, so that I can check why the clock rate isn't determined correctly? This would be the first step to analyze the issue. Best Regards, Thorsten.

Inkscape doesn't work correctly at my side, the GUI elements are not correctly displayed (I'm using the latest XQuartz version) In Libre Office, I've ensured that the correct RGB values are used. Ilmenator, could you please send me the exact file you've used during your Formulor order? I would like to doublecheck, if I'm able to convert this one with Libre Office Best Regards, Thorsten.

Hi Mikael, it is possible, but requires some reverse engineering. It especially has to be considered, that there is no "one approach fits all". E.g. if the keyboard is scanned with >= 50 uS, a microcontroller might be sufficient to emulate the keyboard. For higher scan rates, a FPGA based approach might be better. In any case, you need good programming skills and an oscilloscope for debugging to implement such an emulation your synths. Best Regards, Thorsten.

Great! :smile:

Hallo, das kann ich bei mir nicht reproduzieren - die untere Zeile funktioniert nach dem Verlassen des Menues. Es ist vielleicht wichtig zu wissen, dass der vorherige Inhalt verloren geht, der Bildschirm muss also von Deinen Events neu aufgebaut werden. Oder meinst Du mit "garnichtmehr", dass selbst das Terminal Kommando: lcd @(1:1:2)Test nicht mehr funktioniert? Gruss, Thorsten.

Hi Willem, this is normal if Wilba's frontpanel is used, and no MBSEQ_HW.V4 file exists in the root directory of the SD Card. You've to upload the hwcfg/wilba/MBSEQ_HW.V4 file which is located in the midibox_seq_v4 release package. Best Regards, Thorsten.

Ok, it seems that all button functions which are assigned to pin 0 are triggered at once: # SR Pin BUTTON_GP1 M5 0 ... BUTTON_GP3 M6 0 ... BUTTON_GP5 M7 0 ... BUTTON_GP7 M8 0 ... BUTTON_GP9 M4 0 ... BUTTON_GP11 M3 0 ... BUTTON_GP13 M2 0 ... BUTTON_GP15 M1 0 It seems that a solder joint of one of the 74HC595s is faulty. Unfortunately I don't have a schematic of the frontpanel available right now, otherwise I could tell you the exact unit. However, just open the case and check all pins of the 74HC595s (or follow the trace of the GP15 button to a 74HC595, and check exactly this pin) Best Regards, Thorsten.

Could you please check if the modified MBSEQ_HW.V4 file really has been uploaded? You could edit it in the MIOS Filebrowser. Scroll to the button definitions. Then you should see, that all BUTTON_ entries are commented out with '#': ## SR Pin #BUTTON_DOWN M4 2 #BUTTON_UP M4 3 #BUTTON_LEFT 0 0 #BUTTON_RIGHT 0 0 # ## SR Pin ... Can you confirm this? If not -> upload the right file Best Regards, Thorsten.

I took your file, imported it into Libre Office (because I don't own other suitable software for the Mac), added a frame around the frontpanel, changed black to red colour, exported to .svg and tried to submit it at Formular (and also Ponoko) - in both cases I get the error message, that the .svg file contains wrong colours. So, I copy&pasted the frontpanel components it into a new document, exported to .svg and submitted again - now it complains about lines which are thicker than allowed. Has anybody experiences with Ponoko or Formulor templates created with Libre Office or similar open source software which is available for MacOS? Best Regards, Thorsten.

If you don't specify the LED_MATRIX_PATTERNs, MBNG will take the defaults which are documented here: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Fdefault%2Fdefault.ngc If you don't like the defaults, then just customize the predefined patterns. Best Regards, Thorsten.

You've to update the toolchain: http://www.midibox.org/mios32_toolchain/ Best Regards, Thorsten.

Good catch! This bug only exists in the PIC16F4685 variant, and the problematic code location is clearly marked with: ;; EXTRA sending routine for second byte: dirty but ok here ;-) Could you please try if this one works better before I officially release it? -> http://www.ucapps.de/mios/midibox_fm_v1_4g.zip Best Regards, Thorsten.

First of all: a 16x16 matrix is a bad choice, please layout two 8x16 matrices instead, so that the LEDs are brighter. Then you will be able to configure the matrices with: DOUT_MATRIX n=1 rows=8 inverted=0 sr_dout_sel1=1 sr_dout_r1=2 sr_dout_r2=3 sr_dout_g1=4 sr_dout_g2=5 sr_dout_b1=6 sr_dout_b2=7 DOUT_MATRIX n=2 rows=8 inverted=0 sr_dout_sel1=8 sr_dout_r1=9 sr_dout_r2=10 sr_dout_g1=11 sr_dout_g2=12 sr_dout_b1=13 sr_dout_b2=14 with a 8x16 matrix, you will get 8 hues per colour (makes 512 possible colors) The hue can be passed with the rgb parameter. E.g. let's say an encoder is mapped to 4 banks, you can specify: to change the LED ring color depending on the bank Best Regards, Thorsten.

Aehm... kann es sein, dass Du IC1 und IC2 vertauscht hast? Vergleiche mit meinem Bild: Gruss, Thorsten.

Hi Willern, very nice song! I'm always happy when people create something new out of these tutorials! :) To the GP15 button: ok, this explains a lot. In order to analyse this a bit further, it makes sense to output all button functions which are triggered by GP15 You can do this with following MBSEQ_HW.V4 file: http://www.ucapps.de/tmp/test_wilba_frontpanel_buttons.zip first update your MIDIbox to the latest release V4.079 (because the MBSEQ_HW.V4 file is not compatible with older releases) upload the modified MBSEQ_HW.V4 file with the Filebrowser thereafter enter "reset" in MIOS Terminal -> your MIDIbox will be rebooted push each button and check the terminal output. Each button should only generate a single message when pressed or depressed E.g. GP15 should result into following messages: [221644.599] [SEQ_UI_Button_Handler] Button SR:24, Pin:0 not mapped, it has been pressed. [221645.495] [SEQ_UI_Button_Handler] Button SR:24, Pin:0 not mapped, it has been depressed. if more messages are print, then please copy&paste them into this posting. Then I can determine which additional functions are triggered, and tell you which parts of the PCB require visual inspection. Best Regards, Thorsten.

Ethernet PHY error messages are now disabled by default in the new releases V4.079 and V4L.079 Best Regards, Thorsten.

A new version is available which inherited functions from the big brother ;) MIDIboxSEQ V4L.079 ~~~~~~~~~~~~~~~~~~ o added new MIOS Terminal commands: new, saveas, save, load, delete, session, sessions Similar to "the big brother" MIDIbox SEQ V4, you are now able to create multiple sessions on SD Card, or to create a backup of your current session. Best Regards, Thorsten.

V4.079 is now officially released From the ChangeLog: MIDIboxSEQ V4.079 ~~~~~~~~~~~~~~~~~ o added new Fx which allows to send to one or more additional MIDI channels from a single track with various behaviours (forward to all, alternate between channels, randomly select channel) The new functions can be configured at the Fx->Dupl (like Duplicate) page o groove page: added possibility to change the intensity for all tracks at once o MBSEQ_HW.V4 file: SR numbers for BUTTON and LED functions which are assigned to the BLM8x8 matrix (-> Wilba's Frontpanel) are now named M1..M8 instead of 17..24 See also the configuration template under hwcfg/wilba/MBSEQ_HW.V4 The old syntax is still provided to keep old MBSEQ_HW.V4 files compatible. Once the new SRIO_NUM_SR parameter is set to 17 or more SRs, the new syntax has to be used. o MBSEQ_HW.V4 file: new parameter SRIO_NUM_SR allows to specify the maximum number of DIN/DOUT shift registers in a chain. Up to 23 DINs/DOUTs can be chained now - this is also the new default value in the MBSEQ_HW.V4 templates. o whenever a MBSEQ_HW.V4 file is uploaded with the MIOS Filebrowser, the configuration will be automatically reloaded (no need to reset the core) o official support for Ilmenator's Track Position Display. See also http://www.midibox.org/dokuwiki/doku.php?id=tpd_pcb An example configuration (TPD directly connected to J2 of Wilba's Frontpanel PCB) can be found under hwcfg/wilba_tpd/MBSEQ_HW.V4 o the TPD display mode can now be configured in the Utility->Options menu (item #11) o added new MIOS Terminal commands: new, saveas, save, load, delete, session, sessions Best Regards, Thorsten.

Ok, somit erreicht die Applikation weder den MCP3208, noch den 74HC595 Koennte schon moeglich sein... :-/ Gruss, Thorsten.