TK.

I programmed on a perltk based GUI some years ago, it didn't make fun. Perl isn't really an object oriented language (tcl as well), therefore I wouldn't prefer these languages for graphical user interfaces. Of course, simple things are easy to do, but once the complexity increases (and this is the case for MIOS Studio), then you will notice that you are on a one-way-street. Btw.: Hiroo Hayashi implemented the C++ based MIDI API hook for win32-perl some time ago, I was one of the first users and told him about JSynthLib. Some months later I found Hirro again as one of the main contributors of JSynthLib --- I guess that he found out the same like I wrote above. ;-) Best Regards, Thorsten.

Hi Pearl, Yes, there are limitations, which can easily be fixed. E.g., if the error happens on a "rgoto" or "bra", use "goto" instead If the error happens on a "rcall", use "call" instead If it happens on a "bz" or "bnz", use "skpnz/skpz" and "goto" or "rgoto" instead Just take a look into the main.lst file and search for the error message, this should make clear where it exactly happens Alpha version (not complete!) of C based MIDIbox LC can now be downloaded from this location: http://www.ucapps.de/mios/midibox_lc_v2_0_alpha1.zip Best Regards, Thorsten.

Hi John, the documentation of the MIDI filter project is a little bit outdated. It refers to an old PIC16F solution, but can currently be replaced by a PIC18F452 core + MIOS, with all it's advantages (integrated low-level drivers for all peripherals you want to use) MIDI processing is very easy with MIOS, especially when you are using the C wrapper. There is a special "hook" (C function) which is called each time when a complete MIDI event has been received. Let's say you want to send a program change + bank message when a program change is received, the appr. code is: ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS when a complete MIDI event has been received ///////////////////////////////////////////////////////////////////////////// void MPROC_NotifyReceivedEvnt(unsigned char evnt0, unsigned char evnt1, unsigned char evnt2) __wparam { unsigned char pc; unsigned char bank; // expect program change on channel 1 (-> 0xc0) if( evnt0 == 0xc0 ) { // program change number (0..127) is in evnt1 // we've stored the "mapped" p.c. + bank message in BankStick // the address is 2 * received p.c. number pc = MIOS_BANKSTICK_Read((evnt1 * 2) + 0); bank = MIOS_BANKSTICK_Read((evnt1 * 2) + 1); // send these MIDI events out MIOS_MIDI_TxBufferPut(0xc0); // Program Change, Channel #1 MIOS_MIDI_TxBufferPut(pc); MIOS_MIDI_TxBufferPut(0xb0); // Bank Change, Channel #1 MIOS_MIDI_TxBufferPut(0x00); // or 32 or 0 and 32... depends on sound module MIOS_MIDI_TxBufferPut(bank); } } [/code] This is only a simplified examle, I'm sure that you will extend it once you are able to play with the hardware :) A LCD and DIN module makes sense (for the DIN, 8 buttons are propably enough, so you could build a single 74HC165 on a breadboard). For the BankStick I'm not sure, because if you only want to store 128 settings, and if each setting contains a program change and bank number, then the internal 256 byte EEPROM would be sufficient. In this case use the MIOS_EEPROM_* functions instead of MIOS_BANKSTICK_* Best Regards, Thorsten.

thanks kc, I've added the two cards to the list (I haven't added the motherboard to avoid confusion...) Best Regards, Thorsten.

:'(

No, faders are not configured in mios_tables.inc - it should work without any additional configuration. Could it be that you set "NUMBER_MOTORFADERS" to 0? It must be 8 - only "ENABLE_MOTORDRIVER" has to be set to 0 Best Regards, Thorsten.

Hi Pearl, another question: are you interested in beta-testing the C version - maybe it will be easier for you to add some modifications Best Regards, Thorsten.

Hi George, if you don't expect an quick reply, it's ok :) Best Regards, Thorsten.

Hallo, wenn Du mit Generic Remote arbeitest, moechtest Du nicht wirklich die MBLC Applikation verwenden. Diese Emulation besitzt ja quasi keine Eigenintelligenz, sondern wird komplett vom Host (Logic, Cubase, ...) gesteuert - deshalb auch diese seltsamen MIDI Events, die von der Generic Remote Unterstuetzung nicht richtig verarbeitet werden. Doch Kopf hoch: es gibt ja noch die MIDIbox64E (ein generischer Controller), und diese Applikation enthaelt ein vorkonfiguriertes Setupfile for die MBNG Hardware :) Also: lade am besten mal das setup_midibox_ng.hex file hoch, und anschliessend das midibox64e.syx file aus dem mk_syx.zip Packet Gruss, Thorsten.

Hi, the "rate" lable is an error at my own frontpanel (you will only find this error in the pictures, but not in the .fpd file), it's the depth parameter which is controlled by this encoder Best Regards, Thorsten.

