TK.

You could use the LEDs of your LTC module to ensure that the MIDI signals are going into the slave: just connect on of the inputs of the LTC module directly with the Rx input of the slave PIC (pin #26) Best Regards, Thorsten.

Hi, RST is the reset line, it depends on the display if it has to be connected or not. In fact there are 5 possibilities: *general answer mode on* no reset pin: thats the common case floating low-active reset pin (reset with logic-0): add a pull-up resistor (10k to +5V) so that the display is not in reset state after power-on floating high-active reset pin (reset with logic-1): add a pull-down resistor (10k to ground) so that the display is not in reset state after power-on low-active reset with internal pull-up: let it open high-active reset with internal pull-down: let it open *general answer mode off* How to find out the type of reset pin? Normaly it can be read in the datasheet, and if not, try an external 10k pull-up first (in most cases the reset line is a low-active input) - if it still doesn't work, try a pull-down. CS3 and CS4 are output signals of the core, so: no problem. You could connect a second KS0108 type display in parallel to the first one, with the only difference that the chip select lines are connected to CS3/4 in order to double the resolution (nice for MIDIbox LC) Best Regards, Thorsten. FAQMARKER

in this application: no Best Regards, Thorsten.

Hi, see http://www.ucapps.de/mios.html - the specs are still up to date. No, it isn't possible to connect more than 64 pots to a single core module Best Regards, Thorsten.

Hi Thomas, since all cores are working standalone, the application has been uploaded correctly - a slave will run regardless of the device ID, this ID is only required to address the slave when changing parameters with the control surface or JSynthLib, so no need to reprogram the chips. Maybe I should repeat my question: are the optocouplers disconnected? The 6N138 should only be stuffed on the master module, the MIDI Ins of the slave modules have to be driven by the master. I've the hope that you could write a short report about your experiences (pitfalls etc.) with the project for the MIDIbox portal in order to help other DIY people who are maybe also confused about all the informations on my website (which are sometimes not very detailed, sometimes incomplete, sometimes outdated :-/) Best Regards, Thorsten.

Hi, every SID core module drives a 1 MHz clock, so I think it's better to use them seperately. In fact a SID slave is a totally independent synth module which could also be used standalone. A master is nothing else than a slave + the control surface with the capability to send parameters to up to 4 slaves... You could connect the analog pins (J5) to ground, but in fact this doesn't make a big difference so long as the AIN driver of MIOS is disabled. Don't forget the pull-up resistors! Don't connect the remaining free pins (e.g. the LCD port) to ground or +5V! Best Regards, Thorsten.

Hi, you could connect J11:MI of the master to J11:MI of the slaves so that all incoming MIDI messages are directly sent to the slaves. This is just for testing. If it still doesn't work, you have to check each slave seperately like it has been done for the master... Best Regards, Thorsten.

Hi, 1) of course 2) this has nothing to do with the controller capabilities, all info screens are sent by the host application 3) this is controlled by the host application You should search for a Logic or Mackie Control user manual on the web which describes the handling Best Regards, Thorsten.

Hi, it's important that the LCD type is set to #1 in the MIOS ID header (if this hasn't been done by SmashTV, you have to use the change_id application). D/I replaces the R/S signal Best Regards, Thorsten.

Check the wiring to the slaves, ensure that the slave boards are not stuffed with an optocoupler, press the link button. If this doesn't help, please describe exactly how your hardware looks like Best Regards, Thorsten.

I will publish a perfect PCB sooner or later, please don't hurry... I got two MAX525 as free samples from Maxim, and therefore never took care for the price. I'm planning to create an alternative solution for a cheaper DAC sooner or later - ideally with a pin compatible chip, so that one PCB layout can be used for both. But please understand that this takes its time - especially since I'm very pleased with the AOUT module I've already created by myself. Since two weeks I've an Sample&Hold board up & running which supports up to 64 analog outputs (8 S&H chips are used to multiplex the 8 outputs of the MBHP_AOUT module - makes 64 outs) --- this multiplexer extension requires some extra attention in the layout to ensure best signal/noise ratio - it's also important that the MBHP_AOUT and MBHP_AOUT_MUX modules can easily be connected together - such things just cost extra development time. If you are asking for a release date, here my answer: this summer or maybe earlier ;-) However, People with electronic knowledge should already be able to write a driver for an alternative chip - the source is located in aout.inc - if anybody is interested: step forward! Best Regards, Thorsten. FAQMARKER

