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.

Getting Gadget to play nice with other apps...

I've owned Gadget for two days, didn't take too long for the limitations to start annoying me...

I have a track that is based on some guitar swells, at 100bpm each swell lasts four bars, which is 9.6 seconds, so using Bilbao is not an option.

So far the best setup I have managed is to use Audiobus with Gadget in the input and Loopy in the output so that then I can use the AB transport controls to start and stop the track. The main problem there is that the MIDI clock drifts audibly, so I also have to load MIDIFlow up and then use that to control the clock and send it to both Gadget and Loopy (I also tried MIDIBus but that still had the drift).

The setup works but it's cumbersome. Has anyone with more experience in Gadget got a more elegant solution?

Comments

  • edited June 2015

    My advice is forget trying to sync gadget with something else and have them play nicely together... it will drive you mad and is a not a good workflow. having said that, you should be able to send midi clock out from Loopy to Gadget (i've done this) and cut MIDIFlow out of the equation... but even so - for a whole song this is still rubbish... I wouldn't go down this route.

    I would simply chop you 4 bar guitar sample in half (2 x 2 bars ) and then load each half into Bilbao and then trigger on the first and third bar respectively. Should work fine. If you hear a slight click then don't worry about it, because if you're going to end up in Aura finally, you can go back and replace with the original 4 bar sample.

    But for workflow, this allows yu to get on with the rest of your track in gadget and trigger the guitar part wherever you want in your composition.

    My advice is, when composing, stick only to Gadget and bring things in as samples if needed. It's a wonderful self contain and fast composition environment. It doesn't play nicely with anything else particularly (apart from sending midi note and ccs INTO gadget - which works really well).

  • @richardyot - P.S. - Based on your post yesterday... i tried out a bit of Kiev earlier and worked out how to get some nice glitchy stuff out of it... So thanks.

  • @richardyot said:
    I've owned Gadget for two days, didn't take too long for the limitations to start annoying me...

    I have a track that is based on some guitar swells, at 100bpm each swell lasts four bars, which is 9.6 seconds, so using Bilbao is not an option.
    The setup works but it's cumbersome. Has anyone with more experience in Gadget got a more elegant solution?

    You could also try importing your 9.6 second sample into Abu (10 seconds max) - then moving most of the chop markers to the far right - until you have say 3 left only - take those and chop your guitar sample into 4 bits. (or you could try 2 also with just one chop marker in the middle)

    I've been lucky in that Gadget syncs well for me with Loopy - I don't find it drifts out of sync too bad, but I often do a stop/start in Loopy to resync just to be safe. I record 2 or 4 bar loops into Loopy and import to Gadget, but those pops and clicks in Bilboa and Abu really drive me nuts - sometimes I get lucky and import a loop and it's not bad though. (I posted a comment on the Korg forums about this and got a reply that it "will be passed along to the developers" about 2 weeks ago ... )

  • @Halftone said:
    You could also try importing your 9.6 second sample into Abu (10 seconds max) - then moving most of the chop markers to the far right - until you have say 3 left only - take those and chop your guitar sample into 4 bits. (or you could try 2 also with just one chop marker in the middle)

    The problem with this is - I found it doesn't work. The issue is that Abu has a built in decay that kicks on on a sample longer than a few seconds... It starts fading it out. Pretty annoying. But you'll get a duck in sound towards the end of the 2nd and the 4th bar if you do this.

    Instead you should chop into <5 secs (using Audioshare which will give you a tiny microfade to avoid a click) and put into 2 different Bilbao patches.

  • Method I often use -- not for everyone. Depends on your music.

    Here it is. I actually take any loops or samples I want to use in Gadget, and first tweak them in Egoist. It allows me to tailor and process any manipulations or transpose any particular areas. Narrowing and refining my sample to a preferable state. I then bring them into gadget or even to Samplr.

    This may not be what you wanted to know. But, since you are new to Gadget, I thought I would put it out there.

    Oh, syncing. I use with Cubasis and have NO issues syncing or timing. I use the "external" only clock setting in upper right menu choices of Gadget.

    Just have patience. You have it 48 hours. I buy new apps and don't use them for longer periods then that for the first time. Or even open them.

  • I would simply chop you 4 bar guitar sample in half (2 x 2 bars ) and then load each half into Bilbao and then trigger on the first and third bar respectively. Should work fine. If you hear a slight click then don't worry about it, because if you're going to end up in Aura finally, you can go back and replace with the original 4 bar sample.

    Simple as that is (the replacing it in Auria anyway part) it has never occurred to my 'make it pretty now' mindset, so grazie etc.

  • xenxen
    edited June 2015

    @RustiK

    +1 for syncing with Cubasis. I find that works well.

  • Kiev an also make some great dark techstep atmospheres too..

    @Matt_Fletcher_2000 said:
    richardyot - P.S. - Based on your post yesterday... i tried out a bit of Kiev earlier and worked out how to get some nice glitchy stuff out of it... So thanks.

  • @richardyot said:
    I've owned Gadget for two days, didn't take too long for the limitations to start annoying me...

    I have a track that is based on some guitar swells, at 100bpm each swell lasts four bars, which is 9.6 seconds, so using Bilbao is not an option.

    So far the best setup I have managed is to use Audiobus with Gadget in the input and Loopy in the output so that then I can use the AB transport controls to start and stop the track. The main problem there is that the MIDI clock drifts audibly, so I also have to load MIDIFlow up and then use that to control the clock and send it to both Gadget and Loopy (I also tried MIDIBus but that still had the drift).

    Loopy and Gadget sync really well for me, I've tested with both metronomes running for a while. It works to the point where I have performed with them working in sync.

Sign In or Register to comment.