ssp

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:

just finished planning the next two projects so i am going to need 3 gm5 chips and two gm5 pcbs, one gm5 is for my second gm5x5x5 and the other two are for internal fitting into cases for the projects. cash waiting if you can spare them. thanks

you have remembered that an encoder uses 2 din pins? so if you use pin 0 then the encoder also takes the pin next highest. so on a dinx4 board you can only have 16 encoders, remembering that the first shift register is for the menu buttons, however these can be made available for encoder or button use should you require. so the mb64e can have a max of 64 encoders on the max link of 4 dinx4 boards to one core. then you can have 64 pots or faders (non motorised faders) linked to the ainx4 boards. personally the use of the first sr1 for the menu functions with an lcd is so helpful in programming everything, as the editor will take time to get used to, also using the menu and lcd you can acertain each encoder, pot, fader, button number and then edit it correctly in the editor. when linked to the editor, if you use midi learn it does not change the button number in the editor to the correct one that being inputted, you would have to change the button number manually in the editor.

looking for a single gm5 smt chip please, just opened my sealed strip of two and there was only one in the strip blisters, the other blister is sealed but no chip! cant remember who i had them off but no biggie. if anyone has a spare they dont need let me know please. thanks

happy birthday wilba heres a little something from me and skippy

just connect the gm5 on its own, see if thats working and being picked up in the operating system. make sure the gm5 has its optocoupler in, as that will need it. also on the ucapps site is a driver for the gm5 grab that just in case you need it, dont write the gm5 off just yet. as for the core you have changed components etc so first thing first check all of your connections, check for shorts and solder joins etc. pull the pic and then check the voltages as per the instructions on ucapps.de. check things one by one before ruling them out.

ok have you pulled the optocoupler in ic2? if not pull that you dont need it also have you linked the gnd pin from the gm5 to the core? this is will give you a timeout error also. also make sure you have the pins linked correctly, use J6 on the gm5 for midi in and out to the core and use the gnd from J7 to link the gnd from the gm5 to the core gnd. as in this picture. once you have it connected like that, load up mios, connect the relevent links in the midi setup and then try reuploading mios first, then reinstall the seq files.

leds are optional not a requirement. also if you had gone here: http://ucapps.de/midibox16e.html ignore the 16e bit as this is the 64e section its just a link name that needs to be changed on the ucapps site. and if you scroll down it states: How many LEDs should I use? It has to be differentiated between the LEDs assigned to the buttons and the LEDrings assigned to the rotary encoders. LEDrings are nice-to-have, but no must. Every LEDring can consist of up to 16 LEDs, the appr. pattern can be defined with the vmidibox editor or with the mk_syx.pl script. I'm using 11 LEDs for every LEDring, and they are connected to the DOUT module like shown in this diagram. Also the LEDs assigned to the buttons are nice-to-have, but no must. They can either indicate the status of the button (especially usefull if the button is in toggle mode), or they can be controlled via MIDI (-> native MIDI remote support). See also this schematic.

take a look at this thread and ask sam a few questions, im sure he will be willing to help and advise.

goto rs electronics and enter navimec in the search, i found it there straight away. http://uk.rs-online.com/web/search/searchBrowseAction.html?method=getProduct&R=0126846

thanks janis however that doesnt detail anything involved or the code change involved. all i can see is poor old nils trying to understand a question from someone and not getting much luck!

im just wondering if its possible to assign the led's to the faders? i have not had time to look at the code yet, im hoping to do that this week, however is it possible to assign leds to the faders as well as the encoders i want to put a line of leds next to each fader so that as the fader is moved up the leds light up in sequence as the fader value increases or decreases. i know that the led rings do this when used with the encoders. or can i have both? leds rings around the 8 encoders and leds by the side of the faders? so basically each fader would have a line of leds like a vu meter say use the max amount which is 16 leds. if this is possible then i can experiment with my spare cores, ain and douts this week. thanks

navimec ftw

