TK.

What is the name of your MIDI Interface? Best Regards, Thorsten.

yes, therefore it has been removed from my website. Please remove it from your webserver as well Best Regards, Thorsten.

You can download project_mbseq.hex of http://www.ucapps.de/mios/midibox_lc_v2_0_alpha1.zip into the MIDIbox SEQ, this will give you a full featured Mackie Control Emulation. Best Regards, Thorsten.

I already own some ENC28J60 samples, and I'm planning to play with them in some weeks. A Swissonic MIDI-USB interface (available at Thomann) will cost you 20 EUR, and I'm sure that the usage is less troublesome than doing experiments with Ethernet. Other people probably will need an ethernet switch if they want to connect something else to the ethernet line. It's the same like adding an USB hub... accordingly I don't see an ethernet interface as a solution for saving one USB port. Could you please search for a driver, which is *already* available for MacOS, Windows and Linux? I saw a lot of solutions (ideally I would use RTP MIDI, but it seems that a driver is only available for MacOSX), but nothing which could really universal enough for a MIDIbox project. In distance to MIDI over IP, OSC is pretty easy to realize - it can use UDP packages to transfer informations. Such packages can be sent with a TCP/IP stack like uIP (http://www.sics.se/~adam/uip/index.php/Main_Page) Best Regards, Thorsten.

Schade, ich habe heimlich auf einen Praezedenzfall fuer Leitungsreflexionen gehofft ;-) Gruss, Thorsten.

Hallo, das wird so nicht stabil funktionieren, der Retry-Mechanismus, wie er auf der MBHP_IIC_MIDI Seite gezeigt wird (IIC_MIDI_Send() Funktion) ist sehr wichtig, ansonsten koennen Daten verloren gehen, falls die CPU schneller sendet als das IIC Modul ueber die MIDI Leitung uebertragen kann. IIC laeuft ja mit 400 kbit, und MIDI mit nur 31.25 kbit -> Flaschenhals-Problem) Um eine Note zu uebertragen, muesstest der Master Start, 0x10, 0x09, 0x93, 0x3c, 0x7f, Stop senden 0x10: Slave ID 0x09: Type "Note" 0x93: oberes Nibble: nochmals Note, unteres Nibble: MIDI-Kanal 4 0x3c: Notenwert (hier: C-4) 0x7f: Velocity Der Slave antwortet meistens mit einem ACK. Doch wenn er mal keine Daten mehr annehmen kann (Datenstau), antwortet er stattdessen mit NAK. Der Master muss den Transfer dann mit einem Stop/Start solange neu aufsetzen, bis der Slave wieder ACK sendet. Es gibt eine Demo-Applikation (midi_router Projekt), doch ich befuerchte, dass sie die Sache nicht verstaendlicher macht, zumal hier die Uebertragungsroutine in Assembler geschrieben ist. Gruss, Thorsten.

Tach auch, Du koenntest einen Schrumpfschlauch ueber das andere Widerstands-Beinchen ziehen, und es dann an J2:Vd anschliessen. Statt Schlauch gibt es auch andere Moeglichkeiten zum isolieren, zur Not hilft Tesa. Loete einfach die vier Datenleitungen D0..D3 am LCD ab, und isoliere die offenen Enden, bspw. mit Tesa Gruss, Thorsten.

MIDIbox CV V1.2 is now available for download New Features: Support for AOUT_NG module Support for BankStick (128 Patches can be stored) Interpolation function which allows to smooth 7bit controllers (CC/velocity/...) over 12bit resolution with selectable slew rate Legato/Mono/Poly now selectable seperately for each channel main page now displays patch number, patch name and 8 animated (short-triggered) activity meters there is now a DIN sync start/stop output available at pin C.1 (CORE::J7:SC) the DIN sync clock output is now located at pin C.0 by default (CORE::J7:RC, consistent with MBSEQ) ChangeLog: http://www.ucapps.de/midibox_cv_changelog.html Updated User Manual: http://www.ucapps.de/midibox_cv.html Download: http://www.ucapps.de/mios_download.html Have fun! :) Best Regards, Thorsten.

