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.

AUM Metering

As much as I dig AUM I've always thought it's Achilles heel is it's metering. I have seen it touched on in other threads but the search didn't bring up anything definitive.

We AUM users know it's not necessarily the most accurate metering available in an iOS app, but I'm not 100% sure what it's metering displays. You have the choice of channel in, channel out, speaker/main out, bus out, etc. with the color of the digital metering lanes being changing depending on what is selected.

What is the 2 line indicator on the far right? You'd think it'd be the highest peak indicator but it's often not registering the db's the in's & out's are peaking at. Are the center stereo green lanes when the speaker/main L/R out is selected RMS or peak level?

Some examples below of the metering with Plectrum AU, it easily goes over 0db on input and even with the AUM channel at -4db it spikes into the red, something Plectrum on other hosts (Auria, etc.) hasn't done in my experience. Any tips, explanations, etc. appreciated...be cool.

Comments

  • edited July 2017

    The fader(s) won't have any effect on the displayed signal level coming from the instrument when you're monitoring "Ch___In." So dropping your fader to -4 isn't going to be reflected on the meter when you're monitoring levels in that mode. You could drop it all the way down and it will still show the signal in from your chosen source.
    But tapping the 3 meter dots at the output stage as well as the set next to the instrument icon will change the metering mode. You'll see what mode you're in above the level meters top center. I think that may help out with what you're trying to achieve....?

    We do DESPERATELY need a proper metering app in AU format though. Desperately.

  • @brice said:
    The fader(s) won't have any effect on the displayed signal level coming from the instrument when you're monitoring "Ch___In." So dropping your fader to -4 isn't going to be reflected on the meter when you're monitoring levels in that mode. You could drop it all the way down and it will still show the signal in from your chosen source.
    But tapping the 3 meter dots at the output stage as well as the set next to the instrument icon will change the metering mode. You'll see what mode you're in above the level meters top center. I think that may help out with what you're trying to achieve....?

    We do DESPERATELY need a proper metering app in AU format though. Desperately.

    @Brice I appreciate it brother. I am at times not the best at getting my point across, so my bad as they say.

    I know about AUM's metering selection (you can do the "3 dot meter" method or tap the actual meter to bring up a selection dialog menu), and that pre fader input won't be effected by fader moves. My issue I guess is accuracy & what some of the indicators mean/do.

    You can see on the second photo the green lanes in the meter and two white lines far right that move as well. I thought they were peak indicators at first but no matter what the meter is set to (in/out/etc) they are always well ahead of the lanes and don't correlate with their peaks (i.e. say meter is set to input and peaks register as -5 db on green meter lanes but the white line segments on the right are showing the peaks go well over +0db.)

    I dunno...as you say we need a great AU metering app, and until then I'll check levels in other apps if critical and above all, use my ears...

  • edited July 2017

    Ahhh, okay, now we're on the same page! I think....and I could be completely wrong here...that the 3 dot meters are static in what they're monitoring. And tapping on them will simply change the the master meter input at the top of the screen. Meaning, you could be monitoring the signal coming out of an app / into the fader with the main level meters at the top, but the 3 dots beside the output node will always be measuring that output signal as a safeguard to let you know if you're clipping on the way out, regardless of what you're monitoring with the main meters. Same thing with the 3 dots next to the input node, they will always be monitoring incoming level on their own, but they can also be set to show in the main level meters as well.

    And the value seem to be fairly accurate on this end. At least in this morning's worthless jam session. I've purposely clipped the output via jacking the fader to max, and the over values / level warnings next to the output node share the same peak values displayed in the main meters....as seen here:

    But that is pushed to an extreme obviously. As far as the subtleties you're referring to between dots and meters, I am not so sure of that accuracy. But with AUM's 32-bit floating point bit depth option I suppose we can be a little bit careless with our channels so long as we're not clipping our plugins. But yes, all the more reason we need a proper AU solution.

  • edited July 2017

    @brice said:
    Ahhh, okay, now we're on the same page! I think....and I could be completely wrong here...that the 3 dot meters are static in what they're monitoring. And tapping on them will simply change the the master meter input at the top of the screen. Meaning, you could be monitoring the signal coming out of an app / into the fader with the main level meters at the top, but the 3 dots beside the output node will always be measuring that output signal as a safeguard to let you know if you're clipping on the way out, regardless of what you're monitoring with the main meters. Same thing with the 3 dots next to the input node, they will always be monitoring incoming level on their own, but they can also be set to show in the main level meters as well.

    And the value seem to be fairly accurate on this end. At least in this morning's worthless jam session. I've purposely clipped the output via jacking the fader to max, and the over values / level warnings next to the output node share the same peak values displayed in the main meters....as seen here:

    But that is pushed to an extreme obviously. As far as the subtleties you're referring to between dots and meters, I am not so sure of that accuracy. But with AUM's 32-bit floating point bit depth option I suppose we can be a little bit careless with our channels so long as we're not clipping our plugins. But yes, all the more reason we need a proper AU solution.

    @brice Thanks brother. It really doesn't hamper any kind of creativity and as long as levels aren't screaming it's all good. Take care man...and I am sure your jam was badass. Get a Venus fly trap and if it gets down to the groove, you're in business....

Sign In or Register to comment.