Digispunk

well, i got some initial success using Miditrix and Mdi yoke, i say initial, since i could upload Pot values without error, but the new button values dont update... need to investigate thanks TK.

thanks, TK, im definitely using the 18f version of Serge's editor, but i will try the Miditrix app to see if it improves sysex handling.

made some progress - decided to start from scratch and reload MIOS - found that the MIDI in port cable was dodgey - so corrected it successfully uploaded MIOS ver.9f to core successfully uploaded Midibox64 app - ver 2.4 all pots, buttons, faders etc work, LCD displays all correctly and tested MIDI out with Ableton and it works fine - now back to Serge's MIDI editor - try to upload new bank via sysex and get this reply "MIDI time out! Whats up???". serge editor displays problem/error messages when uploading searched and found a similar problem here - http://www.midibox.org/forum/index.php/topic,10877.msg94380.html#msg94380 was hoping to find the answer - but it seems that Foona manged to overcome the problem by switching to a new computer and MIDI interface - which is odd as he could upload MIOS/Midibox64 app etc without problem but got the time out error using serge - any ideas besides switching to a new computer and Midi interface? i am using M-Audio UNO midi interface after a short rest, i gave it another go with the same Midi interface etc, strangely the upload from serge to core worked a bit - i say a bit because the dump was registered on the core as successful, and the pots i re-labeled in serge worked, but the buttons didnt, not sure why. anyhow after a few more attempts, it stopped working altogether and went back to the 'midi time out' messages i have tried adjusting the 'delay between sysex blocks' time but that doesn't help.... i will try again tomorrow.

sorry if it wasnt clear - but i have uploaded the midibox application :) all the pots and buttons work, the lcd shows the values etc and when it boots up - so yes MB64 app is installed, and midi monitor app on the computer shows it is sending the correct midi messages i just dont know the procedure for uploading a bank/patch to the unit with serge's editor, and i cant manually edit the box through hardware because the buttons arent programmed with the menu functions (they are all midi note messages)

Hi everyone i'm trying to upload/send a new Midibox64 bank/preset using Serge's Midibox64 editor, i've made the patch with all the desired button/pot commands, and saved the sysex file for future reference, now the problem is - how to upload to my midibox? i've tried using the 'send sysex' button and the dialogue box says its sending, but my midibox does not acknowledge the incoming data. does the midibox need to be in a special mode to recieve the dump? if so my problem is that none of the buttons are currently progrmmed to navigate the menu structure. for troubleshooting info - im using MIOS 1.9 i have the midi in/out device set properly - tested and checked using Midi OX and also by way of learn commands so i dont think thats the issue i dont have a bankstick attached yet are there any detailed tutorials for uploading banks? i tried using the search terms 'serge / midibox64 editor / upload bank etc and not found one yet.

stryd - you are stuck on repeat! stryd - you are stuck on repeat! stryd - you are stuck on repeat! ;0)

Styrd - im sure you mean well, because you have helped loads of other people on this forum, but no - i dont think you have the exact answer im looking for, i think you would have told me by now, anyhow - there are lots of others on this forum who might be able to help me solve it with a bit of trial and error

Hi stryd - if you are refering to this post - http://www.midibox.org/forum/index.php/topic,13207.msg113303.html#msg113303 then yes - its mentioned in your answer, but you didn't point me to the specific part of the code to be modified, and thats what im looking for - the fastest route to the exact solution, the point is - if someone has actually done what im trying to do, and succeeded - i would like to hear from them, exactly how to do it - thats the ideal situation - dont you think? anyhow - i have been searching, and that piece of code seems like the most likely suspect, so im looking for confirmation - can you confirm that is exactly whay i need to modify and incorporate into the application?

ive been checking out the Mios C page and found this - http://www.ucapps.de/mios_c_send_range.html Send CC Events on pot movements within specific range (Scaling) looks like that might be what im looking for, if im not mistaken, it can specify which AIN input is to be scaled - with defined input and output amounts - am i ont he right track here?

Hi Guys, here's the story so far - boards are done, components have been amassed, core tested and working, metal work is done, and getting ready to do the soldering this week. this one is going to be loaded with everything from pots and faders to joysticks and touch strips. there's a space on the upper left for pitch bend and mod wheels, im using a pair i hacked off an alesis photon, and have been puzzling over the midibox software for the correct way to scale the analogue inputs to work at full range - if anyone can anyone point me to the correct part of the code to modify, i should be able to do the maths to set the exact amounts needed. i have a friend who can program and assemble, but he asked me to see if anyone has done this before to avoid the trial and error process. more pix coming soon...... :D

Hi, i posted a question about Pitch and Mod wheels in the parts section, and have been nudged towards the software side in search of solutions - the problem goes like this - i have pitch and modwheels mounted in housing that can only turn the pots the usual 90 degrees - but the pots themselves are capable of 270 degree rotation - the pitch wheel pot is 5k and moves 45 degrees either side of the central axis - which rests at the 180 degree point the mod wheel pot is 10k and moves 90 degrees from 0-90 i am guessing that the MIDIBox ASM file can be modified to interpret the limited turning range of the pots, and map them onto the full resolution of MIDI paramaters, has anyone had a similar experience and found a working solution through software? or if its not possible through software how about a hardware solution? cheers Digi

Hi Stryd, do you mean that i can modify the Midibox ASM code to work with the limited range of the pots as they are? cheers

