TK.

Based on very fruitful discussions about the MIDI player capabilities (see ) a new release is available now: MIDIO128 V3.011 ~~~~~~~~~~~~~~~ o USB device settings have been changed. IMPORTANT: please install MIOS32 Bootloader V1.010 before uploading the application! Otherwise code upload via USB won't work anymore! (Backup: upload via MIDI IN1/OUT1) o 4 USB ports are enabled now. Note: if your operating system still displays only a single MIDI port for USB, then unplug the USB cable and remove the USB MIDI driver in your system setup, so that the driver be installed again once the core module has been re-connected. E.g. under MacOS this can be done with the Audio-MIDI Setup application (search for "Audio" in Spotlight) o support for GM5 driver under Windows. - upload the application with MIOS Studio - close MIOS Studio - install the GM5 driver which can be downloaded from http://www.ucapps.de/mios32_download.html - start MIOS Studio -> 4 "GM5" USB ports should be visible o 4 MIDI IN/OUT ports are enabled now. Pin mapping for LPC17 (see also http://www.ucapps.de/mbhp/mbhp_core_lpc17_midi3_midi4_extension.pdf): - MIDI OUT3 is available at J5B.A7 - MIDI IN3 is available at J5B.A6 - MIDI OUT4 is available at J4B.SD - MIDI IN4 is available at J4B.SC since MIDI IN3/OUT3 allocate analog input pins, AIN Pin #6 and #7 is not available anymore! o Matrix DINs are now also inverted with the InverseDIN flag in the .MIO configuration file o support for MIOS Filebrowser, which will be part of MIOS Studio 2.4 o It's now possible to record MIDI files! Press EXIT + first softbutton (under REC) o Fast Forward and Fast Rewind are now available by pressing EXIT o rotary encoder now selects the tempo (BPM) in main page o BPM mode can be switched between Auto/Master/Slave/Lock by pressing shift button + soft button 2 "Lock" prevents tempo changes from the MIDI file. The BPM generator is always in master mode. o play modes: aside from All and Single, we've now also a "Loop" mode which repeats the selected song o first MIDI song already selected after boot o if you scroll the .MID page to the right side, you will find configuration options for MIDI ports assigned to the Rec/Play/Clock IN and Clock OUT functions o a couple of minor bugfixes [/code] Please note that the documentation at my website hasn't been updated yet! Best Regards, Thorsten.

A new release is available: MIDIboxSEQ V4L.068 ~~~~~~~~~~~~~~~~~~ o support for GM5 driver under Windows. MacOS and Linux users: just install this update, no additional changes required. Windows users: - upload the application with MIOS Studio - close MIOS Studio - install the GM5 driver which can be downloaded from http://www.ucapps.de/mios32_download.html - start MIOS Studio -> 4 "GM5" USB ports should be visible o USB device settings have been changed. IMPORTANT: please install MIOS32 Bootloader V1.010 before uploading the application! Otherwise code upload via USB won't work anymore! (Backup: upload via MIDI IN1/OUT1) o support for MIOS Filebrowser, which will be part of MIOS Studio 2.4 [/code] Best Regards, Thorsten.

I will reconsider my opinion ;) We've now a new version which fixes the USB MIDI issues under Windows, and which also allows to use the brand new MIOS Filebrowser which is part of MIOS Studio 2.4.0! :) MIDIboxSEQ V4.068 ~~~~~~~~~~~~~~~~~ o USB device settings have been changed. IMPORTANT: please install MIOS32 Bootloader V1.010 before uploading the application! Otherwise code upload via USB won't work anymore! (Backup: upload via MIDI IN1/OUT1) o support for MIOS Filebrowser, which will be part of MIOS Studio 2.4 o support for GM5 driver under Windows. MacOS and Linux users: just install this update, no additional changes required. Windows users: - upload the application with MIOS Studio - close MIOS Studio - install the GM5 driver which can be downloaded from http://www.ucapps.de/mios32_download.html - start MIOS Studio -> 4 "GM5" USB ports should be visible [/code] Your other requests are not lost, I'm collecting them before doing the next update. Best Regards, Thorsten.

