TK.

Hi, no this GLCD isn't natively supported by MIOS, since it's a low-performance display and therefore not sufficient for a MIDI realtime system. It could work with a second core module if it only has to listen to the MIDI stream (-> could be used as MIDIbox LC display). A custom display driver (LCD type #7) would be required anyhow, it has to be plugged into the MBLC application - nobody has implemented a driver for the HD61830 yet Best Regards, Thorsten.

This time I'm searching for potential crash test dummies who own at least a ready-built MIOS core, LCD, MF module (motorfader(s), DIN module (buttons) Best Regards, Thorsten.

Hi Olivier, MIDIO128 will be ported to MIOS very soon, this means that you will be able to add up to 64 analog inputs beside of the 128 inputs and 128 outputs very easily. Also a cascadable AOUT module with n * 8 channels and 12 bit resolution is in the queue for the MBHP (release date: unknown ;-)). You possibly have to program the application by yourself (based on the MIOS drivers) or to find somebody who plans to realize the same like you. I'm not able to tell you how it has to be programmed exactly (it's also a question of time... and I don't own such a hardware for testing), but I could give some proposals. Reg. the implementation of aftertouch and velocity: see this posting http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1057976738 which contains some superb informations Best Regards, Thorsten. FAQMARKER

128 inputs. With 64 buttons you've 64 remaining inputs for up to 32 rotary encoders. Best Regards, Thorsten.

Wenn Du den Grundsatz "Strom nimmt immer den Weg des geringsten Widerstandes" beachtest, geht es auch noch einfacher: [tt] . . ____ . Taster --- Masse |----|____|---*-------o | o----> +5V . . 10k | . . . . o AIN Pin [/tt] Wenn der Taster geoeffnet ist, fliesst der Strom ueber den 10k Widerstand. Die Spannung am AIN pin betraegt 0V Wenn der Taster geschlossen wird, fliesst der Strom ueber den Taster, die Spannung am AIN pin betraegt somit +5V Gruss, Thorsten. P.S.: diese vereinfachte Rechnung ist nur dann erlaubt, wenn die Impedanz am AIN Pin so gross ist, dass sie fuer die restliche Schaltung keine Belastung darstellt. Das ist hier der Fall...

Two things have gone wrong: 1) the "-os_upload" flag should never be used to convert a .hex file of a MIOS application, it seems that your MIDIbox SID directory doesn't contain a consistent project anymore. I don't know which changes you made exactly, but anything was wrong. So my suggestion: download the release again from my website, unpack it into a seperate (!) directory and do exactly the changes which are required and nothing else. Convert the .hex file within the release directory. 2) of course, when uploading an application you've to set the correct MIOS device ID (hex2syx.pl -device_id 0x.. main.hex), the core will ignore all SysEx strings which don't contain its device ID. So, use the script in the following way: d:\perl\bin\perl hex2syx.pl main0 .hex -device_id 0x00 d:\perl\bin\perl hex2syx.pl main1 .hex -device_id 0x01 d:\perl\bin\perl hex2syx.pl main2 .hex -device_id 0x02 d:\perl\bin\perl hex2syx.pl main3 .hex -device_id 0x03 Hope this helps :) Best Regards, Thorsten.

Yes - but this was also possible with the PIC16F based version. The new feature is, that all these 128 parameters can be received independent from the selected page, the PIC16F was only able to receive the 16 parameters of the selected "subbank". In fact this means that 128 virtual knobs are available, and it depends on your hardware how much can be controlled without switching to another page. With 16 encoders I highly recomment 8 additional buttons which should be assigned to the "Select Page" function, so that you can quickly change between the different views. Best Regards, Thorsten.

Sure! :) Excerpt from the ChangeLog o biggest improvement: MIDIbox64E can handle with up to 64 rotary encoders and LEDrings! o all 128 encoder and 64 button entries stored in a bank can be updated by incoming MIDI events o the previous "subbank" mechanism which divided the 128 encoder entries into 8 "banks within banks" has been renamed to "pages" The width of a page is free definable. This means, that all 128 encoder entries can be controlled by MB64E with a single encoder (low-cost solution) as well as with up to 64 encoders! Best Regards, Thorsten.

If anybody has already built a MIOS based MIDIbox with at least one rotary encoder + 8 buttons + a LCD and would like to beta-test the MB64E application, just drop me a mail: tk@midibox.org Best Regards, Thorsten.

Hallo Kay, fuer 64 Buttons benoetigst Du 2 DINX4 Mddule, ansonsten ist alles korrekt. Gruss, Thorsten.

Thanks for the feedback, Steve! Btw.: did you already try the ALPS encoder I sent you? :) Best Regards, Thorsten.

Hi Dan, You will find an enhanced AIN handler for MIDIbox SID here: http://www.ucapps.de/tmp/sid_ain_enhanced.zip it allows you to assign up to 64 pots to any menu parameter, It would be nice, if you could write a short tutorial, how to integrate this driver into the SID application (see the file header) and how to customize the setup Best Regards, Thorsten. P.S.: hope it works... it was a quick hack based on the code of cs_menu_enc.inc ;-)

