TK.

You are right, the 3rd cap was missing in the orderlist :-/ However, this cap isn't really necessary, it's just a lowpass for frequencies above 20 kHz - you will not "hear" any differences. With a 6.8nF it could happen that frequencies below 20 kHz are cutted -> so, let it open Let us know if everything works :) Best Regards, Thorsten.

Hi Ian, yes, this is necessary! this junction can be used if another core module should be supplied. If you plan to build two core modes, one for the MB64 firmware, the other for the SID firmware, you can make a direct connection from CORE1:J2 to CORE2:J2, and don't need to mount a second 7805, caps, rectifier, on the second board. It is just a 1:1 connection of CORE:J10 to SID:J2 (not all pins are used) yes, since it has no inputs, but only outputs, it's not critical to let the appr. pins open outputs should be "open" (don't connect it with ground or a pull-up resistor) Outputs -> open Yes - there will be a layered (with less pots) and a full control (with a lot of pots), so the stuff will fit on the 19" panel anyhow :) Coool! In Germany it is currently very difficult to purchase a SID at Ebay ;-) Best Regards, Thorsten. Regards Ian

Hi Pat, the MIDIbox SID hasn't reached the functionality of the SIDstation yet, and I don't plan to clone this product. The synthesis results are hard to compare, since the LFO/ENV/Pitch generators have been programmed on a different way. So, I think that there are a lot of sounds which can only be realized with a MIDIbox SID, other sounds which can only be realized with a SIDstation. All features which I plan to implement can be found at http://www.ucapps.de/midibox_sid.html, these are functions from the SIDstation (or in fact functions which have been invented by the C64 hackers in the last 20 years), partly some new things like CV outs, which allow to control analog filters or Fx gear, and a user interface with a lot of pots & buttons :) Best Regards, Thorsten.

Thats the purpose of the "Display PlugIns": it will be possible to program an own display routine (doesn't matter if for LCD dotmatrix, graphic or LED displays...) and to transfer the code via MIDI into the flash memory of the MIDIbox. I will provide some examples, so that everybody should be able to change them for his needs Motto: create your personal MIDIbox Skin ;-) Best Regards, Thorsten.

Hier mal die Knoepfe (und bei der Gelegenheit die Pots), die ich so benutze: MIDIbox Plus: Reichelt: | Pots 10 k | x | P6M-LIN 10K | 0.53 | | Knobs for the Pots | x | KNOPF 15 GR | 0.64 | | Caps for the Pots | x | DECKEL 15 GE | 0.09 | MIDIbox64: Reichelt: | Pots 10 k | x | P6M-LIN 10K | 0.53 | Conrad: | Softtouch Knobs | x | 715883-88 | 0.89 | (die haben vor dem Teuro mal eine Mark gekostet!) MIDIbox16E: RS: | ALPS STEC16B36 encoder, 36/72 steps/revol. | x | 2651723 | 2.50 | Reichelt: | Knobs for the Pots | x | KNOPF 15 SW | 0.64 | | Caps for the Pots | x | DECKEL 15 RT | 0.09 | Wie man sieht, bieten Albs und Canford also durchaus gute Preise! Gruss, Thorsten.

You can also check it without an AINX4 module - the MIDIbox64 will send 8 values at the same time due to the missing multiplexer, but for testing purposes this is ok - your schematic is correct. Best Regards, Thorsten.

Sorry, this was an error in the part list (fortunately the schematic, the PCB and the Reichelt ordernumber was correct) - it should be a 100 Ohm resistor. Btw.: the resistor just only opens the possibility to reset the PIC without a power-off by applying Vss to MRST# for a short moment. It's for my personal use ;-) --- instead of buying a new resistor, you can just bypass it (take a bridge and clamp the MRST# pin directly to +5V) Best Regards, Thorsten.

I just uploaded the list of components: http://www.ucapps.de/mbhp/mbhp_mf_orderlist.txt yes, the MAX4427 could also work - Which H-Bridge is the cheaper one? Best Regards, Thorsten.

You forgot the picture :) A good idea! So you can reuse the knobs and faders when the firmware provides a control surface :) Best Regards, Thorsten.

Hi Pete, Thats a good idea! Note: so long as you don't use the MIDI-In for other MIDI gear, you can get use of the internal MIDI merger and plug the floorboard directly into the MIDIbox64 - the program change commands will just be forwarded to the MIDI Out. Yes, and the fastest way to select patches :) I plan to implement the ideas for the "next generation" step by step. Most ideas will be integrated into the MIDIbox64/MIDIbox16E/MIDIbox MF firmwares: Pot/Button-Groups with seperate banks, Button-Matrix like known from calculators, MIDIbox-Link which allows to build a network of up to 16 MIDIboxes without a MIDI chain, Display PlugIns which allow to customize the display output - and all upcoming ideas :) It seems that the MIDIbox projects will never be finished ;-) Best Regards, Thorsten.