In order to get a stable baseline before doing additional changes, I released Bootloader V1.010 and MIDIO128 V1.011 today! Marton's request to optionally invert matrix buttons made it into this versions, some others are postponed. Following updates can be expected in the next days: update of the MIDIO128 documentation to cover new features, and also the changed workflow with the MIOS Filebrowser which is part of MIOS Studio 2.4.0 optional, second 2x40 LCD to display additional MIDI file informations (including volume bars to visualize the channel activity) + lyrics option to transpose notes played from the MIDI file Do we still need the additional buttons? Best Regards, Thorsten.

A new MIOS32 Bootloader release v1.010 is available which finally solves the USB MIDI issues under Windows by enabling the usage of the GM5 device driver. -> http://www.ucapps.de/mios32_download.html Unfortuntely this change means, that Bootloader and Applikation have to be updated. Old application releases are not fully compatible anymore (the new bootloader can't be accessed from the old releases), therefore a cumbersome update procedure is required which is described below. I must say that I don't like such dependencies, but I don't see a more comfortable approach. Therefore it's better to initiate the major update now than never... Following steps are required for the complete update: 1) install the new MIOS32 Bootloader: upload the MIOS32 Bootloader V1.010 which is available at http://www.ucapps.de/mios32_download.html wait some seconds until the bootloader has been installed close MIOS Studio disconnect the USB cable, after some seconds connect it again. open MIOS Studio: the USB port should be found 2) install the new application release - this has to be done *after* bootloader installation! upload the new application binary which is available at http://www.ucapps.de/mios32_download.html close MIOS Studio Windows users: you should install the GM5 driver now. MacOS/Linux users: no special measure required, the legacy drivers are working great! open MIOS Studio, and select "GM5 Port 1" for MIDI IN and OUT -> communication with the core should be possible again. Windows users: note that beside of the higher robustness of SysEx transfers and better performance, the GM5 driver finally gives you multi client capabilities! This means for example, that MIOS Studio is now able to communicate with the core in parallel to other MIDI programs (like your DAW) without MIDI port access conflicts! Last but not least some troubleshooting tips for the case that an update fails: if the USB MIDI interfaces won't be found by MIOS Studio after the update, it could be that your operating system needs a bit more time than after a usual update to register the ports. It shouldn't take more than 10..20 seconds. Just open MIOS Studio again after this time. if you uploaded an old application by accident which isn't compatible to the new bootloader, you've two possibilities: either stuff the "Boot Hold" jumper J27 on your MBHP_CORE_STM32/MBHP_CORE_LPC17 module, reconnect the USB cable and reopen MIOS Studio to get direct access to the bootloader, or upload the application via traditional MIDI IN1/OUT1 Best Regards, Thorsten. P.S.: This thread is dedicated for the major updates in V1.010 MIOS32 Bootloader V1.011 an future versions are notified under again!

MIOS Studio 2.4.0 is available now It now provides a very useful filebrowser, which is supported by the latest MIDIbox SEQ and MIDIO128 releases: The "Update" button retrieves the directory structure. Once it has been read, files and directories can be selected in the directory tree. Existing files can be downloaded to your computer at a speed of ca. 40..50 kb/s. New files can be uploaded from your computer at a speed of ca. 10..20 kb/s. The edit functions allow to modify files in text or binary (hex) format, which is really helpful for quick changes on application specific configuration files without disconnecting the SD Card from the core, or enabling the MSD driver (which would deactivate USB MIDI). Have fun! :)

Yes - this handling needs proper documentation - it was the most simple way to provide separate configuration flags for all ports. It seems that I should add a loopback detection, but I'm unsure if this will really help. E.g. if transfers are stopped and you missed the message, that a loopback has been detected (which could also happen if the detection algorithm is not good enough to identify a *real* loopback), the behaviour could be confusing as well. Please ignore MSD mode, it works only properly without such issues under MacOS. Once MIOS Studio 2.4 has been released, accessing the SD Card via MIDI will be the prefered choice anyhow. :) Best Regards, Thorsten.

