TK.

Hi Matt, this could be realized with the "MIDI merger" application, which provides two MIDI Ins and one MIDI Outs. It requires some additional modifications to parse for program change events, however - the source code is free available ;-) Best Regards, Thorsten.

Hi Rob, the open analog input A4-A7 should be connected to ground, otherwise the box will send random MIDI events Best Regards, Thorsten.

Hallo Sly, Die ID 00...0142 ist nicht optimal, damit wuerdest Du die Device ID auf 42 setzen. In Deinem Fall waere 00..0100 besser geeignet. Zur MF Calibration erstmal eine Frage: wenn Du den ersten Fader bewegst, sollten sich die restlichen Fader automatisch mitbewegen. Laesst sich das bei Dir reproduzieren? Gruss, Thorsten.

Hi DriftZ, yes, a LED for each pot makes sense. Will be supported with the next update of MIDIbox64 SEQ 8 tracks with the PIC18F based SEQ: maybe ;-) Best Regards, Thorsten.

Hallo Sebastian, zu den LCDs: sofern Du "character LCDs" verwenden moechtest, kannst Du quasi jedes hernehmen, sie sind quasi alle HD44780 kompatibel. Bei EBay gibt es 2x40 LCDs im Ramschverkauf (siehe bspw. http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=3018908161&category=12070 Grafik-LCDs: hier wird es schon schwieriger, ein passendes zu finden. Momentan werden nur KS0108 kompatible unterstuetzt. Sobald ich die zusaetzlichen Treiber in MIOS V1.2 integriert habe, wird es zu diesem Thema eine bessere Dokumentation geben 2: man muss den Bootstrap-Loader einmalig in den PIC18F einprogrammieren, danach funktioniert der Update auch ueber das MIDI-Interface. Falls Du den JDM nicht nachbauen moechtest, kannst Du mir den PIC auch einfach (zusammen mit dem Rueckporto) zuschicken 3: die Reihenfolge ist egal, in den Listen (mios_tables.inc und lc_io_table.inc) traegt man einfach die Pin-Zuordnung ein, den Rest uebernimmt die Software :) Gruss, Thorsten.

Hallo Sly, Du hast Deine Box wirklich schnell auf die Beine gebracht! :) den idealen Kalibrierungswert kann man mit der "mf_calibration" Applikation ermitteln. Siehe auch: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1049264534 Zu Logic: irgendwo unter Options->Control Surface->Allgemeine Optionen (bin leider gerade nicht unter Windows eingeloggt...) kann man die MIDI-Bandbreite einstellen. Per default steht sie auf 50%, mit 100% erhalten die Fader oefters einen Update, und bewegen sich somit "smoother". LTC: hierbei gibt es das Problem, dass der Bootloader bereits vor der MIOS Initialisierung einen SysEx-Request mit der falschen Baudrate verschickt. Deshalb waere es besser, wenn Du das "to-COM" Flag in der PIC ID einstellen wuerdest (siehe Concepts->MIOS->Bootloader). Gruss, Thorsten.

Ich bezweifle, dass das moeglich ist. Und wenn, waere die Ansteuerung viel zu langsam :-/ Der PIC ist halt nur ein 8 bit controller... Best Regards, Thorsten.

The random notes could be caused by an "unterminated" DIN chain. So far as I remember greg's layout doesn't come with the regired 10k pull-up resistor on the input of the last 74HC165 (Pin 10). It should help :) Best Regards, Thorsten.

The command set of this display is the same, so it should be compatible. To the 4x20 LCD issue: it seems that not all wires are connected correctly. Black lines are visible when the display has not been initialized. Best Regards, Thorsten.

Hi Michael, the crystal type seems to be ok (I checked this on the farnell homepage), so it must be another problem. Could you create a MIDI-Ox logfile and post it here? It would be interesting, on which way the MIDI events are corrupted. Best Regards, Thorsten.

Hi Shawn, so long as you are using logic ICs which are supplied with the same voltage, resistors between the outputs and inputs are not required. The current consumption of the input is 0.5uA, this means that you could (theoretically) drive up to 50.000 inputs with one PIC output. Ok, in practice the number is much lower due to capacitancies, but in fact with such a low consumption you don't have to take care about the max current Best Regards, Thorsten.

Hi SB, yes, the MIOS application also outputs the 1MHz clock, so that it should work. Best Regards, Thorsten.

Hi Rob, I guess that you missed this schematic: http://www.ucapps.de/mbhp/mbhp_ainx4_64pots.pdf Best Regards, Thorsten.

Hi, it seems that your simulation tool doesn't warn you that the transistors will be destroyed in this way. A direct connection from a logic IC output to the base pin leads to a high current which will fry the pn-junction. A serial resistor (1k or more) should help to reduce this current. Alternative solution: if you are using the Microchip EEPROMs (24LC256), you could use the A0 pin (Pin #1) to select the chip. This pin is wired to ground by default, if you connect it to +5V, the chip will not respond to incoming messages and is therefore disabled. So just implement a logic which selects only one chip (A0=0V), and disables all other chips (A0=5V). Best Regards, Thorsten.

No ;-) The ISA bridge will be unidirectional and only helpfull to access soundchips directly in the same manner like I did it with the SID. Best Regards, Thorsten.

No ;-) The ISA bridge will be unidirectional and only helpfull to access soundchips directly in the same manner like I did it with the SID. Best Regards, Thorsten.

