TK.

After I saw a nice live performance from Weltklang music yesterday (see http://www.weltklang-music.de/html/body_langenacht2004.html and http://www.weltklang-music.de/html/body_langenacht.html), who are using the Korg Kaosspad to trigger and modulate sounds, I defenitely also want to experiment with touchpads. Only question: where to buy the pads... Could you try to find some manufacturers or distributors who offer such pads in low quantities? Best Regards, Thorsten.

thats the point - where to buy keys? Well, I guess that you won't be able to buy a single keyboard w/o the electronic parts, and especially you won't save money by doing so. My suggestion: try to find an old keyboard at EBay and add a MIDIbox to the Out port. MIOS provides an integrated MIDI merger, so that notes of the keyboard as well as controllers (or any other MIDI events) from the MIDIbox are part of the MIDI Out data of the MIDIbox. Behind the MIDIbox you can add a MBHP_USB module. Here two keyboard mods - take it as inspiration: Best Regards, Thorsten. FAQMARKER

Hallo, das ist eine reine Konfigurationsgeschichte die eigentlich keine zusaetzliche Hardware benoetigt - vorrausgesetzt, einer der PCs hat einen MIDI Thru Port. Falls nicht, muesstest Du dem Core Modul noch ein LTC Modul spendieren, so dass Du einen zweiten MIDI Out hast, der jedoch die gleichen Daten wie der erste Port sendet. Die beiden Cubase Hosts musst Du dann so konfigurieren, dass die Funktionen auf unterschiedlichen MIDI-Noten liegen. Mindestens 128 Noten stehen Dir zur verfuegung, falls sich auch noch der MIDI Kanal selektieren laesst, sind es sogar 16*128 Noten (und 16*128 Controller) Gruss, Thorsten.

Thanks! :) No, I'm not in a band, the mp3 page is just a database of some one-night creations of the last years. Best Regards, Thorsten.

I'm not sure about the currents, perhaps they are ok (assumed that your LCD has a backlight), but they could be false if your PSU has a max current of 200..300 mA. However, I think it makes sense to follow all the instructions from the MIDI troubleshooting page: http://www.ucapps.de/howto_debug_midi.html There are a lot of tips how to get a sign of life from the core module Best Regards, Thorsten.

thanks for your understanding - you won't regret the choice of rotary encoders, its the best solution for synths/controllers/sequencers which provide multiple control layers and banking The CV solution is also described at the "MIDIbox SEQ Options" page. There is also a new layout for the AOUT module (8 channels, 2 gates): but I haven't found the time to write more about the details yet Best Regards, Thorsten.

Hi uclaros, but these are PIC*C* types and no "F" types, means: microcontrollers with OTP (One Time Programmable) memory. In other words: you can program the memory once and then never again - makes development difficult, no? ;-) Best Regards, Thorsten.

Hallo Andreas, ich weiss nicht, ob Matthias hier mitliest. Er hat den Page Modus eingebaut und koennte sicherlich am besten weiterhelfen. Evtl. per EMail kontaktieren (die Adresse steht im COPYRIGHT.txt file der MIDIbox64 Release) Gruss, Thorsten.

Hallo Dirk, Du kannst beruhigt mit der Frontplatte loslegen, meine eigene aendert sich mit Sicherheit nicht mehr. D.h., neue Funktionen werden so integriert, dass man sie mit den vorhandenen Bedienelementen erreicht. Die bestehende Matrix wird bspw. um eine alternative Ansicht fuer die AOUT Routings erweitert - Du musst also keine zusaetzlichen LEDs hinzufuegen Displaygroesse: bis zu 2x40 ist bereits moeglich, von mir empfohlen: 2x20, groessere Displays lohnen sich nicht wirklich. Mehrere Displays oder Grafikdisplays werden von meiner Seite nicht supported, und wuerden uebrigens auch das Realzeitverhalten der Software Engine beeintraechtigen, so dass man eigentlich schon ein zweites Core Modul nur fuer das Frontpanel hernehmen muesste CV In: unter MIOS Programming habe ich beschrieben, wie man die analogen Eingaenge mit der MB SID nutzen kann. Es gibt sogar ein Codebeispiel zu diesem Thema: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1066834196 Gruss, Thorsten.

continued via PM