Hi Maik, it should work, it's a nice modular solution! Best Regards, Thorsten.

Hi, a song consists of 128 positions, and each position can be looped up to 16 times. It's also possible to jump between different positions. This jump feature will be enhanced in future, so that you can select the "entry point" within a song from a keyboard. This will redefine the usage of a song - let's say you will have 16 entry points selectable with 16 keys, they will play 16 phrases which consist of up to 16 song positions Best Regards, Thorsten.

Hi Alkex, it seems that the MBSID application tries to initialize the BankStick. You should hear 128 "peeps", thereafter everything should be ok. If you haven't connected a BankStick, you possibly forgot the 1k Pull-Up at pin RA4? Best Regards, Thorsten.

Hi Allan, currently you can forward any parameter you want to any number of AOUT channels you want... because the routing is hardcoded ;-) A user-configurable option will be available sooner or later, but since there are so much possibilities, this is currently a "low priority" feature for me. The CS allows you to modify parameters of all selected oscillators at the same time. It doesn't matter which oscillator is selected. So, let's say you are using OSC1 and OSC2 for a nice saw sound, and OSC3 for percussions. Then just select OSC1 and OSC2 (both LED should lit), and tweak the Finetune parameter. Then select SID 2, do the same, and so on... It's even possible to select multiple oscillators and SIDs at once --- since the oscillators are not synchronized (by default) you will get a very fat sound (by default ;-)) You see, the control surface allows such a quick usage, that you don't really need such special features like global finetune. In my oppinion it would complicate the menu structure too much. Best Regards, Thorsten.

Hi, in my opinion a 2x16 display isn't really useful for a LC emulation, other people are saying that they only use the LC as mixer replacement and don't need any display... so, hard to say if you feel really satisfied with this solution, this question has to be answered by yourself. Disabling motor driver: see main.asm (C version: main.h) Best Regards, Thorsten.

Hi, yes, there wasn't that much memory in the small PIC16F877 to support larger displays... Best Regards, Thorsten.

Hi Steve, yes, thats correct. Regardless of what I'm saying, the schematics are always the reference ;-) Best Regards, Thorsten.

Hi, this is not possible with the MB64E application, see also http://69.56.171.55/~midibox/forum/index.php?topic=4834.0 just read the main.asm (c version: main.h) file, it contains a lot of additional informations :) You can disable the motor driver Best Regards, Thorsten.

Hallo Sascha, ich bin kein Cubase User, und besitze lediglich eine (etwas aeltere) Demo Version von SX. Ich gehe mal davon aus, dass Du versucht hast, die MBLC als einen normalen MIDI Controller zu konfigurieren... das wird so nicht funktionieren. Unter Geraete->Geraete konfigurieren... sollte sich die Option "Mackie Control" befinden, hier kannst Du diesen Controller Typ einrichten. Ausserdem musst Du die Applikation vorher neu assemblieren, und dabei in main.asm die LC_EMULATION_ID auf 0x14 setzen, so dass eine Mackie Control erkannt wird (Cubase ignoriert die Logic Control ID) Frage nebenbei: ist dein Controller mit zwei 2x40 Displays ausgestattet? Falls nicht, waere die MIDIbox MM besser geeignet, die kommt mit einem 2x40 Display aus. Gruss, Thorsten. P.S.: dieser Tip ist mit der neuen C basierenden MBLC implementierung obsolet - diese bietet eine automatische ID erkennung

Hallo, laut Datenblatt betraegt vdd-v0 bei 25° ca. 4.8V (typical). Somit muss an V0 ca. 0.2V anstehen - es ist also keine negative Spannung notwendig. Hast Du Dir mal das Pinning im Datenblatt genau angesehen? Mit 0V an Pin 1, 5V an Pin 2 und 0V an Pin 3 solltest Du bereits die Kloetze sehen (uninitialisiertes Display) --- kannst Du diese einfache Verschaltung nochmal ueberpruefen? Gruss, Thorsten.

Hallo Basti, dieser Fehler ist mir bekannt, ich habe allerdings bisher noch keinen Weg gefunden, den Explorer dazu zu ueberreden, die Seite korrekt darzustellen. Mein Tip: verwende Mozilla, Firefox oder einen anderen alternativen Browser (das hat auch noch andere Vorteile, bspw. bessere Security) Spezielle Hardware-Jumpersettings gibt es bei der MBCV nicht. Die Software-Optionen sind in main.asm beschrieben Gruss, Thorsten.

super! :) Gruss, Thorsten.

This is the MIDIbox SID made by Klingen - the box design might look familiar, but note that this panel is selfmade and not from Schaeffer! :) Klingen wrote:

it seems to be the first MIDImon in the gallery :) Seppoman wrote: