TK.

Don't worry, another device ID is meant here which isn't essential. You can disable this dummy warning somewhere in the IC-Prog preferences. Best Regards, Thorsten.

Did you also try the MIDI In/Out ports of your PC? Best Regards, Thorsten. P.S.: the MIDI troubleshooting guide has been updated: http://www.ucapps.de/howto_debug_midi.html

...although it's cheaper than my 240x64 LCD. But it will require a seperate controller (or MBHP core module) + dedicated driver. And the contrast is possibly very bad... Best Regards, Thorsten.

Hi Nenad, seems to be a low-cost encoder, the spec doesn't say if it is detented or not... I wouldn't buy it. Why not purchasing a best-quality ALPS STEC16B03 for ca 2 EUR @ http://www.schuricht.de? However, rotary encoders are not supported by the PIC16F based MIDIbox64, they require a fast decoding routine which is only provided by PIC16F MIDIbox16E, or by MIOS of course. Best Regards, Thorsten.

Regarding your hardware setup: yes, this will work. The number of connected pots can be defined in the main.asm header, and for the DIN chains it doesn't matter. Best Regards, Thorsten.

Yep - sooner or later... ;-) Best Regards, Thorsten.

I found a solution - direct links are working again. Best Regards, Thorsten.

Sure - check the "generic remote" module, and see also http://www.midibox.org/users/dimitris/midibox_cubase_setup/index.html Best Regards, Thorsten.

Maybe sooner or later - but currently I've other priorities... so if somebody with programming skills feel interested: the changes have to be made in mb64_buttons.inc and mb64_leds.inc. The easiest way would be to switch between different DIN and DOUT maps depending on the state of a dedicated DIN. Best Regards, Thorsten.

Lieber nicht, bevor sie verdampfen ;-) Am besten baust und testest Du die MIDIbox schrittweise (Modul fuer Modul). So weisst Du, wo Du zu suchen hast, falls mal etwas nicht auf anhieb funktioniert. Gruss, Thorsten.

Fine fine, so send it to ik@midibox.org so that this FAQ will be part of the portal :) There is only one error: > make sure u have the latest sid_init.inc file it isn't sid_init.inc, but sid_ain.inc (http://www.ucapps.de/tmp/sid_ain_enhanced.zip). This file should also be uploaded to the portal - I won't support it in the future (means: I don't want to try it out with every new SID release) Best Regards, Thorsten.

Hi, the DINs are scanned every milisecond, so if the pulse width of the clock out isn't long enough, then you could use an external monoflop to enlarge the pulse. Better solution: take a look into the j5_din_v1_3.zip example, it explains how dedicated input pins can be captured. It's not limited to J5, you can use any free IO pin. The example shows, how to hook the capturing routine J5_DIN_Update to the SRIO driver, but you can also call it from USER_Tick for a higher update rate. 300 uS should be adequate enough. The J5_DIN handler will call USER_J5_DIN_NotifyToggle on every change which is comparable with the common DIN_NotifyToggle callback. Of course, you can send CC events from this function. Powersupply: balanced supplies should be seperated from digital units, so I cannot suggest to mix these voltage domains. Best Regards, Thorsten. P.S.: I will move this topic to the MIOS section since it's especially interesting for programmers.

Latency is no issue. And since I don't want to repeat myself every month, there is now a new entry in the FAQ, see QA35 Best Regards, Thorsten.

The first snapshot has been rolled out ;-) Steve: I discontinued the PIC16F version since it wasn't flexible enough. I'm using the MIOS based version by myself to turn the MIDIbox LC into a generic controller (w/o rotary encoders, this will be solved with the MIDIbox NG application) Best Regards, Thorsten.

No, the MIDImon allocates 3 DOUT registers of a DOUTX4 module. You don't need an additional core, e.g. the MIDIbox64 application allocates 8 DOUT registers maximum (=64 LEDs), this means that the remaining 8 DOUT's are free and can be used for other purposes. Just integrate the MTC module (see Concept->MIOS->Download led_digits_mtc_v1_3.zip file mtc.inc) into your project. Best Regards, Thorsten.

