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.

OB - Xd 3 AUv3 Synth by DiscoDSP (Released)

12467

Comments

  • @Gavinski said:
    @ecou said:

    @Gavinski said:

    @ecou said:
    So the only difference is the interface ? For 17.99$CAD. No thanks

    Not just the UI - see my post above. But yeah, doesn’t look like a very essential upgrade

    Are you going to do a video putting both versions against each other sound wise ?

    I have no plans to do that. It already took me a full day, morning to night, to prep and make that last video and I have other things to do. They sound the same as far as I can hear, I compared a few patches from the original version and this one myself before making the video and heard no difference - and i said that specifically in the video. I also mentioned that I hadn't yet been able to hear an example where oversampling whether x2 or x4 made a difference. What I did also say in the video though is that they are capable of sounding different, largely because the new version has a filter capable of self oscillation (kind of) which the old one was not capable of. That doesn't affect old patches though because that ability can be turned in or off with a button. There are other things that can make a difference to sound, if you want, like using a knob to adjust filter key tracking. I mentioned all this in video already too. Tldr - I wouldn't buy the new one expecting a better sound out of the box. Buy it for other features like the self oscillating filter or the better UI, if these are important to you. The old version will be good enough for many already.

    I did not know you made a video already. I watched it. Thank you

  • @jamietopol said:

    @seawind161 said:
    Is anyone else able to reliably save presets? I’ve hesitated to post this for fear that it’s user error. I’m on the latest version of the app, an M2 12.9, 17.5.1.

    In AUM, I make a new bank (which is populated with "Default" presets by default), make a preset, hit "Rename Preset" (the only way I see to save), and key in a name. So far, so good, and the new preset shows up in the new bank.

    But if I go to another bank, and then back to the new bank, the new preset is gone and the bank is filled with "Default" presets.

    The same seems to hold true with the standalone version.

    This is with the "updated" app that was supposed to fix these issues.

    Someone, please tell me that I’m just failing to understand how this "system" works.

    I think the developer is aware of several issues and is working on fixes, but you shouldn't hesitate to reach out to them via their website form.

    I contacted the developer 3 times today and each time they responded to my questions concerning scaling the UI, thus was their last reply:

    “Implementing a flexible scaling feature on iOS requires a high-quality resampling algorithm that we’re working on.
    As we continue to refine the app, we’re committed to providing an optimized and visually crisp experience. We appreciate your understanding and patience as we work on these improvements.”

  • @rapidfire said:

    I contacted the developer 3 times today and each time they responded to my questions concerning scaling the UI, thus was their last reply:

    “Implementing a flexible scaling feature on iOS requires a high-quality resampling algorithm that we’re working on.
    As we continue to refine the app, we’re committed to providing an optimized and visually crisp experience. We appreciate your understanding and patience as we work on these improvements.”

    That's Good News! :sunglasses:

  • @Samu said:

    @rapidfire said:

    I contacted the developer 3 times today and each time they responded to my questions concerning scaling the UI, thus was their last reply:

    “Implementing a flexible scaling feature on iOS requires a high-quality resampling algorithm that we’re working on.
    As we continue to refine the app, we’re committed to providing an optimized and visually crisp experience. We appreciate your understanding and patience as we work on these improvements.”

    That's Good News! :sunglasses:

    Fingers crossed 🤞

  • @jamietopol said:

    @Poppadocrock said:
    So has anyone successfully loaded any patchbanks that are free across the web or from their older version of OB-XD yet?

    Yes. I opened each bank in the old version of OB-Xd and selected "Export Bank" in the menu. I was then able to import each exported bank in the new version of OB-Xd. This worked for the old KVR Coummunity Banks, Luke's Soundhouse bank, etc.

    That’s great to know. Cause I’ve accumulated several banks and want to use all those patches in the new one, once I buy it, which is inevitable…

  • Here is my video for the OB-Xd 3

  • Is this obxd better than BA-1 ?

  • @sigma79 said:
    Is this obxd better than BA-1 ?

    Two completely different synths with different architecture and 'better' is always very 'subjective'.
    I'd say get both, they complement each other nicely.

  • @Samu said:

    @sigma79 said:
    Is this obxd better than BA-1 ?

    Two completely different synths with different architecture and 'better' is always very 'subjective'.
    I'd say get both, they complement each other nicely.

    Cheers Samu.

  • @seawind161 said:
    Is anyone else able to reliably save presets? I’ve hesitated to post this for fear that it’s user error. I’m on the latest version of the app, an M2 12.9, 17.5.1.

    In AUM, I make a new bank (which is populated with "Default" presets by default), make a preset, hit "Rename Preset" (the only way I see to save), and key in a name. So far, so good, and the new preset shows up in the new bank.

    But if I go to another bank, and then back to the new bank, the new preset is gone and the bank is filled with "Default" presets.

    The same seems to hold true with the standalone version.

    This is with the "updated" app that was supposed to fix these issues.

    Someone, please tell me that I’m just failing to understand how this "system" works.

    Hi,
    Not sure if you still want information on saving presets, but I contacted the developer this morning and they promptly replied with an answer, from update v3.5.4 they included an Overwrite function for storing our own presets. This is how I got it to work……
    tap the red Menu tab/Bank/New Bank and name it,
    After creating a preset, tap the red Menu/Copy Preset,
    select your new Bank from list,
    Open Menu and tap Paste/Overwrite, your preset is now saved in your new Bank.
    When you want to save another preset, repeat everything I just wrote except this time after copying your new preset,
    select your new Bank/tap Preset bar/select default (next in list)/Menu/paste Preset/Overwrite, do this for all new presets.
    BEWARE - If you don’t select the next Default in your new Bank, your newly created preset will automatically position itself on top of your first saved preset.
    This works every time and does not disappear 👍
    Mike.

  • Version 3.5.5 out and still won’t load or read banks….

    /DMfan🇸🇪

  • @Poppadocrock said:
    Thanks @rapidfire

    You’ve welcome 🍻

  • @rapidfire said:
    Not sure if you still want information on saving presets, but I contacted the developer this morning and they promptly replied with an answer, from update v3.5.4 they included an Overwrite function for storing our own presets. This is how I got it to work……

    Thanks, Rapidfire. Makes me wonder if the folks at Disco DSP had ever seen any AUV3s before they came up with what might charitably be described as "this Fuster Cluck".

  • @seawind161 said:

    @rapidfire said:
    Not sure if you still want information on saving presets, but I contacted the developer this morning and they promptly replied with an answer, from update v3.5.4 they included an Overwrite function for storing our own presets. This is how I got it to work……

    Thanks, Rapidfire. Makes me wonder if the folks at Disco DSP had ever seen any AUV3s before they came up with what might charitably be described as "this Fuster Cluck".

    I expect because the devs know how everything operates they naturally assume we know also!
    🍻

  • @seawind161 said:

    @rapidfire said:
    Not sure if you still want information on saving presets, but I contacted the developer this morning and they promptly replied with an answer, from update v3.5.4 they included an Overwrite function for storing our own presets. This is how I got it to work……

    Thanks, Rapidfire. Makes me wonder if the folks at Disco DSP had ever seen any AUV3s before they came up with what might charitably be described as "this Fuster Cluck".

    😂

  • @rapidfire said:

    @seawind161 said:
    Is anyone else able to reliably save presets? I’ve hesitated to post this for fear that it’s user error. I’m on the latest version of the app, an M2 12.9, 17.5.1.

    In AUM, I make a new bank (which is populated with "Default" presets by default), make a preset, hit "Rename Preset" (the only way I see to save), and key in a name. So far, so good, and the new preset shows up in the new bank.

    But if I go to another bank, and then back to the new bank, the new preset is gone and the bank is filled with "Default" presets.

    The same seems to hold true with the standalone version.

    This is with the "updated" app that was supposed to fix these issues.

    Someone, please tell me that I’m just failing to understand how this "system" works.

    Hi,
    Not sure if you still want information on saving presets, but I contacted the developer this morning and they promptly replied with an answer, from update v3.5.4 they included an Overwrite function for storing our own presets. This is how I got it to work……
    tap the red Menu tab/Bank/New Bank and name it,
    After creating a preset, tap the red Menu/Copy Preset,
    select your new Bank from list,
    Open Menu and tap Paste/Overwrite, your preset is now saved in your new Bank.
    When you want to save another preset, repeat everything I just wrote except this time after copying your new preset,
    select your new Bank/tap Preset bar/select default (next in list)/Menu/paste Preset/Overwrite, do this for all new presets.
    BEWARE - If you don’t select the next Default in your new Bank, your newly created preset will automatically position itself on top of your first saved preset.
    This works every time and does not disappear 👍
    Mike.

    Looks like the SonicLab apps finally have a competitor for "worst preset system ever" 🤷‍♂️

  • @Gavinski said:

    Looks like the SonicLab apps finally have a competitor for "worst preset system ever" 🤷‍♂️

    I did not think it was possible, lol.

  • edited August 2024

    @Gavinski said:

    Looks like the SonicLab apps finally have a competitor for "worst preset system ever" 🤷‍♂️

    I find the OB-Xd preset system easier than both Synthmaster 1&2, at least this system does not duplicate its presets and end up being lost, the only downside is when using CC Program Change, it’s very random, sometimes a correct bank and preset can be selected, other times the selection is hit-n-miss.

  • edited August 2024

    3.5.6 is out. Still greyed out banks when trying to import and the app won’t read manually moved banks. Did not notify developer since they already know about it and seems to be pushing updates with single fixes.

    /DMfan🇸🇪

  • edited August 2024

    I asked the dev if they’re planning on bringing iPhone support, and they said no 😖

    They’re going to keep supporting the old version though, so that’s good.

  • Got this in reply regarding beta testing and greyed out banks:

    Seems to me they are not overwhelmingly happy about the feedback…

    /DMfan🇸🇪

  • @DMfan said:

    Seems to me they are not overwhelmingly happy about the feedback…

    'highly qualified in-house team' and 'thoroughly tests' doesn't rime that well when an end user can bump into issues within a few minutes of launching their app :sunglasses:

    But hey, I'll let them do their thing and won't waste any more time and just accept it 'as is'.

  • edited August 2024

    @Jumpercollins said:

    My vid lol.

    I should conduct myself better if Im to become famous ( wear my best shirt etc )

    The 2nd half of vid is ok if I recall.

    Did make a static patch of non synth tweaking but through loads of fx.

    Is it a good patch ( never sure )

    It were also to test how Dragonfly works with polyphony and not sure until I try with hardware controller.

    anyway.

    The point is.

    The obxd upgrade is 32 voice poly where as old is 8 ?

    Even without triggering the 32 voices.

    More voices affects the sound of the first voice/voices even only triggering a few voices. Sort of how unison affects the voice.

    The sound engine seems to have more room ( hollow )

    For the oscilators and overall sound to expand. A pyramid without a point.

    The old may sound similar but would be more mono, oscilator wise. Like a pyramid.

    This probably isnt the case. Mono sounding oscilators etc lol.

    I did buy Nerd synth and found the sound engine to maybe sound stereo, so that even the oscilators sound pwm samples. Which I dont like but might be a case of sounding good when fully driven.

  • edited August 2024

    With the obxd-3

    There isnt many synths with the nice wooden sounding. Bordering wavetable ?

    Not sure really.

  • Just make sure to enable the VAM switch to make OB-Xd really shine :)

  • @Samu said:
    Just make sure to enable the VAM switch to make OB-Xd really shine :)

    Nice Samu.

    Didnt know what the VAM were for.

  • edited August 2024

    Looks great. I wish the og app had this Interface

  • @gregsmith said:
    I asked the dev if they’re planning on brining iPhone support, and they said no 😖

    They’re going to keep supporting the old version though, so that’s good.

    Great news regarding the old version. 😌 Thank you for the info!

Sign In or Register to comment.