Loopy Pro: Create music, your way.

What is Loopy Pro?Loopy Pro is a powerful, flexible, and intuitive live looper, sampler, clip launcher and DAW for iPhone and iPad. At its core, it allows you to record and layer sounds in real-time to create complex musical arrangements. But it doesn’t stop there—Loopy Pro offers advanced tools to customize your workflow, build dynamic performance setups, and create a seamless connection between instruments, effects, and external gear.

Use it for live looping, sequencing, arranging, mixing, and much more. Whether you're a live performer, a producer, or just experimenting with sound, Loopy Pro helps you take control of your creative process.

Download on the App Store

Loopy Pro is your all-in-one musical toolkit. Try it for free today.

Did IPad OS17 break anything?

13»

Comments

  • Nothing in particular I’ve noticed yet.

  • @Poppadocrock said:
    Nothing in particular I’ve noticed yet.

    Just a quick question: do you route any MIDI out of the iPad to anything else via USB? If so, does it work properly?

    My guess is that the problems a couple of us are experiencing haven’t affected a lot of people due to most people just sending MIDI into the iPad from controllers etc - which seems to be fine even with the kit I can’t send out to.

  • @bygjohn said:

    @Poppadocrock said:
    Nothing in particular I’ve noticed yet.

    Just a quick question: do you route any MIDI out of the iPad to anything else via USB? If so, does it work properly?

    My guess is that the problems a couple of us are experiencing haven’t affected a lot of people due to most people just sending MIDI into the iPad from controllers etc - which seems to be fine even with the kit I can’t send out to.

    As I’m at home I tried it - I can route MIDI to the 3 synths I have without any issue. That’s using either a keyboard (via AUM) or MIDI from the piano roll in Zenbeats, all through a USB hub. Each synth expects MIDI on a different channel (1, 2 or 3) and that works as expected.

    I haven’t updated to 17.2 yet though.

  • @michael_m said:

    @bygjohn said:

    @Poppadocrock said:
    Nothing in particular I’ve noticed yet.

    Just a quick question: do you route any MIDI out of the iPad to anything else via USB? If so, does it work properly?

    My guess is that the problems a couple of us are experiencing haven’t affected a lot of people due to most people just sending MIDI into the iPad from controllers etc - which seems to be fine even with the kit I can’t send out to.

    As I’m at home I tried it - I can route MIDI to the 3 synths I have without any issue. That’s using either a keyboard (via AUM) or MIDI from the piano roll in Zenbeats, all through a USB hub. Each synth expects MIDI on a different channel (1, 2 or 3) and that works as expected.

    I haven’t updated to 17.2 yet though.

    That’s interesting and very helpful, thank you.

    I’m still on 17.1.2, which is an update along from the first version that got installed when I set the new iPad up. Which iPad are you using? I ask because I’m wondering if it may just be some models affected - mine is an M2 Pro 11”.

  • @bygjohn said:

    @michael_m said:

    @bygjohn said:

    @Poppadocrock said:
    Nothing in particular I’ve noticed yet.

    Just a quick question: do you route any MIDI out of the iPad to anything else via USB? If so, does it work properly?

    My guess is that the problems a couple of us are experiencing haven’t affected a lot of people due to most people just sending MIDI into the iPad from controllers etc - which seems to be fine even with the kit I can’t send out to.

    As I’m at home I tried it - I can route MIDI to the 3 synths I have without any issue. That’s using either a keyboard (via AUM) or MIDI from the piano roll in Zenbeats, all through a USB hub. Each synth expects MIDI on a different channel (1, 2 or 3) and that works as expected.

    I haven’t updated to 17.2 yet though.

    That’s interesting and very helpful, thank you.

    I’m still on 17.1.2, which is an update along from the first version that got installed when I set the new iPad up. Which iPad are you using? I ask because I’m wondering if it may just be some models affected - mine is an M2 Pro 11”.

    I’m using a 2022 256GB 10.2”

  • @michael_m said:

    @bygjohn said:

    @michael_m said:

    @bygjohn said:

    @Poppadocrock said:
    Nothing in particular I’ve noticed yet.

    Just a quick question: do you route any MIDI out of the iPad to anything else via USB? If so, does it work properly?

    My guess is that the problems a couple of us are experiencing haven’t affected a lot of people due to most people just sending MIDI into the iPad from controllers etc - which seems to be fine even with the kit I can’t send out to.

    As I’m at home I tried it - I can route MIDI to the 3 synths I have without any issue. That’s using either a keyboard (via AUM) or MIDI from the piano roll in Zenbeats, all through a USB hub. Each synth expects MIDI on a different channel (1, 2 or 3) and that works as expected.

    I haven’t updated to 17.2 yet though.

    That’s interesting and very helpful, thank you.

    I’m still on 17.1.2, which is an update along from the first version that got installed when I set the new iPad up. Which iPad are you using? I ask because I’m wondering if it may just be some models affected - mine is an M2 Pro 11”.

    I’m using a 2022 256GB 10.2”

    Thanks, that’s useful to know.

  • You can still play audio over speaker with any of the Aria compacts in 17..2 (this was new in 17.1.1) Possibly other devices.

  • I've noticed issues with deleting files using the Files app. I swipe to delete an old file, then it instantly reappears. This is a really bad one because then I'm not sure if the file is deleted or if I try again I'm actually deleting another file.

  • @NeuM said:
    I've noticed issues with deleting files using the Files app. I swipe to delete an old file, then it instantly reappears. This is a really bad one because then I'm not sure if the file is deleted or if I try again I'm actually deleting another file.

    I'd suggest closing the folder and re-opening it to see if it updates correctly with a full redraw.

  • edited December 2023

    @uncledave said:

    @NeuM said:
    I've noticed issues with deleting files using the Files app. I swipe to delete an old file, then it instantly reappears. This is a really bad one because then I'm not sure if the file is deleted or if I try again I'm actually deleting another file.

    I'd suggest closing the folder and re-opening it to see if it updates correctly with a full redraw.

    Yes, that works temporarily. But it also makes deleting multiple files impossible to confirm without restarting every time.

  • edited December 2023

    Just noticed if you try to add a new wallpaper and lock screen to the iPhone it goes completely haywire in iOS 17 now. A hard restart fixed the issue. Wow. A lot more bugs than I first suspected.

  • @bygjohn said:

    @Poppadocrock said:
    Nothing in particular I’ve noticed yet.

    Just a quick question: do you route any MIDI out of the iPad to anything else via USB? If so, does it work properly?

    My guess is that the problems a couple of us are experiencing haven’t affected a lot of people due to most people just sending MIDI into the iPad from controllers etc - which seems to be fine even with the kit I can’t send out to.

    Nope. Audio in/Audio out & Midi in, either via Bluetooth or sometimes via Audio/Midi interface. I’m dying to get some hardware like the Roland S-1 tweak synth or something small. So yea haven’t tested any midi out, My bad. I haven’t tested my interface sending midi in recently either, now that I think of it… if so that’s a big deal. More often then not I use the Korg nanokey sending Bluetooth midi, I have a few midi keyboards but don’t haven’t a designated work space. This makes it a hassle to always set up. I hope that gets fixed. If I do try soon I’ll report back.

  • @Poppadocrock said:

    @bygjohn said:

    @Poppadocrock said:
    Nothing in particular I’ve noticed yet.

    Just a quick question: do you route any MIDI out of the iPad to anything else via USB? If so, does it work properly?

    My guess is that the problems a couple of us are experiencing haven’t affected a lot of people due to most people just sending MIDI into the iPad from controllers etc - which seems to be fine even with the kit I can’t send out to.

    Nope. Audio in/Audio out & Midi in, either via Bluetooth or sometimes via Audio/Midi interface. I’m dying to get some hardware like the Roland S-1 tweak synth or something small. So yea haven’t tested any midi out, My bad. I haven’t tested my interface sending midi in recently either, now that I think of it… if so that’s a big deal. More often then not I use the Korg nanokey sending Bluetooth midi, I have a few midi keyboards but don’t haven’t a designated work space. This makes it a hassle to always set up. I hope that gets fixed. If I do try soon I’ll report back.

    Thanks!

  • edited December 2023

    Wrong thread

  • edited December 2023

    This is about Mac’s but thought it was interesting

  • No problem here with 17.3 beta in any app I use for music.

  • @bygjohn said:

    @os68ng said:

    TBH! Two out of four ports working beats my other kit, where the outgoing MIDI just disappears into a black hole. The whole thing is crazy, as the devices show up properly in AUM (and NS2), and can send MIDI into the iPad just fine. But nothing gets out to them.

    The midi output enters singularity 🤣 In my case port 3 goes into port 1 and port 4 into port 2. Weird.

    Same here. Just bizarre. I’ve been meaning to contact Apple Support, but preparations for Christmas and other mundane irritations have basically crowded that out for the moment.

    btw. the MIDIflex 4 problem is already under investigation:

    https://nektartech.com/macos-14-sonoma-compatibility/

    We are aware of an issue with port routing the MIDIFlex4 MIDI Interface, which occurs in MacOS 14 (Sonoma). As a result, data which is routed to Port 3 and Port 4 will be passed through Outputs 3 and 4.
    Our contact at Apple has told us that the problem will be addressed in an OS update as it occurs with a number of other MIDI interfaces and controllers.

    (There is a typo in their post: It should be "through Outputs 1 and 2", because otherwise it does not make any sense.)

    It seems that this also affects Sonoma on the Mac 😕 What a luck that I did not update yet :D

    And I have tested it again on the iPad with iOS 17: Still not fixed by any update :neutral:

  • edited February 2024

    With iPadOS/iOS 17.4 beta1, Apple has made an big difference to the Appstore and the purchase history…
    In one way very good, but, one annoying thing concering the search app from purchase history.

    Perhaps Apple will improve this further with 17.4 beta2…

  • @HolyMoses said:
    With iPadOS/iOS 17.4 beta1, Apple has made an big difference to the Appstore and the purchase history…
    In one way very good, but, one annoying thing concering the search app from purchase history.

    Perhaps Apple will improve this furher with 17.4 beta2…

    This may be related to the coming changes to the App Store. Are you in the EU?

  • @uncledave said:

    @HolyMoses said:
    With iPadOS/iOS 17.4 beta1, Apple has made an big difference to the Appstore and the purchase history…
    In one way very good, but, one annoying thing concering the search app from purchase history.

    Perhaps Apple will improve this furher with 17.4 beta2…

    This may be related to the coming changes to the App Store. Are you in the EU?

    Yeah - an EU citizen...

    I'm not a fan of this new EU-thing that we will be able to buy/download apps outside Appstore...

  • @os68ng said:

    @bygjohn said:

    @os68ng said:

    TBH! Two out of four ports working beats my other kit, where the outgoing MIDI just disappears into a black hole. The whole thing is crazy, as the devices show up properly in AUM (and NS2), and can send MIDI into the iPad just fine. But nothing gets out to them.

    The midi output enters singularity 🤣 In my case port 3 goes into port 1 and port 4 into port 2. Weird.

    Same here. Just bizarre. I’ve been meaning to contact Apple Support, but preparations for Christmas and other mundane irritations have basically crowded that out for the moment.

    btw. the MIDIflex 4 problem is already under investigation:

    https://nektartech.com/macos-14-sonoma-compatibility/

    We are aware of an issue with port routing the MIDIFlex4 MIDI Interface, which occurs in MacOS 14 (Sonoma). As a result, data which is routed to Port 3 and Port 4 will be passed through Outputs 3 and 4.
    Our contact at Apple has told us that the problem will be addressed in an OS update as it occurs with a number of other MIDI interfaces and controllers.

    (There is a typo in their post: It should be "through Outputs 1 and 2", because otherwise it does not make any sense.)

    It seems that this also affects Sonoma on the Mac 😕 What a luck that I did not update yet :D

    And I have tested it again on the iPad with iOS 17: Still not fixed by any update :neutral:

    Very interesting. I suspect that more people will have the problem on Macs, which should help bump it up Apple’s priority list.

  • @os68ng said:

    @bygjohn said:

    @os68ng said:

    TBH! Two out of four ports working beats my other kit, where the outgoing MIDI just disappears into a black hole. The whole thing is crazy, as the devices show up properly in AUM (and NS2), and can send MIDI into the iPad just fine. But nothing gets out to them.

    The midi output enters singularity 🤣 In my case port 3 goes into port 1 and port 4 into port 2. Weird.

    Same here. Just bizarre. I’ve been meaning to contact Apple Support, but preparations for Christmas and other mundane irritations have basically crowded that out for the moment.

    btw. the MIDIflex 4 problem is already under investigation:

    https://nektartech.com/macos-14-sonoma-compatibility/

    We are aware of an issue with port routing the MIDIFlex4 MIDI Interface, which occurs in MacOS 14 (Sonoma). As a result, data which is routed to Port 3 and Port 4 will be passed through Outputs 3 and 4.
    Our contact at Apple has told us that the problem will be addressed in an OS update as it occurs with a number of other MIDI interfaces and controllers.

    (There is a typo in their post: It should be "through Outputs 1 and 2", because otherwise it does not make any sense.)

    It seems that this also affects Sonoma on the Mac 😕 What a luck that I did not update yet :D

    And I have tested it again on the iPad with iOS 17: Still not fixed by any update :neutral:

    Update from Nektar: MIDIflex should work now (see link above and the comments on the website). My tests on my iPad were not successful. It could be that there is something like the audio midi manager in iOS but that is not accessible via UI. On macOS it worked by following the instructions on their website. Also on my virgin iPhone. 🤔

  • @os68ng said:

    @os68ng said:

    @bygjohn said:

    @os68ng said:

    TBH! Two out of four ports working beats my other kit, where the outgoing MIDI just disappears into a black hole. The whole thing is crazy, as the devices show up properly in AUM (and NS2), and can send MIDI into the iPad just fine. But nothing gets out to them.

    The midi output enters singularity 🤣 In my case port 3 goes into port 1 and port 4 into port 2. Weird.

    Same here. Just bizarre. I’ve been meaning to contact Apple Support, but preparations for Christmas and other mundane irritations have basically crowded that out for the moment.

    btw. the MIDIflex 4 problem is already under investigation:

    https://nektartech.com/macos-14-sonoma-compatibility/

    We are aware of an issue with port routing the MIDIFlex4 MIDI Interface, which occurs in MacOS 14 (Sonoma). As a result, data which is routed to Port 3 and Port 4 will be passed through Outputs 3 and 4.
    Our contact at Apple has told us that the problem will be addressed in an OS update as it occurs with a number of other MIDI interfaces and controllers.

    (There is a typo in their post: It should be "through Outputs 1 and 2", because otherwise it does not make any sense.)

    It seems that this also affects Sonoma on the Mac 😕 What a luck that I did not update yet :D

    And I have tested it again on the iPad with iOS 17: Still not fixed by any update :neutral:

    Update from Nektar: MIDIflex should work now (see link above and the comments on the website). My tests on my iPad were not successful. It could be that there is something like the audio midi manager in iOS but that is not accessible via UI. On macOS it worked by following the instructions on their website. Also on my virgin iPhone. 🤔

    Hmmm. Nothing had changed when I tested it briefly the other day.

  • I'm on iOS 16.7.2 on my iPad, and now that iOS 18 is out, I'm thinking of updating to iPad OS 17.7 before Apple forces me onto iOS18.

    So, to revive this thread, are there any auv3s that were broken by iPad OS 17 that never recovered?

    I dread updating my iPad for fear of losing music apps :-( but as time goes on app updates only work on newer iOS releases so have to do it periodically.

  • @belldu said:
    I'm on iOS 16.7.2 on my iPad, and now that iOS 18 is out, I'm thinking of updating to iPad OS 17.7 before Apple forces me onto iOS18.

    So, to revive this thread, are there any auv3s that were broken by iPad OS 17 that never recovered?

    I dread updating my iPad for fear of losing music apps :-( but as time goes on app updates only work on newer iOS releases so have to do it periodically.

    In my workflow, everything is fine with iOS 17.7, but it’s freaking impossible for one man to test thousands of apps in all interactions for every host.

    Just tell us the name of the app and host, so we can check it for you. I’ll update to iOS 18 in a week or two.

  • @Luxthor, I'm not worried about the hosts (in my case AUM, Cubasis, Garageband, Notion), but the many auv3s I have. Just wondering if anyone is having issues with iOS 17.7 with any auv3?
    If not, I'll try updating before Apple disable the ability to do so.

  • @belldu said:
    @Luxthor, I'm not worried about the hosts (in my case AUM, Cubasis, Garageband, Notion), but the many auv3s I have. Just wondering if anyone is having issues with iOS 17.7 with any auv3?
    If not, I'll try updating before Apple disable the ability to do so.

    I have no problems using my usual set of apps in iOS 17.7. There were a lot of updates, and many things are fixed. All in all, everything works fine. Regarding hosts, I’m using mainly AUM, dRambo, LP, and LP4i. On the iPhone, it’s Cubasis and Koala. Just close the eyes and YOLO the darn thing. 😂

  • @Luxthor said:

    @belldu said:
    I'm on iOS 16.7.2 on my iPad, and now that iOS 18 is out, I'm thinking of updating to iPad OS 17.7 before Apple forces me onto iOS18.

    So, to revive this thread, are there any auv3s that were broken by iPad OS 17 that never recovered?

    I dread updating my iPad for fear of losing music apps :-( but as time goes on app updates only work on newer iOS releases so have to do it periodically.

    In my workflow, everything is fine with iOS 17.7, but it’s freaking impossible for one man to test thousands of apps in all interactions for every host.

    Just tell us the name of the app and host, so we can check it for you. I’ll update to iOS 18 in a week or two.

    yeah...I definitely haven't tried or opened every app I have since updating to OS 17, but off the top of my head I can't think of anything that made me regret updating....I think the main reason I updated to OS 17 was so I could install Logic Pro for iPad ...but after subscribing to Logic Pro for a year turns out I didn't use it that much...I just use the desktop version like I always have. I dont see myself updating to OS 18 any time soon though...Im on a 2020 non M series iPad Pro...not sure I'd get all the benefits as M series owners would and I didn't see any features that really moved me...at least not any that would benefit audio production ..I'd love to hear your feedback though...especially if you find something that you think would benefit iPad audio producers.

  • @Strizbiz said:

    @Luxthor said:

    @belldu said:
    I'm on iOS 16.7.2 on my iPad, and now that iOS 18 is out, I'm thinking of updating to iPad OS 17.7 before Apple forces me onto iOS18.

    So, to revive this thread, are there any auv3s that were broken by iPad OS 17 that never recovered?

    I dread updating my iPad for fear of losing music apps :-( but as time goes on app updates only work on newer iOS releases so have to do it periodically.

    In my workflow, everything is fine with iOS 17.7, but it’s freaking impossible for one man to test thousands of apps in all interactions for every host.

    Just tell us the name of the app and host, so we can check it for you. I’ll update to iOS 18 in a week or two.

    yeah...I definitely haven't tried or opened every app I have since updating to OS 17, but off the top of my head I can't think of anything that made me regret updating....I think the main reason I updated to OS 17 was so I could install Logic Pro for iPad ...but after subscribing to Logic Pro for a year turns out I didn't use it that much...I just use the desktop version like I always have. I dont see myself updating to OS 18 any time soon though...Im on a 2020 non M series iPad Pro...not sure I'd get all the benefits as M series owners would and I didn't see any features that really moved me...at least not any that would benefit audio production ..I'd love to hear your feedback though...especially if you find something that you think would benefit iPad audio producers.

    How are things going for iOS 18, I’ll definitely wait for 18.1. 😔 Or SWAM update.

Sign In or Register to comment.