TK.

Hi Pearl, yesterday I've integrated this function into the LC application in form of a "layer button". Release: maybe tomorrow (I want to add other features...) Best Regards, Thorsten. P.S.: locator buttons are not required, such a feature is already provided by LC :)

Doh! You are right! Ok, meters will be provided very soon! :) Best Regards, Thorsten.

Hallo Johannes, diese Bauteile haben keine Polaritaet. Beim Quarz sollte man lediglich aufpassen, dass die Beinchen nicht das Metallgehaeuse (oder gar die Leiterbahnen des PCBs) beruehren. Aufpassen muss man bei: ICs, Transistoren, Spannungswandlern, Dioden, LEDs, ElKos, 1MHz Oszillator des SID Modules, Steckern... Gruss, Thorsten.

Joysticks von einer RC Fernbedienung: dass ich darauf noch nicht gekommen bin (ok, meine RC Zeit liegt schon ein paar Jaehrchen zurueck ;-)) - klar, diese Joysticks sind ideal, weil sie meistens mit 10k Potis ausgestattet sind Gruss, Thorsten.

Der Optokoppler sollte eigentlich nicht daran schuld sein. Der Rx ist ja lediglich ein Eingangspin, der nicht treibt, und deshalb auch keinen Kurzschluss verursachen kann. Ok, bevor wir nun weitere Ursachenforschung treiben, probiere einfach den anderen PIC aus. Gruss, Thorsten.

Problem is that I don't know how to visualize it better. Let's take a look under my MB64 case: ;-) Best Regards, Thorsten.

Hi Kent, alright, a preliminary schematic can now be found here: http://www.ucapps.de/tmp/midi_router.pdf It's a simple master-slave design. Every slave acts as a IO device and provides a Tx buffer of 64 bytes and Rx buffer of 128 bytes. The slave firmware will be so simple, that it never has to be updated again, therefore a programming socket is not required. The brain of the system is a PIC18F based core which accesses the PIC slaves over a parallel bus. A handshake protocol (Request/Acknowledge scheme) ensures that only one PIC drives the bus at one time. Up to 8 slaves can be connected. The 100k terminators at the end of the bus ensure proper signals for fast accesses (like SCSI). The master core will cyclicaly request every slave for new data. Incoming data streams can be filtered, merged, converted and routed to any MIDI Out(s) Best Regards, Thorsten.

Without BankStick only one patch is available, which is stored in the internal 256 bytes EEPROM. Best Regards, Thorsten.

It doesn't matter, the master fader just have to send the MIDI event "E8 <low-byte> <high-byte>" However, if you want to have a 10-bit resolution, a PIC18F core is required Best Regards, Thorsten.

I haven't found the switch in Logic which enables the VU meter option of LC, can somebody help me? Best Regards, Thorsten.

three core modules, some DINx and DOUTx modules and software skills (or somebody who helps you to customize this controller...) Best Regards, Thorsten.

Hi Kieran, well, a simple 1-track/32-step sequencer has already been integrated (the Wavetable sequencer). However, a more complex sequencer should be possible, but it depends on the requirements. A 4-track TB303 style sequencer is very simple and could be added w/o problems. However, there is no place to store more than one pattern, so it would only be usefull for live sessions. A more complex analog style sequencer like MB64seq requires an additional core. Best Regards, Thorsten.

Hallo Stefan, probierst Du mal den RxTx-Test aus? http://www.ucapps.de/howtodebug/test_rxtx.hex.zip Er leitet die eingehenden MIDI events direkt an den Ausgang weiter - damit waeren zumindest die softwareseitigen Fehlerquellen (z.b MIDI Merger disabled und Device Nummer != 00) ausgeschlossen. Gruss, Thorsten.

Hallo Jens, folgende Dateien helfen weiter: http://www.ucapps.de/midibox/midibox_plus_16.pdf (Schaltplan) http://www.ucapps.de/midibox/mplus_pcb_v1.gif (PCB Quickview) http://www.ucapps.de/midibox/mplus_pcb_v1.brd (Eagle Datei, kann mit der Freeware Version eingeladen und ausgedruckt werden) Desweiteren helfen vielleicht auch die Fotos auf der MIDIbox Plus Seite weiter. Gruss, Thorsten.

