superdavies

Hi your photos are really interesting! Just few questions: is it a clone or is it a real tonewheel? touchscreen is a really good idea! it seems to me like a sort of controller for a software synth like the NI b4 isn't? If is a real tonewheel, maybe you can solve some problem I got...basically one...HOW? 8) Thank you very much, i really would like to know everything about your organ... Bye Andrea

Done Very easy, just useful knowing midi messages ( just learned) . It works!!! Andrea Thank you very much!!!

Yes, it's true, in fact it need upper manual on channel 1 and lower on 2: but the question is this, how to con figure the midio for send the note on-off on channel 1 for the first 64 contacts and on channel 2 for the other 64? Thank you very much! Andrea

Hi Midiboxers! I have a little problem with the conf. of my midio. Connected to a Pc running B4 of Native instruments I can't be able to drive the two manuals of the organ because the 128 midimessages generated by the midio works only in the first manual: How can I configure it for working also in the second manual? Thank you very much! Andrea

Ok Now I know what "Robinfawell" means...it's you! Hi!!! Thank you for your link, very interesting; I really don't want choose between lightweight and sound of an hammond organ! I perfectly know that if I want a portable one I got to choose one of the 100 clones in the market but if a what "THE SOUND" I need the original. My proposal is only for the fun of the project, I really don't need it for doing something or for playing in a band or so on: It's an idea, the midification of a hammond organ! I don't what to synthetize the toneweels, I want only to get rid of the classical hammond controllers (keyboards, drawbars, persussion buttons, reverber buttons ecc ) and to midifying all these controllers so the Hammond itself will look like a "box" with no user interface, only the midi connectors for drive it with a midi keyboard, a sequencers, a "midibox". Ex: connect a midikeyboard to my "Hammondbox" and I start moving many pots: this pots send midimessages to my hammondbox that can read them and retransform them in a pots movements so the hammond can read as a drawbars movement. Hope to be more clear this way! ;) Thank you very much! Superdavies

Thank you very much! ;) Only a thing: I really don't know what "robinfawell" mean...can you please be more specific? Just in these days i'm thinking about my project, write down somethings, make some schematics...but it's very hard! :-\ Just waiting for other suggestion... bye Andrea

Hi Midiboxers!!! :D Here's my question. Really want to know best choice between the two for mhy project: Here it is. One core running midio128 for the midification of two manuals and other core running mb64 for the controller section; I will use the project for control the NI B4. I think I have two way: first is to link the two in a multicore enviroment, second is to plug the two in a midimerge for having only one midi out to connect to the pc running the software. What's the best choice, in performance, latency, ecc? For the miboxlink, do I need to rewrite the application? Thank you very very much!!! Superdavies

Hi everybody Just a simple question: I'm building a midio128 and i'm connecting the 4 dinx4 module together for having the 128 digital imput (normal midification of a double keyboard). In the page of the din module I find this in the part that talk about the components and I can't understand: "If you are using the DIN module with a MIDIO128, you maybe want to drive the pins "high-active" (which means: +5V = on, 0V = off). In this case please solder the two red isolated cables not to 5V, but to 0V (Vss), so that the resistors act as pull-downs" What does it means? Where are the two red isolated cables? I see the schematics for connecting 32 buttons on a din, what's the difference in this new configuration? Thank you in advance!!! Andrea

Hi to everyone This idea is really mad me crazy! I have an old hammond m3 and I have a lot of hammond stuff like keyboards, drawbars, tone generators ecc That's my proposal and question for you: I would like to build some kind of "Hammond expander"...the main parts of the sound generation of hammond (tonewheels, filters and so on ) made in a custon enclosure (very heavy, I think) and the controller section of the organ (keyboards, drawbard, presets, percussions and so on ) made in a custon lightweight keyboard; the two are connected via midi. As you can understand it is possible to control the tone generator part with a sequencer and use it like a real expander, or you can connect another keyboard to the expander midi in for pilote it... Maybe it is also a good idea for made it more transportable. What do you think, is it possible to do? I really know that for the manuals there's no problem but maybe is a little bit difficult for the drawbars and other controller...Suggestions, can anyone tell me the right way to do it or maybe there's someone that have just done? For the keyboarf part is easy with midio or midibox 64, but for the tone generator part, how to do? Thank you very much!!! Andrea

