cimo

hi snaper follow this link and read ALL of the posts in the first 2 threads about adapting your MB to your needs and design i advice you to download MB64 application and open the files main.asm and mios_table.inc : it s a good start to understand the application and the parameters and value you will need to adjust. simone

and i guarantee that mike ships PICs with the bootloader, and you won t need to use a PIC burner anymore so don t worry Snaper, if you buy from Mike you won t need a PIC burner simone

hi again then you don t need to "burn" anything to the PIC but just uploading some software and you can do that on a mac with no problems at all. Anyway a Celeron is a good companion for any occasion and will be there humming for you and warming up your house this winter and as long as you keep it plugged into the 220 socket you won t need to feed it or bring it out for a walk. Seriously, if you plan to use your MB with a Mac i d advice you to use Mac since the beginning for uploading software because you will change and adapt your MB quite often before finding the right tweak. best simone

.. be sorry for my laptop !! :'( thanks, i am browsing all those links around but i can t really find out anything about how to regulate the voltage coming from a FireWire port, i guess it s autoregulated but i can t figure out if it s hardware regulated (is it possible?) or by the driver .. .. i am interested on this because i plan to build a "selfsufficient" little portable music installation: in the beginning i am going to use a car battery but i plan to buy solar panels when i will have some spare money or fund the project somehow... i plan to supply the laptop and then get all the necessary power from the laptop down to all the controllers, i really like the "plug n play" style.. .. if you have some info about that FireWire stuff .. i ll be here around simone

Video about the IR GP sensor from Sharp in a customised MIDIbox64E ...coming in a few minutes

:) :) jidis i do totally agree about this: i am right now building a crap PC with components found on the trash.It will be in charge of running a Ubuntu for downloading purposes and Internet for guests and experiments for me. About snaper i know from our PMs that you will buy the pic together with the modules probably from Mikes Shop.The PICs coming from Mikes are aready burned with the necessary software, all the following uploading of software to the PIC you can do it with a OSX system (Tiger preferred but i do it in Panther anyway), there is a thread about this here http://www.midibox.org/forum/index.php?topic=5230.0 best simone

hi thanks doc you don t really know how stubborn i am ;-) so what i guess is that firewire offers a "variable" voltage output and that the output can be regulated ("asked") by the slave device? i don t think there will be any problem with the mainboard, i ve already shortcircuited the usb and my powerbook just get stuck and gives me a screen with the following instruction: press the power buttons for a few seconds ... :) anyway if anybody has some more infos about firewire and how to use the power coming from it .. here is your thread ... thanks simone

hi snaper the projects that you re lloking for is the MB64 because it supports analog pots/faders and has a lot of features for them english is not my language either so don t worry about language just be nice patient never pretend etc etc for 32 pots/faders you need an AIN4 of course you need 1 CORE module you ll need a 6 to 9 volts transformers (minimum 0,5 A) for 32 buttons you ll need a DIN4 1 more DIN2 to connect the jog wheel and transport buttons that s really a basic you ll need much more stuff: a convenient box, tools, etc don t worry you ll figure out yourself: i advice you to start writing down all these things so if you order anything from a shop you will have to do it only once a question: what is the display on your design? a LCD to control parameter or just a tranport controller? At the beginning of this section of the forum you will find a nice step to step guide >>> read it all // please let us know if you have any experience in electronics, there is no discrimination here about that but communication will be easier if i know what you can do what you will learn to do ;-) about the modules and where to buy it: there is a german guy who sells pre etched pcb and all the components here: http://www.mikes-elektronikseite.de/ best simone

hi snaper welcome!!! i am giving you the first steps 1 read properly the pages about MIDIbox64 and MIDIbox64e and the wiki, they are really well written 2 try to figure out what you want to build and draw a schematic, i use to start from the front panel for example so i know how many encoders, faders buttons if i want light etc 3 when you have a (+ or -) clear idea come back to this thread and we can help you to find out which modules and how many of them you need.You will probably get also some good tips about how to improve your design.Let us know also if you consider etching PCB by yourself or want to buy premade PCB with all the components good luck and welcome aboard simone

directly from Apple s web site: Power Input voltage range: 8 to 33 V Input power range: approximately 1 W Output voltage range: approximately 18 V to 24 V Output power range: up to approximately 15 W mmmm sounds different from what i ve fund out before.. does anybody know the right specification? thanks simone

