ios 15.1

Daveypoo

@LinearLineman said:
@Daveypoo, I have the same pro. No problems with 15.

Good to know. I'm in the middle of a project so I'll probably hold off until that's done. Appreciate it.

Wrlds2ndBstGeoshredr

I have a 2017 iPad Pro on iOS 13-something. Animoog Z requires at least 14-something. Is there any reason I should not update to 15.1? Otherwise I’ll need a new iPad to use Z.

Edit: Ah, never mind; I just saw that @Daveypoo and @LinearLineman are using my same iPad. Animoog Z here I come!

bbelo

Some USB-C hubs stopped working (might have been present with 15.0 as well).
See also this thread https://discussions.apple.com/thread/253172894?page=2
Mine definetly did FIXED USB-C hub (model FX-1902)

Howard

As discussed here, don't upgrade to iOS 15 if you plan on using any of the Yonac apps in Audiobus 3, Beatmaker 3, Keystage or Camelot Pro. They apparently still work fine though in AUM.

Poppadocrock

I was pretty surprised that only iPhone 12 and later can go to iOS 15. I know this happens eventually but they skipped a lot of phone releases from iOS 14.8 to 15.1.

0tolerance4silence

@Poppadocrock said:
I was pretty surprised that only iPhone 12 and later can go to iOS 15. I know this happens eventually but they skipped a lot of phone releases from iOS 14.8 to 15.1.

?
My 6s+ is eligible for the update... am I missing something?

LinearLineman

I’m also having a problem updating an iPhone 6s, too, only it says it won’t update because not enough storage (needs 3.6 gigs). I’ve stripped the apps and photos and it still has under 3 gigs available. The phone is 16 gbs… and the Apple shit is around 13 gb by itself. WTF?!

Is connecting to a computer the only way? Is it because the OS has gotten a lot bigger over the yrs? Thx.

Gdub

iPhone 11 running iOS 15 no problem here

0tolerance4silence

@LinearLineman said:
I’m also having a problem updating an iPhone 6s, too, only it says it won’t update because not enough storage (needs 3.6 gigs). I’ve stripped the apps and photos and it still has under 3 gigs available. The phone is 16 gbs… and the Apple shit is around 13 gb by itself. WTF?!

Is connecting to a computer the only way? Is it because the OS has gotten a lot bigger over the yrs? Thx.

Imo it’s more about the way files are handled... a delete is rarely an actual delete... check recently deleted folders around and empty those as well to free up space... you may also try to transfer stuff temporarily to another device.

cyberheater

My iPad Pro (2nd Gen) keeps trying to update to 15.1 but keeps failing. No idea why.

[Deleted User]

The user and all related content has been deleted.

Daveypoo

Ok, finally updated yesterday. All seems to be well.

Bob

@bbelo said:
Some USB-C hubs stopped working (might have been present with 15.0 as well).
See also this thread https://discussions.apple.com/thread/253172894?page=2
Mine definetly did FIXED USB-C hub (model FX-1902)

Same here, after a desperate upgrade to IOS 15.1 hoping to fix the current Mixbox nightmare, my hub can’t connect to my audio interface. Totaly stuck now....

j_liljedahl

@NeonSilicon said:

@Samu said:

@NeonSilicon said:

I don't have either so I can't test them unfortunately. I'll go check the release notes, but those have been pretty useless as far telling what has been fixed over the last couple of years.

Should be enough to check if there's some AUv3 related fixes?

Not really. The beta release notes almost never have any information about what has been changed or fixed in the audio stuff. The initial beta for iOS 15 had a note that AU's now provide custom views that could be displayed by the host. I think they actually meant that some of the builtin AU's now had UI's, but it was poorly worded.

From what I've understood is that effect plug-ins with midi support can no longer return 'null' or something like that?!

The only host I have where the plug-ins fail is Cubasis 3. They work without issues in all the others...
So it's either a Cubasis 3 issue or iOS15.x issue as the plug-ins apparently work under iOS14 and Cubasis 3.

That's interesting because Cubasis 3 may be the only host that is doing custom things with the interaction with the AU render block. I'm thinking this because Cubasis 3 does some multithreading and they may need to control some of this interaction outside of the default path. It may end up being an interaction between two or three of the parties and that can lead to some pretty hard to fix bugs.

