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 July 15th.

17172737577

Comments

  • wimwim
    edited July 2017

    @ElGregoLoco said:

    @Nicebutfun said:
    Surprisingly had a crash free slicer session for a few hours yesturday and really enjoyed using bm3.
    Not gonna bother with midi set ups for the time being.
    And really got to grips with the package.
    I feel like intua are letting me learn the app, so when the update lands i am already comfortable
    Thanks bm3 you are helping with my patience control

    Yeah, I also had a few crash free sessions, sometimes during 5-6 hours... And in this case, BM3 is like a dream come true for me. Best beat making solution ever when it will be stabilized.

    PS : @mathieugarcia do you think that it would be possible to work directly with AAC files one day or is it just not possible because of the way the app save slices and everything...? Being able to load a full recorded vinyl on a pad to cut slices is a very wonderful feature in terms of creativity, but it feels very heavy when the file must be converted to WAV format...

    Probably the file effectively needs to be converted to wav in memory for processing in the app anyway. So, memory-wise I'm guessing it would have no effect. Processing wise, it means decompressing the file first, which may not be a big deal, but might affect loading times. It could help with storage, though.

  • @ElGregoLoco said:

    @Nicebutfun said:
    Surprisingly had a crash free slicer session for a few hours yesturday and really enjoyed using bm3.
    Not gonna bother with midi set ups for the time being.
    And really got to grips with the package.
    I feel like intua are letting me learn the app, so when the update lands i am already comfortable
    Thanks bm3 you are helping with my patience control

    I also had a few crash free sessions, sometimes during 5-6 hours... And I admit that when this happens, BM3 is like a dream come true for me... Best beat making app ever when it will be stabilized !

    It tends to crash on my mini 2 when I do something involving a lot of memory like IAA sampling or rapidly swapping patterns while playing with unsaved banks. Doing one thing at a time seems to stabilise the app pretty well.

  • I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

  • @LucidMusicInc said:

    @ElGregoLoco said:

    @Nicebutfun said:
    Surprisingly had a crash free slicer session for a few hours yesturday and really enjoyed using bm3.
    Not gonna bother with midi set ups for the time being.
    And really got to grips with the package.
    I feel like intua are letting me learn the app, so when the update lands i am already comfortable
    Thanks bm3 you are helping with my patience control

    I also had a few crash free sessions, sometimes during 5-6 hours... And I admit that when this happens, BM3 is like a dream come true for me... Best beat making app ever when it will be stabilized !

    It tends to crash on my mini 2 when I do something involving a lot of memory like IAA sampling or rapidly swapping patterns while playing with unsaved banks. Doing one thing at a time seems to stabilise the app pretty well.

    This does not completly apply on my iPad Air2 sadly... This morning I had a full crash just touching a pattern to drag it on the sequencer view... Pattern that I already dragged 4-5 times on the sequencer window in the previous 30sc.

  • edited July 2017

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    At the moment only the banks will allow IAA/AB recording but to my knowledge they can be any length and easily copied over to an audio track. Simply load up your plugin on a pad and start recording. I would hope eventually that the audio tracks in the song arranger become ready for IAA/AB. You can post on the Intua forums to get a better answer maybe.

  • @ElGregoLoco said:

    @srcer said:

    @ElGregoLoco said:

    @gonekrazy3000 said:

    @ElGregoLoco said:

    @srcer said:

    @ElGregoLoco said:
    I still have regular crashes on my side (like every 5-6 hours of use) and I identified many odd behaviors when playing with audio files/pattern (like when you slice a pattern on a audio file and then want to edit it, the ending loop marker is not at the right place, etc), but after more than 30hrs on the app I can now confirm that it is (or will be in fact) wonderful... I will now probably wait until the 'public beta' is over i.e. wait for a few updates before I use it again (in the current state it is not stable enough for me to build a full project in... Too risky IMO), but I'm really looking forward to be able to use it correctly...
    Peace.

    Perhaps @mathieugarcia should add you to his beta team so you can test the forthcoming code before it's released :)

    Don't ... Just don't... I begged to be in the beta when it was opened and they rejected my proposal in a 'not very nice' way... That's why I made jokes back then to say it was a VIB (Very Important Beta)...
    I really wish I could have been part of the beta as it seems that most beta testers have not really used the thing given the instable state it is in right now...
    Yesterday night I spent 6 hours working on a project, I thought everything was fine and then I tried to save a sliced loop to AIFF so that I could reload it in the same bank on the second page of pads to slice it again with a new effect on (HP filter to make the intro, would have been good). At first it seemed to worked but once sliced to pad on the second page of the bank, the app crash completly everytime I touch pad... Another 6 hours to the trash can I guess (I already lost about 40hrs on the app trying to finalize at least one simple project, but I was never able to because of the instability of the app)... Right now, I'm very frustrated and feel like back when I was believing in Retronyms... Sad

    @Tritonman said:
    Can I delete a sound from a pad once it is put there? Is there an actual manual with an index yet?

    It seems sometimes you can and sometimes you can't... Probably linked to the fact that the sample is currently playing or not I guess... Sometimes when I cannot delete a pad, I close the app and restart it and I can then delete it ...
    The same goes with files/folders that you delete from the library on 'Edit' mode... You have to quit the app and restart it to see them disappear from the lib...
    What a good beta tested app... For sure...

    PS : Sorry for being so sarcastic and negative... But given the teasing and the first feed back from beta testers, I admit I really thought this app would be the holy grail for me.. .And therefore, I am very disapointed today...
    I still love what the app intend to propose and the functionnalities it tries to achieve... But the fact that it is so buggy and instable make it impossible to finish a project...
    I mean, it's supposed to be really more suited to my sample based music style than Gadget (for which it take me hours to put to the right tempo and slice loops outside the app before I load in Bilbao) but at least, Gadget has never crashed on me, has always been supa stable on my iPad Air2 and allows me to finalize music projects (it does less than BM3 regarding samples, but at least it does it correctly).

    Its getting a bit old with you constantly stating the fact that they turned you down from the beta. i think i personally have seen at-least 10+ posts now. you're bitter that they turned you down. we get it. but please stop posting it again and again.

    Yes. the app is a mess. no i am not a tester. that being said the release branch isn't the betas the testers have. its atleast a couple versions behind. so many of these bugs have already been fixed. I'm just going to patiently wait till the broken stuff gets fixed. but even in its broken state this is the best sampler on IOS. I'm having a blast tinkering around in it for the challenge @JangoMango created.

    I understand why you say that, but I don't think I complained about not being part of the beta for weeks now...
    And here, I was just replying to someone suggesting that it would be a good idea if I was part of the beta given the love I got for the app, the time I spend on it and the number of bugs I identify... That's it, I was not trying to complain more about the beta on my side.

    Plus, the last 2 pages of the thread make me feel a bit better as at least 3-4 other people, including you, confirm that the app is a bug fiesta in its current state and cannot be used to make complete projects as is...
    I admit that I completly misunderstood the devs communication before release then... I really thought that they delayed the release for months several times and asked 'fans' to be patient about it because they intended to release something fully ironed and stable... That's why I'm disappointed.
    But at least, now, experiencing that much bugs and crashes, I feel like I'm part of the beta... Lol

    Peace and sorry again for bothering you man.

    The mea culpa is on my shoulders. I didn't mean to bring up a sore subject. Just wanted to get @mathieugarcia 's attention, since here is a very passionate person who wants just the kind of workflow this app was made for and has dedicated much time only to find bugs that maybe no one else can help reproduce. Regardless I just want this app to live up to its potential :)

    Very nice man, I appreciate a lot.
    But I'm not the only passionate slicer which reports bugs on this forum... We are many good and free (we even paid for it lol) beta testers on this forum.
    For example, I'm in the same position as the man @AudioGus ... I love the app, but have bad crashes when using the slicer sometimes.
    Devs said yesterday on Twitter that a v3.0.1 in which some unexpected crashes are fixed is on the way...
    Fingers crossed

    PS: I think people need to realise that the guys who are complaining here about crashes and bugs are probably the strongest lovers of the app from the beginning... The expressed frustrations are only the results of months of high expectations. Peace.

    Hey. i'm curious. are you still using an Air2 ? with or without an audio interface ?

  • @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    add an audio track. set its input to the pad you have blocs wave on. click record. it should record into the timeline.

  • @gonekrazy3000 said:

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    add an audio track. set its input to the pad you have blocs wave on. click record. it should record into the timeline.

    Damn good idea!

  • @gonekrazy3000 said:

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    add an audio track. set its input to the pad you have blocs wave on. click record. it should record into the timeline.

    Ohhh, thanks.

    I was doing the sampling thing, which you'd load the IAA app on the bank/pad and go into the sampling screen and record it. It was actually kinda working except for a click at the end of the loop that existed no matter what. I tried applying some crossfade to the loop but it always clicked at the end.

    Maybe that way I can record a nice-sounding continuous loop.

    Not quite there emulating Ableton Live basic functionality, but almost.

  • @LucidMusicInc said:

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    At the moment only the banks will allow IAA/AB recording but to my knowledge they can be any length and easily copied over to an audio track. Simply load up your plugin on a pad and start recording. I would hope eventually that the audio tracks in the song arranger become ready for IAA/AB. You can post on the Intua forums to get a better answer maybe.

    Thanks for the input, I kinda stumbled upon this exact same solution as I stated in the message above.

    But no matter what I did, I always got a noise click at the end of the loop.
    Not in the wavefile, but the noise click happens when it reaches the end and it loops to the beginning.
    Which makes it unusable.

  • @Retzilience said:

    @LucidMusicInc said:

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    At the moment only the banks will allow IAA/AB recording but to my knowledge they can be any length and easily copied over to an audio track. Simply load up your plugin on a pad and start recording. I would hope eventually that the audio tracks in the song arranger become ready for IAA/AB. You can post on the Intua forums to get a better answer maybe.

    Thanks for the input, I kinda stumbled upon this exact same solution as I stated in the message above.

    But no matter what I did, I always got a noise click at the end of the loop.
    Not in the wavefile, but the noise click happens when it reaches the end and it loops to the beginning.
    Which makes it unusable.

    So ... edit the sample? The sample editor is excellent once you get familiar with it. It's super easy to zoom in to the end and/or beginning of the sample, then highlight the noise and fade it out. There are super useful buttons that look like <| and |>, which take you to the beginning or end, and zoom way in with one click. The fade and other functions are under the "Process" button.

    I've not had clicking problems myself, but my audio tends to end pretty cleanly within the loop. Clicks can be a problem especially if you have sustaining sounds at the end of the loop.

  • @wim said:

    @Retzilience said:

    @LucidMusicInc said:

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    At the moment only the banks will allow IAA/AB recording but to my knowledge they can be any length and easily copied over to an audio track. Simply load up your plugin on a pad and start recording. I would hope eventually that the audio tracks in the song arranger become ready for IAA/AB. You can post on the Intua forums to get a better answer maybe.

    Thanks for the input, I kinda stumbled upon this exact same solution as I stated in the message above.

    But no matter what I did, I always got a noise click at the end of the loop.
    Not in the wavefile, but the noise click happens when it reaches the end and it loops to the beginning.
    Which makes it unusable.

    So ... edit the sample? The sample editor is excellent once you get familiar with it. It's super easy to zoom in to the end and/or beginning of the sample, then highlight the noise and fade it out. There are super useful buttons that look like <| and |>, which take you to the beginning or end, and zoom way in with one click. The fade and other functions are under the "Process" button.

    I've not had clicking problems myself, but my audio tends to end pretty cleanly within the loop. Clicks can be a problem especially if you have sustaining sounds at the end of the loop.

    I checked the end of the loop, there's no click there, I think the click came from the process of looping instead of the sample.

    I was using it with the ipad internal engine, it wasn't hooked to my audio interface, I may have to test that.

  • @Retzilience said:

    @wim said:

    @Retzilience said:

    @LucidMusicInc said:

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    At the moment only the banks will allow IAA/AB recording but to my knowledge they can be any length and easily copied over to an audio track. Simply load up your plugin on a pad and start recording. I would hope eventually that the audio tracks in the song arranger become ready for IAA/AB. You can post on the Intua forums to get a better answer maybe.

    Thanks for the input, I kinda stumbled upon this exact same solution as I stated in the message above.

    But no matter what I did, I always got a noise click at the end of the loop.
    Not in the wavefile, but the noise click happens when it reaches the end and it loops to the beginning.
    Which makes it unusable.

    So ... edit the sample? The sample editor is excellent once you get familiar with it. It's super easy to zoom in to the end and/or beginning of the sample, then highlight the noise and fade it out. There are super useful buttons that look like <| and |>, which take you to the beginning or end, and zoom way in with one click. The fade and other functions are under the "Process" button.

    I've not had clicking problems myself, but my audio tends to end pretty cleanly within the loop. Clicks can be a problem especially if you have sustaining sounds at the end of the loop.

    I checked the end of the loop, there's no click there, I think the click came from the process of looping instead of the sample.

    I was using it with the ipad internal engine, it wasn't hooked to my audio interface, I may have to test that.

    Some suggestions to test:

    • If you take that same sample into AUM or another app does it loop without a click?
    • Did you check the beginning of the loop? Try a 3ms fade in?
    • Check the loop markers carefully in BM3. I've found that there are sometimes three that need to be checked / adjusted to all agree: the song loop markers, the clip end point, and the sample end point.
    • Try switching disk streaming on and off to see if there's any difference.
  • Hey hey, just bought and installed BM3 and couldn't find transient detection in slice mode. Did a Google search to see if I was missing something, and it took me to page 57 of this thread, where it seems others are frustrated too about the fact that it's not included! I'm feeling like I wasted my money here because I bought it specifically for this functionality (mainly for sampling a whole bunch of Nord Drum one-shots at the same time), after having read elsewhere on this forum that it was going to be an included feature. There are 20+ pages after this one that I don't want to wade through just for this info, just wondering if someone can help me: have they confirmed they are adding it, or is it radio silence? Any help would be very appreciated.

  • @wim said:

    @Retzilience said:

    @wim said:

    @Retzilience said:

    @LucidMusicInc said:

    @Retzilience said:

    I'm sorry if that's already been discussed, but I need some help.

    I'm starting to get the hang of banks together with IAa

    I have no trouble recording internal sequences or external synths, but I'm having some trouble to understand sample recording,

    Simple example : if I want to record a blocswave loop live, how should I do it?

    At the moment only the banks will allow IAA/AB recording but to my knowledge they can be any length and easily copied over to an audio track. Simply load up your plugin on a pad and start recording. I would hope eventually that the audio tracks in the song arranger become ready for IAA/AB. You can post on the Intua forums to get a better answer maybe.

    Thanks for the input, I kinda stumbled upon this exact same solution as I stated in the message above.

    But no matter what I did, I always got a noise click at the end of the loop.
    Not in the wavefile, but the noise click happens when it reaches the end and it loops to the beginning.
    Which makes it unusable.

    So ... edit the sample? The sample editor is excellent once you get familiar with it. It's super easy to zoom in to the end and/or beginning of the sample, then highlight the noise and fade it out. There are super useful buttons that look like <| and |>, which take you to the beginning or end, and zoom way in with one click. The fade and other functions are under the "Process" button.

    I've not had clicking problems myself, but my audio tends to end pretty cleanly within the loop. Clicks can be a problem especially if you have sustaining sounds at the end of the loop.

    I checked the end of the loop, there's no click there, I think the click came from the process of looping instead of the sample.

    I was using it with the ipad internal engine, it wasn't hooked to my audio interface, I may have to test that.

    Some suggestions to test:

    • If you take that same sample into AUM or another app does it loop without a click?
    • Did you check the beginning of the loop? Try a 3ms fade in?
    • Check the loop markers carefully in BM3. I've found that there are sometimes three that need to be checked / adjusted to all agree: the song loop markers, the clip end point, and the sample end point.
    • Try switching disk streaming on and off to see if there's any difference.

    Thanks A LOT for your input. I'll test all above.

  • @HandOfEmpty said:

    Hey hey, just bought and installed BM3 and couldn't find transient detection in slice mode. Did a Google search to see if I was missing something, and it took me to page 57 of this thread, where it seems others are frustrated too about the fact that it's not included! I'm feeling like I wasted my money here because I bought it specifically for this functionality (mainly for sampling a whole bunch of Nord Drum one-shots at the same time), after having read elsewhere on this forum that it was going to be an included feature. There are 20+ pages after this one that I don't want to wade through just for this info, just wondering if someone can help me: have they confirmed they are adding it, or is it radio silence? Any help would be very appreciated.

    Pretty sure that they confirmed it's going back in eventually. It was removed from release version for some reason. But no idea when this will happen.

  • @HandOfEmpty said:
    Hey hey, just bought and installed BM3 and couldn't find transient detection in slice mode. Did a Google search to see if I was missing something, and it took me to page 57 of this thread, where it seems others are frustrated too about the fact that it's not included! I'm feeling like I wasted my money here because I bought it specifically for this functionality (mainly for sampling a whole bunch of Nord Drum one-shots at the same time), after having read elsewhere on this forum that it was going to be an included feature. There are 20+ pages after this one that I don't want to wade through just for this info, just wondering if someone can help me: have they confirmed they are adding it, or is it radio silence? Any help would be very appreciated.

    I was also really disappointed that slice by transients was not included in the initial release. Although I won't go so far as to say I feel like I wasted money on BM3.

    According to the developer's comments on the Intua Forum it should be available in an update. I'm hoping that it will be available in the first update.

    From the Intua Forum:

    "-'Slice by transient' with sensitivity knob (I thought this was a confirmed feature but I'm only able to slice to grid etc).
    We'll bring this one back, it's in there but results were not consistent enough to make it "release worthy".

    https://intua.net/forums/discussion/comment/17202/#Comment_17202

  • edited July 2017

    Thanks for the answers, I appreciate it.

    Also figured out a work around for part of what I want to do with it.

    One cool trick I'd heard about elsewhere, using 'fixed level' but adding expression by mapping filter cutoff to velocity: (which is buggy unfortunately)

    Go to Modulations for a Sample then BYPASS the default mapping of Note Velocity to Gain - this will effectively sound the same as "fixed level", so every time you play a note (from a controller that sends velocity) it will play back the sound at the same level, whatever you've got the gain set to.

    Then, go back to the sample page and add a low pass filter, set its level to the minimum (i.e filter closed), then doube tap and map it to Midi - Note Velocity. Notes will play back at full level, with the filter opening up depending how hard you hit the pad or key of whatever controller you're using.

    Sounds great, but...

    Bug 1:

    If the filter is already open, then you play a lower velocity note, the very beginning of the new note will play before the filter closes, resulting in a click.

    Maybe Bug 2:

    Setting a pad to "fixed level velocity" also "flattens" out the midi, meaning Midi Note Velocity can't be used to modulate anything else unless you use the workaround I described above, which is a bit unintuitive I think, took me a bit of headscratching to figure it out.

    I think Bug 1 is definitely worth fixing ASAP - being able to map filter to velocity should definitely be something that works without hiccups! Is this a known bug? If they fix thix, I'll probably keep using the app.

  • Finally got rid of all the samples shipped with this and am now down to around 380 mb's . Waiting on transport bar or the ability to use this properly with audiobus . Planning on using just for sampling now but it is not playing nice with Cubasis. Hopefully Intua gets this fix into the first update.

  • edited July 2017

    Intua are fully on top of the AU loading issue. I could load a session with 16 instances of Ruismaker FM without a hitch in the latest beta.

  • @Tritonman said:
    Finally got rid of all the samples shipped with this and am now down to around 380 mb's . Waiting on transport bar or the ability to use this properly with audiobus . Planning on using just for sampling now but it is not playing nice with Cubasis. Hopefully Intua gets this fix into the first update.

    This doesn't make sense as BM3 ships at approx 120mb

  • Thanks for awesome update!

    @brambos said:
    Intua are fully on top of the AU loading issue. I could load a session with 16 instances of Ruismaker FM without a hitch in the latest beta.

  • @MusicMan4Christ said:
    Thanks for awesome update!

    @brambos said:
    Intua are fully on top of the AU loading issue. I could load a session with 16 instances of Ruismaker FM without a hitch in the latest beta.

    +1

  • Anyone having problems downloading IAP content?

  • @thesoundtestroom said:
    Anyone having problems downloading IAP content?

    INTUA addressed this in the 3.0.1 beta. Not sure when it's going to be released.

  • @philowerx said:

    @thesoundtestroom said:
    Anyone having problems downloading IAP content?

    INTUA addressed this in the 3.0.1 beta. Not sure when it's going to be released.

    Cheers

  • @philowerx said:

    @thesoundtestroom said:
    Anyone having problems downloading IAP content?

    INTUA addressed this in the 3.0.1 beta. Not sure when it's going to be released.

    Pretty sure I saw something earlier (Saturday) saying will be out next week including more sounds.

  • I've been busy creating my own instruments sampling apps like Kaspar, iM1, Sampletank and even the piano from Module. It's a doddle and sounds great :)

  • Does anyone else have any issues deleting samples? Press delete but they remain for me.

  • @Carnbot said:
    Does anyone else have any issues deleting samples? Press delete but they remain for me.

    If they are used in an open session, you have to close the session before delete is enabled.

Sign In or Register to comment.