TK.

I like the constant time slides :) The drums are groovy, but mixing needs improvements. However, for a live session it sounds like you had a lot of fun! :) Best Regards, Thorsten.

Hi Alkex, great one! :) (Btw.: in my implementation, I used vertical bars, because this matches better with the lables of a common MIDIbox SID panel) Best Regards, Thorsten.

not really, you only need to consider that each linked core adds a latency of about 320..400 uS... However, compared to the latency of your PC MIDI interface, this is ultra low ;-) Best Regards, Thorsten.

Hi Ted, this doesn't depend on the MIDIbox, but on the host application! Under Logic, I have to select the Name/Value mode in a special preferences panel. I can also select it with a special key combination (which I forgot in the meantime - I hate shortcuts ;-)) Best Regards, Thorsten.

I love this style of music, too :) Btw.: I'm using the same cases for my AOUT module and the Moog filter: Best Regards, Thorsten.

Hi Matthias, what happens, if you install the ezmon.sys and ezusb.sys driver again? (both are located under ez-usb/driver/) Best Regards, Thorsten.

Hi, it will lead to unforeseen problems: all newer PICs contain the EUSART, and this peripheral has a bug which is very anoying for MIDI transfers (zero-frames are inserted sporatically). See also this posting: http://forum.microchip.com/tm.aspx?m=85120 I will propably switch to the PIC18F4620 this summer - if Microchip doesn't provide a fixed revision until then, I will use a second (smaller) PIC, dedicated for MIDI transfers, and connected to the PIC18F via IIC. However, on the other hand: if you want to create a sophisticated (graphical?) user interface, you should consider the use of external memory (flash or battery buffered SRAM). Connecting 1 MB or more to the PIC shouldn't be a big problem, most GPIO pins can be used for other external peripherals (like the LCDs) in parallel. Just only the chip select line requires a dedicated pin. And if speed does matter (but I think this is not the case for your project) it's better to use a chip family which provides an external memory interface (like 8051 or Z80 derivatives, or maybe a 16bit controller?) Best Regards, Thorsten.

Hallo Andreas, nein, diesen BankStick-Sound gibt es bei der MBFM nicht... aber apropos "so wie bei der MBSID": ich habe mal auf die schnelle einen Interconnection Test, sowie eine Testton-Applikation zusammengebastelt. Vielleicht helfen sie bereits weiter (zum Testen der Signale zwischen OPL3 und YAC muesste ich erstmal meine Box aufschrauben) -> http://www.ucapps.de/mios/mbfm_interconnection_test_v1.zip (Anleitung in main.asm lesen) -> http://www.ucapps.de/mios/mbfm_testtone_v1.zip (1kHz Ton ueber alle 4 Kanaele) Gruss, Thorsten.

Hallo Andreas, wenn ich mich jetzt nicht total irre, koennen die Chips auf dem OPL3 Board durch eine Ueberkreuzung der Daten/Adress/Control-Leitungen nicht zerstoert werden, denn es handelt sich um reine Eingangssignale. Es wurden also lediglich "die falschen Daten in die falschen Register" geschrieben. Doch wenn das 2x40 LCD einen Knacks bekommen hat, dann koennte noch irgendetwas anderes vorgefallen sein, was den YMF262 in Mitleidenschaft gezogen hat. Doch das laesst sich per Ferndiagnose schlecht sagen. :-/ Ich werde mir mal einen Test ueberlegen, mit dem man die YMF262 Pins 19, 20, 21 und 22 auf einen definierten Stand bringen kann - wenn sich das irgendwie bewerkstelligen laesst, koennte man mit einer gewissen Sicherheit sagen, dass das Businterface noch funktioniert Bis dahin koenntest Du mal ausprobieren, ob vielleicht ein Audio Signal an Pin 8 und 14 von IC3 anliegt (Note anspielen!) Gruss, Thorsten.

no, it's not a bridge, but something like a "manual reset button" (cheap solution: without button ;-)) ok, so it's not a reset problem This could have several root causes. Assumed that you are using the suggested crystal from Reichelt (if not: which one are you using instead), it could be that one or more ground/3.3V lines of the chip have no contact with the PCB. Therefore the general hint: add a little bit more solder to all pins. If all these hints don't help, then just send me the module so that I can check it with my own equipment (not to my postal address, but to a packstation - I will mail you this address if required) - for me it would be interesting to learn, which errors can be made, this will help next users who are facing the same issue. I built 4 MBHP_USB modules so far, and tested them with several computers (also at friends), so that I at least know, that the circuit and software are ok, and that the reason for the failure on your board must be a bad connection or something like that... Best Regards, Thorsten.

Nobody has written an editor yet... Best Regards, Thorsten.

