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.

Discovery synth by DiscoDSP is coming to iPad

2

Comments

  • FPCFPC
    edited September 19

    @dendy said:

    @FPC said:

    @Samu said:
    Now we're talking!

    OB-Xd V3 shaped up to be pretty nice after a few initial quirks and I'm quite sure we don't get these 'growing pains' when Discovery finally drops :)

    Do you have this on desktop? Wonder if it's better than Nerd Synth...which I really like :)

    I expected somebody will ask this. Well Discovery is true clone / emulation of Nord Lead 2 synth with all his features very close to real HW .. Nerd Synth is nothing like that, it just has sampled waves from Nord Lead A1 and other major importsnt details of sound character (filter, pwm modulation, fm modulation) are unlike the any nord .. so yeah, you can get some simple basic sounds which are a kinda-like in nord terrirory , but as soon as you want to go deeper to sound design you realise it has nothing to do with HW ..

    TLDR; - if you want just few factory presets which sounds a little bit (sometimes) like nord, nerd synth is ok for you .. if you want true Nord Lead legendary sound with ability to design any sound you can design on HW - then Discovery is for you :-)

    Cheers. I'll pick this one up.

    A quick Google search confirms year of release coincides exactly with when stopped buying synths and making music for 13-14 years, so it's a mystery to me.

  • edited September 19

    @pruddo said:
    related, desktop and free:
    https://en.wikipedia.org/wiki/Synth1

    Looks like that synth hasn't been updated for macOS since 6/19/2021. Is it abandonware?

    Also, this note by the developer, "Confirmed to work on Intel Mac. Not confirmed on the M1 Mac (I hope it works)" doesn't exactly instill confidence.

    I won't install that.

  • @NeuM said:

    @pruddo said:
    related, desktop and free:
    https://en.wikipedia.org/wiki/Synth1

    Looks like that synth hasn't been updated for macOS since 6/19/2021. Is it abandonware?

    Also, this note by the developer, "Confirmed to work on Intel Mac. Not confirmed on the M1 Mac (I hope it works)" doesn't exactly instill confidence.

    I won't install that.

    it is what it is..
    haven’t had a single problem with it on M1 MacBook.. (Reaper, Logic)
    like it a lot

  • @NeuM said:

    @pruddo said:
    related, desktop and free:
    https://en.wikipedia.org/wiki/Synth1

    Looks like that synth hasn't been updated for macOS since 6/19/2021. Is it abandonware?

    Also, this note by the developer, "Confirmed to work on Intel Mac. Not confirmed on the M1 Mac (I hope it works)" doesn't exactly instill confidence.

    I won't install that.

    For probably 15 or so years I’ve installed it on multiple computers with multiple operating systems under multiple versions of Ableton. Zero problems. It’s one of most beloved VSTs ever. Basic but sounds great IMO

  • This particular thread seems to have a problem (I’m not even sure this comment will appear). I see page one and then it jumps to page two with zero comments on it.

  • @NeuM said:
    This particular thread seems to have a problem (I’m not even sure this comment will appear). I see page one and then it jumps to page two with zero comments on it.

    Strange, I see your comment, on page 2, along with other comments

  • @Gavinski said:

    @NeuM said:
    This particular thread seems to have a problem (I’m not even sure this comment will appear). I see page one and then it jumps to page two with zero comments on it.

    Strange, I see your comment, on page 2, along with other comments

    I think I just discovered what the problem was. After I updated my iPhone to the latest iOS it seems my browser defaulted to a built in content blocker setting. After turning it off I can see the entire thread now. How weird. Pretty sure this didn’t happen with prior updates.

  • edited September 20

    I’ll pass, but who knows if things change in the future?

    I have no doubt it’s a great sounding Nord clone but it’s still yet another VA and iOS is loaded by now with great sounding VA stuff. This, and it being a capped version compared to desktop, and the stuck-up answers from the developer regarding issues with OB-Xd 3 that are still there, makes me skip this one.

    I don’ t usually get into these kinds of negative posts but DSP really pissed me off and won’t even answer despite me politely offering to help earlier and getting the answer ”we’re pro’s so we don’t need any help”. 😡

    /DMfan🇸🇪

  • @DMfan said:
    I’ll pass, but who knows if things change in the future?

    I have no doubt it’s a great sounding Nord clone but it’s still yet another VA and iOS is loaded by now with great sounding VA stuff. This, and it being a capped version compared to desktop, and the stuck-up answers from the developer regarding issues with OB-Xd 3 that are still there, makes me skip this one.

    I don’ t usually get into these kinds of negative posts but DSP really pissed me off and won’t even answer despite me politely offering to help earlier and getting the answer ”we’re pro’s so we don’t need any help”. 😡

    /DMfan🇸🇪

    Plus them sticking to iPad only vs iPhone is an automatic deal breaker for me too

  • Is there a decent way to save one's own presets? It seems very convoluted, but perhaps I'm missing something.

  • @ALB said:
    Is there a decent way to save one's own presets? It seems very convoluted, but perhaps I'm missing something.

    I would just save 'AUPresets' in the host and completely ignore and avoid the built-in bank/program management...
    ...a simple task like copying one layer from one preset to another preset causes plenty of head-aches...

  • @Samu said:

    @ALB said:
    Is there a decent way to save one's own presets? It seems very convoluted, but perhaps I'm missing something.

    I would just save 'AUPresets' in the host and completely ignore and avoid the built-in bank/program management...
    ...a simple task like copying one layer from one preset to another preset causes plenty of head-aches...

    Thanks for the honest answer - will do. I get really annoyed with bad user preset management/UI.

  • edited September 20

    Preset management seems bad indeed - what is the way to save your own presets without overwriting something? Do you have to copy it, then look around for an empty slot, then save it there? How to create your own bank? Super confusing

  • @Samu said:

    @ALB said:
    Is there a decent way to save one's own presets? It seems very convoluted, but perhaps I'm missing something.

    I would just save 'AUPresets' in the host and completely ignore and avoid the built-in bank/program management...
    ...a simple task like copying one layer from one preset to another preset causes plenty of head-aches...

    It would be nice if more developers followed standard drop-down menu format with sub-menus. This works out really well in apps like TAL-U-NO-LX and many others. And the thing I love about TAL is the presets are all easily found outside their apps and they can be renamed or pre-sorted into folders without using the app itself.

  • @NeuM said:

    It would be nice if more developers followed standard drop-down menu format with sub-menus. This works out really well in apps like TAL-U-NO-LX and many others. And the thing I love about TAL is the presets are all easily found outside their apps and they can be renamed or pre-sorted into folders without using the app itself.

    For Discovery with 3500+ presets a simple 'favorite/star' function would be quite handy as well with an option to only show starred presets.

    discoDSP's OPL uses sub-menus but it's a pita to dig thru thousands of presets that way...

    For apps with 1000+ presets a favorite system feels almost mandatory :)

  • @Samu said:

    @NeuM said:

    It would be nice if more developers followed standard drop-down menu format with sub-menus. This works out really well in apps like TAL-U-NO-LX and many others. And the thing I love about TAL is the presets are all easily found outside their apps and they can be renamed or pre-sorted into folders without using the app itself.

    For Discovery with 3500+ presets a simple 'favorite/star' function would be quite handy as well with an option to only show starred presets.

    discoDSP's OPL uses sub-menus but it's a pita to dig thru thousands of presets that way...

    For apps with 1000+ presets a favorite system feels almost mandatory :)

    Yes, implementing a "Favorites" system seems to be the last consideration for many patch-heavy apps. Those that do it right off the bat usually find a permanent place in my lineup.

  • @Gavinski said:
    Preset management seems bad indeed - what is the way to save your own presets without overwriting something? Do you have to copy it, then look around for an empty slot, then save it there? How to create your own bank? Super confusing

    Maybe you need to use this method described for OB-Xd 3. It sounds like there are slots and you must explicitly copy the preset from working memory to a specific slot to save it. Reminds me of KQ Dixie.

  • @uncledave said:

    @Gavinski said:
    Preset management seems bad indeed - what is the way to save your own presets without overwriting something? Do you have to copy it, then look around for an empty slot, then save it there? How to create your own bank? Super confusing

    Maybe you need to use this method described for OB-Xd 3. It sounds like there are slots and you must explicitly copy the preset from working memory to a specific slot to save it. Reminds me of KQ Dixie.

    Thanks Dave. I know you are wise in the ways of the deverati, so I must ask: why do you think some devs devs use such convoluted preset systems? This is 2024 ffs 😂

  • @Gavinski said:

    @uncledave said:

    @Gavinski said:
    Preset management seems bad indeed - what is the way to save your own presets without overwriting something? Do you have to copy it, then look around for an empty slot, then save it there? How to create your own bank? Super confusing

    Maybe you need to use this method described for OB-Xd 3. It sounds like there are slots and you must explicitly copy the preset from working memory to a specific slot to save it. Reminds me of KQ Dixie.

    Thanks Dave. I know you are wise in the ways of the deverati, so I must ask: why do you think some devs devs use such convoluted preset systems? This is 2024 ffs 😂

    I'd say it's old code, easy to create. Fixed array sizes, corresponding fixed menu sizes, simple. And pretty reasonable for a phone app from 10 years ago. No need to change it...

  • What, no AUV3 parameters ?? Ok this is joke .. hope it will be updated soon, without AUv3 automation basically unusable for me ... shame

    there is also some ug, it is not possible to deactivate arpeggiator on factory presets (for example default "antidote" preset)

    and ina ility of create own preset bank is bummer, to be forced to overwrite existing patches / banks to save own is bad decision

    A bit disappointed for now..

    Btw anybody noticed this ? First time it starts in AUM 🤣

  • edited September 21

    “watching as the plot thickens…..these popcorns have too much salt on them…bring me the….JUCE!”

    /DMfan🇸🇪

  • edited September 21

    @dendy said:
    What, no AUV3 parameters ?? Ok this is joke .. hope it will be updated soon, without AUv3 automation basically unusable for me ... shame

    there is also some ug, it is not possible to deactivate arpeggiator on factory presets (for example default "antidote" preset)

    and ina ility of create own preset bank is bummer, to be forced to overwrite existing patches / banks to save own is bad decision

    A bit disappointed for now..

    Btw anybody noticed this ? First time it starts in AUM 🤣

    Create a user bank, once you’ve tweaked an existing preset, menu, copy preset, select slot in user bank, and paste & save, copying layers between existing presets is a bit more pita though…

    It sounds good but s currently let down by sub-par preset management, missing AUParameters and blurry UI.

    I’ve learned my lesson that higher priced ‘desktop ports’ are no guarantee for a high quality product…

  • edited September 21

    It sounds incredible, approximately 3500 patches. 🤩

    A few notes from using it last night:
    UI is primitive, true 30-year-old HW emulation