Maybe Ralf's implementation will give you some additional inspirations: http://www.suckow.de/ralf/ledmatrix4x20/ It has been used in Monodeck II: http://www.monolake.de/monodeck/index.html Yes, I prefer 74HC595 only because it will still be available in 10 years and more, and it can be purchased worldwide. Maxim chips are coming and going... sometimes they are out of stock, and you will have to wait some months for the next production run. Or they will be discontinued, and you will have to search for a replacement part. No issue if only a small circle of people is interested for a short term... Best Regards, Thorsten.

It should work. After the change_id application has been uploaded successfully via MIDI (you should see the appr. response messages in MIOS Studio), the core should reset, thereafter the MIDI Out should only send garbage (mostly pitch bender events) due to the wrong baudrate. The LCD will print the new ID - it should be 0000000000000100 Best Regards, Thorsten.

Thats not correct, each port can be accessed individually, assignments can be made for each track seperately, and the information is stored in a pattern, so that you can even change the instrument (port) on-the-fly while changing to a new pattern. Without such advantages, it wouldn't make much sense to build more than one MBHP_IIC_MIDI module... Best Regards, Thorsten.

Hallo, willkommen im Forum! :) Ja, das MBHP_IIC_MIDI Modul kann man auch von anderen Mikrocontrollern aus ansprechen. Dazu braucht es noch nicht einmal einen IIC Port, die Kommunikation funktioniert auch per "Bit-Banging" (SCL und SDA direkt von der Software aus stimulieren). Mit einem integrierten IIC Master Peripheral ist es natuerlich bequemer. :) Gruss, Thorsten.

Note that the PIC has two PWM outputs as well. However, controlling the brightness of individual LEDs is not possible with the MIOS concept, as it would load the CPU so much, that no other tasks could be executed in parallel. Problem is, that you need a PWM period of 10 kHz and more if brightness should be controlled with a resolution higher than 3bit. Thats the reason, why normaly dedicated chips (or microcontrollers with special integrated PWM peripherals) are used - they keep the load of the main CPU low. Best Regards, Thorsten.

So long you are using prepared track configurations, no changes in the code are required. Such configurations could even be edited on a PC and transfered to MBSEQ via SysEx.... if an editor would be available. However, SysEx dumping is supported, so the basics are there. If you have some programming experiences, why not writing an editor from which every user could benefit? :) Best Regards, Thorsten.

Razmo tried this, and it didn't work in the first place. After some emails it turned out, that there is a DC offset at the output of YAC512, which will be amplified above 5V after IC3 and IC5. This completely removes the AC part if OPAs are only supplied by +/- 5V, so that the audio output behind IC6 is silent. Workaround was to add a cap/resistor pair after each IC3/IC5 output in order to remove the DC part Note also, that using the 5V supply of the digital domain will add some noise to the analog domain. Razmo used a seperate transformer. Best Regards, Thorsten.

Oha - das liest sich, als gaebe es ein Problem mit Reflexionen auf den Signalleitungen. Praktisch konnte ich damit bisher keine Erfahrungen sammeln, deshalb bin ich mir auch nicht sicher, was nun die perfekte Loesung ist. Die Theorie wird hier kurz erklaert: http://www.elektronik-kompendium.de/sites/grd/0301035.htm, und sicherlich auch irgendwo in Wikipedia. Probiere mal folgendes: schliesse die SC und RC Signale am Ende der DOUT und DIN Kette (J2:SC/J2:RC) mit jeweils 220 Ohm-Widerstaenden gegen Masse ab. Wenn das nicht weiterhilft, probiere auch mal 100 Ohm, 470 Ohm und 1k (falls vorhanden) - ich weiss hier wirklich nicht, welcher Wert besser geeignet waere. Die DI/DO Signale sind nicht so wichtig, da die Leitung zum jeweils letzten IC im Vergleich zu RC/SC sehr kurz ist. Auch fuer die Spannungsleitungen sind die Widerstaende nicht relevant. Wenn das weiterhilft, schreit es geradezu nach einer neuen Wikiseite ;) Gruss, Thorsten.

