TK.

Hi Rogic, the error messages can be ignored; the DRC test notices that the font used for the copyright overlaps the GND area, but this is ok Best Regards, Thorsten.

No, this isn't possible with MB16E, but it will be supported by MIDIbox NG where encoders and buttons are sampled on the same shiftregister chain. However, there is a workaround: if you plan to build a DINX4, and want to connect (lets say...) 8 encoders and 16 buttons, you can cut the SO; SC and RC track between IC2 and IC3 and connect one half to port J7 of the core module (encoders) and the other half to port J9 of the core module (buttons). Just handle it like 2 seperate DINX2 modules... (the power tracks have to be connected only once) Best Regards, Thorsten.

I've planned to integrate 4 analog CV outputs and 4 triggers so that such filters can be controlled from the SW implemented generators (LFOs, envelopes) and via CC. :) Best Regards, Thorsten.

Hi, Yes, it should be enough space. Also for a complete pot/button configuration w/o MIDI Learn.... it's in my ToDo list :) yes Best Regards, Thorsten.

Ja - sorry - ich hatte irgendwie den Kontext nicht mitbekommen :-/ Gruss, Thorsten.

Nicht ganz, man benoetigt vier Core Module fuer 32 Motorfader, und einen oder zwei Cores fuer die restlichen Pots & Buttons. Es haelt sich also noch im Rahmen. ;-) Gruss, Thorsten.

This is definitively the MIDIbox of the Week! :D Best Regards, Thorsten.

Hi, you could search for your local ALPS distributor. Alps manufacturs many kinds of pots and faders, detended types should also be available... http://www.alps.com Best Regards, Thorsten.

Hi Rogic, I'm only using the Linux version of Eagle, but it should also work under Wintendo: select File->CAM Processor, load a predefined job (Gerber) and change the printer device for the "solder side" tab to "PS". Finally click on the "process section" button. (.eps is a compatible variant of postscript .ps) Best Regards, Thorsten.

Hi Dave, This is really a critical issue. Currently only two screens are visible (if you are not in the menu). One main screen if no pot is moved: which shows the selected layer, bank, sequencer position of the current track, a track overview (selected/muted) and in the second line an overview about the muted pot columns The second screen will be activated when a pot is moved: the values depend on the MIDI event type (here: Note event), Track Mode, etc. I think that for an encoder solution a larger display is mandatory, which should show at least the status of 8 encoders - here for Layer A (assigned to Note Number), B (assigned to velocity) and C (assigned to Gate Length) of Track 1: Maybe it makes also sense to show the note and velocity (as moving bar) at once... however, I've planned a "Display Plug In" feature for MIDIbox NG which would allow everybody to design his own screen layout (your private MIDIbox skin... ;-)) I develop on my ultimate MIDIbox since four years and fortunately find enough time for my job, leisures and other pleasures ;-) Here: :-) http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=news;action=display;num=1034254654 Best Regards, Thorsten.

Hi Rogic, yes, it runs with the "old" PIC16F - after I removed all the dedicated routines for motorfaders and the sequencer, I had enough free memory for some new extensions. And I think that I will add some more features in the future, for example some predefined meta events which simulate a "mute channel" and "solo channel", and a function which allows to define pot/fader groups. But before the other firmwares will be updated. Best Regards, Thorsten.

I think this is not really the final version - but it's running fine :) http://www.ucapps.de/midibox/midibox64_v100.zip Changes: Sequencer and Motorfader parts removed Support for 64 pots, 64 buttons, 64 LEDs a device ID from 0 to 7 allows you to address up to 8 MIDIbox64 in a long MIDI chain Device ID and MIDIbox-to-COM option can be patched directly in the .hex file (see README.txt) navigation buttons can be optionally disabled these 4 buttons are automatically disabled if no LCD is connected 5 new display modes banks can be named MIDI time code (MTC) will be displayed at page #5 several minor bugfixes and improvements new mk_syx script and MIDIbox64 editor See also: http://www.ucapps.de/midibox64_changelog.html Thanks to Serge for the good cooperation in the last days regarding the editor updates! :) Best Regards, Thorsten. P.S.: the MIDIbox16E and MIDIbox MF will be updated with similar features in about 2 weeks

