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 StoreLoopy Pro is your all-in-one musical toolkit. Try it for free today.
Comments
@j2snell
I'm not sure if it's intended to be used as IAA-no mention in description/manual.
It loads fine in AUM. Reveals its midi in port, but not the out, hence the confusion on the first try. Those AB3 restrictions could be ignored when used as IAA, so midi settings remain visible, or by revealing its global midi out port, so channel separation can be managed in host, without confusion where those notes coming from.
For now as it remembers those settings made in standalone mode its sending midi to AUM fine and I can send notes to it from AUMs keyboard or Rozeta, so all good
Thanks
A question I have been pondering...@j2snell
If we are feeding Refractions constant midi in, does this mean the AI continues to change ?
If so - then when the midi is stopped - Refractions is just dealing with the last portion of midi notes it received?
So how much midi info (timewise - or note maximum) is being held in AI?
EG: Would a 5 minute section of midi input that has been fed into the app be held and affecting the AI / Refractions melodic output?
Trying to get my head around how much note info the app holds in AI - and how midi input is dealt with
@recccp
I haven't delved into IAA, so no implementation there, only Audiobus.
Ah I see... Yes I've been using RF to send MIDI out Network Session. I have a virtual MIDI destination, but not a virtual MIDI source. I'll add that next update. Thanks for finding that.
@Mayo
Yes, the incoming MIDI imprints the AI memory the same way screen inputs do. Playing keys on the keyboard or drum pads on a MIDI drum controller would be the same as touching the screen. My goal was to allow users not to have to use the screen to input notes.
It takes all the notes that were input, whether from MIDI or touch screen. When regenerating notes, RF favors notes that were adding during the most current session (since the app was launched) but also takes into account notes input in all session (since it was first installed or since the AI memory was reset)
No max is programmed into it. It continue to record the incoming info of track, note, etc...
Sure - but that would not set Refraktions to play in a 5-minute loop. The loop time is set per track in Pattern length. Currently the max loop time is 8 measures, but I'll be expanding that in the future.
@j2snell Your app is awesome. I have had it since it launched. I always wondered if the AI was per session or retained between sessions. Now I know!
Anyway, thanks for your hard work creating and updating this app. The latest update feels really significant and the app runs very smooth now with a lot of good control options. One of the best apps, for sure.
Thanks @CracklePot !
I love the sound of this app!
It always reminds me of the soundtrack for the video game Myst, which is fantastic. Especially the Gamelan synth.
thanks for the detailed info @j2snell.
The max loop time of 8 measures being increased would be a real bonus
Great addition of 3 finger swipe for tempo - now i am able to play without always changing tempo!!
>
May well be my error, but I’m finding that the volume control for individual midi out is not having any effect.
Would also be good if, when set, the name of the synth being used replaces the standard instrument.
Otherwise, update is working well, and edging Refractions ever higher as the best generative app. The interface reminds me of something from Bladerunner, and as a generative app it blows the socks off Intermorphics.
@Zen210507
Volume control has no effect on midi receiver/ext. instrument it isn't sending any CC messages. When used for internal sounds it works here as expected.
@j2snell
Since midi in is there, would you consider making some of the basic track/seq editing options accessible via midi CC (start/stop, scroll, clear notes per track, clear all notes), please.
@Zen210507
To clarify - when you tap the screen, all the MIDI note output at full velocity rather than matching the volume set in the Settings Panel?
So, for example, if I set Track 1's MIDI destination to the Animoog (and not global) then:
1) "Animoog" would appear in the Settings Panel where it currently says "Track 1: Glass"
2) "Animoog" would appear in the lower left when the screen is tapped instead of "Track 1"
?
Thanks,
J
@recccp
Refraktions can hear certain system messages from an external sequencer, including Start, Stop, Position. Are those working for you? I just tested using Ableton (sending MIDI to Network Session 1, MIDI Clock Type: Song). In Refraktions, the "Sync to external MIDI clock" needs to be on to receive these messages.
What MIDI message clears all notes, or notes per track (channel?)
Thanks,
Jason
>
What I’m doing is trying to alter individual volume using the settings panel. This works fine with in-app sounds, but does not do much when controlling another synth. Another poster here says this is by design?
As for name settings, your examples are exactly what I have in mind.
Really enjoying this update.
@j2snell
Sorry, what I meant is to make gesture like e.g swipe to clear track midi learnable, user definable or even fix CC#, so it could be triggered from midi controller.
The idea would be that RF is running in the background as seq, I can enter/clear notes on the fly from a midi keyboard/controller, occasional scrubbing for variations, and stopping seq, when other seq's being used for more predictable stuff.
If this goes against your vision, please ignore me as I'm having a lot of fun with the app as it is.
Thanks
@Zen210507
Got it - I was registering touch inputs as maximum velocity, as compared to MIDI controller inputs as the velocity that comes in from the MIDI. But now that you point it out, it totally makes sense to have the touch input to MIDI be set by the volume setting that is used for the sample playback. Good idea.
Cool, I was thinking about that myself when using the app yesterday.
I'll put those in the queue. Thanks!
@recccp
Oh! That is interesting. I could envision a section of assignable control changes that the user sets. I'll think that over in terms of implementation....
Hi - just picked up Refraktions yesterday. Digging into it today - is the scales mode working correctly? I select A minor key (for example) and when playing notes on the screen I'm seeing G, G#, A# but Can't seem to play an A..? Liking the app though...
@tja
There's a demo video for 2.1.3 (the last version) on the new FB page for the app:
https://www.facebook.com/Refraktions/videos/2061087750842879/
I'll make the 2.2 version soon. I know it's definitely easier for me simply to see an app in action.
@Halftone
I did a test - I set the root key in Music Scales to A# and see both A and A# when I tap the screen. Do I have the same settings as you? Let me know and I'll investigate...
Just tied - set to Amin - if I start on left I see G2, then G#, A#,C2, D, D#, F. Shouldn't be seeing any sharps right? I'm using on iPhone and moving my finger up the scale as small increments I can - could that be it? I then tried changing to A# minor and see the same set of notes when I play.
Yes, I think the scales are a little wonky, seeing the same behaviour here.
@Halftone @TheVimFuego Ah I see what you're saying. Yeah I originally set each scale to C, then when I added the root key, I just shifted the start point of the pattern. Ironically I'm more a rhythm musician that a keyboardist, so I'm new to scales. What I was told my a keyboardist friend is that if a particular scale is like this:
Root key is C
Then a particular scale might be:
C, C+1, C+2, C+4, C+6, C+7 or something
You know, some notes are in the scale, some aren't, based on how many 'steps' it is away from the root key.
So then changing the root key, the pattern would stay the same (+1, +2, +4, +6, +7)
Is that correct? If not, I'm eager to learn how I can code the musical scales correctly.
Thanks,
Jason
@j2snell
Correct, the intervals (gaps between the notes) are what defines a scale.
Start at the root and work from that.
I’m primarily a guitarist so if it doesn’t go Kerannng I’m generally out of my comfort zone.
@TheVimFuego I did find this framework I can implement:
https://github.com/danielbreves/MusicTheory
That way I won't have to learn it all from scratch.
But given what you've said, I think the notes are right, but my labels are wrong. So I'll fix that next version.
@j2snell I have been switching scales and root notes and monitoring the note output from Refraktions, and I believe that the root note is not changing correctly. The modes I tried seem to be correct, but when I change root notes, the note sequence stays the same. I believe all the scales and modes are correct for C as the root, and when you change roots, the sequence still remains in C, which would seem incorrect from what is expected, but again is correct still for the root of C.
I think that when the Root Key slider in moved from C, it is starting the sequence on the new Key note correctly, but it is still starting the note spacing sequence from C. It needs to start the spacing sequence from the new Key note as well.
For example, if we look at this Major scale (+0, +2, +4, +5, +7, +9, +11) starting from C, we would get C, D, E, F, G, A, B. If we want to change Root Key to D and keep the same scale, we would get D, E, F#, G, A, B, C#.
But what I think is going on is Refraktions is starting on D as the Key note, but starts the spacing sequence at +2, giving us D, E, F, G, A, B, C (+2, +4, +5, +7, +9, +11, ++0). If you shift this so it starts on +0 you get (+0, +2, +3, +5, +7, +9, +10). This sequence is the Dorian mode for D, but we expect D Major. The D Dorian mode matches the scale for C Major, so we are getting the correct Key note of D, but we are stuck with the scale of C Major, giving us the D Dorian mode instead of D Major.
@j2snell - just curious, whatever happened to the rhythm based app mentioned earlier in this thread?
@CracklePot OK, I'll investigate to see if it is setting it. It sounds like the control in the Settings Panel is not changing the scale in the Sequencer...