TK.

Hallo, ich vermute, dass es aufgrund der langen Schieberegister-Ketten zu den Unstabilitaeten kommt. Urspruenglich wurden nur bis zu 16 Schieberegister hintereinander unterstuetzt (= 4 DINX4 und 4 DOUTX4 Module), sobald die Kette laenger wird, koennen die beschriebenen Probleme auftreten. Abhilfe verschafft die hier beschriebene Line Transmitter/Receiver Schaltung: http://www.ucapps.de/mbhp_line_driver.html Sie sollte spaetestens nach dem 16. Schieberegister eingefuegt werden, bzw. sobald zwischen zwei Schieberegistern ein laengeres Kabel verwendet wird (in ihrem Fall also bereits nach dem 1. DIN) Gruss, Thorsten.

Hi, could be related to a power issue: how do you power the STM32F4DISCOVERY and your MIDI controller in host mode? could also be related to an application issue: which application are you using, resp. if you wrote one by yourself: how is the MIDI data processed? Best Regards, Thorsten.

V4.091 is now available under http://www.ucapps.de/mios32_download.html From the ChangeLog: MIDIboxSEQ V4.091 ~~~~~~~~~~~~~~~~~ o new parameter type "Chord2" provides an alternative set of 32 chords o new parameter type "Aftertouch" allows to send and record channel pressure events o CPU load display has been re-adjusted for LPC17 and STM32F4 o hwcfg/wilba*/MBSEQ_HW.V4: default F1-F4 assignments changed to: F1: Track Select, F2: Live Forwarding, F3: Recording, F4: Save All o MBSEQ_HW.V4: added new button/LED functions: FX, MOVE, SCROLL o MBSEQ_HW.V4: added new LED_MEASURE function which will activate a LED when the first step of the measure is played. o CC Parameter layer label now prints "#<number>" instead of "CC" o Jam page: AStart now starts to record into first step in live recording mode (as intended), it starts on the selected step in step recording mode o Purpose of Record and Live Button & LED change: they switch between record (and live) mode w/o changing to the Jam page o new button/LED combo: JAM_LIVE and JAM_STEP: they switch to the JAM page and select Live resp. Step recording mode o BLM16x16+X keyboard can now record into any track o Transpose page now allows selection based on Scale o New option page item #10 "Initial Gate Trigger Layer" (empty or trigger on each 4th step) o Event configuration page: new drum track configuration 2*64/2*128 o AOUT: added suskey function (AKA fingered portamento: slew rate only enabled if more than 2 keys are played) This function can be enabled in the CV Configuration page o removed obsolete (non-working) pattern based scale control o fixed LED behaviour in Step View page (corrected display if page is deselected) o various minor bugfixes & improvements Best Regards, Thorsten.

@Rowan: unfortunately merging MBSEQ and MBCV isn't possible - too many conflicts, too much work to solve the conflicts, and at the end it would also influence the performance of both apps (running in parallel) @Andrew: I just hacked this into the firmware without testing. Could you please try this version? -> http://www.ucapps.de/mios32/midibox_seq_v4_091_pre9.zip SusKey is always enabled, currently it can only be disabled by editing the MBSEQ_GC.V4 file in the root directory Best Regards, Thorsten.

You could temporary connect a LED via 220 Ohm resistor between 5V and pin #6 as shown in the schematic: http://www.ucapps.de/mbhp/mbhp_iic_midi.pdf If it lights up, you know that the firmware is basically running. Best Regards, Thorsten.

Hi Michael, caps should be ok, but I can't say if the pk2cmd will program the PIC correctly. Very important hint: don't forget to add the 10 uF cap between 5V and ground, otherwise the PIC won't boot. Only additional debugging help: the green power LED should turn on, otherwise the firmware isn't running... Best Regards, Thorsten.

I'm aware of your intentions, but it doesn't work for me. Putting labels at the wrong place leaves a very bad user impression. It's a no-go for a good frontpanel layout. It's clear that you intent to add them as a reminder for GP button assignment, but not there! For learning purposes somebody could just print out a template and place it over or under the device, but later he won't need it anymore (or only if he didn't use the device for a long time). Btw.: the labels will also reduce flexibility for future improvements. Best Regards, Thorsten.

Hi, relative changes can be sent with the various relative value modes, example: EVENT_ENC id= 1 type=NRPN chn= 1 nrpn=1 enc_mode=40Speed EVENT_ENC id= 2 type=NRPN chn= 1 nrpn=2 enc_mode=40Speed EVENT_ENC id= 3 type=NRPN chn= 1 nrpn=3 enc_mode=40Speed EVENT_ENC id= 4 type=NRPN chn= 1 nrpn=4 enc_mode=40Speed Aside from 40Speed, there is also 00Speed, Inc00Speed_Dec40Speed, Inc41_Dec3F, Inc01_Dec7F, Inc01_Dec41 These are all "relative values" (I guess that this is for what you asked for) Sending different NRPN numbers would be possible with conditional events. Best Regards, Thorsten.

