TK.

Hallo Peter, die 2.2k Fader werden funktionieren; vielleicht sogar besser als 10k Potis weil die Spannung stabiler ansteht als bei einem hoeheren Widerstandswert. Als naechstes muesstest Du nun MIOS, und anschliessend die MIDIbox64 Applikation mit MIOS Studio aufspielen. Gruss, Thorsten.

Grandiose! This performance really deserves an entry in the MIDIbox Blog! I really like the unusual combination of instruments and the way how you presented it - let me know once you've your first gig in south germany! :) Best Regards, Thorsten.

What happens if you call this command line directly: perl gen_inc_file.pl project_MBHP_CORE_STM32.bin mios32_bsl_MBHP_CORE_STM32.inc mios32_bsl_image mios32_bsl If this doesn't help, just write down the required changes and I will create the binary for you. Best Regards, Thorsten.

If you've luck the port names can be changed somewhere in the registry (just open "reged" and search for the name which should be changed) They can't be defined in the descriptor. Best Regards, Thorsten.

Hi, this #define is locally declared in mios32_spi.c, since it isn't (normally) used somewhere else. So: you have to copy&paste the #defines from there into your hardware.c file It's defined in the stm32f10x_dma.h file which is provided by ST: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fdrivers%2FSTM32F10x%2Fv3.3.0%2FSTM32F10x_StdPeriph_Driver%2Finc%2Fstm32f10x_dma.h Also when this flag is set for a channel which is doing a SPI->RAM transfer? Note: I'm using two channels: one channel for RAM->SPI (TX), and another for SPI->RAM (RX) transfers. The callback function should be called on a "RX" interrupt, but why is the interrupt triggered before the actual SPI->RAM access happened? This seems to be odd! Best Regards, Thorsten.

There are several approaches to handle this properly (e.g. "configure" mechanism or other makefile generators), but they require some time consuming doc reading to understand the setup. My proposal: If you want to handle this for a small project with only a small number of files, the most simple solution would be to write the required commands into a shell script. Best Regards, Thorsten.

Ok, dann probiere mal diese Firmware aus: http://www.ucapps.de/mios32/midibox_seq_v4l_055c.zip Der Controller Modus wird mit MIDI Chn+Mute aktiviert. Die unteren "Page" LEDs fangen dann an zu blinken um den Spezialmodus zu signalisieren. Die meisten anderen LEDs haben keine Funktion. Master/Tempo/Stop/Play funktionieren auch weiterhin im normalen Sequenzer Modus. Der Sequenzer wird auch nicht angehalten... weil die Controller Daten ueber MIDI OUT2 ausgegeben werden, wo ja (standardmaessig) sowieso keine Sequenzen rauskommen, sondern nur der MIDI Clock. Vorteil: der Sequenzer kann weiterhin ueber USB/OSC/MIDI OUT1 spielen, waehrend der MAQ16/3 ueber OUT2 einen MIDI Clock erhaelt, sowie seine Controller Daten. Gruss, Thorsten.

Die Anpassung sollte problemlos machbar sein. Doch wie moechtest Du zwischen den Modi umschalten? Spezielle Tastenkombination? Wenn ja: welche? Gruss, Thorsten.

The warnings can be ignored. For the perl part I fear that it will only work under Linux or MacOS. Expert tip: you could install Ubuntu on a virtual machine, such as Virtual Box: https://www.virtualbox.org/ By putting the MIOS32 svn tree on a shared drive, the Windows based MIOS Studio version can access the new build! :) Best Regards, Thorsten.

ok! Best Regards, Thorsten.

Very cool! Great to know that this simple method works! :) Best Regards, Thorsten.

I remember that I wanted to display the received BPM tempo rate, but haven't added the appr. extension into the seq_bpm driver yet. Once it's available, the "SLA" indication wouldn't be required anyhow :) Best Regards, Thorsten.

Which Operating System? Best Regards, Thorsten.

Happy Birthday Peter! Unfortunately I missed to record a birthday song early enough, so take this as replacement ;) Best Regards, Thorsten.

