I'm actually already aware of Ms. Sobhany's work, I've watched the Youtube videos when they first came out, but I noticed for example, that many user's comments brought out the fact that she could have easily just used real DJ decks for at least 1/3 the cost (so cost would be the factor here of "why would someone use a tablet?"). Also a lot of commentators didn't like her mixing and said her beatmatching was off. So I am unsure how seriously to take her. I mean it's one thing for someone to strike out into new ground, but maybe if I saw Dr Dre. using a tablet or Black Eyed Peas or something, then I'd pay more attention (I'm not announcing musical preferences here :) just examples).
I agree with Olivier, audio support on android, when compared to i* devices, is very limited in ability. My apps are mostly sequencer / programmable and are not designed for "instant live play" but rather, program and play, and I was considering adding more features such as Scene switching, etc like Live has the ability to do. Such a thing is definitely possible on Android even at this stage. Where android really lacks right now is audio latency more than anything - it's just impossible to easily do a live play type of app where you can synthesize a sound on the fly while playing live. That is where you really get hit by latency. But for programmable sequencers and samplers, you can easily eat up the latency just by using patterns and pattern switching. Anyway, I digress. My original question was aimed more at the "why would they choose a tablet and my app when they could grab Ableton Live or other and put it on a tablet PC if they liked touch control". Although I do agree that having a real touch interface would have great appeal. But in an app, for example, like a MIDI or Loop sequencer, the touch control may be more difficult than using a mouse or stylus even (unless new types of operating are invented as part of the app). So my question was really based not on technology, but usage. -nik On Feb 21, 2:55 pm, Olivier Guilyardi <[email protected]> wrote: > On 02/21/2011 08:37 PM, Olivier Guilyardi wrote: > > > On 02/21/2011 07:52 PM, Mark Murphy wrote: > >> On Mon, Feb 21, 2011 at 1:35 PM, Olivier Guilyardi <[email protected]> > >> wrote: > > > And, clearly, DJ'ing and many other advanced music usages are not possible > > on > > Android currently. Some things can be done with audio on Android (and I > > did) but > > there are many limitations. > > I think I'm being a bit rude here. Maybe that's because, as an audio > developer, > I have great expectations. To clarify things: as long as you can deal with > certain limitations (high latency, no I/O sync) then Android support does work > correctly on many devices, and there are certainly plenty of beautiful apps > which could be developed on current Android tablets. > > For example, tablets are perfect for MIDI and OSC controllers. You can have > virtual sliders, knobs, VU-meters, etc... Presets for major software such as > Live, Protools, etc.. I haven't done a survey of what's available currently, > but > I'm sure there is some room for that. And it's very feasible technically IMO. > > -- > Olivier -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
