TK.

Please try to upload the application again - which messages are displayed in the upload window exactly? (you can copy&paste them into this posting with rightclick->select all; rightclick->copy) Best Regards, Thorsten.

What happens if you disconnect the MIDI IN of sammichSID from the Behringer Controller (maybe it has some kind of loopback enabled?) Best Regards, Thorsten.

@IGI: if you would use the SysEx librarian of MIOS Studio, you could control the target bank Best Regards, Thorsten.

Ja, das senden von SysEx streams sollte wirklich ausreichend im Manual erklaert sein. Falls nicht, bitte einen Gegenvorschlag machen. :) Gruss, Thorsten.

Yes, it works even if the DOUT_MATRIX and DIN_MATRIX control different number of rows - they are always in sync and don't disturb each other. At least software-wise. Hardware-wise you have to expect less brightness on the LEDs if no dedicated sink drivers are used. Best Regards, Thorsten.

I like this - the style is somehow like "Kalkbrenner meets Reggae Dub"! :thumbsup: Unfortunately you stopped the video to early!

The RTFM told me, that you can control this with the VAs parameter :smile: Best Regards, Thorsten.

I remember that somebody else had similar problems, and we solved this with the "guide track" function. In order to set a guide track, press the SELECT button in SONG page and change it with GP encoder 11 - this item is only visible in song mode, not in phrase mode. The guide track will take over the control of the song step. E.g. if the selected guide track has a length of 72, the sequencer will switch to the next song position whenever these 72 steps (*loops) are processed. Best Regards, Thorsten.

I fear that this isn't possible without firmware changes, that you would have to do individually. Because I don't see a generic approach to merge multiple DOUT_MATRIX entries - on the firmware side this could (somehow) be hardcoded of course. Best Regards, Thorsten.

Hast Du Dir eigentlich schonmal den MBHP_CORE_STM32F4 angeschaut? (um mal wieder so langsam on-topic zu werden... ;-) Gruss, Thorsten.

Unfortunately there are no free ADC inputs which could be used for this purpose. There is no CC available which allows to control a step, but I could add this, especially since the MIDI CC configuration is very flexible meanwhile, so that new functions can be added without much effort at my side. Question is: how should it behave exactly? I see two possible use cases: 1) let's divide the CC value into 128/<number-of-steps> ranges. E.g. with a 16 step track: - Step 1 would be selected with 0..7 - Step 2 with 8..15 ... - Step 16 with 120..127 Whenever the CC value changes between one of these ranges, the appr. step would be played immediately 2) like 1, but the appr. step would be played with the next step clock (depending on the track divider value) Which approach would be preferred? If the trigger pulse is > 2 mS, this is feasible Best Regards, Thorsten.

Hallo Martin, MIOS Studio interpretiert die Requests als Lebenszeichen vom PIC, und meldet deshalb, dass der Query abgeschlossen ist. Die Symptome sind in der Tat merkwuerdig, da kommt auch der Fachmann ins gruebeln... :-/ Es hoert sich alles nach einem Wackelkontakt an. Der PIC sollte bspw. auf keinen Fall booten (und somit einen Request senden), wenn Du Dich ihm mit der Hand naeherst. Im Grunde ist das der eigentliche Indikator, dem Du nachgehen solltest, damit lassen sich dann evtl. auch die Ausfaelle von TEST_MIDI2 und TEST_CORE4 erklaeren (TX auf 0.4V ist nicht ok!) Du koenntest bspw. mal saemtliche Loetpunkte mit einem Finger "abtasten", und schauen, wann der PIC besonders oft neu bootet. Gruss, Thorsten.

SELECT+CLEAR is already supported by this version! :) Best Regards, Thorsten.

Yes, it somehow related to the 74HC595. I haven't found out yet, what exactly could cause such an effect. Best Regards, Thorsten.

