TK.

Duplicate:

yes, the clock divider is still not implemented (and DIN sync input isn't implemented as well) Will be something for my winter vacation, where I (traditionally ;-) work on MBCV CC: all parameters are already available via NRPN, which is some kind of extended CC Is this sufficient? Best Regards, Thorsten.

+1 MIDIbox is a non-commercial DIY project, we are doing this during our sparetime since several years, we are not Amazon! Best Regards, Thorsten.

Hi Robin, why are you still trying to use wget? We already clarified, that wget is currently not working, and you wrote how you solved this (by directly downloading the file with your webbrowser): After download, just unpack the file with "tar zxvf <filename>" Replace <filename> by the filename of the file that you've downloaded - it's that simple! ;-) Best Regards, Thorsten.

Hallo Sascha, momentan wird nur ein einziges AOUT_NG Modul unterstuetzt, doch ich kann die Firmware so erweitern, dass auch zwei Module funktionieren. Zu den DOUTs: rechne schonmal mit drei weiteren Shift Registern fuer die Gates und Clocks - diese Ausgaenge werde ich naemlich in Zukunft auch hier zur Verfuegung stellen, so dass die "Fummelloesung" ueber J5A/B und den 74HC541 Buffern entfaellt. USB ist eigentlich die einfachste Loesung, schliesse die MIDIbox einfach an einen USB Hub mit externem Netzteil (muss ja nicht an einen PC angeschlossen werden) Falls das Board nicht ueber USB versorgt wird, kannst Du die 5V (nicht 7V!) an J2 anschliessen. Ansonsten gibt es gerade hier einen aktuellen Thread zu diesem Thema: brauchst Du nicht, die Firmware supported jedoch auch hier Duo-Color LEDs als Option. Auch das ist nur eine Option, die von Wilba's Frontpanel verwendet wird: http://www.midibox.org/dokuwiki/doku.php?id=wilba_mb_seq Ich habe leider keinen speziellen Schaltplan dafuer parat, werde ich bedarf mal aufmalen. Fuer die Matrix benoetigst Du jedenfalls 1 DIN Shift Register, 1 DOUT Shift Register, 64 1N4148 Dioden und 64 Taster. Siehe oben - die Loesung mit dem 74HC541 ist demnaechst obsolet Ich bin gerade dabei, die Hardware zu vereinfachen - doch das ist ein langsamer Prozess... ;-) Mir ist bewusst, dass deshalb die vorhandene Dokumentation etwas verwirrend sein kann, auch hier muss ich nochmal ran. Im Grunde sollte ich klar unterscheiden zwischen "recommended" und "optionalen" bzw,. "historischen" Loesungen Ja!!! Mit den zusaetzlichen Buttons kannst Du lediglich die Trigger setzen, doch die Parameter (bspw. Notenhoehe oder CV Werte) muessen weiterhin ueber die GP Encoder eingestellt werden. Es gibt uebrigens alternativen zur klassischen 4x16 BLM, siehe auch: http://www.midibox.org/dokuwiki/doku.php?id=mididocs:seq:usingblm Gruss, Thorsten.

Hi Sascha, here is a good starting point: http://www.midibox.org/dokuwiki/doku.php?id=mididocs:index To the Evolver: I don't know the detailed MIDI implementation of this synth, but if oscillators can be played with individual notes then it will be easy. Alternatively check if it allows to modify the pitch via CC messages for each individual oscillator. Best Regards, Thorsten.

Hi, this "junk" are SysEx based debugging messages. Your MIDI parser should be able to handle (and ignore them). You can make the message visible with MIOS Studio, the messages should appear in the terminal window. They might give you important hints about the configuration. E.g. the first message says "Button 8 gedrueckt" and the second message says "Encoder 0: 1" Could it be, that these messages are generated from your .NGR or .NGC file? Best Regards, Thorsten.

Thanks for testing! Meanwhile I think that you are probably using a wrong Micro-USB cable, but I don't have enough experiences with the different cable types yet so that I'm not 100% sure. The cable should show a B (for USB Device), and not A (for USB Host): Do you see a B letter on your cable? Independent from this, it seems to be possible to enforce B mode. Probably this wednesday I could give you some new test applications (the mini-app and a MIDIbox SEQ build) which fakes the B type. If this solves the issue, I will make it available as an option. Best Regards, Thorsten.

Ok, added to wish list, will be available in one of the next firmware releases. Best Regards, Thorsten.

Das MBHP_CORE_STM32F4 Modul ist besser, weil es fuer dieses in Zukunft (ab 2015) eine erweiterte Firmware ("MIDIbox SEQ V4 Plus") geben wird, die auf den aelteren Core Modulen nicht laufen wird. Best Regards, Thorsten.

Drum tracks are using the memory space for the track name to store the drum instrument names. So: yes, due to this feature it isn't possible to use the track name for drum tracks. Best Regards, Thorsten.

Yes, 15k will work as well, just only the signal/noise ratio is lower (means: higher danger for jittering values), but 15k should still be in the acceptable range. Norbim gave some important hints, please follow-up on this. Best Regards, Thorsten.