Grazie ad entrambi per i consigli. Devo dire che, contrariamente a quanto vivamente consigliato, mi trovo decisamente meglio con l'asm che con il c! sarà forse per il fatto che le modifiche che devo apportare sono basilari comunque...meglio così! Stasera faccio qualche tentativo poi vi faccio sapere...intanto grazie di cuore! Andrea

Hi Thank you very much for your help. Ok, after all, see some light! In hte mios-download section there are two ain64_din128_dout128...one coded in C one coded in ASM, since now I only used the one coded in C but doesn't matter, let's try use the one you suggested me coded in asm! Now I try to do as you told me, this evening I'll return to you with my results! Thank you very, very much!!! Andrea

Buongiorno a tutti Ho da qualche settimana finito di realizzare il mio primo progetto midibox, basato su midibox64. Con mia somma gioia, una volta finito l'assemblaggio di tutti i componenti (AIN, DIN ecc) pe realizzare il mio progetto, creo un primo prototipo con numero x di potenziometri numero x di pulsanti e numero x di led, un lcd, solo per vedere se tutto funziona: gli carico dentro l'applicazione ufficiale del midibox64 e tutto magicamente funziona!!! Fino a qui tutto bene, però ho saltato piè pari tuta la sezione dedicata alle applicazioni "user"...il problema sta proprio qui! Il mio midibox (nella mia idea iniziale ) delve essere configurato per avere 40 potenziometri, 20 pulsanti e 20 led, nessun banksticks, nessun lcd ( che comunque possiedovisto che ne era vivamente raccomandato l'inserimento). Comincio a documentarmi, leggo e rileggo tutto ciò che si può leggere sulla programmazione in C, il mios, gli esempi, scarico i file per convertire ciò che si modifica, navigo all'interno degli zips delle applicazioni skeleton o quelle già sviluppate...insomma mi faccio letteralmente il C...!!! Credetemi, ancora ora non ci ho capito quasi nulla!!! OK, nel mio caso la cosa migliore è prendere una applicazione già fatta (tipo ain64_din128_dout128_v1_3.zip ) modificarla e poi ricaricarla dentro al mio midibox...ma come si fa? Complice l'inglese (che mastico, ma probabilmente non abbastanza) mi trovo infangato di brutto!!! Qualcuno se la sente di darmi quelle 2 o tre dritte utili ad andarne fuori? Grazie a tutti!!! Andrea

Hi Thank you very much for your interesrt and your help! I really want to understand!!! I red all the links but I still can't understand...maybe is a good thing to point me at the first step with an example. Ok, I tell you the things I understand: mios user application need to be coded in C or ASM, in our case we use C; We have two possibilities ,(in my case) use the skeleton or use and existing apps and modify it. Let's try the second because I think it's the best for me! As I need only 40 pots, 20 buttons and 20 leds and I don't need ant banksticks or LCD (but I have one ) maybe best thing is to use ain64_din128_dout128_v1_3.zip. I have it, and in my opinion I need to modify such files that is in this zip...but I have main.c,main.h, cmios.h which one I need to modify? I already have the activeperl, gputils, sdcc ecc but I really don't know how to handled with them. ??? Can plese explain, in my needing, how to do this? Thank you very much! Andrea

Hi to everyone Few months ago I started my midbox project, a very, very simple one. Apart for the electronic part of the project that is really good explaned with schematics, photos, suggestion and so on, the "software" part of the site, in my opinion is not as equal! Let me explain: I'm not very familiar with software development, but i'm quite a person in a good understanding feeling, as for electronics or mechanics and other things, just a brief study and I can understand all. I wrote a couple of message in the forum tryin' to have some advice for the writing of my first application, how to do and so on, I red and studied ALL the midibox.org, uCApps.de, and the forum too but I still can't understand the right way to change (or create ) my own apps. I need a very simple configuration for my midibox: 40 pots, 20 buttons, 20 leds, no lCD, no banksticks a simple midicontroller for use with softsynth softwares: so I thought that a good starting point may be the ain64_din128_dout128_v1_3.zip for the reason That I need only to reduce the number of pots, buttons and leds. I downloades the zip, I downloaded also activepearl, sdcc ecc ecc, i red the example, I downloaded also other apps, navigate thru the zips, open the files, studied them, tryin' to use the software but still can't understand!!! I don't think I'm stupid!!! But i'm really feel so!!! :o 1) Can anyone can explain me step by step how to modify an application (in C)? 2) Suggestion!!! Starting thinking that maybe I'm not the only one with this problem, what do you think about making a possible upgrade for the site-part that talking about the apps? Maybe it's a good idea to make some kind of tutorial , step by step for people that is "stupid" as me? I promise that, if anyone can make me understand, I made it for the entire community!!! ;) Excuse me for the long message but this is what I honestly think: uCApps.de is really GREAT, well done, lot of examples and so on, but the weak point is the expanation for the making of new applications...I wrote this one for trying to contribute! :) Is there anyone that want to take my hand and explain the first steps? Maybe this is useful for other people! Thank you very much! Andrea from Italy

Hi everyone I've just finished the building of my midibox. it is very simple: 1 core, 1 ain with 8 pots, 1 din with 10 buttons, a dout with 6 leds. I load into the pic the mios and the ain64_din128_dout128_v2_0.zip application also if I have less than 64/128/128 items. Ok, it works! It send midi message (test with miosstudio) and seems fine. My next step is to write down and appropiate application: I Think I have to use C language, but, i think maybe there's another way...I tryed serge midibox64 editor but, when I try to assign different event, I can't understand the way to put them in to the pic for return to me even after I shout off the midibox (I don't have banksticks!!!). The fact is that I need a simple controller to control software like b4 and the buttons now only send note on message, instead I want them to send other control message...How to do? Second question is how can I set the led? I know they work (because when I turn on the midibox, they flash ) but how can I assign them to features I want? Thank you very much Andrea

