TK.

here is a howto for cubase, maybe it helps http://www.avishowtech.com/midibox/wiki/index.php/Cubase Best Regards, Thorsten.

Hi, the device ID does matter. Maybe you've changed it by accident (e.g. with JSynthLib?) The JSynthLib editor provides a function to change it back to 0 (or just read in the Wiki how to do this) Or even more simple: just burn the firmware again into the PIC Yes, the noise at the beginning sounds like a reset (therefore: good) You could send a program change (try different MIDI channels, maybe you've changed it also!) in order to check if the MIDI In is working, because this should change at least the Patch number Best Regards, Thorsten.

Servus, freut mich, dass Dir die Box gefaellt! :) Der Treiber laesst sich eigentlich ziemlich einfach mit der MB64 Applikation verknuddeln - du musst lediglich das app_lcd.inc aus dem Treiberpacket in das midibox64_v2_3 Verzeichnis kopieren und neu assemblieren. Falls im ID Header noch keine "7000" (fuer Custom Driver) steht, muesstest Du dies entweder mit der change_id Applikation aendern, oder unter USER_Init (File: main.asm) folgende Zeilen hinzufuegen: ;; select LCD type #7 (custom LCD driver, hooks in app_lcd.inc will be used) movlw 0x00 ; not used by this driver movwf MIOS_PARAMETER1 movlw 0x00 ; not used by this driver movwf MIOS_PARAMETER2 movlw 0x07 call MIOS_LCD_TypeSet [/code] Hast Du den Nokia Treiber schon ausprobiert? -> lcd7_pcd5844.zip Das vorkompilierte .syx File sollte auf allen LCDs ein Testbild anzeigen Best Regards, Thorsten.

Es geht vielleicht auch ohne Schaltplan - aus main.asm ; use PORTA and PORTE (J5 of the core module) for 8 additional gate outputs #define ENABLE_J5 0 [/code] Gruss, Thorsten.

Hallo, Du machst ueberhaupt nichts falsch, es handelt sich hierbei um ein prinzipielles Problem mit der Aufloesung und dem supporteten (hard/softwarespezifischen) Datenformat. Hier kocht fast jeder Hersteller sein eigenes Sueppchen. Es faengt schon damit an, mit welchem Event (data entry MSB oder LSB) die Daten uebernommen werden - sind MSB und LSB vertauscht, hoerst Du fuer kurze Zeit ein haessliches Knacksen. Oder der Heresteller supported lediglich eine Aufloesung von 7 bit, in diesem fall wird meistens nur das MSB gesendet, manchmal wird aber auch das LSB verlangt und das MSB ignoriert. Manchmal (vor allem bei "biased" Values, also +/- Werte), unterscheidet sich die Berechnung von MSB und LSB - und dies scheint bei Dir der Fall zu sein. Ich wuerde Dir empfehlen, einfach mal den Programmautor zu kontaktieren - es sollte nicht zu schwierig sein, die Software um weitere Datenformate zu erweitern. Gruss, Thorsten.

If you don't remember the enjoyment which comes up when hearing the first SID sounds, then it propably never worked ;-) Once you've burned the PIC16F firmware into the PIC, you will hear the default sound. There is no need for uploading a patch just to hear anything from the SID Best Regards, Thorsten.

Hi Jorge, there must be something wrong with your installation (I'm no Windows expert...) However, you could use Serge's SysEx loader which allows you to upload the .syx file with a different device ID w/o the need for generating a new .syx Best Regards, Thorsten.

nice input, wazoo! :-) They provide a common cathode, and since it's possible to customize the LED patterns, I don't see problems from the software side :) FAQMARKER Best Regards, Thorsten.

Hi Alex, the biggest problem with sending MIDI data via RF is, that MIDI doesn't provide some kind of flow control. There is a defined baudrate (31250 baud), this means that the transmitter needs to support the appr. bandwidth to avoid buffer overflows. At the receiver side it must be ensured that a bitstream is received error-free. Thats very difficult at this baudrate (impossible at large distances and a lot of EMC arround?) There are three solutions: adding an ECC (error correction code) so that at least one bit errors can be repaired, and multiple bit errors are regognized (so that your robot software never executes invalid commands). Second solution: a bidirectional connection between Transmitter/Receiver + a transfer protocol to realize flow control (e.g. receiver has to acknowledge the data with a checksum). Third (and most simple) solution: try to get two premade bluetooth based COM interfaces (or bluetooth ASICs if they are available in small quanitties) which connect together. If they don't provide MIDI baudrate, then you can just use the MIDIbox-to-COM option (which runs at the standard PC baudrate 38400) Best Regards, Thorsten.

Hi Arumblack, I'm no eagle expert, therefore I will only answer to a subset of your questions: I think it's only required that you don't chain ground tracks of the analog domain with the digital domain and vise versa. Both domains should be grounded from a central point. Exceptions are allowed of course, e.g. if the digital part at the end of an analog section doesn't consume much power. But it needs some experience (means: practice) to have a feeling for this. And you cannot get such a practice when you are not trying it out by yourself, no? :) If you want to be at the secure side, then try to seperate the grounds as much as possible. all SID modules can be powered from a single stabilized PSU w/o disadvantages. Of course, you need different regulators if you are mixing 6581 and 8580 Maybe somebody with more layout experiences can give some useful tips? Best Regards, Thorsten.