Cool! :) The MIDItest is the best program to test the performance under Windows. While using it, I noticed that the Tune Request event (F6) wasn't properly handled by MIOS32, it's fixed now. Here the comparison between GM5 and the MIOS32 based MIDI4x4 application (corrected version, which will be released tomorrow): GM5 ================ Results Per Message ===================================== MESSAGES Snd Rcv Snd+Rcv Message TotalTime: 539.41 ms 38188.02 ms 38727.43 ms Message MaximumTime: 0.11 ms 2.26 ms 2.26 ms Message MinimumTime: 0.00 ms 0.44 ms 0.47 ms Message AverageTime: 0.02 ms 1.22 ms 1.24 ms SysexTime: 34.42 ms 164.11 ms 198.54 ms SysexAverage: 0.00 ms 0.02 ms 0.02 ms < 1 ms: 31250 9408 9387 1 - 2 ms: 0 19546 19416 2 - 3 ms: 0 2296 2447 3 - 4 ms: 0 0 0 4 - 5 ms: 0 0 0 5 - 10 ms: 0 0 0 10 - 20 ms: 0 0 0 20 - 50 ms: 0 0 0 50 - 100 ms: 0 0 0 > 100 ms: 0 0 0 Message count: 31250 Sysex count: 157 Sysex size: 10000 Sysex passed: 10000 Message latency: 1.24 ms Total time: 67.396 sec Message jitter: 0.41 ms Message max deviation: 1.03 ms [/code] MIOS32 MIDI4x4 app: [code] ================ Results Per Message ===================================== MESSAGES Snd Rcv Snd+Rcv Message TotalTime: 891.18 ms 81831.34 ms 82722.53 ms Message MaximumTime: 0.15 ms 3.26 ms 3.29 ms Message MinimumTime: 0.02 ms 2.06 ms 2.09 ms Message AverageTime: 0.03 ms 2.62 ms 2.65 ms SysexTime: 34.81 ms 374.18 ms 408.99 ms SysexAverage: 0.00 ms 0.04 ms 0.04 ms < 1 ms: 31250 0 0 1 - 2 ms: 0 0 0 2 - 3 ms: 0 27550 26837 3 - 4 ms: 0 3700 4413 4 - 5 ms: 0 0 0 5 - 10 ms: 0 0 0 10 - 20 ms: 0 0 0 20 - 50 ms: 0 0 0 50 - 100 ms: 0 0 0 > 100 ms: 0 0 0 Message count: 31250 Sysex count: 154 Sysex size: 9999 Sysex passed: 9999 Message latency: 2.65 ms Total time: 107.233 sec Message jitter: 0.28 ms Message max deviation: 0.64 ms The increased latency is caused by the 1 mS RTOS timeslots. This is actually no problem as this constant delay can be compensated by a DAW. But it's interesting that MIOS32 has less jitter than GM5 - and this is the relevant value! :) Best Regards, Thorsten.

Hi, The HS oscillator is used. The firmware doesn't set the configuration since it's assumed that it will be uploaded via the Pdfsusb tool as described under Installation. The binary of the Microchip USB bootloader contains the configuration flags, which you could take over if you want to program the firmware without this bootloader. There are various reasons. I developed the firmware 2005 (so: 7 years ago!) under Linux. The MPLAB IDE was only running under Windows, and my computer was too slow to run it in a wine emulation (at this point of time). Later I switched to MacOS - same situation. The reason why SDCC is used: in order to define the descriptors properly without zero-padding between the "db" statements, I was forced to use a C compiler. The Microchip C compiler is not free, and I don't want that people have to spend money just to re-compile my firmware. What do you mean with "fail" exactly? Note that SDCC 2.8.0 has to be used. The GPUTILS version doesn't matter. "Proper toolchain"? Do you really want to buy an expensive compiler just to compile a small piece of my firmware? However, here the binary for 4 IIC modules: http://www.ucapps.de/mbhp/mbhp_usb_pic_v1_1_4iic.zip It really seems that you haven't read my installation instructions... By using the Microchip USB bootloader you've a perfect way to test the USB communication with an independent firmware. Best Regards, Thorsten.

Hi Gert, I've currently no bandwidth to check your setup at my side, please continue debugging! (I never tried other baudrates than the common MIDI baudrate on the LPC17 core) J14@PIC: it's enabled with the DEFAULT_TOUCH_SENSOR_SENSITIVITY in your setup file. Could it be, that you set it to 0 in your configuration? Best Regards, Thorsten.

Hallo Roman, Unterebenen werden nicht unterstuetzt! Ziel ist es, die Entwickler zu Zwingen, den Benutzern eine moeglichst flache Menue-Hierarchie zu bieten! Gruss, Thorsten. P.S.: das meine ich ernst!

You will need a MBHP_AOUT_* module, connected to J19, to output the voltage Best Regards, Thorsten.

