TK.

Hi Volg4, in the last years it turned out that especially in the UK it's very hard to find a cheap (online) shop for electronic parts. It's cheaper to order the stuff from the US The simplest solution: order the kits from SmashTV! Extremely good value, and you can get a preburned PIC, too (this saves you from building a JDM programmer)! :) Best Regards, Thorsten.

Hi bount, you are mixing digital inputs with analog inputs. The J5 solution is only for people who don't want to use analog pots - the example is directed to programmers (not for users) You have to connect your pots to J5, there is no other port where you could do this. Buttons have to be connected to a DINX4 module Best Regards, Thorsten.

Hi uclaros, appart from the high danger of destroying other MIDI interfaces like you've already mentioned, I don't see problems. I would suggest 5V DC. 12-15V will heat up the 7805 too much Best Regards, Thorsten.

MIDIbox64 doesn't support motorfaders, but (after a lot of effort from my side), you can use MIDIbox64E as an alternative firmware. This package includes a setup_midibox_ng.asm configuration which matches with the MIDIbox LC layout, and which can drive 8 motorfaders, 8 V-Pots, 1 datawheel, 8 LED rings, 64 LEDs and 64 buttons. LC/MC clone: It's not only the display which makes the difference, it's the whole concept. A MIDIbox64(E) can work independent from a host, you can control any MIDI gear with it. Advantage: very generic approach, disadvantage: a lot of effort to integrate this perfectly into a sequencer software (e.g. if you want to control VST(i)s) A Mackie/Logic Control requires support from the host software. Advantage: perfect integration. E.g., if you insert some VSTs into the channel strip, you will see the parameters automatically on LCD. No need for creating different MB64E setups. Disadvantage: beside of the higher prices for the parts, you are limited to the functions which are provided by the host (see some postings above, where somebody wants to create a grouping function) Best Regards, Thorsten.

Hi Redhead, you could add a loop to LC_ENC_SendVPot (lc_enc.inc) which sends 8 increment events from CC #16-CC #23 so long a certain button is pressed. But I disbelieve that such a function is really useful - let's assume some pans are full-left, some others are full-right, and you want to bring them to mid position. When you are moving a V-Pot which is full-left to the middle, the V-Pots which are full-right will still stay in this position. There is no real feedback from the host (even the LED ring position doesn't always help due to the reduced resolution), this means that you are not able to determine how much a single V-Pot has to be incremented until it reaches a certain position. Best Regards, Thorsten.

Hallo Thomas, in der MIOS Download Section gibt es ein 8x8 Button Matrix Beispiel, das natuerlich auch mit einer 3x4 Matrix funktioniert Gruss, Thorsten.

You didn't mention how you've changed the device ID and the MIDI channel, therefore I assume you made it wrong. Did you try the Program Change on all MIDI channels? Yes, it should work even if no SID module is connected Best Regards, Thorsten.

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.