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

13567…11

Comments

  • NeonSiliconNeonSilicon

    @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?

    If you'd like another data point, I'm on a first generation iPad Pro 9.7" with the latest iOS14 beta and Model D glitches in both standalone and AU settings.

    It was fine before the latest update even on my old hardware and running the OS betas.

    All your software synths sound terrific BTW.

  • MoogMusicIncMoogMusicInc

    @VoytecG said:

    @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

    Thank you!

  • KandavuKandavu
    edited April 2021

    @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?

    This is the latest v. 1.3.2 side loaded onto my M1 Mac Mini. The GUI isn’t all there. An external keyboard works, you can toggle the presets & access the settings.

    As per noticeable differences in sound, I can’t say with the speakers I’ve got at the moment.

  • xorxor

    For what it’s worth...
    iPad Pro 2020 12.9”
    iPad OS 14.4.2
    AUM 1.3.9, 44.1, buffer: 256
    Before update (1.3.1): 7 instances, monophonic, (playing) dsp: 97%-99%, sounds good
    After update (1.3.2): reload session dsp: 106%-110%. Total crackle fest, changed buffer to 512 and ok, 1024 pretty good and back to 95%-96%.
    Single ui was sluggish in both versions, more than that just keep getting worse.
    New version has a huge dsp spike just after loading the session that I don’t recall the old version having. Jumps up to 107% after all 7 instances are loaded then quiesces to 94% after a couple of seconds. Playing then jumps to 95%-96%

  • NeuMNeuM

    In my case, loaded into GarageBand as an AUv3, resulted in horrendous static/white noise mixed in with all sounds. Quit GB and tried the apps in standalone mode and everything worked fine, so there is clearly something going on with the AUv3 and possibly chewing up too much memory. I switched the settings in iOS to 512 on the “Preferred Audio Buffer Size” and that seems to have solved the issue temporarily in my case, but beyond this I did no additional testing.

    iPad Pro 12.9” (if I recall correctly, the second gen iPad Pro), running iOS 14.4.2

  • CharlesalbertCharlesalbert

    @xor said:
    For what it’s worth...
    iPad Pro 2020 12.9”
    iPad OS 14.4.2
    AUM 1.3.9, 44.1, buffer: 256
    Before update (1.3.1): 7 instances, monophonic, (playing) dsp: 97%-99%, sounds good
    After update (1.3.2): reload session dsp: 106%-110%. Total crackle fest, changed buffer to 512 and ok, 1024 pretty good and back to 95%-96%.
    Single ui was sluggish in both versions, more than that just keep getting worse.
    New version has a huge dsp spike just after loading the session that I don’t recall the old version having. Jumps up to 107% after all 7 instances are loaded then quiesces to 94% after a couple of seconds. Playing then jumps to 95%-96%

    Same iPad and iOS same behavior here 👍

  • horsetrainerhorsetrainer

    I think I'll hold off on upgrading till this gets sorted out.

  • Stuntman_mikeStuntman_mike

    Yeah, the update has doubled resources 😢

  • Philandering_BastardPhilandering_Bastard
    edited April 2021

    @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

    Hi, Air 2 user. After the update, Model D will hover around 95% CPU in AUM, buffer 256. This wasn’t the case previously. A buffer of 1024 will bring it down to 40%, single instance. Any additional instance brings it back into the red.

    Edit: iOS 13.7

  • Stuntman_mikeStuntman_mike

    @MoogMusicInc said:

    @VoytecG said:

    @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

    Thank you!

    14.4.2 iPad 6th generation

  • TheSoundKidTheSoundKid

    Oh god. Thanks I’m still in iOS 13 :) & everything work fine without any glitches.

  • MoogMusicIncMoogMusicInc

    Thanks everyone for posting your device and iOS combo.

    Quick update: we have already found one problem and are testing a fix. We might not be able to do a full testing run tonight on all devices but are working as fast as we can. We only tested a selection of device/iOS combos for the last release and that caused this problem to slip through, so we want to be thorough this time.

    Thanks so much for your patience and all the reports!

  • Philandering_BastardPhilandering_Bastard

    @MoogMusicInc said:
    Thanks everyone for posting your device and iOS combo.

    Quick update: we have already found one problem and are testing a fix. We might not be able to do a full testing run tonight on all devices but are working as fast as we can. We only tested a selection of device/iOS combos for the last release and that caused this problem to slip through, so we want to be thorough this time.

    Thanks so much for your patience and all the reports!

    Appreciate it.

  • dvidvi

    To be honest, my Model D was offloaded, I can’t remember when was the last time I used it.

    With the update, I’m getting 70% - 100% DSP (big spikes when switching apps to type this) and sluggish UI with two AUs on AUM @128, which is the rate I use for everything else without issues. iPad Air3 with latest iPadOS.

  • NeuMNeuM

    @MoogMusicInc said:
    Thanks everyone for posting your device and iOS combo.

    Quick update: we have already found one problem and are testing a fix. We might not be able to do a full testing run tonight on all devices but are working as fast as we can. We only tested a selection of device/iOS combos for the last release and that caused this problem to slip through, so we want to be thorough this time.

    Thanks so much for your patience and all the reports!

    Thanks for being so responsive! Much appreciated.

  • michael_mmichael_m

    @NeuM said:

    @MoogMusicInc said:
    Thanks everyone for posting your device and iOS combo.

    Quick update: we have already found one problem and are testing a fix. We might not be able to do a full testing run tonight on all devices but are working as fast as we can. We only tested a selection of device/iOS combos for the last release and that caused this problem to slip through, so we want to be thorough this time.

    Thanks so much for your patience and all the reports!

    Thanks for being so responsive! Much appreciated.

    Yes, thank you - definitely appreciate the response!

  • MoogMusicIncMoogMusicInc
    edited April 2021

    @Kandavu said:

    @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?

    This is the latest v. 1.3.2 side loaded onto my M1 Mac Mini. The GUI isn’t all there. An external keyboard works, you can toggle the presets & access the settings.

    As per noticeable differences in sound, I can’t say with the speakers I’ve got at the moment.

    The macOS release is not the same as the iOS release. Please don't side load an iOS binary on an M1 machine but rather download the dedicated macOS version from the App Store. The iOS binaries have none of the work we did for macOS.

    [Update] only afterwards noticed you were trying Minimoog Model D, this use case is unsupported. Porting Model 15 took a significant amount of work, we don't expect that side loading Model D would work correctly.

    <3 your friends at Moog

  • LittlewoodgLittlewoodg

    @Littlewoodg said:
    Couple instances in Auria Pro, + Fabfilter Twin, + multi sample Piano instrument, + audio clips: cpu 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)

    Edit: this report was pre update
    Same cpu after...

  • SpudSpud

    @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

    Thanks! I hope it can be maintained to work on the older devices. I love this app - all Moog apps sound noticeably better than any other synth apps I have used, but I can't afford an iPad upgrade right now.

  • reasOnereasOne

    I hope this gets fixed so i can update some time!

  • ApexApex

    I have not updated Model D yet. Is Model 15 having the same issues? Please say no. Model 15 is easily my favorite synth and I use it on everything. 🙏🏻

  • VaultnaemsaeVaultnaemsae

    Another user here who was stung by the update that claimed improvements!

  • SamuSamu

    @Apex said:
    I have not updated Model D yet. Is Model 15 having the same issues? Please say no. Model 15 is easily my favorite synth and I use it on everything. 🙏🏻

    At least on my iPad Air 2 Model 15 has the same type of issues and the macOS version 'crawls' on my 3Ghz 6-Core i5 MacMini.

    But since I'm only using 1 instance most of the time I can live with the temporary 'glitch'.

  • Kurt_KKurt_K

    @Philandering_Bastard said:
    97% CPU On my Air2.

    Soo, no?

    Bummer...

    Only 40% on my Air 3 - if that helps.

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • Philandering_BastardPhilandering_Bastard

    @tja said:
    I really need to stop updating Apps just because there is a new version.

    I need to tattoo that somewhere visible.

  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • [Deleted User][Deleted User]
    The user and all related content has been deleted.
  • BradBrad

    Instances like this are the reason Apple should allow us the clone/properly backup. Then we could just revert back to the previous version. It would be less frustrating for us the users and for the developers as well.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024