TK.

It could work this way: - Export the track into a MIDI file. - Import back from the MIDI file to another track Best Regards, Thorsten.

The router setup won't be cleared with RESET_HW, because it's not a "hardware related setup". Intention is to allow to change the event definitions without reseting the existing router configuration. Instead of re-powering the core, you could also initialize all router nodes with the default parameters (see cfg/default/default.ngc of the installation package) good catch! Please try this pre-release: http://www.ucapps.de/mios32/midibox_ng_v1_025_pre4.zip Best Regards, Thorsten.

Ok, since some other minor changes were requested anyhow, please try V1.011 The bandwidth can be configured with the ain_bandwidth_ms parameter, e.g.: Best Regards, Thorsten.

A new MIDIbox KB release is available: MIDIbox KB V1.011 ~~~~~~~~~~~~~~~~~ o support for "ain_bandwidth_ms" which allows to reduce the number of generated events over time. o added "ain_pitchwheel_inverted", "ain_modwheel_inverted", "ain_sustain_inverted" o added "ain_sustain_switch", which allows to change between switch and pot behaviour Best Regards, Thorsten.

Das trifft sich ja gut :) Es wuerde mir Umstaende machen, wenn ich das Modul selbst zusammenbauen muesste. Andererseits helfe ich gerne beim Flashen, Konfigurieren, Ausprobieren - ist ja schon ein interessantes Thema! Gruss, Thorsten.

The approach is to use one track which sends the base note for the transposer to BUS1 (in the documentation it's called "loopback track") - you can use any track for such a purpose (I'm normally using Track16) And then enable the transpose mode for the track which plays the chords. The "loopback track" should send "E, A, C, E" And the chord track should play a Minor, Minor, Major, Minor chord Advantage of this approach: other tracks can get the transposed base note as well. Accordingly there is no need to duplicate this entry. It's also better if you would like to interactively change the transposing. In addition, it could make sense to enable force-to-scale for all transposed tracks with root note C and the Major scale. In this case, you don't need to consider Major/Minor in your chord entry, because the force-to-scale mechanism will ensure this automatically (only white keys will be played, like for the Em, Am, C chords) Best Regards, Thorsten.

Please use the most recent MIOS STudio release (2.4.5) Best Regards, Thorsten.

No, because the SCS is always enabled, and it will overlay the output of the first LCD when you are pressing the EXIT button. If your configuration doesn't rely on the automated LCD line extension over multiple devices (combined LCD view), then it's ok Best Regards, Thorsten.

Problematic is, that the community still wasn't able to implement a USB and Ethernet driver for the Broadcom chip, which doesn't rely on (closed source) Linux components. Patience is a virtue... ;-) Best Regards, Thorsten.

Hallo, das sollte mit einem FSR Sensor funktionieren, das wird auch auf der weiter oben verlinkten Webseite erwaehnt. Hier eine Einfuehrung zum Thema FSR: http://learn.adafruit.com/force-sensitive-resistor-fsr Die gibts bspw. bei Conrad: http://www.conrad.de/ce/de/product/503368/Drucksensor-FSR-400-ca-10-g-10-kg und sind leider nicht billig! Ein MBHP_CORE_LPC17 waere in der tat die beste Loesung, vor allem wenn Du noch kein MIDI Interface besitzt - denn der Core laesst sich ueber USB flashen, und MIDI USB kann er natuerlich auch (neben OSC fuer Wireless... doch das ist noch ein anderes Thema) -> http://www.ucapps.de/mbhp_core_lpc17.html Als Firmware koennte man die MIDIbox NG nehmen: http://www.ucapps.de/midibox_ng.html jean-puetz-bart-angelegt ich hab' da mal was vorbereitet: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fain_fsr.ngc jean-puetz-bart-abgelegt Hiermit wird ein Velocity-Sensitives Note On event versendet Direkt am Core koennte man bis zu 6 Sensoren anschliessen. Da ich in Muenchen wohne, koennte ich Dir auch beim basteln helfen, allerdings biete ich aus Prinzip keine Fertigloesungen an. Sprich: das Core Modul und die restlichen Komponenten muesstest Du Dir selbst bestellen und zusammenloeten. Gruss, Thorsten.

Concerning the bank handling: it works as expected at my side. It don't know if this is the actual problem, but I recommend you to avoid banking for receivers, so that they are always up-to-date based on the incoming values independent from the selected bank. At the bottom of this file: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fmapmidi.ngc you will find a new example for EVENT_SENDER banks You will also notice, that I'm using a nice trick in order to save memory: a single receiver forwards to multiple senders (located in multiple banks) which are assigned to the same id. Best Regards, Thorsten.

