TK.

http://www.voti.nl The quality of the rotary encoders is extreme good, they've the same "expensive" feeling like ALPS encoders, but they are much cheaper and easier available for hobbyists. So, Voti kicked Schuricht from the pole position, it's my #1 recommentation for rotary encoders now :) Note that the rotary encoders have the same pinning like ALPS STEC16B, see also http://www.voti.nl/common/sw_rot_1_doc.gif They are detented, 24 pulses. In the meantime I prefer such encoders instead of the non-detented ones. They are especially perfect for MIDIbox SEQ and MIDIbox SID - type: "MIOS_ENC_MODE_DETENTED2" Voti sells also other usefull stuff for the MBHP projects, like PIC18F452, 10 MHz crystals, LCDs, etc.. Best Regards, Thorsten.

I've received the samples today - just 3 days after the email contact! The quality of the rotary encoders is extreme good, they've the same "expensive" feeling like ALPS encoders, but they are much cheaper and easier available for hobbyists. So, Voti kicked Schuricht from the pole position, it's my #1 recommentation now :) Note that the rotary encoders have the same pinning like ALPS STEC16B, see also http://www.voti.nl/common/sw_rot_1_doc.gif Best Regards, Thorsten.

Hallo, der maximale Wert von 10k ist eher ein Erfahrungswert und hat nichts mit irgendwelchen Berechnungen zu tun. Ein hoeherer Wert kann evtl. zu sporadischen Wertaenderungen fuehren, selbst wenn der Fader nicht beruehrt wird. Wenn Du Glueck hast, passiert das bei deinen Fadern nicht, oder vielleicht stoert es Dich auch gar nicht... Die von Dir vorgeschlagene Schaltung traegt nicht dazu bei, die Spannung am Schieber zu stabilisieren, ausserdem ist sie weiterhin nicht linear. Weitere Infos liefert Google mit den Stichwoertern "belasteter spannungsteiler potentiometer" Gruss, Thorsten.

Hallo, ein Widerstand parallel zum Poti hilft leider nicht weiter. Ist der Widerstand an den aeusseren Kontakten angeschlossen, also zwischen 5V und Masse, wird vielleicht die Spannungsquelle etwas mehr belastet, aber am Ausgangswiderstand aendert das nichts. Wird der Widerstand zwischen dem Schieber und einem der aeusseren Kontakte angeschlossen, fuehrt das zu einem nicht-linearen Spannungsverlauf. Und noch ein Hinweis: beim Faderkauf solltest Du darauf achten, dass es sich um lineare, und nicht logarithmische Fader handelt... Gruss, Thorsten.

Hallo Toxvox, ja, deine Annahmen sind voellig richtig. An jeweils einem DOUT/DIN/AIN Modul koenntest Du sogar bis zu 32 LEDs/Taster/Potis anschliessen. Falls es Dir darum geht, Platz und/oder Geld zu sparen, waere es vielleicht sogar besser, die 2 x 4051 Multiplexer und die beiden 75HC165 und 74HC595 Shiftregister zusammen mit den LEDs/Taster/Potis direkt auf eine Lochrasterplatine zu loeten. Der PIC benoetigt lediglich den MIOS Bootstrap Loader, ueber den kannst Du dann MIOS sowie die gewuenschte Applikation beliebig oft via MIDI aufladen. Das Brennen des Bootstrap Loaders uebernehme ich kostenlos gegen Rueckporto, allerdings bin ich bis Ende April in Urlaub --- vielleicht koennte das auch jemand anderes uebernehmen, der einen PIC Programmer (JDM Modul) besitzt. Wie die Einstellungen gespeichert werden, haengt von der Applikation ab. Es gibt derzeit keine Applikation, die Konfigurationsdaten *nicht* im internen Flash pder EEPROM abspeichern wuerde - passt also. Die MIDIbox64 Applikation laeuft bspw. auch problemlos ohne BankStick, allerdings steht dann nur eine Bank zur Verfuegung. Gruss, Thorsten.

Hi Creekree, it should work with the same circuit which is used for LED indicators (LTC module). Maybe you've to change the 10 uF caps to a 1 uF or lower for best visual results... The LTC sends pulses on every MIDI event, than more pulses over time, than higher the deflection of the needle (such a measure behaves like an integrator) Best Regards, Thorsten.

The slimline MIDIbox SEQ made by Hallucinogen - he built it into an old Compaq PC keyboard:

