TK.

Ok, now I remember - it seems that this guy has been forgotten in the MBHP_CORE_LPC17 layout (no third pin header)... It has to be connected to FB2 in order to avoid coil saturation problems. Ethernet will work without the connection (at least at my side)... but this connection will make it more robust. References: http://knowledgebase.nxp.com/showthread.php?t=1499 (note that this picture shows a MagJack with a different pinning - just only the "red wire" which goes to FB2 is for interest) I'm unsure if it's really worth to add this connection. E.g. the Embedded Artists base board also doesn't provide it. Best Regards, Thorsten.

ok, das bedeutet schonmal, dass Deine Konfiguration uebernommen wurde. Sehr seltsam - das bedeutet, dass die Pins permanent auf 5V stehen. Probierst Du mal probehalber das zweite Shift Register aus? Es ist ja nicht fuer die Matrix konfiguriert, somit sollten die Ausgangspins auf 0V stehen. Falls die ebenfalls permanent 5V ausgeben, ist etwas mit der SC oder RC Leitung nicht in Ordnung. Arbeitest Du unter Windows? Verwendest Du den Korg MIDI Treiber (mit dem sollte es besser funktionieren)? Das ist normal: mit "msd on" wird das USB MIDI Interface deaktiviert, deshalb kann der Core auch nicht den "msd off" Befehl empfangen (das wuerde dann nur noch ueber die normalen MIDI Ports funktionieren) Gruss, Thorsten.

Ok, you are right that for such purposes the MBNet would be very useful. The CAN communication handler is already implemented & working (e.g. I can connect to a MBSID V2 via a LPC17 core) - so, it won't be that difficult to support this possibility to link multiple cores, therefore I added it to the feature list. :) With a single SRIO chain (up to 16 DINs and 16 DOUTs) 64 encoders and 64 LED rings can be serviced. With a second SRIO chain (+16 DINs and +16 DOUTs) 128 encoders and 128 LED rings Best Regards, Thorsten.

Alright - understood and fixed in v1.3a :) MIDIbox Seq Dr V1.3a ~~~~~~~~~~~~~~~~~~~~ o backward mode and progression now working correctly for tracks with more than 16 steps [/code] Best Regards, Thorsten.

The appr. changes are now available in v4.065: MIDIboxSEQ V4.065 ~~~~~~~~~~~~~~~~~ o the DEBOUNCE_DELAY parameter of the MBSEQ_HW.V4 file will now be also taken for the BLM8X8 (Wilba's Frontpanel) o Mixer: setup now automatically loaded when a new mixer map is selected o Sessions: the SAVE function now also stores the current mixer map [/code] Best Regards, Thorsten.

Ja, Du kannst den Patch auch direkt mit dem "load" Kommando laden (wenn Du ihn in matrix.mio umbenennst). Bei einem Neustart (Startup) wird jedoch wieder der default.mio Patch eingeladen - deshalb die Empfehlung, den Patch auch gleich entsprechend zu benennen. Gruss, Thorsten.

The buttons are really nice! Great work! :) Best Regards, Thorsten.

Some parts of MBNG can be re-used in the MBKB later, but it has to be considered that adding additional DIN and DOUT registers will affect the scan rate for the keyboard, therefore it's probably not a good idea if you really want a "high quality" solution. However, depending on the outcome of the second SRIO chain investigations it might be possible to scan the keyboards independent from remaining DINs/DOUTs, and this will definitely help for using MBKB as a controller - but I won't start this before MBNG is (almost) finished. Btw.: no problem to add MBHP_AINSER64 modules to MBKB, because this module has already a dedicated interface. simply via MIDI IO You are right, it makes sense to merge the MBNG and MBKB project in mid-term (but not for the first release) I updated http://www.ucapps.de/midibox_ng.html accordingly (the MBKB topic is now sorted under "Features/Specs under evaluation") I will consider an independent scan rate from the beginning, because this has also other advantages: LED rings can be serviced faster, this makes them brighter :) Yes, this will be required anyhow if MBNG is used as a programmer. I've added this topic to the spec is it really required? Anyhow, I added CopperLAN to the evaluation list. The company got already a MBHP_CORE_LPC17 module to test the communication between MIOS32 and the Copperdiono :) Yes! :) (because my MBLC works with a MBHP_CORE_STM32 as well, and I will also test MBNG with the MBSEQ hardware) Best Regards, Thorsten.

The problem is, that with progression enabled the steps stay in the current section (A, B, C or D). It will be difficult to overcome this limitation - is it important? Best Regards, Thorsten.

