I am looking to create a midi application for android, what I am planning to do that I think is unique, is to allow the user to map the controller.
so lets say you add a button when you press it you can get it to give out 3 midi commands. or have it timed to the midi clock so when you press it, it sends a command then lets say for the next four beats it sends another command,
also got some ideas for knobs and faders. what do you all think
I think that’s a good idea… but how is that different from the recently released Lemur on iOS? Lemur has scripting so you can do all that kind of stuff…
That said, I’ve just moved from iOS to Android so the more midi apps, the better!
to be honest i have not really had a look at the lunar one for IOS. I have only had a look at the android ones available.
I’m going to start off pretty simple with a 1st release I’m thinking of a 9 pad screen. in the android menu you can go into editing mode to add midi commands for when it is pressed/released.
second release I want to add midi feedback to the pads. traktor has led out so I want to really abuse those values to be able to provide different colours that are a lot more vivid than any controller can be.
what features do you think I should add after that
its an interesting idea, Its kinda a hacked system as you need to tell tractor the devon controller is connected to get the midi output. might ask for it as a feature request from NI. don’t know how much joy we will get tho. it would be pretty easy for them to add, but I’m guessing NI havnt got that many people working on traktor so there are more critical things to get right
just looked at there site and scripting language. I think the big difference is, is that I want to create a product designed for traktor. I don’t want people to have to learn a scripting language. I want people to just be able to decide what control they want with just a few drop down boxes, but still want to give the users the ability to do some crazy stuff with midi.
I think most djs are not overly technical. many like technology but are not programmers so a scripting language is that not friendly to them. people like using gui’s. I think the complexity of tractor midi mapping is enough to put a lot of noobs off
but you need to activate that controller in tractor, and presenting a controller as another controller also raises some ethical and possible legal issues, so its not a road I’d want to go down at this point. maybe after the app is launched, getting a tractor update that sends this data to the app aswell
im going to try do it in java. going to make a test app with just 1 button, just need to see what the latency is like but im pretty confident it should be ok in java. if not will have to be c++ just not got alot of experience with it
Awesome initiative! Not really that stoked with Android MIDI apps currently available, so I’ve been thinking about developing one myself, problem is I’m not that an experienced developer. If you need help beta (or alpha) testing, drop me a line!
The main focus points for me would be stability and customizability.
my aim is, is to get somthing working for feb time, then build on that concept. found a midi libary for java so it shouldnt be too much work. not sure how im going to send the message accross bluetooth or wifi yet. il have to look into that. think there is some built in api for it though