Search the Community

Hi, for the past few weeks I have been looking at development boards as a base for developing audio/music projects. I almost decided on an STM32F7 discovery board until I found out about the MIDIbox NG. This board with its STM32F4 module looks ideal for what I want to do but I have two major questions before I can decide. I'm currently trying to learn as much as I can about MIOS and trying to find related threads on this forum but in the mean time all the help would be greatly appreciated, thanks!   1) Can I use a capacitive touch screen with the MIDIbox NG ? The projects I want to develop will make use of capacitive touch displays from 4.3” up to 7”. Either directly driven from the board or by using an intelligent display like those based on FTDI's EVE or Nextion. But I can't find any example of this, which makes me wonder if it is possible at all ? Would this mean I should write my own driver for MIOS for the screen, or could I use existing drivers and STM32 libraries for this, or even integrate GUI frameworks like µGFX, touchGFX or embedded wizard, etc .. with MIOS ? And how difficult would that be ? Or is MIOS not really designed for this and should I better look into MPU/Linux based solutions?     2) From what I understand so far, MIOS is mainly a MIDI control/processing OS, but how suited is it as a base to develop your own synth for instance? Are there any limitations or can you basically do anything you could do on a barebone STM32 board and thus use all its code examples, libraries, dev tools, toolchain ,etc ? I guess what I'm asking is, how well does MIOS and it's amazing features integrate with your own code or can you only use API functions? How transparent is it and does it impose limitations ?   Are there currently projects like these (synths, Eurorack modules, etc ..) that are based on MIDIbox that I could check out to get an idea what is possible? (I've been looking at the MIDIbox gallery and there are some truly extraordinary devices, but most seem to be controllers and I haven't yet found anything with a touch GUI)   Thanks!

Hi, I'm want to buy 4 pre-programmed PIC18F4685  for my new SID synth. Is there still any place online or anyone in the community interested in selling? Best Frank

Hi TK,   In midi-ox, it shows me C-1 with value 0x18 and in MIOS-Studio it shows me C-0 with a value of 0X18. Traktor C-1 has a value of 0X18. See attached photo.   Marco.

Hi all, I am facing a very, very strange problem with MIOS Studio under Windows 10. I have created an application using Eclipse with MIOS32 on my Win10 machine, but when this application is loaded in the STM32F407 via MIOS Studio, I loose the USB connection between MIOS Studio and the MBHP. I thought first it was my application, but when I upload it with MIOS Studio on a XP machine, the USB connection works Here are the steps I follow : - installation of MIOS Bootloader V1.0.18 on the MBHP using ST LINK - I start MIOS Studio 2.4.6 : the USB MIDI port appears and MIOS Studio displays the bootloader message - I select the HEX file compiled from Eclipse and upload it into the board : application is uploaded correcly. MIOS Studio looses the USB connection when the STM32 restarts (normal behavior up to now) - if I scan now the MIDI devices on the computer : no more MIOS32! I can try anything from disconnecting USB, power supply, etc... It never appears again I then reloaded the bootloader using ST LINK : USB connection to MIOS Studio works again. At this level, I thought it was an error on my side, blocking USB. I connect now the MBHP to a WinXP machine and I take the HEX file compiled on the Win10 machine. The bootloader appears as expected and I am able to upload the HEX file into the MBHP. But now, when the MBHP restarts (with the application compiled on Win10 machine), it works perfectly with MIOS Studio under XP! If I connect it to the Win10 machine again : fail! So the problem is clearly not in my code, nor in the toolchain being run under Win10. Did somebody already saw that?   Benoit

I have built two CORE 8 and seven DIN cards from Smash TV.  A friend laid out my Hex files and others and walked me through loading them into my CORE 8s.  I have wired up two manuals and connected them to the first four DINs.  He built the HEX files and the others to fit my two manual old Conn.  The #0 CORE is for the two manuals and the #1 CORE is for the pedals and stop tabs.  I have also loaded the St. Anne's free version to my Win 8 PC.  All manual keys work properly except for the E-1 on the swell.  In watching the output I noticed the E-1 shows Channel 7 rather then Channel 1.  So I need to correct this but don't know how.  My friend is very ill and can not help me at this time. I have MIOS Studio on the PC but other than monitor the keys I don't have a clue.  It would appear to me that the key is incorrectly listed in the file that is loaded on the CORE.  I do recall using some program to make minor changes to the codes, but don't recall what or where is was or how to do it. All I know is to run a cable from the CORE Out to MIDI In on my USB Midi device and also run a cable from the CORE In to MIDI Out on the USB Midi. Can anyone point me in the right direction?  I did download the "tutorial" on MIOS Studio but that isn't much help.  More confusing then helpful. I am located in the US in Berkeley Springs, WV.   My friend was in California and he send me the files and walked me through over the phone.  The files I have are: HEX FILES: device_id_00,   device_id_01,   device_id_02,   device_id_03,   main_swell_3,   and   setup_midio128  all with ".hex" MISC:  Beckham 0.syx,   Beckham 1.syx,   midio128_v2_2b.zip,   MIOS_Studio.exe Any help would be greatly appreciated.   I am presently wiring the pedals and may use a touch screen for the stops and couplers. Jay Beckham  

