We are evaluating the possibilities of entering other markets as well but it's nothing that could happen anytime soon...

the longer it takes the more money your'e losing !

Google OS is crap where it comes to coding music apps. Latency is terrible, no MIDI support, etc;... Go and hastle Google about it, not Steinberg.I am afraid you have chosen the wrong mobile OS device to create music on.BTW; Definetely no money lost by not developing for Android, money lost by buying Android for music though... PS; Look on the bright side though, you can still Google all those juicy iOS apps using rather excellent Google browser

waveform wrote:I see there's an android remote that works with cubase http://www.humatic.de/htools/touchdaw/Looks like Steiny left it too late and third party developers have beaten them to the punch !

To answer your question:android is useless for music production - LATENCY!!!.iOS is the future standard for music production (CoreMIDI and CoreAUDIO support) apps until android "isecream" comes along in 2012/2013... (maybe)BTW; By that time we will be using iOS 5 or 6 or 7 on iPads PS; and your link is dwarfed by this one, I'm afraid...http://www.saitarasoftware.com/Site/AC-7_Core.htmlThis is just one of many available, as they say: "there is an app for that"... ... and here is another one if you prefer Ableton Live:http://www.touch-able.com/Site/touchable.htmlBTW; From developers point of view this is just a nightmare. So many different incarnations of android OS, so many different hardware options and not one of these bring unified unity (Microsoft Windows anyone? )...BTW; Hey Steinberg, How about that iPad dedicated release of both apps ?

I understand that latency is a problem when playing on a live keyboard or directly process incoming audio. But 95% of the music apps out there don't have any live input that instantly has to produce sound at the output. Most are just audio recorders, step sequencers, sound/beat generators etc (like Loopmash for instance). Finger/audio input and audio output work just fine on Android.

BTW: Control surfaces usually have nothing to do with the audio/MIDI system of Android or iOS. They just fire a normal network message into the local net every time when the screen is hit and I've never heard that the network stack of Android is slower than the iOS one. The server on the PC/Mac (rtp, CoreMIDI etc) then interprets this message and sends a generated MIDI command over a virtual MIDI cable to the DAW (or whatever protocol is needed to control a program). General control surfaces like the OSC variants show this every day. Even specialized apps for for DAWs that allow dedicated control from the outside (most but Cubendo) work exactly the same on both platforms.

atlatnesiti wrote:BTW; From developers point of view this is just a nightmare. So many different incarnations of android OS, so many different hardware options and not one of these bring unified unity?

Where is the difference to iOS? There are four major iOS versions out there each with lots of intermediate releases working on dozens of different iPODs, iPhone, AppleTV and iPad hardware devices that range from something very simple like several years old iPods to higher ended devices like a new iPad 2.

OK, the difference is that the developers have the permissions from the user base to constantly go the easy way by saying: "The software just works on the latest device and OS from Apple and if you want the software then you have to dump your old device and buy something new". The users then just go to the next Apple store and buy the next iToy as told. Additionally these sheep are bravely buying the same apps again just when the display resolution changes on the new device (eg when the iPodBig, em, iPad was released) and of course there is no moan when the latest iRig doesn't run on a four year old iPod. Understandable this is a paradise for developers.

You could do the same on Android by saying 'This app needs a 1GHz processor, 128MB RAM and Android 2.3 minimum' and it will just work on every device as long as the thing follows the minimum specs.

waveform wrote:I see there's an android remote that works with cubase http://www.humatic.de/htools/touchdaw/Looks like Steiny left it too late and third party developers have beaten them to the punch !

To answer your question:android is useless for music production - LATENCY!!!.iOS is the future standard for music production (CoreMIDI and CoreAUDIO support) apps until android "isecream" comes along in 2012/2013... (maybe)BTW; By that time we will be using iOS 5 or 6 or 7 on iPads PS; and your link is dwarfed by this one, I'm afraid...http://www.saitarasoftware.com/Site/AC-7_Core.htmlThis is just one of many available, as they say: "there is an app for that"... ... and here is another one if you prefer Ableton Live:http://www.touch-able.com/Site/touchable.htmlBTW; From developers point of view this is just a nightmare. So many different incarnations of android OS, so many different hardware options and not one of these bring unified unity (Microsoft Windows anyone? )...BTW; Hey Steinberg, How about that iPad dedicated release of both apps ?

Sure, this is the issue entry for the low latency performance under Android. But I don't see any current Steinberg app that requires low latency audio to do what it does. So the issue doesn't matter at all.

You are a pathetic jerk. Users ought to be able to come here to discuss possible uses for their devices (which might have been bought for other legitimate reasons) and not have your thoughtless stupidity dumped upon them.

You are a disgrace and really give Apple users a bad name.

Come back when you can answer the question with something approaching relevance.

With the emergence of smartphones and how they are useful to making everything available even on a portable option, an android app would most likely be the thing that people would look after it. And in terms of going with the ones that you like most, you just have to ensure that you have the proper things setup.

Not the best thing to see what you have lost from that easy, I suppose.