TK.

Die Verkablung ist ziemlich einfach und man kann dabei eigentlich nichts falsch machen. Allerdings laesst sich mit dieser Orgel-Tastatur (aus den 80er Jahren) keine Velocity realisieren, da die Tasten nur einen Schliesskontakt haben. Fuer Velocity benoetigst Du Tasten mit einem Oeffner und Schliesser. Ich beobachten schon seit Jahren keine Ebay-Auktionen mehr... wenn heute nichts brauchbares auffindbar ist, dann vielleicht naechste Woche - Geduld! ;) Genereller Tip: Wenn Du nur ein Masterkeyboard benoetigst, dann kaufe doch einfach ein fertiges, so wie dieses hier: http://www.thomann.de/de/miditech_garagekey_retoure.htm (hat allerdings nur 3 Oktaven) oder dieses: http://www.thomann.de/de/cme_mkey.htm Die komplette Elektronik ist bereits integriert, und wenn Dir das Gehaeuse nicht gefaellt, kannst Du die Tastatur ja einfach zusammen mit der Elektronik ausbauen - das kommt Dich insg. am guenstigsten. Gruss, Thorsten.

Ok, diese Tastatur kenne ich. Die Chips lassen sich nicht weiterverwenden (-> aus den Sockeln nehmen!). Die Tasten schliessen auf Masse, somit musst Du jede einzelne an das DIN Modul anschliessen. Gruss, Thorsten.

Hi, dedicated PICs for each pair of 8 motorfaders are still required, but since the PIC is part of the MBHP_MF_NG module anyhow, the complexity is low. You will only need multiple of these MBHP_MF_NG modules, they are working standalone. No core module is required. I could add the selection of a dedicated MIDI channel to the firmware, it isn't so difficult. Best Regards, Thorsten.

No, it's very likely the encoder. Just contact Wilba directly :) Best Regards, Thorsten.

Machst Du mal ein paar Fotos von der Keyboard-Platine und vor allem von den Chips? Mit etwas Glueck handelt es sich bei den Chips um 74HC165 Aequivalente, so dass Du sie direkt an das Core Modul anschliessen kannst. Falls nicht, muesstest Du die Chips entfernen und jede Taste einzeln mit dem DINX4 Modul verdrahten. Gruss, Thorsten.

See the rules in http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Finclude%2Fmakefile%2Fcommon.mk It's inspired from the the "super makefile": http://content.gpwiki.org/index.php/Make Best Regards, Thorsten.

I searched for "mbseq frontpanel", and this thread was one of the first hits: Read especially the comments from SmashTV. I think that if you ask him nicely he would tell you the current status. Best Regards, Thorsten.

Nein, aber ich finde die Tastatur zu teuer fuer das was man bekommt. In der Regel sind die Folientasten ja sehr traege... Dann doch lieber 16 Minitaster fuer 0.10 EUR pro Stueck. Gruss, Thorsten.

Do you know if the encoder is the original one delivered by Wilba? If it has been replaced by another encoder type, where (for example) the ground pin is at the middle and not at the left side, you will notice such a behaviour. The hardware has to be changed to overcome this. If you are unsure, just buy a replacement! Trigger matrix: chaining events is already possible, there is no need for multiple trigger matrices to handle this :) Best Regards, Thorsten.

Ja - allerdings ist diese Tastatur ziemlich teuer, schau Dich lieber mal bei EBay um. Gruss, Thorsten.

Ja, das parallele Scannen von Tasten gehoert sogar zur Grundkonfiguration. Du benoetigst ein MBHP_CORE_LPC17 Modul sowie zwei MBHP_DINX4 Module (fuer 64 Tasten). Die Leiterplatten gibt es hier: http://www.midibox-shop.com/buy_lvo.html Und die Bauteile kannst Du bei Reichelt bestellen: http://www.ucapps.de/mbhp/mbhp_core_lpc17_orderlist.txt http://www.ucapps.de/mbhp/mbhp_dinx4_orderlist.txt Ausserdem dann noch ein LPCXPRESSO Modul, bspw. bei Watterott: http://www.watterott.com/de/LPC1769-LPCXpresso das wars dann aber auch. :) Gruss, Thorsten.

It seems that you misunderstood me - could somebody please help to translate german english to american english? Best Regards, Thorsten.

I could add this to a wish list, but who will implement this? ;) It's nothing what could be implemented in a couple of hours without having the hardware directly available to try out how the code is working. So: somebody who owns a similar system and who has the required programming skills has to help out here. Best Regards, Thorsten.

Yes, the changes in the drum engine are standard now :) Best Regards, Thorsten.

Hallo Bernhard, sehr wahrscheinlich ist Dein Netzteil zu schwach, so dass die Spannung in die Knie geht sobald das Backlight versorgt wird (Stromaufnahme typischerweise 100..200 mA) Probiere mal ein anderes Netzteil mit mind. 500 mA Gruss, Thorsten.

I had the same issues and thought that I'm the only one (the sammichFM modification hasn't been done by me... ;) Please try this version: http://www.ucapps.de/mios/midibox_fm_v1_4d.zip Best Regards, Thorsten.