. 🤦‍♂️ Those who are expecting from DiscoDSP to rewrite the entire UI framework in Apple Metal… Cmon guys, this is so unrealistic.

    Desktop version is MIDI pre-mapped (MIDI CC are bound to the original Nord Lead knobs).
    But you can control or automate all CC in iOS port anyway.


    Of course, they just need to expose all CC controls in AUv3.

    Some UI elements (controls) are half responsive with finger touch.

    No tempo sync in “Gate pattern”. The pro version has an edit option where you can select the tempo sync speed at 0.5x, 1x, or 2x.

  • @Luxthor said:

    Desktop version is MIDI pre-mapped (MIDI CC are bound to the original Nord Lead knobs).
    But you can control or automate all CC in iOS port anyway.

    That's Midi CC's for the currently selected layer.
    The desktop version of Discovery already has independent AUParameters for all 4 layers.

    The next update will most likely expose the all AUParameters so all good.
    Gate Sequencer already syncs to host tempo (1/32 per gate step).

    All in all some few rough edges remain but nothing that can not be work-around...

  • @Samu said:

    @Luxthor said:

    Desktop version is MIDI pre-mapped (MIDI CC are bound to the original Nord Lead knobs).
    But you can control or automate all CC in iOS port anyway.

    That's Midi CC's for the currently selected layer.
    The desktop version of Discovery already has independent AUParameters for all 4 layers.

    The next update will most likely expose the all AUParameters so all good.
    Gate Sequencer already syncs to host tempo (1/32 per gate step).

    You can always use “morph” between layers and assign modwheel for multilayer automation. Better than nothing. ;)

    All in all some few rough edges remain but nothing that can not be work-around...

    I always wanted the Nord Lead emulator on iOS. This one is more than enough for me. What I really don’t like is the existence of the pro version. This way it looks like we paid for the demo version, and they expect from us to pay all over again for the pro version too?! 

  • @Luxthor said:

    @Samu said:

    @Luxthor said:

    ... What I really don’t like is the existence of the pro version. This way it looks like we paid for the demo version, and they expect from us to pay all over again for the pro version too?! 

    are there any major differences between this and PRO?

  • @Luxthor said:

    I always wanted the Nord Lead emulator on iOS. This one is more than enough for me. What I really don’t like is the existence of the pro version. This way it looks like we paid for the demo version, and they expect from us to pay all over again for the pro version too?! 

    The 'Nord Sound' is the primary reason why I even bought Discovery.

    The Pro version would have made more sense (I would not be surprised if that drops as well with 2-3 months or so) but if it was double price with the issues in the current Discovery build it would have been a big turn-off for many...

    The biggest F-U would be to add a $20 IAP to Discovery to turn it into Discovery Pro :D

  • @MAtrixplan said:

    are there any major differences between this and PRO?

    Yes, Increased polyphony, sample-layer, a few additional step-modulation sources, improved oscillators and filters and more presets etc. :)

  • @MAtrixplan said:

    @Luxthor said:

    @Samu said:

    @Luxthor said:

    ... What I really don’t like is the existence of the pro version. This way it looks like we paid for the demo version, and they expect from us to pay all over again for the pro version too?! 

    are there any major differences between this and PRO?

    Just a few: ;)

    • 5000 presets vs 3500
    • 12 oscilators vs 8 oscilators
    • 128-voice vs 16-voice
    • 12 filters vs 8 filters
    • 4x oversampling vs 2x
    • Wave oscilator vs none
    • Graphic envelope modulation vs none
    • Edit option on every group segment. So countless more features.
    • Etc.
Sign In or Register to comment.