ultra

can you please repost the site where you got the case? www.weloe.com doesn't work. thanks, ultra

what is this sammich thing i keep hearing about?????

i've looked into FSR's and have also gotten some samples sent to me. i think the kind of effort it would take just isn't worth it, when a trigger finger is available cheap enough, and all the hard work is done for you. to use an FSR, you'd have to convert the resistance to a voltage using a transistor or an op amp, because the ain reads voltage. using it in a voltage divider wouldn't work either, because it wouldn't be linear. so if you came up with a reliable way of doing this, i'm listening. but i think part of this project's attraction to me is how easy it would be. ultra

hey vinylboy, go ahead and post a blueprint here and start with all the prep work and whatnot. i'll get back to you. ultra

i wouldn't bother integrating this into a seq. partly because i already have one, but mostly because you could just sequence this via midi. from the seq, all you'd have to do is just assign it to the note associated with the pad, and the layered sounds would play. i figure an internal sequencer (much simpler than the seq) could be used just to make some quick patterns, and you'd have the option to connect it to any other sequencer you want. i'm going to use the trigger finger, even though i'd prefer a 2x8 layout like in your image. by using the trigger finger, i can route its own midi into the core and translate it to whatever i want. the trigger finger's own electronics will take care of reading the resistances (it uses force sensing resistors) and setting the velocities. so really it'll be a lot like routing a separate trigger finger to a core via midi, except the configuration will be done in mios. also, the trigger finger is discontinued and is available for pretty cheap from ebay. let me know if you end up wanting to build one, i'll post the plans and i'll be using parts you can find easily at mouser (most likely). also writing the firmware for it will be no problem for me. i'll make a simple editor that allows you to add your drum machines, name the drums, and assign the mappings to them, so all you ever have to do after the one time setup is pick your machine and drum :). ultra

just throwing out an idea i had for another midibox, perhaps others would throw in their 2c. i have an m-audio trigger finger that i want to put into a midibox. i'll take just the pads out of the trigger finger (get rid of the knobs, faders, etc) and put it into a new case. then i'll route the midi straight into an ultracore, and write software that's designed for layering multiple drums. the software would let you pre-program your drum machine mappings into it. so for a pad, you could pick which drum from which machine would play on that pad from a list of available drums. then, you could add additional drums from other machines to the same pad for layering. the one-time setup of the midi mappings, with drum names that make sense, would make it easy to set up a lot of different drums and drum layerings. incoming midi would only have to address a note assigned to that pad, and all associated drums would play. so complex sequences for layering can be reduced to a single note that plays all the layered drums for you. i also thought a 4x40 lcd would be appropriate for showing information and setting up the pads. perhaps even 16 encoders and 16 buttons for the 16 pads would allow some additional control, and maybe a simple drum sequencer could be integrated. the ultracore would allow multiple drum machines to be directly connected. just my idea, it'll be a while until i build this (if ever), so i just hoped to start a thread to bat around ideas. ultra

hey did you look into this? ultra

hey if you pull this off, it'll be a one of a kind midibox (to my knowledge). the new akai lpk25 is a fairly inexpensive midi controller that has a compact design, so if you ripped out the keys and guts you could probably just route it's midi straight into the core. ultra

don't forget usb :)

here's a question i haven't been able to find documented anywhere: what is the ain resolution for the core32? thanks, ultra

nice little app

wow!