Yes, you can try this without the control surface. The configuration can be done from the MIOS Terminal as described in the ChangeLog Best Regards, Thorsten.

Mainly there are two possibilities: 1) a 1:1 emulation of the MBSEQ frontpanel. Button/Encoder events have to be sent to MBSEQ, and MBSEQ sends LED/LCD changes to Lemur. In fact I already implemented this into the MBSEQ V4 firmware two years ago to allow remote-control of a second "core-only" MBSEQ, but it's undocumented and well hidden in a configuration file ;) This mechanism could also be used to control the MBSEQ remotely from an iPad once Lemur supports SysEx messages with more than 128 bytes (this limitation should be fixed in a future update) 2) creating a completely new control surface which is optimized for the iPad, because the usage of virtual encoders is too cumbersome, and at many places you would like to control certain functions with dedicated buttons (on dedicated pages) instead of clicking through the menu pages. This is feasible as well, it could be implemented on the same way like I did for the and the implementation at the MBSEQ firmware side is easy - but creating a perfect Lemur control surface for controlling all the parameters is a challenge. If somebody with Lemur skills would like to do this, I could take over the MBSEQ firmware part. Exactly! No, this isn't possible, the HTML protocol isn't made for this, and there are no RAM resources free for a webserver anyhow. Haha, totally wrong! ;) MIDI (over USB) has the best performance, OSC is a bit slower since it requires additional string based parsing at the receiver side, and all other protocols are not compatible to MIDI synthesizers or DAWs anyhow, and would require some kind of proxy/bridge which will add latency. Best Regards, Thorsten.

Hi, yes, it should be sufficient to adapt the button and LED assignments in setup_mbseq_vintage.asm! :) Best Regards, Thorsten.

Woah! Sounds like the installation was infected by a virus! ;) Best Regards, Thorsten.

You can reach the developers here: http://www.invisionpower.com/products/board/ But I'm unsure if our license covers future major updates (I guess: not), we would have to pay for a new license. Best Regards, Thorsten.

Hi Petrolio, You could add a function which changes to the record page to seq_buttons.inc, it could look like this (untested, but hopefully working code): SEQ_BUTTON_Record ;; do nothing if button has been depressed btfsc MIOS_PARAMETER2, 0 return ;; branch to utility menu movlw CS_MENU_PAGE_RECORD goto CS_M_HLP_ChangePage [/code] This function can be referenced in SEQ_IO_TABLE_DIN of your setup_* file (e.g. you could either replace an existing button assignment, or you could assign it to an unused DIN pin if available) Thats too much work, especially since the resources of the PIC are limited (e.g. a 32bit timer will be required for high-resolution time measurements) and since the V3 firmware is programmed in assembly language. Even if somebody would spend some days (or even weeks) to downstrip the firmware and to program the enhancements for you, the result would never reach the accuracy of the V4 implementation. Best Regards, Thorsten.

Servus, da die MIDI Ports des Bootloaders bereits sichtbar sind, sieht es eigentlich ganz gut aus! :) Stell mal die Device ID wieder auf 0, und druecke dann auf den Query Button. MIOS Studio sollte nun melden, dass der LPC17 Core gefunden wurde, wechselt von "PIC" auf "LPC17", und dann kannst Du das .hex File aufladen. Gruss, Thorsten.

I'm planning to use 6 pins for the resistor network like the original TR909 design. The two remaining pins can be used for the gates. Yes, using 4 pins instead of 6 could be an option if somebody wants 16 velocity outputs instead of 10 I'm not planning to overwork the MB808 application, e.g. because of effort reasons (meanwhile programming PIC assembly is a pain in the *ss for me ;)) And I don't want to change the existing pattern structure (individual accents for each step would increase the pattern size dramatically, much less patterns could be stored than before) Therefore we will still have only a single track which enables/disables accent for all other tracks. Only difference is, that the velocity level for accented and not accented notes can be configured for each instrument. The accent levels can be controlled individually if drums are played via MIDI. The 9090 uses some S&H stages to multiplex the velocity levels. This has two disadvantages: the S&H stages have to be refreshed each mS by the firmware, this increases the CPU load. Another disadvantage: it isn't possible to set the trigger at exactly the same moment with a new velocity level - velocity would have to be set earlier, this adds an unwanted delay to the trigger. Since the original design doesn't use S&H stages as well, I prefer to go this way. I see the point... But currently I'm only planning to add a small extension to an existing project with as less effort as possible, renaming the project could give you the wrong sign that this is a new project which is open for adding much more extensions. Thats definitely not the case. ;) However, how about MIDIbox SEQ V3D Best Regards, Thorsten.

It's only a frontend which communicates bidirectionally with MBSEQ (running on a MBHP_CORE_STM32 or MBHP_CORE_LPC17) The communication can be realized via the Lemur demon (-> e.g. MBSEQ connected via USB to a PC/Mac), or directly via Ethernet - MBSEQ supports both options. I do agree, therefore I prefer to run the sequencer engine on a microcontroller instead of the iPad, because iOS can't guarantee stable timings as well, especially once the sequencer should be synchronized to an external MIDI clock. Best Regards, Thorsten.