I think the problem is Cubasis does not support MIDI outputs from AUv3 effects. So it sets the midiOutBlock to nil. But iOS 15 changed this to ”not nullable” and the nil is not passes on to the plugin, instead it gets a garbage pointer that crashes when used.

So, an iOS bug triggered by a missing feature in Cubasis.

NeonSilicon

@j_liljedahl said:

@NeonSilicon said:

@Samu said:

@NeonSilicon said:

I don't have either so I can't test them unfortunately. I'll go check the release notes, but those have been pretty useless as far telling what has been fixed over the last couple of years.

Should be enough to check if there's some AUv3 related fixes?

Not really. The beta release notes almost never have any information about what has been changed or fixed in the audio stuff. The initial beta for iOS 15 had a note that AU's now provide custom views that could be displayed by the host. I think they actually meant that some of the builtin AU's now had UI's, but it was poorly worded.

From what I've understood is that effect plug-ins with midi support can no longer return 'null' or something like that?!

The only host I have where the plug-ins fail is Cubasis 3. They work without issues in all the others...
So it's either a Cubasis 3 issue or iOS15.x issue as the plug-ins apparently work under iOS14 and Cubasis 3.

That's interesting because Cubasis 3 may be the only host that is doing custom things with the interaction with the AU render block. I'm thinking this because Cubasis 3 does some multithreading and they may need to control some of this interaction outside of the default path. It may end up being an interaction between two or three of the parties and that can lead to some pretty hard to fix bugs.

I think the problem is Cubasis does not support MIDI outputs from AUv3 effects. So it sets the midiOutBlock to nil. But iOS 15 changed this to ”not nullable” and the nil is not passes on to the plugin, instead it gets a garbage pointer that crashes when used.

So, an iOS bug triggered by a missing feature in Cubasis.

This is still kinda weird to me. Both the docs and the header files show midiOutputEventListBlock and midiOutputEventBlock as optionals under Swift and nullable under iOS 15. Are these the properties that are the issue? If they are, then did Apple just mess up the implementation and set them to a bad pointer or is the problem really in Cubasis 3 and it's setting the property to a bad address?

j_liljedahl

@NeonSilicon said:

@j_liljedahl said:

@NeonSilicon said:

@Samu said:

@NeonSilicon said:

I don't have either so I can't test them unfortunately. I'll go check the release notes, but those have been pretty useless as far telling what has been fixed over the last couple of years.

Should be enough to check if there's some AUv3 related fixes?

Not really. The beta release notes almost never have any information about what has been changed or fixed in the audio stuff. The initial beta for iOS 15 had a note that AU's now provide custom views that could be displayed by the host. I think they actually meant that some of the builtin AU's now had UI's, but it was poorly worded.

From what I've understood is that effect plug-ins with midi support can no longer return 'null' or something like that?!

The only host I have where the plug-ins fail is Cubasis 3. They work without issues in all the others...
So it's either a Cubasis 3 issue or iOS15.x issue as the plug-ins apparently work under iOS14 and Cubasis 3.

That's interesting because Cubasis 3 may be the only host that is doing custom things with the interaction with the AU render block. I'm thinking this because Cubasis 3 does some multithreading and they may need to control some of this interaction outside of the default path. It may end up being an interaction between two or three of the parties and that can lead to some pretty hard to fix bugs.

I think the problem is Cubasis does not support MIDI outputs from AUv3 effects. So it sets the midiOutBlock to nil. But iOS 15 changed this to ”not nullable” and the nil is not passes on to the plugin, instead it gets a garbage pointer that crashes when used.

So, an iOS bug triggered by a missing feature in Cubasis.

This is still kinda weird to me. Both the docs and the header files show midiOutputEventListBlock and midiOutputEventBlock as optionals under Swift and nullable under iOS 15. Are these the properties that are the issue? If they are, then did Apple just mess up the implementation and set them to a bad pointer or is the problem really in Cubasis 3 and it's setting the property to a bad address?

This is what I’ve heard from Bram. I don’t have the iOS 15 headers installed (old Xcode) so can’t check, but maybe it’s different in the obj-c headers?

Or maybe it is nullable, but an iOS bug gives a bad address if nulled, or indeed Cubasis are setting a bad address from the start.

NeonSilicon

@j_liljedahl said:

@NeonSilicon said:

@j_liljedahl said:

@NeonSilicon said:

@Samu said:

@NeonSilicon said:

