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
@DaveB , I really miss an option to sync the Delay to the host -tempo; you could make the 'power'-button for the Delay also a threeway-switch (like Drive now has): Off-Synced-Timed.
When Ambience is bypassed, the Ambience-knob is still working (with no effect); I'd prefer that knob also disabled (and grayed out fi.) then.
What does "Enable sorting" in Settings do? I thought: sorting the presets by name, but that's not working...
@Harro when I hit enable sorting, I can long press on a preset and drag it to the top of the list. Try that.
The reason to disable ambience when bypassed is because loading the usual third party mono IR sounds strange when the ambience knob was meant to work as a mid-side implementation with the preloaded stereo IRs. But I guess you’re just talking about the visual aspect of it being greyed out?
Sync to host is a good idea of course, but if implemented it should apply to the chorus, tremolo, and phaser as well, not just the delay.
Aha, thank you. I would never have discovered that.... The problem is though that every long press on a preset also activates (loads) that preset! That should not happen while sorting!! @DaveB
I meant ‘disable the bypass-knob’ so you can’t change the Ambience value while bypass is active. For several reasons: it changes the preset (that has bypass in it) : you get a * after the presetname after turning the Ambience-knob, which is confusing. It can also be confusing when you forgot that for a preset the bypass was on and the ambience-knob has no effect.
You’re right that sync to host would also be nice for the other ‘timed’ FX...
Yes it’s better to have the ambience knob greyed out when bypass cab engaged for the reasons you mentioned. I also found myself moving it in bypass and wishing it went back to where the previous preset had it set. So taking its movement out of the equation is a good idea.
However if someone wanted to save a preset with bypass for later use with their own IR, it does make sense for the aesterisk to show up, since you’d be theoretically saving is as a new preset. It’s only the original preset if you revert back to the exact same cab choice.
@DaveB a few quick observations for now:
Deep Chorus HB preset has the Fuzz on, but Deep Chorus SC preset has it off. Discrepancy?
Silent tuner default On is fine, but if I turn it off it doesn’t state save standalone nor in AUM. When I open the app again Silent tuner goes back to on. Maybe not worth fixing, kind of a non issue.
Every time I load the app the first message quickly flashes “Tuner off”. Seems unnecessary.
if I’m on a preset and flip the kill feedback option, the screen flashes ABS out 1 and adds the aesterisk to the name, then turning it off flashes ABS out 0 but doesn’t get rid of the aesterisk even though it’s the unchanged preset. So if the intention is to save a new preset with kill feedback on, it doesn’t work. Because I tried to save a new preset with kill feedback on, cycled through others, and when I went back to the saved preset the kill feedback was off. So I think it’s a bug.
-just like the Silent tuner not state saving, the kill feedback and enable sorting also don’t. But those probably should revert back to off anyway. For those who like a non-silent tuner, we will always need the extra step of turning off the toggle every time we load the app.
I’m not a fan of any app that exits out to a website to show the manual. I understand a website is easier to update more frequently. But I see you have the ability for a text box by clicking on the heart and it is a nice message, but I would consider having the manual inside the app too. Your app is quirky enough where it would be nice to the reference and your explanation of the quirks, without exiting the app. I want to read stuff and try it right away. I get that the manual looks better on the website, but it’s worth considering a manual or quick guide inside that explains the knob quirks. You could always add a link to your company in there, or link it to the “db audioware” in upper left.
I feel like “db audioware could be a different color, perhaps same color as the arrrows, or at least different in some other. The faint color against the same sharper on of 20th anniv. seems slightly strange to me. Or if that’s your exact color and font for your company logo, maybe spruce up the 20th anniv into something else more festive, or whatever. perhaps a kind of gold or something sharper than the arrows but similar color.
The drive is much improved in terms of level to tone ratio, I hear it dissipating in a much more pleasant and realistic way. The fuzz however has that fizz in the background when the tone knob is up. You can hear it prominently and it’s what gives the impression of fizzy and digital. I also think that there’s too much overlap between the two drive modes. With some setting the override sounds more fuzzy than the fuzz. Also the level knob on the fuzz seems to be weaker output than with the overdrive, especially with the gain at noon or past. For the fuzz it would be great for the tone knob to go much woollier and bass prominent at minimum, at noon to be where it currently sounds like at minimum, and at max not to get so sharp and fizzy. Fuzz is goood, fizz is not.
I will get more in depth about the fuzz later to offer specific cases. But the point is I like the new implementation of the overdrive, but the fuzz needs to be more different from it, and less fizzy when cranked.
-Yes the ambience knob could be greyed out when cab is bypassed, or just consider freezing it when bypassed.
-trim knob works great.
-no access to manual link in AUv3. Another reason to consider quick manual on the inside.
More soon! Thanks for your hard work and attention to your product!
@DaveB
Straight out of the box.
Sounds really good.
It doesn’t take much tweaking to get a good sound.
I used an Ibanez Artcore AS73T-TCR-12-03.
Happy Anniversary.
I’ve sent you a message as well.
Hey @DaveB !! I deleted the app and reinstalled it, and then I was able to see the read only Factory preset bank, and also the additional presets you made featuring the fuzz. I really like those presets, they show off the fuzz much better than when I played with it hours earlier. I think you could dial down the fizz on the fuzz the same way you did with the drive. But overall I do think it’s wooly and bassy enough, just seems trickier to set it just right. So those fuzz presets were really helpful.
I know I bombarded your inbox earlier with bugs/suggestions, but I wanted to run a certain bug by the group to see if anyone else is experiencing this. The opening preset “signature” is acting weird. It state saves whatever you do to it, but in a buggy way. So I tuned on the chorus pedal in signature, exited the app. When I load it up again, the chorus pedal stays on, but when I go to turn off the chorus, the effect stays on even if it is turned “off”. It seems to be happening only with the chorus. The other pedals also state save, but I can turn them off just fine upon reloading the app. Isn’t your intention for the app to always open with the signature preset in its original form? Anyway it’s acting weird. Anyone else notice this?
Also, I screen captured a quick demo, just some noodling, to show some of the great sounding presets. Infinity Reverb, Deep Clean, and Brit Grit. I used my Motu M4, strat copy with the Mojotone ‘58 hot bridge pickup, and a Mogami gold cable. I’m an average player but I don’t skimp on the gear. So many good sounds in this app. Cheers!
@JoyceRoadStudios Thanks for that great little demo. The app is really coming along.
@DaveB: about 20thA and Midi (in AUM): I noticed - after connecting my FCB1010 (foot controller) directly into the app via AUMs 'hamburger' icon (on the left of the app-icon) - that there are all kinds of 'strange' midi-control-assignments hardcoded in 20thA ! Some buttons on the FCB1010 changed knobs like 'Tone' and 'speed' (directly from min to max) (obviously meant for pedals instead of knobs) and the FCB1010-pedals changed the Trim- en Treble-amounts(!). Because you can't change the midi-assignments in 20thA (as AU nor standalone), I suggest you should disable the 'hamburger'-midi-input-icon (make it invisible?) and let users only use the parameters via AUMs midicontrol: that works fine!
NB: there is no way (as far as I know) to adjust the midicontrol-assignments in 20thA standalone!
I’d like to clarify something important, which may not be obvious.
The Ambience dial is best used for listening through headphones.
The purpose of the stereo IRs is to deliver a realistic amp in a room feel through headphones - a sort of binaural simulation. Silent practice with headphones is far more entertaining and comfortable with the realistic ambience - you feel less like you have a box strapped onto your head.
However, there are times where you will want to turn ambience down, and use the mono cabinet simulation. In a busy mix, for example, ambience on every guitar track is likely to mess up your stereo image.
Also, if you're playing through nearfield monitors or an FRFR setup, the Ambience knob is mostly redundant. You're moving air in a real room - you probably don't need a virtual room simulation as well!
Of course, there are no rules in music - please use the Ambience knob as you wish. I just wanted to clarify my intent
The midi control assignments are listed in the manual. I’ve set my controller up to route via Nurack’s midi control changer. Now I’ve set it up I’d be gutted if that method of control was removed.
Also, are you able to ‘toggle’ pedals with AUM’s midi control? When I last looked it only offered knobs/faders, the only on/off toggle is to enable/disable the app. Am I missing something?
You can midi learn (or type in) the parameter-values (CC, Note or PC) in AUM after you have assigned your controler to AUMs 'general' Midi Control (f.e. via the midi-matrix). And yes, depending on the parameter-function (f.e. On/Off), you can 'toggle', etc.
And about midi in standalone: it's in the manual indeed, but you can't expect from users reprogramming their controlers just for this app. A midi-control changer is a solution for that, but not ideal (though I can live with that).
So... I use midi control in AUM a fair amount, but I assumed the toggle or knob thing was a limitation of the implementation. I can midi learn to, for example Drive, but it’s not an on/off toggle control in AUM, it’s 0-100% - is there a way to change this?
Both methods (hard-coded CC values as per the manual, and host control via AUv3 params) will remain. Some hosts may not offer AUv3 parameter automation, so hard-coded CC values are a good backup.
(Note that the individual hard-coded CC values may change during the beta phase, as I add or remove params)
I can toggle pedals using buttons (transmitting CC data) on my Korg NanoKontrol, via AUM's parameter control.
You don't have to change that 'range: 0-100%' in AUM when your controler sends 127 (100%) for toggle ON and 0 (0%) for toggle OFF: that way the Drive-param for 20thA goes ON and Off... (it works for me).
What are you planning on sending to the drive on/off control?
Awesome update! I think it’s ready to release. I’m just going to call it “20”. 20thanniversary to me sounds like a marriage app. But t it is definitely my go-to for guitars from now on. Thank you so much for putting this out there for us!!!
Yes, there's also 'something else strange' with "Signature" in AUM: after reloading a AUM-session with 20thA in it, there's NO presetname showing in 20thA (it's label is empty - regardless what preset was saved before), but after changing a knob "Signature *" appears.... I know there are many apps that don't select (show) a previously saved preset after reloading, so this may be an IOS-thing. "Unknown" might be a better name to appear then?
CC toggle, or momentary. My issue is I can toggle pedals on/off using the apps midi control, but as far as I can see you can’t do that with AUMs midi control, which is for a pot or encoder. Is that possible?
Thank you, this goes for other apps too, like iFX rack I think, the parameter is exposed, but you can’t change the control type. This has been the advantage for me of stacking Nembrinis where each one has a toggle on/off, or Th-u where you can learn it internally. Don’t get me wrong though, I’m happy with 20thA’s control, I just can’t see how you replicate it with AUM’s midi control.
You could set up a simple streambyter or mozaic script to convert things to toggles. I wonder if someone has already posted that.
I appreciate your help in looking for a solution, but I’m mainly just trying to point out that you can’t achieve with AUM midi control the same thing you can with the built-in app midi control, i.e. toggle the pedals on and off with midi cc from a foot switch. If I’m wrong all well and good. Am I wrong?
I must not be managing to be very clear, good job I didn’t get into posting on the vaccination thread
I’m toggling pedals using CC buttons on a Korg NanoKontrol, via AUM midi. Works absolutely fine.
But I’m not a black belt in AUM routing. Am I missing something?
I’ll go home and do some more homework before I confuse things any further...
I think that he is hoping that sending a value of 127 (for instance) will act as a toggle. I.e. press a momentary button (such as a sustain pedal) to turn it on then press again to turn it off.
If you can turn the pedals (effects) on/off with MIDI CC from a foot switch, that switch is sending CC values of 0 for off and 127 for on. Those same inputs will work with 20thA in AUM. The distinction between a 0–>1 value and an Off/On value are managed between AUM and the app; they don't really concern us. And the 3-level Drive control takes 0, 63, 127.
That's assuming you're not looking for a true "toggle" effect, as suggested by @espiegel123 , where successive sends of the same CC value alternately trigger On and Off. I've not seen many apps that work like that.
The buttons on my controller send Note On on press, Note Off on release, not very convenient. I use a StreamByter script in Audiobus to convert the Note Offs to CC values alternating 0 and 127, which work fine. But that's only needed because of the odd functionality of the controller.
I’ve been having a great bit of fun playing with 20th anniv. for the past few weeks, it sounds good right out of the box. But over the last few days I seem to be having my first brush with tendinitis in my fretting hand. Is this a bug? It could be the washing machine I was angling upward with one hand while fixing the other day, or the other guitar apps I’ve been playing regularly, but I will be taking a couple days off. Keep on rockin’ this beta y’all!
Thanks everyone. I wasn’t hoping for anything, I just thought that for toggle CCs there was a difference in how AUM midi control worked and how the app midi worked and that the latter should not be discarded, as suggested in the earlier post, in favour of the former.
However, I’ve now checked with my controller and it does toggle the pedals in 20thA using AUM Midi control correctly (with a toggle on/off alternate message). So I was mistaken and happy to be so.
Just wanted to say thanks to everyone for the great feedback.
I'm currently shaking off minor side-effects from my first dose of AstraZeneca vaccine. Once I'm back to "coding fitness" I'll take a few days to digest the comments on 1.0.6, and build a 1.0.7 release - hopefully the release candidate!
Hope you all have a nice weekend