TK.

It seems that an "off" pattern is missing... :-/ Best Regards, Thorsten.

@KUI @novski There is new hope! While stress-testing the OLEDs today (more about the app in the next days...), I found a potential flaw in the LCD driver, and managed to fix it with a plausible method. Could you please check if this app is working at your side? -> http://www.ucapps.de/tmp/mios32_test_app_lcd_ssd1306_LPC1769__20131215.zip @KUI: if you would try this with a local build, just update your SVN repository Best Regards, Thorsten.

Since you are only shifting 16 bits, I've to doublecheck: you've only connected 2 74HC165 SRs and 2 74HC595 SRs together, right? Or do you have more than 2 SRs per module? How exactly do you want to send the clock and latch/load signals? And why are you not using a common core module, running with MIDIO128 or similar, for the test? This has the advantage, that you would test the whole system. Best Regards, Thorsten.

Or even worse: the Union Jack! ;-) Best Regards, Thorsten.

Hier ist ein einfaches Konfigurationsbeispiel fuer 4 Baenke: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmf_banks.ngc Das MBHP_MF_NG Modul ist fuer das Motormix Protokoll konfiguriert (!), und kommuniziert in diesem Beispiel ueber OUT3/IN3 (-> J5.A6/A7) Falls Du es erstmal ueber einen "normalen" MIDI IO betreiben moechte, dann koenntest Du auch MIDI IN2/OUT2 nehmen: # we've a single MBHP_MF_NG module with 8 motorfaders # It has to be configured for Motormix protocol! MF n=1 enabled=1 midi_in_port=IN2 midi_out_port=OUT2 chn=1 ts_first_button_id=1001 config_port=USB3 LEDs bei 50% schalten: das geht bspw. mit fwd_id=LED:<hw_id>, also: EVENT_MF id= 1 hw_id= 1 bank=1 fwd_id=LED:1 type=CC chn= 1 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" EVENT_MF id= 2 hw_id= 2 bank=1 fwd_id=LED:2 type=CC chn= 2 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" EVENT_MF id= 3 hw_id= 3 bank=1 fwd_id=LED:3 type=CC chn= 3 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" EVENT_MF id= 4 hw_id= 4 bank=1 fwd_id=LED:4 type=CC chn= 4 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" EVENT_MF id= 5 hw_id= 5 bank=1 fwd_id=LED:5 type=CC chn= 5 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" EVENT_MF id= 6 hw_id= 6 bank=1 fwd_id=LED:6 type=CC chn= 6 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" EVENT_MF id= 7 hw_id= 7 bank=1 fwd_id=LED:7 type=CC chn= 7 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" EVENT_MF id= 8 hw_id= 8 bank=1 fwd_id=LED:8 type=CC chn= 8 cc=16 range=0:127 lcd_pos=1:1:1 label="^std_mf" Es sollte sogar moeglich sein, die LEDs mit den Fadern zu dimmen! :smile: EVENT_LED id=1 dimmed=1 EVENT_LED id=2 dimmed=1 EVENT_LED id=3 dimmed=1 EVENT_LED id=4 dimmed=1 EVENT_LED id=5 dimmed=1 EVENT_LED id=6 dimmed=1 EVENT_LED id=7 dimmed=1 EVENT_LED id=8 dimmed=1 Gruss, Thorsten.

I couldn't explain it better! :) This thread is now linked to the user manual as an extension to the (too short) Guide Track introduction. Best Regards, Thorsten.

You could start MIOS Studio with: MIOS_Studio --gui_height=550 to overcome this. In addition, you could disable the virtual keyboard (for example) the following way: MIOS_Studio --gui_height=550 --gui_hide_keyboard All available commandline options are displayed with: MIOS_Studio --help Best Regards, Thorsten.

Hallo, das Display ist kompatibel, selbst vom Pinning her. Kann es sein, dass Du den Stecker falschrum reingesteckt hast? In diesem Fall liegt naemlich das Backlight-Display direkt zwischen 0 und 5V, und wuerde deshalb hell leuchten. Gruss, Thorsten.

