TK.

Ok, dann hast Du wirklich was falsch verstanden. Der Core wird "nicht gefunden", wenn Du nicht das selbe Interface fuer IN und OUT selektierst, aber darum geht es bei diesem Test doch gar nicht - die Meldung sagt lediglich, dass der Code Upload so nicht moeglich ist, auch das MIOS Terminal wird so nicht funktionieren. Du moechtest nicht die Firmware neu aufladen, sondern ueberpruefen, ob am MIDI Out etwas rauskommt. Und zwar, indem Du den MIDI OUT des Core Moduls an den MIDI In des MIDI Interfaces anschliesst, im MIDI IN Monitor von MIOS Studio das MIDI Interface selektierst und ueberpruefst, ob die Noten ankommen. Doch da Du den Shruthi nun umgeruestet hast, koenntest Du ihn doch jetzt mal direkt am MIDI Out anschliessen? Oder funktioniert das immer noch nicht? Gruss, Thorsten.

Sorry, ich blick nicht mehr durch... %-) Gruss, Thorsten.

Dafuer benoetigst Du einen MIDI Router, der auf dem PC laeuft. Windows: http://www.hermannseib.com/english/miditrix.htm MacOS: http://notahat.com/midi_patchbay Linux: http://murks.lima-city.de/serendipity/index.php?/archives/7-ALSA-and-JACK-MIDI-explained-by-a-dummy-for-dummies.html Gruss, Thorsten.

Hi, MIOS32 handles MIDI data packet based which simplifies the merging: package in -> package out I guess that with "MIDI router of LPC" you actually mean the MIDI router of MIDIO128? Yes, you can configure it to forward incoming data to a MIDI Out port. 16 nodes are available (16 "virtual cables") which you can use for setting up forwarding rules. The parameters are explained at the MIDIO128 page, search for the keyword "router". Best Regards, Thorsten.

Everything looks fine, no additional configuration required. The error messages can be ignored, once the remaining files can be generated without the control surface they will disappear, but the sequencer will also work without the banks/mixer maps, etc... it will just use the initial setup, where track1 sends a note each beat. While the app is configured correctly now, it's time to debug the hardware. How do you test the output of MIDI OUT1? Best Regards, Thorsten.

Wo hast Du den Shruthi angeschlossen? Am MIDI Out des Core Moduls? Gruss, Thorsten.

Ja, den koenntest Du erstmal ausprobieren falls wirklich notwendig. Weil beim MBHP_CORE_LPC17 Modul der Strom am MIDI Out auf ca. 5 mA begrenzt ist; der LPC1769 wird nur mit 3.3V betrieben. Das liegt jedoch noch innerhalb der MIDI Spec, das Problem ist der MIDI IN Port des Shrutis, bei dem sich nicht an die MIDI Spec gehalten wurde. Dein MIDI Keyboard arbeitet wahrscheinlich auf 5V Basis. Gruss, Thorsten.

Du musst auch im OUT Fenster das Core-Modul selektieren, um eine bidirektionale Verbindung herzustellen. Gruss, Thorsten.

Apropos: mit MIOS Studio 2.2.3 wird die Note im Klartext angezeigt -> jetzt updaten! :) Gruss, Thorsten.

Das Problem koennte uebrigens auch an der Optokoppler-Schaltung vom Shruthi-1 liegen. Der Pull-Up (R14 auf dem Digi-Board) ist mit 10k zu hoch dimensioniert, versuche es mal mit einem 1k Widerstand. Falls das auch nicht weiterhilft: den 6N137 durch einen 6N138 austauschen. Gruss, Thorsten.

With a bit of luck only the 74HC595 and/or 74HC165 have to be replaced... :-/ Best Regards, Thorsten.

No, MBHP_MF_NG doesn't emulate Motormix - is this really required? Logic or Mackie Control should be sufficient? /Edit: Mackie HUI and Motormix are now supported with V1.002 of the firmware, see postings in June I just have released a new version, it can be downloaded from http://www.ucapps.de/mbhp_mf_ng.html V1.001 got some new operating modes: The additional CC modes allow to use more than two MBHP_MF_NG modules with unique CC numbers Please note that the mode IDs are incompatible to the previous version! -> if you are using MBHP_MF_NG V1.001 (or higher), you can only configure it with MIOS Studio 2.2.3 (or higher) Best Regards, Thorsten.

