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.

Released Waldorf Blofeld for iPad

1234568

Comments

  • @frosttrance_7 said:

    @Dalle said:

    @dendy said:
    hm, are you sure ? I don’t remember Blof HW filters self-oscillating

    Quite sure. Other things like FM feedback, osc brilliance, noise and effects also sound different between the hardware and software.

    That's strange, because EvilDragon beta tested it, and he said that the software is a 1:1 copy of the original. Maybe ask Waldorf about it.

    I’ve sent Waldorf a messge about it, but it’s not something most people care about. The sound is close but not a 1:1 copy in any way. Very easy to verify by comparing FM feedback for example, completely different results. The reverb is a totally different algorithm with different parameters, phaser and flanger sound different etc.

    I just wish they used the same code instead of changing things.

  • @dendy said:
    edit: it self oscillates - you just need to have turned on at least one oscillator - you can turn the oscillator volume to zero in mixer so basically it doesn't go to filter, but filter keeps self oscillating ..

    my raw guess is it was working same way on HW

    The filters on the software don't self oscillate without being excited by an input first (turning the oscillator up and then to zero for example). Filters on the hardware do.

  • @Dalle said:

    @dendy said:
    edit: it self oscillates - you just need to have turned on at least one oscillator - you can turn the oscillator volume to zero in mixer so basically it doesn't go to filter, but filter keeps self oscillating ..

    my raw guess is it was working same way on HW

    The filters on the software don't self oscillate without being excited by an input first (turning the oscillator up and then to zero for example). Filters on the hardware do.

    uhm sorry you are true.. i thought i have volume of osc set to zero but it was axtually set to 1 .. when it is zero, no self oscillation ..

  • Um. Edits to an oscillator octave don't really work? I tried setting one to 16' and it became 1/2 when the setting was saved. Now no value setting succeeds in any other result. Anyone else experience this?

  • edited May 5

    @garden said:
    Um. Edits to an oscillator octave don't really work? I tried setting one to 16' and it became 1/2 when the setting was saved. Now no value setting succeeds in any other result. Anyone else experience this?

    I noticed that. When you change the value, it changes immediately in the display. If you Cancel, the new value stays. If you Confirm, the value drops to 1/2. Looks like a mixup in selecting an indexed value as opposed to a continuous variable.

    Edit: corrected typo.

  • @garden said:
    Um. Edits to an oscillator octave don't really work? I tried setting one to 16' and it became 1/2 when the setting was saved. Now no value setting succeeds in any other result. Anyone else experience this?

    I just drag on the control to select the octave instead of tapping, but you're right, using the other method seems to be broken

  • @royor said:
    Last night I imported HGF-Blofeld-Waveset-A-128.wpc through the samples tab.. import went fine.. could see all the samples.. tried to scan through them and pick something lower down the list and it wouldn’t pick that sample.. it would always bounce back to the top of the list and pick one from that view.. there was no way to pick a sample lower down the list and have it stick.. sounds like it’s related to @Gavinski ’s issue.. settings don’t stick..

    Woke up this morning, updated Blofeld + now that same list of samples has a red coloured font instead of white.. can’t even read it without the screen being as bright as possible.. 🤷‍♂️ and still can’t pick a sample lower down the list..

    Will send an email to them after my morning coffee..

    Same here — What fixed it for me was to re-import the HGF-Blofeld-Waveset-A-128.wpc with related presets into a new bank/group, after deleting the old group. However, this is only possible by deleting every single patch individually, as it's still not possible to delete a group that has presets in it (???).

    What is a disaster, next to the many glitches in the interface (tried Apple Pencil [no fun]) and bugs not ironed out in the release, is the preset management. Hope there'll be fixes on the way, as otherwise it certainly is a great synth.

  • @Grandbear said:

    @garden said:
    Um. Edits to an oscillator octave don't really work? I tried setting one to 16' and it became 1/2 when the setting was saved. Now no value setting succeeds in any other result. Anyone else experience this?

    I just drag on the control to select the octave instead of tapping, but you're right, using the other method seems to be broken

    Also, as someone mentioned, pressing cancel instead of confirm works OK lol
    But yes, great sound, pity the release version is definitely a bit rough around the edges

  • I'll echo what's been said, in case someone at Waldorf is keeping score.

    1. It's great to have a Blofeld on my iPad.
    2. It sounds rich and there's lots to play with in terms of modulations, filters, and waveforms.
    3. The interface leaves much to be desired. (a) Hitting the right spot to move a slider isn't as easy as we're used to. (b) Preset management is crude. Being able to add a second tag, "Favorites," would help. Or, better, having a dedicated favoriting system.
  • @MMS said:
    Same here — What fixed it for me was to re-import the HGF-Blofeld-Waveset-A-128.wpc with related presets into a new bank/group, after deleting the old group. However, this is only possible by deleting every single patch individually, as it's still not possible to delete a group that has presets in it (???).

    Thanks for that info.. I’ll patiently wait for a possible fix.. I can’t see myself deleting 128 files individually.. I did contact them and they were going to look into it.. and not being able to delete groups that have presets in them? What were they thinking? 🤷‍♂️

    @dokwok2 said:
    3. The interface leaves much to be desired. (a) Hitting the right spot to move a slider isn't as easy as we're used to. (b) Preset management is crude. Being able to add a second tag, "Favorites," would help. Or, better, having a dedicated favoriting system.

    Absolutely agree.. A no-brainer way to mark favourites is essential.. like breathing..

  • It crashes in Groove rider too. Moreover, the load is not visible at all. It just knocks out the program. It's the same in Aum. The load is 7-8 percent. And crashes. Something's wrong with Blofeld. Everything else works fine.

  • wimwim
    edited May 9

    @solncekreeze said:
    It crashes in Groove rider too. Moreover, the load is not visible at all. It just knocks out the program. It's the same in Aum. The load is 7-8 percent. And crashes. Something's wrong with Blofeld. Everything else works fine.

    Works fine in GR-2 here.
    iPad 9th gen, iPadOS 17.7.1

    [edit] ok, I did manage to get one crash while changing presets just now.

  • Not had a single crash with Blofeld yet (Using AUM, Cubasis, Logic Pro for iPad) on my 11" M1 iPadPro, iPadOS18.4.1...

  • @Samu said:
    Not had a single crash with Blofeld yet (Using AUM, Cubasis, Logic Pro for iPad) on my 11" M1 iPadPro, iPadOS18.4.1...

    I have an ipad m1. 18.4.1. It works fine on init. You start changing presets and it crashes. But not at all. Some presets work fine. This is Blofeld's problem. In GR2, everything else works fine. I'll try it again in Cubasis.

  • @wim said:

    @solncekreeze said:
    It crashes in Groove rider too. Moreover, the load is not visible at all. It just knocks out the program. It's the same in Aum. The load is 7-8 percent. And crashes. Something's wrong with Blofeld. Everything else works fine.

    Works fine in GR-2 here.
    iPad 9th gen, iPadOS 17.7.1

    [edit] ok, I did manage to get one crash while changing presets just now.

    That's the problem.

  • Are presets stored in the file system like in Microwave?

  • wimwim
    edited May 9

    @timfromtheborder said:
    Are presets stored in the file system like in Microwave?

    I see a blofeld.wdb file in My Device > BlofeldPlugin > Presets. It's updated whenever I open Blofeld.
    I can export presets anywhere I like in the file system. They get a .bpz extension.

  • @solncekreeze said:

    @wim said:

    @solncekreeze said:
    It crashes in Groove rider too. Moreover, the load is not visible at all. It just knocks out the program. It's the same in Aum. The load is 7-8 percent. And crashes. Something's wrong with Blofeld. Everything else works fine.

    Works fine in GR-2 here.
    iPad 9th gen, iPadOS 17.7.1

    [edit] ok, I did manage to get one crash while changing presets just now.

    That's the problem.

    You should report it to Waldorf. If enough people report the preset loading crashes it is likely to increase its priority.

    Some people have a lot of trouble with this and others not so much.

  • @wim thanks. I really prefer how Microwave just straight up saves them in a folder. The in app browser sucks but it was easy to make my own bank using the files app. More developers should do that! Lol

  • @espiegel123 said:

    @solncekreeze said:

    @wim said:

    @solncekreeze said:
    It crashes in Groove rider too. Moreover, the load is not visible at all. It just knocks out the program. It's the same in Aum. The load is 7-8 percent. And crashes. Something's wrong with Blofeld. Everything else works fine.

    Works fine in GR-2 here.
    iPad 9th gen, iPadOS 17.7.1

    [edit] ok, I did manage to get one crash while changing presets just now.

    That's the problem.

    You should report it to Waldorf. If enough people report the preset loading crashes it is likely to increase its priority.

    Some people have a lot of trouble with this and others not so much.

    That's what I did.😊 I hope that they will fix the errors.

  • @espiegel123 said:
    You should report it to Waldorf. If enough people report the preset loading crashes it is likely to increase its priority.

    I've been thinking on this a lot lately. We are a group that often discuss an issue and then maybe one(1) report to where it actually matters, the developer.

    Might there be a way we could organise this, a category of it's own maybe. Not to torture developers, quite the opposite. But, you know, if we could use the power of many to really push, getting: glitches, bugs and feature request fixed and done.

    I have no clue how to go about and organise such a thing but it might be something you wise guys (I mean that in a positive way) can come up with.

    It looks and sounds kind dumb now, when I wrote it out but, who knows.

  • I’m guessing with all the CPU complaints I’m reading, this one wouldn’t be much use on an iPad Air 3?

  • Is There An In Deep Tutorial For Go Blofeld ?

  • @Samu said:

    @id_23 said:
    Sounds great on my m1 iPad Pro…
    If not a little quiet?

    Adjust the main volume knob at the top of the UI, It's independent from the preset level just like a real hardware synth :)

    I have only played with it a little bit, and it sounds awesome, haven’t noticed a volume issue, nor did I notice that the volume knob was independent.

    But, I wanted to emphasize the point you made- I wish every softsynth would do this with the volume. I like to keep my gain staging consistent and having software instruments always putting out close to 0dbfs is frustrating. Way to go Waldorf!

  • Which is the one to get when choosing between Microwave and Blofeld? (I already have Nave.)

  • edited May 14

    @Krupa said:
    I’m guessing with all the CPU complaints I’m reading, this one wouldn’t be much use on an iPad Air 3?

    I went through the "trouble" of installing on mine to test it for you, I don't use it much for music since I got my Pro M1. Darn it takes time to load a slot of whatever in AUM. I guess I'm going to appreciate the Pro a bit more (for a while). Here's a screenshot with 2 Blofeld and Revolv and Fluss as plugins (famously heavy). AUM buffer set to 512. Works fine, no crackle.

  • @Pxlhg said:

    @Krupa said:
    I’m guessing with all the CPU complaints I’m reading, this one wouldn’t be much use on an iPad Air 3?

    I went through the "trouble" of installing on mine to test it for you, I don't use it much for music since I got my Pro M1. Darn it takes time to load a slot of whatever in AUM. I guess I'm going to appreciate the Pro a bit more (for a while). Here's a screenshot with 2 Blofeld and Revolv and Fluss as plugins (famously heavy). AUM buffer set to 512. Works fine, no crackle.

    Ah thanks 🙏 I did actually get it while it was still on offer and should have come back to mention the same🙌

  • @Wrlds2ndBstGeoshredr said:
    Which is the one to get when choosing between Microwave and Blofeld? (I already have Nave.)

    I definitely prefer Microwave.
    Preset management is much easier/more intuitive, the presets themselves sound better (to my ears) , the UI is nicer…

  • @Kashi said:

    @Wrlds2ndBstGeoshredr said:
    Which is the one to get when choosing between Microwave and Blofeld? (I already have Nave.)

    I definitely prefer Microwave.
    Preset management is much easier/more intuitive, the presets themselves sound better (to my ears) , the UI is nicer…

    I haven't gone deep into Blofeld but I definitely prefer Microwave UI by a long shot

  • Blofeld update just dropped and it's got the nice scroll widget from Microwave!

    Option to hide the on-screen keyboard and optional midi-out is still missing in the AUv3 for both Blofeld and Microwave.

    But it's re-assuring to know they do listen to feedback :)

Sign In or Register to comment.