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.

Nembrini Audio - The Voltour Valve Enhancer (overdrive/distortion)

13»

Comments

  • dendydendy

    39 instances on M1 AIR , same consitions like on my iPhone XS MAX test

  • dendydendy
    edited September 2023

    interestingly, also 39 instamces of Saturn (with 3 bands enabled/active) on that M1 air
    (again same conditions, same total load around 73%)

  • dendydendy
    edited September 2023

    just to put thing in perspective, on that M1 ipad i can run 8 instamces of Model D (playing 1 note in default preset) with 80% of CPU load

    also don't forget Nanostudio uses just single core so in Logic or Cubasis you will be able to run 2x or 3x as much instances based on your cpu type

    logic has no precise CPU meter but i was able to run around 21 instamces of Modl D and cpu meter was showing something approximately around 80%.. not going to test it with Voltour, i do not have time for adding probably 100+ instances :-))))

  • LuxthorLuxthor

    @espiegel123 said:

    @Luxthor said:

    @espiegel123 said:

    @Luxthor said:

    I’ve made a normal usage environment; all four instances were working when the screenshot was taken. What you are saying is a proper heavy load test. I agree with everything said; please make one. ;)

    The situation is that those CPU numbers don’t really tell you anything reliably meaningful about cpu intensive need of a plugin when the CPU is not under a heavy load because of the way CPU throttling and real-time core reallocation work.

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

    I know that, as does everyone else on the forum. I still think that values taken from normal projects and considering device age and power can help someone in need to know at least approximately CPU usage.
     
    Or should we ignore those requests and move on?

    The point is that those numbers aren’t meaningful. It isn’t that they give a sense of the cpu usage in non-heavy load situations. They don’t even give a meaningful sense on normal situations. So, yeah, I would say ignore those requests unless one has a meaningful comparison.

    As @Birdpie said, how many instances of an AU can you take in AUM till the CPU maxes out (starts crackling)? Considering nothing else works in the background, I bet those numbers will vary anyway. But it is indeed the only option.
     
    I did a test with Zeeon on the M2 iPad Pro; the normal ‘E’ core did 7%; the high-performance ‘P’ core did 4%; it’s pretty much consistent with 1% deviation, and this is enough for my needs.
     
    For example, it’s easy to say VAPoly takes double the power of VAMono, and VAPoly16 takes double the power of VAPoly. So you can conclude that VAPoly16 is pretty hungry. But what should you say for PhaseMonkey?
     
    The best way is to make our internal measurement system.
     
    Three major groups for CPU power consumption regarding specific devices, host sample rates, etc. will be divided by the maximum instances before audio starts to crackle:
     

    • Light (24 max instances)
    • Moderate (12 max instances)
    • Heavy (6 max instances)

    So we can say that on the iPad Pro M2, Zeeon is light on CPU power.

  • espiegel123espiegel123

    The thing is that those numbers don’t necessarily tell you what you think they do.

  • LuxthorLuxthor

    @espiegel123 said:
    The thing is that those numbers don’t necessarily tell you what you think they do.

    No one cares for those exact numbers; they're arbitrary by the system anyway. We just need to find the best way to communicate.

  • LuxthorLuxthor

    @dendy said:
    interestingly, also 39 instamces of Saturn (with 3 bands enabled/active) on that M1 air
    (again same conditions, same total load around 73%)

    All FabFilter plugins are light, even on my MacBook Pro i7. I don’t know what I would do without them. ;)

  • GavinskiGavinski

    Short demo on Twitter with a chance to win a free copy of any Nembrini app. This really does sound good btw!

    https://x.com/gavinski_s/status/1702026108064121234?s=61&t=h9IT_HLFyi9pwn2iXlMGDQ

  • waka_xwaka_x

    finally got it!:)
    such a wild beast.
    I love it.

  • ZerozerozeroZerozerozero

    They may stop supporting your device though. Had a couple of their apps do this. Hopefully they won’t all go this way. I’m sure some peoples experience of Nembrini is fine. Mine wasn’t. Just to be aware.

  • wimwim

    @Zerozerozero said:
    They may stop supporting your device though. Had a couple of their apps do this. Hopefully they won’t all go this way. I’m sure some peoples experience of Nembrini is fine. Mine wasn’t. Just to be aware.

    What device and OS version is that?

  • ZerozerozeroZerozerozero

    17.3.1 iPhone 12.
    There’s a thread with others confirming.
    Lots of emails back and forth supplying videos etc.

  • kirmesteggnokirmesteggno

    @Zerozerozero said:
    17.3.1 iPhone 12.
    There’s a thread with others confirming.
    Lots of emails back and forth supplying videos etc.

    What's their reasoning?

  • ZerozerozeroZerozerozero

    @kirmesteggno said:

    @Zerozerozero said:
    17.3.1 iPhone 12.
    There’s a thread with others confirming.
    Lots of emails back and forth supplying videos etc.

    What's their reasoning?

    They couldn’t replicate issue so no fix

  • kirmesteggnokirmesteggno

    @Zerozerozero said:

    @kirmesteggno said:

    @Zerozerozero said:
    17.3.1 iPhone 12.
    There’s a thread with others confirming.
    Lots of emails back and forth supplying videos etc.

    What's their reasoning?

    They couldn’t replicate issue so no fix

    That sucks. Did you try to request a refund from Apple pointing to the issue?

  • espiegel123espiegel123

    @Zerozerozero said:

    @kirmesteggno said:

    @Zerozerozero said:
    17.3.1 iPhone 12.
    There’s a thread with others confirming.
    Lots of emails back and forth supplying videos etc.

    What's their reasoning?

    They couldn’t replicate issue so no fix

    That doesn’t mean they stopped supporting it just that they haven’t been able to reproduce the issue — which can make it difficult to solve. I understand that if you are experiencing a problem that it might feel like the developer isn’t supporting you , but the developer may want to solve the problem but can’t because they can’t make it happen.

  • kirmesteggnokirmesteggno

    @espiegel123 said:

    @Zerozerozero said:

    @kirmesteggno said:

    @Zerozerozero said:
    17.3.1 iPhone 12.
    There’s a thread with others confirming.
    Lots of emails back and forth supplying videos etc.

    What's their reasoning?

    They couldn’t replicate issue so no fix

    That doesn’t mean they stopped supporting it just that they haven’t been able to reproduce the issue — which can make it difficult to solve. I understand that if you are experiencing a problem that it might feel like the developer isn’t supporting you , but the developer may want to solve the problem but can’t because they can’t make it happen.

    In a way its understandable, if only one or two users have this problem and you can't replicate it it could be too expensive depending on your schedule to have someone or yourself researching the issue for days if not weeks.

  • ZerozerozeroZerozerozero

    Yeah, may not have enough resources etc to warrant looking into/fixing.
    obviously won’t risk buying any more apps from them though.
    Was just to make other buyers aware.
    Pitfalls of being a phone user..

Sign In or Register to comment.

© Vanilla Keystone Theme 2024