Apollo midi controller & iOS / iPadOS13?

MarkH

Does anyone know first hand if Apollo works okay on ipad os 13? I have been holding off updating but would like to try now.

wim

It worked in a quick test from iPhone 7s on iOS 13.2 to iPad Air 2 iOS 12.3.1.

I see no use for Apollo anymore since Bluetooth MIDI connects between my devices with any hosts I need it to without it now. For those hosts that don't, I just use Audiobus to connect the devices and pass along the midi.

MarkH

@wim said:
It worked in a quick test from iPhone 7s on iOS 13.2 to iPad Air 2 iOS 12.3.1.

I see no use for Apollo anymore since Bluetooth MIDI connects between my devices with any hosts I need it to without it now. For those hosts that don't, I just use Audiobus to connect the devices and pass along the midi.

Thanks. Yes, with further experiments I can meet my immediate (app to app) needs with a direct BT connection. I am still new to all this so it's quite confusing

wim

Yeh, sure is confusing. Don't hesitate to ask questions. There's always someone around here that's been through the same process.

MarkH

@wim said:
Yeh, sure is confusing. Don't hesitate to ask questions. There's always someone around here that's been through the same process.

Here is a question, or pehaps an observation that I don't understand. I am connecting Animoog to Parat+ and I notice that when using Apollo, somehow Animoog remembers my CC mappings. When I connect directly over Bluetooth it doesn't (unless I use the Save function, of course). How come?

wim

@MarkH said:

@wim said:
Yeh, sure is confusing. Don't hesitate to ask questions. There's always someone around here that's been through the same process.

Here is a question, or pehaps an observation that I don't understand. I am connecting Animoog to Parat+ and I notice that when using Apollo, somehow Animoog remembers my CC mappings. When I connect directly over Bluetooth it doesn't (unless I use the Save function, of course). How come?

Just a guess, but I think that's because Animoog remembers connections to other apps that are local on the device. To it, Apollo looks like just any other app, and it's Apollo that's doing the magic Bluetooth stuff. Animoog doesn't even know it's ultimately communicating over Bluetooth.

It could also be that Apollo is keeping its "Virtual Port" to Animoog alive even if it's not connected to anything via Bluetooth. If you force-quit Apollo, and/or reboot your device, that cc mapping might disappear.

iOS handles Bluetooth MIDI connections differently than other connections. For instance, you have to re-initiate the Bluetooth connection to a NanoKEY Studio manually every time, even though other Bluetooth connections auto connect.

MarkH

@wim said:

@MarkH said:

@wim said:
Yeh, sure is confusing. Don't hesitate to ask questions. There's always someone around here that's been through the same process.

Here is a question, or pehaps an observation that I don't understand. I am connecting Animoog to Parat+ and I notice that when using Apollo, somehow Animoog remembers my CC mappings. When I connect directly over Bluetooth it doesn't (unless I use the Save function, of course). How come?

It could also be that Apollo is keeping its "Virtual Port" to Animoog alive even if it's not connected to anything via Bluetooth. If you force-quit Apollo, and/or reboot your device, that cc mapping might disappear.

No, it seems to have a very long memory. I tried closing apps and then I tried rebooting both iPads but in each case it remembers the CC mapping. I guess Apollo is doing this for each MIDI destination.

MarkH

@MarkH said:

@wim said:

@MarkH said:

@wim said:
Yeh, sure is confusing. Don't hesitate to ask questions. There's always someone around here that's been through the same process.

Here is a question, or pehaps an observation that I don't understand. I am connecting Animoog to Parat+ and I notice that when using Apollo, somehow Animoog remembers my CC mappings. When I connect directly over Bluetooth it doesn't (unless I use the Save function, of course). How come?

It could also be that Apollo is keeping its "Virtual Port" to Animoog alive even if it's not connected to anything via Bluetooth. If you force-quit Apollo, and/or reboot your device, that cc mapping might disappear.

No, it seems to have a very long memory. I tried closing apps and then I tried rebooting both iPads but in each case it remembers the CC mapping. I guess Apollo is doing this for each MIDI destination.

Actually I have decided this is Animoog remembering the last configuration, not Apollo

MarkH

@MarkH said:
Does anyone know first hand if Apollo works okay on ipad os 13? I have been holding off updating but would like to try now.

I got a reply from the developer to say he has tested a number of iOS 13 devices and it seems okay. I have now checked it out on iPadOS 13 and it seems to work fine.

MarkH

@MarkH said:

@MarkH said:

@wim said:

@MarkH said:

@wim said:
Yeh, sure is confusing. Don't hesitate to ask questions. There's always someone around here that's been through the same process.

Here is a question, or pehaps an observation that I don't understand. I am connecting Animoog to Parat+ and I notice that when using Apollo, somehow Animoog remembers my CC mappings. When I connect directly over Bluetooth it doesn't (unless I use the Save function, of course). How come?

It could also be that Apollo is keeping its "Virtual Port" to Animoog alive even if it's not connected to anything via Bluetooth. If you force-quit Apollo, and/or reboot your device, that cc mapping might disappear.

No, it seems to have a very long memory. I tried closing apps and then I tried rebooting both iPads but in each case it remembers the CC mapping. I guess Apollo is doing this for each MIDI destination.

Actually I have decided this is Animoog remembering the last configuration, not Apollo. I think this may be what you (@wim) said