Hi to everyone I'm starting a new midibox project based on this idea: midifying 2 keyboard and make some controller to control a VST instrument. I've bought all the stuff and i've just build them. My question is about the exact procedure for linkin'g the two cores, first of midio128 (for keyboards) and second of midibox64 (for controllers). I've read the Midibox link page and I think I have to made midibox64 the master and midio 128 the slave: what about the power supply? I have to use J2 or I have to power up the two using J1? what components I have to remove? I have to plug also an Ltc and LCD module...where? In the midio or in the midibox? Is it possible to find somewhere a little example about the thing I'm tryin'to do ( I really don't think I'm the first to do this) the right procedure for linking only two cores? Second question. After the work is done I need to have 3 midi connector on the rear of my controller:2 Midi in, midi out and midi thru: The midi in is the one of the midibox and it is free, the midi out of the midibox isn't free because is connected to the PC running the VST instrument, the midi out of the PC running the VST is free: What to do? Where I must plug another midi controller if I'm in need? Can I plug it in the midi in of midibox or it's better in an eventual midi in in the PC running the VST? Where to put a midi merge to have 2 midi in? After or Before midibox? And what about midi thru? Excuse me for my question, maybe stupid, but I'm not very familiar to midi, but I WANT understand!!! Thank you very much!!! Superdavies

Hi Everyone I recently bought some parts to start my midibox project based to midibox64 (for the controller section) and midio128 (for make a non midi keyboard working with the controller ). I have a question, how can I make the two work together for control a thing like a VST instrument? How can I connect them together and what is the right procedure? I have read all about midi merge but I can't understand what a have to do? Thank you in advance! Superdavies