TK.

ack. - these are the required modules. Best Regards, Thorsten.

You're welcome! :D Good that I've also created a test firmware... because without MIDI input the SID will play no sound ;-) Best Regards, Thorsten.

...without documentation about the different possibilities yet, and therefore no official release. Downloads: http://www.ucapps.de/midibox16e/midibox16e_v1004.hex.zip http://www.ucapps.de/midibox_mf/midibox_mf_v1000.hex.zip http://www.ucapps.de/midibox/mk_syx.zip http://serge.ucapps.de The mk_syx archive contains some example configurations for LC and Houston emulation. As you can see, I haven't re-engineered all buttons of the Houston controller yet (it's only a question of effort...) but if somebody would like to complete the list: step forward! :) I've planned to write HOWTOs for both emulation types, but it could take a while... Best Regards, Thorsten.

You've programming skills? Fine - herewith you are nominated as official owner of the Mackie Control/Houston PlugIns ;D Best Regards, Thorsten.

This time from Arto/Finland. He will provide some sound patches in the future. :)

Hi Swede, the demo version of Cubase SX V1.02 doesn't include the Mackie PlugIn, therefore I cannot confirm if this configuration works ok. But note: a Mackie emulation with 2x40 LCD isn't really useable. Maybe I could provide a mod which skips some characters (overall 2x16 characters have to be removed between the 8 channel strips...) but the result will be far from perfection. :-/ If you are interested in Mackie mode, you should better wait for the 5" LCD solution: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1043023674 -> for the emulation stuff graphical LCDs are most flexible. -> Houston emulation is only usefull as low-cost solution Best Regards, Thorsten.

Well, as a Chip Design Engineer I've to work 40-50 hours a week... on the other hand I've very flexible working hours - I can come when I want and can go when I want, I just only have to do my job. Normally my daily work is interesting and makes a lot of fun (since it has nothing to do with PIC controllers or horrible MIDI protocols... ;-)), I don't feel stressed at the weekends so that I've still the time to realize my dreams ::) Concerning the Houston protocol: unfortunately the Steinberg guys didn't implement the multiclient setup capability, so it isn't possible to combine several Houston boxes with the same flexibility like known from the Mackie Control. But it is possible to add other MIDI controllers to the same MIDI line as "Generic Remotes" - this allows you to assign additional pots, faders or encoders to any parameter (disadvantage: without the same flexibility and especially without display support from the host application...). In my eyes the best solution: the Houston emulation only with 8 V-pots and some buttons to control the EQs, fx-VSTs, VSTis and the transport bar. & one, two or more MIDIbox MF without display to control the volumes (or other functions --- bank-switching is supported by Cubase!) Best Regards, Thorsten.

Hallo, durch die LED-Kraenze fliesst insgesamt nur sehr wenig Strom, da sie per Zeit-Multiplex angesteuert werden - soll heissen: alle 800 uS wird ein anderer Kranz erleuchtet. Das spart Strom und Verdrahtungsaufwand. :) Die Leiterbahnbreite kannst Du auf 16 MIL (0.4 mm) reduzieren. Ja, diese Belts kosten wahrscheinlich viel zuviel ;-) Gruss, Thorsten.

Hallo Jens, die Platine ist erst seit heute verfuegbar - sie heisst "Mplus_V1" Gruss, Thorsten.

Great! :) Best Regards, Thorsten.

Hi Christoffer, unfortunately the PIC18F CPU isn't code compatible to the PIC16F, so this will not work. It needs some effort to port the SID firmware, but I will do it after the first MIOS release. Best Regards, Thorsten.

My ALPS faders only have such an extra track --- for the touch detection. :) Best Regards, Thorsten.

In addition to the LC emulation, MB16e, MBMF, MB64 and the upcoming MBLC will support the Houston protocol with the next release :) For Cubase users this protocol offers some advantages - the integration into the Cubase SX environment is better, and a 2x40 LCD can be used instead of a graphical LCD, this saves some money.... with a graphical LCD, the font will be nicer than in Mackie Control mode. However, with a BankStick or via SysEx data dump exchange you will be able to switch between both modes - just choose your personal favourite ;-) Thanks to Frank - he gave me the right hints - currently I'm testing the emulation with the demo version of Cubase SX :) Best Regards, Thorsten.

Hi Dan, sure, this is possible :) Best Regards, Thorsten.

Die Clock-Spannung faellt mit der Zeit auf < 4V - das ist normal. Nein, den BankStick kann man erstmal nicht ohne LCD ueberpruefen, es sei denn, Du baust mal schnell eine MIDIbox SID nach, die gibt naemlich einen Sound aus, wenn man den BankStick ein/aussteckt ;-) Aber warte einfach auf das MIOS, dort werden wie gesagt alle allgemeinen Funktionen verfuegbar sein, so dass Du Dich ueber solche Internas wirklich nicht kuemmern brauchst. :) WIe ich bereits schrieb: mit diesem Betriebsystem mache ich mir selbst "das Leben" einfacher, deshalb moechte ich eigentlich nichts mehr herausgeben, was in wenigen Tagen obsolet sein wird. Ja, Du kannst den Programmierport auch einfach nach aussen legen. Gruss, Thorsten.