Hi William, I cannot give you any info if this works with Nuendo or not, I'm a Logic user... Best Regards, Thorsten.

Hi Redhead, I don't think that this will work - MIDIbox LC is completely controlled by the host application. So - maybe your host already provides such a feature? Best Regards, Thorsten.

Die Inkrementalgeber sind zu teuer! (vielleicht hilft diese Aussage, liest Conrad mit? ;-)) Btw.: aus der Produktbeschreibung: Gruss, Thorsten.

Simple and fastest solution without much programming effort: Just map the note values to new values by using a table with 128 entries: TABLE_ADDR MY_TABLE movf MIOS_PARAMETER1, W ; (contains the note value) TABLE_ADD_W ; add to table pointer tblrd*+ ; read byte from table movf TABLAT, W ; result in TABLAT ;; now you can do what you want with the new value ;; should be located at the end of the assembler program MY_TABLE db 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07 ;; ... 128 bytes (=16 lines) in total db 0x78, 0x79, 0x7a, 0x7b, 0x7c, 0x7d, 0x7e, 0x7f [/code] Best Regards, Thorsten.

Hi Julian, Voti normaly delivers within 1-2 days, but it seems that he sold more encoders then expected in the last weeks. Currently he is waiting for a delivery of new encoders, it seems that it is stucked in customs (it can take one day or multiple weeks, those public nameities are always unpredictable :-/) Best Regards, Thorsten.

It's a piece of cake with cmios :-) ///////////////////////////////////////////////////////////////////////////// // 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) { // convert note off messages to note on with velocity 0 if( (evnt0 & 0xf0) == 0x80 ) evnt0 = 0x90 | (evnt0 & 0x0f); // react on notes at channel 1 if( evnt0 == 0x90 ) { // forward the 7-bit value to the first DOUT shift register MIOS_DOUT_SRSet(0, evnt1); } } [/code] Best Regards, Thorsten.

Hi, yes, you need 2 AINX4 modules for the vintage option, they have to be connected in the same way like for MIDIbox64 Best Regards, Thorsten.

Hi Davo, a lot of program changes will be required for this different concept, thats all what I can say to this topic. Best Regards, Thorsten.

Hi Matteo, search for "CS_MENU_BUTTON_SID3" and "CS_MENU_BUTTON_SID3" in cs_menu_buttons.inc and change it in the following way: CS_MENU_BUTTON_SID3 movlw 0x00 movwf SID_BANK goto CS_MENU_MS_NotifyBankChange CS_MENU_BUTTON_SID4 movlw 0x01 movwf SID_BANK goto CS_MENU_MS_NotifyBankChange [/code] Best Regards, Thorsten.

Cool! Danke fuer den Tip, werde ich heute noch auf der mbhp_mf Seite einfuegen. Fuehrt Conrad auch Inkrementalgeber? (Rotary Encoders) Gruss, horsten.

It's even harder for you to change the code then changing the wires ;-) Toggle state: just save the new state with the snapshot button once all LEDs are off Best Regards, Thorsten.

Hi Robin, you are making things more complicated then they are... you don't need a specific address for the table, and you can put it into the assembler code where you want - once you are using a label (BANKSTICK_DUMP_TABLE) it will get automatically a reference which can be used in the code (-> TABLE_ADDR BANKSTICK_DUMP_TABLE). It must only be ensured that the table is not located within a function. Means: you have to make sure that the PIC never executes the data of the table (so, never do a "goto BANKSTICK_DUMP_TABLE"). Normaly I'm putting tables at the end of an .inc file, the function above the able must end with a "return" or a "goto"/"rgoto" Best Regards, Thorsten.

an auto detection for the MIOS ID itself is infeasible, each core module in the MIDI chain needs an unique ID, otherwise it wouldn't be possible to address informations (code/data) to a dediated PIC. But you don't need to change any code line in order to change the IDs of the sysex blocks, you only need to re-generate the .syx file from the .hex file with the hex2syx.pl script like described in the README.txt of the MIOS package, and you have to follow the step by step instructions which can be found http://www.ucapps.de/midibox_sid_csB.html (they are still valid) Best Regards, Thorsten.

Hi Julian, 8 AOUTs and 8 gates are planned Best Regards, Thorsten, (P.S.: the user manual is finished: http://www.ucapps.de/midibox_fm_manual.html)

Hi Martin, check the "planned additional features" list under http://www.ucapps.de/midibox_seq.html - this is the stuff which will be implemented sooner or later and which should fit into a single PIC. Once this has been done (maybe in one or two years or so...) I will think about extensions ;-) Arp styles are already available. In fact the definition of an arpeggio sequence is the definition of a style (the concept is not like that what can be found in common synthesizers) Best Regards, Thorsten.