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.

DRC's background activity was causing "phantom" noise on iPad Pro 10.5

2»

Comments

  • sinosoidalsinosoidal

    @j_liljedahl said:

    @brambos said:

    @j_liljedahl said:
    When an app is started by IAA, it will not be visible in the task manager until the app has manually or programatically been moved to foreground at least once.

    Lolwut? That does explain the zombie-problem indeed. But what sort of bizarro thought-process could have possibly led to that decision? They're knowingly initiating an unstoppable audio rendering process? :o

    Well, an IAA node app that was started by an IAA host would in normal cases stop its audio engine when disconnected from the host - thus it won't actually be running in the background, only keep a zombie process that makes further IAA activity fail until the user manually launches and terminates the app.

    However, there are a couple of cases where it could actually still be running, draining battery or make eerie noises:

    • A programming mistake makes the app not stop its engine upon IAA disconnection.
    • The IAA host does not correctly disconnect its nodes when terminated (manually by user or by crashing).
    • Or, the host does try to disconnect its nodes, but it was hosting more than 4 or so IAA nodes. In this case, only a few of them will be disconnected before iOS determines that the host takes too long to close, and thus terminating it fully before it had chance to disconnect all remaining nodes! (Yeah, ain't that great?) This is the reason Audiobus3 has the "Clear Session" action. Also it means that in AUM you should tap "CLEAR" in the menu before swiping away AUM from the task manager, if you had IAA nodes loaded.

    Wow... this is wicked!

  • sinosoidalsinosoidal
    edited January 2018

    @j_liljedahl I was able to replicate what you have just described by opening Audiobus, choosing DRC as a node and then terminating Audiobus by swiping it in the Task manager. I have then checked on Xcode the list of processes running in background and DRC was there and there was no task manager entry for it.

    Question: is there any way an app has to proactively check if it is connected to a valid node or not, in order to shutdown it self or terminate the audio engine in order to save battery? Thx!

  • mrcanistermrcanister

    does this still happen if you close the host app and then swipe out DRC? i don't know what xcode is, but that's what i usually do with modstep and bm3.
    i came up with a lovely patch the other day, like a slightly overdriven e piano type sound with a bit of mod on the reverb. sounds lovely.
    AU would be sweet

  • sinosoidalsinosoidal

    @mrcanister it seems that sometimes people have a ghost DRC that is not listed in task manager eating CPU in background. This might happen when a inter app audio host such as Audiobus opens the app and then doesn't close it properly. Have you had similar problems?

    I have been investigating the possible cases and it seems that this is only possible if a host like Audiobus gets closed, DRC GUI was not even open and DRC background audio setting is enabled. Host session is terminated, DRC is notified, but since it has the background audio setting enabled it keeps the audio engine working in background and there is no GUI to close it.

  • sinosoidalsinosoidal
    edited January 2018

    @johnfromberkeley I'm uploading a beta of DRC to hopefully sort this issue out. Do you mind trying it out? Is anyone else suffering from the same issue?

    From my investigation I have concluded that one possible case was:

    • DRC was started by Audiobus (or any other IAA host)
    • DRC GUI was not even open
    • Host was terminated but DRC background audio setting was enabled
    • DRC would stay in background

    I'm now ignoring background audio setting when DRC is notified by the host that the session is terminated. This means that if DRC is in background and it was on a IAA session, the audio engine will be terminated.

    It would be awesome to have feedback from real world usage at this point.

  • j_liljedahlj_liljedahl

    @sinosoidal said:
    @johnfromberkeley I'm uploading a beta of DRC to hopefully sort this issue out. Do you mind trying it out? Is anyone else suffering from the same issue?

    From my investigation I have concluded that one possible case was:

    • DRC was started by Audiobus (or any other IAA host)
    • DRC GUI was not even open
    • Host was terminated but DRC background audio setting was enabled
    • DRC would stay in background

    I'm now ignoring background audio setting when DRC is notified by the host that the session is terminated. This means that if DRC is in background and it was on a IAA session, the audio engine will be terminated.

    It would be awesome to have feedback from real world usage at this point.

    Yes, this is the correct way to do it. A "background audio" user toggle should only be used when the app runs stand-alone, not connected to a host. A typical node app (such as a synth or effect) should stop its audio engine (and thus stop running in background) when disconnected from host.

  • BiancaNeveBiancaNeve

    @brambos said:

    @j_liljedahl said:
    When an app is started by IAA, it will not be visible in the task manager until the app has manually or programatically been moved to foreground at least once.

    Lolwut? That does explain the zombie-problem indeed. But what sort of bizarro thought-process could have possibly led to that decision? They're knowingly initiating an unstoppable audio rendering process? :o

    I think at the time IAA was launched the idea was it would save memory not loading the GUI etc

  • johnfromberkeleyjohnfromberkeley

    For the record, everyone should buy DRC. This issue will get resolved, and it’s a great sounding synth.

    @sinosoidal - How do I test the beta? Do you need my TestFlight email?

  • sinosoidalsinosoidal

    @johnfromberkeley said:
    For the record, everyone should buy DRC. This issue will get resolved, and it’s a great sounding synth.

    @sinosoidal - How do I test the beta? Do you need my TestFlight email?

    Yes please, send me a private message with it! Thx!!!

  • mrcanistermrcanister

    @sinosoidal
    yes, i've noticed this but not just with DRC tho. this after thinking i'd found The way to avoid this happening!
    i've noticed that sometimes when i open a standalone the gui will appear for split second and the app will then load up.
    i was under the impression that this was a systemic issue with standalones? still a bit of a novice with ios, deciding what's the best way for me to have everything setup.
    quality synth. the clock is really solid too

Sign In or Register to comment.

© Vanilla Keystone Theme 2025