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
One easy way is to add Drambo as an fx node in AUM on your channel where you have the IAA app on top, then just add a recorder or flexi sampler inside Drambo and tap Rec.
Thank you bleep!
Speaking of the Recorder module
I have the issue that the recorder module doesn’t save the recordings in drambo standalone mode.
Happens both when i save on Icloud and internal.
Yes “save with samples” is on.
This happens on an iphone 12 pro max. I have not tested on ipad yet.
Anybody else having this issue?
If I'm not totally mistaken the recorder module was/is purely intended for making temporary recordings.
You can drag the recording to any of the other samplers and it will get saved with the project.
Aha. A bit wired but that explains it 😊. Thanks
If no Aum involved (Drambo standalone mode) the only way of recording and using an audio file from an Iap is Audioshare? I kinda prefere to use Drambo in Stand alone mode.
An easy hack is a small USB audio interface as an audio loopback device. Unfortunately, iOS does not support internal audio routing because it's not built for musicians in the first place.
More and more modern USB audio interfaces feature internal digital loopback btw.
Indeed...
...but many interfaces lack a dedicated app for iOS to enable it and control or control the level of loopback.
I've got two interfaces which both support hardware loopback (Steinberg UR-242 and Audient ID4mk2).
When using the UR-242 on the iPad the loopback is 'disabled' in the dspMixFX app and can not be enabled.
For the iD4mk2 I can select inputs 3&4 (which are used for loopback) but since there's no app for iOS to control the loopback level (it's set to 0 on power on to avoid potential feedback issues) it's a no-go for now...
The only hope we have left is a 3rd party Audio Driver for iOS/iPadOS using DriverKit that will allow internal loopback without the need for an external audio interface...(The question is will Apple ever let it enter the AppStore since they have their stupid media licensing deals with media companies).
I see…thanks guys and Audioshare for now
For those interested I just submitted a request to Audient for the ID.app for iOS devices...
This would allow us to control the loopback volume making it possible to record the audio the iPad produces using inputs 3 & 4 which can already be selected in any audio-recording software that supports input channel selection...
I have no super high hopes for this app to appear but if it does it will be a blast!
Cheers!
Is anyone using Syntronik with Drambo ? If so , what would be the best way to midi control it ?
I don't find a way to assign cc controller to the parameter's in syntronik .. midi learn doesn't pick anything .
Tx
edit : found the solution / i didn't had the module midi output ( set to omni for syntronik to work ) after the cc gen
Any chance to remove audio feedback latency (10ms is a minimum setting), maybe there is a workaround? Thx
No there isn’t though you can align tracks to compensate for latency.
What are you trying to achieve?
Is it just me or does Drambo not like cc 64 from controllers to be assigned with midi learn? I tried it with my nk2 and lpx and it won’t respond to 64 but will midi learn it. Is that cos it’s used for sustain usually?
Tell me, how do I write to Drambo technical support? Inform that on 16.3 (ipad) the logo opens in the wrong place (not in the center, but on the left). And then it doesn't work through support.
The misplaced launch screen is caused by an iPadOS bug and affects many, many apps.
I had hopes it would be fixed with iPadOS16.3 but I guess we'll have to wait for 16.3.x or 16.4.
Same visual 'bug' is also present when opening AUM and a bunch of other apps, thankfully it doesn't affect functionality.
Fastest way to reach Drambo dev is thru the BeepStreet forum.
http://forum.beepstreet.com
Cheers!
I thought it was a feature! lol
Thought it was kinda neat how the logo slings down to the lower left corner right before it opens.
Don’t fix! 🙂
?
Works here. MIDI learn detects CC64 on the knob and the knob reacts on CC value changes.
Thank you, We will wait, maybe they will fix it.
The main thing is that the functionality is not affected-the right idea.
Somehow gone from super stable app to frightening one. Got 2 crashes today one while working with notes in piano roll, other with some au’s.. nothing was saved, autosave doesn’t restore shit. Never had issues with those au’s previously. I also feel that “overwriting” save doesn’t save correctly when followed by crash but cannot confirm. Also very buggy undo - can undo one note or the whole loop, and there is no redo. Afraid to touch that now. Autosave and redo highly needed..
I believe this is related to your screen size, because it's normal on my 9.7" iPad 6 with iPadOS 16.3.
Could you please be a bit more specific about the crashes? Ideally on https://forum.beepstreet.com/categories/known-issues
Quite likely. I have 12.9. But I think it's because of the stage manager. When you turn it on, the problem disappears.
I have also had a couple of chrashes pr session. I have not reported them because the have been very sudden and thus i have not been able to figure out how to recreate them.
But they usually occur when doing some sort of editing pianoroll, automation or in the step sequencer.
I’ll try to do some sort of report on beepstreet forum. But again it might be hard to recreate
All reports are helpful, even the crashlogs for the 'random' crashes.
It always helps to know if any AUv3's are involved as some crash more easily than others.
Device type and iOS version is equally important as some crashes only happen on some devices and some iOS versions which makes trouble shooting a pita. (As an example 'memory leak' related crashes happen faster on devices with less RAM).
Another factor that may be important is to know if the transport/playback was running while the crash happened?
I'm quite sure once the cause is know a fix will come
Cheers!
Thanks.
.
If anyone else experiences crashes, be sure to send the crash report to
Please try to describe what you did right before the crash, a few hints can already be very helpful.
Thanks @Samu and @rs2000
I have been looking around trying to find the chrash log.
But i can’t find it. Any hints?
Go to Settings -> Privacy & Security
Then Analytics & Improvements
Then Analytics Data
(This is for iPadOS16.3)
Scroll down to until you find something with Drambo select the file and tap the share icon top right.
You can mail it directly from the share sheet or save it to a folder in files.app, archive the folder and then send it.
I usually leave the "Share With App Developers" enabled, this way when their app crashes the crashlog should be sent to the developer automagically.
You can also zip the crash-log and post it at the beep street forum.
Good Luck!