I mean all helper labels. ARM selection labels at the top: don't belong to the top LEDs, they belong to the GP leds when ARM page is selected SEQ1/SEQ2 lines at the top: don't belong to the top LEDs as well Scale selection labels below above position LEDs: don't belong to these LEDs, they belong to the GP LEDs when the Scale page is selected. Remaining helper label line under GP buttons: under these circumstances doesn't make sense anymore... either all GP functions will be labeled at the right place, or they won#t be labeled at all, and users have to find a different way to memo the assignments - I would remove this line as well Summary: remove "helper" labels and SEQ1/SEQ2 helper lines Best Regards, Thorsten.

Hi, this could happen if the two groups are assigned to the same bank. Please ensure that - Group 1 is assigned to bank 1 - Group 2 is assigned to bank 2 - Group 3 is assigned to bank 3 - Group 4 is assigned to bank 4 (actually I should remove the bank selection, or make it only optional, because it's an obsolete legacy feature and not user friendly) Best Regards, Thorsten.

The gallery shows pictures of my first build, where I used dedicated DIN/DOUT modules. Meanwhile I replaced the modules by a MB6582 PCB Best Regards, Thorsten.

Hi Sauaen, Interesting find! Yes, please commit the changes, so that I can try them at my side. The change should be documented in http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2FFreeRTOS%2FREADME_1st.txt so that it can be reproduced on FreeRTOS updates. While I'm writing this, I noticed that we are using a 3 years old FreeRTOS version. I will update soon. Very likely the malloc handling has been improved meanwhile, so that the change becomes obsolete. But please commit anyhow so that in case of issues we are able to switch back. Best Regards, Thorsten.

Hurray, progress with the new frontpanel! :-) But from my point of view, the additional labels, and also the SEQ1/2 lines, are more confusing than helping. They are above LEDs which don't belong to the appr. functions. It would be better to remove them. Best Regards, Thorsten.

Good! ;-) To be clear on that: nothing will get lost (I've a TODO list) - but please accept that sometimes there are situations at my side which require higher attention. Best Regards, Thorsten.

No, it probably hasn't been verified and therefore probably won't work after the changes for somebody else who requested changes for the virtual interface... Patience please, the issue is noted, I need to schedule a review & code changes at my side - which probably won't happen in the next weeks! I guess that you can life with this limitation... Best Regards, Thorsten.

Yes, this should work fluently w/o hick ups. How can I reproduce this - which setup are you using? Best Regards, Thorsten.

I guess that after some changes requested by somebody else, this function isn't working anymore. Shows me that the "real" (not virtual) BLM16x16+X needs to be reviewed & improved, this task is already on the wish list. Best Regards, Thorsten.

Hi Kazik, to 1) I added this request to the MBSEQ V4+ wish list - to make this possible, more RAM will be required which is only available for the MBHP_CORE_STM32F4 to 2) this would require an interpolation algorithm, added this to the MBHP_CORE_STM32F4 wishlist as well (it will consume more compute power which should be available for this core - let's try it out!) Best Regards, Thorsten.

Sometime this year Best Regards, Thorsten.

Yes, I added it yesterday (the documentation was only in the source code) "binary logical" the first digits are at the right side, and the last at the left side. Best Regards, Thorsten.

I think it's related to a (known) limitation of the MBSID V2 system: during a patch change, the firmware has to read ca. 512 bytes from the bankstick, during this time a MIDI buffer overrun can happen if too many events are received. I fear that there won't be a proper solution for MBSID. On the other hand: due to the SID background noise, the usage of lower volumes shouldn't be preferred anyhow. It's better to lower the volume on the mixer. Best Regards, Thorsten.

Hi, according to the documentation following port mask should enable SPI1: ports=00010000000000000000 Best Regards, Thorsten.

A scale editor is still on the Wishlist: ---------------------------------------------------------- http://midibox.org/forums/topic/19701-blm-feature-requests/?do=findComment&comment=171522 Scale Editor ---------------------------------------------------------- it will probably be provided for MBSEQ V4+, since it will cause some additional RAM consumption. I guess that this will solve the request. Alternatively some additional scale entries could be provided for "flattened scales", but this approach would be less flexible. Best Regards, Thorsten.

According to the linked post, jumper SB10 has to be bridged with a solder blob. Could you please try this out - I guess that this will solve the issue. And could you please create a picture for documentation? Best Regards, Thorsten.

Perfectly quoted - it gives all information :) Best Regards, Thorsten.