I was able to reproduce this: the delays in the if branches caused a parser malfunction once the execution was continued. You will find a bugfix in the repository. Best Regards, Thorsten.

The SCS doesn't support 40x2 LCDs, but only 20x2 LCDs This is mainly limited by the number of available pins at J10, but also by a missing mechanism to configure the SCS layout In addition, as you already noticed, a different LCD size clashes with the LCDs connected to the other E lines. The SCS LCD has to be connected to E1, there is (currently) no way to change the LCD number for the SCS Best Regards, Thorsten.

EVENT_SENDER doesn't check for the bank selection. Ok, I can change this. And it seems that a simple possibility to map CC numbers with a single EVENT_SENDER would also be nice to have, right? But it would be difficult to map the channel as well - in such a case the usage of individual EVENT_SENDERs is a must! So - is it required to map CC *and* channel? Then the map function won't help, and you've to continue with your current approach (which will work as expected once banks are supported) Best Regards, Thorsten.

I think that I found the reason: the remote function wasn't turned of when a Note On with velocity 0 was received (which is equivalent to Note Off) This is fixed with V4L.075, please give it a try. Oh! :-/ Yes, it could be, that your drummachine isn't 100% MIDI compliant, which means that the optocoupler at MIDI IN needs more current, or that the device expects 5V based MIDI signals. There are several possibilities to overcome this issue. Most simple: add a 220 Ohm resistor in parallel to R21 (for MIDI OUT1) resp. R26 (for MIDI OUT2) to increase the current. Best Regards, Thorsten.

Interesting to know, thanks for the feedback! A new version is available: MIDIboxSEQ V4L.075 ~~~~~~~~~~~~~~~~~~ o MIDI remote keyboard function now also deactivated when Note On with velocity 0 received Best Regards, Thorsten.

Very nice! :) So - V4.075 is officially released now: MIDIboxSEQ V4.075 ~~~~~~~~~~~~~~~~~ o MBHP_IIC_MIDI working properly again on a STM32 core (issue was caused by a compiler change) o Track event configuration page: if a parameter layer is configured for CC, Pitchbender or Program Change, it's now possible to send the event manually by pressing one of the GP buttons below the controller configuration (GP10, 11, 12, 13) o MIDI remote keyboard function now also deactivated when Note On with velocity 0 received Best Regards, Thorsten.

@DIJF: is this really the track which behaves faulty? Because it seems that it doesn't play any step... @vcfool: could you please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_075_pre2.zip It has been compiled with the "old" compiler version (official MIOS32 toolchain) - I've the impression that it works better than the newer gcc Best Regards, Thorsten.

if_equal won't work this way, because each EVENT_ENC stores it's own value! It isn't possible to copy the value into ^section from a meta event, but the question is: why do you really need this? Why not using RunSection:20, and then in your .NGR file: if ^section == 20 then if ENC:67 == 0 then ... elsif ENC:67 == 1 then ... elsif ENC:67 == 2 then ... else ... endif endif Best Regards, Thorsten.

Could you please enter "track 1" in the MIOS terminal, and post the output here? Best Regards, Thorsten.

BLM_PrepareCol will increment the blm_selected_column and shift the new selection into the DOUT *while* this is done, the DINs will be shifted out, thereafter BLM_GetRow will be called. The DINs will contain the state of the previous (!) selection. Therefore "blm_selected_column-1" The & 0x3 applies a mask, so that the resulting value is 0, 1, 2 or 3 (so, it also takes care for the wraparound) Best Regards, Thorsten.

Fortunately I was able to reproduce this! :) It happens due to a compiler change which generates faster code - too fast for the STM32 IIC driver! Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_075_pre1.zip Best Regards, Thorsten.

Nice colour! (which especially points out, that this MIDIbox was built in the Netherlands! ;-) Best Regards, Thorsten.

Instead of ^value, you could retrieve a value also from a (id) or (hw_id), e.g. (id)ENC:1 In the example above: yes, with the first encoder. Best Regards, Thorsten.

The remote function should only be active as long as you are pressing the C7 key, and it should be deactivated by releasing the key. Can you confirm this behaviour? you mean via remote function? It should work with the latest MBSEQ V4L release (V4L.073 and higher, after it has been overworked by Martijn) hm... thanks for the input, this has to be considered of course... Best Regards, Thorsten.