Hi Chriss, most synthesizers (hardware & software) only support a resolution of 7 bit... also a physical pitch wheel normaly doesn't send values with a greater resolution, although the appr. MIDI event type allows 14 bit (I've tested this on several keyboards). However, it's planned to support 10 bit resolution with MIDIbox NG, but you have to wire the AIN modules and the pots/faders very careful with shielded cables in order to avoid jittering values - and you need a MIDI device which supports this resolution. Best Regards, Thorsten.

perfect :) Best Regards, Thorsten.

Hi Christopher, I'm also missing a quick-change function in the JSynth environment. It's a general feature which has to be integrated into the core lib. If there will be no button available in the future, I will possibly add it by myself... Yes, you can re-use your PIC16F for the slave cores - I will do this as well. :) Best Regards, Thorsten.

Hi Nenad, no, currently it isn't really clear enough why your circuit is failing. Do you mean that after you've changed the ICs the MIDIbox is running for some minutes, and that thereafter they are damaged so that they have to be replaced again? In this case I would say: stop exchanging the ICs! Remove all ICs from the sockets (LTC and Core module) and measure the Vss/Vcc voltages on all sockets to ensure that the voltage level never exceeds 5V. It seems that something is wrong with your LTC module - so the main focus should be to find the root cause there. Print out the schematic and compare it with your board, check every track for short circuits, the polarity of the caps & diodes (LEDs) - this should help. Best Regards, Thorsten.

Where did you order the crystal and the caps - do you know the order numbers? Best Regards, Thorsten.

Hi Nenad, I'm not sure - how did you select the to-COM option without a LCD. Did you use a patched .hex file? If not - if you've used the default firmware - your box is running with the common MIDI baudrate and this would be the reason for the random MIDI events. Best Regards, Thorsten.

Hi Ian, the source code mod is easier than resoldering all the parts (ok: for myself ;-)) In irq.inc, you have to exchange the LED routines: ;; ========================================================================== ;; LED subroutines for timer handler ;; ========================================================================== LED_Set0 movlw 0x01 ; Digit 0 on, Digit 1 off, Digit 2 off xorlw 0x07 movwf PORTC movf LED_DIGIT0, W goto LED_SetDigit LED_Set1 movlw 0x02 ; Digit 0 off, Digit 1 on, Digit 2 off xorlw 0x07 movwf PORTC movf LED_DIGIT1, W goto LED_SetDigit LED_Set2 movlw 0x04 ; Digit 0 off, Digit 1 off, Digit 2 on xorlw 0x07 movwf PORTC movf LED_DIGIT2, W ; goto LED_SetDigit LED_SetDigit ;; First: Check Flash Flag IFCLR LED_FLASH_FLAG, 0, goto LED_SetDigitCont ; change char to "led off", depending on counter IFSET LED_FLASH_CTR, 5, movlw 0x10 LED_SetDigitCont call LED_GetCode movwf LED_TMP ;; scrambling: ;; LED a: PORTA[0] ;; LED b: PORTA[1] ;; LED c: PORTA[2] ;; LED d: PORTA[3] ;; LED e: PORTA[5] ;; LED f: PORTE[0] ;; LED g: PORTE[1] ;; LED dot: PORTE[2] andlw 0x0f ; PORTA[3..0] IFSET LED_TMP, 4, iorlw 0x20 ; PORTA[5] xorlw 0x2f movwf PORTA swapf LED_TMP, F rrf LED_TMP, W andlw 0x07 xorlw 0x07 movwf PORTE ; PORTE[2..0] return I just have exchanged the polarity with the xorlw instructions Best Regards, Thorsten.

Hi Greg, the "MIDIbox link" option has not been integrated into the MB64 firmware yet (this time Serge was faster than me ;-)). Best Regards, Thorsten.

No, there is no easy way to check the crystal type - only the specs given by the manufacturer can help. Ok, I think that you should test a more simple firmware in order to eliminate all possible errors.... http://www.ucapps.de/howtodebug/test_tx.hex.zip sends a volume controller (B0 07 7F) every second, and http://www.ucapps.de/howtodebug/test_rxtx.hex.zip just forwards the incoming data from MIDI-In to MIDI-Out This will help you to determine if the chip is clocked with the correct frequency. Btw.: did you program the PIC with IC-Prog? Did you ensure that the "HS Oscillator" is selected? Best Regards, Thorsten.

Hi Matt, does this help? Best Regards, Thorsten.