Audiobus: Use your music apps together.

What is Audiobus?Audiobus is an award-winning music app for iPhone and iPad which lets you use your other music apps together. Chain effects on your favourite synth, run the output of apps or Audio Units into an app like GarageBand or Loopy, or select a different audio interface output for each app. Route MIDI between apps — drive a synth from a MIDI sequencer, or add an arpeggiator to your MIDI keyboard — or sync with your external MIDI gear. And control your entire setup from a MIDI controller.

Download on the App Store

Audiobus is the app that makes the rest of your setup better.

monitoring cpu while loopy proing?

Hiho,

What does anyone use to monitor cpu usage while in Loopy Pro?

Cheers

Comments

  • @Bruques said:
    Hiho,

    What does anyone use to monitor cpu usage while in Loopy Pro?

    Cheers

    Now, Loopy Pro offers a CPU or DSP meter, don't you know or does it not offer what you want?

  • (Insert usual note: CPU monitoring in iOS can be misleading. https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing)

  • wimwim
    edited July 2023

    There's a tiny cpu % indicator at the bottom right of the screen. See above for why it's not more prominent.

  • edited July 2023

    @wim said:
    (Insert usual note: CPU monitoring in iOS can be misleading. https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing)

    Ok noted, so nothing like a GUI'd equivalent to ps terminal command (EDIT: top, not ps!), just that procedure for starting with empty project and building up, and practically testing, and noting the percent indicator changes. fair enough

  • @Bruques said:

    @wim said:
    (Insert usual note: CPU monitoring in iOS can be misleading. https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing)

    Ok noted, so nothing like a GUI'd equivalent to ps terminal command (EDIT: top, not ps!), just that procedure for starting with empty project and building up, and practically testing, and noting the percent indicator changes. fair enough

    As noted. in the article wim linked to, the cpu percentage readout is not very meaningful until the cpu is on the verge of overloading. So, noting incremental changes as you add things isn't particularly informative because of how cpu throttling and core assignment works.

  • All that said, AUM has individual node CPU readouts. That to me is useful as it can point out the relative CPU consumption of individual apps. That's what I'd use if trying to find out which apps might be causing overloads.

    The beauty for me with Loopy is the way it can idle plugins. I don't worry much about overloads any more because as soon as I suspect things are beginning to bog down, I can just commit to audio clips and idle the plugins. Because they're still there in the project, I can go back to them at any time to add or change parts. The process is fluid and I barely concern myself with overloads even on my ancient iPad any more.

  • @wim said:
    All that said, AUM has individual node CPU readouts. That to me is useful as it can point out the relative CPU consumption of individual apps. That's what I'd use if trying to find out which apps might be causing overloads.

    The beauty for me with Loopy is the way it can idle plugins. I don't worry much about overloads any more because as soon as I suspect things are beginning to bog down, I can just commit to audio clips and idle the plugins. Because they're still there in the project, I can go back to them at any time to add or change parts. The process is fluid and I barely concern myself with overloads even on my ancient iPad any more.

    Yeah, same, idle in loopy is wonderful. but just keeping an eye on what does what, need to know for gigs to preempt issues, not wait for them to occur mid gig. good shout on using aum to additional test some stuff. cheers

  • @Bruques said:

    @wim said:
    All that said, AUM has individual node CPU readouts. That to me is useful as it can point out the relative CPU consumption of individual apps. That's what I'd use if trying to find out which apps might be causing overloads.

    The beauty for me with Loopy is the way it can idle plugins. I don't worry much about overloads any more because as soon as I suspect things are beginning to bog down, I can just commit to audio clips and idle the plugins. Because they're still there in the project, I can go back to them at any time to add or change parts. The process is fluid and I barely concern myself with overloads even on my ancient iPad any more.

    Yeah, same, idle in loopy is wonderful. but just keeping an eye on what does what, need to know for gigs to preempt issues, not wait for them to occur mid gig. good shout on using aum to additional test some stuff. cheers

    The easiest way to test is to load up seversl instances of likely cpu hogs.

  • @tja said:
    Now, Loopy Pro offers a CPU or DSP meter, don't you know or does it not offer what you want?

    Meter is there but values are sometimes ... weird.

  • wimwim
    edited October 2023

    CPU use is not worth bothering oneself about on iOS except as a very general indicator, and always taken with an understanding of what is really being measured.

    https://wiki.audiob.us/doku.php?id=cpu_load_comparisons_and_testing#why_the_cpu_meters_can_be_misleading

Sign In or Register to comment.