ssp

easiest way to rule out the button is get a fine pair of tweezers or a pice of wire and touch one ned to the pin that it uses and the other to gnd, see if the lcd shows a 0 to 127 jump, if so its the button. so say your using pin 4 for this button and then its going to to gnd, then all you do is put one end of the tweezer on pin header 4 and the other to gnd (same if using a wire) and if your lcd shos a jump from 0 to 127 then its the button. one other thing make sure you have the wires going to the right terminals on the button!!

i bet more than likely you have it linked wrong, its the most common mistake to make. to stop this happening i only put one row of header pins on my dinx boards. if you look at the dinx4 board from the top (presuming you have got a smashtv board) you only put the headers on the leftmost outer holes, and the same on the j2 headers also here is one of my dinx4 boards, the first headers on J1 are only on the leftmost holes and on J2 the inner (left) holes also. try this, hope it helps.

if you have got any ain pins ungrounded this will cause the core to send data. you can either ground all the pins on the core for now, or another easy way is to edit the setup file and set the ain to 0 and the mux to 0 then recompile and then uplaod again to the core, when you do this the core will not send the ain data anymore, this is how i disable the ain on my cores when i have none connected rather than grounding.

if you have messaged them through ebay and they havent responded and you are not happy then you need to goto the resolution centre and file a complaint, they will see that you have tried to contact the seller. wait the required period of days then they will refund you.

if it were any other person i would be curious but as it is doug i would not worry in the slightest. as we all know doug has been through the wringer lately and his time has not been his own. He is not in the habit of ripping people off, so all i would say is be a little more patient and he will get things sorted. Doug is a good guy, give him a little time and he will sort things out.

i grabbed one of these recently http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&item=190457126345 use it most of the time now its a good set up and works well along side my metcal system.

hi protosx with the case what about just having the faceplate made? as that will take the most use and wear, the base can be a stained wood for now, if you want the black look then get an ebony stain and give it several coats, or you can get some mdf cnc cut and then powder coated, mdf can be powdercoated as it has moisture content that allows it to be charged for coating. Or you could have the lower case made out of acrylic sheet that has been heat bent on the edges to make a box, then fix the metal face to that. If your stuck for ideas or want help with the face let me know and i will gladly design a face panel for you to the size you need in solidworks in sheet metal format and have it in the correct format for a cnc company if you want. The biggest cost is the design translation to cnc files for thier machines, if i were to do a full case for you in sheet metal and then map it to a cnc file for a company you would then only be paying for the material and cnc time which would not be much at all then. have a think on it and get back to me. ssp

Hi protosx. Let me say some very nice work there! Now in anser to your question. You can make a new "patch" or "bank" of settings for the one strip. save this and then make a new "patch" or "bank" for the next strip. You then switch between the different banks. You can also use the morphing feature to morph between current and saved settings for the controls. You would need several bankstick chips chained together for the amount of storage you want. I know someone on the board recently made some really nice bankstick pcb's recently as i was drooling over them myself! you could ask for a copy of the eagle file and get some made. With my BPM controller i also use it for other plug-in's so i use the bank change feature for each plug-in i want to use, each plug in is given its own bank and i select the bank for the plug-in in use. The best thing about it is that when you have the bankchip attached you can "name" each button or controller to what ever you want! I hope this helps. there is more details on this in the tutorial section for the mb64e on ucapps.de

hmm... the forum is not an issue as everything you need to know is here, i gave you two specific links to two sections that dealt with the item you wanted to know about. From that point on its upto you how you proceed to continue on your chosen project, that was an example of what i built to achieve the same thing, it was an "option" presented to you. The one thing everyone gets told when they want to build things here is to read, read and read some more, i know even i had to learn and i still dont know much but i get by and i also get help from the guys here. The main reason i get help is the fact i have simply made an effort to learn and build things myself before asking the 100 or so questions people invariably do. anyway, im done, bttd

once again search is your friend

search is your friend

