TK.

No - don't panic! ;) Yes, and once the MBSEQ_C.V4 file will be written again, these parameters will be replaced by MIDI_BUS_Channel 0 1 MIDI_BUS_Port 0 0 MIDI_BUS_Lower 0 0 MIDI_BUS_Upper 0 127 MIDI_BUS_Options 0 0x00 MIDI_BUS_Channel 1 2 MIDI_BUS_Port 1 0 MIDI_BUS_Lower 1 0 MIDI_BUS_Upper 1 127 MIDI_BUS_Options 1 0x00 MIDI_BUS_Channel 2 3 MIDI_BUS_Port 2 0 MIDI_BUS_Lower 2 0 MIDI_BUS_Upper 2 127 MIDI_BUS_Options 2 0x00 MIDI_BUS_Channel 3 4 MIDI_BUS_Port 3 0 MIDI_BUS_Lower 3 0 MIDI_BUS_Upper 3 127 MIDI_BUS_Options 3 0x00 [/code] and the error messages will disappear. Best Regards, Thorsten.

Congratulations! :) Best Regards, Thorsten.

Since each track only supports a single length layer, you have to realize this on a different way: use one track for the stretched or (better) sustained note use another track for the short notes. Assign both tracks to the same MIDI port and channel. Best Regards, Thorsten.

Depending on the track configuration that you selected in the "event" page, either one or two trigger layers are available. The first trigger layer A should always be assigned to the gate (if not, the gate will be triggered on each step) The second trigger layer is free assignable. Thats what you noticed. If your selected track configuration only supports a single trigger layer, the remaining 7 assignments are ignored. So, what should I say to this "issue description"? ;) Long time ago somebody requested this feature - he still wanted to control the sequencer remotely while recording a track. If you don't like this feature, just disable it in your MBSEQ_HW.V4 file (set MIDI_REMOTE_KEY to 0) yes and yes. I will try to reproduce this... Best Regards, Thorsten.

Yes, because it's more useful for sustained and stretched notes. (if you haven't tried this yet, do it now - it results into great sound effects! :)) It would be annoying if the CC would only be sent when a new note is triggered by the gate - for such purposes it's usually better to use the velocity parameter, and to assign it to the sound destination on your synth. To your initial request: since each step can only store 128 values (0..127), there is no possibility to disable a CC without reducing the original value range. You could either set subsequent CCs to the same value, or you could use a dedicated CC track where the gate allows you to disable CC steps. Best Regards, Thorsten.

No, the MBHP_ETH module isn't supported yet, but it will be soon once I receive the PCBs from Seppoman :) Instead of disconnecting the serial IOs, you could also clamp the CS line to +3.3V as long as you won't find a notification in the ChangeLog Best Regards, Thorsten.

Do you own a multimeter? Could you please measure the voltages between ground and J19:SO, J19:SC, J19:RC1 and J19:RC2 when a) the MBSEQ firmware is running (so that output drivers are enabled) and b) the core is in bootloader mode (J27 stuffed during power-on) so that output drivers are not enabled This would help to understand if it makes sense to continue with HW checks, or if a special application is required for further analysis. Best Regards, Thorsten.

When asking such questions you should mention in which country you would like to buy the parts. I guess that a Reichelt order number won't help? ;) Best Regards, Thorsten.

Hi, strange... - which EEPROMs are you using exactly? And which MBSID firmware version - The latest (and greatest)? Does this also happen when all IIC EEPROMs ("BankSticks") are removed from the sockets? Thats fine, the bidirectional communication is working, even to the second PIC The device number is flashed into the PIC. It won't change if you put the PIC into another socket. The "change_id" application (available on the MIOS download page) can be used to assign a different ID if this helps, but I guess that it won't make a difference at the end. Best Regards, Thorsten.

You have to set the following two environment variables to the path of your mios/trunk directory. Example: export MIOS_PATH=~/svn/mios/trunk export MIOS_BIN_PATH=$MIOS_PATH/bin [/code] (~ is a shortcut to your /Users/<your-login> directory) The export commands can be executed in the same shell where you will execute "make". Alternatively you can enter the commands into your ~/.bash_profile file, so that they will be executed whenever a new terminal is opened. Best Regards, Thorsten.

Beta21 is available now: MIDIboxSEQ V4.0beta21 ~~~~~~~~~~~~~~~~~~~~~ o ongoing preparation work for BLM16x16 Features will be described under http://www.ucapps.de/midibox_seq_manual_blm.html o the simple Transpose/Arpeggiator MIDI split function has been replaced by a new bus routing concept. There are 4 busses that can be configured in the MIDI page. Each bus provides a dedicated MIDI port, channel and lower/upper MIDI note to define a keyboard range. o the bus can either be routed to the transpose/arpeggiator function ("T&A Mode"), or it can be used to play the currently selected track "live" ("Play Mode") o Track Mode page: now allows to select the bus over that the transpose/arpeggiator function should be controlled o Record function: whenever active, the MIDI port and channel used for recording won't be routed to Transpose/Arpeggiator/Play bus. o the "Roll" trigger now selects a 2D10 roll instead of 3D08 since it's more useful in most cases. In order to apply customized roll values, please use the roll function of the parameter layer instead of the Roll trigger. o implemented "Roll2" parameter layer function. This alternative solution to "Roll" allows to define the number of step repeats, and the distance between them. o added optional button/LED function for UNDO o fixed MIDI clock issue sent to USB5..USB8 (resulted into multiplied tempo values in some DAWs) o CC assignment displayed correctly in mixer page o LFO CC not sent anymore if track is muted o fixed crash if preset name is longer than 7 characters o fixed step selection of copy function o inverted encoder behaviour in mute page: moving clockwise will unmute, moving counter clockwise will activate mute o if a previously "empty" pattern/map/song is stored without name, it will be labled with "unnamed" now. o LFO effect now works on CC parameters as intended o If a track is in CC mode, a CC/Pitchbender value will only be sent if the gate trigger is set. CCs/Pitchbender events are sent for each step regardless of the gate as before if the track is in Note or Chord mode. o transpose now works correctly on CC and Pitchbender values, but only if the track is configured for CC mode. Transpose will be ignored for CC/Pitchbender events if track is in Note or Chord mode. o AOUT gates now 0V after power-on o some minor bugfixes [/code] Have fun! :) Best Regards, Thorsten.

Go to http://www.findchips.com and enter 74hc165 into the search mask :) Best Regards, Thorsten.

The construction looks very similar to my setup, with one exception: since MBSEQ frontpanel and BLM are separated, my solution is easier to transport. And I can remove the BLM if I need some free place at the desk for something else. In order to connect BLM to my MBSEQ I will use a single cable for MIDI IO and power supply. With optocouplers instead of TTL level digital IO the allowed cable length is ca. 10 m! :) Best Regards, Thorsten.

For STM32/MIOS32 I'm normaly using strtol since it allows to differ between decimal and hexadecimal values. here an example: ///////////////////////////////////////////////////////////////////////////// // help function which parses a decimal or hex value // returns >= 0 if value is valid // returns -1 if value is invalid ///////////////////////////////////////////////////////////////////////////// static s32 get_dec(char *word) { if( word == NULL ) return -1; char *next; long l = strtol(word, &next, 0); if( word == next ) return -1; return l; // value is valid } [/code] You have to add "#include <string.h>" to the header of your .c file Best Regards, Thorsten.

At least the PIC part of the ultracore can be re-used for the BLM :) Best Regards, Thorsten.

I already considered to provide 4 transpose/arpeggiator busses routed to Bus1..Bus4, that can be loopbacked or controlled from keyboard splitzones (and now also from BLM16x16+X). And a "play through" function is planned as well. This concept is similar to your proposal, as each track can select the desired transpose or arpeggiator zone individually. Advantage compared to your idea: it fits better with the loopback mechanisms! I don't like the velocity option - it makes the configuration more and more complicated and especially intransparent! I mean: you would probably know how to use it, but the next guys would think that transpose seems to be buggy if they don't remember that they activated such a strange option by fault. Btw.: this is the wrong topic to discuss about MBSEQ features. Your request will probably get lost here! Best Regards, Thorsten.

Wow! Now it becomes interesting! :) Best Regards, Thorsten.

P = U*U/R = 5V*5V/10000 Ohm = 0.0025W So, you could even use 1/400 watt resistors :) Best Regards, Thorsten.