Hello, I just finished a pic based core and wanted to upload MIOS by MIOS Studio Linux. I bought the pic from Mike, so bootloader is installed already. MIOS Studio recognized the bootloader but can't upload the OS. It sais that it recieves upload request but no response after 16 try. I checked the voltages, the pic legs midi loop, the midi out with a led and it all works. Can it be soldering problem even if MIOS Studio sees the bootloader?   Thanks for any help!

Hello Guys, Some days ago i finished my first ucapps project, the Core_LPC17. I immediately connected it to my PC (windows 7 64-bit) , bit he wasnt recognized by MIOS studio, so i installed the GM5 driver. Hes displayed in the MIOS selection line (Screenshot 1) , but still no ucapps device is dedected. so i tried to connect the device to my old Laptop (winXP) and there the connection worked perfect (so it seems to be a software problem). does anybody know what i could have missed or how to get the connection running? -Gm5 is installed as mentioned above - I tried to restart my PC several times - I also tried to use other USB ports - on my XP Laptop, MIOS shows the Ucapps device as "USB-Audiogerät" (in englisch it should be simething like "USB-Audiodevice"). Under win7, this option isnt avaliable (screenshot 2) Greetings, Kilius P.s. : Im new with this Midi topic, so feel free to correct me if something isnt right:) thanks (scrennshot 1) (screenshot 2)

Hallo Zusammen, ich habe vorgestern mein erstes Ucapps - Projekt fertiggestellt, den Core_LPC17. Habe ihn sofort an meinen PC (windows 7 64-bit) angeschlossen, aber er wurde von MIOS nicht erkannt. Also habe ich den GM5 Treiber installiert. Der GM 5 erscheint auch in der MIOS Auswahlliste oben (Screenshot) , aber trotzdem wird kein Gerät erkannt. Deshalb habe ich es an mein Altes Laptop mit Windows XP angeschlossen. Da hat alles einwandfrei Funktioniert. Also scheint es ein Software-Problem zu sein. Hat irgendjemand eine Idee, was ich vergessen haben könnte bzw. wie ich die Verbinfung herstellen kann? -Gm5 ist ja installiert -neustarten habe ich auch schon ersucht - andere USB ports habe ich auch verwendet - auf dem alten XP-Laptop wird in MIOS das Board als "USB-Audiogerät" angezeigt, die Auswahlmöglichkeit wird aber bei win7 nicht angezeigt Grüße, Kilius P.s. : Ich bin neu auf dem Gebiet, also verbessert mich bitte falls hier was falsch ist :) danke  

I was connecting through usb to MIOS from stm32f core and 4.086 with no issues. Then i uploaded 4.087 and MIOS cannot find the core now.   I can see midi input on the midi monitor when i start and stop a sequence.   What happened?   Midi connection to mios is working fine.  I'm running WIN XP. MIOS 2.4.6   Any ideas?     On the positive note: .087 is running and i've successfully configured the 8 analog gates from my dout! :) :) And i know the drum trigger and clock functions will work as well!

Hello,   I used a pic based Core to make a midi pedalboard.  As I know how to use PIC micro controllers and that I needed very special features, I developed my own code (from scratch).   In order to be able to update my pedalboard software if needed, without having to open the enclosure each time, I thought implementing a boot loader.   Mios 8 is ready to use, with midi functionalities, and it could be a good solution...   Just One question :   Can I use it with my custom program or is it only working with Mios dedicated programs?    All configuration are made by my program. It is fully standalone. Therefore, after Mios procedure, my program must be loaded and executed as if Mios was not there...   Is it what it does?   Thank you for your help,   Alexandre 

Hello all,   I have recently completed a Sammich that has been sitting on a friends shelf for the last 4 years!   I will explain what has happened so far to try and give a clear picture.   The build went really well apart from a lifted pad which was repaired (this only affected the low power LCD backlight) and is now working.   Everything electrical checks out, all test points are clear and there are no shorts, the correct jumpers are set for the 8508 SID's, the voltage jumpers are correct also.   Basically the Sammich turns on and the LCD shows some black squares, then tells me: MIOS v1.9g ©2009 T Klose, and then goes on to say READY.   I have an M-Audio 2x2 midisport usb interface, I have downloaded the latest MIOS Studio software (PC and Mac), and the latest setup_sammich_sid.hex, and the mios_v1_9g_pic18f4685.hex   My problem is that no matter what i do, it doesn't seem to want to let me upload the hex file to the PIC/Sammich.   when I first power on the sammich, if i press query in the mios studio immediately, i get the screen telling me its connected to the core and ready, and then i browse for the setup_sammich_sid.hex and hit start, and then it tells me it can't contact the core and to reboot the sammich, which i do, it tries to do it then it says it can't it and gives me an error saying:    Upload aborted due to error #12: MIDI IN Frame ErrorNo response from core after 16 retries!   It only ever seems to give me the connected to core message immediately after I power it on, and press query, and then only very briefly, from what i understand, it is supposed to keep polling every few seconds for an upload if it doesn't have mios/hex burnt in.   I have tried doing this under windows 7 64bit, and OS X 10.10, using the same M-Audio 2x2 ( isee from the white/blacklist that this particular device may not work under OS X, hence why I'm trying under windows 7.   I have looked at the troubleshooting guide, and done the midi loopback tests from the PC and the sammich, and the check out fine.   I think i either have a duff midi interface, or something else is wrong.   I will post some screenshots incase anyone else can help by looking at them, any help is greatly appreciated.   [EDIT]   I have now tried to upload the file from another 2 different types of midi interface on the Mac, but still have the same error in mios studio.   [EDIT]   I have just purchased a Neusonik uMIDI/O22 to test with, once it arrives i will give it a go and see if it makes any difference.      

