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.

SunVox update to v1.9.4 - check it out!!

13»

Comments

  • @Samu it is possible to get sample accurate MIDI timing with plain Virtual MIDI. No IAA, no AUv3. There's just not many devs implementing it correctly. One example of a sample accurate combination is Xequence -> Gadget, no matter the buffer size or load.

  • (NB: Report sent to Mr Zolotov :))

  • @SevenSystems said:
    (NB: Report sent to Mr Zolotov :))

    Thanks, I mean SunVox is still the only 'sampler' on iOS that has multiple interpolation options and in the latest update the new 'noise' is quite close to the 'SID-Noise' that was originally created using a 23-bit shift register :)

    The 'Audio Input' module in SunVox is also missing 'input selection' when using multi-channel audio-interfaces but that's a minor issue.

  • @SevenSystems said:
    @Samu it is possible to get sample accurate MIDI timing with plain Virtual MIDI. No IAA, no AUv3. There's just not many devs implementing it correctly. One example of a sample accurate combination is Xequence -> Gadget, no matter the buffer size or load.

    Maybe Steinberg should hire you to 'fix' their Midi Implementation and maybe they could then also be convinced that 48PPQ is simply ridiculous ;)

    Nice to know at least one working combination but for me personally I prefer 'integrated' solutions (Cubasis / BM3+AUv3, Gadget, SunVox or etc.) and render the output for assembly. I use Freeze in Cubasis all the time.

  • @Samu: yes, integrated solutions are still the optimum way to go in my opinion as well... but tell that to the rest of the Audiobus forum crowd, I can see the stones flying already ;)

  • @SevenSystems said:
    @Samu: yes, integrated solutions are still the optimum way to go in my opinion as well... but tell that to the rest of the Audiobus forum crowd, I can see the stones flying already ;)

    I know, ironically when the AB3.1 update dropped the first thing I tried with it was Pro-Q 2 from Fabfilters and it failed miserably killing all audio from the other apps in the chain. I do hope it will be fixed soon though...

    2 hosts fail the plug-in at the moment AB3.1 and GarageBand. The rest work as expected :)

  • Another big advantage in integrated solutions is that the UI stays consistent and works at all screen sizes, no scaling or scrolling problems... SunVox is a good example of that (getting back on-topic... :D)

  • @SevenSystems said:
    Another big advantage in integrated solutions is that the UI stays consistent and works at all screen sizes, no scaling or scrolling problems... SunVox is a good example of that (getting back on-topic... :D)

    True that, one option that would be nice in SunVox would be to 'maximise' certain areas and 'switch' between views.
    (For example when editing a sample maximise the sample editor to cover the whole screen).

    Would also love to 'swap places' of the sections ie. keep the keyboard at the bottom, have pattern editor on the left and the 'box grid' & 'time-line' to the right with active box-options below it. A 'double tap' on the section dividers to open & close the different sections would make it easier to 'keep a clean working space'.

    Sure on a 1920x1080 screen it's no problem but the Air 2 is like cramped 1024x768 screen in comparison.

  • edited July 2018

    @Samu said:
    Sure on a 1920x1080 screen it's no problem but the Air 2 is like cramped 1024x768 screen in comparison.

    ...and don't even begin to talk about the iPhone ;)

    (I'm not even showing the pattern or timeline editor there!)

    But there's only so much you can do with a 4" screen...

  • @Samu said:

    Now If SunVox was an AUV3 we could potentially have sample-accurate sync.

    May IAA R.I.P. I will not miss it at all...

    Apparently he is working on it!

    http://www.warmplace.ru/forum/viewtopic.php?f=17&t=4370&p=16244&hilit=Jocphone#p16244

    Some extra words of encouragement would possibly help..

  • @Jocphone said:

    @Samu said:

    Now If SunVox was an AUV3 we could potentially have sample-accurate sync.

    May IAA R.I.P. I will not miss it at all...

    Apparently he is working on it!

    http://www.warmplace.ru/forum/viewtopic.php?f=17&t=4370&p=16244&hilit=Jocphone#p16244

    Some extra words of encouragement would possibly help..

    Totally fricking awesome especially now that we have and can use 'almost fullscreen' AUv3's :)

  • edited July 2018

    @Jocphone said:

    @Samu said:

    Now If SunVox was an AUV3 we could potentially have sample-accurate sync.

    May IAA R.I.P. I will not miss it at all...

    Apparently he is working on it!

    http://www.warmplace.ru/forum/viewtopic.php?f=17&t=4370&p=16244&hilit=Jocphone#p16244

    Some extra words of encouragement would possibly help..

    That's great news, always wanted this. :)
    That's going to be amazing hosted in apeMatrix/AUM/AB3

  • Just a heads up on the MIDI timing issue: I had a longer email conversation with NightRadio (Sunvox creator), and the explanation for the inaccurate MIDI timing is somewhat surprising:

    In fact, the MIDI in implementation itself is just fine. HOWEVER, the Sunvox engine internally always quantizes all notes, even those received live via MIDI, to the nearest pattern grid line!

    So, to get the most accurate timing possible when using MIDI in, you have to set the Sunvox project BPM to 800 (the highest possible value). Setting it to the same BPM as your MIDI data source is a good idea in theory, but in practice doesn't work because the two clocks won't be exactly in sync and thus sudden phase shifts by +/- 1 line will occur once every few seconds or minutes.

    NightRadio told me that this limitation will be removed in an update.

  • @SevenSystems said:
    Just a heads up on the MIDI timing issue: I had a longer email conversation with NightRadio (Sunvox creator), and the explanation for the inaccurate MIDI timing is somewhat surprising:

    In fact, the MIDI in implementation itself is just fine. HOWEVER, the Sunvox engine internally always quantizes all notes, even those received live via MIDI, to the nearest pattern grid line!

    So, to get the most accurate timing possible when using MIDI in, you have to set the Sunvox project BPM to 800 (the highest possible value). Setting it to the same BPM as your MIDI data source is a good idea in theory, but in practice doesn't work because the two clocks won't be exactly in sync and thus sudden phase shifts by +/- 1 line will occur once every few seconds or minutes.

    NightRadio told me that this limitation will be removed in an update.

    Thanks for following that up, great that it will get fixed due to your feedback.

  • @SevenSystems said:

    NightRadio told me that this limitation will be removed in an update.

    So all in all SunVox can be treated as a proper 'Sample Player' after all :)
    There's already some quantise settings in the app that can be turned off(Preferences->Recording).

    I always suspected the 'tempo' to be one parameter that could affect the response.
    If/When SunVox gets link BPM could go all the way up to 999.

    Regarding SunVox IAA implementation it can sometimes fail when loaded as an IAA Effect but can be 'fixed' by launching the app first.

    Strangely enough (since I've become a 'touch addict') I'm starting to enjoy the iOS version of SunVox more than the desktop version. Maybe a 'smart cover' will not be such a bad investment after all if I get an iPad Pro at some point :)

Sign In or Register to comment.