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.

Beatmaker 3.01 update live

2456789

Comments

  • @LucidMusicInc said:
    Modstep... crazy sequencing capabilities...

    @gonekrazy3000 said:

    @Blipsford_Baubie said:
    @tja
    When recording midi, if the clip speed is set to anything other than 1x, the duration of the midi note is recorded at the wrong length. So if the clip speed is set to slower than 1x, while recording you can actually see the recording of the note run ahead of the play head. The result is a longer than desired note length during regular play back. If clip speed is set to faster than 1x, you will see the note lag behind the play head while recording. The result is shorter than desired note lengths.

    Last year I've submitted proper bug reports and on two different occasions two different devs have responded. No follow ups since. How many updates have their been since?

    Regarding note length This happens if record quantise is on. Disabling it makes it so no changes happen to note length. The recording before and after the timeline but I haven't experienced at all. Been having no issues recording midi in a year. I record into cells at 1/4th speed all the time. There's been atleast 14 betas and 3 public releases since last year. So it might have been squashed in that time.

    Shakes head at all the issues on an app that was released..............

  • @RustiK said:

    @LucidMusicInc said:
    Modstep... crazy sequencing capabilities...

    @gonekrazy3000 said:

    @Blipsford_Baubie said:
    @tja
    When recording midi, if the clip speed is set to anything other than 1x, the duration of the midi note is recorded at the wrong length. So if the clip speed is set to slower than 1x, while recording you can actually see the recording of the note run ahead of the play head. The result is a longer than desired note length during regular play back. If clip speed is set to faster than 1x, you will see the note lag behind the play head while recording. The result is shorter than desired note lengths.

    Last year I've submitted proper bug reports and on two different occasions two different devs have responded. No follow ups since. How many updates have their been since?

    Regarding note length This happens if record quantise is on. Disabling it makes it so no changes happen to note length. The recording before and after the timeline but I haven't experienced at all. Been having no issues recording midi in a year. I record into cells at 1/4th speed all the time. There's been atleast 14 betas and 3 public releases since last year. So it might have been squashed in that time.

    Shakes head at all the issues on an app that was released..............

    But I am also complex and full of bugs...you too, perhaps :)

  • @Dham said:

    @Strizbiz said:
    while I appreciate an update, I dont think we need to be hyped up before each one, the hype leading up to the launch date was plenty for me, at this point I'd rather just see theres an update when it's live, especially if it's bug fixes and not any new features, just posting the changes after the update is live works for me, lol.

    Letting us know that an update has been submitted and listing the features does not qualify as 'hype' IMHO. More like good communication between the developer and their customers. Damned if they do damned if they don't. Smh

    to each his own bro

  • Ever think of ignoring something you're not interested in? Those of us interested can carry on, and your delicate sensibilities won't be tried.

  • Let's see if we can get to page 10 of this thread before the thing drops.

  • @Carnbot said:

    @OscarSouth said:

    @Dham said:

    @Strizbiz said:
    while I appreciate an update, I dont think we need to be hyped up before each one, the hype leading up to the launch date was plenty for me, at this point I'd rather just see theres an update when it's live, especially if it's bug fixes and not any new features, just posting the changes after the update is live works for me, lol.

    Letting us know that an update has been submitted and listing the features does not qualify as 'hype' IMHO. More like good communication between the developer and their customers. Damned if they do damned if they don't. Smh

    This is just a copypasta thread. Fair enough Intua officially posting the advance notification on their official board. What gets copypasted ain't no thing.

    No hype, just useful to have a separate thread to discuss what's fixed or not fixed in this update than the other huge thread to wade through :)

    Yea I found it useful personally and enjoyed reading about the upcoming changes.

  • Feels like the coming update been delayed? Nowadays Apple approve apps very fast, but, perhaps something came up an Intua fixed that and reupload the new build to Apple... Who nows...

  • @ErrkaPetti said:
    Feels like the coming update been delayed? Nowadays Apple approve apps very fast, but, perhaps something came up an Intua fixed that and reupload the new build to Apple... Who nows...

    Hope it's released soon...

  • @JohnnyGoodyear said:

    @RustiK said:

    @LucidMusicInc said:
    Modstep... crazy sequencing capabilities...

    @gonekrazy3000 said:

    @Blipsford_Baubie said:
    @tja
    When recording midi, if the clip speed is set to anything other than 1x, the duration of the midi note is recorded at the wrong length. So if the clip speed is set to slower than 1x, while recording you can actually see the recording of the note run ahead of the play head. The result is a longer than desired note length during regular play back. If clip speed is set to faster than 1x, you will see the note lag behind the play head while recording. The result is shorter than desired note lengths.

    Last year I've submitted proper bug reports and on two different occasions two different devs have responded. No follow ups since. How many updates have their been since?

    Regarding note length This happens if record quantise is on. Disabling it makes it so no changes happen to note length. The recording before and after the timeline but I haven't experienced at all. Been having no issues recording midi in a year. I record into cells at 1/4th speed all the time. There's been atleast 14 betas and 3 public releases since last year. So it might have been squashed in that time.

    Shakes head at all the issues on an app that was released..............

    But I am also complex and full of bugs...you too, perhaps :)

    Will verify that I have seen a few. :*

  • Hope it's released soon too, just crashed before saving a huge sample I'd been chopping up, auto save hadn't saved a recent session....

  • edited August 2017

    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    EDIT: Just to say, I've checked this is the only layer on that pad!

  • @Michael_R_Grant said:
    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    Try altering the polyphony of the sample and then playing. That might work.

  • @Michael_R_Grant said:
    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    EDIT: Just to say, I've checked this is the only layer on that pad!

    I have something similar occur when I'm sampling from AU or IAA. I will sample to a pad then move to another pad to sample and the note from the previous pad continues to hold. I end up having to close the AU and loading it fresh to a new pad.

  • @Noirflux said:

    @Michael_R_Grant said:
    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    EDIT: Just to say, I've checked this is the only layer on that pad!

    I have something similar occur when I'm sampling from AU or IAA. I will sample to a pad then move to another pad to sample and the note from the previous pad continues to hold. I end up having to close the AU and loading it fresh to a new pad.

    Sorry if you know this but after sampling an AU then I think best practice is to unload the AU from the pad otherwise you will hear both sounds.

  • +1

    @Trueyorky said:

    @Noirflux said:

    @Michael_R_Grant said:
    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    EDIT: Just to say, I've checked this is the only layer on that pad!

    I have something similar occur when I'm sampling from AU or IAA. I will sample to a pad then move to another pad to sample and the note from the previous pad continues to hold. I end up having to close the AU and loading it fresh to a new pad.

    Sorry if you know this but after sampling an AU then I think best practice is to unload the AU from the pad otherwise you will hear both sounds.

  • I usually keep the AUv3 loaded on a separate pad and record the sample to another.

  • @Samu said:
    I usually keep the AUv3 loaded on a separate pad and record the sample to another.

    Placing a marker in my memory bank and hopefully recall when needed. Guess I know what I will be attempting later on this evening. I have a date with my guitar and a kayak prior to that.

  • @Trueyorky said:

    @Noirflux said:

    @Michael_R_Grant said:
    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    EDIT: Just to say, I've checked this is the only layer on that pad!

    I have something similar occur when I'm sampling from AU or IAA. I will sample to a pad then move to another pad to sample and the note from the previous pad continues to hold. I end up having to close the AU and loading it fresh to a new pad.

    Sorry if you know this but after sampling an AU then I think best practice is to unload the AU from the pad otherwise you will hear both sounds.

    @Samu said:
    I usually keep the AUv3 loaded on a separate pad and record the sample to another.

    I do what Samu does. When I load the AU in plugin mode then record a sound, I use the "move to next pad" option. But I still hear the another sound playing. I assumed it stop the other sound from playing. Perhaps I will just unload and address each pad separately. Thanks,

  • @Noirflux said:

    @Trueyorky said:

    @Noirflux said:

    @Michael_R_Grant said:
    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    EDIT: Just to say, I've checked this is the only layer on that pad!

    I have something similar occur when I'm sampling from AU or IAA. I will sample to a pad then move to another pad to sample and the note from the previous pad continues to hold. I end up having to close the AU and loading it fresh to a new pad.

    Sorry if you know this but after sampling an AU then I think best practice is to unload the AU from the pad otherwise you will hear both sounds.

    @Samu said:
    I usually keep the AUv3 loaded on a separate pad and record the sample to another.

    I do what Samu does. When I load the AU in plugin mode then record a sound, I use the "move to next pad" option. But I still hear the another sound playing. I assumed it stop the other sound from playing. Perhaps I will just unload and address each pad separately. Thanks,

    To clarify my procedure...
    Load the AUv3 to pad 1 set the target pad to 2 and enable move to next pad, this way the pad with the AUv3 wont play the sample.

  • @Samu said:

    @Noirflux said:

    @Trueyorky said:

    @Noirflux said:

    @Michael_R_Grant said:
    I've been recording my own samples and then playing them pitched up or down (sometimes with time stretch, sometimes without) and often there seems to be an audible 'note' playing with the sample, even if the recording isn't of anything that produces a note. Anyone else getting that? It's weird.

    EDIT: Just to say, I've checked this is the only layer on that pad!

    I have something similar occur when I'm sampling from AU or IAA. I will sample to a pad then move to another pad to sample and the note from the previous pad continues to hold. I end up having to close the AU and loading it fresh to a new pad.

    Sorry if you know this but after sampling an AU then I think best practice is to unload the AU from the pad otherwise you will hear both sounds.

    @Samu said:
    I usually keep the AUv3 loaded on a separate pad and record the sample to another.

    I do what Samu does. When I load the AU in plugin mode then record a sound, I use the "move to next pad" option. But I still hear the another sound playing. I assumed it stop the other sound from playing. Perhaps I will just unload and address each pad separately. Thanks,

    To clarify my procedure...
    Load the AUv3 to pad 1 set the target pad to 2 and enable move to next pad, this way the pad with the AUv3 wont play the sample.

    Oh okay awesome. Thanks!

  • @OscarSouth said:

    @Carnbot said:

    @OscarSouth said:

    @Dham said:

    @Strizbiz said:
    while I appreciate an update, I dont think we need to be hyped up before each one, the hype leading up to the launch date was plenty for me, at this point I'd rather just see theres an update when it's live, especially if it's bug fixes and not any new features, just posting the changes after the update is live works for me, lol.

    Letting us know that an update has been submitted and listing the features does not qualify as 'hype' IMHO. More like good communication between the developer and their customers. Damned if they do damned if they don't. Smh

    This is just a copypasta thread. Fair enough Intua officially posting the advance notification on their official board. What gets copypasted ain't no thing.

    No hype, just useful to have a separate thread to discuss what's fixed or not fixed in this update than the other huge thread to wade through :)

    Yea I found it useful personally and enjoyed reading about the upcoming changes.

    you know what would be useful to me? The actual update itself..... still waiting on it...... lol

  • Where is it? Waiting eagerly!!

  • edited August 2017

    Haven't you guys heard?

  • Ok. I know I cannot POSSIBLY be the only one who has heard.

  • @Blipsford_Baubie said:
    Haven't you guys heard?

    :(

  • edited August 2017

  • Just turned up here - anyone tried it yet?

  • The user and all related content has been deleted.
  • @tja said:

    I see auto-save world is still intact.

Sign In or Register to comment.