TK.

One MBHP_DINX4 kit is sufficient, rosch means that 1 and a half of the module will be used. Best Regards, Thorsten.

Spectra is so cool, thanks a lot for posting this! :-) Best Regards, Thorsten.

Here the appr. mb64e_meta.inc file: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox64e%2Fmeta_examples%2F5%2Fmb64e_meta.inc Just copy it into the src directory (overwrite the original mb64e_meta.inc file), and recompile the application. Usage: ; send note event depending on encoder direction ; the encoders have to be configured in "0 +/- 1" mode! ; ; Example Config: ; Meta Event 0x30 will send a Note On Event C-2 on left-turn, and C#2 on right-turn Best Regards, Thorsten.

Finally a preconfigured firmware where the left/right button can be replaced by an encoder: http://www.ucapps.de/mios/midibox64_v2_4f_with_datawheel.zip DIN Assignments: EXIT button at D7 SNAPSHOT button at D6 Encoder at D4/D5 Best Regards, Thorsten.

I still prefer PICKIT 2/3, because the Brenner8 software doesn't run under MacOS :-/ Another reason: in future, there won't be so many people who need a PIC programmer for the old MIDIbox projects anymore (especially since there is always the option to buy pre-burned PICs from SmashTV). Therefore I need something which is well established today, and which is a stable reference for the next years. Everything else is a nice DIY solution for people who like the challenge, but counter-productive at my side (e.g. updating documentation, testing updates, supporting people who can't get it running, etc). Best Regards, Thorsten.

yes MBSEQ has it in the BPM page Best Regards, Thorsten.

It's the BPM generator which generates the FC events, the router commands shows that IN and OUT are enabled at both sides. So, try: set mclk_in IN3 off set mclk_out OUT3 off at both cores to avoid the feedback. Best Regards, Thorsten.

There is an alternative solution, and you partly already used it: Turn of the core and push the start button in MIOS Studio. Then turn on the core again (supply power), and the upload will start via 1st level bootloader, and not via the (faulty) application. This allows you to update your application directly, since it won't be started before the upload begins (and has been finished) Best Regards, Thorsten.

Fine! :) What was the error, maybe the contrast pot? Best Regards, Thorsten.

Bei mir funktionierts; verwendest Du auch wirklich den aktuellen SVN Stand? Bzw. hast Du mal "svn update" eingegeben, um das Repository auf den neusten Stand zu bringen? Gruss, Thorsten.

Hi, you did it right - the most simple way to link two cores is a common MIDI IO crosslink, and MIDI3 was a good choice. But I'm surprised that you get a feedback. Could you please enter the "router" command in both applications, and copy&paste the terminal output into this posting? Best Regards, Thorsten.

In order to clarify this, I've ordered a PICKIT2 compatible programmer and will test it under MacOS with all PICs used in the MBHP -> http://www.reichelt.de/Programmer-Entwicklungstools/DIAMEX-PIC-PROG/3/index.html?&ACTION=3&LA=5&ARTICLE=137174&GROUPID=2969 If it works, I will recommend PICKIT2 or PICKIT3 (and compatible) in future. Best Regards, Thorsten.

Hi, it should be possible to send multiple SysEx strings from a single .syx file now; please try this pre-release: http://www.ucapps.de/mios32/midibox_seq_v4_079_pre2.zip If this still doesn't help, could you please attach a .syx file which allows to reproduce the issue at my side? Best Regards, Thorsten.

This would work for sending, but not for receiving. Means: if your DAW sends back EQ values of a channel strip which is not part of the current bank, they won't be taken over, because there won't be matching encoder events in the current bank. Btw.: how many encoder events do you need exactly? Maybe it's possible to assign the same events in all groups (to the same physical encoders) when they should always be available. Did you already try this? Best Regards, Thorsten.

With the MB64E firmware this should be possible by using Meta Events. I can give you an explicit example once I'm back from vacation; for preparation: could you please specify, which note values (and velocity values) should be sent exactly on left/right turns? Best Regards, Thorsten.

It requires some changes in setup_midibox64.asm and mios_tables.inc (as described in the files), but I must admit, that the change isn't straightforward... in addition you've to install the MIOS toolchain to recompile the application. Anyhow, I could change the setup for you and give you a .hex file... Next week after my holidays. Best Regards, Thorsten.