Hallo Andreas, die (meist) digitalen Spannungen zu vergleichen, ist nahezu aussichtslos, denn sie werden so schnell geschaltet, dass je nach verwendetem Messgeraet und eingeschalteten Patch andere Werte gemessen werden. Ohne Oszi geht da leider nix. Die Effekte, die Du an Deinem LCD beobachtest, finde ich eigenartig. Egal, wie man die Eingaenge ansteuert, der Kontrast sollte ueber das gesamte Display gleich sein, und fehlende Pixel sollte es auch nicht geben (es empfaengt ja lediglich ASCII-Codes). Irgendetwas ist da bei der Verdrahtung schiefgelaufen, und ich hoffe, dass das LCD noch intakt ist (denn nach Beschreibung scheint das nicht mehr der Fall zu sein). Es koennte sogar sein, dass der OPL3 sich gerade wegen des defekten (?) LCDs nicht mehr ansteuern laesst. Wenn bspw. eine Datenleitung permanent getrieben wird, dann wuerde der YMF262 fehlerhafte Kommandos erhalten. Oder andersherum: am OPL3 Board wurde eine Leitung vertauscht, die gegen die Daten des LCDs treibt - auch in diesem Fall kann man nicht vorhersagen, wie sich das LCD verhaelt, und der OPL wuerde sich nicht ansteuern lassen. Waere es fuer Dich so ohne weiteres moeglich, die Verbindungen zum LCD zu entfernen, so dass nur noch das OPL3 Modul an Port CORE:J15 haengt? Ausserdem waere es interessant zu wissen, wie sich das LCD verhaelt, wenn das OPL3 Modul nicht angeschlossen ist. Gruss, Thorsten.

Yes, it works with two 128x64 displays Best Regards, Thorsten.

Do you know, why it didn't work before? Best Regards, Thorsten.

Great that some problems get solved even if nobody answers ;-) Best Regards, Thorsten.

Hi, the volume register of the SID has only a resolution of 4bit, it doesn't really make sense to control it with a pot. It's better to control it on the analog way Best Regards, Thorsten.

Hi Alex, metering the modulation outputs is such a cool idea, that I couldn't resist to built this into the v1.7303 by myself! :-) See http://www.midibox.org/forum/index.php?topic=6098.msg37721#msg37721 In cs_menu_matrix.inc you will find the offsets of LFOs and ENVs Best Regards, Thorsten.

And now really the last feature, based on an idea from Alkex: [tt] o the LEDs of the modulation matrix are now also used for metering the output values of LFO1-6 and ENV1-2 This new mode is enabled by default, and can be toggled to the old mode (which shows the modulation matrix assignments) by pressing two mod target buttons at the same time (e.g. O1 and O2 pitch). The assignments are also displayed automatically, so long one of the mod target buttons is hold. [/tt] -> http://www.ucapps.de/mios/midibox_sid_v1_7_303beta13.zip Best Regards, Thorsten.

You can use any voltage source, not only pots, but also analog sensors (e.g. light or heat sensors)... and pots of course. If pots are used, just connect the outer pins to J5:Vd (+5V) and J5:Vs (Ground), and the middle pins to J5:A0...J5:A5 Best Regards, Thorsten.

Hi Jerry, I recomment to program this in C, at the http://www.ucapps.de/mios_c.html page you will find some examples, how to process the digital inputs and outputs. If "90 29" should control 8 digital outputs at once, then you only need to add: if( evnt0 == 0x90 && evnt1 == 0x29 ) for(i=0; i<8; ++i) MIOS_DOUT_PinSet(i, evnt2 == 0x00 ? 0 : 1); [/code] ...to the MPROC_NotifyReceivedEvnt hook Best Regards, Thorsten.

Not before v1.7303 has been released (and this version needs a lot of new documentation as well!) Best Regards, Thorsten.

thanks for the input, I've updated the links! A tutorial can be found here http://www.midibox.org/forum/index.php?topic=1504.0 But to make it clear: MIDIbox LC is not intented as a newbie project, it definitely requires a learning curve! If you've never completed a "normal" MIDIbox (like MB64 or MB64E) before, the given informations won't be enough. Best Regards, Thorsten.

Hi Olgimat, problem is, that some assembler source files have UNIX style linefeeds. I haven't found the time to upload an update yet (after more than one year you are the second one who asks for this, therefore the low priority ;-)), but there is an easy solution: under Linux type "unix2dos *.inc", or under Windows open the affected .inc files with the wordpad and save them again Best Regards, Thorsten.

yes... and the assign function should provide min and max values no, it means: controlling two SIDs with a single core in order to realize stereo effects from a single patch Best Regards, Thorsten.

The firmware is final, just only the documentation is missing. However, some infos can be found in this thread, and a drum sound programming example here: http://www.ucapps.de/howto_sid_wavetables_1.html Best Regards, Thorsten.