I'm using a (best quality) SmashTV MBHP_DOUTX4 module as well for the tests, which makes it even more mysterious. > With the clock coming from J15B. I am unable to get the bootloader store function to access displays 9-16. That's plausible, because the bootloader update application ($MIOS32_PATH/bootloader/updater) has been compiled with an older lcd driver which doesn't support J15B. You could re-compile it (now where you are able to do this) to get the change. I can't give you additional debugging hints today (it's 0:30 in germany...), but for the case that you would like to continue with some software changes: - the test application is located under $MIOS32_PATH/apps/mios32_test/app_lcd/ssd1306 - the driver under $MIOS32_PATH/modules/app_lcd/universal in $MIOS32_PATH/modules/app_lcd/universal/app_lcd.c you will find the APP_LCD_SERGLCD_CS_Set() function which sets the CS lines. MIOS32_BOARD_J28_SerDataShift() is used to update the 74HC595 SR connected to J28 E.g. an interesting SW change would be following modification at !all branch in APP_LCD_SERGLCD_CS_Set() int selected_lcd = mios32_lcd_device - 8; // BEGIN mod: swap CS lines of 15th and 16th LCD if( selected_lcd == 7 ) selected_lcd = 6; else if( selected_lcd == 6 ) selected_lcd = 7; // END mod int selected_lcd_sr = selected_lcd / 8; u8 selected_lcd_mask = value ? ~(1 << (selected_lcd % 8)) : 0xff; This would swap the CS lines of the 15th and 16th display in the software If now display 16 still outputs incorrect data, you know that the problem is located at the hardware side. Best Regards, Thorsten.

I've no explanation for this. Based on the picture that you sent some postings earlier, it looks like the wrong commands are sent to the 16th CS line. Because with: > I then routed cs line for display 16 to display 15 and 16, same text and corruption on both. > I then routed cs line for display 15 to display 15 and 16, clean text no corruption on either display. you proved that the remaining signals (especially SCLK and SDA) are clean. Display 16 is handled correctly at my side. So, let's assume that there is an issue with the 74HC595 output at your side. CS16 has to be connected to pin 15 of the 74HC595, please check this first. Check also another 74HC595, who knows... :-/ Best Regards, Thorsten.

It seems that your Eclipse setup doesn't reference the right GCC version. Did you configure the PATH to this version somewhere? Another good test for the version number is following command line: arm-none-eabi-gcc --version it should return: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.7.4 20130913 (release) [ARM/embedded-4_7-branch revision 202601] Copyright © 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Best Regards, Thorsten.

V1.027 is available: MIDIbox NG V1.027 ~~~~~~~~~~~~~~~~~ o .NGR: added "set_active" command. It can be alternatively used instead of the bank mechanism to activate/deactivate events, e.g. if the same events should be activated in multiple banks under certain conditions. A demo can be found under cfg/tests/multibnk.* o it's now possible to set a static forward value independent from the actual value of the event which initiates the forwarding. E.g. with EVENT_xxx fwd_id=SENDER:1:42 the SENDER:1 will always get value 42 for additional processing o support for multiple MBHP_MF_NG modules in a chain. See cfg/test/mf_multi.ngc for a configuration example o support for Logic Control Meters Configuration example: see cfg/templates/logictrl.ngc (search for "meter") o added new GLCD fonts (provided by Pcbatterij): Inverted and Tiny. In order to test these fonts, try following commands in the MIOS Terminal: lcd %C&t@(1:1:1)Tiny Font lcd %C&i@(1:1:1)Inverted Font o fixed OSC receiver (avoided stack overflow) o various minor bugfixes Best Regards, Thorsten.

V1.4g is available: MIDIboxFM V1.4g ~~~~~~~~~~~~~~~ o fixed SysEx import issue with OP Algorithm o added presets/bank2/funkybank-v1.syx to the release package. This bank contains 128 awesome patches which have been created by Martin aka. mburch The new bank by mburch is a *must have* for all MIDIbox FM users! :) Best Regards, Thorsten.

Encoder muessen direkt an das DIN Modul angeschlossen werden, sie koennen nicht ueber eine Matrix betrieben werden. Die Motorfader sind ok, die gleichen habe ich auch (vor gut 13 Jahren gekauft...) Ich bin mir noch 100% sicher, was Du meinst, aber vielleicht hilft die Bank-Funktion weiter, mit der man mehrere Faderwerte auf verschiedene Baenke verteilen kann. Mit Hilfe von Meta Events (die man sich dann bspw. auf Buttons legt) kann man dann zwischen den Baenken hin- und herschalten. ja; kauf' Dir einfach die guenstigste SD Karte im Supermarkt (oder bei Reichelt...) Gruss, Thorsten.

MIOS is up-to-date, but the application firmware is expired (RC28 was released 2009, meanwhile we've V2.043). Many new features have been added, many bugs have been fixed (also the knob issue). We can't help you to workaround such an old firmware... The update is only possible with a MIDI interface - you've to buy one, or borrow it from a friend. Take care that the MIDI interface is not on the blacklist: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist Once you've a working bidirectional MIDI connection, just upload the setup_sammich_sid.hex file, which is part of the release package. Best Regards, Thorsten.

:-/ Are you able to swap displays? It would be interesting, if for example display 16 behaves the same way if another OLED is plucked into the socket. And another interesting test: how does it behave, if the CS line of display 16 is connected to the same 74HC595 pin, which is routed to display 15 (I would expect, that both displays show the same text) Best Regards, Thorsten.

Luke, here a firmware for testing the SELECT+COPY function: http://www.ucapps.de/mios32/midibox_seq_v4_080_pre1.zip It also copies the layer mode, so that it's (for example) possible to copy notes into a layer, which was previously configured for CC Best Regards, Thorsten.

Hi Damien, which version is installed on your sammichSID? It could be an older one... You could update it with MIOS Studio, the firmware is located in the midibox_sid_v2 package here: http://www.ucapps.de/mios_download.html That's normal, because sammichSID has only a single PIC core. Each core can handle two SID chips. E.g. in the lead engine patches you select the chip with L/R (left/right) Do you hear sound on both audio channels? Best Regards, Thorsten.

Very nice! :) Best Regards, Thorsten.