TK.

Hi, each DAC requires a dedicated software driver, not all DACs provide the same features like the MAX525 (e.g. serial interface and chaining capabilities), not all DACs are so well documented. Nothing is impossible, but the programming effort has to be made by yourself... Best Regards, Thorsten.

Yes, this can be handled by software - it means that the program has to react on each transition, and not only on a 1->0 signal change. In other words: each time the USER_DIN_NotifyToggle function is called, you know that the switch has been moved, with a latching switch you don't need to filter out 0->1 transitions Best Regards, Thorsten.

Hi, testing shouldn't be so difficult: SC and RC are the same signals for each module. You could disconnect the SI pin of the DINX1 module, and connect the SI pin of the DINX4 instead to the core in order to check if there is a general problem with the DINX4 Best Regards, Thorsten.

Hi Steve, it's possible to map physical inputs to the pin numbers which are used by the software, it requires a small modification within the USER_AIN_NotifyChange function. I don't remember the pot order of the old MB64 hardware, maybe just only one bit needs to be toggled - could you please tell me the order of the first 8 pots? Best Regards, Thorsten.

doesn't really make fun (at least from the implementation side...) Best Regards, Thorsten.

"Super Poly"for MBSID is still in the request queue... (and not cancled ;-) Best Regards, Thorsten.

Hi, some older 6581 get very hot, some other not - thats normal and not really an indication if the SID is still working or not. It could be, that there is a problem with your PSU. What is the voltage at J1? Is it AC or DC? Maybe it makes sense to check the polarity of the 7812 - if it's mounted at the wrong way, the voltage won't be stabilized. Best Regards, Thorsten.

Hi Ludo, the two software implemented envelopes don't provide a delay... or do you mean depth? There is only one "curve intensity" parameter for each envelope, and this feature can be assigned to attack/decay/release (in any combination) Best Regards, Thorsten.

Hi Iceberg, the MB64E bank consists of 128 MIDI parameter values and 64 digital button states. It's possible to use up to 64 analog inputs, they are just mapped into the upper MIDI parameter range (65..128) So, for a single LFO, just select "unmuxed" mode and "1 pot" in main.asm, in this case the LFO will control the 65th MIDI parameter of a bank The number of buttons won't be reduced (analog sources are NOT connected to the DIN module!) Best Regards, Thorsten.

Hallo, die LEDs kannst Du ueberpruefen, indem Du die Kathode (kurzes Beinchen) an Masse schliesst, und die Anode (langes Beinchen) ueber einen Widerstand (z.B 220 Ohm oder 1 kOhm) an +5V. Falls Du bei den LEDs die Polung vertauscht hast, ist das nicht weiter schlimm - sie gehen davon nicht kaputt. Nur schliesse sie niemals ohne Widerstand an, denn bei hoeheren Stroemen verabschieden sie sich sofort (ohne Vorwarnung) Wenn die Buttons ebenfalls nicht funktionieren, deutet das auf ein Problem mit den DIN/DOUT Modulen hin. Schaue Dir vor allem die Leiterfuehrung der SCLK und RCLK Signale an. Diese Leiterbahnen sind so dicht nebeneinander gefuehrt, dass da mal schnell ein Loetklumpen zu einem Kurzschluss fuehren kann. Also: am besten die DIN/DOUT visuell genaustens untersuchen. Alternativ mit einem Piepser (Multimeter) auf Kurzschluss pruefen - hierbei vorher alle ICs (auch den PIC) aus den Sockeln nehmen Gruss, Thorsten.

no, the MIDIbox Link port just only saves one optocoupler and some resistors if two core modules are connected directly. It works at TTL level (0V/5V). The common MIDI port is a current loop (0/20 mA), therefore higher distances can be realized. From the software point of view, the behaviour of both hardware solutions is identical Best Regards, Thorsten.

Yes, these are the layer buttons, which have another purpose in the Song menu Best Regards, Thorsten.

because the FM percussions of the OPL3 are very flexible, see also this picture: http://www.ucapps.de/midibox_fm/mbfm_drum_panel_pre1.gif If Windows only provides a single patch with some unoptimized settings, then you won't have much fun. Best Regards, Thorsten.

Hi, the answer can now be found in the Wiki: http://www.avishowtech.com/midibox/wiki/index.php/MIDIboxSIDFAQ#QA25 Best Regards, Thorsten.

I just have released v2.3a, which contains an important bugfix for MIDI clock slave mode. I noticed a so called "race condition" which happens when the MIDI clock master sends a Start and Clock event at the same moment. Don't know if somebody ever noticed this (this imperfection exists since v2.0), but when this happened, the sequencer was one clock behind the master. -> http://www.ucapps.de/mios/midibox_seq_v2_3a.zip Best Regards, Thorsten.

Kaum zu glauben, dass die Chips immer noch bei Dir herumliegen - immerhin sind sie 70 Cent billiger als bei Reichelt, und dann auch noch mit vorprogrammierten Bootstrap Loader -> kaufen! :-) Gruss, Thorsten.

Hi Johnc, beside of the most comfortable solution to buy two new PICs, you could try to do some measurings first. Which instruments do you own - analog meter, digital meter, scope? Which voltages do you read at following pins: RD7 - pin #30, LCD enable line - it should toggle very fast ca. 2 seconds after startup for ca. 500 mS, until MIOS notices that no LCD is connected RD4 - pin #27, port J14 - should be 0V, if you read another value, then it is very likely that the bootstrap loader hasn't been started Tx - pin #25, the MIDI Out pin - should be 5V, if not, the BSL hasn't been started Best Regards, Thorsten.

Perhaps you can use this chip with the serial port driver of Yamaha http://www.yamaha.co.uk/xg/html/software/s_serial.htm, so that no self-written driver is required Best Regards, Thorsten.

A MIDI Thru is not really required if you chain the core modules. MIDI Out PC -> MIDI In Core 1 -> MIDI Out Core 1 -> MIDI In Core 2 -> MIDI Out Core 2 -> MIDI In PC Best Regards, Thorsten.

Hi Stefan, I will get 4 x CEM 3378 in the next days from a group order which was organized by p-cord. So, there will be some people who will use this chip with their MIDIbox SID/FM in the future :) Independent control: it's a planned feature to allow free-assignable analog outputs (to any MIDI or internal event, with offset and depth, setups stored in BankStick), but it's low-priority. I use currently only one external filter, which can be quickly connected to the outputs of MBSID/FM/SEQ, therefore I don't need such a flexible solution by myself... but it will come (at least, once the PIC18F4620 is fully working) Best Regards, Thorsten.

Hi, the LED behaviour can be configured on a very flexible way - maybe too flexible? ;-) Just read the midibox64.ini file, which is part of the mk_syx package: ################################################################################ # LED Map: assignes the LED shift registers to the Button Shift # registers or special values # Currently following values are supported: # 0 Default Setting (see Map below) # 1 Button Shift Register 1 (Button ID #1-#8) # 2 Button Shift Register 2 (Button ID #9-#16) # 3 Button Shift Register 3 (F1-F4 and Navigation Buttons: ID #17-#24) # 4 Button Shift Register 4 (Button ID #25-#32) # 5 Button Shift Register 5 (Button ID #33-#40) # 6 Button Shift Register 6 (Button ID #41-#48) # 7 Button Shift Register 7 (Button ID #49-#56) # 8 Button Shift Register 8 (Button ID #57-#64) # 9 reserved # 10 External Bank (1 of 8) # 11-15 reserved # 16 MIDI Status received for Button ID #1-#8 # 17 MIDI Status received for Button ID #9-#16 # 18 MIDI Status received for Button ID #17-#24 # 19 MIDI Status received for Button ID #25-#32 # 20 MIDI Status received for Button ID #33-#40 # 21 MIDI Status received for Button ID #41-#48 # 22 MIDI Status received for Button ID #49-#56 # 23 MIDI Status received for Button ID #57-#64 # 24-31 reserved ################################################################################ [LED_MAP] LED_SR1 = 1 # (Button ID #1-#8) LED_SR2 = 2 # (Button ID #9-#16) LED_SR3 = 3 # (F1-F4 and Navigation Buttons: ID #17-#24) LED_SR4 = 4 # (Button ID #57-#64) LED_SR5 = 5 # (Button ID #25-#32) LED_SR6 = 6 # (Button ID #33-#40) LED_SR7 = 7 # (Button ID #41-#48) LED_SR8 = 8 # (Button ID #49-#56) [/code] So, let's say you want to map the incoming events, which are assigned to button #1..#8, to the first DOUT shift register, then write: [code] LED_SR1 = 16 Best Regards, Thorsten.

(Sidenote: please add such knowledge to the Wiki, it could be very useful for newbies when we could just refer to the appr. page: http://www.avishowtech.com/midibox/wiki/index.php/Live%21) Best Regards, Thorsten.

Hi George, in general such mechanisms can be realized very easily, especially with a C based application. But I cannot give you a fast solution for especially your needs. My hope is, that somebody else feels motivated to program on such special variations, for myself it wouldn't make fun. To the problems with Greg's board: the pull-up resistor at the end of the 74HC165 (pin #10, see mbhp_dinx4.pdf) is not part of Greg's PCB, you have to add it in order to avoid the random events. It's also required to clamp all unconnected analog inputs to ground Best Regards, Thorsten.

Hi, first I would suggest to take a screwdriver, open your computer keyboard with it and check the contact of the CAPS-LOCK key, it seems that it is stucked ;-) Could you please check if the same problem exists in this release: http://www.ucapps.de/mios/midibox_lc_v2_0_alpha1.zip Best Regards, Thorsten.

Hi Rainer, the input voltage to the 7805 is too high, the recommented voltage range is between 7V and 10V... But you are right, it's strange that the 7805 gets hot with such a low power consumption, could it be that there is a short circuit at one of your boards? What is the total current draw? Like for the LCD this could be a side effect which is caused by the overheaded 7805. no I would suggest to try the circuit with a second power supply which delivers a lower voltage for Core:J1. If this works better, you know where to "debug" (the cheapest solution is the use of a 7809 between the 12V supply and the 7805 input) Another potential problem that I saw at your pictures is, that you propably forgot to mount R2 of the core module? Best Regards, Thorsten.