The introduction for this chip exists since more than one year, but there are no devices available yet. Please keep also in mind that it would mean a lot of effort for myself to create a new USB project (which I wouldn't really need) - maybe 3 months or more - and a lot of extra support effort to help you with debugging the new hardware - just to give you an impression. So, I think that somebody else has to implement an alternative USB solution. Best Regards, Thorsten.

Hi Dan, DriftZ wrote a driver for 3 digits some time ago (see http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios;action=display;num=1064077146;start=3#3), you could ask him for the code... Best Regards, Thorsten.

Evtl ist da noch mehr falsch - wie geschrieben: noch nie getestet... ich weiss noch nichtmal, ob diese Option fertig programmiert ist. In Zeile 158 steht bspw. "bz SEQ_LED_UpdateIRQ_GPLED_Not0", aber ich vermute mal, dass dort eigentlich "bz SEQ_LED_UpdateIRQ_GPLED_0" stehen sollte, damit in der oberen Reihe auch der der GP Status angezeigt wird. Weitere Fehler darfst Du selbst finden ;-) Gruss, Thorsten.

I guess you don't have programming skills, so it would require some programming effort from my side to realize this. :-/ yes... yes, but I think that you haven't read http://www.ucapps.de/midibox_seq_options.html yet... pots are the worst selection you can make for such a flexible sequencer. Best Regards, Thorsten.

some relaxing SID and Reaktor sounds - the bridge to Part III http://www.mp3.de/frequencies Lyrics: Time Flow Time Flow ;-) Best Regards, Thorsten.

Mal eine grundsaetzliche Frage: hast Du die ICs "richtigrum" eingesetzt (siehe Schaltplan)? Ist es nun der 6N138 oder der PIC, der den Kurzschluss verursacht? Was passiert, wenn Du die Jumper an J3 entfernst? Gruss, Thorsten.

Mal eine grundsaetzliche Frage: hast Du die ICs "richtigrum" eingesetzt (siehe Schaltplan)? Ist es nun der 6N138 oder der PIC, der den Kurzschluss verursacht? Was passiert, wenn Du die Jumper an J3 entfernst? Gruss, Thorsten.

Hallo, ich bin mir nicht mehr so sicher, ob es sich evtl. doch um einen Softwarefehler handelt. Ich konnte diese Option ja noch nie ausprobieren (mangels entsprechender Hardware), und habe sie deshalb nur auf Verdacht eingebaut - in der Hoffnung, dass sie auf Anhieb funktioniert. Es koennte sein, dass die Polaritaet an den Kontrolleitungen fuer die Kathoden vertauscht ist. Oeffne mal seq_leds.inc, Zeile 239: dort steht "IFSET IRQ_TMP1, 0, movlw 0x01". Ersetze das IFSET durch ein IFCLR. Das gleiche dann in Zeile 245, 251, 257 Ergebnis? Gruss, Thorsten.

Hi Ian, I found some warnings in the .err file like: Warning[203] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 571 : Found opcode in column 1. (incf) Warning[206] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 574 : Found call to macro in column 1. (IFCLR) Warning[206] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 577 : Found call to macro in column 1. (IFCLR) Warning[203] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 579 : Found opcode in column 1. (movlw) Warning[203] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 580 : Found opcode in column 1. (call) Warning[203] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 582 : Found opcode in column 1. (comf) Warning[203] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 584 : Found opcode in column 1. (movlw) Warning[203] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 585 : Found opcode in column 1. (call) Warning[203] C:\PROG STUFF\MIDIBOX64E_V2_1\MAIN.ASM 589 : Found opcode in column 1. (return) it seems that the assembler fails since there are no space characters between the instructions and the first column. Therefore the assembler cannot determine if the "word" at the beginning is really an instruction (like incf) or a label (like USER_SR_Service_Prepare) Tip: just add TAB characters before every instruction, and the assembler should pass. If not, check the .err file again Best Regards, Thorsten.

Hi Matteo, seems to be ok... Next question: which MIOS version are you using? My recommentation: MIOS V1.6 and SID V1.6alpha3 A sidenote to give you an impression about the possibile hardware errors: some weeks ago a user had similar problems with his MIDIbox SID modules. After a lot of forum postings he finally sent me the modules since he wasn't able to identify the root cause by himself. After some quick checks I found out that it wasn't only one problem, therefore it was nearly impossible to support him via forum under these circumstances. Here a list: bad soldering joint at the bottom of the core module (J10:MD pin) slack joint (loose connection) between the SID and the core module - sometimes it worked, mostly not... a tiny solder blob caused a short circuit near of IC3 of the SID module one of the SID was defective So, what should I say... ensure that the modules are properly connected - use ribbon cable, they are easier to solder. carefully check the bottom of the PCBs for short circuits try different SIDs if available connect a LCD if available, it saves a lot of time during debugging always use the latest MBSID and MIOS release (remember that MIOS has to be uploaded with the first level bootstrap loader...) to avoid compatibility problems try alternative applications (e.g. the sidplayer) Best Regards, Thorsten.

D2k made two new and really improved MIDIbox LC :) He wrote:

And here are the results of the first round: Some guys already noted, that the survey script has been changed last week. This was because of security reasons - the old script didn't refuse double votes made by the same person. SmashTV has installed a new script which works much better and fixed the counters based on informations from the logfile (thanks for your help!). Don't be confused about the "Total Votes: 0" in the survey view, this is the output of the old script! It's too much effort to fix this just for this competition... so, here the instructions for the next round: log into the portal click on Survey->MIDIbox Logo Competition vote for your favourite logo click on "view results" for the statistic Best Regards, Thorsten.

Hallo, wie verhalten sich die LEDs, wenn "DEFAULT_TRACK_LEDS_ENABLED" auf 0 gesetzt ist? Gruss, Thorsten.

Hi Ian, what's the content of the .err file? (If you've assembled the main.asm, the name of the error file is "main.err") Best Regards, Thorsten.

Hi Matteo, I'm not sure about the caps, but you should hear some sound regardless of the value. There is a program in the MIOS download section which helps you to debug the SID module. Search for "mbsid_interconnection_test.zip" and follow the instructions in the main.asm header: ; A CORE->SID Module Interconnection Test ; ; This application allows you to check the interconnections to the SID module ; with a multimeter. You can control the SID pins by sending a Modulation Wheel ; event to your MIDIbox SID - just connect a keyboard or use ; MIDI-Ox (View->Control Panel) ; ; By default all unselected pins are 0V, except for the CS# pin which is 5V ; ; The Pins are mapped to following Modulation Wheel Values: ; ; # 0: Pin A0 = 5V ; # 1: Pin A1 = 5V ; # 2: Pin A2 = 5V ; # 3: Pin A3 = 5V ; # 4: Pin A4 = 5V ; # 5: Pin RES# = 5V ; # 6: Pin D0 = 5V ; # 7: Pin D1 = 5V ; # 8: Pin D2 = 5V ; # 9: Pin D3 = 5V ; #10: Pin D4 = 5V ; #11: Pin D5 = 5V ; #12: Pin D6 = 5V ; #13: Pin D7 = 5V ; #14: Pin CS# = 0V ; ; The pin names are also visible on LCD (if connected) Results? Best Regards, Thorsten.