Unfortunately it turned out, that the multi-USB port issue under Windows still wasn't solved. :frantics: Therefore I enabled MIOS32 for using the GM5 driver! This driver gives you the best performance, and especially robust SysEx transfers! Permission granted by the head of Ploytec! :) -> UPDATE: link removed, the new release is now available under http://www.ucapps.de/mios32_download.html MIDIboxSEQ V4.068 ~~~~~~~~~~~~~~~~~ o support for GM5 driver under Windows. MacOS and Linux users: just install this update, no additional changes required. Windows users: - upload the application with MIOS Studio - close MIOS Studio - install the GM5 driver which can be downloaded from http://www.ucapps.de/mbhp_usb_gm5.html - start MIOS Studio -> 4 "GM5" USB ports should be visible [/code] I really hope that this solves your USB issues under Windows! I've intensively tested this setup under WinXP and Win7 Best Regards, Thorsten.

Hi Marton, really nice to read that you were able to setup the MIDIbox without additional hints from my side! :) Inversion flag: I can add this but it will require some testing... but just to confirm, the diodes of your keyboard are soldered with the reverse polarity, right? Back to the Windows MIDI USB topic: there is no acceptable workaround for the Microsoft driver... but with the permission of Ploytec I enabled MIOS32 for using the GM5 driver! This driver gives you the best performance, and especially robust SysEx transfers! :) -> http://www.ucapps.de/mios32/midio128_v3_011_pre6.zip (Note: if you haven't done this yet, install MIOS32 Bootloader V1.009 first! This update is still required!) MIDIO128 V3.011pre6 ~~~~~~~~~~~~~~~~~~~ o Number of USB devices set to 4 again o support for GM5 driver under Windows. MacOS and Linux users: just install this update, no additional changes required. Windows users: - upload the application with MIOS Studio - close MIOS Studio - install the GM5 driver which can be downloaded from http://www.ucapps.de/mbhp_usb_gm5.html - start MIOS Studio -> 4 "GM5" USB ports should be visible [/code] I really hope that this solves your USB issues under Windows! I've intensively tested this setup under WinXP and Win7 Best Regards, Thorsten.

Hi, confirmed! The events are sent because they are not gated in Note tracks, only in CC tracks (that's intended) The actual issue is, that they are sent while you are changing the configuration, and this isn't so nice. A possible solution: confirming the new configuration by pressing the buttom below the item, similar to the CC value (that you requested some time ago). I think that this will be the best solution. No, it's still not possible to change the name of a mixer map from the control surface... ;) I'm unsure if this is really a wanted feature. From my point of view, removing sessions is a very sensible topic. Just consider that a kid is playing with your MBSEQ and removes all your sessions, because it's so easy and it's fun to clean up everything! ;) Best Regards, Thorsten.

No, the Trk. field just selects the track which should be recorded. No, with the changes you would only need to select a different track, the recording port and MIDI channel would change according to the track configuration if the new feature is enabled. Best Regards, Thorsten.

