ultra

i don't think the folks at akai, ableton, or wherever are really browsing our forums to find something marketable. and if they are, oh well. something like a colored grid is a fairly obvious solution for handling clips in live. julien i'm not taking anything away from what you're doing, i think it's awesome. but you created this design because it makes sense, right? well that's why akai made their new controller. the big difference is that you will be able to make yours do exactly what you want, and akai has to build it for everybody. therefore theirs is generic, and yours is not. i like to see commercial controllers similar to what i'm doing because i can look at them and see if i left anything out. i can also commend myself when i've thought of something they've overlooked. muso i think you should post your controller design and let other users give feedback, ideas, and expand on it like we always have done. who really cares a commercial company comes along and makes something similar? how does it affect you? to me, the only concern i have is them taking away the tools we use to control their programs (like liveapi), and i don't think that's going to happen.

the ultracore wasn't designed to have pcb sockets mounted to it. you can jump to another pcb with ribbon cable if you need that. the reason is because i didn't want to design the board based on the placement/sizing/whatever of those sockets.

hi guys. it's thursday and i started working on getting all the information together and i realized i can't remember how much the package weighs so i can properly charge shipping. so tomorrow i'll get it weighed and send the messages out tomorrow evening. anybody who hasn't yet, please pm me with shipping info and paypal e-mail address. thanks. ultra

i've been looking into the cv out a bit too for my seq. all the info is at ucapps.

you might be able to modify the driver linked in this thread: http://www.midibox.org/forum/index.php/topic,11967.msg110413.html#msg110413

hi, you're not too late but i've left this order open way longer than i should have. tomorrow night (wednesday) i will send out the invoices. anybody who wants one can add themselves until then. ultra

wow i thought it looked cheesy when i saw the first drawing (sorry), but the end result is outstanding. good work!

thanks PT. TK: i might be living in excess here, but i was hoping to connect 5 of these touchpanels. i suppose there's only room on the core32 for 3 of these?

thanks PT! edit: so does this mean that for mios32/core32, i want lcd1 = d0, lcd2 = d1, etc..? i'm not even plugging this into the pic core at all.

hey phil: i have a couple questions and comments about connecting this and your schematic: did you limit the current from the 5v b+/b- source? your schematic shows a resistor to the cathode but it doesn't say a value. your connections to anode and cathode from b+/b- are backward. also should be 9x1uF capacitors, and i believe they can be polarized because the pins of the lcd are labeled p and n. i'm sure non-polarized are ok but harder to find in that capacitance (is this correct?). does it count backward with the data lines? you connect your first to d7 and i'm assuming it goes backward from there to other lcds? in my pcb schematic i've connected like this: D7 --> lcd1 D6 --> lcd2 D5 --> lcd3 D4 --> lcd4 D5 --> lcd5 i've also adapted this to the pinning of the core32's lcd header instead of the regular core. i'm not sure if the pinout is the same (doesn't matter i guess), but are any of the actual connections different? thanks! ultra

well i'll be damned

wilba is using the button and duo led matrix: http://ucapps.de/midibox_seq_options.html

tk and phil: thank you! i'm really looking forward to being able to get what i want out of my live controller. this is gonna rock. for those who don't know: this is for a $15 touchpad that can be attached to the low cost DOG character lcds (the m size) available at mouser. so now we all have the ability to put touchscreens on our midiboxes for x/y pads and menus. :)

whenever i have time to work on it.

awesome. the bulk order says it ended two days ago, but it'll be just a few more days. i have a wiring contract to take care of this week and between that, school, and my job, i'll be busy 100% of the time. so don't worry, it'll be taken care of soon. anybody who's already ordered and sees this can PM me their shipping info. ultra

no problem

where's my board???????????? can you have sahira do my smd soldering for me?

beautiful!

to minimize wiring from board to board, and to match wilba's kit, you can order my pcb. check this thread http://www.midibox.org/forum/index.php/topic,12811.0.html the second post has a link to the information about the pcb, and the first post links to the wiki to order it. basically, this will keep you from having to connect the banksticks and IIC modules to a core with additonal pcbs and wiring. if you don't need the IIC modules (extra MIDI I/O), you probably don't need this board and would be better off getting just a bankstick board and the rest of the stuff. ultra

i've added you to the group buy. good luck with the wiki :).

i'm ok with off-topic. this thread isn't much more than to announce the group buy anyway. look for the "log in" button on the wiki. i think i have to log in, even if i'm logged into the forum. if that doesn't work, and you want to order, just put it here and i'll edit the page for you. i'm not sure what you mean by "supported". maybe look at it like "used by the community". i think that people will continue to use it because it may be enough for them, and you can always get your questions answered and find the information here. i'm pretty sure tk isn't going to remove the v3 info once v4 comes out :). personally, i like using the ultracore pcb as a development board because it has everything you need right on it, and especially the lcd pinouts and extra lcd header are handy to have. i'll be using a seq v4 but i won't run out of uses for my ultracore.

well the ability to customize is where you'll really unlock the potential :)

if you haven't, you'll want to develop some c skills along the way (not too difficult i've found out). python knowledge shouldn't be required. maybe by then i'll have this all moved over to mios32 using osc.

you basically have to write your own midibox app for this. i provide functions you can use. the midibox64 is it's own application so it won't have anything to do with this. also, i haven't added in the functionality to use pots yet. every value sent to live is relative to prevent parameter jumping, so i left out potentiometer/ain functionality. i suppose i should add it at some point, but the first version is generally to fit my purposes ;). if you take out the detent thing in your encoders, they feel more like a pot and this works really nice with live because then no parameters jump.

nope