MIOS Studio 2.2.3 is available now Updates: MIDI IN/OUT monitor translates the MIDI event into text format! :) Keyboard and upload panel not resized anymore. This has the advantage that the terminal and MIDI monitor panel can be enlarged quickly without re-adjusting the other panels (disadvantage: Upload and Keyboard window can't be hidden anymore, but I can live with that - still searching for a better solution...) MBHP_MF_NG SysEx tool supports new operating modes of firmware v1_001 Silent update MIOS Studio 2.2.4 MBHP_MF_NG SysEx tool supports new operating modes of firmware v1_002 Best Regards, Thorsten.

Ok, as you can see here: [11954.227] File /SESSIONS/DEFAULT/MBSEQ_C.V4: doesn't exist the MBSEQ_C.V4 file doesn't exist in the default session directory (it's not located in the root directory) I just noticed, that it isn't possible to create this file without the control surface. I will make this possible in the next release. However, you could also create it manually, and only insert the required content. - type "msd on" - this should mount the SD Card on your computer (note: MIDI communication not possible anymore! Close MIOS Studio) - create the file /SESSIONS/DEFAULT/MBSEQ_C.V4 with a text editor - enter following line into this file: MIDI_DefaultPort 32 [/code] - store the file - unmount the SD Card from your OS - reset the core (e.g. turn it off and on again) - open MIOS Terminal - check that the new MIDI_DefaultPort value has been taken over by typing "global" into the MIOS Terminal -> all tracks should now send to MIDI OUT1 Best Regards, Thorsten.

No progress yet, I prioritized MBCV V2 :) Best Regards, Thorsten.

access granted. Best Regards, Thorsten.

Currently the patch and snapshot handling will be overworked, see also: http://www.ctrlr.org/viewtopic.php?f=2&t=861 (please note: r965 fails to handle the MBSID panel correctly, please wait for a newer release, and wait until the MBSID panel supports the new features!) Due to the upcoming conceptional changes, I haven't prepared patch sending yet - it will work flawlessly sooner or later! :) Best Regards, Thorsten.

R.I.P. :-(

Modifiying the ain64din128dout128 app is not the most simple solution, you would have to work through the tutorials to understand the basics first -> http://www.ucapps.de/mios8_c.html otherwise you are lost when debugging your modifications. If Julien (who brought up the idea) can support you on this topic, it might be feasible for you without spending so much time. 4051: just have a look into the MBHP_AINX4 schematic, the 4051 doesn't need additional circuitry, you can connect it directly to the appr. pins of the core module. Are you able to enhance your MIDIbox based on this schematic, or do you need additional help here? (currently I won't have the time to draw a customized schematic) Don't forget to connect all unusued pot inputs to ground! Best Regards, Thorsten.

V2.040 comes with an important bugfix: MIDIboxSID V2.040 ~~~~~~~~~~~~~~~~~ o fixed SysEx patch write issue which happened when patches were received with the common format (e.g. preset patches) [/code] Best Regards, Thorsten.

This bug was easy to reproduce and it's fixed in V2.040 :) Best Regards, Thorsten.

If you are using the OSC option, no MIDI routing should be required as data is transferred directly via ethernet. So, the remaining configuration has to be done at MBSEQ side (normally from the control surface) Without a SD Card you can only use the default configuration: each track sends data to USB1 You could route this data to your synth via a virtual MIDI Patchbay running on your Mac. I recommend this one because it has very low latency: http://notahat.com/midi_patchbay Alternatively: install a SD Card and change the global MIDI port in the MBSEQ_C.V4 file, so that MBSEQ sends to MIDI OUT1 by default. Best Regards, Thorsten.

(btw.: I'm out since I don't think that implementing MB64 from scratch based on this template application is worth the effort compared to the 0.30 EUR extra costs) Best Regards, Thorsten.

Really? With r945 for Windows which I posted two postings above yours? Best Regards, Thorsten.

Here the link to a "known good" version for Windows: http://www.ucapps.de/tmp/Ctrlr_r945.exe Best Regards, Thorsten.