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.

Moog Model D 1.3.2 update is out

2456711

Comments

  • Don't know what time the Moog people get to work but I do hope they chime in...
    ...this update is NOT what I expected from Moog (Same goes for the Model 15 update).

    I hope it's some kind of dev/debug build that got uploaded to AppStore by mistake...

  • @Samu said:
    Don't know what time the Moog people get to work but I do hope they chime in...
    ...this update is NOT what I expected from Moog (Same goes for the Model 15 update).

    I hope it's some kind of dev/debug build that got uploaded to AppStore by mistake...

    They really dropped the ball on this one.

  • edited April 2021


    With the minimal iOS Signal Processing switched on and the 1028 buffer in AUM, one au instance has DSP at 48% & two instances at 82%.
    Thanks 👍🏼

  • @Kandavu said:

    With the minimal iOS Signal Processing switched on and the 1028 buffer in AUM, one instance has DSP 48%, it’s playable. Thanks 👍🏼

    ios 13 ,128 buffer , same DSP (Air2) , so definitely I won't update

  • There’s also that memory threshold where you have to have several things going to open up access to devices full memory capabilities.

  • Hopefully, everyone reading this thread who has upgraded will report the CPU issues to Moog. Pretty please!

  • @Charlesalbert said:
    Can load 6 instances on AUM IPAD pro 12.o 2020 then crash. Don’t know before if I could load an instances more.

    There is a RAM memory limit for AUv3s. Things fail ungracefully if that limit is exceeded.

  • @uncledave said:

    @Charlesalbert said:
    Can load 6 instances on AUM IPAD pro 12.o 2020 then crash. Don’t know before if I could load an instances more.

    There is a RAM memory limit for AUv3s. Things fail ungracefully if that limit is exceeded.

    So all is fine and in my case there is nothing related to the update?

  • The user and all related content has been deleted.
  • @d4d0ug said:

    iPad Pro MQDT2B/A iOS14.4

    Bits/Samplerate?
    24/48 or 16/44.1 ?

  • Hello,
    I checked the upgrade on my secondary iPad (6th gen iPad), and this "upgrade" is nothing, but big mistake. Completely useless. 97% DSP i one instance in the AUM, and only some distorted noise coming very late . Crap.

  • I’m at 33% on model d with one instance open on my iPhone 11. My air 1 would would probably fry. Welp I’m glad I have a Boog

  • On iphone 12 previously I could run 8 concurrent model D's, now it maxes out at 5.

  • The user and all related content has been deleted.
  • Thanks for the heads up! I won't update yet. The last Model D update made it hungrier for CPU on my Air 2 also. Please email Moog with reports so they can address this.

  • Couple instances in Auria Pro, + Fabfilter Twin, + multi sample Piano instrument, + audio clips: 44%. Air 4th Gen latest iOS. I didn’t run more instances because that’s not my usual use case (I generally don’t run multiple instances of anything)

  • @d4d0ug said:

    @jolico said:

    @d4d0ug said:

    iPad Pro MQDT2B/A iOS14.4

    Bits/Samplerate?
    24/48 or 16/44.1 ?

    As i took the screen shot, with the DSP(?) maxing out, the screen shot sound distorted.

    TBH I’m not in the habit of trying to run multiple instances of any app. These days I try and cut to audio as soon as possible, before things get messy and crackle out. I would have hoped that 3 moog instances would work. But meh, maybe not now.

    FWIW, a buffer of 256 might be a little small for multiple instances.

  • @espiegel123 said:
    Hopefully, everyone reading this thread who has upgraded will report the CPU issues to Moog. Pretty please!

    Done

  • edited April 2021

    @Philandering_Bastard said:

    @espiegel123 said:
    Hopefully, everyone reading this thread who has upgraded will report the CPU issues to Moog. Pretty please!

    Done

    Done. Got a ticket.

  • Hi everyone,

    thanks for the feedback. On the devices we tested we got better AUv3 CPU behavior but it seems we might have missed some combinations. We'll look over the iOS and device details reported in this thread and try to reproduce the behavior you're seeing. We apologize for the annoyance and inconvenience and will push a new update out as soon as possible.

    <3 your friends at Moog

  • @VoytecG said:

    @Philandering_Bastard said:

    @espiegel123 said:
    Hopefully, everyone reading this thread who has upgraded will report the CPU issues to Moog. Pretty please!

    Done

    Done. Got a ticket.

    You need to open the standalone and go under ABOUT to find the email link.

  • McDMcD
    edited April 2021

    Doesn't this app also run on the new Mac M1 computers? Maybe they are eager to make a great synth for that emerging market and the "Minimal DSP Resource" for IOS is the attempt to make the app functional for IOS devices.

    No one has mentioned perceived changes in the sound... does anyone have an M1 to comment on impressions in that use case?

  • Ok, here goes my report:

    With the previous version, I couldn't load two AUv3 instances of Model D and/or Model 15 on AUM or anywhere else. Only one at a time. But they were working ok in standalone mode.

    iPad Air 1 iOS 12.5.1

    With this new update, I can't even play those apps in standalone mode, glitches everywhere...

    Hoping for a fix. Thank you! :)

  • @MoogMusicInc said:
    Hi everyone,

    thanks for the feedback. On the devices we tested we got better AUv3 CPU behavior but it seems we might have missed some combinations. We'll look over the iOS and device details reported in this thread and try to reproduce the behavior you're seeing. We apologize for the annoyance and inconvenience and will push a new update out as soon as possible.

    <3 your friends at Moog

    <3 Thank you for the reply!
    As a user, with the new version, I expected better optimization for the hardware. The opposite happened. I hope it's a work accident.
    Greetings.

  • @McD said:
    Doesn't this app also run on the new Mac M1 computers? Maybe they are eager to make a great synth for that emerging market and the "Minimal DSP Resource" for IOS is the attempt to make the app functional for IOS devices.

    No one has mentioned perceived changes in the sound... does anyone have an M1 to comment on impressions in that use case?

    Model D is not available for the M1 (yet?). Only Model 15, but I don't own it...

  • @FRibeiro said:
    Ok, here goes my report:

    With the previous version, I couldn't load two AUv3 instances of Model D and/or Model 15 on AUM or anywhere else. Only one at a time. But they were working ok in standalone mode.

    iPad Air 1 iOS 12.5.1

    With this new update, I can't even play those apps in standalone mode, glitches everywhere...

    Hoping for a fix. Thank you! :)

    This is very helpful, thank you!

  • @VoytecG said:

    @MoogMusicInc said:
    Hi everyone,

    thanks for the feedback. On the devices we tested we got better AUv3 CPU behavior but it seems we might have missed some combinations. We'll look over the iOS and device details reported in this thread and try to reproduce the behavior you're seeing. We apologize for the annoyance and inconvenience and will push a new update out as soon as possible.

    <3 your friends at Moog

    <3 Thank you for the reply!
    As a user, with the new version, I expected better optimization for the hardware. The opposite happened. I hope it's a work accident.
    Greetings.

    Could you please provide the exact details of the device you're using with the iOS version? Thank you!

  • @MoogMusicInc said:

    @VoytecG said:

    @MoogMusicInc said:
    Hi everyone,

    thanks for the feedback. On the devices we tested we got better AUv3 CPU behavior but it seems we might have missed some combinations. We'll look over the iOS and device details reported in this thread and try to reproduce the behavior you're seeing. We apologize for the annoyance and inconvenience and will push a new update out as soon as possible.

    <3 your friends at Moog

    <3 Thank you for the reply!
    As a user, with the new version, I expected better optimization for the hardware. The opposite happened. I hope it's a work accident.
    Greetings.

    Could you please provide the exact details of the device you're using with the iOS version? Thank you!

    As I described in the mail (57344), it's the iPad 6th gen (2018). MMMD Seems to work as the standalone, but not as the AUv3 in hosts (AUM and/or Keystage). Previous version uses much more DSP than other apps, but was Okay (for me).

  • @VoytecG said:

    @MoogMusicInc said:

    @VoytecG said:

    @MoogMusicInc said:
    Hi everyone,

    thanks for the feedback. On the devices we tested we got better AUv3 CPU behavior but it seems we might have missed some combinations. We'll look over the iOS and device details reported in this thread and try to reproduce the behavior you're seeing. We apologize for the annoyance and inconvenience and will push a new update out as soon as possible.

    <3 your friends at Moog

    <3 Thank you for the reply!
    As a user, with the new version, I expected better optimization for the hardware. The opposite happened. I hope it's a work accident.
    Greetings.

    Could you please provide the exact details of the device you're using with the iOS version? Thank you!

    As I described in the mail (57344), it's the iPad 6th gen (2018). MMMD Seems to work as the standalone, but not as the AUv3 in hosts (AUM and/or Keystage). Previous version uses much more DSP than other apps, but was Okay (for me).

    Could you also please share which iOS version you're using?

  • @MoogMusicInc said:

    @VoytecG said:

    @MoogMusicInc said:

    @VoytecG said:

    @MoogMusicInc said:
    Hi everyone,

    thanks for the feedback. On the devices we tested we got better AUv3 CPU behavior but it seems we might have missed some combinations. We'll look over the iOS and device details reported in this thread and try to reproduce the behavior you're seeing. We apologize for the annoyance and inconvenience and will push a new update out as soon as possible.

    <3 your friends at Moog

    <3 Thank you for the reply!
    As a user, with the new version, I expected better optimization for the hardware. The opposite happened. I hope it's a work accident.
    Greetings.

    Could you please provide the exact details of the device you're using with the iOS version? Thank you!

    As I described in the mail (57344), it's the iPad 6th gen (2018). MMMD Seems to work as the standalone, but not as the AUv3 in hosts (AUM and/or Keystage). Previous version uses much more DSP than other apps, but was Okay (for me).

    Could you also please share which iOS version you're using?

    14.4.1

Sign In or Register to comment.