TK.

Hi John, if you've got an acknowledge string after every code block, you know that the app has been loaded (see http://www.ucapps.de/mios_bootstrap.html) Best Regards, Thorsten.

Hi Jeremy, I wrote at the MBHP_USB page: The driver works fine under WinXP in the meantime, so it must be an issue with your USB host. Best Regards, Thorsten.

ueberpruefe ihn bitte mit einer aehnlichen Schaltung wie beim Standalone Test --- nur diesmal nicht auf dem Core Module, um moegliche Fehlerquellen auszuschliessen. Wichtig ist, dass die interne LED ueber einen 220 Ohm Widerstand angesteuert wird. Die Diode D1 kannst Du auf eigene Gefahr weglassen, sie soll die LED vor Verpolung schuetzen. Auf der Ausgangsseite ist die Versorgungsspannung, sowie der 1.2k Widerstand besonders wichtig. Nein, das ist voellig richtig. Interessant waere hoechstens die Spannung gegen Masse des PCs --- und diese Masse ist nicht unbedingt mit dem Core Modul verbunden. Der Optokoppler trennt uebrigens die MIDIbox galvanisch vom PC, es besteht also keine elektrische Verbindung. Das ist besonders wichtig, um evtl. Brummschleifen zu vermeiden. Letztlich ist beim Optokoppler auch nicht die Spannung, sondern der Strom wichtig. Er sollten mindestens 5 mA fliessen, wenn eine logische 0 getrieben wird. Bei einer logischen 1 fliesst kein Strom. Da Logisch 0 immer nur fuer einen extrem kurzen Zeitpunkt anliegt, kann man den Strom leider nicht mit einem normalen Messgeraet messen - deshalb ist dieser Messwert auch nirgendwo zu finden. Und ob nun 5V oder 4.751234V anliegen, ist ebenfalls egal, Hauptsache die Spannung (gegenueber PC Masse) liegt ueber dem TTL Pegel (>3V). Die Spannung gegen MIDIbox Masse ist unwichtig, und vor allem unterschiedlich, je nach verwendeten PC, Netzgeraet, usw. Gruss, Thorsten.

Dem Datasheet nach zu urteilen sollte es mit dem 6N137 auch funktionieren, ich bin mir jedoch nicht 100% sicher, ob sich evtl. die Widerstandswerte am Ausgang (R5 und R6) aendern. Der standalone Test sollte jedoch klappen: http://www.ucapps.de/howtodebug/mbhp_core_extract_opto_test.gif Ergebnisse? Gruss, Thorsten.

Puh, darauf waere ich nie gekommen! Gleich mal vormerken, fuer den Fall, dass jemand anderes auf das gleiche Problem stoesst: FAQMARKER Gruss, Thorsten.

Hi Tim, possibly yes, but there must be a reason why one of the shift registers went bad. Maybe a short circuit at the bottom side? the shift clock SC is a fast switching signal, therefore no DC. You cannot measure the voltage with a common multimeter. However, the mbsid_interconnection_test_b.zip could help to determine if all 74HC595 output pins can be controlled from the core module. Just follow the instructions in the main.asm file of this package. Another important hint: don't forget that with MIOS V1.7 and MIDIbox SID V1.6 the SC input of the SID module has to be connected to pin CORE:J11:MD of the core module. See also http://www.ucapps.de/mios_v1_7_hardware_mods.html Best Regards, Thorsten.

Hi, most SIDs are getting very hot, some not. Hey, thats analog gear :) I don't see problems so long the voltage at pin 28 is still 12V after power-on. If it's much lower (< 11V...), a soldering error could be the reason. But if you see >11V, then you've got one of the older chips which consume a lot of power. Best Regards, Thorsten.

It was very risky to do this with your very first (and such an expensive) panel - but the results are impressive! Well done :) Best Regards, Thorsten.

Really an interesting one! Best Regards, Thorsten.

Das ist aergerlich - am besten informierst Du mal Michael Klein ueber dieses Qualitaetsproblem, vielleicht sind ja auch noch weitere Core Platinen betroffen. Dies ist jedoch nicht der Grund, warum der PIC nichts empfaengt. Vielleicht schaust Du Dir auch nochmal alle Leiterbahnen, die zum Optokoppler fuehren, genauer an. Vergleiche die Platine auch nochmal mit dem Schaltplan, vielleicht hast Du ja auch einfach nur einen Widerstand vertauscht, oder was auch immer. Jedenfalls hilft es, die Schaltung genauer zu verstehen. Falls Du keinen weiteren Fehler findest, hilft es vielleicht wirklich nur noch, den 6N138 auszutauschen, und zu hoffen, dass es dann funktioniert. Gruss, Thorsten.

