Lide

Thanks for that. In the meantime I had my first live-gig with this box and it worked fine! ;D ;D ;D ;D hope this box works a long time... cannot imagine working without it on ableton live anymore.

I did the case-design my own. The frontpanel (where the knobs/faders/buttons are mounted) and the backpanel (where the pcbs are mounted) i designed with frontplattendesigner and ordered from schaeffer-ag. The sidepanels are milled out of standard alumina-profiles such as sold by maytec or bosch rexroth. The panels are mounted together with brackets i made myself (simply alumina plates which are bent). You can see them mounted to the side-panel in the picture above. This work is well done with a AutoCAD Mechanical Desktop, which I use at work for constructions. 8)

yes. ;D 8) last weekend i did a jam session with my friend. The performance with this midibox is fine. Here is an additional picture of the inside of my midibox: Indeed there are more cables i expected. But i just managed it that there is no wasted space inside ;) Greettz, LIDE

thanx. tried it and seems to be cool now. 8) i´m a happy midibox owner now... ;D ;D ;D ;D ;D ;D

When i store a sysex-dump with vmidibox, change the code and upload it, and then upload the sysex stored before, will this overwrite the changed debounce settings?

so when i change the debounce counter value it won´t be overwritten from the new syx upload?

And an additional question: Now that i have configured all my pot and button modes, is it possible to change the change the code, upload the new syx file without losing that configuration?

Hi out there! Here you finally can get a picture of my new live-controller! Works fine so far. So I want to thand all guys helping me to get along with this! THX!!! There is one Problem left with my MB: sometimes i press a button and LIVE does not respond on it and i have to push a second or maybe more times. It seems to be irregular. Could this be because i set the debounce counter to 0? Greetz, LIDE

Ok ;D After testing several connections of the DIN and changing some app-code I got my encoders work now. Thanx a thousand times for helping!!! Next I will do is mount all modules in my midibox and link them together. So I´m waiting for my front- and backpanel... 8)