hast Du den Loopback Test ausprobiert? Wenn der Input Monitor das das gleiche wie der MIDI Out Monitor anzeigt, weisst Du, dass MIDI-Ox richtig konfiguriert ist. Gruss, Thorsten.

I knew it was a bug... ;-) Best Regards, Thorsten.

Hi, to your last question: you can start and stop the sequencer within the main menu by pressing the select button. But to the other questions: I strongly recomment to build the hardware before drilling the panel! In my opinion a step sequencer with just 6 buttons doesn't really make fun, sooner or later you want to have them all so that your creativity flow won't be interrupted when you have to search for the right key on your keyboard. You will understand this once you've played around with the mighty functions! The additional buttons are not so cost insentive. If you are using miniature buttons (the same I used for my MIDIbox SID), you will have to pay about 0.10 EUR for each, plus 0.40 EUR for every DIN register + socket, plus 0.03 EUR for each pull-up resistor, makes about 8 EUR for 44 buttons + resistors + 6 shift registers. Do you really want to omit a powerful user interface just to save 8 EUR? Best Regards, Thorsten.

Have you ever tried to swap the PICs in order to ensure that the firmware has been uploaded correctly? Such tricks can save a lot of time ;-) Best Regards, Thorsten.

1) check the schematic, it explains which resistors are required for 1V/octave - you are also able to use it for 0-5V or -4/4V, therefore such values are not specified 2) of course, MBSEQ has already been tested on a PolyKobol system :) 3) which pins are free on your PIC? These are the pins which can be used for such additional control signals (it has to be driven from midi_evnt.inc) Best Regards, Thorsten.

Yes, in principle thats correct. There is a tutorial application in the MIOS download section which explains BankStick transfers step-by-step, search for "bs_xfer_v1_4.zip" Best Regards, Thorsten.

Is the Link enabled? The Link button has to be pressed, otherwise the MIDI events won't be forwarded to the slaves. (see also http://www.ucapps.de/midibox_sid_csB.html, search for "link") Best Regards, Thorsten.

Hi, are you able to record the MIDI messages into a MIDI files, so that I would be able to replay it on my PC w/o using Cubase? Best Regards, Thorsten.

From my experience it's a wiring error in 90% of all cases. You could upload the MIDIO128 application in order to check if every button sends a single MIDI event. If not, you know that there is a short somewhere, and you should also be able to locate the affected digital inputs (can be derived from the sent MIDI events) Best Regards, Thorsten.

It's more comfortable to modify the SID device SID in main.asm, to build and new .hex file and to convert it to a new .syx file (don't forget to specify the MIOS device ID with "hex2syx.pl main.hex -device_id 0x<id>" in order to address the right core) -- so long as the MIOS device ID is equal to the SID device ID, this shouldn't be too confusing Otherwise you would have to change the SID device ID via SysEx, and this would require that only one core module is connected to the MIDI Out of your PC. Best Regards, Thorsten. P.S.: seems that it makes sense to implement some kind of automatic device ID configuration into the SID application...

Siehe lc_io_table.inc Eigentlich wird die Konfiguration bereits im Header von main.asm beschrieben, man muss sie nur Schritt fuer Schritt durchgehen, um zu verstehen, was dahintersteckt Gruss, Thorsten.

Thanks - got it and after some try and error it's working now :) the ultimate answer to the 1A command is 1B 42 ;-) You can download the patch under http://www.ucapps.de/tmp/mblc_sonar_mod.zip, just copy lc_mproc.inc into the midibox_lc directory and compile the code again. I will put this patch into the next release Best Regards, Thorsten. P.S.: Emagic published the Logic Control MIDI Implementation one year ago, but in the meantime it has been removed from the website...

Ok, dann hast Du wahrscheinlich genau das gleiche Problem wie Stephen (http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1078305083) Er hat auch schon einen Patch fuer Cubase geschrieben, der scheint jedoch noch nicht 100% stabil zu laufen Gruss, Thorsten.

Cool! I just have downloaded the demo - Do I have to enable the access to Mackie Control somewhere, or does Sonar try to locate it automatically during the startup phase? Best Regards, Thorsten.