Hallo, ich kann heute noch nicht sagen, welche neuen Untermenues in den naechsten Jahren hinzukommen werden - aus diesem Grund habe ich die Bedienung so flexibel gestaltet, dass ich darauf keine Ruecksicht nehmen muss. Wenn Du nun eigene Taster fuer die Menues einplanst, dann wirklich nur auf eigene Gefahr. Mit Sicherheit wird es noch ein Menu fuer das AOUT Modul geben, spaeter auch mal fuer die uebergeordneten Patches fuer alle 4 SIDs (Performances oder wie man das dann nennen mag) Run/Stop: bei diesem Einschaltstrom werden die Kontakte des Schalters mit der Zeit korrodieren. Falls Du keine bessere Loesung findest (bspw. bei Conrad --- die sind zwar teuer, bieten dafuer jedoch einen schoenen bunten Katalog), hilft. evtl. ein Relais. Gruss, Thorsten.

Mal dumm nachgefragt: ganz oben schreibst Du, dass ein LTC modul am Core angeschlossen ist, und weiter unten, dass es eine Rueckkopplung zwischen Tx und Rx gibt- Kann es vielleicht sein, dass das LTC Modul einen Kurzschluss hat? Oder hast Du einen MAX232 in den Sockel gesteckt? In diesem Fall wuerde der MIDI In ebenfalls nicht funktionieren (siehe http://www.ucapps.de/mbhp_ltc.html evtl. macht es Sinn, den MIDI In mal ohne LTC auszuprobieren. Gruss, Thorsten.

Hallo, Diesen Effekt kann ich mir gerade nicht erklaeren. Die Wahrscheinlichkeit ist eigentlich sehr gering. Vielleicht ist die MIDI Buchse falsch angeschlossen? Oder D1 ist falsch gepolt? Oder die Versorgungsspannung am Optokoppler fehlt? Zwischen Pin 5 und 8: 5V Zwischen Pin 7 und 8: ebenfalls 5V im Ruhezustand Zwischen Pin 5 und 6: 5V im Ruhezustand M- ist ein Pin von J13 - Du kannst das auch ohne die Stecker verdrahten Gruss, Thorsten.

Hallo, nun koenntest Du erstmal die Versorgungsspannungen am 74HC165 messen - vielleicht hast Du ja eine Bruecke vergessen? Siehe http://www.ucapps.de/mbhp/mbhp_dinx4.pdf Zwischen Pin 8 und 16: 5V Zwischen Pin 15 und 16: 5V Wenn die Spannungen ok sind, kann es eigentlich nur noch an einem Verdrahtungsfehler liegen. Vielleicht ist der Register oder Shift Clock (RC/SC) nicht richtig angeschlossen, oder Du hast einen Kurzschluss auf diesen Leitungen. Ohne Oszi hilft hier nur eins: Leiterbahnen visuell ueberpruefen. Gruss, Thorsten.

Hi Pilo, if the devices are not controlled from an interrupt service routine, but from the main program, you can use the LCD data pins for the shift clock (SCLK) and the digital out (DOUT). For the digital input (DIN) you have to use a dedicated pin, but it can be shared by all devices if they support an high impedance mode if CS not active. So, only the chip select lines require dedicated outputs. If there aren't enough free, you could use one or more shift registers (74HC595), connected to the same SCLK and DOUT lines like the other chips. The register clock (RCLK) has to be driven seperately. In this way you will have an endless number of chip select outputs, but every serial register increases the latency by ca. 8 uS Alternatively you could add some glue logic for the chip select lines which decodes (e.g.) 8 outputs from a 3 bit input line (3-to-8 decoder) Best Regards, Thorsten.

Alright, the MIDIbox MM application is now available under http://www.ucapps.de/mios_download.html in the hope that I don't have to give support for this HUI variant. From the CHANGELOG.txt: MIDIbox MM V1.0 ~~~~~~~~~~~~~~~ Initial version which emulates the Motormix nearly completely: o eight motorfaders send and receive position data with 10 bit resolution o eigth touch sensors can be connected o eight virtual pots (rotary encoders) send relative events o one additional rotary encoder ("jog wheel") sends relative events o all 67 button functions are available o all 72 LED functions are available o two status digits (7 segment digits) o messages are displayed on a 2x40 LCD (only!) Additionally this application provides following functions: o a dirty hack makes it possible to add eight LEDrings to the V-Pots. However, the host application must send the absolute V-Pot position to the display - currently it only works with Sonar, Cubase doesn't get use of the so called "rotary pointer" (see Motormix specification) o a layer function which allows to map Motormix button functions and LEDs to a smaller number of buttons (additional "Shift Key") o 128 general purpose controllers can be send with the V-Pots in GPC mode o internal menu for motorfader calibration o optional "dont-send-if-touchsensor-not-pressed" function (disabled by default to avoid confusion, but heavily recommented if touchsensors available) Following function of the original Motormix is not implemented: o different graphical forms of the "rotary pointers" at the lower LCD line, since the graphics are not documented. Instead, always a vertical bar + the decimal value will be displayed Additional Notes: o Meters are not supported by the Motormix protocol o MTC digits are not supported by the Motormix protocol o LEDrings normaly not supported by the Motormix protocol. The LEDring hack works only with Sonar, and not with Cubase o the two 7 segment digits have to be connected directly to the shift registers --- no multiplexing required o only one 2x40 LCD is supported by the Motormix protocol o tested with the MIDIbox NG hardware, buttons and LEDs are assigned according to the existing design. The mapping can be changed in mm_io_tables.inc o *IMPORTANT* since I'm a Logic user (and therefore prefer the Logic Control emulation), this application has only be tested with following demo programs: -> Sonar 3 Producer Demo Edition -> Cubase SX Demo V1.02 No guarantee that it also works with other versions o Note for Cubase users: most buttons are not assigned to a function by default - you have to do this by hand in the device configuration! It seems that these functions don't have a LED feedback, but this could be different in newer Cubase versions. Please read also the "Remote Control Devices" Documentation which can be found at the Steinberg Website Best Regards, Thorsten.

Hallo Marc, ist doch klasse! Die Spannungen stimmen nun alle, Du hast den 7809 also nicht zerschossen, und kannst die Module beruhigt anschliessen. Auf den Wechselspannungswert, den Dein Messgeraet bei einer Gleichspannung anzeigt, kannst Du Dich nicht verlassen - Gleichspannung != Wechselspannung. Gruss, Thorsten.

Hi Ingebret, more detailed description about such a trivial thing aren't my strength. Hm - are you willing to improve the menu documentation once you've tried it with your own MIDIbox SID? Best Regards, Thorsten.

But display messages are only sent to one controller, motormix doesn't allow to address two or more displays via one MIDI cable. And MIDIbox MF is already a very generic controller. However, if somebody would write the documentation (basic description, block diagramms, photos) and would help newbies who are asking for the details in the forum, and if you would swear not to ask for special features for a thing which I would never use by myself, I'm possibly willing to modify the LC application for the Motormix protocol... But please understand that my own motiviation isn't that high - I've already a perfectly working controller, and I only own Logic and therefore cannot test the application with Cubase, Sonar, Pro Tools... so, once I provide a Motormix emulation, it would be very fine if somebody else could maintain it in the future! Otherwise this request would only lead to a lot of additional effort for myself which I don't really want. Best Regards, Thorsten.

Hallo Dirk, eigentlich muss Du nur die neuen *b Versionen herunterladen. Du kannst die Aenderung jedoch auch direkt vornehmen, und zwar in "sid_sr.inc", SID_SR_PIN_WR von 3 auf 5 aendern. Der SIDplayer laesst sich leider nicht in die MIDIbox SID Applikation integrieren, da er jedoch sowieso nur zusammen mit dem PC laeuft, sollte das kein grosses Problem darstellen. Schliesslich ist das Programm in wenigen Sekunden aufgeladen... Gruss, Thorsten.

Hi Ingebret, I'm not sure if you really want to change the menu display handler, or if you are just searching for a more detailed description how it works. Normaly I'm assuming that people trust me - I would never release such an unusable menu handler - I gave my best to make the whole UI so flexible and especially intuitive as possible so that I don't have to lost much words on it. You will notice this once you are playing with the SID ;-) You've guessed that: the right arrow is the cursor? This isn't correct. This arrow shows if the page can be scrolled to the right, or if you are at the right end (arrow into the other direction). The cursor just blinks with a 1:4 duty cycle (here: gray shated) so that it doesn't disturb your creative flow, but points out exactly which item has been selected. Sorry that my skills are too low for creating an animated .gif ;-) Best Regards, Thorsten.

