TK.

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.

In song mode the reference measure for synching pattern changes is always 16 * 16th notes, so it works like intended. In newer MBSEQ V3 releases, the number of "reference steps" can be selected between 1..256, but this won't cover your usecase, as this is a global setting, which will be used for all pattern changes. To be honest: I don't know how to solve your request! There are different step lengths possible for all 16 tracks, how should the firmware determine the intended pattern length without limiting existing possibilities? (e.g. playing 8 step tracks 2 times before changing to the next pattern?) Best Regards, Thorsten.

Shipped today: kynsi Flexinoodle QuPe grnsky lucem Yogi gnups JW LinkwitzRiley ultra Oman Jan75 Jurbo StormB Will be shipped once I got the money: nebula curve Frank mbreges midigor agxaudio No response yet - your order will be cancled in ca. 1 week 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 dynamona this SirVish pomics Roverbox Edis trainspotter zgba matyt deno31254 Zzzz... (please wake up) emju Edis intellijel woluf Freidieb Serge_D Harley Godzisz Snyderman 3amsleep ballpein Best Regards, Thorsten.

The software sees 4 events, but due to the detent it should only increment one time for 4 transitions. There is of course an optional "progression" algorithm in MIOS, which increments with higher values if the encoder is turned faster. But for slow moves it has to increment a single step per detent, otherwise you would miss some values when finetuning a parameter. Which are interpreted as a single Inc/Dec if a detented encoder type is selected in your MIOS setup - yes. Yes - which is optionally done if the encoder is turned faster (depending on the "speed parameter" you could even see more inc/decs No, the advantage is, that with a non-detented encoders you can stop turning "in the middle" of 4 Inc/Dec events, which are normaly required for a single "click". Accordingly, you will get a higher resolution if the encoder is turned slowly. Another advantage is, that you will get a less steppy feel if the encoder is turned fast. On the other hand: detents are great if you want to control low-resolution values, because they give you a more precisely feel. Therefore I recomment detented encoders for MBSEQ (where you want to enter note values precisely), and for the datawheel of MBSID (not for the remaining encoders, as you want to tweak CutOff (as an example) quickly). It makes sense to try a detented encoder first - and if you don't like the feel (and the noise when turning the encoder), just remove the detents... or buy some non-detented encoders later. Best Regards, Thorsten.

We reached beta9 state: Moved icon and menu items for MIDI Device Routing Implemented XML save/restore feature for all elements of MIOS Studio on closing/reopenning. Workspace configurations can also be saved and restored via File menu MIDI Filter definitions can also be saved/restored via XML Changed MIDI Device Manager handling of physical MIDI Devices. Fixes problems with mmj re-adding the same devices when rescanning, and virmidi listing multiple devices for each port. Thanks again to Adam! Best Regards, Thorsten.

The internal IO pin output drivers of the PIC are already limited at 25 mA, so that the 100 ohm resistor doesn't make a big difference. I think, that an additional protection isn't required, but if somebody experienced problems with shortened IOs, please let me know. Best Regards, Thorsten.

I guess that you assumed that removing the detent would already increase the resolution. This of course won't help - there are also some software changes required. Maybe this illustration helps to understand the approach: If you remove the mechanical detent, you will remove the "click" shown in these waveforms, so that all transitions of the quadrature code can be used to determine, if the encoder is turned clockwise or anti-clockwise. Considered, that the SW scans the encoder fast enough, it is possible to quadruple the resolution of a "DETENTED2" type encoder Best Regards, Thorsten.

MIOS Studio tries to upload code, but it periodically gets an upload request, which means, that the bootloader doesn't receive the first code block and endless requests for new data. There seems to be an issue with the MIDI In port. I would propose to check TEST_IN1..TEST_IN7 and TEST_INOUT1 of the troubleshooting guide and to post the results here to give us an impression about what is already working. The same effect (upload requests, but receiving the code block fails) happens with a rare number of MIDI interfaces which are on the Blacklist, but I guess that this shouldn't be an issue with yours (TEST_INOUT1 helps to detect interfaces which don't transfer SysEx streams correctly). Best Regards, Thorsten.

Actually there are two options, which are documented here, search for "ABW" Either you disable the ABW (ADSR Bug Workaround) flag in the configuration menu so that drum sounds will be played immediately. But this can lead to envelope hickups or even more random timings (only if AD and R = 0 the gate will open immediately, in all other cases they have a random lag between 0..25 mS) Or you enable it, which has the advantage of completely working ADSRs and a defined delay of 30 mS, which can be easily compensated in a DAW - even for live sessions (e.g. in Logic Audio, all tracks which don't use the ABW are routed to a bus which inserts a +30 mS sample delay). Best Regards, Thorsten.

BL 1X20G 2,54 Best Regards, Thorsten.

It takes longer for me to find this out, than for you to update the firmware! Best Regards, Thorsten.