Hi Anders, yes, you will need a bankstick to store different setups. Then you need to configure 5 buttons as "special function buttons" as documented in midibox64e_sfb_table.txt E.g. let's say that the buttons are connected to the first 5 inputs of the first shift register, then write: 1.1 = FF 02 00 # switch to Bank 1 -- for quick access 1.2 = FF 02 01 # switch to Bank 2 -- for quick access 1.3 = FF 02 02 # switch to Bank 3 -- for quick access 1.4 = FF 02 03 # switch to Bank 4 -- for quick access 1.5 = FF 02 04 # switch to Bank 5 -- for quick access [/code] in your .ini file (which then has to be converted to a .syx file) This has to be done for all banks, so that the SFBs are always available (this makes the SFB "global") Best Regards, Thorsten.

The MB64E has an integrated MIDI merger which will do this job - just enable it. :) Best Regards, Thorsten.

When you connect the USB cable, you will see 4 MIDI interfaces on your PC (when you connect the USB cable on a GM5, you will see 5 MIDI interfaces) Not really. And: I don't know the current capabilities of Live, but if it allows to forward MIDI streams as well, I would use this DAW instead of MIDI-Ox, because I guess that each application which will connect to a MIDI interface will add (a small amount of) latency, resp. CPU performance. Because each application has to be notified whenever new MIDI data is received. Best Regards, Thorsten.

Hallo, ich habe Dein File in matrix.mio umbenannt, und unter Disk->Load eingeladen - alles funktioniert wie erwartet: DIN 1..4 sowie DOUT 1 sind als Matrix konfiguriert. Wenn ich nun bspw. mit einem Kabel einen DOUT Pin vom ersten Shift Register mit einem DIN Eingang verbinde, wird nur eine MIDI Note gesendet. Wenn ich Masse (Vs) mit einem DIN Pin verbinde, werden 8 Noten gesendet. Hast Du eigentlich ein SCS (also LCD, Encoder, Buttons), um die Einstellungen direkt zu modifizieren? Falls nicht: dann musst Du das File in default.mio umbenennen, denn nur dieses wird nach Startup eingeladen. Tippe auch mal im MIOS Terminal den "show" Befehl - tauchen hier Deine Matrix-Einstellungen auf? Gruss, Thorsten.

Take care! The MIDIsport 2x2 has a "MIDI THRU" switch in front, which will forward MIDI IN to OUT without USB being involved. This switch has to be latched in ("turned on") to enable USB Best Regards, Thorsten.

ok for me. About a fair price: at least the material and shipping costs that you paid. Best Regards, Thorsten.

Sehr schoen (und vor allem robust!) :) MIDI-Fighter scheinen ja gerade sehr aktuell zu sein. Gruss, Thorsten.

The MagJack pinning is not identical to RJ45 (you're comparing apples and oranges ;-)) The documentation under http://www.ucapps.de/mbhp_core_lpc17.html says: Since the LPCXPRESSO module doesn't provide dedicated pins for the two Ethernet Socket LEDs, you have to solder them directly from the appr. on-board SMD LEDs to J26 of the core module with two wires: Best Regards, Thorsten.

I can understand the confusion, and I think that I should improve the integration of mixer maps. A mixer map is part of the session, but currently it won't be stored with "Session Save" in the main page. Instead it has to be saved separately in the mixer map page -> this will be changed. After the mixer map number has been changed, you've to press the LOAD button to load it from SD Card. I will change this as well, so that it's automatically loaded on a mixer map number change. Best Regards, Thorsten.

I'm not a Windows user... maybe somebody else knows why this can happen? Best Regards, Thorsten.

Fine! :) Best Regards, Thorsten.

Yes, I guess that sooner or later another guy will request a loop mode for a single .mid file - let's wait (1..2 years ;-)) Note that we're at v3.010 meanwhile, it fixes a bug in the configuration interface (MIDI router wasn't accessible) Best Regards, Thorsten.

Hi, yes, you found the documentation for the wrong toolchain. Here is the right entry point: http://www.ucapps.de/mios32_c.html This page also contains some tutorials which are worth to read, because they explain the basic concepts step by step. Once you've reached #012b, you know how to access the AINSER64 module! :) Best Regards, Thorsten.

Hallo Marcus, danke fuer den Hinweis, das habe ich glatt uebersehen! -> fixed in midio128_v3_010 Hintergrund: der MIDI Router ist nun ein Modul, das von mehreren MIOS32 Applikationen verwendet wird. Beim Umziehen habe ich vergessen, das MIDIO128 SCS auf die neuen Variablen umzubiegen, deshalb hatten Aenderungen keine Wirkung. Ueber das Terminal lies sich der Router jedoch ganz normal konfigurieren - und nur so hatte ich es getestet, und deshalb den Fehler nicht bemerkt. Gruss, Thorsten.

Got it, fixed it! The tap tempo function was calculating with 5 taps based on the delay measured for 4 taps - therefore the resulting tempo was too high. In v4.064 it should work very accurately now! :) Best Regards, Thorsten.

For the records: Shimoda's issue has been fixed, see also: A new release is available: MIDIboxSEQ V4L.064 ~~~~~~~~~~~~~~~~~~ o corrected tap tempo function [/code] Best Regards, Thorsten.