Hi everyone,   I have a strange problem with my STM32F4 Discovery not being able to communicate with MIOS studio.   I flash the STM32F4 with the mios32 bootloader no issues via ST link, but then if I reboot the core and connect through the left Micro-USB, the USB MIDI driver doesn't come up on either windows or macOS (so I can't connect it to MIOS studio). If I boot the core in boot hold mode, the USB-MIDI driver comes up on both Mavericks or Win7 (MIOS bootloader) the core gets recognised and can upload an application (ID=0), but when I then upload midibox_seq_v4_086 and reboot, even though it works on the displays of my MbSeq4, no USB Midi drivers again in either Win7 or Mavericks.   To test further, through boot hold mode I uploaded midio128_v3_019, reboot, and the drivers do come up and I can use the terminal, but I get 'No response from MIOS8 or MIOS32 core' (I've checked with all Device ID values, none works). If I now try to upload midibox_seq_v4_086 I get the 'Warning: no reponse from the core' message half way through and the core doesn't seem to send an upload request after booting.   I have done this when the STM32f4 Discovery board is not connected with the MBHP_CORE_STM32F4 module and it exhibits the same behaviour.   Is this midibox_seq_v4_086 messing up the USB midi drivers somehow?  Or perhaps some residual code somewhere if it connects under boot hold?   Any help is much appreciated!

Hello there,   i recently fixed my mbsid (mios1.9f and sid v1.7303e, both compiled for 18F4620). And recompiled the sidapp, so the LC512 bankstick is now supported. What I read is, that in this sidapp there's only 128 possible patches per bankstick (as there are only 128 program changes 0xC0). When I switch on my mbsid, I hear the rising sound (meaning found bankstick) TWO times. In contrast in the old config (in setup_8580_without_cs.asm), running the LC512 as LC256 I only got ONE rising sound.   Does that mean I have double the space now or two patch banks? BTW: I know that bankstick addressation is hardcoded via GND/+5V on Pins 1,2,3 of the LC256/LC512   And related question to that is (have been peeking around, but then again got a little confused): How to change access to banksticks in mbsid (v1.7/mios1.9) via MIDI, i.e. BankChange or sysex.   Many thanks, copes

I'm having a bit of an issue with my build I recently completed.  Please excuse the newbness...I'm a bit new to the digital realm of synths but plenty of years in analog circuitry.  I finally took the dive into this project to accompany my expanding modular synth and it looks like I hit my first wall.  Running MIOS on OS 10.8.4 with a MOTU Fastlane that doesn't seem to appear on the blacklist. PIC was purchased from Smash w/V1.9G and devID 0. I have all the other PICs pulled so I can get this thing tested.  PSU is a linear Condor +5V/3A, 9V ~1.5A   MIOS on launch scans the MIDI interface   MIDI: Fastlane USB #3 Port B   Scanning for MIDI Inputs... [1] Fastlane USB #3 Port A [2] Fastlane USB #3 Port B* MIDI Monitor Ready   ...end nothing else after this   Output wind ow shows:   Scanning for MIDI Outputs... [1] Fastlane USB #3 Port A [2] Fastlane USB #3 Port B* MIDI Monitor Ready   [16697.988] f0 00 00 7e 32 00 00 01 f7 [16697.988] f0 00 00 7e 40 00 0d 02 00 00 00 00 00 00 01  00 00 00 00 f7 [16698.199] f0 00 00 7e 40 00 02 f0 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 [16698.412] f0 00 00 7e 40 00 02 f0 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 [16698.512] f0 00 00 7e 40 00 02 f0 00 00 00 01 10 11 12 13 14 15 16 17 18 19 1a f7 COUNTING CONTINUES ....   When I send a query it seems to contact the PIC because the LCD window shows [Rebooting MIOS] Then flashes the MIOS version and then shows [Ready]   So far I've started on the debug page and nothing is really working except for MIDI is showing the loopback on TEST PC1  TEST MIDI1 Pass TEST MIDI2 Fails TEST OUT1-3 Fails   TEST IN1A&B Good   I need to continue with the other tests but I'm wondering if this maybe a problem with my MIDI interface before I continue.   Thanks so much for any help.