Mainstage for the iPad

For iOS (iPhone, iPad & iPod), Android, Windows Phone, etc. App and Hardware talk
RELATED
PRODUCTS

Post

The real question is: Why is Mainstage so resource intensive to begin with?

Did MS run on Macs even 4-5 years ago? Because, based on straight MIPS/Gflops calculations, the current iPad Air/mini retina is basically equivalent to CPU/GPU power of PC's about 5 years ago - and gaining fast.

I guess I'll stick with my BIAS amp, MIDI guitar, iOS synths, Audiobus, Apollo, MIDIbus, etc. configuration for live gigs with iPad and leave all the DSP and amps back in the studio :).

G
Don't ask me, I just play here.

Post

ZenPunkHippy wrote:Sorry, but you are kidding yourselves if you believe that apps running on iPads are mainly slow because of poor optimisation. That is simply not true, it is pure speculative fantasy and does not match with reality.

The reality is: tablet and phone CPUs are 5 - 10 times slower than desktop CPUs. It's not very difficult to understand!

Note: I am talking about raw number crunching ability. Go look at the benchmarks if you don't believe me.
That is indeed correct, and exactly that is the problem. I used daws 10 years ago, when a desktop was 10 times slower than the current ipad or other mobiles, and those daws worked smoothly. They actually did because devs did care about cpu consumption.

If you were an architect and you had to build a house, I'm sure it would look different if you had 5000m2 or 100m2 of ground to build it onto ;).

Post

planeth wrote:
ZenPunkHippy wrote:Sorry, but you are kidding yourselves if you believe that apps running on iPads are mainly slow because of poor optimisation. That is simply not true, it is pure speculative fantasy and does not match with reality.

The reality is: tablet and phone CPUs are 5 - 10 times slower than desktop CPUs. It's not very difficult to understand!

Note: I am talking about raw number crunching ability. Go look at the benchmarks if you don't believe me.
That is indeed correct, and exactly that is the problem. I used daws 10 years ago, when a desktop was 10 times slower than the current ipad or other mobiles, and those daws worked smoothly. They actually did because devs did care about cpu consumption.

If you were an architect and you had to build a house, I'm sure it would look different if you had 5000m2 or 100m2 of ground to build it onto ;).
Problem is: If you were an architect and had the option to use 5000m2 instead of 100m2, would you go into the 100m2 instead? I wouldn't, and asking todays "architects" to go back in time 10 years is not fair. Of course that some may just be spoiled and lazy when coding, but today DAWs have no comparison with those that existed ten years ago, feature wise.
Fernando (FMR)

Post Reply

Return to “Mobile Apps and Hardware”