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.

Microwave by Waldorf - out now! (iPad)

14567810»

Comments

  • @rapidfire said:

    @R_2 said:

    @rapidfire said:
    I just wish they would make Nave AUv3 so that I can use more than one instance in my projects, but the developer who created Nave left Waldorf and no one else knew how to modify it.

    Rolf Wöhrmann (current Waldorf CEO) developed it.

    Hi @R_2,

    Stefan Stenzel – Chief engineer and technical lead. He was responsible for the synthesis engine and was the principal architect behind Nave’s wavetable technology.
    

    Nave was released for iPad in 2013 as Waldorf’s first dedicated iOS synthesizer. It was notable for bringing Waldorf’s wavetable synthesis heritage to a touchscreen interface, including features such as:

    • advanced wavetable oscillators,
    • speech synthesis for creating wavetables,
    • 3D wavetable editing,
    • audio-to-wavetable conversion,
    • an interface designed specifically for touch interaction.

    Although Waldorf Music published the app, the original product credits consistently identify Stefan Stenzel, Rolf Wöhrmann, and Axel Hartmann as the creators of the initial Nave app.

    As far as I remember Stefan Stenzel was running Waldorf back then. They hired Rolf Wöhrmann for the iOS work on nave (and Axel Hartmann for the outstanding GUI).
    Perhaps Stefan was responsible for the core wavetable engine. But i doubt Rolf can’t update it to AUv3 if he’d wanted.
    They have updated nave desktop since Stefan left Waldorf.

  • @Crabman said:
    The Asic bug is a hell lot of fun . Though a bit dangerous. It can get extremly loud and dirty in a heartbeat. Love it.

    What is the asci bug?

  • @cam said:

    @Crabman said:
    The Asic bug is a hell lot of fun . Though a bit dangerous. It can get extremly loud and dirty in a heartbeat. Love it.

    What is the asci bug?

    Hi. It seems like it is a flaw in the programming of the ASIC chip used in the original hardware. See this KVR post for details.

  • @R_2 said:

    @rapidfire said:

    @R_2 said:

    @rapidfire said:
    I just wish they would make Nave AUv3 so that I can use more than one instance in my projects, but the developer who created Nave left Waldorf and no one else knew how to modify it.

    Rolf Wöhrmann (current Waldorf CEO) developed it.

    Hi @R_2,

    Stefan Stenzel – Chief engineer and technical lead. He was responsible for the synthesis engine and was the principal architect behind Nave’s wavetable technology.
    

    Nave was released for iPad in 2013 as Waldorf’s first dedicated iOS synthesizer. It was notable for bringing Waldorf’s wavetable synthesis heritage to a touchscreen interface, including features such as:

    • advanced wavetable oscillators,
    • speech synthesis for creating wavetables,
    • 3D wavetable editing,
    • audio-to-wavetable conversion,
    • an interface designed specifically for touch interaction.

    Although Waldorf Music published the app, the original product credits consistently identify Stefan Stenzel, Rolf Wöhrmann, and Axel Hartmann as the creators of the initial Nave app.

    As far as I remember Stefan Stenzel was running Waldorf back then. They hired Rolf Wöhrmann for the iOS work on nave (and Axel Hartmann for the outstanding GUI).
    Perhaps Stefan was responsible for the core wavetable engine. But i doubt Rolf can’t update it to AUv3 if he’d wanted.
    They have updated nave desktop since Stefan left Waldorf.

    Talking of which, or whom, if anyone hasn’t already experienced it, NLogSynth Pro is worth experiencing https://apps.apple.com/gb/app/nlogsynth-pro/id393879841

  • @u0421793 said:

    @R_2 said:

    @rapidfire said:

    @R_2 said:

    @rapidfire said:
    I just wish they would make Nave AUv3 so that I can use more than one instance in my projects, but the developer who created Nave left Waldorf and no one else knew how to modify it.

    Rolf Wöhrmann (current Waldorf CEO) developed it.

    Hi @R_2,

    Stefan Stenzel – Chief engineer and technical lead. He was responsible for the synthesis engine and was the principal architect behind Nave’s wavetable technology.
    

    Nave was released for iPad in 2013 as Waldorf’s first dedicated iOS synthesizer. It was notable for bringing Waldorf’s wavetable synthesis heritage to a touchscreen interface, including features such as:

    • advanced wavetable oscillators,
    • speech synthesis for creating wavetables,
    • 3D wavetable editing,
    • audio-to-wavetable conversion,
    • an interface designed specifically for touch interaction.

    Although Waldorf Music published the app, the original product credits consistently identify Stefan Stenzel, Rolf Wöhrmann, and Axel Hartmann as the creators of the initial Nave app.

    As far as I remember Stefan Stenzel was running Waldorf back then. They hired Rolf Wöhrmann for the iOS work on nave (and Axel Hartmann for the outstanding GUI).
    Perhaps Stefan was responsible for the core wavetable engine. But i doubt Rolf can’t update it to AUv3 if he’d wanted.
    They have updated nave desktop since Stefan left Waldorf.

    Talking of which, or whom, if anyone hasn’t already experienced it, NLogSynth Pro is worth experiencing https://apps.apple.com/gb/app/nlogsynth-pro/id393879841

    Stefan Stenzel was the core designer of Nave, Rolf Wöhrmann was hired to work on the iOS side of Nave and is now CEO of Waldorf, you were on the right track, I did not now about the iOS development. The last update for Nave was 7 years ago, no new features were added, it had more to do with AudioBus 3 update.

  • Nave was pretty cool, but the ring modulation sounded weak or a bit quiet. It would be nice to have it as AUv3, but I think Oscidia is a much better wavetable synth. It even uses less CPU than the Blofeld.

  • I just pulled tht trigger for the synth, what an amazing one wow I'm so glad to buy it

  • I just pulled tht trigger for the synth, what an amazing one wow I'm so glad to buy it

  • I love the Microwave but I'm having a few issues with the updated version and I'm hoping to have a reality check before I report to Waldorf:

    1. I have no way to objectively verify this, but I'm feeling that the CPU usage is higher, to the extent that my M1 ipad pro sometimes chokes when I play a chord. This never happened with the previous version. After a while the ipad gets very hot, again something I did notice previously. Can anyone else chip-in with their findings?

    2. When setting up a mono patch (which can only be done by selecting the voices in multi mode), there is sometimes an audible click artifact when some notes are retriggered.

    3. The fingered portamento and fingered glissando modes do not work as expected. There is always a glide between notes. This should only happen when notes overlap (manual page 21).

    Any users willing to provide input?

  • @stim said:
    I love the Microwave but I'm having a few issues with the updated version and I'm hoping to have a reality check before I report to Waldorf:

    1. I have no way to objectively verify this, but I'm feeling that the CPU usage is higher, to the extent that my M1 ipad pro sometimes chokes when I play a chord. This never happened with the previous version. After a while the ipad gets very hot, again something I did notice previously. Can anyone else chip-in with their findings?

    2. When setting up a mono patch (which can only be done by selecting the voices in multi mode), there is sometimes an audible click artifact when some notes are retriggered.

    3. The fingered portamento and fingered glissando modes do not work as expected. There is always a glide between notes. This should only happen when notes overlap (manual page 21).

    Any users willing to provide input?

    Hi @stim,
    I have just setup three Microwave 1s in Cubasis 3 on my iPad Air 4, each track is playing three note chords for eight bars using Multi presets, the DSP is peaking at 35% and stays constant when using a latency of 2.7, if I change latency to 10.7 the DSP peaks at 24. The portamento and glissando modes work fine and when the glide control is zero then it’s just normal playing. My 13” Air M2 would give better DSP results.
    Mike

  • @rapidfire said:

    Hi @stim,
    I have just setup three Microwave 1s in Cubasis 3 on my iPad Air 4, each track is playing three note chords for eight bars using Multi presets, the DSP is peaking at 35% and stays constant when using a latency of 2.7, if I change latency to 10.7 the DSP peaks at 24. The portamento and glissando modes work fine and when the glide control is zero then it’s just normal playing. My 13” Air M2 would give better DSP results.
    Mike

    Hey Mike,
    Thank you very much for checking this! You saved me some egg-on-face :p

    My concern about CPU usage arose because, since the update, one of my MW projects in Drambo has been giving CPU spikes so my suspicions were aroused. I copied your approach - in a fresh project I loaded-up three instances of MW with complex multi and had each play an 8-note chord. CPU usage touched around 50% and was stable - no spikes. So, the culprit isn't MW. I have some head-scratching to do.

    Regarding the fingered portamento and glissando modes however, I am pretty sure that these are not working. I whipped up a very basic mono patch to demonstrate this (attached as zip). While gliss and portamento are working in general, it is the more expressive fingered style - i.e. slides only happen on overlapping notes - that are not. Same situation on the desktop version. I will send this to Waldorf, hopefully they can look into it.

    Thanks again for putting me straight B)
    stim

Sign In or Register to comment.