Hallo, freut mich, dass Dir das Curve Feature gefaellt. Ich mache meine Sounds gar nicht mehr ohne (auch wenn die Bedienung vielleicht nicht so einsichtig ist, da man den Attack/Decay/Release ziemlich aufdrehen muss, bis man etwas merkt) Ich vermute Du musst auf Java 1.4.2 updaten, die neue JSynthLib Version verwendet einige der neuen Internas (bspw. das neue MIDI API) Gruss, Thorsten.

Hi Pilo, this reminds me that I wanted to write a detailed pin description and a list of possibilities (which pin can be controlled at which program level). However, can get some days... Yes, J6 and J7 are perfect so long no AIN multiplexers or motorfaders are connected to the core. Best Regards, Thorsten.

Hi, yes, there are no known issues with MIOS V1.7, so you can change the PCB. Doc's Problem was a missing Vdd wire at the DOUT board. Best Regards, Thorsten.

Hi Majo, I've currently no access to my MIDI gear, but I remember this imperfection. Sorry, I forgot to fix this in V1.6 - however, so far I know it can only happen if the CC target of velocity/aftertouch/modulation wheel is assigned to its own init value (velocity: CC#2). I will try to prevent this combination in the next release. All the other CC targets should work. You don't need to upload MIOS and the application again if you've assigned this critical CC by fault, you only have to prevent that any note will be sent to the SID until the CC target has been changed to != CC#2 Change of Link button: for some people thats a very important button if they are working with an inflexible sequencer like Cubase which doesn't allow to reconfigure the MIDI environment on-the-fly to avoid feedback loops during startup or if CC data is recorded. I've implemented this function on request by other people, and don't want to remove it again. Superpolyphony: is definitely planned - see also the StepB introduction page Superpatches: up to 16 combinations are prepared (saved at BankStick address 0x0080-0x00ff), but I haven't found the time to finish this yet (I'm working on other mighty applications like MIDIbox SEQ in parallel and prefer to play with the new possibilities by myself before implementing the next ones, therefore it can mostly take a long time before such ideas are available... - please understand this) Joining outputs: without the resistors you would have a short circuit. However, I recomment the use of 4 seperate audio inputs of a soundcard (so that effects can be routed easier in the sequencer software), or the use of an external mixer. Routing Velocity/Aftertouch/Modulation to more than one CC: unfortunately not possible anymore since the patch structure is frozen --- and especially heavily overloaded since I've already implemented so much features ;-) See also sid_sysex_table.inc - there is only one byte free anymore in the patch. I would have to cancel other features to realize this. Modulation matrix with different depths: two years ago I decided to implement the sound engine different from traditional synths. Common synthesizers have only one or two LFOs, one envelope generator, and a modulation matrix which allows to route these signals to different targets at the same time. But I found it better to have more LFOs and EGs which can only be switched on/off to the targets. Advantages: more expressive sounds, easier and less complicated handling (especially nice for live playing), cheap control surface (only 56 buttons and LEDs). Since the depth can be controlled at the LFO/EG directly, I didn't find a reason why I should add 56 additional depth parameters (which would consume 21% of the patch structure) for the targets. Of course, people think "Synth A and B can do this, why isn't it implemented in MIDIbox SID". My argument: because it's different and has it's own charisma and especially some features which cannot be found in other synths ;-) If you want to have another concept, you will have to reprogram the whole application at many placed --- and not only this --- you would also have to change the whole infrastructure (new control surface, new editor, overworked patches, etc...) Hint: if you want to realize really expressive sounds, then use the wavetable sequencer for (up to three) additional modulation sources. Imagine that the sequencer can modulate the modulation parameters of LFOs/EGs, but also his own input parameters.. Oh, I just have noticed that such a possibility is also not given in other synth architectures, therefore maybe unknown by most of you guys ;-) Best Regards, Thorsten.