hi all i ve always supplied my MBs with the usb hub, of course with the limitation of not having a lcd and with power problem from time to time. I also added lately a GP IR sensors to my modified MB64e (see my posts in this topic http://www.midibox.org/forum/index.php?topic=5270.0) but i get a lot of jittering also due to the unstable power supply (usb) I also happily switched to a powerbook g4 OSX ppc, as you might know apple always supported the FireWire protocol/connection. Usb is dominating the market so i can easily get a cheap (and very small) MIDI/usb interface and mount it on my box and have a single cable to connect to the computer and supplying the box. Now it is impossible to find such a small and cheap usb/FireWire interface but FireWire has 6 Watts of power, that at 5 volts makes 1,2 Ampers , right? i am not an electronic geek but that has to be right, please confirm if you can. usb has only 0,5 ampers not even the half of it. Here we go now: why no to use a cable with two plugs: a usb and a firewire: the usb will connect to the usb/MIDI interface transmitting and receiving MIDI and powering ONLY the usb/MIDI interface while i will use ONLY the power pins from the FireWire plug to feed the box, lcd, GP sensors and whatever can be supplied with 1,2 Ampers. In my powerbook usb hub and FireWire are so close to each other and i almost don t use the Firewire. Of course this is only of any interest for those who want a self supplied MB with straight connection to computer and you will have to carry a special cable for the box. Let me know what you think simone

hi all yes it helps a lot but i had to go all the way to 0x1e to get a good result, and with such a big value the precision is not so good but still usable. >> i have to admit that i can see the GP project clearly getting better and better every passing day thanks to you guys <<< next step will be to add a smaller 0,1 microF bypass caps in parallel with the 2200 microF, building a metal housing for the GP and clamp it to the ground, and try to place a couple of bright leds around the GP. I also had another idea about power supplies but i fear i am going out of topic not only in this post but also in the forum s section so please come to the design concept section if you are interested in Firewire and self supplied MBs i will post it there. simone

to say it all... after installing MidiPipe and having the sensor working properly i didn t even bother myself with going any forward with that.... i ve been waving my hand, my feet and even placed the sensor orizontally and danced in front of it!!! But now it s time to get serious again and i will try the MIOS_AIN_DeadBandSet(x) function.. i ll do it right now and report asap. Sorry for repeating myself but i have an unanswered question. Let s say i want to rewrite my application (custom MB64e) in C so that i can add your (Goule) gating code and Audiocommander s expanded range code, can i get all the features found on MB64E in C app.? Or , at least, can i find C code for Meta event and Group switching? txx simone

hi i am smoking my midipipe with great appreciation for this little piece of sotware!! let s say i am almost tempted to forget about all this C thing and be happy with having midipipe translating and doing all the job, anyway i am stubborn and curious by nature and will try to implement the stuff either software or hardware side. i have now a full CC range with the GP considering that a brighter enviroment will help the jittering problem i wouldn t be surprised if those smd leds you have in those ikea lamps are actually giving you a more stable value.That would be an hardware solution for the jittering problem, placing a couple of leds around each GP.But i am not sure for the moment i will try later on and write back. So here s a "temporary solution" for all those using GPs, midiOX if you re on PC and MidiPipe for OSX. simone

mmmm midipipe... sounds interesting at least i can get full CC range while i am working around a software/hardware solution thanks for the bunch of infos guys .. this forum is an amazing place !! yes i got a good result with a 2200 microfarad and light in the room now i will also try the AIN_BAND_SET function ... about the opamp yes i agree it seems to be quite difficult to find a proper opamp project for this and i can t really do it myself.. again i have to repeat myself because there is something which is not entirely clear to me: your code is in C, my application is in Assembler, you can t put C code into an Assembler application right? So first i have to rewrite my application in C eventually with Assembler in it (because that it is possible) and add your interpolation C code to use with the GP btw i have only 1 GP and 10 pots and the GP doesn t affect the pots behaviour, supplying the MB with the USB s 5 volts (no lcd) at this point i believe we/i could start a new thread about "how to implement a GP sensor into a MB application" step by step guide because i do believe there are a lot of people here wishing so saludos y abrazos de tenerife simone

yeah .. i ve found out myself (and reread the posts) that what you need is a connector :-\ .... anyway on the same touch pads i had to connect the pins of the buttons (also connected to ffc cables) to external buttons.I solved the problem the hard way and peeled some of the plastic away, soldered new cables to the ffc, some tiny shrinking hose and there you go. simone

hi sign me up for a couple of them about ffc i had the same problem with a touch pad i used for a project and i ve found out a solution i usually pick up all kind of electronic trash and i got some old vhs players, inside i ve salvaged some ribbon cables and easily cut off just the number of wires i needed and slipped the ribbon into the socket.. now i think there are different kinds and sizes of ffc but if you re lucky you can use the same trick. I have some more of those ribbon cables so if you can send me the tech data of the socket i can check if they will fit... let me know simone <<vacation is .... writing a lot of posts in the forum>>

hola los botones del menu estan conectados (como todos los demas) a uno de los modulos DIN.A cual depende de que MIDIbox estas construiendo y de toda forma lo puedes tambien eligir tu modificando el codigo. Para ver donde conectarlos tienes que descargar el software buscar el archivo main.asm y encontrar algo parecido: este ejemplo es de la MB64E simone

hi all so far stepped into C with a long list of errors as a first result ??? set up the C enviroment on virtualPC started to peer into all the C applications just to get a first glimpse picked up the 128in_64out_64pots example for its similarity to mb64 and my project added the "gate" code written by Goule got a bunch of errors i guess it is because that code is written for a specific MIDIbox and some values have to be adapted to the current project i will try to figure out myself but if anybody can point me to the right direction .. feel free!! guess what? keeping the room s light on improves the jittering problem, it actually stops it in my case to resume: 1 if i pick up the C skeleton and add the Assembler code in main.c to fit my project (11 pots, 12 encoders, 23 buttons plus 1 GP sensor) that should be it to have a functional box right? 2 what about groups and meta events ? i didn t see anything about that in the C examples, hasn t it be implemented yet or am i missing something? (my guess is that i have to put the usual xxx_meta.inc in the mios_wrapper folder and link it somehow in mios.c) 3 (for audiocommander) which portion of the code of the sensorizer is handling the bit shifting (yes i am using a word which i don t really understand ;) ) and where should i put it ? 4 drinking orange juice will help me understanding C coding ? greetings from somewhere (or better nowhere) in the middle of the atlantic ocean simone