Hi John, thats nothing to be worried about. All MBHP designs are working with low-active digital inputs, means: a button function will be activated (or in your case: a Note On message will be sent) on a 5V->0V transistion. The Pull-Up resistors which are tied to 5V are used to have a defined logic signal (5V) when the buttons are not closed, otherwise the input would float and could toggle between Logic-0 and Logic-1 - uncontrollable. MIDIO128 provides a function to invert the DIN to a high-active input - this would require Pull-Downs instead of Pull-Ups - but this is just an option and no requirement. The default setting (low-active input) is the most preferable. If you don't know why high-active inputs could be useful, then just ignore this option ;-) Best Regards, Thorsten.

Hi Robin, alright - the size of 20137 sounds correct, these are 17 converted 1k blocks, and the original file was a little bit larger than 16k - perfect! Yes, now you could read out the BankStick again and convert the resulting .syx to a .asm file like described in the bs_xfer package. However, it's more like a toy, but it helps you to 100% ensure that the file has been uploaded. For a first test it's ok when you assemble the reset.asm file directly, but later you propably want to have multiple files in a single BankStick, and for this it would be easier to include all data files into a single assembler file, so that the assembler can take care about the data locations. Ok, now you should proceed with the function which sends the SysEx string, see: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1078174868 Later you should think about how to organize the data. I would suggest to create a table which contains: the bankstick number the offset address the size of the SysEx string But I fear that I don't have enough time to explain more details before my holidays... :-/ Best Regards, Thorsten.

Hi, thats very unlikely! The MIDI Out is (normaly) protected with a resistor, so that a short cannot destroy the hardware. Mostly it's the driver which locks up the interface. I've the same problem with a M-Audio MIDIsport 2x2, under some special circumstances (I haven't understand it yet...) the MIDI Out doesn't work anymore until the next Windows reboot. Best Regards, Thorsten.

This shouldn't make a problem. Best Regards, Thorsten.

Hi *, in order to simplify the upload of configuration data, I've integrated a new SysEx block write/read function into all applications which required "delays between bytes" during the upload before. Now the same MIDI-Ox settings can be used like for a common MIOS dump (no reconfiguration anymore), and the upload will also work under MacOS X More informormations regarding this topic can be found here: http://www.ucapps.de/howto_tools_mbsyx.html Additionally the MIDIbox64E application can now not only handle with rotary encoders, but also with pots and motorfaders. This feature is in experiemental state, and therefore not well documented. Two new hardware setups are provided with the MIDIbox64E package for the MIDIbox NG hardware (-> normaly used as Logic/Mackie Control emulator), and for MIDIbox SEQ (normaly used as sequencer) A third setup allows to run the MIDIbox64E application on a MIDIbox64 with 64 pots --- it's just used for testing, but could be interesting for people who want to add some encoders to their existing hardware in the future. Here a list of all relevant files: MIDIbox64 http://www.ucapps.de/mios/midibox64_v2_3.zip http://www.ucapps.de/midibox64_changelog.html http://www.ucapps.de/midibox/midibox64_sysex_implementation.txt http://www.ucapps.de/midibox/mk_syx.zip MIDIbox64E http://www.ucapps.de/mios/midibox64e_v2_1.zip http://www.ucapps.de/midibox64e_changelog.html http://www.ucapps.de/midibox64e/midibox64e_sysex_implementation.txt http://www.ucapps.de/midibox/mk_syx.zip MIDIbox MF http://www.ucapps.de/mios/midibox_mf_v2_1.zip http://www.ucapps.de/midibox_mf_changelog.html http://www.ucapps.de/midibox_mf/midibox_mf_sysex_implementation.txt http://www.ucapps.de/midibox/mk_syx.zip MIDIO128 http://www.ucapps.de/mios/midio128_v2_1.zip http://www.ucapps.de/midio128_changelog.html http://www.ucapps.de/midio128/midio128_sysex_implementation.txt http://www.ucapps.de/midio128/mk_midio128_syx.zip Best Regards, Thorsten.

Hi Robin, This could be the reason why the converted .syx file is more than 3 times larger than the original file. You've to save the SysEx data in binary format - just like a common .syx file. Thereafter use bin2asm.pl to convert this binary to a assembler file. Check the content of the generated assembler code, the data behind the db statements must match with the data displayed in the MIDI-Ox window. Best Regards, Thorsten.

Hi Robin, it's normal that the resulting file is larger than the original binary after the hex2syx conversion -- this is due to the required conversion algorithm which converts 8-bit values to 7-bit values. MIOS converts them back to the 8-bit values during the upload. So, normaly you should get about 1184 bytes per 1k block (original size: 1024 bytes) But it's very strange that the converted .syx files are much larger. How did you convert the binary exactly? What is the content of the resulting assembler file? You should see the address offsets within the files (they are inserted as comments at the end of each line), what is the last offset value? Best Regards, Thorsten.

Hi Jim, yes :) MIDIbox MF supports the same features like MIDIbox64E, this means that you are also able to "morph" one scene smoothly to another scene. Best Regards, Thorsten.

