|
Post by uncledave on Nov 15, 2021 18:47:07 GMT
Hi nic, I've noticed that, after my iPad has run for a while, virtual MIDI ports from StreamByter and MidiFire appear, even though the apps are not running, and have not been started since reboot. These ports are visible in Audiobus, AUM, and even Synthmaster 2. Another member in the Audiobus forum was so troubled by this that he removed the offending apps. I don't really care, but I wonder if you need an iOS 15 compatibility update. I'm on iPad 6, with iPadOS 15.1.
Possibly related is that I notice many apps that should not be running, including SB and MF, are present in memory, occupying about 400 pages each. These are visible in a jetsam log. I wonder if the system is starting every app to ask it something, and the apps are wrongly starting services, like virtual ports, that should be deferred. I can send you the logs, if you think they'd help.
Just wanted to let you know.
Cheers, dave
|
|
nic
Soapbox Supremo  
Troublemaker
Press any key to continue
Posts: 2,011
|
Post by nic on Nov 21, 2021 20:07:08 GMT
Hi uncledave , Yeah, I'm aware of it. Seems iOS 15 launches 'most used' apps in the background without warning, to 'speed up' the user experience. None of my MIDI apps expect to be launched in the background so they register their virtual ports and then iOS suspends them. When 'launched' (actually brought to the foreground) all hell breaks loose. So the app fails to launch at all, and you have to force close and restart - not exactly 'quick';-) This can happen at any time, so it appears that MF/SB ports magically appear in other apps as you describe. I am working on how to either tell iOS never to include as a quick launch or figure out how to pick up the pieces when starting after having been launched in the background. When I figure it out, I will submit updates to Apple. Regards, Nic.
|
|
|
Post by uncledave on Nov 22, 2021 0:16:13 GMT
Hi nic, Thats funny, since apps I use very seldom, or even never, seem to be hanging around, including MidiFire actually.
When I first noticed the MF ports (I have 4 enabled), I opened MF and it gave an error connecting to CoreMidi, probably because it collided with "its own" ports already created.
It's not a serious problem for me, but good to know that you're on it.
Cheers, Dave
|
|
|
Post by uncledave on Mar 29, 2022 17:40:17 GMT
This appears to have stopped definitively with iPadOS 15.4. The memory globs associated with these processes are much smaller now, so I guess the system no longer actually causes them to run.
|
|
|
Post by uncledave on May 6, 2022 9:58:50 GMT
But they have returned, not sure why. I logged a SIGABRT from MidiFire, which I had not opened. MF and StreamByter consistently appear in my list of "not running but actually loaded" apps. Strange.
|
|
|
Post by micabeza on May 24, 2022 5:26:26 GMT
nic, have you figured out a solution to your background issue yet? and being new to MF, I assume this is only an issue when iOS launches it in the background, not if I launch it and throw it in the background for an hour (while it is receiving midi that entire hour)?
I'm planing to take my mess of controller scripts and their routings, throw em all in MF, and let that handle the clutter in the background, so I only have to deal with 1 midi input stream in hosts (as opposed to the controller matrix hell I have in AUM now)
|
|