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.

Who wants to test DRC AUv3?

12467

Comments

  • AudioGusAudioGus

    @sinosoidal said:

    @AudioGus said:

    @kinkujin said:

    @AudioGus said:

    @kinkujin said:

    Tested NS2 for the first time yesterday. What a great app! I think I have spent more than one hour making music on iOS for the first time in my life! :smiley:

    Lol

    That wasnt me, that was @sinosoidal . Though I'd love to get an hour of music making myself.

    Lols all around!

    I'm going to dissect this topic a bit further. I spend most of my time launching my apps in debug, make a small test and close. Change something, launch in debug again, test, and the close. My actual time for music making is so limited this days. Then there are some apps that are not intuitive at all, with non sense user interfaces. That's why I have spent one hour with Nano Studio 2, it is really well designed and the work was flowing! :blush:

    Oh I hear yah. NS2 is a dream playflow.

  • ALBALB

    @sinosoidal said:

    I'm going to dissect this topic a bit further. I spend most of my time launching my apps in debug, make a small test and close. Change something, launch in debug again, test, and the close. My actual time for music making is so limited this days. Then there are some apps that are not intuitive at all, with non sense user interfaces. That's why I have spent one hour with Nano Studio 2, it is really well designed and the work was flowing! :blush:

    A recommendation for NS2 from the maker of my favorite synth. I can’t wait to use DRC in NS2!

  • sinosoidalsinosoidal
    edited December 2018

    @janogarcia said:
    @sinosoidal Something seems to have changed in regards to how the stepped rotary controls are handled.

    The less the steps the control has, the faster you have to drag the control for it to react.

    For example, the Octave controls for the OSCs now require a fast up/down gesture to react, and it get worse for the SUB OSC, which now requires an extremely fast gesture.

    Tested on DRV v2.0.0 (95), iOS 12.1, iPad Air and iPhone SE.

    I'm uploading a new build that fixes the problem you describe and makes a important memory usage optimisation. More memory, more instances. As you know, I'm limiting the number of instances to three to avoid a DRC collective crash. However, there has been people here saying that it is crashing even with 3 instances. I hope this build prevents that from happening. If it is clear that it is stable with 3 instances, I will raise the limit to 4 instances.

    I hope you are having great holidays with your family and friends! :blush:

    EDIT: submission of beta builds is disabled between 23 and 27 on App Store. It seems that I need to wait a couple of days to complete this.

  • skiphuntskiphunt

    @sinosoidal I’m using beta v2 build 95. Have not noticed any performance issues with many of the presets I’ve played with. iPad 10.5 iOS 12.1.1

    Was just messing around with it this morning played through a bass heavy, bluetooth loud speaker and noted just how rich and thick it sounds overall. Doesn’t get thin at higher volumes like some others can.

  • kinkujinkinkujin

    @sinosoidal Any timeline for release of this version? Not that I'm impatient or anything ...

  • AudioGusAudioGus

    @kinkujin said:
    @sinosoidal Any timeline for release of this version? Not that I'm impatient or anything ...

    I got that part covered.

  • JanosaxJanosax

    Presets are still not state saved/recalled here on iPhone 7 Plus latest iOS version various hosts.

  • sinosoidalsinosoidal

    @Janosax said:
    Presets are still not state saved/recalled here on iPhone 7 Plus latest iOS version various hosts.

    Ensure that you have purchased unlock synth engine on the standalone, you can do it so by opening menu and choosing store. It must have a tick on it.

    I suspect that is the problem because everyone in this thread that was having the same problem reported to me that it has been fixed on build 95. Keep me updated! Thx!

  • sinosoidalsinosoidal

    @kinkujin said:
    @sinosoidal Any timeline for release of this version? Not that I'm impatient or anything ...

    In January, as soon as the main issues are all resolved. How much confience do you have in the current release for production? In a scale of 0 to 100.

  • JanosaxJanosax

    @sinosoidal said:

    @Janosax said:
    Presets are still not state saved/recalled here on iPhone 7 Plus latest iOS version various hosts.

    Ensure that you have purchased unlock synth engine on the standalone, you can do it so by opening menu and choosing store. It must have a tick on it.

    I suspect that is the problem because everyone in this thread that was having the same problem reported to me that it has been fixed on build 95. Keep me updated! Thx!

    Ok I missed that, thanks that’s fixed now here too :)

  • [Deleted User][Deleted User]

    @sinosoidal said:

    @kinkujin said:
    @sinosoidal Any timeline for release of this version? Not that I'm impatient or anything ...

    In January, as soon as the main issues are all resolved. How much confience do you have in the current release for production? In a scale of 0 to 100.

    I’ve not had any major issues of late with saving in NS2. NS2 does use its own save system, that only tends to see the first lot of sounds, but it’s easy enough to load any of the apps other sounds and then save them as an NS2 preset.

    The AU seems quite reliable and robust now. Not saying there are definitely no hidden away bugs, but I’m not coming across any issues now.

    Personally I would release it.

  • gregsmithgregsmith

    I’ve finally got round to testing this and seems to work fine apart from its suffering from being out of tune at 48khz sample rate. I’m stuck at 48khz on iPhone X and this is happening with lots of synths in stagelight and other hosts. See more in the stagelight thread here:

    https://forum.audiob.us/discussion/29594/stagelight-is-live-on-the-app-store/p32

    We’re trying to establish if this is a host problem or a synth problem. Some apps like Mood and Model D don’t have this issue.

  • SatieSatie

    Good with three instances in cubasis ans AB3. Four instances would be nice.
    I find the release stable enough for a spread out...

  • sinosoidalsinosoidal

    @Fruitbat1919 said:

    @sinosoidal said:

    @kinkujin said:
    @sinosoidal Any timeline for release of this version? Not that I'm impatient or anything ...

    In January, as soon as the main issues are all resolved. How much confience do you have in the current release for production? In a scale of 0 to 100.

    I’ve not had any major issues of late with saving in NS2. NS2 does use its own save system, that only tends to see the first lot of sounds, but it’s easy enough to load any of the apps other sounds and then save them as an NS2 preset.

    The AU seems quite reliable and robust now. Not saying there are definitely no hidden away bugs, but I’m not coming across any issues now.

    Personally I would release it.

    Thanks for your feedback! :blush:

  • sinosoidalsinosoidal

    @gregsmith said:
    I’ve finally got round to testing this and seems to work fine apart from its suffering from being out of tune at 48khz sample rate. I’m stuck at 48khz on iPhone X and this is happening with lots of synths in stagelight and other hosts. See more in the stagelight thread here:

    https://forum.audiob.us/discussion/29594/stagelight-is-live-on-the-app-store/p32

    We’re trying to establish if this is a host problem or a synth problem. Some apps like Mood and Model D don’t have this issue.

    I'm waiting for a powered USB hub to test with an external sound card. There is also other tests I need to do, for instance, change the sample rate of the host (by the way, which hosts allow to do that?).

    The audio unit is supposed to receive that indication from the host and set the sample rate on the internal audio engine.

  • [Deleted User][Deleted User]
    edited December 2018

    @sinosoidal said:

    @janogarcia said:
    @sinosoidal Something seems to have changed in regards to how the stepped rotary controls are handled.

    The less the steps the control has, the faster you have to drag the control for it to react.

    For example, the Octave controls for the OSCs now require a fast up/down gesture to react, and it get worse for the SUB OSC, which now requires an extremely fast gesture.

    Tested on DRV v2.0.0 (95), iOS 12.1, iPad Air and iPhone SE.

    I'm uploading a new build that fixes the problem you describe and makes a important memory usage optimisation. More memory, more instances. As you know, I'm limiting the number of instances to three to avoid a DRC collective crash. However, there has been people here saying that it is crashing even with 3 instances. I hope this build prevents that from happening. If it is clear that it is stable with 3 instances, I will raise the limit to 4 instances.

    I hope you are having great holidays with your family and friends! :blush:

    EDIT: submission of beta builds is disabled between 23 and 27 on App Store. It seems that I need to wait a couple of days to complete this.

    But is that needed for newer iPads and iPhones with more RAM. I thought Apple removed the RAM limitations for newer devices. So was that just rumors?
    Like i said, my 5 years old macbook runs easy 50-100 instances and it has also „just“ 8GB RAM so more than 10 should be easy for the latest iOS devices (in theory even the same amount with the 6GB RAM iPads).

  • sinosoidalsinosoidal

    @Satie said:
    Good with three instances in cubasis ans AB3. Four instances would be nice.
    I find the release stable enough for a spread out...

    Next release I will raise the limit to 4 instances and look forward for your feedback about the stability.

    What I have found during my tests:

    a) memory consumption increases dramatically with the size of the window.
    b) in a iPad PRO 12.9, the full window of a DRC instance is using around 130MB of memory. If the window is the default AUM size, it only uses around 80MB.
    c) if the window was close with a fullscreen size, it stays in memory with that size.

    In conclusion...

    If the user had the precaution of keeping the windows small, it would be possible to have around 5 instances. But this is something that will be hard to explain to most of the users. If prefer to go safe and limit to a number of instance that I'm sure that will not break with all DRC's open.

    The goal is to decrease memory usage even more... but that will take time!

  • sinosoidalsinosoidal
    edited December 2018

    @Cib said:

    @sinosoidal said:

    @janogarcia said:
    @sinosoidal Something seems to have changed in regards to how the stepped rotary controls are handled.

    The less the steps the control has, the faster you have to drag the control for it to react.

    For example, the Octave controls for the OSCs now require a fast up/down gesture to react, and it get worse for the SUB OSC, which now requires an extremely fast gesture.

    Tested on DRV v2.0.0 (95), iOS 12.1, iPad Air and iPhone SE.

    I'm uploading a new build that fixes the problem you describe and makes a important memory usage optimisation. More memory, more instances. As you know, I'm limiting the number of instances to three to avoid a DRC collective crash. However, there has been people here saying that it is crashing even with 3 instances. I hope this build prevents that from happening. If it is clear that it is stable with 3 instances, I will raise the limit to 4 instances.

    I hope you are having great holidays with your family and friends! :blush:

    EDIT: submission of beta builds is disabled between 23 and 27 on App Store. It seems that I need to wait a couple of days to complete this.

    But is that needed for newer iPads and iPhones with more RAM. I thought Apple removed the RAM limitations for newer devices. So was that just rumors?
    Like i said, my 5 years old macbook runs easy 50-100 instances and it has also „just“ 8GB RAM so more than 10 should be easy for the latest iOS devices (in theory even the same amount with the 6GB RAM iPads).

    From my findings, it seems that the sum of the memory used by alls instances of a process from the same family, in this case DRC, cannot surpass 512MB, otherwise all instances will crash. I cannot explain why though.

    DRC is currently memory hungry because of the UI which is dynamically rendered. It is not just a bunch of images and splines. Bigger the window, bigger the size in memory that is needed to render the whole window surface.

  • gregsmithgregsmith
    edited December 2018

    @sinosoidal said:

    @gregsmith said:
    I’ve finally got round to testing this and seems to work fine apart from its suffering from being out of tune at 48khz sample rate. I’m stuck at 48khz on iPhone X and this is happening with lots of synths in stagelight and other hosts. See more in the stagelight thread here:

    https://forum.audiob.us/discussion/29594/stagelight-is-live-on-the-app-store/p32

    We’re trying to establish if this is a host problem or a synth problem. Some apps like Mood and Model D don’t have this issue.

    I'm waiting for a powered USB hub to test with an external sound card. There is also other tests I need to do, for instance, change the sample rate of the host (by the way, which hosts allow to do that?).

    The audio unit is supposed to receive that indication from the host and set the sample rate on the internal audio engine.

    Audio Evolution Mobile let’s you change sample rate but on iPhone X it shows this message:

    I’ve started another thread on it and I think it’s a host issue in Stagelight and AEM as AB and some other hosts don’t have the same issue.

    https://forum.audiob.us/discussion/30502/many-synths-out-of-tune-at-48khz-sample-rate/p2

  • SamuSamu

    @sinosoidal said:

    I'm waiting for a powered USB hub to test with an external sound card. There is also other tests I need to do, for instance, change the sample rate of the host (by the way, which hosts allow to do that?).

    At least ApeMatrix, AUM, Cubasis, BM3 support changing the sample-rate and pop-up a warning if the hardware doesn't support the selected sample-rate.

    The audio unit is supposed to receive that indication from the host and set the sample rate on the internal audio engine.

    They should but as mentioned in the other thread there are some communication misses when sample-rate is changed that need to be sorted out.

    Hope you'll get it sorted out :)

  • [Deleted User][Deleted User]

    @sinosoidal said:

    @Cib said:

    @sinosoidal said:

    @janogarcia said:
    @sinosoidal Something seems to have changed in regards to how the stepped rotary controls are handled.

    The less the steps the control has, the faster you have to drag the control for it to react.

    For example, the Octave controls for the OSCs now require a fast up/down gesture to react, and it get worse for the SUB OSC, which now requires an extremely fast gesture.

    Tested on DRV v2.0.0 (95), iOS 12.1, iPad Air and iPhone SE.

    I'm uploading a new build that fixes the problem you describe and makes a important memory usage optimisation. More memory, more instances. As you know, I'm limiting the number of instances to three to avoid a DRC collective crash. However, there has been people here saying that it is crashing even with 3 instances. I hope this build prevents that from happening. If it is clear that it is stable with 3 instances, I will raise the limit to 4 instances.

    I hope you are having great holidays with your family and friends! :blush:

    EDIT: submission of beta builds is disabled between 23 and 27 on App Store. It seems that I need to wait a couple of days to complete this.

    But is that needed for newer iPads and iPhones with more RAM. I thought Apple removed the RAM limitations for newer devices. So was that just rumors?
    Like i said, my 5 years old macbook runs easy 50-100 instances and it has also „just“ 8GB RAM so more than 10 should be easy for the latest iOS devices (in theory even the same amount with the 6GB RAM iPads).

    From my findings, it seems that the sum of the memory used by alls instances of a process from the same family, in this case DRC, cannot surpass 512MB, otherwise all instances will crash. I cannot explain why though.

    DRC is currently memory hungry because of the UI which is dynamically rendered. It is not just a bunch of images and splines. Bigger the window, bigger the size in memory that is needed to render the whole window surface.

    Thank´s for the info. I hope things going well and get solved. DRC is really a superb synth and at the same time the most cpu friendly here for me from the analog beasts. And the GUI is really great to work with. One of the few virtual analog but with a modern GUI which works good on my notebook and even on my iPhone.
    (There just seems a bug in the desktop version if i choose the colors in the day/night versions, the colors i choose are not the colors i get).

  • [Deleted User][Deleted User]

    New to the DRC party. Just dropping by to say how much I’m enjoying it so far and look forward to the AUv3 version. Any guesstimation on when that may drop? Wondering how many instances I’ll be able to fire up inside BM3 on a 10.5. Cant wait.😬

  • sinosoidalsinosoidal

    @WillieNegus said:
    New to the DRC party. Just dropping by to say how much I’m enjoying it so far and look forward to the AUv3 version. Any guesstimation on when that may drop? Wondering how many instances I’ll be able to fire up inside BM3 on a 10.5. Cant wait.😬

    January for sure! It is a good time to purchase “Unlock Synth Engine” purchase as the price will rise with this release.

    The maximum number of instance will probably be three maybe four. Let’s see how it goes.

  • ohwellohwell

    @sinosoidal Kudos on how smooth you’ve managed to make the AU over the last few weeks!

    I noticed since I joined the beta that (if I’m not mistaken) there is no current equivalent to the mod wheel/aftertouch/pitch bend pages within the AUv3. Three small points that I consider low priority (IMO it’s best to first release the auv3 as soon as it is stable and optimized enough, these are things for down the road.)

    • Is there some other way to set the pitch bend range from within the auv3?
    • I know that midi learn can replace the functionality of the mod wheel and aftertouch pages, but IMO it would be extremely valuable to have them within the AU in terms of workflow. You’ve done a great job with those pages in selecting parameters that are musically significant and can/should be tweaked in conjunction with each other. IMO the ideal DRC workflow for aftertouch and modwheel would involve tweaking the selected options in those pages first, and only going for midi learn as a last resort - or for mapping parameters to things other than mod wheel and aftertouch.
    • Finally, afaik the mod wheel and aftertouch pages’ settings are saved per patch, in the full app, right? That’s super valuable too.

    For reference for people who wonder, I’m mean e.g this page (and tabs - the button for access and relevant tabs for au are circled in blue, I scribbled in black over the part of the page that’s not relevant for the au):

    Keep up the fantastic work @sinosoidal ! I’m noticing a ton of enthusiasm for the DRC auv3 in other threads, things seem ripe for a very successful release!!

  • sinosoidalsinosoidal

    @ohwell said:
    @sinosoidal Kudos on how smooth you’ve managed to make the AU over the last few weeks!

    I noticed since I joined the beta that (if I’m not mistaken) there is no current equivalent to the mod wheel/aftertouch/pitch bend pages within the AUv3. Three small points that I consider low priority (IMO it’s best to first release the auv3 as soon as it is stable and optimized enough, these are things for down the road.)

    • Is there some other way to set the pitch bend range from within the auv3?
    • I know that midi learn can replace the functionality of the mod wheel and aftertouch pages, but IMO it would be extremely valuable to have them within the AU in terms of workflow. You’ve done a great job with those pages in selecting parameters that are musically significant and can/should be tweaked in conjunction with each other. IMO the ideal DRC workflow for aftertouch and modwheel would involve tweaking the selected options in those pages first, and only going for midi learn as a last resort - or for mapping parameters to things other than mod wheel and aftertouch.
    • Finally, afaik the mod wheel and aftertouch pages’ settings are saved per patch, in the full app, right? That’s super valuable too.

    For reference for people who wonder, I’m mean e.g this page (and tabs - the button for access and relevant tabs for au are circled in blue, I scribbled in black over the part of the page that’s not relevant for the au):

    Keep up the fantastic work @sinosoidal ! I’m noticing a ton of enthusiasm for the DRC auv3 in other threads, things seem ripe for a very successful release!!

    Thanks for your feedback. It has been more than the last few actually. I have been working towards this goal for several months! :blush:

    For now, those controls will only be available via midi. I'm trying to reduce the number of panels to the bare minimum to save memory. I'm sure that time will bring optimisations.

    I'm about to post a new build with a minor fix and the increase of the maximum instances to four. The idea is to understand if people can have 4 instances safely.

  • SatieSatie

    New build - 4 instances:

    • Good so far in cubasis
    • Not good in AB3 - all DRCs black after adding the fourth
    • AUM - not good with two DRCs or more - no sound until deactivating the second instance.

    Greetings 🤔🙄

  • SatieSatie

    @Satie said:
    New build - 4 instances:

    • Good so far in cubasis
    • Not good in AB3 - all DRCs black after adding the fourth
    • AUM - not good with two DRCs or more - no sound until deactivating the second instance.

    Greetings 🤔🙄

    Sorry - after restart iPad - there is no issue with 4 instances with AUM. I will test AB3 later.

  • ZaubrerZaubrer

    Regarding the price increase: I definitely would not increase it beyond the price of the Model D App. DRC is the third search result after Model D and Model 15 and given it is free to try, I guess many people will choose it over the first two. The price of under 10€ bucks is a huge selling point if you ask me. I think I would not increase it over 15€. To be honest I would not mind paying a small fee of 5€ to unlock the AUv3 capabilities. I would also imagine that not all buyers need AUv3 as well, especially if they are „first timers“ just delving into the world of synthesizers and search for Moog on the App Store.

  • sinosoidalsinosoidal

    @Zaubrer said:
    Regarding the price increase: I definitely would not increase it beyond the price of the Model D App. DRC is the third search result after Model D and Model 15 and given it is free to try, I guess many people will choose it over the first two. The price of under 10€ bucks is a huge selling point if you ask me. I think I would not increase it over 15€. To be honest I would not mind paying a small fee of 5€ to unlock the AUv3 capabilities. I would also imagine that not all buyers need AUv3 as well, especially if they are „first timers“ just delving into the world of synthesizers and search for Moog on the App Store.

    Thanks for your feedback! We will not add AUv3 support as a new in-app. We will honour everyone who has already shown their support buying "Unlock Synth Engine" and increase the price of this purchase for future users. This way, existing users can benefit from AUv3.

  • vitocorleone123vitocorleone123

    You are awesomely generous! A small in app would've probably been successful... But I welcome free AUv3 goodness. Thanks!

Sign In or Register to comment.

© Vanilla Keystone Theme 2025