TK.

Hallo Alex, eine gute Grundlage ist sicherlich die "Pedal Box" von Durisian: http://www.midibox.org/dokuwiki/doku.php?id=pedal_box Allerdings wirst Du nicht drumherum kommen, die Firmware zu erweitern (bzw. Durisian darum zu bitten, eine Erweiterung vorzusehen). Fuer den Fall, dass Du die Software selbst erweitern moechtest, kann ich Dir weitere Tips geben... 1) Mute Pulse: hier muesste ja nur ein Signal geschaltet werden, richtig? Das koennte man von einem freien IO aus waehrend des Patch-Wechsels "senden". 2) ja, koennte man in die Firmware einbauen. Im internen EEPROM des PIC18F4620 koennen bis zu 1024 Bytes gespeichert werden. Falls das zu wenig ist, kann ein externen EEPROM (-> BankStick) angeschlossen werden, die entspr. MIOS Funktionen sind verfuegbar und dokumentiert. Gruss, Thorsten.

this was also my first thought, especially considered that the firmware capabilities are very user friendly, but accordingly also limited. On the other hand I think, that they made a good product out of their platform. It's superior compared to other commercial solutions (e.g. Doepfer), and users are paying for the development and support efforts -> well done! :thumbsup: Best Regards, Thorsten.

Thanks for the changes! But I'm very careful with "2.0" versions (and as you mentioned, the Windows crash still happens). Beside of this minor issue, which only happens under Windows, and which is probably related to a stupid error in my code, but doesn't affect the actual handling during runtime (only exit of application) there is no need for an update. I'm even more careful with "latest git versions", because using such undefined sources usually lead to a disaster when multiple people are trying to build the code some weeks or months later -> never use such versions for public releases...! So, I will give 2.1 a try once it's available, and then incorporate your changes into the original code. Until then, I prefer a stable version which has been proven by many MIDIbox users under Mac/Windows/Linux in the past. Best Regards, Thorsten.

On the DINX4/DOUTX4 module, there isn't enough space for polarized connectors... :-/ But at least I considered this on the new MBHP_DIO_MATRIX module, because meanwhile I don't want to miss them as well! :) Best Regards, Thorsten.

:thumbsup:

Bin gespannt! :) Theoretisch waere es zumindest so realisierbar: die MBFM hat ja einen CC Modus, in dem die Controller-Aenderungen, die am Geraet vorgenommen werden, als CC versendet werden, so dass sie sich in der DAW aufzeichnen lassen. Ctrlr koennte diese CCs auswerten, und direkt an die Regler im Panel weitergeben. Da die CC Nummern auch den SysEx-Adressen entsprechen, waere kein zusaetzliches Mapping notwendig, und somit mit wenig zusaetzlichen Programm-Code integrierbar. Wuerde das dem entsprechen, was Du Dir vorstellst? (ich halte es fuer sinnvoll, beim Lemur basierten Panel fuer die MBCV V2 habe ich das bspw. schonmal ausprobiert und war ziemlich zufrieden mit dem Ergebnis) Das waere jedoch etwas anderes - muss es wirklich ein "Local Off" Modus sein, muss Ctrlr oder die DAW wirklich die CCs erst zurueck an die MBFM senden? Das wuerde bspw. die Gefahr fuer eine ungewollte Feedback-Loop vergroessern. ist auch sehr unueblich bei Synthesizern, oder kennst Du einen, bei dem es so ist? Hier bestuende ebenfalls die Gefahr fuer eine Feedback-Loop. Die Merge-Option fuehrt einen externen Datenstrom mit dem intern generierten zusammen, und gibt ihn am MIDI Out aus. Sinnvoll ist das bspw. in folgender Konfiguration: MIDI Controller oder Keyboard -> MBFM im Merge Modus -> DAW So koennen sowohl die Daten des Controllers/Keyboards, als auch der MBFM (bspw. im CC Modus) aufgenommen werden. Dies nur als Beispiel, es gibt noch weitere Anwendungsfaelle. Nicht sinnvoll ist dieser Modus, wenn Du die MBFM direkt am MIDI IN/OUT Deines PCs angeschlossen hast, denn in diesem Fall macht es wenig Sinn, eingehende Daten wieder auszugeben. Deshalb ist dieser Modus auch nur optional. Verwendest Du die aktuelle Version 1.4? Dort wurden ja einige Zuordnungen korrigiert. Deine Beschreibungen sind sehr gut, ich kann sie auch ohne Ableton Live nachvollziehen. (Habe keine Lizenz, bin seit Jahren Logic Pro User und zu alt, um umzusteigen... ;-) aber zur Not tuts auch die Demo-Version, die glaube ich nur zeitlich limitiert ist, aber auf alle Funktionen Zugriff gewaehrt) Gruss, Thorsten.

Great! :thumbsup: Best Regards, Thorsten.

I guess that you added an encoder table, because 0x3280 is the location where this table is expected. Probably you forgot to add -DDONT_INCLUDE_MIOS_ENC_TABLE to the MIOS_WRAPPER_DEFINES variable (located in Makefile) as explained at the bottom of this page: http://www.ucapps.de/mios_c_send_enc_rel.html Best Regards, Thorsten.

