TK.

You probably have to change the appr. TRISA and TRISB registers to enable output mode for the used pins. For Port A, it could also be, that the ADC has to be disabled to use the pins as IO. This can be done with ADCON1 = 0x07 (for PIC18F452) resp. ADCON1 = 0x0f (for newer PICs) Best Regards, Thorsten.

You are spreading your questions to too many (unrelated) postings - I'm sure that this will confuse other users in future. USB MIDI is currently only tested under MacOS, where it's working stable. I haven't checked this under Windows yet, this could be the reason why it doesn't work (the new USB driver provided by ST is very different compared to the one used for STM32F1xx) One reason for the failure under Windows could be, that you've to re-plugin the USB MIDI cable, and thereafter restart MIOS Studio, after the bootloader has been installed. Btw.: some words to the SD Card connections: it could be, that I will change some pinnings soon, so that the internal (ROM based) bootloader can be used to fetch the flash from a SD Card. I especially like this possibility, because it's platform independent. :smile: Best Regards, Thorsten.

Hi Adam, there were almost no changes since 2012. All features that you can see on the Lemur snapshots are available, but the project itself still requires a lot of work for the control surface (not defined yet) and the documentation. Last but not least I would have to find some time to continue with this... ;) If somebody wants to help out: step forward! :) The SCS based menu interface is different to MBCV1, it's more like on MIDIO128 and MBNG (e.g. requires 2x20 LCD, rotary encoder and 6 buttons) It doesn't allow to change all parameters - this is currently only possible with the Lemur UI. The application has been designed for LPC17 (and faster CPUs, I guess that it will run on a STM32F4 as well) The STM32 hasn't enough "horsepower" for handling the high-speed modulation pathes, and will probably stall. Best Regards, Thorsten.

The LED is not assigned to a function anymore after we change the purpose of the "Sync" button (it switches to the BPM menu page as you noticed) Best Regards, Thorsten.

Hi, should work again in v4.078 shouldn't happen anymore in v4.078 selectable as "external controller" in v4.078 (assigned to CC#111 by default) added to the wishlist, but I will wait for more requests in this direction from other users before starting with the implementation to avoid that the change goes into the wrong direction. corrected the manual, a bank has only 64 patterns anymore. will show "off" now. The "all" setting is available as the last value in this item (v4.078) Here a pre-release for testing: http://www.ucapps.de/mios32/midibox_seq_v4_078_pre3.zip ChangeLog (so far...): http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2FCHANGELOG.txt this is not a bug, I just overlooked that the documentation wasn't consistent at all places after the bank size has been reduced some years ago. Best Regards, Thorsten.

V4L doesn't record program change. Usually a PC would be configured in a mixer map, but this feature isn't accessible on a V4L. :-/ Best Regards, Thorsten.

If this really makes sense, then I could probably provide it as a special MIDI router option (this would actually be a bad place, but I've no better idea where to put such an "unrelated" feature without much programming effort) Best Regards, Thorsten.

Hi, you wrote this posting some time ago, and I guess that you found the answer to some questions already in the forum. Which questions are still open? Btw.: the BLM emulation is the best way to find out what's (and how it's) working. In order to enable the communication, you've to edit the MBSEQ_GC.V4 file with the MIOS filebrowser based editor. E.g. set BLM_SCALAR_Port 18 to enable BLM communication for the MIDI port USB3 Thereafter enter "reset" into MIOS Terminal to restart MBSEQ V4L and to load the changed configuration. Best Regards, Thorsten.

Yes, correct. In the documentation I changed the number of ports from "up to 11" (which was for the STM32F103 based core, and includes UART, IIC and USB) to "up to 12" for LPC17 based core. Best Regards, Thorsten.

Hi, see this tutorial: http://www.ucapps.de/midibox64_tutorial.html search for "merge" The change takes place immediately. The value is stored in the bank, which is either the internal EEPROM (if no BankStick connected), or the external EEPROM (the BankStick). It will be restored after power-on from the default bank, and on bank changes. Best Regards, Thorsten.

@Bibi: enter "set debug on" in the MIOS Terminal (part of MIOS Studio) Now any DIN changes should display a message, which is useful to find out the hw_id values which correspond with the input pins. It's also nice to prove, that all inputs are scanned correctly. Best Regards, Thorsten.

The first problem could be related to the display width/height configuration. Which lcd_width/height values did you configure in the MIOS32 bootloader? Best Regards, Thorsten.

This could be related to a different problem - I haven't tested the STM32F4 based bootloader on a Windows PC yet; only MacOS Best Regards, Thorsten.

Separate Device IDs will be required if you want to access the cores from MIOS Studio. The change_id application can be used to re-program the device ID without re-flashing the PIC MIOS8 bootloader. Best Regards, Thorsten.

Just to ensure before I start debugging: does this issue still exist? Best Regards, Thorsten.

Wow, you created a really sophisticated control surface! :smile: FFW requested a similar feature, therefore I had already a solution in my mind: the new .NGR command "set_active" Please try out this pre-release: http://www.ucapps.de/mios32/midibox_ng_v1_027_pre2.zip Here a demo configuration: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=/trunk/apps/controllers/midibox_ng_v1/cfg/tests/multibnk.ngc and the appr. .NGR script: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=/trunk/apps/controllers/midibox_ng_v1/cfg/tests/multibnk.ngr Receivers can't be put into a bank, because it's assumed that events should still be updated on incoming MIDI messages regardless if they are active or not. But you could try the .NGR command "set_lock" instead. A locked event won't receive messages -> exactly what you want. :smile: Best Regards, Thorsten.