Mabye you've something like an external feedback loop? (MIDI Out data is directly transfered to MIDI In) Otherwise: the Kawai driver is worth a try! Best Regards, Thorsten.

Hi, first you should check the "\windows\win.ini" file where you can find a special configuration block for Logic. All MIDI interfaces should be marked with 1, if especially your COM interface is marked with 7, it would mean that Logic ignores it. Just remove the whole block so that Logic checks the interfaces again. If it still doesn't work, try the Kawai K5000 driver: http://www.kawaius.com/download.htm Best Regards, Thorsten.

Controlling motorfaders is extremely time critical, therefore neither multiplexers, nor more than 8 motorfaders are supported by MIOS to ensure best results. Last year I visited an AES convention and got the chance to have a look into commercial controllers. I noticed that all of them are using dedicated microcontrollers for every single motorfader! So, MIOS is powerful enough to control 8 motorfaders at the same time! Isn't this already a great achievement? It saves you a lot of money! :) Best Regards, Thorsten.

Hi Robin, yes, the whole upload procedure was successfull: > F0 00 00 7E 40 00 0F 07 F7 is an acknowledge message (0F) which reports that the received checksum matched with the calculated checksum, that the data has been copied into the BankStick and that it has been verified (read-back and compare) The value behind 0F (here: 07) is the same checksum like reported by the hex2syx.pl script. You will receive an error message (0E) if any step fails (e.g. BankStick not connected, checksum error, verify error, etc...) > F0 00 00 7E 40 00 01 F7 is the upload request of the first level bootstrap loader. A reset instruction will be issued after up- or downloads via MIOS, therefore this message appears like on a common startup So - now you are sure that the binary has been copied into the BankStick. Best Regards, Thorsten.

I finally was able to add some really nice contributions of the last 2-3 weeks to the gallery: A B4 controller made by Rasmus (Denmark) - the older forum members maybe still know him, he is one of the first MIDIbox users :-) Check also his music: http://www.soundclick.com/bands/4/slowflying.htm http://www.soundclick.com/bands/0/rasndavemusic.htm http://www.soundclick.com/bands/0/rasmusfris.htm The MIDIbox64 of Thomas (Germany): Thomas' customized MIDIbox64E which is used as Traktor controller: A tiny "handboard" (based on the floorboard firmware) by Raphael (France): A MIDIbox64 which controls the Fx section of a Raveolution 309, made by Christian (Germany): A Cubase controller, based on MIDIbox64 by Niko (France): More pictures of these designs can be found in the steadily growing gallery: http://www.ucapps.de/midibox_gallery.html

Ich kann zur Beruhigung sagen, dass mir das auch mal hin und wieder passiert. Ist aber nicht weiter schlimm, musst halt nur aufpassen, dass Du den Chip nicht falsch herum einsetzt. Am besten "schmorst" Du mit dem Loetkolben eine neue Markierung in den Sockel - als Erinnerungshilfe. Gruss, Thorsten.

Kx driver - ja, eine der ersten Versionen war mal buggy, daran koennte es liegen. Siehe auch http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1061838430 Gruss, Thorsten.

Hi, following info should be especially interesting for dutch people :) I got a mail from Wouter van Ooijen that he now offers rotary encoders: http://www.voti.nl/winkel/producten.html#M-SW-ROT for a very fair price. He will send me some samples so that I can check the quality Best Regards, Thorsten.

I'm glad that we finally solved all issues and promise that the whole setup procedure will get easier in the next months, once the autoconfiguration has been implenented and Wilba has released the "MIOS Studio" which allows to upload a .hex file and changing the device ID w/o the use of hex2syx.pl and MIDI-Ox. And now have a lot fun with all your SIDs! :-) Best Regards, Thorsten.

Normaly the whole ID field should be zero. If you are using more than one core module in a chain, it makes sense to set the IDs of the other cores to 0x01, 0x02, 0x03, etc If you are using a to-COM interface, add 0x100 If you not using a standard character display, add 0xX000 (x = GLCD type) So, in most cases you are fine with 0x0000000000000000 Best Regards, Thorsten.