julian the fsrs just wear out, common issue with them, no point doing the sensitivity upgrade its better to just replace the fsr sheet. I got mine from mpc stuff the guys there were great. when i built the bpm controller i spoke with franklin eventoff who actually designed the fsr its elf and we spoke about it in great deal and he said the only issue with it is that after a period of time they wear and become un-useable. It is better to replace them when that happens.

as its your first post you wont get many offers in here, the best thing to do is to put up some pictures as well so people can see the actual items for sale and see its genuine.

wow , thanks guys, i really did not know that i could use c for mb64e and still up it to the 452's. Now i have something to get my teeth into again!

hi thorsten. the reason i stuck with the asm side of things was because i thought that the mb64e was still not ported to the new core unit, at the moment i think it still has not been ported or am i wrong? this was why i stayed using the assembler code. is it possible to write something in c and still upload it to the 452's? this is what i am not dure of and also what has prevented myself from going to c. Im basically back to noob 101 again!

thanks thorsten, i almost see what you mean now, i have some more reading to do again and lots of notes to make so i have reference again. I have been reading all my notes on the meta handler routine we did for the mmc unit and the mmc handlers so i am hoping that by the time i have read everything again and written some test code i will have a grasp of it again. is it possible to say write something in "c" and then port it to the 452 core? everyone has said i should move onto "c" now as it makes life much easier, i have found a website with details tutorials and tests so i am neck deep in that also. so if i get that in my grasp or the basics i will try writing something and uploading the text here to see just how bad it is!. thanks as always

thanks nils, yes i understood that , however that would be in c and the mb64e isnt supporting c code yet. ok so i just did a few changes to the encoders and realised that to change the patches its a program change not a cc# doh! so i assigned the program change to an encoder and bingo worked first time, so all that has to be done is to apply the two features to two sets of - and + buttons.

ok today i did a quick test, using an encoder on a din sr i set the cc# to 0 and the min value to 0 and the max to 5, the reason for this is that the synth has 5 banks. when i turned the necoder it stepped nicely through the banks up and down with the turn of the encoder back and fore. now to apply this to a set of buttons i would need either a -1 or +1 byte assigned to each button, the same with patches. i cant find any subjects on the forum or ucapps that relate to this feature for making patch or bank buttons , the editor only has a bank feature for teh encoders, if you apply it to a button you only have a 0-127 state and a repeat press does not increment the patch it only jumps to the patch at the relative byte value, then back to the first patch on release. how would i code a small script to achieve this function? two buttons for bank and two buttons for patch labeled bank- bank+ patch- patch+ so the starting state for bank- is B0 00 00 a press of bank+ changes this to B0 00 01 which sets it to bank 2, pressing bank+ changes it to B0 00 02 which is bank 3, pressing bank- 2 times returns it to B0 00 00 bank 1. and patch- initail state is C0 00 which is patch 1 then a press of patch+ gives you C0 01 which is patch 2 and then pressing patch- takes you back to C0 00 patch 1. basically the same function set as the banks however for the patches. i cant find a cc# for patches that allows the stepping through of patches, if i can find this then i could assign an encoder to patches and have a button for the banks. i am not sure if a step -1 and +1 function would need to be written in or a table of the complete sysex would be needed. thanks update: some of the softsynths im using will only respond to the sysex commands for bank and patch change they do not respond to the cc# of cc# 0 for bank and cc#32 for patch.

