TK.

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.

Jo, der Rest sollte passen. PIC Brennen: kein Problem, schreibe einfach eine EMail an tk@midibox.org, um meine Adresse zu erhalten. Gruss, Thorsten.

Hallo Lemonhorse, das .jar File ist aus der Release verschwunden, weil es bereits in der v0.17 redundant war. Du kannst den Editor aus der Kommandozeile mit "java JSynthLib" starten. Oder einfach "run" eintippen - in run.bat steht naemlich genau diese Zeile drinnen. "run.bat" kann man auch aus dem Explorer anklicken Zu 2): ja, wuerde ich grundsaetzlich empfehlen. Ansonsten wuerde bspw. die Split Funktion bei den Slaves nicht funktionieren. Das Updaten ist sehr viel einfacher geworden. Vorrausgesetzt, jeder Slave hat bereits eine eindeutige MIOS ID (0x01, 0x02, 0x03), konfiguriert sich der Rest nun automatisch - mehr infos unter http://www.ucapps.de/midibox_sid_csB.html Gruss, Thorsten.

Tja, gerade deshalb ist es so schwer, ueber das Forum Debugging Hilfe zu leisten - oder wuerdest Du diesen Fehler vermuten, wenn Du das urspruengliche Posting nochmal durchliest? ;-) Sehr gut! Das kann irgendwie nicht sein. Im Ruhezustand sollten 5V anstehen, bei MIDI Daten sollte der Wert nach unten gehen (die genaue Spannung kann niemand sagen, da es sich um ein digitales Signal handelt das sehr schnell zwischen 0V und 5V wackelt) Entweder misst Du den Wert nicht gegen die Masse der Soundkarte, oder der MIDI Adapter hat eine Macke. Wo wir auch schon wieder bei meiner heissgeliebten MIDI Troubleshooting Guide waeren: http://www.ucapps.de/howto_debug_midi.html Mach' mal ab "At the PC site" weiter --- stelle mit Hilfe einer Loopback sicher, dass der MIDI Adapter funktioniert. Schliesse eine LED an, usw. Und schreibe dann bitte auf, welcher Test geklappt hat, und welcher nicht! Fuer Dich mag das vielleicht etwas Schreibarbeit sein, aber verglichen zu dem, was andere schreiben muessen, um die Informationen aus Dir herauszuquetschen, ist das gar nichts ;-) Gruss, Thorsten.

Hi, yes, the whole protocol is documented fine, so an emulation seems to be feasible. You could take the LC emulation as basis and modify the MIDI processor functions which decode the incoming MIDI events. The same has to be done for the output functions. Estimated effort: 3 months to learn assembler, 1 month to understand the LC application, 1 month to implement and test the changes. Best Regards, Thorsten.

Link to additional answer: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=gallery;action=display;num=1079994325;start=15#15 your crosspostings are producing a lot of effort! :-( Best Regards, Thorsten.

See also http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1086450431 Addendum: MIDIbox LC is an exception, because the host application (Logic/Cubase/etc...) requires to connect each core to a seperate MIDI IO! Note that this limitation is only valid for the Logic Control or Mackie Control emulation --- with a common MIDIbox you can chain the modules ("MIDIbox Link") Best Regards, Thorsten.

Each core has it's own MIDI IO port. You can connect them in a chain, or seperately to your PC. Most people prefer the chain method (-> see http://www.ucapps.de/midibox_link.html) so that only one MIDI IO is allocated for all boxes. Latency is absolutely no issue! (-> see http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=mios_toy;action=display;num=1077232194). So, you are the first who don't want to chain the modules - thats ok ;-) Best Regards, Thorsten.

Hallo, stimmt nicht ganz, denn die analogen eingaenge zaehlen extra, MIOS verwaltet also 128 digitale Eingaenge (ich habe das in obiger Liste verbessert) und zusaetzlich auch noch 64 analoge Eingaenge - um ganz genau zu sein ;-) Du benoetigst nur ein AINX4 Modul (jedes AINX4 bietet 32 analoge Eingaenge). nein, die benoetigst Du fuer simplen controller ohne Banking/Paging usw. nicht. Gruss, Thorsten.