What do you mean with "live" version? Do you mean the sources that I used during a certain release? Then just check the SVN log entries. E.g. the last release was based on r1832 of the repository, but when you check it with the latest r number, you won't find changes. Juce: just unpack tools/juce/unpack_me.zip Only use this juce version, don't try another one because it might be incompatible. Best Regards, Thorsten.

The availability is not so good as for the smaller STM32F4-DISCOVERY kit. See http://www.findchips.com And I don't want to be responsible for a sellout of the last available boards ;-) Best Regards, Thorsten.

No, this display is definitely not KS0108 compatible. E.g. it would require 8 CS inputs for 8 segments... such a higher number doesn't make much sense, therefore KS0108 isn't used for large display sizes anymore. The display interface looks more like a T6369c Best Regards, Thorsten.

Great music, great pictures! :thumbsup: Best Regards, Thorsten.

Do you have the datasheet of such a display? Best Regards, Thorsten.

Here some first updates for testing at your side: -> http://www.ucapps.de/mios32/midibox_seq_v4_080_pre2.zip o it's now possible to control the track steps with CCs. Each track has a dedicated CC which has to be configured in the MIDI->Ext.Ctrl page. o it's now possible to turn off the track clock by enabling the new "Manual" mode in the DIVIDER page. Once enabled, a step will only be played if: - manually triggered in the MANUAL page - set with the new CC based step control feature (MIDI->Ext.Ctrl page) Use cases: - predefined MIDI events, stored in the track layers, should be manually triggered (and not sequenced). E.g. in conjunction with a sampler, you could set each step to a note which "fires" a certain sample. In addition, you can fire CCs, Program Change, Aftertouch etc. from the MANUAL page. - the track should be controlled from an analog modulation source (e.g. a sawwave from a LFO). MIDIbox SEQ doesn't provide analog inputs, so that an external CV-to-MIDI interface is required. Note that this interface also has to scale the CC value over the desired step range. If the modulation source should sweep over step 1..16, then the CV-to-MIDI interface has to scale down the converted value to the CC value range 0..15! Note that the scaling over track length that I mentioned earlier doesn't take place since it's problematic in some cases (e.g. if the value slowly sweeps over the CC value range). Instead, scaling has to be done externally. In MBNG you would do this with: # in MIDIbox SEQ V4, we've configured CC#16 for Step Control in the MIDI->Ext. Ctrl page # AINSER8 hardware AINSER n= 1 enabled=1 muxed=0 cs=0 resolution=7bit # Track 1: control step 1..16 EVENT_AINSER id= 1 type=CC chn= 1 cc= 16 range= 0:15 # Track 2: control step 1..32 EVENT_AINSER id= 2 type=CC chn= 1 cc= 17 range= 0:31 # Track 3: control step 1..64 EVENT_AINSER id= 3 type=CC chn= 1 cc= 18 range= 0:63 # ... etc. Best Regards, Thorsten.

The T6369c has a very poor performance and requires buffering in memory. Therefore it's not part of the universal driver (it's a dedicated driver), and probably compile will fail due to unavailable RAM resources. Best Regards, Thorsten.

Yes, you can: power-off the core, press the START button in MIOS Studio, power-on the core -> the core will send an upload request and the application will be uploaded with the 1st level bootloader (which can't be overwritten) Best Regards, Thorsten.

Hi, yes It's accurately explained in the ChangeLog: Song Mode now provides a "Guide Track" which can be configured by pressing SELECT in SONG page: the length of this track defines the loop length and once the last loop has been played, all tracks will be synchronized to step 1. This allows to program breaks with a step length which is independent from the measure. The "Guide Track" now synchronizes tracks and pattern changes independent from the "steps per measure" option So, the guide track is nothing else than a "steps per measure" replacement for song steps. The length of the guide track defines the loop length for the song position, and this gives you a high flexibility. Yes. Resp. if the guide track is used, they have to match with the length of this track (which defines the measure) Best Regards, Thorsten.

Hi, the performance of the Raspberry Pi (running under Linux) isn't sufficient for MBSEQ V4. However, for simple PD based sequencers it's working: http://bit.ly/1diFL5Q Best Regards, Thorsten.

Im SysEx Kommando fehlt die <deviceID> Siehe auch: http://home.roadrunner.com/~jgglatt/tech/mmc.htm Probiere mal stream="0xf0 0x7f 0x7f 0x06 0x02 0xf7" (das funktioniert auch ohne dem MCU Protokoll...) Gruss, Thorsten.

ok - all 8 outputs will be configurable! :) Best Regards, Thorsten.