as the mb64e is not in "c" yet i have to use asm for this Im trying to assign incremental functions to a set of 4 buttons, i did think of using meta events however im not sure how to go if i need to make a set of tables or not. now the functions i want to use are the midi standard bank - and + also patch - and + so by using the buttons i can step up and down midi banks and patches on my synths. the standard sysex functions called are as follows. TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT 00001CAC 1 -- B0 00 01 1 --- CC: Bank MSB <---- this is the bank change command 00001CAC 1 -- C0 00 -- 1 --- PC: Acc. Grand Piano <---- this is the patch change command 0000226A 1 -- B0 00 01 1 --- CC: Bank MSB 0000226A 1 -- C0 01 -- 1 --- PC: Brite Acc. Piano 0000277D 1 -- B0 00 01 1 --- CC: Bank MSB 0000278D 1 -- C0 02 -- 1 --- PC: Elec Grand Piano 00002C77 1 -- B0 00 01 1 --- CC: Bank MSB 00002C77 1 -- C0 03 -- 1 --- PC: Honky-Tonk Piano 00002DF0 1 -- B0 00 01 1 --- CC: Bank MSB 00002DF0 1 -- C0 04 -- 1 --- PC: Electric Piano 1 and here we change the banks, DATA 1 steps the bytes of each patch by 16 bytes ( i hope im right there) so from 50 to 5f steps up through patches 65 to 80 TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT 0001D2FF 1 -- B0 00 01 1 --- CC: Bank MSB 0001D2FF 1 -- C0 00 -- 1 --- PC: Acc. Grand Piano 0001E2B0 1 -- B0 00 01 1 --- CC: Bank MSB 0001E2B0 1 -- C0 10 -- 1 --- PC: Drawbar Organ 0001FC35 1 -- B0 00 01 1 --- CC: Bank MSB 0001FC35 1 -- C0 20 -- 1 --- PC: Acoustic Bass 000206A7 1 -- B0 00 01 1 --- CC: Bank MSB 000206A7 1 -- C0 30 -- 1 --- PC: String Ens 1 0002105D 1 -- B0 00 01 1 --- CC: Bank MSB 0002105D 1 -- C0 40 -- 1 --- PC: Soprano Sax 000214E4 1 -- B0 00 01 1 --- CC: Bank MSB 000214E4 1 -- C0 50 -- 1 --- PC: Lead1(square) what i want to do is have the keys do a stepped decline or incremental mode that allows each press to step through or backwards through the banks/ patches and then be able to freely assign them to any button i wish as i would have done using the meta events feature with the editor. so would i have to set up an incremental code string that holds each sysex byte all the way through from 00 to 5f for stepping upwards and then for declination i would reverse it 5f to 00. The other reason for this is that i can set up several sets of these button features however give each set thier won midi channels and then use each set to control multiple softsynths in forte. so if i had say 4 softsynths running , i could have a bank/patch change set on channel 1 synth 1 and another on bank/patch channel 2 synth 2. thanks

everything you need to know is either in the forums or on the ucapps.de site, first rule of thumb is that if you think you have read enough you probably haven't nils gave you a link where to buy the parts from so try again. as for being specific you wont get more specific than the wiki or any related threads that you can search for in the forums.

Well after a little while playing around with some new softsynths i needed something new to build, I am still working on my control surface console and that is going to take a while to finish the design so i needed something else to do. Now some of the virtual softsynths i am using are really nice, but running them with fx and other features in real time takes cpu power up especially if im using several at a time in the DAW software. So I have decided to build myself a self contained vsti host hardware system with the mb64e as the main interface, the only other item used being a small trackpad ot a rollerball I am more inclined to use a rollerball as it would require less space. I am currently working on the casework and layout but its pretty much laidout in solidworks already. The system will use: a mini itx pentium i3 board, a scythe low level cooler, a raptor 15,000 rpm drive and 3 gig of ram with a layla 3g audio interface. midi handled by a gm5 internally and via usb linked to the mb64e core. psu will be a 1u internal m-itx psu in a slot in section for removal and replacement. The underside will have two removable drive mount plates for adding an additional drive, and the front lower panel will have a slimline/laptop dvd-rw drive for loading synths or software. I have chosen Brainstorms Forte software as the front end as it allows me to combine or convert any midi signal it recieves to any parameter or function i want, also it will allow me to make patches of various setups of synths and fx and save them then assign each one to a certain midi cc# for instant recall. This combined with a really stripped back xp pro that only runs in 60mb of ram it should be really interesting. I have a few pentium4 boards and processor lying around here to test single synths on, so it is possible to make a few of these only running single synths on the p4 boards. Will upload the first renders of the casework later on.

(more concise) why move to trash? nice woodwork ;) one way to get the step in the wood other than using a router is to have a table saw and then you lower the blade to the cut depth you require and then move the guide bar to the cut width you require then pass it through the saw, this gives you a really nice step cut in the wood. very nice work though! :thumbsup: