« 5 More Pianos for Colossus Piano | App News | Chordy 2 by Studio Phiz »

WWDC 2017: Aftermath

Now that people have had a chance to explore iOS 11 there are some interesting finds!

The Good:

iOS 11 includes the ability to record the screen natively! There are reports of some bugs with the recordings, but it is a nice first step. Especially coming from the company that has thus far rejected many apps attempting to offer this ability. Unfortunately, in all of the demo videos I've seen there are no on-screen finger taps. This is fine for video game footage, but in tutorials I think it is vital to show on-screen taps. In a complex synth it can be hard to follow exactly what is being done without them.

If they add this feature though, I may never need to jailbreak again!

The Bad:

Yesterday Apple released an update to the iOS version of GarageBand addressing, "stability improvements and bug fixes." This could be a bad omen. The differences between iOS 10 and iOS 11 seem slight, but Apple doesn't update first-party apps very often. That's a hell of a coincidence if they decided to do this one on the day they release iOS 11 to developers.

I don't think it is too much of a stretch to imagine that something in iOS 11 has necessitated this update. We'll have to wait until developers have had some more time with it to see if other apps will need fixes too.

What's new in GarageBand v2.2.2:

This update contains stability improvements and bug fixes.

The Ugly:

In the last several years Apple has been trying to phase out 32-bit support. First with requirements for 64-bit support, then nags built-in to iOS 10. If you're running iOS 10 you've probably read the message, "This app may slow down your iPad." This message when running 32-bit apps was replaced in 10.3 with, "This app will not work with future versions of iOS." In iOS 11 they make good on that promise.

You are not even be able to load 32-bit apps onto a device running iOS 11, and this is not merely a limitation of the beta. The iOS 11 Beta release notes explicitly state 32-bit legacy support will not be returning.

Meanwhile owners of 32-bit devices are going to find they've hit the limit of Apple's support. iPad 4, iPad Mini 1, iPhone 5, and all devices before them, are now out. All of the folks that have doggedly stuck with a trusty iPad 4 are going to find iOS 10 is the limit.

Reader Comments 10

My iTouch5 has been stuck at iOS9, not even able to move to 10. Dunno about the other 32-bit devices, that's my only older device.
June 06, 2017  | person_outline Blaaaarghonaut
So, on one hand, my iPad 4 will at least not be able to load the next OS, and will continue to be able to run 32-bit apps.

On the other hand, my iPod Touch 6 will be able to load the next OS, but won't be able to run 32 bit apps if they are abandoned or not made compatible.

Such goes the march of time.
GB on MacOS had an update as well yesterday: "Remotely add new tracks to your project using GarageBand on your iPhone or iPad". Could be related to the iOS update perhaps?
June 06, 2017  | person huphtur
Thanks for the informative catch-up Tim. The 32-bit obsolescence is a bitter, Bitter pill to swallow.
June 06, 2017  | person_outline Pete
As a musician using apple products it's frustrating that update usually means bugs instead of bug fixes. Theres always some stupid frivolous bullshit they've added for the same kind of people that think fidget spinners are amazing

Wish apple would make an ios device specifically for musicians and music apps. Still run other stuff but I don't need all the Bells and whistles that actually just slow everything down.

I remember Matt who made nanostudio saying that ios cpu won't dedicate much to background audio processing and instead makes UI a priority which means all your big new bad devices can't run moderately simple audio processing. So frustrating. Fuck you apple. Get your shit together

Sorry about the language but I'm bitter about all this
June 06, 2017  | person_outline Harison Zamperla
I remember Matt who made nanostudio saying that ios cpu won't dedicate much to background audio processing and instead makes UI a priority which means all your big new bad devices can't run moderately simple audio processing. So frustrating.

Not sure how long ago this statement was made, but it's simply not true anymore. Recent iOS devices are very capable machines, and can do complex synthesis at ultra low latency, multiple times oversampled without breaking a sweat. There is nothing hampering audio processing in iOS.
June 07, 2017  | touch_app brambos
"Fuck you apple. Get your shit together "
I'd love to take some of the critics back in a time machine to the days before iOS existed.

They could see for themselves how little you could do with mobile music technology. Perhaps we should take their iPads away and force them to use Palm Pilots...? :-)
June 07, 2017  | person_outline Simon
Tim, I think it has to do with the updated API for AUv3 in relations to AU view sizes. They update it now mainly so that developers can test against it.
June 07, 2017  | touch_app Lucas
On June 07, 2017 - @Lucas said:
Tim, I think it has to do with the updated API for AUv3 in relations to AU view sizes. They update it now mainly so that developers can test against it.

Thanks for that tip! This is the first I've heard of changes to the AU view sizes.

Looking forward to GooseEQ BTW! You now have developer flair here.
Haha, Thanks! Hopefully we will be live soon.
June 07, 2017  | touch_app Lucas
comment

  Post a New Comment

Anonymous comments are closed for old articles. If you'd like to comment please Register.

Comment:

Do not use HTML in your comments. Tags: [b] Bold Text [/b] [i] Italic Text [/i]
Links will be generated if you include http:// or https:// at the beginning of a URL.
Submit