The Synched Pattern Change function doesn't check for the end of a track, but synchronizes a pattern change on the 4/4 measure. It isn't so easy to determine when all 16 tracks have reached the end, especially because of all the possible variations. For example, what if one of the tracks uses different progression parameters, or is clocked at a different speed? Should the synched pattern change really wait until (let's say) all 1024 steps have been processed? It would make the synch function useless! The other sequencer hardware you mentioned, which one do you mean exactly? What is the usemodel, and what are the possible variations? E.g., a common groovebox doesn't allow you to control the track direction, to skip steps, to play them multiple times, to jump randomly and/or to play steps at different speed. For a simple sequencer determining the end of a track is very easy... but not for a more advanced sequencer like MIDIbox SEQ. What I would find more useful (as usemodel), is the possibility to optionally synch pattern changes to two or four measures (=32 or 64 16th notes). I guess that this is the function for which you are asking, right? Best Regards, Thorsten.

Probiere mal folgendes aus: - die 74HC165 des dritten DIN Moduls nacheinander entfernen - tritt das Problem auf, wenn keine ICs mehr in den Sockeln stecken? Oder tritt es auf, wenn mindestens einer im Sockel steckt. Welcher Sockel macht Probleme? - MIDIO128 aufladen und an den Encodern/Buttons herumspielen, die am dritten DIN Modul angeschlossen sind. Jeder Encoder sollte zwei Noten senden, jeder Button eine Note. Sie sollten niemals den gleichen Notenwert senden. - das Kabel zum J1:SI Ausgang des dritten DIN Moduls entfernen - die Encoder/Buttons haben nun keine Funktion mehr, doch tritt das Problem an den DOUT Modulen immer noch auf? Falls ja: SI wieder anschliessen, stattdessen J1:SC abklemmen und testen. Das gleiche auch nochmal mit J1:RC ausprobieren. Die Ergebnisse sollten uns genuegend Input geben, um das Problem besser eingrenzen zu koennen. Gruss, Thorsten.

Yes, it's obscure why you can upload an application correctly, but not a MBFM patch. You can check the reliability of your MIDI interface the following way: create an external feedback loop (MIDI Out->MIDI In) on your PC interface, open the SysEx tool of MIDI-Ox, load the patches into the command window, press Command->Send/Receive SysEx, and thereafter compare the dumps with the SysEx->Compare function. If MIDI-Ox finds errors, you know that the MIDI interface is the reason. Another point is, that you could have overlooked a programming error during application upload. So, just to ensure that MBFM is complete, upload the application again, and doublecheck that all code blocks have been acknowledged without an error message. Best Regards, Thorsten.

Hi Alex, currently there isn't an application available which fits exactly your needs. But I guess that it could be easily programmed with the SDCC wrapper. Or maybe somebody has already implemented a similar floorboard application, which could be easily adapted? Best Regards, Thorsten.

The power consumption mainly depends on the LCDs, LEDs and SID chips you are using. I cannot give you the exact values for each seperate module, but the overall current draw of my completely stuffed MBSID: ca. 1A in the 5V branch, and ca. 0.2A in the 9/12V branch. The consumption of the AOUT_LC module can be ignored (I guess about 10 mA) Best Regards, Thorsten.

this will work Best Regards, Thorsten.

I think that the last encoder assignments won't work this way: ;; encoders 33-48 ENC_ENTRY 13, 0, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 33 ENC_ENTRY 13, 2, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 34 ENC_ENTRY 13, 4, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 35 ENC_ENTRY 13, 6, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 36 ENC_ENTRY 13, 4, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 37 ENC_ENTRY 13, 6, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 38 [/code] It isn't explicitely mentioned, but double-assignments are not allowed. Instead, you have to assign the last two encoders to individual pin groups, e.g. 14,0 (for SR14, pin 0 and 1) and 14,2 (for SR14, pin 2 and 3) Best Regards, Thorsten.

Memo: bei PIC Problemen aller Art, einfach mal dem Onkel Doc-tor zuschicken (er nimmt auch keine Praxisgebuehren ;-) Paya: schreib' bitte Mike eine Mail, dass der Bootloader nicht programmiert war Gruss, Thorsten.

Da die analogen Eingaenge an J5 wahrscheinlich nicht auf Masse liegen, waere die MIDIO128 zum Testen besser geeignet. Ich habe von diesem Phaenomen schonmal von einem anderen Anwender gelesen, damals war es glaube ich aber nur eine einzige LED, die flackerte. Aufgeklaert wurde es nie (zumindest habe ich keinen Feedback erhalten). Deshalb waere es sehr interessant zu wissen, ob das Problem nur mit der MBSEQ Applikation auftritt. Gruss, Thorsten.