I managed to get hold of a pitch bend and mod wheel set from Alesis, they are the ones found in the Photon midi keyboard. i got the housing/mounting frame as well which is going to make it much easier to fit into mu Midibox project. the thing is - the Mod wheel pot is 10k, and the pitch bend wheel is 5k. The thing is - they both have limited mechanical rotation due to the design of the housing, but the pots are capable of a full 270 degree turn, like standard pots. does anyone know if i can use these with the Midibox64 software and get the full range of use - i.e. Pots with limited mechanical turn producing full 0-127 Midi CC values - or do i have to make some changes to the hardware or software? cheers Digispunk

;D thats a very sexy midi object - congratulations

I will tripple check the soldering and report back, anyone got any ideas about the Sharp LCD pinouts? ???

Hi EVRYONE, first good news is that i have got the sidsynth up and running, making bleeps and responding to midi and also the SID control VST - thanks for the help with this. Now i am stuck on the LCD, i am currently trying the 2x40 LCD fro voti, afaik - all the pins are correct, during initial power on all the black bars light, then slowly they disapear and it goes blank. When i twist the contrast pot to adjust - it sometimes shows the black bars again - before disapearing quite rapidly. so i never get the black blocks for long, and i dont get any proper display - considering that my SIDsynth works great. i also got the backlight working fine - any ideas on what might be wrong - apart from the pins? might it be a particular pin assignment? or something different? the other querry is the SHARP LM40X21B - its another 2x40 lcd in blue - i have searched all over the web looking for datasheets and found many, but none have the pin assignments - has anybody used this lcd or the normal yellow/green LM40X21? it has two rows of eight pins - ? thanks for helpz Digi

NIce work Shum, and thanks for the help - good luck with the rest of the project! :) :) :)

:) - i just read this with great interest - , as mentioned before - i am no success uploading regardless of the method used, and my core is being powered with the C64 optimised power supply, i will check out my power supply and report back :-\

Hi Stryd - the work around is not clear to me - how do you implement it? i am still asking what 'shell' do you use to type the commands? i have tried using both perl and command prompt unsuccessfully i can load a sysex into midi ox and send it - that is not a problem its converting the hex into a sysex that is unclear quote - Open a shell and change to the directory which contains the application. Simply start the batch file "CONVERT.BAT" (by typing convert), or type the whole command line perl mk_syx.pl main.hex to convert this .hex file to a .syx file so thats the instructions - i need to know - 1 - what is the shell ? (i am running XP) 2 - how do you change directories? - is it like this ' c:documents and settings/mios hex' 3 - 'hange to the directory which contains the application' - define the application please 4 - do i type everything that is mentioned between the quoates - "perl hex2syx.pl -os_upload update_without_installed_mios.hex" 5 - what does this mean ? - (attend the "-os_upload"!) sorry to ask of so many questions - but i really cant find the answers to these anywhere else

ive now tried using MIOS Studio on three different computers with three different midi interfaces (m-audio uno / 2x2 / yamaha umt-ex) i have also tried using 3 different PICS (all smash tv/ bootsrap 1.1b) in the same core each time i try to upload the hex i get the same messages as previously listed in this thread. java type installed - ' jdk-1_5_0_07-windows-i586-p.exe ' - is it possible this is the wrong JAVA to install? other than that - i get the correct voltage checks on the core midi is going in / comming out of the core ive done cable loopbacks in MIOS studio and it recevies exactly what it sends

where do i type this command? i am using windows xp - do i type it in a 'pearl shell' or in a 'command prompt shell' im sorry im not able to understand this stuff unless its spelled out in simple terms because i dont have any experience with language programmming :-[

would it be possible for some kind hearted soul to post me a link to download the sysex version of the hex file - please please please! i tried to convert it myself with pearl installed but im a bit of a retard, although i can easily send a sysex using midi-ox - :D the hex i need is - pic18f452\midi\update_without_installed_mios.hex here's hoping!!!

this is what i get using the midisport uno interface - it is obviously not the same as the message going out, also the hex upoad self-aborts after three atempts and prompltly displays this error message ' Error: Received unexpected Upload Request Aborting after 3 errors' MIDI IN MONITOR - timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 01 F7 timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7 timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 01 F7 timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7 timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 01 F7 timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7 timestamp [unknown] | Sysex message: F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 F0 F0 00 00 7E 40 00 01 F7

i just swpped MIDI interfaces, so now im trying with an EDIROL UM2x i did some tests to make sure it sends and receives sysex, i connected the 'in' to the 'out' with midi cable (i did this with both leads that i will use), sent the hex file in MIOS studio , and monitored the ports, it seems to send and recieve properly, i get exactley the same messages apearing in the 'in' as the 'out' monitors. so i presume the interface works, now when i hook up to core board and set up the hex, with the 'wait for request before uploading;, i switch on the core, the core sends the request message, MIOSstudio sends the first block - and then nothing comes back in, so i aborted the hex upload, and just powered down the core, and switched it back on to see if it would send the request again, and there was nothing on the input monitor. so i checked the midi connections in the MIOS device routing, i disconnected and then reconnected the MIOS routings, and then the monitor started showing the core request message again, bizarre ??? it seems to be disconnecting the midi routing in miosstudio, i did this five time to check and it happens the same every time, - with your other suggestions - power supply - i am using the 'sid optimised'power supply made from the c64 power block, should i use a different power supply when uploading to the core? i am going to check again with the MIDISPORT UNO interface, and get that midilog you asked for

my PIC was from Smash, and it has Bootstrap 1.1b burned in, - thats why i opted for the hex - -> pic18f452\midi\update_without_installed_mios.hex either way, i thried the hex you proposed, and i got exactly the same error message 'Error: Received unexpected Upload Request Aborting after 3 errors' should i be looking for hardware malfunctions? or is this purely a software thing? your help is truly appreciated!