I just have doublechecked that the released firmware is correct - it works at my side. The flashing LED indicates that the firmware is running successfully -> no installation problem. So, you can concentrate on checking the MIDI connections: 1) MIDI OUT check: move a fader -> PitchBender events should be sent (by default if no other mode is configured) If this doesn't happen, check the the MIDI IN port of your PC has been connected to the MIDI Out port of the core module (port located at the corner of the PCB) Does it work? 2) MIDI IN check: connect the MIDI IN of the PCB with the MIDI OUT port of your PC. Send a PitchBender event over channel #1 from the virtual keyboard of MIOS Studio (again: assumed that the fader mode hasn't been changed yet) -> the motor should start to move. Does it work? 3) Bidirectional check: press the Query button in MIOS Studio: the PIC should be detected. Does it work? If not, check the device ID, maybe the core has been configured for a different one? The device ID is visible in the SysEx message which is sent during power-on, see also http://www.ucapps.de/howto_debug_midi.html Note that this guide also contains some additional tips for troubleshooting the MIDI connections. 4) Configuration: works only with a bidirectional connection -> open the MBHP_MF_NG tool of MIOS Studio Ensure that you are using the latest MIOS Studio version! Best Regards, Thorsten.

Official thread about the MIDIbox KB project moved to: Best Regards, Thorsten.

This is a placeholder for the upcoming MIDIbox KB project. It's work in progress, some initial documentation can be found under http://www.ucapps.de/midibox_kb.html It started in the one Fatar keyboard has already been successfully midified, some other (different types) will follow. :) If you've questions or suggestions for enhancements, just post them here. :) Best Regards, Thorsten.

Congratulations! :) Your report is also nice to read! Could you please add a link to your project page: http://www.midibox.org/dokuwiki/doku.php?id=midibox_sd_card_sample_player Best Regards, Thorsten.

yes, the configuration of MBKB is very flexible, it also allows to handle a 2 octave keyboard. Connections are similar to this one: http://www.ucapps.de/midibox_kb/midibox_kb_fatar_df_61_interconnections.pdf One DIN and one DOUT is required, just translate the output/input connections to the actual circuit. Configuration: set srio_num 1 set kb 1 note_offset 48 set kb 1 rows 8 set kb 1 velocity on set kb 1 optimized on set kb 1 dout_sr1 1 set kb 1 dout_sr2 0 set kb 1 din_sr1 1 set kb 1 din_sr2 0 set kb 1 din_key_offset 32 set kb 1 din_inverted off set kb 1 break_inverted off set kb 1 delay_fastest 100 set kb 1 delay_slowest 2000 store [/code] Best Regards, Thorsten. P.S.: official MBKB thread here:

You could connect the cathode of the backlight directly to Ground, this should result into full brightness. According to the datasheet this is allowed (Vr = 5V, there is a Z diode to protect the LEDs) Best Regards, Thorsten.

Fine! :thumbsup: Best Regards, Thorsten.

Yes, the core development of MIOS, MIOS32, major apps and the hardware platform was mostly done by myself, but without the the help of the community (inspirations, proposals, improvements, testing, support of newbies - and this since more than 14 years!) the MIDIbox project wouldn't be where it is! :flowers: Especially without the technical support of the guys like SmashTV, Mike, Wilba, Nils, Seppoman, StrydOne, etc. etc (*) the projects would still be in a DIY niche which is intended for specialists only. Best Regards, Thorsten. (*) to be honest: I hate such lists, because I would have to add at least 50 additional people who helped in the past, especially in the early years!

Yes, because: I don't plan to support newer versions. Best Regards, Thorsten.

What is the output of sdcc --version [/code] It should return: [code] SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.8.0 #5117 (Mar 23 2008) (Mac OS X i386) Best Regards, Thorsten.

You have to show the complete compile log, otherwise it's difficult to help you remotely (without knowing the history) And you still haven't mentioned, under which operating system you are working... I guess that there is a compatibility issue with the installed SDCC version. As documented here, SDCC 2.8.0 should be used. Meanwhile I guess that you are working on a Mac, here a direct link to the appr. binary: http://sourceforge.net/projects/sdcc/files/sdcc-macosx/2.8.0/ If you are working under a different operating system, please search for the link by yourself! Best Regards, Thorsten.

Your setup isn't correct: it isn't required to move directories. Unfortunately (like many users) you forgot to mention under which operating system you are working. I also don't see how you downloaded the repository... this makes it difficult to give you explicit hints. :sad: Based on the terminal output I guess that you are either working under Linux or MacOS, so here some simple step-by-step instructions: 1) create a directory named "svn" in your home directory: mkdir ~/svn cd ~/svn [/code] 2) check-out the MIOS repository: [code] svn co svn://svnmios.midibox.org/mios 3) set the MIOS variables: export MIOS_PATH="~/svn/mios/trunk" export MIOS_BIN_PATH="~/svn/mios/trunk/bin" [/code] 4) the setup is already done! In order to try it, change to the SDCC skeleton app and compile it: [code] cd $MIOS_PATH/apps/templates/sdcc_skeleton make Best Regards, Thorsten. P.S.: if the "~/" (references your home directory) causes an issue at your side, and you don't know how to fix it, please mention the operating system under which you are working, and the path of your home directory (echo $HOME)

The new Eagle format is XML based, probably you've installed another program which expects a different content. So: store the file on your harddisk, and open it with Eagle from there. For the case that it isn't obvious: please install the latest Eagle version 6.2.0 or higher. Best Regards, Thorsten.

The new MBHP_DIO_MATRIX module combines two DIN and two DOUT registers to simplify the wiring to button/keyboard matrices. It has been mainly created for the upcoming MIDIbox KB project, therefore J3 and J4 (input/output pins) are (almost) 1:1 compatible to most Fatar keyboards. But the module is also useful for other purposes, e.g. for matrices connected to MIDIO128 or simply whenever only two DIN/DOUT shift registers are required for a project. I'm sure that the PCB will be available in SmashTV's MIDIbox Shop soon! :smile: Best Regards, Thorsten.

no problem for me (as long as somebody doesn't start to sell multiple sammichSIDs which he never built for himself...) Best Regards, Thorsten.

ok from my side. Best Regards, Thorsten.

Beam me to Detroit, Scotty! :frantics: Best Regards, Thorsten.