TK.

The updated file can now be downloaded from this URL: http://www.ucapps.de/midibox_sid_cs/mbsid_panel2fix.dwg Best Regards, Thorsten.

Hi George, MIOS standalone is ok, but once you got the MIDI interface running, it would be better to burn the bootstrap loader into the PIC and to upload MIOS through MIDI. Because this allows you to update MIOS in future without PIC burner. However, MIOS itself provides a seperate BSL, so you should be able to upload an application via MIDI (hope that the troubleshooting guide helps...) Best Regards, Thorsten.

Hi Lorin, definitely! The example track sounds very impressing, I would build one! :) Maybe I can help you to port hardware and code to the MIOS platform - are you planning an open source release? Best Regards, Thorsten.

Hi Taylor, normaly it can be programmed into the application, MIOS code doesn't need to be touched. Which application are you using exactly? Best Regards, Thorsten.

Hallo Torben, mit diesem MIDI Merger geht das nicht - MIDI merging mit mehreren MIDI Ins ist nicht trivial (deshalb gibt es so etwas auch nicht zu kaufen) - heutzutage bevorzugt man meistens PC/Mac Interfaces mit mehreren IO Ports, und routed die Ein-/Ausgaenge direkt in der Host Software. Gruss, Thorsten.

Alright - now I see the error (in the outdated .gif file). I'm not able to view the .dwg file (it's from Klingen) - I will ask him for an update Best Regards, Thorsten.

Hi Alkex, the displaytech LCDs which I'm normaly using are also stuffed with a KS0066U controller - it's 100% compatible, but (and this is good!) faster than HD44780 Best Regards, Thorsten.

Hi, I think it's better to answer your questions in the SID boards, since some are "FAQ"s 1) yes, it's not possible to select the BankStick with JSynthLib - the core library doesn't prove such a opportunity, as a JSynthLib user I'm "mightless" It's also a known problem that the "get" function doesn't work properly - in the meantime this concept has been changed (you could download the latest sources from the CVS), but it's not complete yet and a little bit buggy... 2) which patch? 3) known and intended behaviour, the reason can be found here http://69.56.171.55/~midibox/forum/index.php?topic=4878.0, an improvement is also built into the current beta version of v1.7303 which is available on request 4) I see the point - yes, it could be useful (especially for the TB303 emulation) - which button combination would you prefer as a shortcut for such a function? Best Regards, Thorsten.

You could implement this via software to save hardware costs... Best Regards, Thorsten.

Hi, you should hear a nice PWM patch after you've uploaded MIOS and the main.syx (or any other .syx of the midibox_sid_* package). I guess, that there is a problem with you hardware - did you try the SID interconnection test? Best Regards, Thorsten.

Hi, the button handlers are in cs_menu_button.inc Using switches instead of buttons shouldn't require big changes Best Regards, Thorsten.

Hi Chriss, undo your changes and add following lines to cs_menu_button.inc CS_MENU_BUTTON_Ins1 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 0 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_Ins2 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 1 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_Ins3 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 2 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_Ins4 bcf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 3 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP1 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 0 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP2 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 1 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP3 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 2 rgoto CS_MENU_BUTTON_InsOP_Cont CS_MENU_BUTTON_OP4 bsf CS_MENU_MODE, CS_MENU_MODE_INS_OP movlw 1 << 3 rgoto CS_MENU_BUTTON_InsOP_Cont [/code] Best Regards, Thorsten.

Hi Jorge, please believe me: there is no error in the released files, you will only find this mismatch at a picture of my own SID case. You are writing about the OSC section (which provides a DADSR curve) - pwx wrote about the ENV section. Best Regards, Thorsten.

Hi. this is a common HD44780 compatible LCD, it should work without problems. Quality would also be interesting for me - it would be a great alternative display! Best Regards, Thorsten.

Hi Moxi, pattern sets can be saved within a song. Since a song has 128 positions, you can save 16*128 different setups there. Once I've enhanced the song mode (see previous mails and ToDo list), it will be possible to recall the setup without pressing the "play" button before. Also quick changes will be possible (e.g. with an external keyboard) Best Regards, Thorsten.

Hi Chriss, this should be possible by changing the CS_MENU_BUTTON_InsOP_Cont in "cs_menu_buttons.inc" . Currently it either moves the pointer to CS_MENU_SELECTED_INS_FLAGS or CS_MENU_SELECTED_OP_FLAGS into FSR0 depending on the CS_MENU_MODE_INS_OP flag... Quick change: add four additional OP button functions and set the CS_MENU_MODE_INS_OP flag there. Clear this flag within the instrument button functions Best Regards, Thorsten.

This is a really fancy MIDIbox64E made by Moxi! He wrote:

Hallo Andreas, dies ist eigentlich kein generelles PIC Programmierer-Forum, hier geht es hauptsaechlich um MIOS Projekte. Aber ich kann Dir zumindest den Hinweis geben, dass an einigen Stellen das Bus-Protokoll nicht eingehalten wird. So z.B in folgenden Zeilen: MOVLW B'00001000' ;Display AUS MOVWF PORTB CALL Pause2 MOVLW B'00000001' ;Clear Display MOVWF PORTB CALL Pause2 [/code] ich vermisse den Strobe (E=0 -> E=1 -> 2 NOPs -> E=0). Unter http://www.ucapps.de/mbhp/prg/lcd_v1.zip findest Du einen Beispielcode fuer meine alten PIC16F basierenden Projekte, vielleicht hilft es weiter. Die Bank-Warnungen habe ich mit: ERRORLEVEL -302 ; SUPPRESS BANK SELECTION MESSAGES deaktiviert (man muss beim PIC16F hoellisch auf die Bank Selection bits achten...) Warum ein Stack Underflow auftritt, kann ich auf anhieb nicht sagen. Evtl. liegt es daran, dass die Start Routine nicht sauber abgeschlossen ist. Nach dem letzten CALL befindet sich nichts mehr - der PIC wird hier beliebigen Code ausfuehren. Es waere besser, das Programm mit einer Endlos-Schleife zu beenden Gruss, Thorsten.

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.