TK.

All PCBs and most GM5 are sold (or reserved) The request list has been prepared for the 4th bulk order: http://www.midibox.org/dokuwiki/doku.php?id=tk_gm5_bulkorder Best Regards, Thorsten.

The firmware doesn't give you the possibility to combine 2x32k to a single bank with 128 patterns. I spent this effort for MBSID, but it was a lot of work which I don't want to do again (especially because MBSID V2 got a much more complicated bank handling than the previous version) So, based on your descriptions the BankSticks have been formatted correctly for Bank 1 and 2 You can use the MBSIDV2 Editor to split the preset bank into two 64 patch banks, so that all patches are accessible. Best Regards, Thorsten. P.S.: for the case that the documentation isn't clear enough: Bank 1: A0=0V, A1=0V, A2=0V Bank 2: A0=5V, A1=0V, A2=0V Bank 3: A0=0V, A1=5V, A2=0V Bank 4: A0=5V, A1=5V, A2=0V Bank 5: A0=0V, A1=0V, A2=5V Bank 6: A0=5V, A1=0V, A2=5V Bank 7: A0=0V, A1=5V, A2=5V Bank 8: A0=5V, A1=5V, A2=5V

This is normal if you are using a blank EEPROM. It should contain the USB descriptors. Programming the EEPROM requires a core module + the mbhp_usb_gm5_eeprom application. The EEPROM option is for experts only, and normaly not required. The most simple way to ensure that GM5 is soldered correctly is to try out the default configuration (J1/2/3 connected to ground), so that the default descriptors are used. Best Regards, Thorsten.

Shipped today: nebula Roverbox Edis emju Freidieb nitch dubstructor JSx Djo TheProf unit-sound Will be shipped once I got the money: woluf Serge_D mbreges kynsi There are still 19 GM5 and 3 PCBs in stock If you are interested to buy one (or two...), please contact me directly via PM Best Regards, Thorsten.

Mit Unbuntu habe ich mir Linux abgewoehnt (kein Scherz ;)) Best Regards, Thorsten.

This MB808 has been built by Richard. Note that the acryl frontpanel is selfmade! He wrote: If you would like to get a similar frontpanel for your project, or even more customized one, feel free to contact him. :) Best Regards, Thorsten.

V1 still seems to be popular - Oliver built his one into a small 19" rack. Well done! :)

MB808 V1.1 now supports a configurable number of steps per measure: http://www.ucapps.de/midibox_808_changelog.html Best Regards, Thorsten.

According to the emails I received yesterday, it's down since about 7 hours "traceroute" tells me, that the gateway servers of my provider (1&1) are still running, but that the webserver cannot be reached: 6 te-1-3.bb-c.bs.kae.de.oneandone.net (212.227.120.29) 51.883 ms 51.807 ms 52.962 ms 7 te-1-2.gw-dista-a.bs.ka.oneandone.net (212.227.121.216) 51.963 ms 50.941 ms 52.860 ms 8 vl-999.gw-ps4.bs.ka.oneandone.net (212.227.125.5) 54.322 ms 52.868 ms 52.733 ms 9 * *^C [/code] I hope to get it fixed today. Best Regards, Thorsten.

You can connect the additional encoders and buttons directly to the core module, no need to build a second core module. Or are you planning to add LED rings? In this case it could make sense to off-load the core. It will be slow, but you asked for it... If you would configure MB64E encoders in incremental mode, this wouldn't happen. Only exception: you are planning to add LED rings, so that MB64E has to know the absolute values. Interesting - some days ago I considered to remove SysEx import/export option, as the SysEx page will be used for other purposes (see some of the previous postings), and much more data as ever before is used for each pattern, so that MIDI transfer is really too slow (ca. 1 second per pattern). So, do you really want to wait 4 seconds until all patterns have been updated? Does Triton Extreme support USB or TCP/IP (e.g. ftp access to MBSEQ?) - this would be a much faster option to exchange data (ca. 100 times faster) Best Regards, Thorsten.

Thanks for your valuable input! It's great, that you explain a possible solution to handle new functions with the existing user interface, because this is mostly the blocking point for adding new features. See also ris8_allo_zen0's proposals what else could be done with the selected steps: http://www.midibox.org/forum/index.php/topic,10848.msg83704.html#msg83704 Your idea, to use the (more or less redundant) SELECT button to enter the pattern is great - I will go this way. For MBSEQ V3 there is no free memory anymore to implement such a feature, but for MBSEQ V4 it will be simple. :) Sounds also like a good idea, especially because by using the layer button it's clear that only a single layer can be edited this way, accordingly this feature will cost 256 bytes maximum, which is acceptable. ok :) Best Regards, Thorsten.

Yes - actually the encoder positions are the parameter values, all 128 values will be stored in a patch. SysEx (in fact any MIDI data) can be sent by programming a meta event (-> see src/mb64e_meta.inc) yes, possible even without programming a meta event You mean, using a small number of buttons (e.g. 9 or 2*8 ) to enter a program number? No, this isn't natively supported, but could be realized with meta events as well. Unfortunately this requires some advanced programming skills, and there are no examples which directly demonstrate how to implement your request. Best Regards, Thorsten.

dubstructor: yes, there are still 40 unsold GM5 :) Shipped today: dynamona this zgba curve Frank deno31254 midigor agxaudio Snyderman Will be shipped once I got the money: nebula woluf Serge_D mbreges No response yet - your order will be cancled this sunday if I don't get a reply to my PM until then. If you already know, that you don't need the chips/PCB, please write me now SirVish pomics Roverbox Edis trainspotter matyt Zzzz… emju Edis intellijel Freidieb Harley Godzisz ballpein Best Regards, Thorsten.

8 AOUT values and 8 switch settings are stored in the patch. In addition, the "V2A" option allows you to route volume directly to an AOUT. This is especially useful for AM effects (Volume is part of the modulation matrix) Best Regards, Thorsten.

Details about the patch mode are explained here: http://www.midibox.org/dokuwiki/doku.php?id=midibox64_e_patchmode I think that patch mode will be a good solution for your use case, as it allows you to store up to 128 patches per BankStick. And each BankStick can store a configuration for 128 parameters, which means, that you could prepare different BankSticks for different Synths, and/or share parameters for different Synths in different parameter groups which are part of the configuration. The disadvantage of the patch mode: you are not able to assign different CC numbers for different patches. Means in other words: encoders/pots/buttons are always mapped to the same MIDI events. Using different MIDI event mappings will require a new configuration, stored in another BankStick. Best Regards, Thorsten.

In short (to avoid confusion): this won't work Best Regards, Thorsten.

The SID volume has only 4bit resolution, and you will notice additional background noise once you lower it. However, you can control volume from a Knob function (-> Knob Encoder Layer). Just assign parameter #1 to it and you are done. It's even part of the modulation matrix. But due to the reduced resolution and s/n issue, I would propose to use an external analog pot instead - or a digitally controlled VCA, which can be accessed (and modulated) from an AOUT module. Best Regards, Thorsten.

A nice concept, but it still needs some improvements. By watching the video you will notice, how careful the student has to enter data (e.g. see the demo where a calculator is projected on his hand). Any unintended move will quickly lead to a wrong entry. Just imagine entering a mobile number in a train - impossible ;) IMHO just a technical gimmick, as Stryd says very well: a natural extension of commonplace technologies. Calling it a sixth sense is too early for a human-machine interface which works (mechanically) so slow and/or unreliable. Let's wait for the first brain proxy and let's use a common keyboard until then ;) Best Regards, Thorsten.

CC#7 should work now (RC29) Best Regards, Thorsten.

RC29 ChangeLog: o fixed CC#07 (now controls volume as intended) o for 4x20 LCD: MIDI channels and Engines of selected ensemble are displayed at upper line o OSC button now cycles between 1--, -2-, --3 and 123 o added optional CS_MENU_BUTTON_Arp function, which can be assigned to a button in setup_*.asm [/code] Best Regards, Thorsten.

uCapps.de -> uCApps.de or better midibox.org There are no Yes/No buttons. One button is used to navigate through the menu pages (called "Exit" button, but you could also label it "Menu"), the other to store/restore snapshots on the mainpage, and to move the cursor inside menu pages (called "Select" button) Best Regards, Thorsten.

Almost true :) I added your nice explanation to the Wiki: http://www.midibox.org/dokuwiki/doku.php?id=encoders Only one paragraph has been changed: Changed to: Best Regards, Thorsten.

Not really, you can also put them into the box. The Sub-D socket variant has the advantage, that you can change the setup by plugging another BankStick into the socket instead of changing the Bank with a dedicated Bank Selection button or from the menu. I find this more intuitive, but you are free to use alternative methods of course. Yes, via SysEx dumps (see doc/midibox64e_sysex_implementation.txt of the release package) No - each bank consists of multiple groups. The number of groups depends on the configured "group width" which depends on the number of rotary encoders and/or pots which are connected to your MIDIbox. 128 parameters are stored in a bank. If 64 encoders are connected, you choose a group width of 64 in your setup_*.asm file, which means that 64 encoders can control 128 parameters splitted over 2 groups. If 16 encoders are connected, you choose a group width of 16, which means that 16 encoders can control 128 parameters splitted over 8 groups. If only a single encoder is connected, you choose a group width of 1, which means that all 128 parameters can be controlled with the single encoder. Each BankStick can store 8 of such banks, and since up to 8 banksticks are supported, 64 banks are available. The BankStick partitioning changes once you choose the "patch mode" instead of "normal mode", but I guess that I don't need to go too much into detail anymore ;) All parameters are explained in the setup_*.asm file. Select one which basically fits your needs, modify it if required, rebuild a .hex file and upload it into the PIC Sorry for all the confusion, previous users requested too many variants which resulted into a complicate configuration (they have been warned! ;)) Best Regards, Thorsten.

you should quote it completely ;) Best Regards, Thorsten.

Ich vermute, dass sie sich direkt an die ADC Eingaenge des PICs anschliessen lassen, mit 100%iger Sicherheit kann ich das allerdings nur sagen, wenn Du mir ein Datenblatt von den Wheels zeigst. Der Widerstandswert sollte zwischen 1k und 10k liegen, und die Kennlinie sollte linear sein. Gruss, Thorsten.