Hi, This is not quite correct - currently you need 3 cores for the MF section and one core for the encoder section. And thats all - these cores have to be connected in a MIDI chain. The MF firmware as well as the encoder firmware support 40 buttons/LEDs and in the future 64 buttons/LEDs, so that an "main core" for additional IOs is not required. LCD: for motorfaders you don't really need a LCD, for encoders it makes sense. If sometime the MIDIbox Link works (I haven't started to evaluate this solution yet), it will be possible to display informations of every core at one central LCD. In an unreleased MF version (*) I realised SFB events to stop a fader. These events can be assigned to button inputs, so that you can: a) use buttons to stop faders (one button for each fader) b) use capacitive touch sensors instead of buttons (*) I don't release immediate beta versions, but they are available via mail If you have programming skills, you can try to develop something near it with a bigger PIC (see the Microchip page for the wide choice)... from my experience it makes no sense to spent a lot of effort just to save one PIC which costs you about US $8 ;-) Best Regards, Thorsten.

This time from Roberto / Australia - a really cool design with a professional touch! :)

Hi Matthias, I think that your PIC is damaged. The diodes might help, but I cannot give any success guarantee... don't waste PCB area for the diodes, just solder them directly to the buttons. Best Regards, Thorsten.

Alright, banknames would really be usefull. Another suggestion was to display the MIDI Time code like known from MIDIbox Plus. The next firmware will support both. :) Best Regards, Thorsten.

Hi Dave, a great idea! Since three layers are assigned to each pot-row, encoders would improve the handling. I think that 16 encoders are enough, and of course, I could use the MIDIbox16E firmware as skeleton for a MIDIbox16E-SEQ ;-) On the other hand I don't want to spent too much effort on the old firmwares anymore - just wait for MIDIbox NG, it will support both: pots and encoders. And with the plugin capability it will be possible just to "load" a sequencer module into the PIC when required. Best Regards, Thorsten.

Hi Tristan, you could build the LTC module of the MBHP, it can also plugged on the Rx/Tx pins of MIDIbox Plus. Best Regards, Thorsten.

Hi Mandingo, A MIDIbox-Plus like controller can be built with a core module, two 4051 analog multiplexers and one 74HC165 digital input shiftregister. The PIC must run with MIDIbox64 firmware. Best Regards, Thorsten.

Hi Tristan, yes, you should use simple Push buttons, the functional behaviour of the button can be changed in the MIDI Learn menu (or with the MIDIbox editor): "On/Off value" (it's like in your description), "On value only" and "Toggle". Best Regards, Thorsten.

Hi Juanjo, the Exec/Left/Right/Snapshot button should be soldered on special pins - all others are free assignable with special functions or MIDI events. Here the schematic for the first 32 inputs: http://www.ucapps.de/mbhp/mbhp_dinx4_32buttons.pdf Best Regards, Thorsten.

In the MIDIbox64 firmware a lot of tasks are running in parallel (Pot driver, Display driver, Button/LED Driver, Bankstick Driver, MIDI Handler). The sampling period for the buttons is only about 10 mS - thats not fast enough to detect the transitions (falling and rising pulse edges) which are sent by the encoder. The MIDIO128 firmware is optimized for digital IO, the sampling period is about 1 mS and works better, but in my oppinion it's much easier and more fail-save to use a second PIC, running with MIDIbox16E firmware, because the required adaption circuit for each encoder is complex and expensive. Or wait for MIDIbox NG - it will scan up to 128 digital inputs like MIDIO128 and will come with a built-in encoder driver, so that every single input can either be assigned to a button or to an encoder (every encoder requires 2 digital inputs...). Best Regards, Thorsten.

...but it's only available in a SMD package :-/ Best Regards, Thorsten.

Currently I'm rewriting the different display pages of MB64 since some more memory is available after I removed the sequencer and motorfader parts. So, if anybody has a good idea for an usefull layout for 2x40 displays (which additional informations should be displayed?), just let me know. At the moment the layout is similar to the MB16E http://www.ucapps.de/midibox16e_tutorial_en.html (Display Submenu) Best Regards, Thorsten.

Hi Mickey, unfortunately this is a preprogrammed ROM chip which is useless for MIDI. It's a pity that they don't offer the AN2131 of Cypress, because this derivative comes with a bootstrap loader - this special mechanism is activated when the USB cable is plugged in and allows to load the right descriptors and some additional code into the memory so that the device will be recognized as "Standard MIDI-USB device" by Windows, Mac OS X, Linux... without an selfwritten MIDI driver. Best Regards, Thorsten. P.S.: the AN2131 has 2 UARTs (=2 MIDI INs & 2 MIDI OUTs) and costs about US $3 --- but w/ a minimum purchase quantity of 1k devices :-/