Hi Erik, most is correct, there are two different device IDs which might confuse you: the MIOS device ID, used to address OS specific SysEx commands, and the SID device ID, used to address application specific SysEx commands. There is only one error in your enumeration - Step Three: the midibox_sid_v1_5b_8580.hex is a preassembled hex file for the PIC16F based version, but you need the PIC18F version which comes together with the source code and can be downloaded from Concepts->MIOS->Download Best Regards, Thorsten. P.S.: this shows again that I have to remove the PIC16F stuff from the main pages as soon as possible, independent from nostalgic feelings... :-/ Because of the detailed step-by-step guide: FAQMARKER

Did you take the different pinning of the 2n3904 into account? Best Regards, Thorsten.

You don't need a seperate voltage regulator, the backlight output of the core module already provides a current-limiter (leads to a lower voltage level) Best Regards, Thorsten.

You mean a "radiobutton" function. Something like this can be realized by using Meta events (MIDIbox64, 64E, MF, NG) - requires programming skills. It's also already used by more specific applications like MIDIbox LC and MIDIbox SID. Best Regards, Thorsten.

I'll definitely also build such a module based on your plans. :) Best Regards, Thorsten.

Hallo, ja, mit MIOS ist das moeglich. Die MB64 Datenstruktur sieht jedoch nur 64 frei konfigurierbare Buttons vor. Eine Erweiterung ist nicht geplant, um sie mit der alten PIC16F Version kompatibel zu halten (jede Aenderung in der Datenstruktur kostet mich schweineviel Aufwand bei der Pflege der Applikation, des mk_syx Scripts und des vmidibox Editors!) Falls Du also mehr Buttons anschliessen moechtest, muesstest Du entweder auf die MIDIbox NG warten (siehe News -> MIDIbox Roadmap), oder den Button Handler in mb_din.inc erweitern. Wie Du dort siehst, verzweigt er nur dann in das MB64 Modul, wenn einer der ersten 64 Buttons gedrueckt wurde. Ansonsten macht er weiter - und hier koenntest Du bspw. einen selbstgebastelten Handler einbinden, der auf die restlichen Buttons reagiert. Gruss, Thorsten.

Hallo Kay, wie soll Deine Box denn spaeter mal aussehen? Ein LCD benoetigst Du bspw. nur dann, wenn Du die Box standalone - ohne PC - programmieren moechtest, oder wenn die Poti- und Buttonwerte angezeigt werden sollen. Falls Du also Geld sparen moechtest, dann verzichte einfach auf das Display (andererseits ist das Display auch eine wertvolle Debugginghilfe). 1a) jep - das Core Modul muss mit einem PIC18F452 und einem 10 MHz Quarz bestueckt werden 1b) siehe oben 1c) an ein AIN modul kannst Du jeweils 32 potis anschliessen, Du benoetigst also 2 AIN module 1d) an ein DIN modul kannst Du jeweils 32 Taster anschliessen, Du benoetigst also 3 DIN Module 1e) Du moechtest keine LEDs einbauen, also benoetigst Du kein DOUT modul 1f) einen BankStick benoetigst Du nur dann, wenn Dir die interne Bank nicht ausreicht. Pro BankStick stehen Dir bei der MB64 16 weitere Baenke zur Verfuegung 2) klaro, siehe auch die Concepts->MIOS->Bootstrap Loader 3) nicht unbedingt, Du kannst Dir den Bootstrap Loader bspw. auch von jemanden in den PIC brennen lassen, der bereits einen JDM besitzt (einfach Mail an mich, kostet Dich lediglich das Rueckporto). MIOS und die Applikation kannst Du dann spaeter selbst via MIDI einladen und updaten Gruss, Thorsten.

No, this requires a special programmer and special software --- and the LVP allocates pin RB3 so that it cannot be used by the firmware. Best Regards, Thorsten.

Please wait until the application has been released... ;-) Best Regards, Thorsten.

This information is embedded in the .hex file, so that the programmer should regognize it automatically. However, here a snapshot with the config settings which are valid for every PIC16F based MIDIbox project: Best Regards, Thorsten.

Btw.: with the MIOS based MIDIbox64 this can be realized by swapping the Min and Max value. This means: when you set the min value to 127 and the max value to 0, the fader value will change in the reverse direction. This feature is not provided by the PIC16F based version. Best Regards, Thorsten.

A very nice presentation and impressing sounds of your upcoming baby! :) I remember AXS very well, this was one of the first virtual synths I tried in the 90s. Due to lack of multitasking capabilities under DOS I sampled the sounds and loaded them into Fasttracker II - an intricate workflow, but it worked. In the meantime I prefer the full integration of a virtual synth into the sequencer (for a simplified automation), or - like you - a synth with it's own control surface for best ergonomic use (-> MIDIbox SID of course :-)). Best Regards, Thorsten. P.S.: Disc space isn't an issue on the midibox.org server, so just send the files to Ian. The realization and the sources of such a project is a great inspiration source.

Hallo, ja, in Deinem Fall sind es dann 256 Events. Mit dem Jogwheel kann man eigentlich ganz fix durch die Liste scrollen, Buttons zur direkten Anwahl einer Seite werden derzeit nicht unterstuetzt, werde ich aber evtl. bei der naechsten Release beruecksichtigen. Gruss, Thorsten.