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.

GeoShredControl now clashes with other GeoShred apps...

2»

Comments

  • @Simon said:

    @Gavinski said:
    Great detailed response Pat.

    +1.

    Thank you Pat.

    I followed your video step-by-step and still had problems - I couldn't even see GeoShred Control listed in my AUM until I deleted GeoShred Pro from my iPad.

    Once I did this I was able to select GeoShred Control and load it into AUM and it worked fine.

    I think before the update this might not have been the case - before the update I think you could have both apps, Pro and Control, installed on one device without any clash.

    Anyway, thank you for taking the time to investigate and get back to us so quickly.

    Could this confusion be due to a change to the AUv3 AudioComponentDescription identifiers used by the two apps? Perhaps they now appear as the same app, where they were previously different.

  • @moForte Thanks for the detailed response. I definitely wasn't mistaken in that it disappeared as an installable auv3 and having put it back on my device, I saw the following.
    1. In AUM it was now using GeoShred Play for my saved session previously using GeoShredControl.
    2. GeoShredControl was not in the midi controller list in AUM
    3. I have it as a standalone app



    I was mistaken though in that it was actually GeoShredPlay that was asking for the upgrade.

    But from the responses of others above I think I know what went wrong here...

    To test the theory I deleted GeoShredPlay and GeoShredControl, and then reinstalled GeoShredControl.
    This fixed it, as shown below...

    So my conclusion is that the update has applied the same internal app identifiers for multiple GeoShred apps. This confused AUM which for me loaded GeoShredPlay which wanted an upgrade as soon as it opened in AUM and because the identifier is the same, it only showed GeoShredPlay in the MIDI controller list.
    I had to delete both of them (deleting just GeoShredPlay wasn't enough), then just reinstall GeoShredControl to get it to work again.

  • @uncledave said:

    @Simon said:

    @Gavinski said:
    Great detailed response Pat.

    +1.

    Thank you Pat.

    I followed your video step-by-step and still had problems - I couldn't even see GeoShred Control listed in my AUM until I deleted GeoShred Pro from my iPad.

    Once I did this I was able to select GeoShred Control and load it into AUM and it worked fine.

    I think before the update this might not have been the case - before the update I think you could have both apps, Pro and Control, installed on one device without any clash.

    Anyway, thank you for taking the time to investigate and get back to us so quickly.

    Could this confusion be due to a change to the AUv3 AudioComponentDescription identifiers used by the two apps? Perhaps they now appear as the same app, where they were previously different.

    ...and while I was typing and screenshotting, @uncledave has likely found the identifiers that I'd bet are now set to the same value for multiple GeoShred apps.

  • Here is part of an email Pat sent me, which I don't think he'll mind me posting here:

    'If you have more than one GeoShred on your device, then which plugin is found by a host is non-deterministic, because All GeoShreds share the same AUv3 plugin interface ID. This is by design so that users who start from one GeoShred and decide to switch to another GeoShred (Control, get rid of Control and switch to Pro) will be able to run all their projects. That is, if you started from Control (orange icon) and got rid of Control and switched to Pro (Green Icon), then as long as you delete Control, reboot your device to re-index the system wide AUv3 plugins, then all your old DAW, AUM projects will now be using Pro (Green Icon). This is explained in the following FAQ:

    https://www.moforte.com/geoShredAssets5932/help/FAQs/index.html#multipleGeoShreds

    I just did a test with BOTH GeoShred Pro and GeoShred Control on my device, even though I just installed Control, AUM sees GeoShred Pro as the "Audio Unit MIDI Processor". Deleting Pro and rebooting, coming back to AUM, now AUM sees GeoShred Control as the "Audio Unit MIDI Processor".'

  • edited March 2023

    @belldu said:

    @uncledave said:

    @Simon said:

    @Gavinski said:
    Great detailed response Pat.

    +1.

    Thank you Pat.

    I followed your video step-by-step and still had problems - I couldn't even see GeoShred Control listed in my AUM until I deleted GeoShred Pro from my iPad.

    Once I did this I was able to select GeoShred Control and load it into AUM and it worked fine.

    I think before the update this might not have been the case - before the update I think you could have both apps, Pro and Control, installed on one device without any clash.

    Anyway, thank you for taking the time to investigate and get back to us so quickly.

    Could this confusion be due to a change to the AUv3 AudioComponentDescription identifiers used by the two apps? Perhaps they now appear as the same app, where they were previously different.

    ...and while I was typing and screenshotting, @uncledave has likely found the identifiers that I'd bet are now set to the same value for multiple GeoShred apps.

    Sorry, I don't have the tech to do that. But we've had other identifier confusions lately: see MixBox CS and Bs-16.

    Edit: And, once again, the description of the GeoShredPlay upgrade describes AUv3 plug-in support (i.e. hosting), not AUv3 functionality. Maybe the wording is not clear enough, causing confusion.

  • @belldu said:
    ...and while I was typing and screenshotting, @uncledave has likely found the identifiers that I'd bet are now set to the same value for multiple GeoShred apps.

    uncledave is a very clever lad. His tech advice is always worthwhile.

  • Ok, so I think everything is known now. Previously I had GeoShredControl recognised in AUM and GeoShredPlay in standalone. This worked fine.
    Then when the apps updated it got itself in a mess and defaulted to GeoShredPlay in AUM instead, which i mistook for GeoShredControl, as they look identical when open (to my untrained eyes), and GeoShredPlay immediately displayed an IAP prompt.

    I now understand that you can only have one GeoShred app, as even if you take care the first time to install them in an order that works, any app updates could mess it up.

    Updating apps shouldn't cause these issues, its bad design, but equally I understand the limitations that led to that design and the desire to provide upgrade path to GeoShredPro.

    Mystery solved, thanks all.

  • @Simon said:

    @rs2000 said:
    On my later iDevice running iOS 16.3.1, the AUv3 isn't even listed under MIDI Processor plugins. (Standalone works.)

    Do you have GeoShred Pro also installed on the same device?

    No.

  • @BiancaNeve said:
    For £7 a month you can compose in am/C or for just £5 Either Gb major pentatonic or Eb minor :neutral:

    Borrowed chords will attract an interest rate of 24.5% per month.

  • @Simon said:

    @Gavinski said:
    Great detailed response Pat.

    +1.

    Thank you Pat.

    I followed your video step-by-step and still had problems - I couldn't even see GeoShred Control listed in my AUM until I deleted GeoShred Pro from my iPad.

    Once I did this I was able to select GeoShred Control and load it into AUM and it worked fine.

    I think before the update this might not have been the case - before the update I think you could have both apps, Pro and Control, installed on one device without any clash.

    Anyway, thank you for taking the time to investigate and get back to us so quickly.

    If you have more than one GeoShred on your device, then which plugin is found by a host is non-deterministic, because All GeoShreds share the same AUv3 plugin interface ID. This is by design so that users who start from one GeoShred and decide to switch to another GeoShred (Control, get rid of Control and switch to Pro) will be able to run all their projects. That is, if you started from Control (orange icon) and got rid of Control and switched to Pro (Green Icon), then as long as you delete Control, reboot your device to re-index the system wide AUv3 plugins, then all your old DAW, AUM projects will now be using Pro (Green Icon). This is explained in the following FAQ:

    https://www.moforte.com/geoShredAssets5932/help/FAQs/index.html#multipleGeoShreds

    My offer stands that if anyone on this thread is having this problem, please reach out to me either with "Menu> Help> Report a Problem" or a direct email to [email protected]. I'm willing to setup a zoom call for anyone who is having challenges getting GeoShred Control to work as an Auv3 plugin.

    Thanks,

    Pat Scandalis, CEO/CTO
    moForte inc the developer of GeoShred.

  • @rs2000 said:

    Thanks, that sounds good but then something else seems to be wrong.
    On my old iPad with a previous version of GeoShred Control installed, the AUv3 shows up properly.
    On my later iDevice running iOS 16.3.1, the AUv3 isn't even listed under MIDI Processor plugins. (Standalone works.)

    Please reach out to me directly and we can setup a zoom call. If you have only one GeoShred installed and you have rebooted your device so that iOS will re-index the system wide AUv3 plugins, then it should work. Let me know when a good time for you is to look at this and I'm sure we can solve it in short order.

    Thanks,
    -pat

    Pat Scandalis, CEO/CTO
    moForte inc the developer of GeoShred.

  • You continue to deliver support above and beyond your peers, Pat. Thanks!

  • edited March 2023

    @moForte said:

    @rs2000 said:

    Thanks, that sounds good but then something else seems to be wrong.
    On my old iPad with a previous version of GeoShred Control installed, the AUv3 shows up properly.
    On my later iDevice running iOS 16.3.1, the AUv3 isn't even listed under MIDI Processor plugins. (Standalone works.)

    Please reach out to me directly and we can setup a zoom call. If you have only one GeoShred installed and you have rebooted your device so that iOS will re-index the system wide AUv3 plugins, then it should work. Let me know when a good time for you is to look at this and I'm sure we can solve it in short order.

    Thank you, a reboot fixed it indeed!
    There's another issue I've found with GeoShred Play though: After updating the app to the latest version, it has "forgotten" its SWAM TenorSax IAP and "Restore Purchases" gave me the status message "Nothing available to restore".
    I had this happen before about half a year ago, on a different iDevice.
    So yet another reboot and another try - but this time to no avail. It still won't restore my previously available IAP.
    This is on an iPhone, iOS 16.3.1.
    And yes, I’m logged in with the same Apple ID as before.

  • There's another issue I've found with GeoShred Play though: After updating the app to the latest version, it has "forgotten" its SWAM TenorSax IAP and "Restore Purchases" gave me the status message "Nothing available to restore".
    I had this happen before about half a year ago, on a different iDevice.
    So yet another reboot and another try - to no avail. It still won't restore my previously available IAP.
    This is on an iPhone, iOS 16.3.1.
    And yes, I’m logged in with the same Apple ID as before.

    If you are logged in on your device using the same AppleID that made the purchase, then this is likely bug that was introduced by Apple in iOS 16 in Sept/2022: StoreKit Restoration does not always work. It has something to do with the servers that deliver receipts to apps. We have a bug filed with Apple about this, and our internal contact at Apple confirmed that's it's a "known issue" at Apple. It was not only GeoShred, but lots of other apps including the Moog Apps. They mostly addressed it over the past 6 months, but there are still some outliers.

    Generally deleting GeoShred (Play in your case) reinstalling it from scratch and going to "Menu> Store" and tapping on "Restore Purchases" addresses it. Be sure to backup your personal presets with "Menu> Files> Export" so that you can restore them with "Menu> FIles> Import".

    Also again be sure that you don't have multiple GeoShreds. If you do have multiple GeoShreds and you really feel that you need both, reach out to me directly and we can come up with a solution for you to have a single GeoShred. ([email protected])

    Let me know how this goes,

    Thanks,

    -pat

    Pat Scandalis, CEO/CTO
    moForte inc the developer of GeoShred.

  • Thank you very much @moForte for getting in touch and helping me resolve the issue.

    Happy to confirm what @NeuM said, that's outstanding support and I hope that Apple get their issues fixed soon.
    It must be a nightmare for developers to take care of issues that turn out not to be under their control.

Sign In or Register to comment.