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.

EG Pulse - ElliottGarage new AU3 Drum Machine - available right now on App Store

1…3031333536…62

Comments

  • ipadbeatmakingipadbeatmaking
    edited October 2019

    @ElliottGarage what are the default root notes for each pad and are they changeable? To clarify if I have a drum that’s naturally tuned d3 when I go to the chromatic mode what keys am I actually playing when I hit D3 on the chromatic pad? Is the root being read in the file name and automatically being set or is it always C3 or something else. Hope im making sense. Thanks

  • ElliottGarageElliottGarage
    edited October 2019

    @ipadbeatmaking I'm planning to add a loop root key recognizer, but at the moment the root is automatically assigned to C3 even if is another note, that's just a visual identifier

  • bcrichardsbcrichards

    So, I downloaded the update. I'm noticing that there is no Assign button for just regular, manual slicing, and doesn't look like there's anyway to commit these slices to pads. I'm getting some crashing while adjusting slice points as well/changing slice modes as well.

  • ipadbeatmakingipadbeatmaking

    @ElliottGarage said:
    @ipadbeatmaking I'm planning to add a loop root key recognizer, but at the moment the root is automatically assigned to C3 even if is another note, that's just a visual identifier

    Thanks 🙏

  • ElliottGarageElliottGarage

    @bcrichards doh, that was a last second change bug! I'm fixing it

  • espiegel123espiegel123

    @ElliottGarage said:
    @Peblin thanks for your feedback, that's a good idea. I'm also thinking about triplets and a more flexible timeline in general...so maybe changing the engine and the way I store sequences it's the cleaner (but longer and problematic too) way. Maybe we can talk more in private message (I'm gonna check Flow btw) :)
    If I think that all started from a simple 16 step sequencer engine in 2011 :D

    IMO, it is worth taking a look at BeatHawk's step editor. They handle grids nicely. It is easy to mix different types of notes and tuplets even for the same part by changing the grid -- i.e. it is no problem to have a part that has both eighth notes and triplets and sixteenth notes.

  • [Deleted User][Deleted User]

    @bcrichards said:
    So, I downloaded the update. I'm noticing that there is no Assign button for just regular, manual slicing, and doesn't look like there's anyway to commit these slices to pads. I'm getting some crashing while adjusting slice points as well/changing slice modes as well.

    Same crash for me too.

  • ElliottGarageElliottGarage

    @MonzoPro I'm submitting the fix...

  • [Deleted User][Deleted User]

    @ElliottGarage said:
    @MonzoPro I'm submitting the fix...

    Thank you

  • ipadbeatmakingipadbeatmaking

    @ElliottGarage it’s probably right in my face but how do u import a full kit in Pulse (an .egkit file)?

  • bcrichardsbcrichards

    @ElliottGarage said:
    @bcrichards doh, that was a last second change bug! I'm fixing it

    Nice! no worries. Think you’ll add copy/paste pad :) ?

  • bouncebounce

    Thanks for this! Hoping for that bottom left kick orientation and then everything else is whipped cream on top. I’ve got a couple instances going and had this error in AUM “ ElliottGarage: EG Pulse was invalidated. Maybe it crashed.” ipad 10.5.. probably RAM related?

  • bouncebounce

    @david_2017 said:
    8x8 Grid for chromatic? Oh... I said it...

    Ha, I already said it too, don’t sweat it. Been able to get some wild stuff out of this one already so...just grateful how far it has come and curious how far it can go. Champion app.

  • ipadbeatmakingipadbeatmaking

    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

  • echooperaechoopera

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

  • ipadbeatmakingipadbeatmaking

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

  • anicktanickt

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

  • wimwim

    On iPhone 7, iOS 13.1.2, > @anickt said:

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

    Yep. That’s a common mismatch between apps and even hardware. It’s just part of life with midi.

    @echoopera, are you having other midi in issues, or just that one?

  • ipadbeatmakingipadbeatmaking

    @wim said:
    On iPhone 7, iOS 13.1.2, > @anickt said:

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

    Yep. That’s a common mismatch between apps and even hardware. It’s just part of life with midi.

    @echoopera, are you having other midi in issues, or just that one?

    Thanks for the enlightenment. Pardon my ignorance to this and how it’ll probably read, as I’m not trying to be inconsiderate to our hard working devs, but I’m curious: the ‘fix’ needs to come from which side? EG or Cubasis? Or is it hopeless?

  • espiegel123espiegel123

    @ipadbeatmaking said:

    @wim said:
    On iPhone 7, iOS 13.1.2, > @anickt said:

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

    Yep. That’s a common mismatch between apps and even hardware. It’s just part of life with midi.

    @echoopera, are you having other midi in issues, or just that one?

    Thanks for the enlightenment. Pardon my ignorance to this and how it’ll probably read, as I’m not trying to be inconsiderate to our hard working devs, but I’m curious: the ‘fix’ needs to come from which side? EG or Cubasis? Or is it hopeless?

    It's not a bug. You just need to be aware that octave numbering is ambiguous and that different apps and synths may use different octave numbering. The actual midi note numbers are the same but what they call the octaves varies.

  • zvonzvon
    edited October 2019

    @ipadbeatmaking said:
    @ElliottGarage it’s probably right in my face but how do u import a full kit in Pulse (an .egkit file)?

    Just made a quick test, I exported a kit to Google Drive, deleted it from EG Pulse and I imported it with the “open in” command. It worked perfectly.

    I am assuming it will work the same way with email, iCloud, Dropbox and more.

  • ipadbeatmakingipadbeatmaking

    @zvon said:

    @ipadbeatmaking said:
    @ElliottGarage it’s probably right in my face but how do u import a full kit in Pulse (an .egkit file)?

    Just made a quick test, I exported a kit to Google Drive, deleted it from EG Pulse and I imported it with the “open in” command. It worked perfectly.

    I am assuming it will work the same way with email, iCloud, Dropbox and more.

    You’re right. I figured this out a couple hours ago. There’s was no clear indication for me at first but they showed up. Thanks

  • ipadbeatmakingipadbeatmaking

    @espiegel123 said:

    @ipadbeatmaking said:

    @wim said:
    On iPhone 7, iOS 13.1.2, > @anickt said:

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

    Yep. That’s a common mismatch between apps and even hardware. It’s just part of life with midi.

    @echoopera, are you having other midi in issues, or just that one?

    Thanks for the enlightenment. Pardon my ignorance to this and how it’ll probably read, as I’m not trying to be inconsiderate to our hard working devs, but I’m curious: the ‘fix’ needs to come from which side? EG or Cubasis? Or is it hopeless?

    It's not a bug. You just need to be aware that octave numbering is ambiguous and that different apps and synths may use different octave numbering. The actual midi note numbers are the same but what they call the octaves varies.

    Ok I see. Another thing, While physically playing (not drawing notes) the pads Live in Cubasis in chromatic mode those notes aren’t registering/recording at all as anything but c1. Thoughts?

  • espiegel123espiegel123

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:

    @wim said:
    On iPhone 7, iOS 13.1.2, > @anickt said:

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

    Yep. That’s a common mismatch between apps and even hardware. It’s just part of life with midi.

    @echoopera, are you having other midi in issues, or just that one?

    Thanks for the enlightenment. Pardon my ignorance to this and how it’ll probably read, as I’m not trying to be inconsiderate to our hard working devs, but I’m curious: the ‘fix’ needs to come from which side? EG or Cubasis? Or is it hopeless?

    It's not a bug. You just need to be aware that octave numbering is ambiguous and that different apps and synths may use different octave numbering. The actual midi note numbers are the same but what they call the octaves varies.

    Ok I see. Another thing, While physically playing (not drawing notes) the pads Live in Cubasis in chromatic mode those notes aren’t registering/recording at all as anything but c1. Thoughts?

    Not sure. I don’t spend much time in Cubasis these days, Could you post a video demonstrating?

  • ipadbeatmakingipadbeatmaking

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:

    @wim said:
    On iPhone 7, iOS 13.1.2, > @anickt said:

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

    Yep. That’s a common mismatch between apps and even hardware. It’s just part of life with midi.

    @echoopera, are you having other midi in issues, or just that one?

    Thanks for the enlightenment. Pardon my ignorance to this and how it’ll probably read, as I’m not trying to be inconsiderate to our hard working devs, but I’m curious: the ‘fix’ needs to come from which side? EG or Cubasis? Or is it hopeless?

    It's not a bug. You just need to be aware that octave numbering is ambiguous and that different apps and synths may use different octave numbering. The actual midi note numbers are the same but what they call the octaves varies.

    Ok I see. Another thing, While physically playing (not drawing notes) the pads Live in Cubasis in chromatic mode those notes aren’t registering/recording at all as anything but c1. Thoughts?

    Seems the secret solution to the chromatic dilemma is to use the hosts keyboard whilst the pads are set to chromatic mode for your chosen sound. That allows u to play/track them live into the sequencer and they come out properly in Cubasis.

  • espiegel123espiegel123

    @ipadbeatmaking said:

    @ipadbeatmaking said:

    @espiegel123 said:

    @ipadbeatmaking said:

    @wim said:
    On iPhone 7, iOS 13.1.2, > @anickt said:

    @ipadbeatmaking said:

    @echoopera said:

    @ipadbeatmaking said:
    Maybe I’m wrong but in Cubasis the midi out seems to be outputing an octave down when drawing in the notes on the editor of Cubasis from the app in chromatic modes. Drawing a C3 but the playback in Cubasis is reflecting a c2 after drawing. To be clear it’s c3 on the grid but the sound coming out is a c2.

    And also directly recording into Cubasis from playing the pads in chromatic mode is only outputting c1 to the timeline no matter what notes are played. To be clear I’m attempting to bypass the sequencer section of the pulse AUv3 completely and just sequence directly in Cubasis. Is there a Cubasis issue or am I doing something wrong? Thanks for any help u can offer

    Yeah the midi in is really messed up. Doesn’t work as expected.

    Oh boy, things were nearly perfect...this was an unexpected encounter.

    This is due to the fact that there is not a specification for what octave C60 is in. Different synth and now app devs may do it differently. See this and google other articles on the subject.

    http://computermusicresource.com/midikeys.html

    Yep. That’s a common mismatch between apps and even hardware. It’s just part of life with midi.

    @echoopera, are you having other midi in issues, or just that one?

    Thanks for the enlightenment. Pardon my ignorance to this and how it’ll probably read, as I’m not trying to be inconsiderate to our hard working devs, but I’m curious: the ‘fix’ needs to come from which side? EG or Cubasis? Or is it hopeless?

    It's not a bug. You just need to be aware that octave numbering is ambiguous and that different apps and synths may use different octave numbering. The actual midi note numbers are the same but what they call the octaves varies.

    Ok I see. Another thing, While physically playing (not drawing notes) the pads Live in Cubasis in chromatic mode those notes aren’t registering/recording at all as anything but c1. Thoughts?

    Seems the secret solution to the chromatic dilemma is to use the hosts keyboard whilst the pads are set to chromatic mode for your chosen sound. That allows u to play/track them live into the sequencer and they come out properly in Cubasis.

    Good to know.

  • MrSmileZMrSmileZ

    Hmmm this is getting my attention....nice work!
    I may have to buy this soon

  • wimwim
    edited October 2019

    Um ... is there a way to get to the pattern selectors on the iPhone in AudioBus without having to flip to portrait?

    Even flipping to portrait requires pressing down the del or len button in landscape to get the row of selectors to float up once before it’ll appear in portrait.

  • RajahPRajahP

    @wim said:
    Um ... is there a way to get to the pattern selectors on the iPhone in AudioBus without having to flip to portrait?

    Looks like there is a button labeled ‘steps’ there..

  • wimwim
    edited October 2019

    @RajahP said:
    Looks like there is a button labeled ‘steps’ there..

    Eh. Wazzat sonny? I don’t see it. Maybe I’m a gettin’ jes’ too old.

Sign In or Register to comment.

© Vanilla Keystone Theme 2024