|
|
Post by uncledave on Dec 11, 2020 0:01:52 GMT
I created a script that uses a slider parameter to control calculations. It checks for the SyEx message to know when the parameter is changed. This works fine in stand-alone, but when StreamByter is AUv3 in AudioBus3, the script never receives the message. This is in iPadOS 14.2. I tried the same test on my iPad Air with iOS 12.4.7, and it works fine in the same configuration. So it may be due to a change in iPadOS 14.2.
|
|
nic
Soapbox Supremo 
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Dec 12, 2020 10:42:46 GMT
Hi uncledave , iOS14.2 has broken MIDI in terms of sysex messages. Sending a sysex message to CoreMIDI causes a straight up crash in the sending app. I wasn't aware that it was broken in AU also, but I guess something wrong there too. It's to do with changes Apple have made in wrapping CoreMIDI calls to some new API. Channelised/real-time messages work fine - it is just sysex. I read somewhere that it is slated to be fixed in 14.3 but I guess we will see. Note it works in standalone as the sysex message is passed inside the app itself and doesn't go near the Apple code. Regards, Nic. |
|
|
|
Post by uncledave on Jan 5, 2021 2:13:28 GMT
Hi Nic, Thanks for your reply. I have 14.3 and it's still the same. Other devs have reported similar issues in the AudioBus forum, caused by changes to the Apple MIDI classes. Bit of a bummer when Apple makes changes that profoundly affect end users and devs, while they don't really care. When a menu item is changed, I need to call a function to update some parameters, which would be smooth if the Sysex message ever arrived. My work-around is to Install Rules after adjusting, since the initialization code calls the function to init the parameters. It's OK for me because these adjustments are infrequent. Maybe 14.4 will be the charm  Cheers, Dave |
|
|
|
Post by espiegel123 on Apr 3, 2021 15:11:55 GMT
nic: any chance that you will address this so that the StreamByter ui items will work in iOS 14. The issue didn’t go away in iOS 14.3 when Apple fixed the core midi bug that caused crashes. Hi uncledave , iOS14.2 has broken MIDI in terms of sysex messages. Sending a sysex message to CoreMIDI causes a straight up crash in the sending app. I wasn't aware that it was broken in AU also, but I guess something wrong there too. It's to do with changes Apple have made in wrapping CoreMIDI calls to some new API. Channelised/real-time messages work fine - it is just sysex. I read somewhere that it is slated to be fixed in 14.3 but I guess we will see. Note it works in standalone as the sysex message is passed inside the app itself and doesn't go near the Apple code. Regards, Nic. |
|
|
|
Post by uncledave on Apr 3, 2021 15:23:39 GMT
Hi espiegel123, Thanks for chiming in on this one. I'm on iPadOS 14.4.2 now and still no change. I have a work-around for my specific case (very infrequent adjustments), but it's still annoying. And I just happened to try it on my iPad Air, frozen on iOS 12.5.2; works perfectly. I realized then that I'd never actually seen my script work correctly, because it displays the parameter value in the bottom bar when it updates, which I'd never seen. |
|
|
|
Post by uncledave on Jun 10, 2021 13:44:29 GMT
This is fixed in the new SB 1.10, at least with iPadOS 14.6. Gui changes immediately trigger the code conditioned on the sysex message. Excellent.
I had been having trouble seeing modules on iCloud updating between devices. I noticed iCloud updating as soon as I opened it, so it looks like that's fixed also.
Thanks for these.
|
|