Hi, so your sammichSID was working correctly before the update, some control elements stopped working after the update and you haven't done any modification on the hardware, right? Could it be that you've uploaded the wrong firmware? The release package contains a "setup_sammich_sid.hex" file, please only upload this one Best Regards, Thorsten.

The bipolar setting is a hardware option and should work without additional software measures. It just shifts the offset into the negative range. Best Regards, Thorsten.

I like such customizations - well done! :) Best Regards, Thorsten.

Hi Alex, I've no experiences with this. If you've luck you will find special fader knobs with some kind of extension yes, please start it simple and extend over time before building a case. Motorfaders can first be tested standalone by connecting the MBHP_MF_NG module directly to the PC. Once they are working, continue with the STM32F4 based core module, try to get the communication between this core and MBHP_MF_NG working. Continue with bank buttons, add encoders, etc. step by step Best Regards, Thorsten.

Hi Robin, how did you set the environment variables exactly? Here a prebuilt file to doublecheck if it's working better with correctly set variables: http://www.ucapps.de/tmp/005_polling_j5_pins.zip Best Regards, Thorsten.

This case really puzzles me! The MIOS Studio based MIDI IN/OUT monitor log was actually the most useful input, because it shows me that during the query STM32F4 responses with a delay of more than 1 second, which means that something really strange is going on in the application; actually the response should happen within 1..2 mS Let's continue to check different applications, here some prebuilt ones: http://www.ucapps.de/tmp/stm32f4_usb_test_files.zip Please report your observations on all three .hex files. (you can upload a .hex file in bootloader hold mode via MIOS Studio). app_skeleton_r2023.hex: minimal application with the old USB MIDI driver app_skeleton_unmodified.hex: minimal application with the new USB MIDI driver, USB Host and Device mode enabled app_skeleton_without_usb_host.hex: minimal application with the new USB MIDI driver, only Device mode enabled After the app has been started, just check the response by pusing the Query button, that's sufficient. (the MIOS terminal won't work since it isn't supported by the application) Best Regards, Thorsten.

Hi Robin, are they even 0.3V if the inputs are not connected to ground? (they should be around 3V instead since an internal pull-up is activated) Maybe you are checking the wrong pins of the J5* sockets? 5 pins of the "inner" side are Vd + 4 inputs, 5 pins of the "outer" side are ground. Best Regards, Thorsten.

Al Spitzley created a compact PCB for this purpose, here a picture of the prototype: It provides 16 gate triggers and even 10 CV outputs for velocity sensitive drums. I'm not sure if and when he would like to run a batch order, you could ask him nicely. Best Regards, Thorsten.

The mixer map association is fixed with the pattern, not with a track. The program change parameter layer type is not intended for your use case, it was a special request from a user who wanted to switch patches for each step. Actually you are asking for a program change value which should be configured somewhere in the track configuration, and sent whenever you are changing a pattern, right? Best Regards, Thorsten.

Thanks for the compliments! :) Yes, a TTL based connection without optocoupler between PIC and STM32F4 is possible. Beside of the PA3 connection, you also need to connect the grounds together. Best Regards, Thorsten.

Hi Robin, sometimes the LED flashes three times, that's normal and no problem. Since the LED is flashing, it's ensured that the bootloader is installed properly. No need to work with the ST Utility anymore. Connect a button and toggle it, or just disconnect/connect the cable. Whenever you are doing this a Note Event should be sent. very unrelated to the Bootloader. I guess that you are able to select the MIDI IN/OUT port of your core module in MIOS Studio, right? And the Query button returns some board informations, right? This would mean that the application is running successfully. Did you already try out other tutorial applications? Best Regards, Thorsten.

Hi, It seems that even with the old driver USB communication is failing, which indicates that something is wrong with the hardware. E.g. the message which is sent by the core contains the "MIOS32" string as expected. MIOS Studio would thereafter request the board string, but it seems that the core doesn't respond anymore. I never heard about a similar case in the past. Next experiments: 3) keep the bootloader mode (don't depress the blue button after the reset has been triggered with the black button), restart MIOS Studio and select the USB MIDI interface of the bootloader. Then press Query again, does it work? 4) I also need to learn more about how you've built the core module. Are you using the MBHP_CORE_STM32F4 PCB, or a selfbuilt version? Experiment: unplug the STM32F4DISCOVERY board and connect the PA9 pin to the 5V input with a short cable like shown here: Try the Query with the MBSEQ application - result? Best Regards, Thorsten.

It's normal that the size has changed, because you've flashed a different (especially larger) .hex file. Next steps under MacOS: 1) download the "USB Prober" app: http://www.ucapps.de/tmp/USB_Prober.zip It will display the USB devices, the list will be automatically refreshed whenever something changed in the system. Check if you can find the MIOS32 device in "normal mode", and when the bootloader is selected. If the device is displayed in "normal" mode, but not recognized by MIOS Studio (means: no MIDI available), we will continue debugging with this tool. 2) try a MBSEQ release which is using an older USB device driver in MIOS32: http://www.ucapps.de/mios32/backup/midibox_seq_v4_083.zip If this one is working, we've to continue debugging by setting certain options in MIOS32 Best Regards, Thorsten.