I was able to reproduce this Looks like the known multi-USB port issue under Windows is still not solved! :-( Could you please try following release: http://www.ucapps.de/mios32/midio128_v3_011_pre5.zip MIDIO128 V3.011pre5 ~~~~~~~~~~~~~~~~~~~ o Number of USB devices temporary set to 1 again o OUT4 can now be selected in all config pages [/code] USB MIDI should be available immediately without pressing buttons multiple times. (background: the '>' button sends some messages. Once enough messages are sent, Windows accepts the USB MIDI connection and continues as normal... for unknown reasons) This weekend I've the possibility to test this on a Win7 PC MSD is really hard to debug. This code hasn't been developed by myself, it's based on an example from NXP and there are some parts in the code that I don't really understand... However, the upcoming MIOS Filebrowser will help to overcome this issue! :) Not so easy, because switching between MIDI files takes so much time, that they can't be selected without the "feeling that something got stucked". Button Inc/Decs are slower (because you can't push the button fast enough), therefore you haven't noticed this performance issue. The same for FRwd/FFwd A workaround would be, that I stop the file operations when the encoder has switched to the next file (because you won't listen to a temporary selected file anyhow), but the implementation won't be straightforward. Works at my side - please check if you've enabled OUT3 and OUT4 in your .MID setup Somebody requested to make the MIDI port selection option - and your confusion might be the result ;-) Fixed Best Regards, Thorsten.

Ok, now I understand your initial posting. It isn't the problem that random patches can't be sent to the slave cores, but that they are only sent to the first selected core. Which means for example, that if SID2 and SID3 are selected, the patch will only be sent to SID2 From programmer's perspective this makes a difference. ;) Best Regards, Thorsten.

It's currently not possible, but I could add this option. It could be provided as an alternative MIDI port and channel selection in the recording page: named "Trk", which just pre-selects the same port and channel that is configured for the active track. It makes sense to handle this separately for Port and Chn Best Regards, Thorsten.

Yes, you selected the right bootloader binary. I think that I should replace the "rescan MIDI devices" option by a message box which informs the user, that it doesn't work reliable, and that it's better to restart MIOS Studio instead! It would be interesting to know, if you restarted MIOS Studio after the update, and after reconnecting the USB cable? Best Regards, Thorsten.

Here's the update: http://www.ucapps.de/mios32/midio128_v3_011_pre4.zip MIDIO128 V3.011pre4 ~~~~~~~~~~~~~~~~~~~ o USB device settings have been changed. IMPORTANT: please install MIOS32 Bootloader V1.009 before uploading the application! Otherwise code upload via USB won't work anymore! (Backup: upload via MIDI IN1/OUT1) o 4 USB ports are enabled now. Note: if your operating system still displays only a single MIDI port for USB, then unplug the USB cable and remove the USB MIDI driver in your system setup, so that the driver be installed again once the core module has been re-connected. E.g. under MacOS this can be done with the Audio-MIDI Setup application (search for "Audio" in Spotlight) o 4 MIDI IN/OUT ports are enabled now. Pin mapping for LPC17 (see also http://www.ucapps.de/mbhp/mbhp_core_lpc17_midi3_midi4_extension.pdf): - MIDI OUT3 is available at J5B.A7 - MIDI IN3 is available at J5B.A6 - MIDI OUT4 is available at J4B.SD - MIDI IN4 is available at J4B.SC since MIDI IN3/OUT3 allocate analog input pins, AIN Pin #6 and #7 is not available anymore! o support for MIOS Filebrowser, which will be part of MIOS Studio 2.4 o fixed FFwd/FRwd function o song not set back to 1.1 if song position was changed while sequencer was paused [/code] Enabling all 4 MIDI IN/OUT ports will be a test, if anybody really uses AIN Pin #6 or #7 ;-) Reminder: link to MIOS32 Bootloader V1.009: Best Regards, Thorsten.

Excellent! :) I will officially release the application updates this weekend. Best Regards, Thorsten.

Instead of storing the stream, you could just implement a counter which increments on each matching value (starting from 0xf0) till the ID is reached. Since the values are known (for you), this is the most efficient solution since it only consumes 1 byte (considered that you also pre-filter the MIDI port) Because there isn't a control surface like on the "big brother" MBSEQ V4, the channel can only be changed in the MBSEQ_C.V4 file (located in the SESSIONS/<session> directory) The parameter is called MIDI_IN_RecChannel 0 disables the function, 1..16 selects the channel No, but I could provide this as an expert option, also only selectable in a configuration file. The intention of MBSEQ V4L was to have a simple and fool-proven sequencer - than more options I'm adding, than higher the possibility that somebody isn't able to troubleshoot a non-working recording function. Therefore I'm trying to avoid this. E.g. if he assigns a different MIDI OUT channel for one of the two tracks, he would have to change the MIDI OUT channel of his keyboard (used for recording) as well. If he doesn't do this, he doesn't get any notification about this problem. In MBSEQ V4 somebody could enter the MIDI monitor page to ensure, that the MIDIbox gets at least the MIDI data (and he can also find out the channel this way) - but no way for MBSEQ V4L Best Regards, Thorsten.

It makes sense to troubleshoot this first before continuing with the LPC17 connection. One possible reason for a "crash" (resp. hang-up) could be, that there are no pull-up resistors connected to Pin RA4 and RD5 It could happen that the MB64E application tries to read from a BankStick, and if it reads an "undefined" value (e.g. 0 instead of 1) then it could wait endless since clock stretching is assumed. yes That's UART0 (internally - in the software - we are counting from 0, for the users we are counting from 1) Best Regards, Thorsten.

Thank you! I was able to reproduce the issue with this .mid file very quickly! :) An update will be available soon, first I would like to check if the MIOS32 update helps to overcome the USB MIDI issues under Windows: On success I will enable 4 USB MIDI ports for MIDIO128, which will be especially helpful if MIDI IN/OUTs should be routed to separate USB ports. Best Regards, Thorsten.