You won't be able to edit parameters when GP encoders and buttons are so far away from the LCDs! Adding encoders to the BLM and/or MBSEQ circuit could be possible, but I'm not sure if the SRIO chain can be scanned stable enough if the SCLK cables get so long! Up to 10 free DIN registers could be added to the PIC (= up to 40 encoders), and since this chip drives the signal lines at 5V push-pull, it would probably better to add the encoders there. But as already mentioned in another posting, I'm much more happy with a desktop solution, resp. a separated BLM that sits flat on the desk. Best Regards, Thorsten.

From my experiences with the BLM16x4 that I built into a rack case a separate BLM that sits flat on the table is definitely better than a rack mounted option! I haven't got the new rubber button order yet, and will need a frontpanel before I'm able to mount them. Before other people are trying this, I recommend to wait for my tests. I assume ca. 50 EUR - no? You would save 35 EUR, but would get a robust and easy to solder solution in return. Maybe my warning wasn't clear enough: don't do this at home kids! ;) Probably yes See http://midibox.org/forums/index.php?app=gallery&module=images&section=viewimage&img=279 The cables are so thin, and the circuit is so large that a picture doesn't really help. The schematic http://www.ucapps.de/mbhp/mbhp_blm_map.pdf gives you a better overview, but if it doesn't make sense to you, it's definitely better to wait for a PCB, because otherwise chances are high that you've to spend much more time to find and fix wiring errors!!! Best Regards, Thorsten.

For this video I preferred the lowest velocity at the bottom since it is hard to find the lower keys with a camera before your face (thats the reason why I mostly used the upper buttons for all modes ;)) I will provide a swap option so that people can decide themselves. A big advantage of having the loudest keys at the bottom: it will be easier to change the transpose key with a hand that is playing/holding notes. Btw.: I also consider to add a (horizontal) keyboard split option. Only 8 velocity values will be available per instrument, but they can be played in parallel, resp. it won't be required to switch between the tracks. And the mode selection buttons will be changed to the lowest "extra column" keys, so that the most important modes can be switched with a single hand. Soon! Btw.: good that you stopped your activities with the PCB layout, as this gave me some time to reconsider the usage and arrangement of extra buttons. :) yes. And switching between the patterns can either be done immediately (the way I prefer), or synchronized to the measure. It gives you exactly the same functions like the MBSEQ V4 Pattern page, just more direct access. Btw.: muting is possible with the extra column by clicking a button twice (first click selects a track, second click mutes a track) It's your own choice if you prefer a traditional connection via MIDI compatible cables (with optocouplers) or a direct, digital connection. Using optocouplers decouples the BLM circuit and allows long distances. Digital I/O over long cables could be unstable in a noisy environment. One of the 5 UARTs is available at the JTAG port J3 that you don't use yet. This additional MIDI port will be enabled in one of the next MBSEQ releases. I haven't checked the layout, but it can be assumed that any button/LED matrix is compatible with the firmware. Sometimes the mapping has to be adapted in the software, alternatively you have to ensure that the matrix is connected exactly like documented here: http://www.ucapps.de/mbhp/mbhp_blm_map.pdf Best Regards, Thorsten.

In this case it could be a good idea to change the matrix structure to 8x8 instead of 16x4. This would give us 4 quarters, and between these modules there are only the SRIO connections to BLM_SCALAR modules. It would require some firmware changes, but so long only a second variant is required to simplify the HW, it would be ok. This isn't feasible with a double layer board, because there are too many crossing traces between buttons and LEDs. We would need to use a multi layer PCB, and thats expensive. dito, same problem with crossing traces. Please identify the costs before this discussion goes into the wrong direction. So, we have already three plans that contradict each other - are there other opinions; how should your BLM16x16+X look like. (I will start a poll once enough frontpanel ideas have been collected) Best Regards, Thorsten.

The keywords in the manual are "metronome", "copy", "clear", "edit page", "track selection" Best Regards, Thorsten.

Unfortunately this isn't possible. There is no free memory anymore, there is no spare fast accessible MIDI port, and the firmware structure doesn't allow to run low-priority tasks so that BLM handling won't affect the sequencer timings. All the reasons why I switched to a new platform. Best Regards, Thorsten.

Hi Grizz, how is your MBSEQ powered? Notebook PSUs (but sometimes also PSUs of desktop PCs) are mostly too weak. This can lead to such effects that sometimes the core is working, sometimes not. Sometimes the USB MIDI port will be found, sometimes not. The best solution is to connect the MBSEQ to an USB hub with dedicated PSU (1A or more). Alternatively you could use the external power option of the core. Best Regards, Thorsten.