This requires some kind of "radio button" function (means: one LED active at one time). With MIDIbox64 this can be implemented with meta events, with MIOS you just have to insert the code into an existing application (I can provide an example if necessary) Best Regards, Thorsten.

Fine - so it must be a minor problem. :) Power is ok, contrast also. Let's double check the CS lines, they must be connected to: CS1 -> Pin RD0 CS2 -> Pin RD3 CS3 -> Pin RC4 CS4 -> Pin RC5

My offer is still valid: if you send me a display for one week, I will setup a dedicated driver for MIOS Best Regards, Thorsten.

Just to ensure (due to linguistical differences): does it mean that black pixels are visible, or that the screen is blank. ;-) Best Regards, Thorsten.

Hi Scott, fine fine - one more MIDIbox SID which is up and running! :) Beside of the possible problem which has been mentioned by Ian, another reason could be that you forget to select the filter mode and to route the VCO outputs to the filter. This has to be done with the MIDIbox SID editor, or via CC: CC # | Hex | Description | Range | Reset =====+=====+==============================================+=============+====== 44 | 2Ch | Filter Channels | | 0 | | Bit 0: Filter for Voice 1 on/off | | | | Bit 1: Filter for Voice 2 on/off | | | | Bit 2: Filter for Voice 3 on/off | | | | Bit 3: Filter for Audio In on/off | | 45 | 2Dh | Filter Mode | | 0 | | Bit 0: LowPass on/off | | | | Bit 1: BandPass on/off | | | | Bit 2: HighPass on/off | | | | Bit 3: Voice 3 off | | 46 | 2Eh | Filter CutOff frequency | 0-127: val | 127 47 | 2Fh | Filter Resonance | 0-127: val | 0 -----+-----+----------------------------------------------+-------------+------ Example: CC 44 -> 7 CC 45 -> 1 Best Regards, Thorsten.

Hi Dan, ok: MIOS is running, it has been configured for a graphical LCD and you see a black screen (means black pixels or just nothing?). So the error must be a missing or bad connection. Best Regards, Thorsten.

Now this issue has been discussed here: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1048075587 Best Regards, Thorsten.

remember that there are still some undocumented features... ;-) Best Regards, Thorsten.

Hi Dan, Not really. The din_touchsensors circuit is just a button replacement. It delivers an active signal to the MIDIbox when your fingers touch the TS contact (therefore it could also be used for other purposes - how about a panel full of touch sensors which trigger different notes or controller message when you touch it? ;-). But the touch sensor function which is meant here is a function which suspends the faders - it has already been implemented in MB MF and MIOS of course. I guess that I have to give a better oversight: the suspend function disables the motor and brings the MF driver into a state which ignores all incoming repositioning commands for the appr. fader until the suspend function has been disabled again the suspend can be triggered by touch sensors or by dedicated buttons for each fader or by one button for all faders host programs like Logic, Cubase and Nuendo provide an additional functionallity for the automation, called "touch" mode, which suppress repositioning events for a certain time (mostly about 200 ms) when it receives a fader event the MF driver stops the motor automatically when it regognizes that the fader is moved manually. But this detection requires some force (for about 100 ms) which isn't good for the lifetime of the motorfader additionally the host application can receive touchsensor events which also disable outgoing repositioning commands. Sometimes these events are used for additional functions, e.g. Logic provides the possibility to select a channel when you touch a fader. Conclusion: if faders with integrated touch track are available, the use of the touch sensor unit allows to send additional commands to the host application for a proper and lifetime saving automation If the fader doesn't come with a touch track, you can either hope that the automatic suspend saves your fader from damage (however, it isn't sooo dangerous, the fader should should work for some years in this way...), or you could use one button to suspend all faders, or 8 buttons to suspend the faders seperately when necessary. Best Regards, Thorsten.

Hi Amando, Great! I'm looking forward to a new contribution for the MIDIbox extensions page! :) Best Regards, Thorsten.

If the vinyl interface outputs the so called "quadrature code", it wouldn't be a problem for MIOS to handle the apparatus like a rotary encoder. Otherwise a selfwritten decoding routine has to be attached to USER_SR_Service_Finish Best Regards, Thorsten.