Alright, it's on the ToDo list now. Btw.: the next MIDIbox64 version will not provide motorfaders anymore (due to the redesign, which comes with a seperate firmware) - this frees some memory for nice new features. Btw2: In one of the next releases, the sequencer part will be seperated - so I'm able to add functions which are currently under discussion (Pot/Button-Groups with seperate banks, Button-Matrix like known from calculators, MIDIbox-Link, Display PlugIns with customizable "skins"), and for the sequencer all the features which are listed under http://www.ucapps.de/midibox64.html :) Best Regards, Thorsten.

Hi Serge, thanks a lot for this great enhancement! Although all the values whithin the .ini file will put off most of the users, the customization feature opens a lot of new possibilities, which cannot be found on any other freeware or shareware tool! Now I can start to create a special .ini file for the MIDIbox SID which allows everbody to control the sound parameters without a hardware controller - of course, this is not the perfect solution -- we all want to get rid of those colourful PC mouseclicking tools ;-) -- but it will be the most prefered solution for people who don't want to spent too much money for the SID synth. Btw.: to simplify the creation of the .ini file, I will just write a perl script which generates the setup based on my constraints :) For MIDIbox SID control, one important function would be necessary, could you please add it? It's a "pot element", which isn't a pot, but in fact a set of 7 toggle-buttons, which allows me to switch on/off flags within a CC parameter. For example this parameter: CC # | Hex | Description | Range | Reset 32 | 20h | Voice 1/2/3 Waveform | | 4 | | Bit 0: Triangle | | | | Bit 1: Saw | | | | Bit 2: Pulse | | | | Bit 3: Noise (disables all other waveforms)| | | | Bit 4: Disable Voice | | | | Bit 5: Sync | | | | Bit 6: Ringmodulator | | | | Example: 02h = 2 = Saw | | | | Example: 05h = 5 = Triangle & Pulse | | | | Example: 21h = 33 = Triangle & Sync | | can only be handled with such an "set of toggle-buttons" I will publish my MIDIbox SID skin, as soon as this feature is available! :D Best Regards, Thorsten.

Darauf wird es in den naechsten Jahren wohl hinauslaufen, allerdings so weit rueckwaertskompatibel, dass man Stueck fuer Stueck seine bereits fertig gebaute(n) MIDIbox(en) erweitern kann - ich habe keine Lust, meine fertigen Gehaeuse in den Muell zu werfen, und alle anderen User sicherlich auch nicht ;-) Mit dem MIDIbox-Link moechte ich zunaechst einmal erreichen, dass man nur noch eine MIDIbox an die MIDI-Schnittstelle des PCs anschliessen muss, und die MIDI-Chain obsolet wird. Welche Box den Master spielt, und welche Boxen eine eindeutige Slave-ID erhalten, ist sekundaer - jeder kann, wenn er will, aber es kann nur einen geben. ;-) Desweiteren soll es moeglich sein, von einem Master aus Kommandos an die Slaves zu uebermitteln, wie z.B "Bank Switch", "Snapshot" oder "MIDI Learn". Diese Kommandos sind ja bereits implementiert, es fehlt eben nur noch der Link (der wird ueber die superschnelle synchrone serielle Schnittstelle gehen!) und die Moeglichkeit einer effizienten Bedienung - deshalb moechte ich das in ein neues Tastaturinterface gleich einfliessen lassen. Das Handling das Du beschrieben hast, ist bereits realisiert: bei der MIDIbox16E gibt es 4 x 8 Baenke, die sich via SFB ueber 12 Taster ansteuern lassen. Siehe auch http://www.ucapps.de/midibox16e/midibox16e_sfb_table.txt. Was fehlt, ist das Interface zu einer Matrixtastatur - und die muss ich wohl bald mal in Angriff nehmen, mir gefaellt die Idee naemlich sehr gut (gerade in Hinblick auf den MIDIbox Sequenzer :) Was ich nicht unwichtig finde ist die Moeglichkeit, Bankgruppen zu bilden (siehe Saschas aka AK12 Posting). Das sollte dann soweit gehen, dass man auch jedem einzelnen Bedienelement mehrere Baenke (bzw. Zuweisungen) verpassen kann, die sich fuer jedes Element einzeln anwaehlen lassen - und zwar voellig ohne komplexe Menuestrukturen. Leider kann ich momentan erstmal nicht viel mehr dazu beitragen (eigentlich wollte ich ja drei, vier Wochen erstmal gar nix mehr mit den MIDIboxen machen und mich voll auf meinen Beruf konzentrieren ;-)) aber bald geht es weiter! Gruss, Thorsten.

For all who are interested: the MF module is up and running :D Schematics and PCB layout can be found on the MBHP MF page http://www.ucapps.de/mbhp_mf.html The first alpha firmware will be available as soon as I have more sparetime again. Here are some informations for the guys who want to upgrade their existing MIDIbox MF: in difference to the old design the motors are now supplied with 8V. So, you need a LM317 regulator to adjust the correct voltage. With higher or lower voltages the faders will not be moved correctly, since I calibrated the PWM generator for this voltage manually. In worst case (all motors are active), the current load is about 1A! With my current test program, the motorfaders are repositioned very exactly with a 8 bit resolution (planned:9 or 10 bit) in less than 0.5 seconds. There is only one imperfection: they are not moved with exactly the same speed. This is not a software problem, but a mechanical problem (I exchanged the faders to ensure this). I will try to implement some kind of automatic calibration which tries to find out the optimal PWM table values for each fader seperately - an interesting task ;-) Best Regards, Thorsten.

