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
Solid! I knew you'd be all over this. Well done. Glad the built-in synth does proper kicks.
I just want to report to Jim a small nuisance, but his email won’t show up on the FB page on my phone, and I’m away from my tablet until late tonight. Anyone got it on hand? Still happens after first update, but it appears I'm also the only one who has mentioned this.
In case you’re wondering, when transport is stopped with an active clip, the first note won’t play when you play the transport again. It’s not until the clip comes back around that the note is heard.
I verified that the note “on” actually starts on the beginning of the beat, and not towards the end of the clip.
Only happens when you stop transport and start again. If transport is already playing and you launch the clip, the note on event will play first time, as expected.
jimaudiodsp at gmail.com
any tips for how to change the probability of a chord collectively rather than each individual note?
I'll go one further and say that I think initial reactions are important and should be encouraged.
Hearing honest criticism makes some people feel very uncomfortable, but how an app is received on first impression is arguably more important marketing data than any other. Follow up reactions are important too. The more detailed the better. It's true that rude or entitled attitudes ruin such feedback but that's just the world we live in these days.
Of course, that's less useful if the developer doesn't see the feedback. It's still useful for people looking into the app to see if it's for them though.
I did some quick tests and having an AUv3 in a project doesn't stop you from using the pattern crossfader. But I imagine it will be limited to how heavy each project is as you are effectively loading 2 of them simultaneously. I'll plan to keep my use of AUv3s quite light if I want to blend between projects with the crossfader
The first fix release is out. I see some of the issues noted earlier in the thread have been addressed. One I had reported to Jim by email and got an almost immediate response. So, email is an effective way to report bugs.
As there’s no manual yet, can I ask:
I am using Drambo on pad one. I have set 8 pads in drambo as my drum kit. It’s great as I can process each drum element separately using drambos processors, really nice.
When I go back to the sounds page in GR2, I see under the drambo icon there are 9 greyed out knobs. Can I assign them to control elements inside drambo, like the reverb mix on a snare, etc. I’ve messed about but can’t find a way… any help would be great..
All the best
No, with Drambo you can't use those knobs. Those control AUv3 parameters, and Drambo doesn't expose any.
Ok, that makes sense. Thanks for getting back to me 👍
+1
I believe it's helpful for people to have a place to exchange reactions, thoughts, and opinions on apps, whether it's day 1 or later on. Different people will have a different take on the app, what they like, don't like, and wish for. When the intention and the goal is to be informative and respectful, it's fine with me. Negative comments which simply describe the persons feelings about the app without some meat to back it up are just not very interesting or helpful.
It seems like it fully loads the AUs in the background for the next project before it is started. I've tried with multiple AUs without issue. A great feature. I don't know of any other apps that do this.
Seems like if you use the select (dotted square) in the piano roll, and enclose all the notes in the selection area, they can be modified together - works for me. I'm using version 1.0.4.
Loopy Pro may be doing something like that as I think it does manage smooth transitions between projects. I haven't personally verified that it always works smoothly with AUv3's loaded though.
The only think I imagine is using something like tonality to trigger the chords and put a probability on the corresponding note... os sampling the chords...
this is the explanation from the GR-16 manual:
Trigger condition types and their descriptions:
--- means that no trigger condition is assigned to the current step; A note will be played normally, every
time it is triggered by a sequencer.
XX% percentage value indicates, that a probability of playback is assigned to the current step. A note will
be triggered randomly, with a given probability, from 1% (very rare) to 99% (very often).
Prev this value indicates, that current step will be triggered in accordance with the most recent evaluated
step condition in the current Part. It copies the condition of the previous step in the Part. Use it to group
several notes, that intended to be played using exactly the same trigger condition, which precedes them.
!Prev the same as “Prev”, but uses the opposite (inverted) value of the most recent evaluated step condition
in the current Part. A note will be played, if the previous step condition was not triggered, and vice versa.
NPar this value indicates, that current step will be triggered in accordance with the most recent evaluated
step condition in the Neighboring Part. Neighboring Part is the part with previous index number. This value is
mostly used if you need to interconnect several conditional notes, which belong to different (neighboring)
Parts.
!NPar the same as “NPar”, but uses the opposite (inverted) value of the most recent evaluated step condition
in the Neighboring Part. A note will be played, if the previous step condition on the Neighboring Part was not,
and vice versa.
1st means, that current step will be triggered only once, during the first playback cycle of the Pattern.
!1st the same, as “1st", but inverted. I.e. current step will be triggered every time, except during the first
playback cycle of the pattern.
Fill this value indicates, that current step will be triggered only when the Fill mode is activated. To activate
the Fill mode, just hold down the SHIFT button during pattern playback. A Fill mode is deactivated when you
release the SHIFT button.
!Fill the opposite of previous condition: current step will be triggered when Fill mode is not activated, and
will be silent while Fill mode is active.
A:B this type of trigger condition is used, when you want a note to be triggered once during the given
number of pattern playback cycles. Examples:
1:4 a note will be triggered during the 1st playback cycle of each 4 repeating cycles (during 1st, then
during 5th, then 9th and so on);
2:3 a note will be triggered during the 2nd playback cycle of each 3 repeating cycles (during 2nd, then
during the 5th, then 8th and so on);
1:2 a note will be triggered during each first playback cycle of a given two repeating cycles;
2:2 a note will be triggered during each second playback cycle of a given two repeating cycles;
4:4 a note will be triggered during each fourth playback cycle (4th, 8th, 12th, 16th and so on).
!A:B the opposite of “A:B”. Condition value is inverted. It means, a note should be triggered every time,
except for those cases, that match the “A:B” condition described above. Examples:
!1:4 a note will NOT be triggered during the 1st playback cycle of each 4 repeating cycles, but will play
normally within the rest 3 playback cycles;
!2:3 a note will NOT be triggered during the 2nd playback cycle of each 3 repeating cycles (during 2nd,
then during the 5th, then 8th and so on);
!1:2 a note will NOT be triggered during each first playback cycle of a given two repeating cycles;
!2:2 a note will NOT be triggered during each second playback cycle of a given two repeating cycles;
!4:4 a note will NOT be triggered during each fourth playback cycle (4th, 8th, 12th, 16th and so on).
you could use the mod wheel to have at least one parameter maybe?
I think I'd just select the chord notes and move the probability slider. A little tedious but should work.
@wim @EdZAB thanks - I did try this in latest build, using the select tool to select all chord notes and slide the probability does give each note the same % modifier, but unfortunately they're not treated as a unit for playback. so for a triad on any cycle 0-3 of the notes might sound....
@cokomairena thanks, yes I will probably resort to sampling chords for the time being to achieve this
it truly is better than i imagined. I expected it to work for native GR2 elements but not for AUv3s. it really offers a world of new possibilities
due to the iOS 16 sample load bug (now fixed) I only really started my explorations of GR2 today and I am very impressed
I hope there's some more development with regard to MIDI flow, so we can map midi AUv3 LFOs/modulators to synth/fx AUv3 and native parameters. But I am very happy with living with the limitations it thoughtfully provides. I always have Drambo for the rest
Is there a way tò select a part without trigger It or use the arrows left and right? I found only an other way from the mixer. Could be useful use "shift" + part for select a part without trigger It.
And ....p-lock...
I Hope also in other ideas in order tò insert step in step mode, isn t so fluid
Sadly, no.
😵💫😵💫
another thing I don't understand is this workflow of having to access the clip menu, hold down and tell it to edit in order to modify it. couldn't it do it automatically, like drambo? if the clip has not been created it creates it automatically, if it has already been created, it modifies the clip of the selected part.
certain things seem so little sense to me that without the manual in hand I wonder if I'm missing something.
it sounds really good and I think it has one of the best time stretching on ios but in terms of workflow there are many doubts
And i don t under stand how make automation 😅
you have direct selection on the clip screen, the song screen and the mixing screen, on gr-16 you could hold the part button and select any part without triggering, the same with all selectors, keys + a pad would send you to that part directly without triggering it-
also mute+ a pad would solo it, I think these might become available on time.
For now I'm liking Koala much better than the native drum rack.
I had a crash with koala and solved it just like I do on BM3: delete the part and undo, worked like acharm
send a mail to jim!
I'm having so much fun playing recording and automating the master fx 🔥🔥🔥🔥
Yes, true, but if I'm editing synth parts I find it an extra step to have to change the page to directly select a part and then return to the "sound" pages, or having to click the arrows several times to get to the desired track.
small things, but as they slow down the workflow, I find them not very intuitive.
hopefully that will change in the future.
..
double-tap on a clip opens the editor. A little easier, I guess.
That workflow is not so bad once you get used to it, but really seems like a kludge at first.
If your experience is like mine then you certainly are. I think I have most of those uncovered at this point, but you never know what you don't know eh?
(btw, I wonder how many people have noticed the microscopic little
>that is next to invisible on the default dark keyboard. It displays pitch and mod wheels and another tiny little hamburger menu for setting keyboard size and scale lock mode. Man, that is some clever hiding of important details right there.)Move a knob while recording to make a the parameter show up. Then you can edit and draw what you like.
Cubasis pioneered that design gem. I never did like it.
Wow. Lotta sarcasm right now from me. It's good natured on my part, though I'm sure it doesn't come off that way. I'm far more pleased with GR-2 than I expected to be now that I've spent enough time with it.
I think GR-II is brilliant. Not so complex that it’s overwhelming, very nice workflow once you’ve used it for a bit and a really excellent feature set. And above all it’s fun to use!
Yeah it has a few glitches and there are features and workflow optimizations that would be nice but out of the gate this is pretty damned impressive. Bravo Jim Audio!
I have a project that crashed and can no longer be opened. I remember the crash happened when I was using SKIIID (an au instrument)
I just discovered this by accident. The dialog window popped up when i touched Midi Learn in Settings. Woot-woot!
Maybe this has already been mentioned in one of Doug‘s videos or perhaps Leo’s, dunno, i haven’t watched all them yet, but i didn’t recall seeing it here, so I figured I’d share.
anyone have experience with the microtuning possibilities yet?
i can't find out how to (negatively/in a downward way) adjust the master tuning (scale tuning in GR2?)