TK.

So far I remember, AC has developed a C based version to his Speakjet project. If the function is generic enough, it could also be built into the "analog toolbox" (which is written in C as well! :)) Best Regards, Thorsten.

Great! :) Best Regards, Thorsten.

This will be of course no real MIDI merger, but my assumtion was, that this is already clear to you. I cannot give you a schematic for such a multiplexing circuit, but Wikipedia gives you a basic description: http://en.wikipedia.org/wiki/Multiplexer If this information is not enough, I would suggest to build a seperate PIC based MIDI merger, it's propably easier for you, and it's more powerful Best Regards, Thorsten.

Weil es ein Flag in den Filter Registern ist, doch eigentlich hast Du Recht, es sollte woanders versteckt werden ;) Es gab mal eine MBSID Version, in der das Flag nicht funktionierte. Verwendest Du die v1.7303b Release? Warum OSC3 ausschalten: macht Sinn, wenn OSC3 als Sync Master fuer OSC1 dient (OSC1: Sync Flag gesetzt) Gruss, Thorsten.

Wilba hat sie ebenfalls noch vor wenigen Wochen von Albs bekommen Twin-X: they are still available at albs.de, Wilba purchased some a few weeks ago. Best Regards, Thorsten.

Hallo Karl, ich moechte nicht weiter auf eine erweiterung der MIDIO128 Applikation eingehen, weil es unter Assembler wirklich etwas aufwaendiger wird - selbst ich koennte Dir hier vorher keine vorgaben oder Programmierbeispiele geben, ohne das meiste selbst runterzuprogrammieren. Aber generell sind Assembler Programme auch schlecht dafuer geeignet, von Aussenstehenden erweitert zu werden. Ich kenne nur sehr wenige Leute, die meine Applikationen einigermassen ueberblicken. Das ist u.A auch ein Dokumentationsproblem. C ist hier schon besser geeignet, und so etwas wie MIDIO128 liesse sich eigentlich auch sehr einfach und ohne grossen Performance Verlust damit programmieren. Auf meiner Webpage gibt es ein paar C Beispiele, die den Einstieg vereinfachen. Zusaetzlich gibt es auch noch die ain64_din128_dout128_v2_0 Applikation, die Du fuer die ersten Experimente verwenden koenntest (alle ungenutzten analogen Eingaenge - in Deinem Fall wahrscheinlich der komplette Port J5 - auf Masse klemmen, ansonsten werden zufaellige MIDI Events gesendet!) Gruss, Thorsten.

Note that MBSID V2 has a much more advanced arpeggiator :) Best Regards, Thorsten.

Check especially that the two 1k pull-ups are connected for the data and clock line (see core schematic) Best Regards, Thorsten.

Sounds like the encoder pins are swapped, or that the wrong encoder type is selected. There are some infos about different encoders in the Wiki Don't know what could cause the "note delete" issue. Maybe the start button triggers a second function? Have you checked the buttons with MIDIO128? Each button should send a single MIDI event. Best Regards, Thorsten.

I think the best solution would be a backup option in MIOS Studio - it would work with all MIDIboxes Best Regards, Thorsten.

Did you solve this in the meantime? There is a simple test which ensures that the MIDIO128 is uploaded correctly: just disconnect the DINX4 module, and shortly connect J9:SI (the serial input) to ground. The core should send 128 MIDI messages Best Regards, Thorsten.

Hi Andrea, you can change the channel assignments with the mk_midio128_syx script (see README of this package for details) Best Regards, Thorsten.

I added it to the wishlist again (which is located at the MBSEQ main page), so that it won't be forgotten Best Regards, Thorsten.

No, this isn't possible yet, but could be easily added by enhancing the clock divider function. I will add this to the wishlist Best Regards, Thorsten.

Hi Tim, it's a nice idea, but I think that controlling an AOUT_LC module from the core works much faster than accessing a IIC slave. The only advantage I see is, that it sidesteps the IO pin limitation of the core module. Best Regards, Thorsten.

The MIDImerger project is a very timing sensitive project where the second MIDI In is realised as a software UART. It is not possible to use the same approach if the CPU is loaded with other tasks, so it is especially not possible to use the same approach with MIOS. Solution 1 is not possible, as MIDI lines are current loops Solution 3: just use two optocouplers, and join the signals with a digital multiplexer. Maybe transmission gates (4066) could also be used. Best Regards, Thorsten.