I don't have either so I can't test them unfortunately. I'll go check the release notes, but those have been pretty useless as far telling what has been fixed over the last couple of years.

Should be enough to check if there's some AUv3 related fixes?

Not really. The beta release notes almost never have any information about what has been changed or fixed in the audio stuff. The initial beta for iOS 15 had a note that AU's now provide custom views that could be displayed by the host. I think they actually meant that some of the builtin AU's now had UI's, but it was poorly worded.

From what I've understood is that effect plug-ins with midi support can no longer return 'null' or something like that?!

The only host I have where the plug-ins fail is Cubasis 3. They work without issues in all the others...
So it's either a Cubasis 3 issue or iOS15.x issue as the plug-ins apparently work under iOS14 and Cubasis 3.

That's interesting because Cubasis 3 may be the only host that is doing custom things with the interaction with the AU render block. I'm thinking this because Cubasis 3 does some multithreading and they may need to control some of this interaction outside of the default path. It may end up being an interaction between two or three of the parties and that can lead to some pretty hard to fix bugs.

I think the problem is Cubasis does not support MIDI outputs from AUv3 effects. So it sets the midiOutBlock to nil. But iOS 15 changed this to ”not nullable” and the nil is not passes on to the plugin, instead it gets a garbage pointer that crashes when used.

So, an iOS bug triggered by a missing feature in Cubasis.

This is still kinda weird to me. Both the docs and the header files show midiOutputEventListBlock and midiOutputEventBlock as optionals under Swift and nullable under iOS 15. Are these the properties that are the issue? If they are, then did Apple just mess up the implementation and set them to a bad pointer or is the problem really in Cubasis 3 and it's setting the property to a bad address?

This is what I’ve heard from Bram. I don’t have the iOS 15 headers installed (old Xcode) so can’t check, but maybe it’s different in the obj-c headers?

Or maybe it is nullable, but an iOS bug gives a bad address if nulled, or indeed Cubasis are setting a bad address from the start.

Thanks for the info!

I don't know about the Obj-C headers. I was looking at the headers in a project that I did with the AU interface in Swift. I should try to trace it in one from an Obj-C based AUAudioUnit and see if there are any differences. I've been working under the assumption that the Swift interfaces were autogenerated from the underlying Obj-C headers. I could easily be wrong there.

I'll do some playing around and see if I might be able to figure out what's going on. I'm working on a MIDI sequencer related project that has an outside chance of eventually hosting MIDI effects. So, I don't want to do anything now that's going to make it difficult to add/fix later.

tk32

@Samu said:
In total I've gone thru ~250 apps on my iPad Air 2 and just a few have issues when loaded to hosts but no real 'show stoppers'.

250 apps tested!! I thank the stars we have users as dedicated as you in our ranks.

Samu

@tk32 said:

@Samu said:
In total I've gone thru ~250 apps on my iPad Air 2 and just a few have issues when loaded to hosts but no real 'show stoppers'.

250 apps tested!! I thank the stars we have users as dedicated as you in our ranks.

That is what I usually do when 'major' iOS updates drop and give each installed app a launch and check if they still connect to most hosts I have. (Currently I have a grand total of 280 apps installed on my iPad Air 2, that includes 'everything').

This way I have at least a clue on how 'severe' the eventual 'update-damage' is.
(One of the motivators to install iPadOS15 was to be able to do beta on Mela 2 and well the improved multi-tasking etc.).

There might be some 'glitches' but if most stuff works somewhat ok I'm usually quite forgiving
(IAA connection issues are 99.9% solved by launching the app first before making any connections).

If something goes totally south and a quick re-install doesn't solve it and the app is at least a little important to me I tend to get pretty 'vocal' haha...(MixB... is the worst f'kup during my 10+ years on iOS/iPadOS!)

iOS/iPadOS15.2 is due next week so I guess some glitches will likely be fixed.

Cheers!

tk32

Sending you a cold beer @Samu

🍺

bbelo

@Bob said:

@bbelo said:
Some USB-C hubs stopped working (might have been present with 15.0 as well).
See also this thread https://discussions.apple.com/thread/253172894?page=2
Mine definetly did FIXED USB-C hub (model FX-1902)

Same here, after a desperate upgrade to IOS 15.1 hoping to fix the current Mixbox nightmare, my hub can’t connect to my audio interface. Totaly stuck now....

iPadOS15.2 fixes this
Everything works now, yay 😀