Jep, das kommt ziemlich nahe an die "Next Generation" MIDIbox. Ein Tastenfeld macht auf jeden Fall Sinn, und der Bankmechanismus muss ergonomischer werden. Ich sammle diese Ideen nun erstmal und versuche irgendwann, alles unter einen Hut zu bringen. Bei der Bedienung muessen zum Beispiel auch noch die Moeglichkeiten durch den "MIDIbox Link" beruecksichtigt werden, so dass man von einem Terminal (Tastenfeld+Display) aus alle MIDIboxen ansteuern kann. Gruss, Thorsten.

We could share a free webspace account for uploads - does anybody know a good provider with a fast connection? Best Regards, Thorsten.

I don't want to open my laptop just to test this ;-) but since touchpads are based on the same technology, it should work on the same way. I'm not sure, but my experiences with the Yamaha service center are very good. Some years before I wanted to replace a damaged key; after I phoned with the german agency, I got a replacement in between 2 days for about 10 DM (= 5 EUR) (inclusive shipping!) Best Regards, Thorsten.

yes, thats exactly the reason! :) Best Regards, Thorsten.

Alright it makes sense. This feature can be implemented for all MIDIboxes except MIDIbox Plus, since this firmware uses the whole EEPROM memory for storing the snapshot data of 16 banks. Best Regards, Thorsten.

Auf jeden Fall werde ich ein 2x40 Zeichen Display unterstuetzen, das verwende ich naemlich bereits zur Darstellung von Debug-Infos :D Man koennte natuerlich auch mehrere Displays parallel ansteuern, dazu muesste man lediglich die Enable-Leitung multiplexen. Allerdings frage ich mich dann so langsam, in welcher Form ich die Firmware veroeffentlichen soll. Vielleicht sollte ich einen festen Einsprungsvektor fuer die Display-Routine einrichten, der auf einen reservierten Bereich zeigt. Diesen koennte man dann jederzeit mit seinen eigenen Display-Routinen ueberschreiben (von mir aus auch via MIDI). Neudeutsch nennt sich das "PlugIn"... oder "your private MIDIbox-Skin"? ;-) Hinzu kommen dann feste Adressen zur Berechnung und Darstellung von Dezimal/Hexadezimalzahlen, Grafikzeichen, Textausgabe - und feste SFR adressen fuer die aktuellen Poti/Fader/Encoder/Button-Werte Benni: die will ich haben!!! Leider habe ich meinen ELV-Katalog verschlampt, und die Webseite rueckt nicht besonders viele Informationen ueber die LED-Anzeigen heraus - hast Du vielleicht zufaellig die Bestellnummer parat? :) Ilmenator: diesen Controller koennte man so richtig Galaxy-maessig aussehen lassen, vielleicht passend zum Alesis Andromeda? ;-) Jo, wenn man die Encoder versetzt, koennte es klappen. Was die Ansteuerung des Displays betrifft, so wird mir die PlugIn-Geschichte immer sympathischer; das Grundgeruest fuer die verschiedenen Display-Typen stelle ich gerne bereit, die Ausgabe darf jeder selbst programmieren. Gruss, Thorsten.

...sure, if you write me how to translate "Contributions in greek language" :) Best Regards, Thorsten.

Hm... do you notice the same effect when you use an isolated plug for the power-in and connect the ground of the MIDIbox with the metal case? Because this should be the common wiring. Best Regards, Thorsten.

Rippon controllers can be connected like common pots and don't require special electronic parts; here an example: This controller is from an AN1x synthesizer (it can be ordered as replacement part from Yamaha). With no pressure it has a very high impedance, thats the reason why a 10k pull-down is connected between the output wire and ground in order to prevent floating values. With preasure the resistance varies from 0k to 13k from the left to the right side. Best Regards, Thorsten.

Hi Christoffer, I've just uploaded a pdf file which is much easier to read :) http://www.ucapps.de/mbhp_lcd.html > A is Vled + and C is Vledg - Right? yes, A stays for Anode, C for Cathode Best Regards, Thorsten.

Hi Macwreck, these are all special requests where I have to say "sure, the MIDIbox64 can do it, if you modify the firmware by yourself". I can only provide programming examples or ready-made programs which I use by myself, but customizations for controllers which I never touched by myself is nothing for a sparetime project ;-) Here are some inspirations: to 1) see http://www.ucapps.de/floorboard.html, to 2) registered values can be realized with meta events. I can send you a modified source code via email, which includes a up/down meta event as example. 3) groups and individual control will be provided by the "next generation" MIDIbox which is currently discussed on the german board (english summary later...). But it can take a long time until this project is ready for your requirements... ;-) Best Regards, Thorsten.