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.

SUNRIZER is now ((AU<3)) - - - In the AppStore!!! ... (Free Update) - - - [Classic Synth!]

1…1011121315

Comments

  • wimwim
    edited September 2021

    @NeuM said:

    @wim said:

    @NeuM said:
    Guess I’m the only person here who ever uses GarageBand on iOS or desktop?

    Works in GarageBand on iOS for me. I use GarageBand on desktop, but can't test as I don't have an M1 Mac.

    As I mentioned earlier, I think it’s because I downloaded the “trial” version of the desktop software just days before that it is now preventing me from using the iOS download version on my M1 iMac. But this is what’s happening even after I discarded the trial software… clearly there’s some kind of residual file which prevents the new software to override the old trial preferences. But I’m at a complete loss as to what I can do about it now.

    Hoping there's some kind of solution @giku_beepstreet will be able to offer.

    GarageBand will rebuild it's plugin database if you delete the AudioUnit Cache folder: ~/Library/Caches/AudioUnitCache. It's probably advisable to reboot your Mac after doing this. Next time you enter GarageBand it'll rebuild the folder.

    That worked for me in an earlier situation with a different app.

    Another good AU test is to try Ableton Live. I've had more than one plugin that doesn't work in GarageBand but does work in Live Lite (free). That would at least narrow it down to whether it's a GarageBand specific issue.

  • NeuMNeuM
    edited September 2021

    @wim said:

    @NeuM said:

    @wim said:

    @NeuM said:
    Guess I’m the only person here who ever uses GarageBand on iOS or desktop?

    Works in GarageBand on iOS for me. I use GarageBand on desktop, but can't test as I don't have an M1 Mac.

    As I mentioned earlier, I think it’s because I downloaded the “trial” version of the desktop software just days before that it is now preventing me from using the iOS download version on my M1 iMac. But this is what’s happening even after I discarded the trial software… clearly there’s some kind of residual file which prevents the new software to override the old trial preferences. But I’m at a complete loss as to what I can do about it now.

    Hoping there's some kind of solution @giku_beepstreet will be able to offer.

    GarageBand will rebuild it's plugin database if you delete the AudioUnit Cache folder: ~/Library/Caches/AudioUnitCache. It's probably advisable to reboot your Mac after doing this. Next time you enter GarageBand it'll rebuild the folder.

    That worked for me in an earlier situation with a different app.

    Another good AU test is to try Ableton Live. I've had more than one plugin that doesn't work in GarageBand but does work in Live Lite (free). That would at least narrow it down to whether it's a GarageBand specific issue.

    Just checked and there is no AudioUnitCache. Perhaps things changed in Big Sur for the M1 Macs?

    @giku_beepstreet ... Is there an uninstaller for the trial version of Sunrizer?

  • wimwim
    edited September 2021

    @NeuM said:
    Just checked and there is no AudioUnitCache. Perhaps things changed in Big Sur for the M1 Macs?

    Did you go to /Library, or <user>/Library? It's in <user>/Library. If you open Finder then select Go>Library, you should get to the right place.

    I'm on Big Sur as well. The OS doesn't operate differently depending on the processor, so the cache should be there.

  • RobertFernandesRobertFernandes

    Thank you @giku_beepstreet ! You’re one of my favorite developers!

    I also get the same crash as @NeuM and I hadn’t installed the demo version before, I just installed the full version which I had bought for the iPad.

    Mac M1, GarageBand.

  • NeuMNeuM
    edited September 2021

    @RobertFernandes said:
    Thank you @giku_beepstreet ! You’re one of my favorite developers!

    I also get the same crash as @NeuM and I hadn’t installed the demo version before, I just installed the full version which I had bought for the iPad.

    Mac M1, GarageBand.

    Aha. Thanks for confirming the crash error. This helps to narrow down possible reasons for the crash.

    Also, just out of curiosity, could you search your system to see if you have a "AudioUnitCache" file in your Library folder, either the User or System locations?

  • NeuMNeuM
    edited September 2021

    @wim said:

    @NeuM said:
    Just checked and there is no AudioUnitCache. Perhaps things changed in Big Sur for the M1 Macs?

    Did you go to /Library, or <user>/Library? It's in <user>/Library. If you open Finder then select Go>Library, you should get to the right place.

    I'm on Big Sur as well. The OS doesn't operate differently depending on the processor, so the cache should be there.

    Not there under User or in the System Library. And I've performed mutiple system wide searches using the entire word "AudioUnitCache" and even just "AudioUnit" and there is no such cache file.

    I should also note I have never before seen these particular error messages with any other plugins or apps.

  • espiegel123espiegel123

    @NeuM said:

    @wim said:

    @NeuM said:
    Just checked and there is no AudioUnitCache. Perhaps things changed in Big Sur for the M1 Macs?

    Did you go to /Library, or <user>/Library? It's in <user>/Library. If you open Finder then select Go>Library, you should get to the right place.

    I'm on Big Sur as well. The OS doesn't operate differently depending on the processor, so the cache should be there.

    Not there under User or in the System Library. And I've performed mutiple system wide searches using the entire word "AudioUnitCache" and even just "AudioUnit" and there is no such cache file.

    I should also note I have never before seen these particular error messages with any other plugins or apps.

    Files and directories in /Library and ~/Library don't show up in seaches done with Spotlight or Finder (unless you have done something tricky that enables such a capability)

    Did you go to ~/Library/Caches?

    AudioUnitCache is a folder in that directory. I.e. ~/Library/Caches/AudioUnitCache/

    To confirm that such a folder doesn't exist, in the Finder choose Go/Go To Folder

    and paste

    ~/Library/Caches/AudioUnitCache/

    into the text field

  • NeuMNeuM
    edited September 2021

    @espiegel123 said:

    @NeuM said:

    @wim said:

    @NeuM said:
    Just checked and there is no AudioUnitCache. Perhaps things changed in Big Sur for the M1 Macs?

    Did you go to /Library, or <user>/Library? It's in <user>/Library. If you open Finder then select Go>Library, you should get to the right place.

    I'm on Big Sur as well. The OS doesn't operate differently depending on the processor, so the cache should be there.

    Not there under User or in the System Library. And I've performed mutiple system wide searches using the entire word "AudioUnitCache" and even just "AudioUnit" and there is no such cache file.

    I should also note I have never before seen these particular error messages with any other plugins or apps.

    Files and directories in /Library and ~/Library don't show up in seaches done with Spotlight or Finder (unless you have done something tricky that enables such a capability)

    Did you go to ~/Library/Caches?

    AudioUnitCache is a folder in that directory. I.e. ~/Library/Caches/AudioUnitCache/

    To confirm that such a folder doesn't exist, in the Finder choose Go/Go To Folder

    and paste

    ~/Library/Caches/AudioUnitCache/

    into the text field

    That did it. And the contents of the AudioUnitCache is "com.apple.audiounits.sandboxed.cache"

    OK... I threw out the cache folder, restarted, checked the Caches folder and it did rebuild a new one.... but then started GarageBand, added a new track, tried to use Sunrizer as an AUv3 and got the following. So it was a good idea, but the issue does not appear to be in the cache:

  • wimwim

    @NeuM said:

    @espiegel123 said:

    @NeuM said:

    @wim said:

    @NeuM said:
    Just checked and there is no AudioUnitCache. Perhaps things changed in Big Sur for the M1 Macs?

    Did you go to /Library, or <user>/Library? It's in <user>/Library. If you open Finder then select Go>Library, you should get to the right place.

    I'm on Big Sur as well. The OS doesn't operate differently depending on the processor, so the cache should be there.

    Not there under User or in the System Library. And I've performed mutiple system wide searches using the entire word "AudioUnitCache" and even just "AudioUnit" and there is no such cache file.

    I should also note I have never before seen these particular error messages with any other plugins or apps.

    Files and directories in /Library and ~/Library don't show up in seaches done with Spotlight or Finder (unless you have done something tricky that enables such a capability)

    Did you go to ~/Library/Caches?

    AudioUnitCache is a folder in that directory. I.e. ~/Library/Caches/AudioUnitCache/

    To confirm that such a folder doesn't exist, in the Finder choose Go/Go To Folder

    and paste

    ~/Library/Caches/AudioUnitCache/

    into the text field

    That did it. And the contents of the AudioUnitCache is "com.apple.audiounits.sandboxed.cache"

    OK... I threw out the cache folder, restarted, checked the Caches folder and it did rebuild a new one.... but then started GarageBand, added a new track, tried to use Sunrizer as an AUv3 and got the following. So it was a good idea, but the issue does not appear to be in the cache:

    This might get a little more attention in the Beepstreet forum if you haven't already tried there. http://forum.beepstreet.com/discussions

  • NeuMNeuM
    edited September 2021

    @wim said:

    @NeuM said:

    @espiegel123 said:

    @NeuM said:

    @wim said:

    @NeuM said:
    Just checked and there is no AudioUnitCache. Perhaps things changed in Big Sur for the M1 Macs?

    Did you go to /Library, or <user>/Library? It's in <user>/Library. If you open Finder then select Go>Library, you should get to the right place.

    I'm on Big Sur as well. The OS doesn't operate differently depending on the processor, so the cache should be there.

    Not there under User or in the System Library. And I've performed mutiple system wide searches using the entire word "AudioUnitCache" and even just "AudioUnit" and there is no such cache file.

    I should also note I have never before seen these particular error messages with any other plugins or apps.

    Files and directories in /Library and ~/Library don't show up in seaches done with Spotlight or Finder (unless you have done something tricky that enables such a capability)

    Did you go to ~/Library/Caches?

    AudioUnitCache is a folder in that directory. I.e. ~/Library/Caches/AudioUnitCache/

    To confirm that such a folder doesn't exist, in the Finder choose Go/Go To Folder

    and paste

    ~/Library/Caches/AudioUnitCache/

    into the text field

    That did it. And the contents of the AudioUnitCache is "com.apple.audiounits.sandboxed.cache"

    OK... I threw out the cache folder, restarted, checked the Caches folder and it did rebuild a new one.... but then started GarageBand, added a new track, tried to use Sunrizer as an AUv3 and got the following. So it was a good idea, but the issue does not appear to be in the cache:

    This might get a little more attention in the Beepstreet forum if you haven't already tried there. http://forum.beepstreet.com/discussions

    I might do that, but considering the developer (or someone acting on their behalf) posts here regularly, I thought this would be the best first option. Thanks for your assistance, though. I appreciate it.

  • giku_beepstreetgiku_beepstreet
    edited September 2021

    Ok, it's a shame, but I haven't tested this with GarageBand on OsX, Logic only. A quick test: none of AUv3 ios plugins work in GB on M1, tested: Fractal Bits, Spacecraft and EG. I will try to debug it, but it seems like GB / OsX on M1 thing. (no problems in Logic)

  • wimwim

    GB sucks for ported AU's even on non M1 Macs. I can get ones specifically developed for Mac, such as Synthmaster One, to work, but others generally don't.

    I think it has something to do with it only supporting AU's not AUv3 unless they have specific bridging code built in. Or something.

  • NeuMNeuM
    edited September 2021

    @giku_beepstreet said:
    Ok, it's a shame, but I haven't tested this with GarageBand on OsX, Logic only. A quick test: none of AUv3 ios plugins work in GB on M1, tested: Fractal Bits, Spacecraft and EG. I will try to debug it, but it seems like GB / OsX on M1 thing. (no problems in Logic)

    Thanks for looking into this very aggravating issue. And it's good to see it's apparently nothing specific to your app, but one of Apple's own macOS / M1 bugs perhaps. Glad to see it was not just my computer with the problem. ;)

  • mlaumlau

    i noticed that at 2048 ( buffer size ) sunrizer is behaving strangely - on a sonic level - and zeeon is not loading at all … i am on ipad pro 11 ( 2018 ) 14.7.1

  • giku_beepstreetgiku_beepstreet

    @mlau said:
    i noticed that at 2048 ( buffer size ) sunrizer is behaving strangely - on a sonic level - and zeeon is not loading at all … i am on ipad pro 11 ( 2018 ) 14.7.1

    I'm gonna check this. Thanks

  • mlaumlau

    @giku_beepstreet said:

    @mlau said:
    i noticed that at 2048 ( buffer size ) sunrizer is behaving strangely - on a sonic level - and zeeon is not loading at all … i am on ipad pro 11 ( 2018 ) 14.7.1

    I'm gonna check this. Thanks

    if it can help i play in 48/24

  • giku_beepstreetgiku_beepstreet

    I can confirm that GB / iOS Auv3 issues are fixed on OsX 12.00 (beta)

  • SamuSamu

    @giku_beepstreet said:
    I can confirm that GB / iOS Auv3 issues are fixed on OsX 12.00 (beta)

    So in less than a month this 'issue' will be gone granted that users keep their system up-to-date :sunglasses:

  • giku_beepstreetgiku_beepstreet

    @Samu said:

    @giku_beepstreet said:
    I can confirm that GB / iOS Auv3 issues are fixed on OsX 12.00 (beta)

    So in less than a month this 'issue' will be gone granted that users keep their system up-to-date :sunglasses:

    There is a Logic behind ;)

  • SylaarSylaar

    I think my comment got buried… haha

    My preset banks aren't alphabetized. I'm running m1 ipad pro, and iPad Air.

    Also, when mono is selected, the internal keyboard doesn't seem to play correctly. Playing notes beside each other cuts off the sound. For instance, if I play C, and slide to D, the sound cuts off, but then sliding to E the sound comes back, sliding to F cuts off the sound. Using an external keyboard or AUM keyboard, no issues.

    Any ideas?

  • wimwim
    edited September 2021

    @Sylaar said:
    I think my comment got buried… haha

    My preset banks aren't alphabetized. I'm running m1 ipad pro, and iPad Air.

    They're not alphabetized on iOS either. I wasn't aware this was a feature. Could be Doug was misinformed.

  • MAtrixplanMAtrixplan

    @giku_beepstreet said:
    btw. There are many great 3rd party banks made for the grandpa.. e.g.

    Anyone knows where to download this bank? It looks it’s not available anymore. And I purchased Sunrizer today (not regretting ;) ) mostly for this bank.

  • SylaarSylaar

    Thanks @wim!

    Anyone else experiencing the 'solo/mono' in-app keyboard issue?

  • NoiseFlooredNoiseFloored

    @Sylaar said:
    Anyone else experiencing the 'solo/mono' in-app keyboard issue?

    Yep, though it also happens to me with Drambo's keyboard

  • wimwim
    edited September 2021

    Kinda makes sense when you think about the mechanics of using a mouse vs. a touch screen. I imagine there could need to be some special mouse handling routine for a click-drag to work in the same way as a touch. Probably Apple never built that into their libraries.

  • NeuMNeuM

    @wim said:
    Kinda makes sense when you think about the mechanics of using a mouse vs. a touch screen. I imagine there could need to be some special mouse handling routine for a click-drag to work in the same way as a touch. Probably Apple never built that into their libraries.

    No, I’m pretty sure Apple has that covered.

  • SylaarSylaar

    I'm using an ipad touch screen though, isn't that what Sunrizer was built on?

  • NeuMNeuM

    @Sylaar said:
    I'm using an ipad touch screen though, isn't that what Sunrizer was built on?

    They’ve also sold a Mac version of their synth for some time.

  • SylaarSylaar

    I see, thank you. Well I'll just continue to use the Aum or external keyboards until it's fixed!

  • wimwim
    edited September 2021

    @Sylaar said:
    I'm using an ipad touch screen though, isn't that what Sunrizer was built on?

    sorry, I misread your post. Odd - I don't see that behavior. Which patch or patches can I try to see if it's related to the patch?

Sign In or Register to comment.

© Vanilla Keystone Theme 2025