sure :) If Nuendo or Cubase SX allows the use of a MC and a "Generic Remote device" over one MIDI IO port, this should work. One PIC18F core can manage up to 64 rotary encoders, so I don't see the need for two MIDIbox16E. no, thats defenitely not possible :-/ But a core with free analog inputs could handle the 9th fader yes, it would help to estimate how much cores are really required and it would be easier for me to make modifications on the picture to show how the units have to be connected. Best Regards, Thorsten.

Hi Sly, it's just a minor update. The second and fourth page on character LCD displays now shows horizontal metering bars instead of vertical - it looks much better. The update is easy: just unpack the .zip archive, replace mios_tables.inc and lc_io_table.inc by your own files, and adapt the settings in main.asm (don't replace main.asm by the file from the old release!) Best Regards, Thorsten.

yes - as the convpix.pl script has to rotate the fonts for the T6963C, this option will also be useable for your idea Best Regards, Thorsten.

Hallo Robert, es freut mich sehr, dass damit die Zukunft des (werbefreien!!!) Forums gesichert ist. Wo waeren wir heute ohne Deine Hilfe... wahrscheinlich bei Lycos :P Mittlerweile habe ich den binaeren Content (also JPGs und MP3s) auf freie Server verlagert, um das Traffic-Limit meines eigenen Webpackets nicht zu ueberschreiten. Solange Tripod und 8tung.at mitspielen, moechte ich das auch erstmal dabei belassen. Falls es Probleme geben sollte, komme ich nochmal auf Dich zurueck :) Gruss, Thorsten.

Hi Olivier, NRPNs can be sent by using meta events. However, MIDI Learn function will not help here. I will send you the source code so that you are able to program the meta information Best Regards, Thorsten.

Hi Chriss, thanks for your input! :) This was my fault - sure, the Vss (ground) connection is very important, I just have fixed the schematics. Unfortunately not, the SID chip doesn't provide an analog ground. On the other hand: I don't hear this effect... maybe you can improve the signal quality when you add an additional capacitor of 10 uF to the +5V domain of the SID module (parallel to the 100nF cap C8 ) Thats one of the known SID bugs :-( See also the interview with Bob Yannes, who designed the SID: http://stud4.tuwien.ac.at/~e9426444/yannes.html What would you have changed in the SIDs design, if you had a bigger budget from Commodore ? The issue wasn't budget, it was development time and chip size constraints. The design/prototype/debug/production schedule of the SID chip, VIC II chip and Commodore 64 were incredibly tight (some would say impossibly tight)--we did things faster than Commodore had ever done before and were never able to repeat after! If I had had more time, I would have developed a proper MOS op-amp which would have eliminated the signal leakage which occurred when the volume of the voice was supposed to be zero. This lead to poor signal-to-noise ratio, although it could be dealt with by stopping the oscillator. It would also have greatly improved the filter, particularly in achieving high resonance. I originally planned to have an exponential look-up table to provide a direct translation for the equal-tempered scale, but it took up too much silicon and it was easy enough to do in software anyway. Congratulations, you've found a software bug :) Temporary fix: in cs_menu_exec.inc add to following line CS_MENU_EXEC_GoToENV clrf CS_MENU_PARAMETER_L; begin with first envelope following call: CS_MENU_EXEC_GoToENV clrf CS_MENU_PARAMETER_L; begin with first envelope call CS_MENU_P2R_ENV_Num (similar changes have to be made for CS_MENU_EXEC_GoToLFO and CS_MENU_EXEC_GoToMOD) yes, thats correct. Step B will send MIDI data The direction can only be changed by hardware modification (in order to save performance). If you are using ALPS STEC16 encoders, the correct wiring for channel A and B can be found here: http://www.ucapps.de/mbhp/mbhp_dinx4_16enc_alps_stec16b03.pdf Good question! http://www.albs.de provides a good variety, but they are expensive $$$ :-( Does anybody know a better source? Best Regards, Thorsten.

Hi Ilmentator, both: hardware limitations and processing speed. Every software implemented MIDI In requires a pin which can trigger an interrupt, and this interrupt must be processed within ca. 1-10 uS, otherwise the serial data could get lost if multiple MIDI transmitters are sending data at the same time. The PIC shouldn't do anything else than listening to the ports. Therefore I would avoid more than one software implemented UART, this solution: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1046743910 is much better. Best Regards, Thorsten.

Hi LO, yes, MIDIbox Link works also with higher baudrates, therefore also with the LTC by using following interconnections: * LTC::J1::Vs must be connected to CORE::J11::Vs of both core modules * LTC::J1::Vd must be connected to CORE::J11::Vd of one core module * LTC::J1::Mi must be connected to CORE::J11::Mi of the first core module in the chain * LTC::J1::Mo must be connected to CORE::J1::Mo of the last core module in the chain Hope that you will try the PIC18F based MF solution again when "MIDIbox MF" has been ported to MIOS? :) Best Regards, Thorsten.

Yep :) D2k sent me his T6963C based display so that I was able to integrated a rudimental driver into MIOS. The performance of this LCD controller isn't perfect, as it displays the bytes horizontally and not vertically like the KS0108, this complicates the custom font output routine. However, there is nothing which cannot be solved (sooner or later ;-)) Best Regards, Thorsten.