Hi, I´m sorry. Maybe a few words about my complete Midibox-Setup are helpful for further discussions: I want to have a MB64(ID00)+MB64E(ID01) linked together in one box with 71 buttons (64 of them with leds), 44 pots, 9 faders and 2 encoders for controling ableton live. The pots and faders (=2xAINX4), the 64 buttons with the leds (=2xDINX4 & 2xDOUT) and the LCD should be connected to the MB64-core (ID00) . This core is the Midibox Link EP. The other 7 buttons (including the menu buttons) and the 2 encoders are connected to one DINX4 which is connected to MB64E-core (ID01) as Midibox Link FP. But since i don´t have my front- and backpanel yet (DHL sucks :( ) I wanted to test the pots/enc on the supposed cores before connecting&linking all together. The pots seem to work now on MB64-core - after having some grounding problems. Enc still does not work properly on the MB64E-core (see above). So will it work if i connect the DINX4 to J9@MB64E-core and connecting the 7 buttons to J3 & J4 @DINX4 and the encoders to J5 @DINX4 without changing the MB64E-app-code OR what will I have to change if it does not? Sorry for my wack skillz in coding and electronics... Thanks again.

Thanks for the hint. Although I´m a little bit confused right now. In the mios_tables.inc I changed the mode to detend encoders. But at the core-page i read that the DIN with encoders has to be connected to core´s J6 when using MB16e. Is this also right for MB64e? Maybe then my former configuration was wrong, because I connected the DIN module with encoders to J9 of the core-module. However, I changed it and connected the DIN with encoders to J6 of the core and now i cannot get any midi signal out of core... ???

hi, you mean i only have to connect the encoder and it got to work without configurations in the mb64e-app? no parameters to set? i found that picture about the different encoder modes (http://www.ucapps.de/mios/mios_encoder_modes.gif). they work without telling the software which type is connected? and how does the app "know" if there´s a button or an encoder connected? or is this not necessary? greetz, lide

thanx! i tried several times and it worked after uploading mios with mios-studio. then i uploaded the change_id-app and it worked! after that i tried to upload the mb64/mb64e-apps to the cores. it didn´t work with the vmidibox-editors, but with sysexbox. :D

hi all, today i tested my mb64e-core module with a connected din, which has a alps ec11b 20 detend encoder connected. i want to use this to scroll up and down the scenes in ableton live. for this i need two different midi-notes: one note at a click when i turn the encoder to left and another when i turn the encoder to right. i tried it with my configuration but the midi monitor showed, that there are sent 0 and 127 both on two channels (think it was 8 and 9) by one click. does the logical algorithm not work with these encoders? can i use them at all? i think this could be fixed by changing some parameters, but after searching in the mb64e-app-code, i´m really frustrated, because i couldn´t find anything where i see which encoder type has to be selected or what i can change to make this thing work. :'( so anyone who has more skillz in programming and electronic, who can show me the way into the light? thanx&greetz, lide

hi, it seems to be grounding problem. i asked a friend of me to look at it and with the scope he measured peaks on ground signal. so i had to much crossings from board to board. he said the most important is to make circuits always starlike and as short as possible. since i don´t have my front and back panels yet, i connot go on further. this was only for testing if the software works properly. it seems to. i think on thursday i´ll get my front- and backpanel, so i can mount the stuff together as it should be and then have a second look on it. i´ll post here again then if it´s better than work i´ve done before :-[ so far i thank you all again very much for assistance. greetz, lide.

Ok, i measured the following: - pot on pin 1 at ain, pin 2-16 in ground: pot voltage ranges from 0,75V (left) to 5,8 (right) while the display starts to react at 3,4V to increase the value from 0 to 118 (5,75V/right). Turning to the middle i measure about 2,6V. The pot shows a print on the housing that says "10k A". - connecting the pot to pin 16: voltages are the same, display reacts at about 3,8V (0) increasing to 116 (5,75V). Sorry that i´m not that familiar with electronics/programming and detailed in my descriptions. But thanks very much for your time!

yes i think so. and the 5V are on the ain module as supposed. if i change the left and the right pin (vcc and ground) on the pot it should be the same with the difference that the value is decreasing while turning the pot to right, correct? will try this tomorrow. if i measure the voltage between the middle pin and the left or right pin when connected to ain, what voltage-range should be there if i turn the pot from min to max? i will check my hardware tomorrow, because i don´t have it at home right now. thanks for help so far moebius

hi, yesterday i read the main.asm of mb64-app carefully and couldn´t find anything which aims to be the function/parameter to adjust to solve this one. i also read the function-reference without success... anyone help? i really want to finish my midibox this week. :'( greetz, lide

Hi all, i´m really going into the end-phase of building my mb64+mb64e midibox for live. i decided to build 2 cores (1 for mb64 and 1 for mb64e). i´ll post the design as soon as i have my frontpanel and mounted everything together. so long i have only one problem with the pot range (see this thread: http://www.midibox.org/forum/index.php?topic=5593.0 ) If anyone could help me with that issue, i would be really grateful greetz, lide

hi thorsten, i currently have connected one ain-module to one core and only one pot to the ain. the other free ain-pins are connected to ground. mios and mb64-app running on the pic. the problem with live is solved... i forgot to activate the remote for midi-in-port:-[. but the pot-behaviour is still the same. if i turn the pot from left to right, the parameters on the display reach max (127) at half of the complete pot range (mid pos.). i got no idea which changes i have to make in main.asm. maybe i didn´t read carefully enough...

ok. i already got it! :) but now that i have contacted one pot to ain it seems that only one half of the pot range is controling the whole parameters 0-127. i think this is software prob. Can i change a parameter in virtual midibox to solve this problem? and i wanted to test controling ableton live with this pot. i couldn´t assign the pot to any virtual pot/fader in live with the midi learn function of live. why? my midi-led shows that there is signal coming in to my pc and live. mmmhh.... strange this. would be nice to get help from you guys... ??? :(

Hi there, after i got my mios on the pic, i try to upload the mb64/mb64e to the cores i want to use (one for mb64, one for mb64e) with the virtual-midibox-gui. But I don´t know if it did work. Do i have to connect all my din, dout and ain modules to the core before i make the upload? how can i test my hardware and see if the dump did work? thx & greetz, lide

I forgot an additional question: can i upload/debug the m64/mb64e-app. with mios-software? what alternatives do i have for that? greetz, lide

ok - thx very much so far. But do i have ot upload the mb64/mb64e-app too, or is it enough to upload only mios-software and then do the change_id thing? what is meant by "upload this project"? do i have to upload the unmodified change_id-app before i can modify and upload it again? And: Can i upload the modiified with for example mplab without losing the ability to make further uploads/code-changes with midi-connection in future? (Or: do i loose the bootloader, if i use mplab-burner?) sorry for my non-understanding. :-[

Hi all, i have to change the id of one of my pics. after searching i found the change_id app. the main.asm says the required steps to do this are: My question is: what is meant by "upload mios" and "upload this project"? Do i have to put the mios-software on the pic via midi, before i change the id with this app? My pics currently only have the bootloader on it. And one general question (sorry - newbie=me): i´m building a midibox with 2 cores. one core should act like mb64 and the other like mb64e. do i need different mios versions for this? So far i don´t fully understand the context/relationship between the mios software and the mb64/mb64e software? Is it the same? Do i have to set different parameters in mios so that it acts like mb64 or mb64e? thanks for your replies & helping me.