Eher eine Vermutung, aber ich bin mir fast sicher. Laut Datenblatt darf VDD-V0 bis zu 15V betragen. Du koenntest mal eine 9V Batterie zwischen Masse und V0 klemmen. Der Pluspol muss an Masse angeschlossen werden (-> ansonsten keine negative Spannung) Zwischen Minuspol und V0 wuerde ich zusaetzlich nochmal einen 100 Ohm Widerstand haengen, nur fuer den Fall, dass es einen Kurzschluss geben sollte (Strombegrenzung) Gruss, Thorsten.

At the time I wrote this document, uploading an application via .syx was very common, and MIOS Studio, especially a direct .hex upload, was not available... When reading documents, please always have a look to the file date Best Regards, Thorsten.

Perfect, this demonstrates that the "fail save" protection is working! :) From the ChangeLog: o this version *REQUIRES* a PIC18F4620, it won't run on a PIC18F452 ! o there is now a check during the initialisation for the PIC derivative. Execution from any other PIC than PIC18F4620 is gracefully prevented. You will see a message on screen, and a MIDI event "EE <devid[2:0]> <devid2[9:3]> is sent to notify about the wrong PIC [/code] Best Regards, Thorsten.

If you are planning to create a frontpanel for your MIDIbox SID V2 ("Step A", "B" or "C" stage), please consider that the purpose of the Link/CC and Edit button has been changed. This mainly affects the labling the LINK button will get the purpose of a SHIFT button. In addition, it displays a special configuration page, which for example allows you to switch between left and right SID channel the CC button is used for "Page Up" (increments OSC/LFO/ENV/MOD/TRG/KNB) the Edit button is used for "Page Down" (decrements OSC/LFO/ENV/MOD/TRG/KNB) SHIFT+CC and SHIFT+EDIT still switch the CC/Edit function like before - this means: the two LED labels are still valid! in the OSC section, the "Arpeggiator" label should be renamed to "Phase" The Page Up/Down buttons are just a new feature which save you from scrolling to the left end of a menu page in order to select a different oscillator/LFO/ENV/... etc A MBSID with the minimal "Step A" control surface still allows full access to all parameters, but adding a Shift/Page Up/Down button is strongly recommented for faster usage Best Regards, Thorsten.

Danke! :) Ich denke, dass Du so etwas wie die MIDIO128 suchst, mit dieser eigentlich recht einfach gestrickten Applikation lassen sich bis zu 128 Taster und 128 LEDs betreiben. Hardwaremaessig benoetigst Du ein Core Modul, sowie die entspr. Anzahl an DINX4/DOUTX4 Module (maximal 4, jedes Modul bietet 32 Eingaenge, bzw. 32 Ausgaenge) Die LEDs koennen dann von der Host Applikation angesteuert werden (jede LED reagiert per default auf das gleiche MIDI Event, das auch von dem entspr. Taster gesendet wird. Auf Wunsch kann man auch verschiedene MIDI Events hernehmen) Taster: sollte funktionieren, ich wuerde jedoch empfehlen, vor der Grossbestellung erstmal drei oder vier verschiedene Exemplare zu bestellen, und dann das auszuwaehlen, welches Dir (bspw. vom "Klickgefuehl" her) am besten gefaellt. Gruss, Thorsten.

Kann es sein, dass das Display eine negative Spannung an V0 benoetigt? Im Kapitel 5.3 des Datasheets faellt V0 verdaechtig von 0V nach unten Gruss, Thorsten.

Thats ok, according to the datasheets the PIC can be supplied with up to 5.5V, and for the OPL3/YAC I think it's similar Best Regards, Thorsten.

Hi, the Rx pin has a pull-up resistor to +5V, accordingly you should read +5V so long no MIDI data is received (you can doublecheck this by temporary removing the optocoupler) So, it's very likely that there is a problem with the power tracks at the right side of the core PCB With your multimeter you can follow these tracks to locate a crack, a bad connection or something similar - once the voltage turns from 5V to 0V, you know, where it is Best Regards, Thorsten.

The upload was totally successfully, because there are 32 positive acknowledges (32k), and one additional error response, which propably comes from a recorded "dummy upload request", which will be sent by the core after a reset. You could remove this last upload request from the SysEx dump Best Regards, Thorsten.