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.

Audio Evolution Mobile DAW

1151618202148

Comments

  • edited September 2018

    @dwrae said:

    @Janosax said:

    Are you using external MIDI gear? If not, then the app uses the host/AU communication to send timing/sync info that is way more accurate than midi clock.

    No this is for midi sync with other apps like Korg Gadget or apeMatrix.

    And they cannot be used as AUv3 or IAA?

    I’ve checked and apeMatrix and IAA sync is ok. Gadget is not listed as IAA so I’ve to use Audiobus so no sync. And Gadget as IAA has not got sync, midi clock is necessary for that.

  • @Janosax said:

    @dwrae said:

    @Janosax said:

    Are you using external MIDI gear? If not, then the app uses the host/AU communication to send timing/sync info that is way more accurate than midi clock.

    No this is for midi sync with other apps like Korg Gadget or apeMatrix.

    And they cannot be used as AUv3 or IAA?

    I’ve checked and apeMatrix and IAA sync is ok. Gadget is not listed as IAA so I’ve to use Audiobus so no sync. And Gadget as IAA has not got sync, midi clock is necessary for that.

    Ok, that's unfortunate, since that can take a while to implement.

  • @Telstar5 said:
    You mean the auv3 column on the left, right? I got that.. It’s my column on the right that’s blank, the input column. Are you saying I need to have something plugged in (as Time does /Prophet 12 ) to have something show up on that input list?

    No, you first select the input on the left. Based on what you select, the right column changes.

  • No, you first select the input on the left. Based on what you select, the right column changes.

    @dwrae : Aha! Thanks again, Davey... I don’t think Tim specified that in the video so along w double tapping for punch in, etc. this may also clarify for others.. I might even draw up a concise list once I’m done here.. Sigh of relief... Onward

  • @Telstar5 said:

    No, you first select the input on the left. Based on what you select, the right column changes.

    @dwrae : Aha! Thanks again, Davey... I don’t think Tim specified that in the video so along w double tapping for punch in, etc. this may also clarify for others.. I might even draw up a concise list once I’m done here.. Sigh of relief... Onward

    I added the change of long-tap to double tap for the marker menu as text underneath the tutorial video now. Which reminds me, this is also the case for the mixer controls: when you double tap the fader or EQ fader, you get a menu (used to be long-tap).

  • @Matt_Fletcher_2000 said:
    However, with this checked it seems like although multi-channel midi is then getting recorded into midi instrument tracks (you can hear its working while recording and you can see the multi-channel data in the midi clip afterwards), when you play the track back it doesnt sound like it’s actually sending multi-channel midi (MPE) to the AU and you can hear the cc74 data conflicting between different notes. This is with Roli Noise Melody loaded as an AU and playing the Lightblock into AEM.

    You are right. Found and fixed. A lot of this 'force channel' code comes from the time when AEM used FluidSynth as soundfont renderer, where things worked a bit different.

  • track’ and an ‘instrument midi track’ (I’m still not really sure why there needs to be two different types of midi track TBH)...

    When you are using external MIDI gear with MIDI tracks, then you don't want to have things like EQ and insert effects on your mixer channel since they won't do anything.

  • @Matt_Fletcher_2000 said:
    Found two more bugs with this update (not sure if they were in the last update). This is testing with both a ‘midi track’ and an ‘instrument midi track’ (I’m still not really sure why there needs to be two different types of midi track TBH)...

    1. You record midi in once at the very start of your song. Remove the midi clip. Then record again and you get what appears to be a blank midi clip. When you go into it you see just a single grey note that begins way before the 00.00 position at the start of the song. But it doesn’t play. No other notes have been recorded. This doesn’t happen always, just about 50% of the time.

    2. I’m playing about 8 bars and recording in but then it makes a midi clip that’s only about 4 bar long. Where’s the rest of my performance? It hasn’t recorded it... This is the same every time. The last 4 bars or so of my playing don’t get recorded.

    Both these issues are with the Lightblock playing MPE midi into the ‘midi track’.

    I just tried several times with the Lightblock, both into a MIDI instrument track and MIDI track, but I cannot reproduce it. I also tried with the count-in, since you seem to be using that in the video, but that works as expected as well here. Can you still reproduce it, and if so, can you reproduce it without the metronome and count-in being on, just in case it is related to that?

  • edited September 2018

    I made the lane separation lines grey and the default values for the parameters in the automation display are now drawn in light grey (dotted). For example, for panning it is the center, for volume it is the 0dB line. White cannot be used as lane separation line since it is used to indicate the selected track. Please note that the image has been scaled down to 40%, so it might be less clear than on a real screen. I hope this helps.

  • @dwrae those new lane lines look good.

    +1 for the request for track numbers. When you are chopping samples like in the video above every track has the same name as they are clips of the same source track so it is difficult to understand which track you are working on as you scroll (other than remembering the colour).

    Once you have all your sample clips in many tracks is there a quick way to save them all to audio files in one go or do you have to do them one by one. One click with auto naming would be a real timesaver.

    Thx!

  • @gusgranite said:
    +1 for the request for track numbers. When you are chopping samples like in the video above every track has the same name as they are clips of the same source track so it is difficult to understand which track you are working on as you scroll (other than remembering the colour).

    You can rename tracks.

    Once you have all your sample clips in many tracks is there a quick way to save them all to audio files in one go or do you have to do them one by one. One click with auto naming would be a real timesaver.

    Saving all individual clips as audio files is not a typical thing to do IMHO. You can render the whole project as one stereo file, or you can render all tracks at once (stems).

  • @dwrae said:

    @gusgranite said:
    +1 for the request for track numbers. When you are chopping samples like in the video above every track has the same name as they are clips of the same source track so it is difficult to understand which track you are working on as you scroll (other than remembering the colour).

    You can rename tracks.

    Once you have all your sample clips in many tracks is there a quick way to save them all to audio files in one go or do you have to do them one by one. One click with auto naming would be a real timesaver.

    Saving all individual clips as audio files is not a typical thing to do IMHO. You can render the whole project as one stereo file, or you can render all tracks at once (stems).

    No problem. I’m bringing the sample choppers requests! :smile:

    So I am looking for the fastest way to loop, chop, auto fade 3ms off the beginning and end of each slice, and then save slices as audio files. I understand that this probably was not intended use case however. It’s close though!

  • Sorry if I missed it, can you automate more than one parameter?

  • @JudgeDredd said:
    Sorry if I missed it, can you automate more than one parameter?

    Yes, just select the actual parameter to edit in the left panel.

  • @dwrae said:

    @JudgeDredd said:
    Sorry if I missed it, can you automate more than one parameter?

    Yes, just select the actual parameter to edit in the left panel.

    Ahh.. I see the ones that have automation assigned to them are marked with a (*)

    Most excellent!

  • @dwrae said:

    I made the lane separation lines grey and the default values for the parameters in the automation display are now drawn in light grey (dotted). For example, for panning it is the center, for volume it is the 0dB line. White cannot be used as lane separation line since it is used to indicate the selected track. Please note that the image has been scaled down to 40%, so it might be less clear than on a real screen. I hope this helps.

    I’m sure it will be better than before 🙂 Thank you!!

  • @gusgranite said:
    @dwrae those new lane lines look good.

    +1 for the request for track numbers. When you are chopping samples like in the video above every track has the same name as they are clips of the same source track so it is difficult to understand which track you are working on as you scroll (other than remembering the colour).

    Once you have all your sample clips in many tracks is there a quick way to save them all to audio files in one go or do you have to do them one by one. One click with auto naming would be a real timesaver.

    Thx!

    Agreed! This would be really helpful! Also, if you could make the selected track lines (the white lines) bolder, it will be easier to see the track that is selected. Please! 🙂

  • edited September 2018

    @dwrae said:

    @Matt_Fletcher_2000 said:
    Found two more bugs with this update (not sure if they were in the last update). This is testing with both a ‘midi track’ and an ‘instrument midi track’ (I’m still not really sure why there needs to be two different types of midi track TBH)...

    1. You record midi in once at the very start of your song. Remove the midi clip. Then record again and you get what appears to be a blank midi clip. When you go into it you see just a single grey note that begins way before the 00.00 position at the start of the song. But it doesn’t play. No other notes have been recorded. This doesn’t happen always, just about 50% of the time.

    2. I’m playing about 8 bars and recording in but then it makes a midi clip that’s only about 4 bar long. Where’s the rest of my performance? It hasn’t recorded it... This is the same every time. The last 4 bars or so of my playing don’t get recorded.

    Both these issues are with the Lightblock playing MPE midi into the ‘midi track’.

    I just tried several times with the Lightblock, both into a MIDI instrument track and MIDI track, but I cannot reproduce it. I also tried with the count-in, since you seem to be using that in the video, but that works as expected as well here. Can you still reproduce it, and if so, can you reproduce it without the metronome and count-in being on, just in case it is related to that?

    I'll try again when I have time, without metronome and without count in. I'll also try with a "normal keyboard" as a control.

    Maybe the midi stream is "crashing"? Can't cope with the amount of midi being sent on multiple channels from the lightblock? So it records for a bit and then stops after a certain number of notes?

  • @dwrae I believe I've found a bug in "Count-In" when recording midi. When Count In is active (1bar or 2bars, it doesn't matter), the midi track that is being recorded doesn't record the first bar. This happens to me about 80% of the time. This happens whether I'm using a soundfont or an AU. Turning off the "Count-In" allows me to capture all of the recorded track, including the first measure/bar. It appears that something with the "Count-In" option is keeping the first bar of midi from recording. I hope that makes sense! :smile:

  • @dwrae said:
    No, no sidechain atm.

    atm = "At the moment"

    I hate "No" but love it when it's followed by "At the Moment" from the developer (not from some Product/User-base Management flunky). They always think it's a trivial request. The developer knows what's involved.

    I'm curious (while we wait)... does a "side-chain" imply routing another track on a bus into an FX function to modulate the FX function which might be applied to yet another track? I know it's used to allow drums to PUMP through a mix without other tracks being heard on the louder drum notes. But how it get "plumbed" is still a puzzle to me.

    I can wait or go back to Cubasis or AUM or Auria or maybe buy BM2 or 3 and learn how to make it work. Which DAW does sidechaining best today?

  • edited September 2018

    FAC Envolver basically offers sidechaining in almost any host and much more. Is AEMS able to midi control/learn AU parameters? That is needed for Envolver.

  • @Audiojunkie said:
    @dwrae I believe I've found a bug in "Count-In" when recording midi. When Count In is active (1bar or 2bars, it doesn't matter), the midi track that is being recorded doesn't record the first bar. This happens to me about 80% of the time. This happens whether I'm using a soundfont or an AU. Turning off the "Count-In" allows me to capture all of the recorded track, including the first measure/bar. It appears that something with the "Count-In" option is keeping the first bar of midi from recording. I hope that makes sense! :smile:

    I think it's related to the problem that Matt_Fletcher_2000 is experiencing, although I did try today several times. I'll try again, thanks.

  • @McDtracy said:

    @dwrae said:
    No, no sidechain atm.

    atm = "At the moment"

    I hate "No" but love it when it's followed by "At the Moment" from the developer (not from some Product/User-base Management flunky). They always think it's a trivial request. The developer knows what's involved.

    I'm curious (while we wait)... does a "side-chain" imply routing another track on a bus into an FX function to modulate the FX function which might be applied to yet another track? I know it's used to allow drums to PUMP through a mix without other tracks being heard on the louder drum notes. But how it get "plumbed" is still a puzzle to me.

    The audio system inside AEM can do it, there is just no user interface for it. With a side chain, the audio from any other point in the audio 'graph' is used as input to control the (in this case) behavior of the compressor. It's like an fx send although the audio does not get 'through' on the other track/effect, it's only used for analysis.

  • @Janosax said:
    FAC Envolver basically offers sidechaining in almost any host and much more. Is AEMS able to midi control/learn AU parameters? That is needed for Envolver.

    Pumphouse by Audio Damage seems like a good stand in. It has a step sequencer built in which will cover most of my requirements without sidechain. It’s only £2.99

    It does offer sidechain to control it as well but the host needs to support some sort of au routing. No idea how this works but might be worth looking into @dwrae

  • The user and all related content has been deleted.
  • I will test side chaining with the Woodman Compressor app tonight to see if it is possible.

  • @gusgranite said:
    I e chaining with the Woodman Compressor app tonight to see if it is possible.

    Great. Now i’m Curious how Pumphouse pulls it off. $3 and I think there’s a video explaining how to set it up.

  • How do you zoom tracks heights individually like on AppStore screenshot?

  • @Janosax said:
    How do you zoom tracks heights individually like on AppStore screenshot?

    Ooh! Good question! I never thought it was possible! Also, this is a perfect example of why the white lines that show the selected track need to be more bold--You can't tell which track is selected in this picture. I'll be watching for the response to this. It will be nice to know how to zoom track heights individually. :smile:

  • @Audiojunkie said:
    @dwrae I believe I've found a bug in "Count-In" when recording midi. When Count In is active (1bar or 2bars, it doesn't matter), the midi track that is being recorded doesn't record the first bar. This happens to me about 80% of the time. This happens whether I'm using a soundfont or an AU. Turning off the "Count-In" allows me to capture all of the recorded track, including the first measure/bar. It appears that something with the "Count-In" option is keeping the first bar of midi from recording. I hope that makes sense! :smile:

    I think it's related to the problem that > @Janosax said:

    How do you zoom tracks heights individually like on AppStore screenshot?

    You cannot. The project displayed originally comes from the Windows version I used to have where individual zooming was possible.

Sign In or Register to comment.