Hi, Groups are some kind of 'banks in banks'. E.g. A bank of 128 encoder entries can be mapped to 16 physical encoders, which results into 8 groups. Groups can be switched with buttons assigned to special functions (SFB). Unfortunately MB64E doesn't provide the flexibility to define encoders and buttons which are not part of a group, but this is actually what you want to achieve. This has been solved with MIDIbox NG, which is much more customizable, but this firmware won't run on a PIC based core. On a PIC this could only be achieved with a selfwritten application (there are tutorials which describe the basics, but you will need some programming skills to put this together) Best Regards, Thorsten.

Hi, yes, this sounds like a firmware issue. I remember that I optimized the SysEx handling some time ago, but I haven't chekced the "send from SD card" routine... :-/ I will come back to this topic in ca. 1 week. Best Regards, Thorsten.

Well, 1750 chips have been solt, I'm sure that there are enough people (maybe even in the same country you are living) who have some spare parts ;-) Best Regards, Thorsten.

Passt schon, eine Matrix-Verschaltung ist in Deinem Fall die bessere Wahl. Beispiel-Skripte gibt es im midibox_ng Installations-Package (cfg-Verzeichnis), das Du hier runterladen kannst: http://www.ucapps.de/mios32_download.html Ansonsten gibt es noch ein Tutorial ('first steps') sowie eine Dokumentation ueber das .NGC format, wo weitere Beispiele zu finden sind: http://www.ucapps.de/midibox_ng_manual.html Gruss, Thorsten.

Aside from the latency and jitter issue, the slave machine will probably also load the CPUs so much, that the performance of other apps (like your DAW) will be affected. Therefore an alternative idea: you could cannibalize the MIDI interfaces, at least the case and the MIDI IN/OUT ports + optocoupler circuitry would still be useful. And then just build a Mini-GM5 module into the case, which gives you up to 5 IOs. Add another one for up to 10 IOs, etc... Best Regards, Thorsten.

Addendum: it's better if you would place the encoders under the LCDs, otherwise your hands will cover the display whenever you are changing values. Best Regards, Thorsten.

I will check this after my vacation - I guess that this special button behaviour will require two new Meta Events, which allow to control a 'virtual' encoder. Best Regards, Thorsten.

Zu den Drums: eine Diskussion ueber dieses Thema gab es bspw. hier: Vielleicht hast Du Lust, mal ein Diagram zu arbeiten? JSynthLib sourcecode: http://sourceforge.net/p/jsynthlib/code/HEAD/tree/trunk/JSynthLib/synthdrivers/MIDIboxFM/ Arpeggiator: gibt es doch eigentlich schon in der MBSEQ, kennst du bspw diese tutorials? http://www.ucapps.de/midibox_seq_manual_tut.html Gruss, Thorsten.

Hallo Thomasch, Zu frage zwei: ich bin kein Ableton user und kann deshalb leider auch nicht beim Testen helfen, es sei denn, du schaffst es, ein Plugin zu generieren... Zu frage eins: ich habe vor urzeiten mal einen wavetable editor fuer Jsynthlib geschrieben, der leider unter MacOS wegen diverser Java Inkompatiblitaeten nicht mehr laeuft... doch die Sourcen (die Du auf sourceforge findest) sind eine wertvolle informationsquelle. Ich habe gerade keinen Zugriff auf die Sourcen, doch soweit ich mich erinnern kann, besteht bei der MBFM die Wavetable aus 32x4 Eintraegen. Jeder Eintrag besteht also aus 4 Bytes, alle Bytes verwenden nur die ersten 7bit, so dass sie sich ohne Umkodierung via SysEx uebertragen lassen. Im ersten Byte ist in Bit 0..4 ein Jump auf den naechsten Eintrag kodiert, und in Bit 5, 6 und 7 befindet sich ein Flag fuer die naechste 3 Bytes, mit dem man zwischen absolut und relativ Werte umschalten kann. In den folgenden Bytes dann der Wert, der in die CC Register uebertragen werden soll. Gruss, Thorsten.