if anybody on the forum is using liveapi (i know there's a few), i've started a new google group for us to share information. the old one seems to have died, and is filling up with spam. http://groups.google.com/group/ableton-liveapi let's keep this alive! i am still using liveapi and have learned so much about it. i think we can support each other very well. ultra

you could always send it back to me :>

i'm finally continuing my work on using liveapi to integrate mios32 and ableton live. this works by giving programmers a large set of functions they can call to manipulate damn near anything in live. another set of functions are automatically called by live, allowing you to track whatever is going on. this will let users play a live set without ever looking at a computer screen. the possibilities can be a lot more than that. to do this, i've made a protocol that works over midi and allows a midibox to seamlessly communicate with a liveapi script. on the programmer's side of it, you just have a simple set of functions to play with. look at it as a midibox API for LiveAPI, extending mios into live, and vice versa. currently this is being developed for live 7.0.14. i'm fairly confident that most of the code will work for live 8, and i'll try to get a new version going once this is complete. for a teaser, here are some of the functions at your disposal. keep in mind i haven't gotten to the clips, tracks, or track devices yet, but eventually you'll be able to go as far as bring clip or plugin parameter names into the midibox, and of course monitor what is going on with all of it. this list is growing by the day. functions you can call from mios: void MBLIVE_SONG_SetTransport(u8 state); void MBLIVE_SONG_GetTransport(); void MBLIVE_SONG_SetRecord(u8 state); void MBLIVE_SONG_GetRecord(); void MBLIVE_SONG_SetOverdub(u8 state); void MBLIVE_SONG_GetOverdub(); void MBLIVE_SONG_SetFollow(u8 state); void MBLIVE_SONG_GetFollow(); void MBLIVE_SONG_SetBackToArrangement(u8 state); void MBLIVE_SONG_GetBackToArrangement(); void MBLIVE_SONG_SetDrawMode(u8 state); void MBLIVE_SONG_GetDrawMode(); void MBLIVE_SONG_SetArrangementPosition(u8 mode, u16 val); void MBLIVE_SONG_GetArrangementPosition(); void MBLIVE_SONG_SetTriggerQuantization(u8 state); void MBLIVE_SONG_GetTriggerQuantization(); void MBLIVE_SONG_SetTempo(u8 mode, u16 value); void MBLIVE_SONG_GetTempo(); void MBLIVE_SONG_SetTempoNudgeDown(); void MBLIVE_SONG_SetTempoNudgeUp(); void MBLIVE_SONG_SetTimeSignatureNumerator(u8 mode); void MBLIVE_SONG_SetTimeSignatureDenominator(u8 mode); void MBLIVE_SONG_GetTimeSignature(); void MBLIVE_SONG_SetGrooveAmount(u8 mode); void MBLIVE_SONG_GetGrooveAmount(); void MBLIVE_SONG_SetMetronome(u8 state); void MBLIVE_SONG_GetMetronome(); void MBLIVE_SONG_SetLoopStart(u8 mode, u16 val); void MBLIVE_SONG_GetLoopStart(); void MBLIVE_SONG_SetLoopLength(u8 mode, u16 val); void MBLIVE_SONG_GetLoopLength(); void MBLIVE_SONG_SetPunchIn(u8 state); void MBLIVE_SONG_GetPunchIn(); void MBLIVE_SONG_SetPunchOut(u8 state); void MBLIVE_SONG_GetPunchOut(); void MBLIVE_SONG_SetSessionArrangementView(u8 state); void MBLIVE_SONG_GetSessionArrangementView(); void MBLIVE_SONG_SetClipDeviceView(u8 state); void MBLIVE_SONG_GetClipDeviceView(); void MBLIVE_SONG_SetBrowserView(u8 state); void MBLIVE_SONG_GetBrowserView(); void MBLIVE_SONG_SetDetailView(u8 state); void MBLIVE_SONG_GetDetailView(); void MBLIVE_SONG_GetTrackCount(); void MBLIVE_SONG_SetSelectedTrack(u8 track); void MBLIVE_SONG_GetSelectedTrack(); void MBLIVE_SONG_GetSceneCount(); void MBLIVE_SONG_SetSelectedScene(u8 scene); void MBLIVE_SONG_GetSelectedScene(); functions called by live: void MBLIVE_SONG_NotifyTransportChanged(u8 state); void MBLIVE_SONG_NotifyRecordChanged(u8 state); void MBLIVE_SONG_NotifyOverdubChanged(u8 state); void MBLIVE_SONG_NotifyFollowChanged(u8 state); void MBLIVE_SONG_NotifyBackToArrangementChanged(u8 state); void MBLIVE_SONG_NotifyDrawModeChanged(u8 state); void MBLIVE_SONG_NotifyArrangementPositionChanged(u32 val0, u8 val1, u8 val2); void MBLIVE_SONG_NotifyTriggerQuantizationChanged(u8 state); void MBLIVE_SONG_NotifyTempoChanged(u16 value); void MBLIVE_SONG_NotifyTimeSignatureChanged(u8 val0, u8 val1); void MBLIVE_SONG_NotifyGrooveAmountChanged(u8 value); void MBLIVE_SONG_NotifyMetronomeChanged(u8 state); void MBLIVE_SONG_NotifyLoopStartChanged(u32 val0, u8 val1, u8 val2); void MBLIVE_SONG_NotifyLoopLengthChanged(u32 val0, u8 val1, u8 val2); void MBLIVE_SONG_NotifyPunchInChanged(u8 state); void MBLIVE_SONG_NotifyPunchOutChanged(u8 state); void MBLIVE_SONG_NotifySessionArrangementViewChanged(u8 state); void MBLIVE_SONG_NotifyClipDeviceViewChanged(u8 state); void MBLIVE_SONG_NotifyBrowserViewChanged(u8 state); void MBLIVE_SONG_NotifyDetailViewChanged(u8 state); void MBLIVE_SONG_NotifyTrackCountChanged(u8 trackCount, u8 returnTrackCount); void MBLIVE_SONG_NotifySelectedTrackChanged(u8 track); void MBLIVE_SONG_NotifySceneCountChanged(u8 count); void MBLIVE_SONG_NotifySelectedSceneChanged(u8 scene);

well, i found the cause of my own problem. i haven't done any mios32 programming in many months and for some reason my core32 was bricked. i must have left it that way last time i used it. so i closed j27 (which made windows install the driver properly) and uploaded the firmware again, and now it works fine. i did go back to xp anyway but i don't think this was a windows 7 problem after all.

hey tk, thanks for the reply. i'm not sure of anything like this, maybe somebody else knows. i decided that i'm just going back to windows xp. i'd love to be the guy who solves the problem for everybody else who is or will be using windows 7, but i'm just tired of the frustration. i've promised some mios32 and ableton live integration and i just wanna get it finished :)

when i first started using windows 7 RC1, the core32 didn't work at all. this was back in may. then, in july, it magically started working. i haven't done any core32 development since then, and i'd like to start. however, now the core32 doesn't work with windows 7 again. i get "usb device not recognized". is anybody else having any luck with the core32 and windows 7? thanks, ultra

you don't want that crap! :)

hello, this is a midi controller that's been done countless times in various ways by the midibox community. having buttons, knobs, and leds is pretty standard and there's a plethora of information at ucapps.de. there's pretty much nothing you can't do. to do something custom like you want, you need some skills with coding in c, and of course you need an understanding of midibox and mios (again, ucapps, and the forum and wiki). read as much as you can and dive in. ultra

hey julien, there's nothing to wiki yet besides just some general information. in a couple weeks i am moving into my new house, and once i'm settled in i'm gonna get going on this project again.

nice design, where did you find the case?

just so you know, this project is still alive!

i have a spare gm5 chip and pcb i can sell you. does anybody remember what i paid for it? ultra

same here cimo, i haven't been on the forum at all and i haven't been building anything or working on my coding projects. now that summer is here, i'm constantly drawn outside and i can't bring myself to do indoors stuff.