KVR Audio

JavaJ · Post by **JavaJ** » Thu Jan 12, 2012 5:29 pm

Imagining the possibilities if they were to do that. Do you think they are working on it? Can it even be done on iOS. Would love to see something like the Finger or the Mouth for iOS- that would be so cool.

ea · Post by ea » Sat Jan 14, 2012 1:46 pm

JavaJ wrote:Imagining the possibilities if they were to do that. Do you think they are working on it? Can it even be done on iOS. Would love to see something like the Finger or the Mouth for iOS- that would be so cool.

+1

/ea

casiosk1 · Post by **casiosk1** » Sat Jan 14, 2012 3:34 pm

Fat chance.

electro · Post by **electro** » Sat Jan 14, 2012 3:47 pm

What is this big attraction to mobile music apps? Wouldn't pros prefer working on an adequately powered desktop or Laptop?

Keebo · Post by **Keebo** » Sat Jan 14, 2012 4:32 pm

electro wrote:What is this big attraction to mobile music apps? Wouldn't pros prefer working on an adequately powered desktop or Laptop?

Prefer, yes. Sometimes it is good or even necessary to be able to work when away from the DAW.

I'm not a pro but mobility is a big attraction to me.

kuniklo · Post by **kuniklo** » Sun Jan 15, 2012 12:03 am

There are two big obstacles here.

First, mobile devices are currently not powerful enough to run most Reaktor patches.

Second, touch screens don't allow for fine enough control to operate the dense and small controls you find in most patches, nevermind actually wiring up patches from scratch.

The first problem will likely disappear eventually as mobile CPUs get faster but the latter is inherent to the devices so I doubt it's likely that NI will undertake a difficult and expensive porting project for something that few users will find satisfying.

Grain Bastard · Post by **Grain Bastard** » Sun Jan 15, 2012 11:16 am

kuniklo wrote:There are two big obstacles here.

First, mobile devices are currently not powerful enough to run most Reaktor patches.

Second, touch screens don't allow for fine enough control to operate the dense and small controls you find in most patches, nevermind actually wiring up patches from scratch.

The first problem will likely disappear eventually as mobile CPUs get faster but the latter is inherent to the devices so I doubt it's likely that NI will undertake a difficult and expensive porting project for something that few users will find satisfying.

I hear that the new ARM processor that is rumored to be in iPad 3 will be equivelent to a mid range core2duo CPU which is plenty fast enough - iPad1 equates to approx G4 Macbook which early Reaktor versions ran fine on. I would have guessed that some SSE stuff is used on todays versions of Reaktor which might cause problems with porting something over to iOS and it could be so far removed that it would require a complete rewrite.

I think your forgetting that the screen can zoom and pan which would allow you to create a functioning interface - agreed that some ensembles as supplied would be too cramped but Reaktor does nothing UI-wise that couldn't be replicated in iOS, imo.

But in general I agree with you mate, I don't think NI will bother and not that many would be interested - the cost would be high too, limiting userbase even further. The fun but ultimately useless iMaschine shows that NI are interested a little with iOS but not THAT interested.....

JavaJ · Post by **JavaJ** » Mon Jan 16, 2012 5:24 am

I disagree. NI wants to monetize whatever so if they could create it and sell expansions they will. They did iMaschine so.....

kuniklo · Post by **kuniklo** » Mon Jan 16, 2012 4:33 pm

JavaJ wrote:I disagree. NI wants to monetize whatever so if they could create it and sell expansions they will. They did iMaschine so.....

Writing something like iMaschine is child's play compared to porting Reaktor. NI would have to be very confident that an iReaktor would sell extremely well to even consider a port. Either that or it would have to be an *very* expensive plugin.

NI should come out with iReaktor