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.

Blocs Wave, a new app from the Launchpad for iOS team

1…192021222325»

Comments

  • sleeplesssleepless

    @zeropoint said:
    Haven't waded through the whole thread .......but with Blocs Wave loaded in an AUM node, is anyone else not seeing the AUM tab whilst in Blocs ?

    It doesn't seem to support that. Or IAA sync (which would be nice).

  • zeropointzeropoint

    ^^ Thanks. Shame....not so concerned personally about the lack of IAA sync as it has Link. But it's such a fun live tool for jamming with sliced samples....and jumping around your AUM nodes is clunky without that AUM tab......

  • sleeplesssleepless

    ^^ IAA transport when using it in AUM would be nice, though. Also, I still find that, when Linked, BW plays a tiny fraction behind other Link apps (like a few ms of latency). I hope they implement user-definable buffer settings which may overcome this.

  • AndyPlanktonAndyPlankton
    edited June 2016

    @sleepless said:
    ^^ IAA transport when using it in AUM would be nice, though. Also, I still find that, when Linked, BW plays a tiny fraction behind other Link apps (like a few ms of latency). I hope they implement user-definable buffer settings which may overcome this.

    This could be due to the processing time for timestretching/pitch shifting ? Do you get the same delay if you play samples back at their original pitch and bpm ? Might be worth investigating. If you fond this to be true, then you could flatten your samples to get rid of the delay.

  • sleeplesssleepless

    @AndyPlankton said:

    @sleepless said:
    ^^ IAA transport when using it in AUM would be nice, though. Also, I still find that, when Linked, BW plays a tiny fraction behind other Link apps (like a few ms of latency). I hope they implement user-definable buffer settings which may overcome this.

    This could be due to the processing time for timestretching/pitch shifting ? Do you get the same delay if you play samples back at their original pitch and bpm ? Might be worth investigating. If you fond this to be true, then you could flatten your samples to get rid of the delay.

    It could be. I noticed last night that it doesn't happen when slicing a sample, only when playing a loop (even at the original bpm and key). If I slip the transients before the beat grid slightly, it plays tightly with other Link apps. A workaround but not ideal.

  • AndyPlanktonAndyPlankton

    @sleepless said:

    @AndyPlankton said:

    @sleepless said:
    ^^ IAA transport when using it in AUM would be nice, though. Also, I still find that, when Linked, BW plays a tiny fraction behind other Link apps (like a few ms of latency). I hope they implement user-definable buffer settings which may overcome this.

    This could be due to the processing time for timestretching/pitch shifting ? Do you get the same delay if you play samples back at their original pitch and bpm ? Might be worth investigating. If you fond this to be true, then you could flatten your samples to get rid of the delay.

    It could be. I noticed last night that it doesn't happen when slicing a sample, only when playing a loop (even at the original bpm and key). If I slip the transients before the beat grid slightly, it plays tightly with other Link apps. A workaround but not ideal.

    If it is the same when playing at original tempo and key then it probably isn't to do with this, as it has nothing to do, so therefore shouldn't introduce any delay.

    Slip may work for you, but as you say it is not ideal, if you export your loop into something else that doesn't have the same delay, then your loop will be ahead of time in that other app :|

    I'm not sure if link has built in functionality for delay compensation, but yes this would be a good thing to have, then you could adjust each app as required.

  • gonekrazy3000gonekrazy3000

    In other news..... UPDATE IS OUT! :D still waiting for the video though.

  • gjcyrusgjcyrus

    Gonna try this out with Remixlive and Cross DJ as they all have Link! The two competitors can actually benefit from each other's hard work as these apps compliment each other!

    https://forum.audiob.us/discussion/14070/remixlive-1-2-cross-dj-pro-3-1-now-with-ableton-link#latest

  • kobamotokobamoto

    @gonekrazy3000 said:
    In other news..... UPDATE IS OUT! :D still waiting for the video though.

    what update?

  • kobamotokobamoto

    nevermind

  • robosardinerobosardine

    @Launchpadforios said:
    We hear you. We're still motoring quickly through features right now, and whilst we were pleased to get user libraries out pretty quickly, we understand there is still more to do. There are about 100 things we'd like to do right now, and as we roll out new features from here, the prioritisation will be really tough. Especially, with our upcoming two releases coming out over the next few weeks, you'll see why we've been busy.

    I take it you mean by 'new releases' you mean completely new apps?- as opposed to adding new features to other apps. That's been a good few weeks now- is there any news?

  • QuarantinedQuarantined
    edited July 2016

    Deleted

  • AndyPlanktonAndyPlankton

    @Quarantined said:

    If it is the same when playing at original tempo and key then it probably isn't to do with this, as it has nothing to do, so therefore shouldn't introduce any delay.

    I'm not sure that "has nothing to do" is what actually happens - see https://forum.audiob.us/discussion/14100/bad-sound-quality-in-blocs-wave#latest.

    With imported samples, played back at original tempo and key, I am getting very prominent warbling/beating artefacts. I can only assume therefore, that pitch/time-stretch processing is permanently 'on'.

    Either that or the artefacts are coming from elsewhere in the playback engine.

  • QuarantinedQuarantined
    edited July 2016

    Deleted

  • AndyPlanktonAndyPlankton

    @Quarantined said:

    @AndyPlankton said:

    @Quarantined said:

    If it is the same when playing at original tempo and key then it probably isn't to do with this, as it has nothing to do, so therefore shouldn't introduce any delay.

    I'm not sure that "has nothing to do" is what actually happens - see https://forum.audiob.us/discussion/14100/bad-sound-quality-in-blocs-wave#latest.

    With imported samples, played back at original tempo and key, I am getting very prominent warbling/beating artefacts. I can only assume therefore, that pitch/time-stretch processing is permanently 'on'.

    Either that or the artefacts are coming from elsewhere in the playback engine.

    I've exhausted everything I can think of, including every combination of Ableton link on/off, background audio on/off, running within/without Audiobus/Aum, deleting imported samples, re-importing, rebooting devices, uninstalling/reinstalling Blocs ... on multiple devices, and I can't prevent artefacts when playing back in Blocs.

    Had a thought about this, is it to do with buffer size, the reason I say this is that people have said the artifacts are there sometimes and not others, buffer size is controlled by the first app opened.
    Just a thought.

  • QuarantinedQuarantined
    edited July 2016

    Deleted

  • AndyPlanktonAndyPlankton

    @Quarantined said:

    @AndyPlankton said:

    @Quarantined said:

    @AndyPlankton said:

    @Quarantined said:

    If it is the same when playing at original tempo and key then it probably isn't to do with this, as it has nothing to do, so therefore shouldn't introduce any delay.

    I'm not sure that "has nothing to do" is what actually happens - see https://forum.audiob.us/discussion/14100/bad-sound-quality-in-blocs-wave#latest.

    With imported samples, played back at original tempo and key, I am getting very prominent warbling/beating artefacts. I can only assume therefore, that pitch/time-stretch processing is permanently 'on'.

    Either that or the artefacts are coming from elsewhere in the playback engine.

    I've exhausted everything I can think of, including every combination of Ableton link on/off, background audio on/off, running within/without Audiobus/Aum, deleting imported samples, re-importing, rebooting devices, uninstalling/reinstalling Blocs ... on multiple devices, and I can't prevent artefacts when playing back in Blocs.

    Had a thought about this, is it to do with buffer size, the reason I say this is that people have said the artifacts are there sometimes and not others, buffer size is controlled by the first app opened.
    Just a thought.

    I had wondered that myself, but was getting the playback artefacts when running Blocs standalone - and there doesn't appear to be a direct setting for buffer size in Blocs itself. I had even tried running Blocs standalone immediately after rebooting, to make sure that there were no 'zombie' IAA apps running and affecting buffer size.

    Inspired by your thought, I have just closed all apps, launched Audiobus, set buffer size to 1024 (from 256), launched Blocs within Audiobus, and bingo - no playback artefacts! Back to Audiobus, reset buffer size to 256 - artefacts in Blocs again. Back to Audiobus, buffer size back to 1024 - no artefacts in Blocs. So thanks, that is where the problem is. And this is indeed a problem, as this was all done on an iPad Pro, which categorically should not need a buffer size of 1024 to run a single instance of a sample playback engine.

    Wahey !!! :) :) :) At least we know how to reproduce it now, half the battle. I am sure the devs will be tuning and optimising the playback engine with each release, so fingers crossed for an update to address this soon. :)

  • AudiojunkieAudiojunkie

    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Same for BPM?

  • AndyPlanktonAndyPlankton

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Easiest way I have is using MIDIMorphosis, this will give you the pitches in a sample, you can then use this to decide the key, not particularly quick though.

    Same for BPM?

    Use tap tempo in a metronome app ?

  • AudiojunkieAudiojunkie

    @AndyPlankton said:

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Easiest way I have is using MIDIMorphosis, this will give you the pitches in a sample, you can then use this to decide the key, not particularly quick though.

    Same for BPM?

    Use tap tempo in a metronome app ?

    Both are good ideas. I hadn't thought of them. It would be nice to have Bloc to be capable of detecting these values automatically. I have close to 10,000 royalty free loops that I purchased back at the beginning of the millennium that sound great, but don't come with the key information of the loop.

  • AudiojunkieAudiojunkie

    BTW, does anyone know any good audiobus metronome apps that include a tap tempo capability?

  • gjcyrusgjcyrus

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Same for BPM?

    I've never done this but if you could somehow stick all the samples into ITunes, then have a DJ app such as djay, (maybe traktor or cross dj as well), they will tell you key info and bpm. There's also dj software out there that can tell you key info like Mixed In Key that comes to mind

  • AudiojunkieAudiojunkie

    @gjcyrus said:

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Same for BPM?

    I've never done this but if you could somehow stick all the samples into ITunes, then have a DJ app such as djay, (maybe traktor or cross dj as well), they will tell you key info and bpm. There's also dj software out there that can tell you key info like Mixed In Key that comes to mind

    Interesting! I'll have to look at DJ apps to see what I can find there...

  • AndyPlanktonAndyPlankton

    @Audiojunkie said:

    @gjcyrus said:

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Same for BPM?

    I've never done this but if you could somehow stick all the samples into ITunes, then have a DJ app such as djay, (maybe traktor or cross dj as well), they will tell you key info and bpm. There's also dj software out there that can tell you key info like Mixed In Key that comes to mind

    Interesting! I'll have to look at DJ apps to see what I can find there...

    Let me know how you get on, I got a similar library :)

  • parallaxobjectparallaxobject
    edited June 2016

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Same for BPM?

    KeyOmeter ain't too bad:
    https://appsto.re/us/qFT0H.i
    It runs in Audiobus, but I find better results when I run a loop in Audioshare as background audio and let keyOmeter detect from the speaker. Sometimes restarting a loop and/or changing the music style (upper left in app) can help, as it refreshes the detection. You'll often need to figure out the relative minor of major keys for the purposes of Blocs, and sometimes it'll interpret an actual major key as minor, and vice versa, but you can often get in the ballpark. Perhaps a tuner app would be a good companion.

    And Pro Metronome runs in Audiobus and is fairly robust:
    https://appsto.re/us/FNrFC.i

  • AudiojunkieAudiojunkie

    @AndyPlankton said:

    @Audiojunkie said:

    @gjcyrus said:

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Same for BPM?

    I've never done this but if you could somehow stick all the samples into ITunes, then have a DJ app such as djay, (maybe traktor or cross dj as well), they will tell you key info and bpm. There's also dj software out there that can tell you key info like Mixed In Key that comes to mind

    Interesting! I'll have to look at DJ apps to see what I can find there...

    Let me know how you get on, I got a similar library :)

    I sure will! :-)

  • Matt_Fletcher_2000Matt_Fletcher_2000

    @Audiojunkie said:

    @AndyPlankton said:

    @Audiojunkie said:

    @gjcyrus said:

    @Audiojunkie said:
    Does anyone have a quick and easy way to determine the initial pitch of a sample if you don't know what it is?

    Same for BPM?

    I've never done this but if you could somehow stick all the samples into ITunes, then have a DJ app such as djay, (maybe traktor or cross dj as well), they will tell you key info and bpm. There's also dj software out there that can tell you key info like Mixed In Key that comes to mind

    Interesting! I'll have to look at DJ apps to see what I can find there...

    Let me know how you get on, I got a similar library :)

    I sure will! :-)

    You could 'open in' djay2. It will give you a BPM and a key. No need for iTunes.

    It might struggle with short samples though.

  • AudiojunkieAudiojunkie

    After trying things out, I've found that KeyOmeter and Key Detect work well to detect the key of a loop, and liveBPM does well with beat detection. They're not perfect, but they do well enough that I can get the job done. :-)

Sign In or Register to comment.

© Vanilla Keystone Theme 2025