Hallo, MIDI-Ox ist schonmal falsch konfiguriert, beachte auch diesen Kringel: Diese Option ist bei Dir wahrscheinlich aktiviert, deshalb steht der SBLive Output Port in der Port Map --- diesen Port entfernen, ansonsten hast Du eine klassische Rueckkoppel-Schleife. Ansonsten wuerde ich empfehlen, die Troubleshooting Guide Schritt fuer Schritt durchzuarbeiten. Sollte der Upload danach immer noch nicht funktionieren, koenntest Du zumindest beschreiben, welche Tests geklappt haben, und welche nicht: http://www.ucapps.de/howto_debug_midi.html Gruss, Thorsten.

After a HD crash my windows installation isn't running yet, so maybe somebody else could help? However, reassembling the code isn't that difficult, and you have to do this anyhow with every new release. So, it makes sense to get some practice ;-) Best Regards, Thorsten.

Hi, are these questions or conclusions? ;-) Of course, if you haven't programmed the bootloader into the slaves, it's time to do it now. And please don't forget to set the ID of the slaves to 1, 2 and 3! J10 has 4 connections if the ground is already connected from the power supply unit to the SID module --- compare the wiring with http://www.ucapps.de/mbhp/mbhp_4xsid_c64_psu_optimized.pdf Best Regards, Thorsten.

Do you have a 2x16 LCD? In this case it's required to set CS_MENU_DISPLAYED_ITEMS to 4 (-> see main.asm or the appr. setup_*.asm file you've uploaded) Thereafter follow the instructions under http://www.ucapps.de/howto_tools_mpasm.html Best Regards, Thorsten.

Hi Twin-X, there is a new description which describes the required steps: http://www.ucapps.de/midibox_sid_csB.html (search for "Preparation of PIC18F cores") Once this has been done, you can change the MIDIchannel of each SID (seperately of course...) in the CFG menu Best Regards, Thorsten.

Hallo Ferdi, am besten spielst Du mal die MIDIO128 applikation auf, die ist defaultmaessig so konfiguriert, dass jeder einzelne DIN pin eine Note triggert. Auf diese Weise kannst Du schonmal feststellen, ob die Verbindungen physikalisch vorhanden sind, und es sich nicht um ein Konfigurationsproblem in der SID Applikation handelt (bei einem 2x16 Display sollte CS_MENU_DISPLAYED_ITEMS bspw. auf den Wert 4 eingestellt werden). Falls keine Noten getriggert werden, miss die Spannung direkt an den Eingaengen - sie sollte 0V betragen wenn der Button gedrueckt ist, und 5V wenn der Button nicht gedrueckt ist. Falls das nicht der Fall ist, sind die Pull Ups wahrscheinlich nicht angeschlossen (Bruecken vergessen?) Gruss, Thorsten.

Hi Tim, just click on the menu button, move the rotary encoder so that the page scrolls to the SAV menu and click on the button below of this menu entry. Then you can select the target patch number - press "Do!" to save the patch Best Regards, Thorsten.

jep MIOS kann bis zu 128 digitale Eingaenge durchscannen. MIOS kann bis zu 64 Endlosregler verwalten MB64E kann aus historischen Gruenden (Datenformat, Kompatibilitaet, siehe oben) nur bis zu 64 Taster verwalten, aber mit ein bisschen Code waere auch noch mehr drin - die zusaetzlichen Taster liessen sich jedoch nicht mehr bequem mit dem Editor oder am Display konfigurieren an welchen Pins die Encoder, und an welchen die Taster angeschlossen sind, legt man im Setup File (setup_*.asm) fest. Wegen der Limitierung auf 128 Pins ist es bspw. nicht moeglich, gleichzeitig 64 Encoder und 64 Buttons anzuschliessen - das sollte aus obiger Liste hervorgehen. Gruss, Thorsten.

Hi, it doesn't really matter. Maybe it's even better to solder it between SID 2 and 3... Best Regards, Thorsten.

Hi Meeshka, I've no oversight about the current software projects for MIDI, so this is something which has to be driven by the community. Best Regards, Thorsten.