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.

JAmp bleep. A cool little free auv3 experimental instrument

13»

Comments

  • @ninobeatz said:
    v1.2!

    awesome!

  • edited March 6

    @janm31415 said:
    Hi all,
    Developer of the app here.
    Thanks for all the nice words and the growing fan club :smile:
    I always had the suspicion that my email address was not receiving all email I should, so I've updated my contact data in case you want to reach out to me: https://www.jamp-audio.com/contact.html
    As for the crashes at startup when installing: I've heard this before, but I can't reproduce it on my M1. Essentially I'm just following the example install app that Apple provides via Xcode, but maybe I'm still doing something wrong. If I find a solution I will update the app.
    As for syncing with the host app: that should be possible now in v1.1. If this is still somewhat different than the standard way in other apps, let me know with how it should actually work and I will fix it.
    The unreadable text in the "Midi learn" section (in AUM) is also fixed in v1.1. The reason why this happened is because jAmp Bleep starts in "light" mode, but apparently AUM can override that to "dark" mode, making the background black, and then you don't see the black text anymore.
    Anyway, have fun with the app.

    I love this thing!

    I also can add that I think the crash on startup only happens until the iPad is restarted. I got the same behavior on 2 iPads. Maybe that clue helps?

    Btw, I’m not sure what you’re doing in terms of the sound generation, but somehow you are creating bleeps that are so harmonically rich! They process so well! Fractal Bits used to be my go to, but this just sounds so much nicer. Even the low bit/sample rate setting.

    I’d like to request a small change/addition… When in host sync, having the tempo knob change to a clock multiple/divide would be super useful.

  • @MonkeyDrummer said:

    I’d like to request a small change/addition… When in host sync, having the tempo knob change to a clock multiple/divide would be super useful.

    Re clock multiples - I was thinking the same earlier today. However, what would really be good would be a switch so we could choose between clock divisions or direct tempo entry.

  • Dev's video:

  • Clock multiples sound interesting: I'll take a look at it during the weekend.
    I think the Sync/Free toggle can be used as a switch to choose between clock divisions or direct tempo. Since V1.2 this toggle only deals with the tempo. The Start/Stop sync is not controlled by this toggle anymore, but is always active when there is a host with a transport layer.

    As for the crashes: I have an idea where it might go wrong. But a restart will probably always be required on some devices. I've seen other links (like here: https://forum.juce.com/t/help-my-audio-unit-version-3-auv3-is-not-working/45860) where a restart also seems required to let the AUv3 register with the device.

  • FPCFPC
    edited March 7

    @janm31415 said:
    Clock multiples sound interesting: I'll take a look at it during the weekend.
    I think the Sync/Free toggle can be used as a switch to choose between clock divisions or direct tempo. Since V1.2 this toggle only deals with the tempo. The Start/Stop sync is not controlled by this toggle anymore, but is always active when there is a host with a transport layer.

    As for the crashes: I have an idea where it might go wrong. But a restart will probably always be required on some devices. I've seen other links (like here: https://forum.juce.com/t/help-my-audio-unit-version-3-auv3-is-not-working/45860) where a restart also seems required to let the AUv3 register with the device.

    I just want to say thank you for this brilliant app. Very kind of you to give it away, I certainly would have paid for it.
    Thanks too for the updates <3

  • Yah this has been great fun!

  • @AudioGus said:
    Yah this has been great fun!

    +1. Been losing a lot of time playing with this gem. Its is a lot of rewarding fun. Hats off to the sweet Dev. Will def support all future apps by them. THANK YOU! Cheers, ED

  • @ElektrikDiva said:

    @AudioGus said:
    Yah this has been great fun!

    +1. Been losing a lot of time playing with this gem. Its is a lot of rewarding fun. Hats off to the sweet Dev. Will def support all future apps by them. THANK YOU! Cheers, ED

    in a round about way it makes me want to buy Turnado on desktop now as these bleep bloops love Turnado heh

  • So fun! It made me buy Hilda because I just knew it would be a sweet combo.

    Thanks to the Dev!

  • Love it!. It’s like a little musical gremlin. Thank u @janm31415 !

  • It’s not working as an AU in GarageBand. Hitting “on” doesn’t do anything as an AU. It works in standalone

  • @Fear2Stop said:
    It’s not working as an AU in GarageBand. Hitting “on” doesn’t do anything as an AU. It works in standalone

    Yes, the "On" switch won't work in a DAW that supports syncing. You should use the play and stop buttons of GarageBand itself.

  • @janm31415 said:

    @Fear2Stop said:
    It’s not working as an AU in GarageBand. Hitting “on” doesn’t do anything as an AU. It works in standalone

    Yes, the "On" switch won't work in a DAW that supports syncing. You should use the play and stop buttons of GarageBand itself.

    Ahh…so you don’t actually “play” anything? I was wondering why pressing the keys didn’t make any sound 🤣

  • @Fear2Stop said:

    @janm31415 said:

    @Fear2Stop said:
    It’s not working as an AU in GarageBand. Hitting “on” doesn’t do anything as an AU. It works in standalone

    Yes, the "On" switch won't work in a DAW that supports syncing. You should use the play and stop buttons of GarageBand itself.

    Ahh…so you don’t actually “play” anything? I was wondering why pressing the keys didn’t make any sound 🤣

    Indeed, the first version of the app was more like you expected it to work. But if you start using more instances of the Bleep audio unit (as is done in some videos that you can find above), it is more handy that Bleep starts playing in a synchronised way. So the latest version only starts bleeping once you have pressed the host's (AUM or GarageBand or ...) play button.

  • @janm31415 said:

    @Fear2Stop said:

    @janm31415 said:

    @Fear2Stop said:
    It’s not working as an AU in GarageBand. Hitting “on” doesn’t do anything as an AU. It works in standalone

    Yes, the "On" switch won't work in a DAW that supports syncing. You should use the play and stop buttons of GarageBand itself.

    Ahh…so you don’t actually “play” anything? I was wondering why pressing the keys didn’t make any sound 🤣

    Indeed, the first version of the app was more like you expected it to work. But if you start using more instances of the Bleep audio unit (as is done in some videos that you can find above), it is more handy that Bleep starts playing in a synchronised way. So the latest version only starts bleeping once you have pressed the host's (AUM or GarageBand or ...) play button.

    Ohhhh ok makes sense lol

  • I’m definitely in love with this little noise making gem.

    What does seed mean?

  • @Poppadocrock said:
    I’m definitely in love with this little noise making gem.

    What does seed mean?

    Inside Bleep is a random number generator (RNG) that generates the patterns of the different sounds. On a computer you cannot really have real randomness, but a RNG tries to be as random as possible. Each RNG starts with a seed, and from then on a pattern of numbers is generated that looks random. However, with the same seed, the RNG will always output the same list of numbers. For Bleep this means that, if you take a seed like 0 or 1 or ... 999, the patterns that are generated are always the same. If your other settings are also the same, then you should get the same bleeps and bloops. If you choose the "random" setting on the seed knob, then the seed for the RNG will be taken as the current time (in seconds since 1970), and your pattern will thus not be repeatable or predictable.

    There is one caveat here, if you use (i.e. turn) the "Mutate" knob, then the patterns are modified (mutated), and you should turn your mutate knob at exact the same sample (there are 44100 samples / sec) to get the same predictable behaviour as before. So if you record MIDI and turn the mutate knob, the behaviour currently will not be predictable, because Bleep is not that accurately synced. Maybe I can take a look how to do that, but currently I don't know.

    But if you would record settings (a button at the top allows to save settings), where each setting starts with a different seed, and you play through these settings, then the sounds should be predictable (I hope, I actually didn't test it). The different seed is advised here, because then Bleep will restart the RNG from the given seed, so the pattern is predictable again in case you used the Mutate knob.

  • edited March 9

    @janm31415 said:

    @Poppadocrock said:
    I’m definitely in love with this little noise making gem.

    What does seed mean?

    Inside Bleep is a random number generator (RNG) that generates the patterns of the different sounds. On a computer you cannot really have real randomness, but a RNG tries to be as random as possible. Each RNG starts with a seed, and from then on a pattern of numbers is generated that looks random. However, with the same seed, the RNG will always output the same list of numbers. For Bleep this means that, if you take a seed like 0 or 1 or ... 999, the patterns that are generated are always the same. If your other settings are also the same, then you should get the same bleeps and bloops. If you choose the "random" setting on the seed knob, then the seed for the RNG will be taken as the current time (in seconds since 1970), and your pattern will thus not be repeatable or predictable.

    There is one caveat here, if you use (i.e. turn) the "Mutate" knob, then the patterns are modified (mutated), and you should turn your mutate knob at exact the same sample (there are 44100 samples / sec) to get the same predictable behaviour as before. So if you record MIDI and turn the mutate knob, the behaviour currently will not be predictable, because Bleep is not that accurately synced. Maybe I can take a look how to do that, but currently I don't know.

    But if you would record settings (a button at the top allows to save settings), where each setting starts with a different seed, and you play through these settings, then the sounds should be predictable (I hope, I actually didn't test it). The different seed is advised here, because then Bleep will restart the RNG from the given seed, so the pattern is predictable again in case you used the Mutate knob.

    Thanks for that detailed explanation. I have seen the word seed used in different things before, and when I adjusted I could tell it changed the pattern, I just wasn’t sure if there was any correlation between the seed number and the pattern. Now I know there is, except for the random and mutate. Thanks.

  • This app is really fun and gets really groovy. Great work, @janm31415

  • @ninobeatz said:
    v1.3!

    Oh man that's awesome

Sign In or Register to comment.