hi tyni_ian i am up for italian and spanish translations just send me the text and i ll send them back translated simone

hi i ve sent 2 messages to goule and to audiocommander about this thread but then i realized it would be better to write in the forum.. so guys answer me PMing only about music if you need so :-) i am using those sharp sensors as well and i got the jittering down to 1 single value thanks to a capacitor (i am using a 2200 microF) between ground and Vin. The maximum CC i can get is about 80 (decimal) I ve bought sensors from farnell last year for about 15 euros i d like to insert the code to get full range on CC values and for the gating stuff in my application but i program in assembler while as far as i know that code is written in C .. is it possible to insert C code in an assembler application? or is it time to learn some C ? last year i solved the problem in another way: i used MidiOX to map the incoming midi, very easy but now i got a Powerbook and no midiox.. anyway this is a fast way at least for testing new sensors etc. if you work on PC just map the incoming (from the sensor) MIDI to get full use of the CC range. thanks simone

hi massimiliano the velocity stuff has already be implemented, browase around the forum and you ll find it about buttons i got some nice buttons from rjs electronics best regards simone

just the splash windows here from the console Exception in thread "main" java.lang.NoSuchMethodError: javax.sound.midi.MidiDevice.getTransmitters()Ljava/util/List; at org.midibox.midi.MidiDeviceRouting.devicesConnected(MidiDeviceRouting.java:375) at org.midibox.midi.MidiDeviceRouting.connectDevices(MidiDeviceRouting.java:182) at org.midibox.apps.miosstudio.MIOSStudio.connectDevices(MIOSStudio.java:261) at org.midibox.apps.miosstudio.MIOSStudio.<init>(MIOSStudio.java:121) at org.midibox.apps.miosstudio.gui.MIOSStudioGUIDriver.<init>(MIOSStudioGUIDriver.java:61) at org.midibox.apps.miosstudio.gui.MIOSStudioGUIDriver.main(MIOSStudioGUIDriver.java:233) Sep 18 16:53:10 59-33-155-85 crashdump: Started writing crash report to: /Users/simonemarin/Library/Logs/CrashReporter/Dock.crash.log Sep 18 16:53:19 59-33-155-85 crashdump: Finished writing crash report to: /Users/simonemarin/Library/Logs/CrashReporter/Dock.crash.log

java 1.4.2 and NO plumstone i can just see the splash i ll try to install plumstone now and write back

ok i ve made my way throught my new osx system and now i have all the needed tools to change/upload the application anyway i can t get my problem solved i repeat the steps i took: 1 upload a customised mb64e application 2 swap the default MB64E_META_Handler_00 with the one you (Thorsten) posted i didn t change anything else 3 re assemble main.asm and upload the application again 4 download the mk_syx, modify the midibox64e.ini for my application 5 convert to a syx file 6 upload the new syx results in midi monitor i can see that now those buttons are sending a syx and not a note but no midi channel change!! i assume that somehow the meta handler is not active questions is it possible that when i upload the new midibox64e.syx file i am overwriting the meta handler? how will the midibox "listen" to the buttons sending the F0 00 (01 02 etc) event? is it an internal process? thanks best regards simone