Of course, e.g.: if( evnt0 == 0xb0 ) { // listen to CC Channel 1 // the CC number selects the pin: unsigned char pin = evnt1; // and the CC value turns the LED on or off unsigned char value = (evnt2 >= 64) ? 1 : 0; // finally set the LED: MIOS_DOUT_PinSet(pin, value); } Best Regards, Thorsten.

Ok, I misunderstood the term "all others do" and thought, that this is only a problem with a particular LED. In fact it seems that the chip is not booting. Not so nice - it's indeed probably better if somebody could give you a replacement. 1750 GM5 chips have been sold, I don't believe that nobody could give you a spare part! ;) Best Regards, Thorsten.

Yes, this should be ok. Only difference: Mike only programs the bootloader, which means that you've to install MIOS by yourself, and thereafter the application. (no real challenge, both is done via MIDI with MIOS Studio ;-)) -> http://www.ucapps.de/mios_bootstrap_newbies.html Best Regards, Thorsten.

Hi Dave, no, an ethernet connection is not required. The first message just only tells you, that it would be ready... The timing informations which are displayed each second are only for benchmarking purposes. You could disable it by changing in app.cpp Best Regards, Thorsten.

It will blink shortly (will be visible) - so, it would also be a good testing method. One thing came in my mind: are you really checking the right 74HC595 pin? See also this schematic: http://www.ucapps.de/mbhp/mbhp_doutx4.pdf E.g. in your setup, the bass drum is triggered with the first SR, pin D6, which should be 74HC595 pin #6 For the case that I've messed up this: could you please check, if you see a trigger at pin #1 instead? Or at any other DOUT pin? Start the sequencer, enter the Manual page, press GP1 button. You will notice that the sequencer always jumps to this step when you are pressing this button. Press GP5 button, the sequencer will jump to this position... Stop the sequencer. Press GP1 button - the sequencer will play all instruments which are enabled for this step (you will hear this once the DOUT triggers are working) Best Regards, Thorsten.

Unfortunately yes! This is a Windows limitation. If you've luck, multiple USB MIDI ports will work with the GM5 driver, or with the Korg driver. See also the bottom of this page: http://www.ucapps.de/mios_studio.html Best Regards, Thorsten.

Hi, the .NGR page of the manual describes, how to dump a snapshot after power on: http://www.ucapps.de/midibox_ng_manual_ngr.html Extract: if ^section == 0 exec_meta RetrieveAinserValues exec_meta DumpSnapshot endif Best Regards, Thorsten.

Hi, from my point of view you are on the wrong track (resp. group ;-) The handling based on your description is the expected handling. yes, because at the time I created the video the "vintage panel" wasn't correctly supported, which means the track LED didn't display the group - but the track buttons select the group... This was a bug complained by the "vintage panel" users, and I fixed it. In addition, I see now reason why somebody would like to select a track in the pattern page. You are requesting a different handling, but this would mean that I would have to add a "private" option for you, which isn't used by myself (and most users). Is it really worth the effort? I don't think so. Especially since I confirmed, that your hardware is working correctly? Best Regards, Thorsten.

Finally somebody discovered the STM32F4 Discovery adaptions... :wink: Yes, I used this evaluation board to check if it's worth to spend some more time for a proper MBHP integration. Please don't expect a public release this year, because in order to do it right many hardware related topics have to be considered; especially some hardware conflicts have to be solved (more about this topic below). Currently I don't have so much time to continue with this due to various business trips around the world. I will probably continue in September. On the other hand, hackers with some background knowledge would already be able to use this board for own experiments with MIOS32. For a kickstart: here the precompiled bootloader <removed> New page: http://www.ucapps.de/mbhp_core_stm32f4.html What is working so far: - system init, timers, interrupts, FreeRTOS, etc. - accessing the onboard LEDs - USB MIDI and UART based MIDI - code upload via MIOS Studio - I2S (@Niklasni: yes, even the onboard DAC is running, I tested it with apps/tutorials/024_i2s_synth) - SD Card access (but with common SPI) - SRIO - IIC (accessing the MBHP_IIC_MIDI module) What is not implemented yet: - ADC (because I haven't started with the adaption yet) - LCD (low prio, have to find some free pins which are not used for other purposes) - SW based SPI for J19 (have to find free pins, or maybe I will use a HW SPI for this..) and that's all ;-) Applications which are already running without issues (aside from the missing ADC, LCD and J19 support): - MIDIbox SEQ V4 - MIDIbox NG V1 - MIDIO128 V3 - MIDIbox CV V2 so - no real show stopper. But the hardware connectivity will be a challenge, because unfortunately some important pins - especially for UARTs - are allocated by onboard resources. E.g. although the chip contains 6 UARTs, many of them can't be used bidirectionally due to these conflicts. I don't understand, why ST doesn't integrate some more internal multiplexers for alternative connections... In other words: the usage of this board will have some limitations. The main advantage that I see: not only higher speed, but especially much more RAM! 192k instead of 64k (LPC1769, STM32F1) makes a big difference. I'm especially happy that MIOS32 applications like MBNG and MBSEQ can be easily upgraded with an inexpensive core module replacement in future! The onboard DAC and Cortex-M4 based DSP capabilities are also great for synths or Fx units of course, but I'm unsure if I will go into this direction by myself. Best Regards, Thorsten.