Fuer MIDIbox LC solltest Du auch kein anderes Display verwenden, nur ein KS0107/KS0108 basierendes Display bietet die optimale Performance. Leider kenne ich keinen Haendler, der dieses Display anbietet (andererseits: viele Distributoren stellen ihre Lagerlisten leider nicht ins Internet). Meins ist von Reichelt, d2k hat denen das letzte Displaytech 64240A abgekauft, seitdem ist es aus dem Angebot verschwunden :-( Anmerkung: das Displaytech 64240B ist uebrigens nicht kompatibel, es enthaelt einen anderen Controller mit horizontaler Ausgabe der Bytes (-> low performance) Gruss, Thorsten.

Hallo, am besten faengst Du von vorne an, um Dich langsam aber sicher in das Thema einzuarbeiten. :) Welche Hardware hast Du schon, laeuft der Core bereits? Ist ein Display angeschlossen, hast Du bereits MIOS und eine Testapplikation aufgeladen? Gruss, Thorsten.

Hallo Kay, per Software geht das leider nicht, und ich kann auch nicht empfehlen, das LCD-Modul zu oeffnen, weil es danach sehr schwierig werden wird, es wieder so zu schliessen, dass alle Pins Kontakt haben. Hier ein paar allgemeines Infos zu den unterschiedlichen Display Typen: http://www.lcd-module.de/deu/knowhow/knowhow.htm Gruss, Thorsten.

Hi, no this GLCD isn't natively supported by MIOS, since it's a low-performance display and therefore not sufficient for a MIDI realtime system. It could work with a second core module if it only has to listen to the MIDI stream (-> could be used as MIDIbox LC display). A custom display driver (LCD type #7) would be required anyhow, it has to be plugged into the MBLC application - nobody has implemented a driver for the HD61830 yet Best Regards, Thorsten.

This time I'm searching for potential crash test dummies who own at least a ready-built MIOS core, LCD, MF module (motorfader(s), DIN module (buttons) Best Regards, Thorsten.

Hi Olivier, MIDIO128 will be ported to MIOS very soon, this means that you will be able to add up to 64 analog inputs beside of the 128 inputs and 128 outputs very easily. Also a cascadable AOUT module with n * 8 channels and 12 bit resolution is in the queue for the MBHP (release date: unknown ;-)). You possibly have to program the application by yourself (based on the MIOS drivers) or to find somebody who plans to realize the same like you. I'm not able to tell you how it has to be programmed exactly (it's also a question of time... and I don't own such a hardware for testing), but I could give some proposals. Reg. the implementation of aftertouch and velocity: see this posting http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1057976738 which contains some superb informations Best Regards, Thorsten. FAQMARKER

128 inputs. With 64 buttons you've 64 remaining inputs for up to 32 rotary encoders. Best Regards, Thorsten.

Wenn Du den Grundsatz "Strom nimmt immer den Weg des geringsten Widerstandes" beachtest, geht es auch noch einfacher: [tt] . . ____ . Taster --- Masse |----|____|---*-------o | o----> +5V . . 10k | . . . . o AIN Pin [/tt] Wenn der Taster geoeffnet ist, fliesst der Strom ueber den 10k Widerstand. Die Spannung am AIN pin betraegt 0V Wenn der Taster geschlossen wird, fliesst der Strom ueber den Taster, die Spannung am AIN pin betraegt somit +5V Gruss, Thorsten. P.S.: diese vereinfachte Rechnung ist nur dann erlaubt, wenn die Impedanz am AIN Pin so gross ist, dass sie fuer die restliche Schaltung keine Belastung darstellt. Das ist hier der Fall...

Two things have gone wrong: 1) the "-os_upload" flag should never be used to convert a .hex file of a MIOS application, it seems that your MIDIbox SID directory doesn't contain a consistent project anymore. I don't know which changes you made exactly, but anything was wrong. So my suggestion: download the release again from my website, unpack it into a seperate (!) directory and do exactly the changes which are required and nothing else. Convert the .hex file within the release directory. 2) of course, when uploading an application you've to set the correct MIOS device ID (hex2syx.pl -device_id 0x.. main.hex), the core will ignore all SysEx strings which don't contain its device ID. So, use the script in the following way: d:\perl\bin\perl hex2syx.pl main0 .hex -device_id 0x00 d:\perl\bin\perl hex2syx.pl main1 .hex -device_id 0x01 d:\perl\bin\perl hex2syx.pl main2 .hex -device_id 0x02 d:\perl\bin\perl hex2syx.pl main3 .hex -device_id 0x03 Hope this helps :) Best Regards, Thorsten.

Yes - but this was also possible with the PIC16F based version. The new feature is, that all these 128 parameters can be received independent from the selected page, the PIC16F was only able to receive the 16 parameters of the selected "subbank". In fact this means that 128 virtual knobs are available, and it depends on your hardware how much can be controlled without switching to another page. With 16 encoders I highly recomment 8 additional buttons which should be assigned to the "Select Page" function, so that you can quickly change between the different views. Best Regards, Thorsten.