Since you asked for this: the configuration is stored on SD Card, so that you can prepare multiple "patches" :) Please try following beta (untested) and give feedback: http://www.ucapps.de/mios32/midio128_v3_005b.zip The new "mapped" mode has to be enabled explicitly in the matrix configuration (-> M8x8 menu). Once enabled, you can configure individual MIDI channels and notes for each pin. If you haven't built the Control Surface, you will get a template by typing "save template" in MIOS Terminal. In the MATRIX line select mode 1: #MATRIX;Number;USB1;USB2;USB3;USB4;IN1;IN2;IN3;IN4;RES1;RES2;RES3;RES4;OSC1;OSC2;OSC3;OSC4;Mode;Chn;Arg;DIN_SR;DOUT_SR MATRIX;1;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;0;0 [/code] This enables the map below: [code] #MATRIX_MAP_CHN;Number;Row;C1;C2;C3;C4;C5;C6;C7;C8 MATRIX_MAP_CHN;1;1;1;1;1;1;1;1;1;1 MATRIX_MAP_CHN;1;2;1;1;1;1;1;1;1;1 MATRIX_MAP_CHN;1;3;1;1;1;1;1;1;1;1 MATRIX_MAP_CHN;1;4;1;1;1;1;1;1;1;1 MATRIX_MAP_CHN;1;5;1;1;1;1;1;1;1;1 MATRIX_MAP_CHN;1;6;1;1;1;1;1;1;1;1 MATRIX_MAP_CHN;1;7;1;1;1;1;1;1;1;1 MATRIX_MAP_CHN;1;8;1;1;1;1;1;1;1;1 #MATRIX_MAP_EVNT1;Number;Row;C1;C2;C3;C4;C5;C6;C7;C8 MATRIX_MAP_EVNT1;1;1;0x30;0x31;0x32;0x33;0x34;0x35;0x36;0x37 MATRIX_MAP_EVNT1;1;2;0x38;0x39;0x3A;0x3B;0x3C;0x3D;0x3E;0x3F MATRIX_MAP_EVNT1;1;3;0x40;0x41;0x42;0x43;0x44;0x45;0x46;0x47 MATRIX_MAP_EVNT1;1;4;0x48;0x49;0x4A;0x4B;0x4C;0x4D;0x4E;0x4F MATRIX_MAP_EVNT1;1;5;0x50;0x51;0x52;0x53;0x54;0x55;0x56;0x57 MATRIX_MAP_EVNT1;1;6;0x58;0x59;0x5A;0x5B;0x5C;0x5D;0x5E;0x5F MATRIX_MAP_EVNT1;1;7;0x60;0x61;0x62;0x63;0x64;0x65;0x66;0x67 MATRIX_MAP_EVNT1;1;8;0x68;0x69;0x6A;0x6B;0x6C;0x6D;0x6E;0x6F Best Regards, Thorsten.

The V2A function doesn't (resp. can't) mirror the SID internal VCA envelope, it only transports the patch volume setting to the AOUT channel. If you want to control the VCA from an envelope, you have to link ENV1 or ENV2 to volume via modulation matrix. The VCA offset level should be controllable with the CFG->Vol parameter, can you confirm this? Best Regards, Thorsten.

The tracklength was always re-initialized, but it shouldn't be a big problem to save & restore the previous setting in a future firmware version. It definitely makes sense! An automatic store which doesn't lead to unexpected results is too complicated... use copy to make a backup, use paste to revert the backup. Note that MBSEQV4L already stores the copy buffer of all 16 tracks on SD Card. Fur future MBSEQ V4 release I'm planning to do the same, since this method saves some RAM and works fast enough. This will make the Multi Copy function obsolete as well (than less special modes, than better...) Thereafter the free RAM could be used for other purposes :) Best Regards, Thorsten.

This application only works with my own hardware (e.g. which has a graphical 240x64 display), and it isn't configurable yet. My plan is to integrate the LC handling into the upcoming MIDIbox NG firmware and make it better configurable (e.g. with a config file stored on a SD Card) But I want to finish some other projects before starting with this one. Best Regards, Thorsten.

Note that you don't need "iConnect" or any other MIDI hardware device. MIDI data is transmitted through the Lemur Daemon, which is running on a computer (Mac or Windows PC). Alternatively, MBSEQV4L can directly communicate with the iPad via Ethernet. Best Regards, Thorsten.

Great idea! Now I know how to stuff my second PCB :) Best Regards, Thorsten.

Yes - very nice video which demonstrates nicely the possibilities! :) Best Regards, Thorsten.

Yes, but only for MIOS32 based cores. The accuracy is much better, and the wiring is simpler than with the old MBHP_AIN modules (just a serial connection between J19 and the MBHP_AINSER64 module(s)) yes yes! Meanwhile I think it would be better if I just order two cheap prototype boards at Olimex. When all checks passed, the PCB will be available in SmashTV's Shop (I'm sure ;)) Best Regards, Thorsten.

Yes, in theory it's possible to handle BLM functions with a controller. It would be difficult with a common MIDI keyboard, as the rows are mapped to Note Number 0..15 of MIDI Channel 1..16 It would also be important that the controller is able to send a SysEx string in order to enable BLM mode, and it has to send a special key combination in order to select pattern mode (because grid edit mode is selected by default) Best Regards, Thorsten.

Da Du ja bereits die MBSEQV4L Hardware besitzt, und die CPU noch genuegend Freiraum laesst, waere es in der Tat am geschicktesten, wenn man einen simplen Controller Modus in die Firmware einbauen wuerde. Zumal es dann auch mit dem MIDI Mergen einfacher wird, und es mit dem MIDI Clock keine Probleme gibt. Man koennte sogar soweit gehen, dass man am bisher ungenutzten J8/9 Port bis zu 4 MBHP_DINX4 und 4 MBHP_DOUTX4 Module anschliesst... doch die Verwendung der vorhandenen Tastatur-Matrix waere auch kein Problem. Ich muesste halt nur wissen, welche CCs von den entsprechenden Tasten gesendet werden sollen, und wie Du zwischen den Modi wechseln moechtest. Gruss, Thorsten.

It sounds like the noise is coming from the LED switching matrix, this could be the result of a certain coupling between the 5V and +/-12V voltage domain. Try the following: - ensure that the ground of the audio jacks + the OPL3 board is directly connected to the ground of the PSU (and not to the core module) - add 100 uF caps between ground an the -12V and +12V supply input of the MBHP_OPL3 module (take care for the polarity!) - if this still doesn't help, add 10 Ohm resistors in serial between the +12V and -12V output of your PSU and the appr. MBHP_OPL3 inputs, this helps to decouple the noise as well! Best Regards, Thorsten.