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.
Loopy Pro Questions
This discussion has been closed.
Comments
OK that’s great - thanks again. I have sent over my last two crash reports. It looks like a mass of gobbledygook to me but hopefully it will be of help.
Any more problems/ crashes etc I’ll record them an pass them along 🚕 👍
Fader widget - great to send midi to control external instrument, or host like Drambo (from loopy pro auv3).
But why fader get value “zero” during load project in Drambo, or standalone, even if I assign it “change value” to “send midi message”?
But if I assign it also to “change donut parameter volume”, then fader remember it’s value.
Can I have fader only assigned to send midi message and have memorised it’s value during load project?
If no then I will create some “dummy donuts” only for faders, but better to ask.
My guess is that if a fader widget is set to get its value via midi and isn't tied to something with a stable value, it gets reinitialized when the project opens since it is a conduit for incoming. I don't know if it is intentional or a bug that it doesn't remember the last value it was set to.
@Michael ?
That definitely seems like a bug to me. Fader value/position should be saved with the session no matter what IMO.
I am not 100% sure that. Faders in Loopy Pro are, I think, designed to be tied to something that has a persistent value and gets its value from the thing it is tied to (whether that is a clip parameter or effect parameter or whatever. When they are only to send midi messages, the fader isn't connected to anything it can get a value from.
If faders not connected to any parameter were to have persistent values, I guess they would need to send out that value when the project loads if the fader is set to send MIDI on value change.
Ok I made simple project with 8 faders attached value to 8 dummy (silent) donuts - Loopy pro under Drambo as midi plugin.
Another instance of loopypro is as audio effect plugin, which is controlled by launchpad.
And then conflict: launchpad is simultaneously operating on both instances.
If I disable in midi instance of loopy pro, launchpad is also disabled in audio effect instance of loopy pro.
If I enable launchpad automap In audio effect , then you know, in midi instance loopy pro is also enabled.
I would like to control which instance is controlled by launchpad and which not.
Why I use two instances? Because I like to have separate controller window (with mentioned 8 faders) constantly visible, where on audio effect instance of loopy pro Imoperate on donuts with audio loops, and switch pages!
I know , on road map somebody asked for pernament widgets (visible on each subpage), but at now it is not ready….
Hmmmm…. Maybe I will just copy all faders to all pages in audio instance and it will workaround.
But at least I signalise the “problem”.
IMO LoopyPro is so sweet and great, and in terms of MIDI, it’s ability to see all core midi ports under auv3 is brilliant!❤️
That seems like a bug that the Launchpad is disabled in both AU instances if disabled for either.
@Michael ?
That makes sense internally, but not for a MIDI control, which generally (though not always) is one-way.
I understand that but think it's not a useful concept to apply to MIDI sending controls.
I wouldn't expect the control to send it's value on load any more than I would expect a hardware controller to send its knob values on connect, or a TouchOSC control surface to. No value change has occurred until the control is moved.
An option to do such a thing would be very useful though.
Two instances of LoopyPro under Drambo. If I enable binding to Launchpad in one, second also get this setting. Would be nice to have control which instance is under control of Launchpad and which is not (to operate only on screen for example).
https://youtu.be/X6B7wkV2A-U
@Michael : just in case you didn’t see the post above
Hello, I am wondering if loopy can behave like an echoplex pros insert/replace mode, where with a foot switch one could insert/replace portions of one loop?
No. But I think it is on a list of future enhancements.
Is it possible to convert a loopypro recording to AIF or WAV or MP3 and move it onto a windows machine?
How do i export a recording from LoopyPro for use on a Windows machine?
Do you mean a recording of a session or export a loop?
When you do a session recording, the audio is recorded into a folder in your Loopy Pro folder.
There are a number of way to export loops. In the track overview windows , there is an export icon. In the project manager window, there is an export button that will export all loops or the project. In edit mode, select items whose audio you want to export, a menu pops up from which you can choose export. Audio is exported as wav.
If you session record, the recording will be wav or an aac file, depending on whether you choose the lossless option or not.
From where @espiegel123 left off, to get it to another format and over to a Windows machine, one convenient option is AudioShare. It can export to Dropbox, or just use the internal FTP server and point your Windows browser to it. You can't convert to MP3, but it does have AIF.
There are other ways to get the files over to a Windows machine, but they are be more involved. Setting up a Windows share and connecting to it from the Files app, or copying to a USB drive that isn't NTFS formatted (the Windows formatting default), etc...
How do you set it up to record donuts into the sequencer right from the start? I’m recording in AUM with host sync disabled. Whether or not I start with the donuts off/blank or play/lit the sequencer never records the first loop - it does start to record when I tap on them….. but it’s too late by then 😛
When you arm a recording in the sequence room, there is an immediate start option.
Thank you @espiegel123 I can’t see how to arm a recording if there is an audio loop ready installed in a donut - the option won’t appear- if I tap on the timeline the wave appears there. I see that if you tap on the timeline of an empty donuts lane in the sequencer then you get the arm option. I am looking to record from the donuts to the sequencer.
Later - I have managed to get it going now the way I was trying earlier - strange things unpredictable things keep happening though.. it gives me the heebies. I think I’ll just place the items in future if I’m using the sequencer.
I see in the description that automation is mentioned - what does that apply to? Can the sequencer volume be automated?
Cheers
Not at this time.
Can you explain what you mean record from a loop to the sequencer?
The sequencer is DONUTS and one-shots. It basically automates triggering the playback and recording of clips. Each clip has a lane and the events in its lane correspond to playback of that clip. (You can also trim the event so that only part of the clip plays).
I was meaning the donuts as the round ones with the wav inside @espiegel123 - the loops that you can load in and play and have 8 along and six down or whatever you want.
By the sequencer I was meaning the timeline like you get in Cubasis.
I was having trouble getting the sequencer to record to the timeline and not leave a gap at the start - I think I’ve got it now…. I’ve fiddling with it so long I’m not even sure what I was doing wrong now in the first place. The only thing now is that for some reason it will simply stop recording for no apparent reason even though the loops/donuts are at it and the timeline marker is still moving. I was just curious and a little frustrated. As I say I will probably find it a lot easier just to place them on.
Many thanks 😀
What can this be referring to from the AppStore description?
If you post your settings and a video, I can probably figure it out for you. I am not sure if you are running into a bug or if there is something set up that is working as designed but might not be obvious.
That is referring to automating the playback of clips (loops and one-shots). Not automation of volume, etc.
The timeline sequencer is just a way of arranging loops to play back in order on a timeline. It isn't exactly the same thing as, say, the timeline in Cubasis. You sort of need to throw out your preconceptions from other DAWs.
In DAWs like Cubasis, lanes are instruments and you can record and place clips related to those instruments. In Loopy Pro, lanes represent clips (donuts) or one-shots, and you can only place instances of that one clip on each lane. You can't place one riff followed by a different riff in a lane. You can't set up to record a new riff in that lane either, unless you're overdubbing the one that's already there.
I hope that makes sense.
Got you @wim - thank you.
It’s quite an irregular thing @espiegel123 I’ve been trying to replicate it, but as I was saying it seems to be working now, but it will happen again at some time.
Hold that I’ve just managed to get a screen recording of the sudden stopping of the recording - I don’t have a platform for publishing videos at the moment which you need to post here I believe. If you want to pm me your email address I’ll send it over for you to have a look. Please don’t bust a gut trying to work it out on my account - as I mentioned if I’m going to use it now I’ll just be placing it on. But I’ll happily send you it if you want to have a curious look at it 😃
@robosardine - my guess is you were recording into a clip that had a fixed number of bars set. Even though you're recording "into the timeline," what you're really doing is recording into a loop (clip). Clips have properties and one of those can be clip length. If somehow you set a clip length, that would do it. Clips don't expand if you have a number of bars set.
I have tried to keep my tinkering with the settings to a minimum @wim
Here are the settings I had - which are mostly pretty well standard I think.
@robosardine : in those photos , you have retrospective recording on. That will limit your clip recording to the length of the master cycle.
Are you creating the clips you are recording into on the fly or by dragging blank clips out ahead of time?
A video would help.
I sent you a video after you sent me your email address. Should I resend it or was it not what you were looking for.
Here is what I was doing.
I was creating loops in the donuts by placing Loopy Pro in the effect slot - placing Groovebox in the instrument slot. Record loops retrospectively into the donuts when I hear a bit I like.
When I have several ‘loaded’ donuts I was then trying to play them live and record them into the timeline sequencer with the settings shown above by pressing ‘start recording’
Later - I have made a screen recording to show this. I will get a YouTube account and post it when it’s set up. (It’s about time I had one anyway - no point in waiting until I complete a masterpiece to release to the world) Things a bit awry at the moment due to death of our Queen.
It seems to be taking a long time to upload…… mm.. save draft again 😀
It’s there now - and here’s the link
Hey! I’m on YouTube!