J5 is already allocated for Gate outputs, and another problem would be the bad accuracy of STM32 and LPC17 ADCs... I could support an MBHP_AINSER8 module instead, but this could affect the performance of the sequencer :-/ Therefore the usage of CCs is maybe the better approach, just use a second core for the conversion (you could also use it for other purposes as well) yes. 16 DIN pins to step the 16 tracks individually, right? If it's ok to assign a whole DOUT SR (= 8 outputs) for this function, I could easily add this. What type of clock outputs would be for interest? - PPQN/24 (DIN clock) - 64th - 32th - 16th - 8th - 4th (1 clock per bar) - 1/2 - 1 (4 bars) Since PPQN/24 is redundant (already available at J28), it could be replaced by another interesting clock - any proposal? Best Regards, Thorsten.

@John: KS0108 has a special treatment where lcd_num_x doesn't play a role. J28 always has 4 CS lines enabled. Actually it's a part of the universal driver which needs to be overworked, so that CS lines are specified with lcd_num_x However, I changed MIOS32_LCD, so that lcd_width 255 results into the actual width 256 This coding could become important in future. E.g. if there are displays which support 320 pixel, I could use the number 254 for this, etc. Best Regards, Thorsten.

Hallo Rolf, wenn Du bereits ein STM32F4DISCOVERY Board hast, koenntest Du bspw. mit diesem Tutorial direkt loslegen, einen Synthesizer zu programmieren: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F024_i2s_synth%2F MIOS32 bietet ja schon alles was man dafuer braucht. Vor allem die I2S und MIDI (USB und UART basierend), scannen von Buttons, Encodern, LEDs, verschiedene LCD typen (character oder graphisch), SD Card, usw. usw. Die Toolchain basiert auf gcc mit nanolib: http://www.midibox.org/mios32_toolchain/ Und zum Aufladen von Code, sowie zum Debuggen via printf verwendet man MIOS Studio: http://www.ucapps.de/mios_studio.html Alternativ koennte man auch mit Eclipse debuggen (falls Du eine IDE suchst, mit der man bspw. Breakpoints setzen kann, waehrend der Laufzeit Variablen abrufen kann, usw) - irgendwo gab es mal ein Thread zu diesem Thema. Welche Peripherals bietet die Atmel MCU, die nicht im STM32F4 enthalten sind? (wenn man mal vom Audio DAC absieht, doch ein externer DAC ist u.U sogar vorteilhaft, weil man die Spannungsversorgung besser gegen Stoerungen aus der digitalen Spannungsdomaene isolieren kann) Gruss, Thorsten.

Hi, what do you mean with "slave with the sammichSID" exactly? Do you mean that the external synthesizer should be synchronized on a MIDI clock, or do you expect that sammichSID sends MIDI notes (it doesn't...)? Best Regards, Thorsten.

This wasn't the upload window, but the MIDI IN monitor window... however - this message: indicates a checksum mismatch! :shocked: (see also http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fdoc%2Fmios%2Fmios_sysex_implementation.txt ) It seems that the Behringer MIDI interface doesn't work reliable! With some luck it will work when you are trying it multiple times (10..20 tries could lead to success) But I fear that you need another MIDI interface. Btw.: Behringer is already on the blacklist: http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist Best Regards, Thorsten.