ok in the mb64e folder you have got this file called setup_midibox64e.asm open that and you need to assign your encoders to the relative din pins in this part of the file. MIOS_ENC_PIN_TABLE ;; encoders 1-16 ;; SR Pin Mode ENC_ENTRY 9, 0, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 1 ENC_ENTRY 9, 2, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 2 ENC_ENTRY 9, 4, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 3 ENC_ENTRY 9, 6, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 4 thats not the complete list but a few lines to show you the section, you need to work out what encoders are going to what pins. remember that an encoder takes 2 pins so if you have encoders on the second sr (shift register) then you do this. MIOS_ENC_PIN_TABLE ;; encoders 1-16 ;; SR Pin Mode ENC_ENTRY 2, 0, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 1 ENC_ENTRY 2, 2, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 2 ENC_ENTRY 2, 4, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 3 ENC_ENTRY 2, 6, MIOS_ENC_MODE_NON_DETENTED ; V-Pot 4 you can see the sr has changed from 9 to 2, this is because your using the 2nd sr, the first sr is being used for the menu buttons. with the pots make sure you have the right amount set in the ain section as here. #define DEFAULT_NUMBER_AIN 64 <--- this is the default, if you only have 8 pots then set this to 8 and the mux below to 0 #define DEFAULT_ENABLE_AIN_MUX 1 however if you have more than 8 and are using an ainx board then the mux needs to be 1 and any unused pins grounded, however to get round this you can set the ain to the number of pots/faders being used. the menu buttons what i did was move the exec, right, left and snapshot to pins 0-3, i then took the datawheel line out. this gave me 4 more buttons and i still had my menu buttons. remember once you have edited this you then need to recompile the files down then upload them to your mb64e. thorsten will be able to help you in removing the menu buttons to what you want better than i can as i still wanted my menu system on my control unit. there may be a morph setting that allows the menu to be bypassed in use and gives you the 8 buttons, i am not sure. i hope this helps in the meantime.

here you go fozzy, the site i got the info from http://www.4most.co.uk/switches.htm 3rd line up from bottom right

iz ok wilba i haz made ez read now

edited for DENIALZ purposes

U HAZ BEEN DENIED!

nils the only crystals i can get are in the hc49/s format, in your bom they are hc18/u format, will the 49's do?

found these this morning, may be worth a punt on getting a few and see what they are like. http://www.4most.co.uk/assets/File/sunmulon-lcd-new.pdf

just a quick happy birthday to one of the forums most selfless and charitable members! have a good day doug, hope all is well with you!

thorsten. is it possible to have the 32 mblc released without the touch feature please? i dont really use touch anyway, and im not using motor faders at the moment on mine, i just want to use the slimline 100mm panasonic faders i have got that i used in my mb-mmc unit. also in a previous conversation with phil we discussed that the mblc 32 would take 16 faders, has that been implemented into the 32 version of mblc as well yet or is it a section of code to be edited? i was wondering as it would require more lcd display space, unless a 40x4 was used or a graphical unit. thanks

firstly welcome to the forum. if the akai has got midi in and out i dare say that they are for the controller, that is they only output data from the controller, however prehaps in the manual there is a section that states how to use these as additional midi ports over usb? take a look at the manual and see what it says. if not then the easiest thing to do is get your name down for a gm5 kit, its our own usb midi interface, or check to see if nils has any gm5x5x5 boards left and get some of those to make your own 5in 5 out midi usb interface. now you have two options, you build the gm5 kit and this gives you usb midi, the board has got a midi in and out, you can connect those to the cores midi ports and use it that way. however there is a more easy way, you put the gm5 and the core in the same case, then you connect to your computer using usb. internally you then connect the gm5 to the core using the mi/mo pins via digital. i have used this option in my builds and its so much easier only haing to hook usb up to the computer, then you dont have to worry about ports etc. the mb64 is a nice build, however take a look at the mb64e, this will allow endless encoders and buttons using the dinx4 boards. i hope this answers your questions.