TK.

ok for me :) Best Regards, Thorsten.

Hi, in MIOS8 (not MIOS32) SysEx messages are forwarded to the MPROC_NotifyReceivedByte hook. In order to forward an incoming realtime event, write: ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a MIDI byte has been received ///////////////////////////////////////////////////////////////////////////// void MPROC_NotifyReceivedByte(unsigned char byte) __wparam { if( byte >= 0xf8 ) MIOS_MIDI_TxBufferPut(byte); } [/code] Best Regards, Thorsten.

I canceled this plan because when you look on existing iPad sequencers today, you will quickly notice that the user interfaces are superior compared to that what I could ever achieve. It isn't really worth the effort anymore. Instead I'm now going the Lemur route and design user interfaces with this App, see also: Since the sequencer kernel is running on a MBHP_CORE_STM32 or MBHP_CORE_LPC17 module, we can expect best MIDI timings - and this is one topic which makes the MBSEQ (and could never be achieved with an iPad) Best Regards, Thorsten.

Yes, seems to be an upload problem, check the messages in the upload window, probably you are getting checksum errors or no response (timeout?) The most simple way to check the DIN/DOUTs is via the MIDIO128 application as described here: http://www.midibox.org/dokuwiki/doku.php?id=home:mbhp:module:din But first you need to upload MIOS8 successfully before MIDIO128 can be uploaded. MIDI troubleshooting guide: http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

Hi, I'm currently working together with kogz23 on a new MB808 baseboard + frontpanel PCB (combined) which will provide individual velocity levels for the TR9090 project. The velocity levels will be controlled by additional DOUT shift registers + a resistor network (similar to the original TR909 design). Since the number of DOUTs is limited to 16 maximum, only 11 velocity outputs will be available, but I think that this is acceptable for most cases (e.g. Open/Closed HH can be shared) Once I got my hands on the PCB, I will update the MB808 firmware accordingly. The MBSEQV4 firmware can handle individual velocities, but only via an AOUT module (expensive! And only 8 channels are available). The DOUT solution is inexpensive, and it's done like in the original TR909 design. Adapting the MBSEQV4 for the MB808 user interface is too much work, therefore I will only enhance the existing PIC based MB808 firmware. I guess that you will like this enhancement? Because you won't need to build a new MIDIbox, just add some 74HC595 :) Best Regards, Thorsten.

Let's check the quality & service: (for 3 boards = 17 EUR per board) Best Regards, Thorsten.

MBSEQV4L is based on the MBSEQV4 firmware, accordingly all features which are described in the MBSEQ User Manual are available, but most of them are just not accessible... ;) When you search for "clock divider", you will notice that such a function is already part of the firmware. The parameters are stored in the patch structure, individual dividers can be selected for each sequence (resp. even for each track), and Triplet dividers are supported as well. Making them accessible is a good idea, but I doubt that the double-usage of the Master button is practical, because you will toggle between Master/Slave mode whenever this button is pressed. This means in other words, that your sequencer will switch to another tempo (or even stop if no MIDI clock is received) whenever you press the Master button to change the divider settings. So, which button would be better suitable? Or would you prefer to replace one button which normaly isn't used (like RecArm) by this function, configurable in the HWCFG file? And which divider presets should be assigned to the 16 GP buttons? Best Regards, Thorsten.

You would have to replace the 7805 by a switched voltage regulator due to the high voltage (48V). Or you would have to modify the ethernet cable. Details: http://tuxgraphics.org/electronics/200903/hobby-poe.shtml Best Regards, Thorsten.

Hm.... with such a great service it could make sense to provide optional .brd files for MBHP module variants, such as DINX1, DOUTX1 and a mixed DIN/DOUT board. If somebody needs such a downstripped PCB, he could just order it here. Best Regards, Thorsten.

Es liegt am 8 MHz Quarz: das MIDI Protokoll verlangt nach einer festen Baudrate von 31250 Baud. Mit 8 MHz waeren es nur noch 25000 Baud, und deshalb klappt die Kommunikation nicht mehr. Doch immerhin weisst Du nun, woran es lag. Loete doch nochmal den 10 MHz Quarz ein, vielleicht war es wirklich nur ein Kurzschluss. Und funktioniert eigentlich noch der alte PIC? Falls nicht, dann bitte supervorsichtig sein. Aus irgendeinem Grund hast Du ihn zerschossen, und das sollte kein zweites Mal geschehen! Falls Du fuer die neuen PICs keine weitere Verwendung findest, kannst Du sie uebrigens auf dem Flohmarkt verkaufen. :) Gruss, Thorsten.

Great! I love such quick challenges (when I have the time...) :) Yes, the prescaler value doesn't matter in slave mode. And I found a copy&paste error in the MIOS32_SPI driver which caused that J8/9 wasn't working correctly anymore (fixed, please update the repository) Best Regards, Thorsten.

P.S.: I improved the demo apps to cover your usecase. In the SPI_Callback routine of spi_j16_slave_dma received data will be copied into a second buffer (rx_buffer) to ensure consistent values while new data is received. The data_received counter is used to notify new values to TASK_SPI_Handler Best Regards, Thorsten.

I think that in this case it would be better if you would integrate the encoder handling by yourself - a nice exercise to learn programming :) The jitter is normal, the ADCs of LPC17 are really bad, I don't like them. This is also related to the LPCXPRESSO design, because the ADC supply input is directly connected to digital supply. In future MIDIO128 will support the new MBHP_AINSER64 module (see ) which delivers much better conversion results. It isn't really an error, but you are right that it makes sense to use a lower note by default. I will change this in the next release. It means, that events are also sent via ethernet (if enabled). The supported protocols are explained here: http://www.ucapps.de/midio128.html (search for keywords "Supported OSC Packet Formats" My opinions about OSC are written down here: http://www.ucapps.de/midibox_seq_manual_osc.html For MIDI over Ethernet I wrote a proxy, but currently it only works on a Mac. But you could also ask the developer of the organ emulation that you are using to integrate OSC support. The "j" in "jOrgan" sounds like it's based on Java, and Java has already an integrated OSC library. Accordingly it should be trivial to add such a feature to jOrgan, so that it can be accessed via Ethernet. Best Regards, Thorsten.

I'm glad about your video as well - seeing a MIDIbox in action is probably the same feeling like parents have when they watch their kid performing in a school theater. ;) And your music is really cool! Best Regards, Thorsten.

Great that you got it working first time! :) Yes, it's normal that the tempo is not part of the pattern, because usually it would be disturbing if the tempo changes when you are switching to another pattern. Is this really important? I'm sure that most users wouldn't like this option. In order to delete a note of a track, just enter the Trigger page and disable the step. The same can be done from the Step and Live Recording page. Best Regards, Thorsten.

Am besten waere wohl die MIDIO128 V3 Applikation geeignet, zumal sie bis zu 16 Tastatur-Matrizen ansteuern kann (Du benoetigst nur zwei davon, somit auch nur zwei DOUT und zwei DIN Shift Register), und weil sie dank USB kein externes MIDI Interface benoetigt. Gruss, Thorsten.

I did some experiments today and got SPI slave transfers working! :) The point is, that input pins have to be configured for alternative function, and not for GPIO mode, because the SPI peripheral controls the direction. I hacked the slave mode into the existing MIOS32_SPI driver, so that you can use it without accessing the SPI peripheral directly. Just update your repository! This directory contains the test applications that I used: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmios32_test%2Fspi_master_slave%2F spi_j16_master: running on a core to send 16 bytes in master mode spi_j16_slave_polling: running on a second core to receive 16 bytes in slave mode via polling method (not recommended, only for debugging) spi_j16_slave_dma: running on a second core to receive 16 bytes in slave mode via DMA Note that I also fixed the callback bug - it was important to enable the DMA channel before configuring SPI Best Regards, thorsten.

Yes, this is the best solution: because: - common users don't own a JTAG interface anyhow - LPC-Link can still be connected (although it will probably never be used anymore once the MIOS Bootloader has been programmed) Best Regards, Thorsten.

Danke fuer den Input, gut zu wissen! Vielleicht kommt es zu einem Buffer-Overflow im MIDI Treiber (auf PC Seite). @Sascha: tritt das Problem auch dann auf, wenn "Slow Delay" auf (bspw.) 50 mS statt 10 mS steht? Gruss, Thorsten.

Tja, haettest Du gleich erwaehnt, dass Du die MIDIO128 Applikation verwendest, haette ich Dir erst gar kein Beispiel zusammenbasteln muessen... In mios32_config.h folgendes eintragen: #define MIOS32_USB_MIDI_NUM_PORTS 1 [/code] aendern in: [code] #define MIOS32_USB_MIDI_NUM_PORTS 4 #define MIOS32_UART_NUM 4 weitere Aenderungen in der Firmware sind nicht notwendig, die Forwarding-Regeln kannst Du direkt im integrierten MIDI Merger einstellen (entweder am CS, oder Du editierst das DEFAULT.MIO file) Nein, hatte ich noch nicht. Windows? Vielleicht ist das ein Problem in der Juce Library, ich weiss allerdings nicht, wie man die effizient unter WIndows debuggen koennte... (bin Mac User und der PC steht im Keller) Gruss, Thorsten.

there are two things which have to be considered: although the file reader allows values in decimal or hexadecimal format, the file writer will always use hexadecimal format (values starting with 0x) - this could be confusing. Another important thing - and this is what probably was wrong - you have to save your changes, they won't be automatically updated on SD Card. yes, correct! :) I could add simple support for encoders (sending various CC formats including inc/dec) to the firmware. In long term the upcoming MIDIbox NG will support similar features, but in distance to MIDIO128 it will have better capabilities to parse and send incoming/outgoing MIDI events (including SysEx and NRPN support). Of course! Following tutorials describe the details (read the previous tutorials to understand the basics): http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F014_enc_relative%2F http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F015_enc_absolute%2F Best Regards, Thorsten.

Pin 1 of J15 (Vs) goes to Pin 1 of the LCD (pin is typically named Vss) See also this datasheet for comparison: http://www.reichelt.de/index.html?;ACTION=7;LA=3;OPEN=0;INDEX=0;FILENAME=A500%252FLCD202a_Serie%2523DIS.pdf;SID=15vo22oqwQAQ8AAAh4G6Efffe41de1baa00d31b6190feb346e108 Best Regards, thorsten.

No, all parameters are stored in the same file once you save it with the new firmware (from the CS or with MIOS Terminal) Don't worry, your old setup won't be overwritten, it will only be enhanced by the new tables. I changed the format as mentioned in a later posting. all tables are stored in the same .MIO file, in fact the complete configuration is stored in this file. It's possible to use different .MIO files for different configurations (if you want to use the same MIDIO128 core for different purposes, e.g. sending different MIDI events...), but I guess that this is a topic you haven't asked for. I would propose that you try out the proposed procedure to see what I mean, because I think that things become more obvious if you would just follow my instructions before asking details. Your questions confuse me a bit as well, and make it difficult to give you the right directions. If a proposed step doesn't work for some reasons, please tell me which one, otherwise it will be hard for me to guide you remotely. The DIN/DOUT configuration of the 8bit based core is still stored in the PIC flash like before, it isn't stored in a .MIO file. What do you mean exactly with devices? Do you mean for different matrices/buttons/LEDs connected to the DIN/DOUT chain of the LPC17 core, or do you mean the configuration for multiple core modules? Best Regards, Thorsten.

Servus, mir faellt gerade ein, dass Deine Mail (neben vielen anderen) noch unbeantwortet in meiner Inbox liegt, da ich vorher noch etwas vorbereiten und testen wollte... Hier findest Du nun die usb_midi_4x4 Applikation: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fmisc%2Fusb_midi_4x4%2F Sie oeffnet 4 USB Ports zu den 4 MIDI IN/OUTs. Ueber den 3ten USB Anschluss kannst Du das MBHP_MF Modul direkt kontaktieren, kalibrieren und auch die Firmware updaten (es wird irgendwann eine neue Version mit zusaetzlichen Protokollen geben) Sag bitte bescheid, falls es Probleme mit dem Kompilieren der App gibt, dann erstelle ich Dir ein binary... Gruss, Thorsten.

There is no enter function, changes will take place immediately. Just select the next matrix by selecting the first item in this page and increasing the number. The only way is to delete the DEFAULT.MIO file on SD Card - thereafter reboot the MIDIbox. Since changes will be taken over immediately, there is no reason to go back to the main menu. Yes, it's the content of your .MIO file, but you should edit it directly on SD Card. You can do this from your PC. Enter MSD mode ("msd on") so that the SD Card will be mounted (note that thereafter MIOS Studio won't receive any MIDI messages anymore until the SD Card has been unmounted and the MIDIbox has been rebooted) If you own a SD Card reader, you could also use such a device instead of "MSD" mode. Read the SD Card with your PC. No, you can also enter a new name for the file before storing it. Hard to solve this riddle ;) >> 7. The characters on the bottom row on the LCD are missing the tops of the letters. The LCD is a 20x4 rather then a 20x2. How do you go back and reset the LCD initial settings? This seems to be a defect (I remember your "accident": pins were reversed), because it can't be controlled via software. >> 8. lastly, is there a way to dump the mios term list to the printer/ Right-Click -> Select All Right-Click -> Copy Open a Notepad Paste the content into the notepad Print the content Best Regards, Thorsten.