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.

New Art Kerns app midiFILTr-pg is live

2»

Comments

  • @artkerns said:
    Hey, I'll fix this iPhone audio problem. In the mean time you might be able to work around it by plugging in headphones if your phone has an audio jack, or putting the synths you're using in to the audio part of Audiobus 2 or 3. Not sure exactly what is causing the problem but it seems to be iPhone speaker and/or audio rate related. midiFILTr doesn't generate audio but has to set some things up to work properly with background audio, core midi, and Audiobus. Probably something is being set up wrong with the iPhone when AB isn't being used.

    Thanks. I've tried everything. Multiple reinstalls, resets, lots of different apps. Always the same.

    Why would this only effect my iPhone SE and not the Air 2 using the same apps?

  • Again, the workarounds would be plugging in headphones to an iPhone wth an audio jack, or inserting the synths you're using into the audio chain of Audiobus. Those are the workarounds I have that work. Otherwise yes you'll get the bug.

    The iPhone started using a different audio system/chip with the 5se and 6, 48kHz instead of 44.1kHz for the speakers is what I can see but I think there's more to it, it crops up in weird places like this. On my iPhone 6S where I verified the bug, when midiFILTr-PG is started the audio switches from speakers on one side of the phone to the other. Why? I have no idea, separate system sound speaker maybe? I probably have legacy code in the app that relies on things being 44.1kHz that I didn't even notice and it messes something up.

    This is one of the reasons I hesistate to port things to iPhone. The different models have different screen sizes, quirks between generations, etc. Ends up being more work than its worth unless the app is very simple, like this one, and even then I'm learning a lesson about that right now ;). Ipad for whatever reason is a lot more consistent.

  • @artkerns said:
    Again, the workarounds would be plugging in headphones to an iPhone wth an audio jack, or inserting the synths you're using into the audio chain of Audiobus. Those are the workarounds I have that work. Otherwise yes you'll get the bug.

    The iPhone started using a different audio system/chip with the 5se and 6, 48kHz instead of 44.1kHz for the speakers is what I can see but I think there's more to it, it crops up in weird places like this. On my iPhone 6S where I verified the bug, when midiFILTr-PG is started the audio switches from speakers on one side of the phone to the other. Why? I have no idea, separate system sound speaker maybe? I probably have legacy code in the app that relies on things being 44.1kHz that I didn't even notice and it messes something up.

    This is one of the reasons I hesistate to port things to iPhone. The different models have different screen sizes, quirks between generations, etc. Ends up being more work than its worth unless the app is very simple, like this one, and even then I'm learning a lesson about that right now ;). Ipad for whatever reason is a lot more consistent.

    Hi Art, I was using headphones when I was testing on SE and was working ok just that I'd often have to switch midiFILTr-PG to the foreground or else it would eventually disconnect after about 25 seconds or so.

    Tried with xynthesizr with Drc and mitosynth.

  • That's interesting, not sure why it'd do that. I'll try to figure it out and fix it.

  • @artkerns said:
    Again, the workarounds would be plugging in headphones to an iPhone wth an audio jack, or inserting the synths you're using into the audio chain of Audiobus. Those are the workarounds I have that work. Otherwise yes you'll get the bug.

    The iPhone started using a different audio system/chip with the 5se and 6, 48kHz instead of 44.1kHz for the speakers is what I can see but I think there's more to it, it crops up in weird places like this. On my iPhone 6S where I verified the bug, when midiFILTr-PG is started the audio switches from speakers on one side of the phone to the other. Why? I have no idea, separate system sound speaker maybe? I probably have legacy code in the app that relies on things being 44.1kHz that I didn't even notice and it messes something up.

    This is one of the reasons I hesistate to port things to iPhone. The different models have different screen sizes, quirks between generations, etc. Ends up being more work than its worth unless the app is very simple, like this one, and even then I'm learning a lesson about that right now ;). Ipad for whatever reason is a lot more consistent.

    Well, I'm glad you went universal with it. Likely the reason I bought it too.

    With apps like this that I don't really need, but look interesting to use, being universal often closes the deal for me.

    Cool app by the way. I'll be using it a lot more than I'd originally anticipated. I like that you can subtly dial in just the right amount of change in the probability while still maintaining musicality. Glad I bought it. :)

  • Yep it's really good :)

  • @artkerns just tested recent update, and the iPhone problem seems to be fixed. All good. Thanks! :

Sign In or Register to comment.