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
I think it might be Synclavier as it crashed again when adding a bar to a sequence while the sequence was playing. I’ve sent in the crash files with a small explanation. I tried the same thing with synthmaster2 and it is solid in a good way.
My point of view: Repeatable crashes always have the highest priority, and the sooner they're reported the better. They need to be fixed anyway in the latest iOS versions.
I would only wait if you rely on your set in a live show and just can't afford crashes.
Thanks for sending the crash log!
@Mountain_Hamlet @rs2000 The memory issue is very real and to be accounted for.
For a long time I had a loading issue where my main sample heavy (123mb not thaaat heavy if you ask me) Drambo project would load empty in Loopy Pro. I’ve noticed that other very light instances of Drambo were loading correctly.
This lead me to believe it was memory problem so I trimmed down the main project by shortening samples etc. went from 130 to 55mb and voila, it all started to load correctly.
This is on Pro 11 4th gen with 4 or 6gb ram. I cannot imagine what it is like with Air 3.
Or maybe we’re talking about the Apple imposed AUV3 limit that is device independent? It would make sense. In which case, at least in my scenario, breaking up a big Drambo instance into two would most certainly help. I’d be more than happy to be corrected here though.
It looks like dRambo keys are broken in the new update and sending different information than dRambo pads. Specifically, “note off” sending 127 instead of zero. It’s confirmed by many people.
Actually, the AUv3 memory limit (about 300 MB?) applies to all instances of the AUV3 app loaded in the host. All instances share the same code, but have different data. The arbitrary memory limit applies to the total memory (code and data) used by the app. Thus, splitting up a big Drambo instance would not help. Annoying.
Let's just tag @giku_beepstreet and keep our fingers crossed for a quick fix
My comment in regards to the OS is that anyone who uses iDevices will encounter issues
as Apple always introduces new issues with each update however like @rs2000 has mentioned
we need users with the latest OS and repeatable crashes.
The faster we get those fixed the better.
100%
I've tried similar things and it does make a difference in stability.
Be very happy that you've got a Pro 11 4th gen.
My Air 3 does well within it's limits however I do need something with more grunt now.
This was brought up on the Beepstreet forum last night and Giku has been tagged.
Oh, BeepStreet forum is still alive, good to know! 👍😌
We've been having a discussion over on the Beepstreet Forum in regards
to online assistance for the modules and it occurred to me to try ChatGpt.
Here's the link to the thread
https://forum.beepstreet.com/discussion/2453/just-checking-drambo-documentation-is-still-a-bit-sparse-right#latest
Where we've discussed creating a dRambo wiki or a Github as suggested by @drez
@offbrands has kindly offered their time and effort in this regards.
Thank you @offbrands
ChatGpt came back with some very interesting results for the descriptions
which could very useful for rookie users and the replies are instant.
Here's an example
I’ve seen y’all at the beta team spill out multiple manuals worth of advice in a year alone. I personally feel like you could crush it in no time with the right structure and don’t need the bots help.
As long as the team is double checking the work I don’t mind the use of chatGPT for creating help materials. I think it’s sad though and it would suck if someone damaged their ears following incorrect AI help text. 😩
I don’t know Drambo like the back of my hand and I’m new to production, but I can help with a manual. Will maybe be in touch
Thank you.
By now we're all living manuals.
Agreed we can for sure.
Very cool.
Thank you for your offer.
Get in touch with @offbrands and @drez because they are going to start looking at creating a github for dRambo.
See above.
Awesome.
Once again thank you.
It is more complicated than that. The issue Supadom mentioned was not an issue where the plugin was crashing because of memory limits. Sometimes splitting up instances does help. Sometimes it doesn’t.
The shared memory for all instances of an AU used to be a fixed limit but that changed many OS versions ago and seems to be dynamic now. Apple hasn’t documented the current allocation limits and hosts and AU have no way of knowing what the limit is.
Woah, woah, woah! I'm just the idea guy! I'm not invested in iOS enough to contribute much. Unfortunately, I've got some hand/wrist issues that don't allow for the platform to be viable for me anymore as a music writing tool. I'm only going to use Note very sparingly from here on out.
I just love the community
No worries.
Still, the idea is worth looking into it seems and as mentioned in the Beepstreet thread let's see what happens.
Here’s a what I wrote over at beepstreet.
Hope this vibes with everyone. The idea is to have a community once the foundation is made of the modules currently within and for people to add contributions afterwards, not too dissimilar to patchstorage but rather than sharing a patch it’ll be to give recipes to different modular ideas within Drambo.
Again this will be on GitHub and will make it simple for people who don’t use it (IE; edit this page here button with minimal effort and push) - it will take a couple weeks for the foundation at any rate.
I don’t know if there’s a stack of screenshots of all the modules @Gravitas that you or any of the other beta testers might be privy to, but if so that would be helpful!
Cheers everyone. Please provide any input.
EDIT: link to general idea of the flow of the help. Basically a wiki but with a map that connects nodes and a smoother flow to it.
https://help.obsidian.md
When considering the structure of this new documentation, in addition to recipes, please consider this from marketing 101:
The difference between features, benefits, and other elements like value propositions is often clarified through a framework that helps guide messaging.
Here’s how these are typically defined:
• Example: A phone has a 12MP camera, 128GB of storage, and a 6.1-inch display.
• Example: The 12MP camera allows you to take high-quality photos, making memories vivid and clear.
• Example: “Capture life’s moments in stunning detail—always keep your memories in focus.”
• Example: Compared to other phones in its class, this camera performs better in low light.
• Example: Owning this camera isn’t just about taking photos; it’s about cherishing every moment.
Focusing on benefits and value propositions rather than just features is generally the key to effective communication.
Excited that git was landed on, happy to contribute once it's up!
Drambo curious here.
Earlier in this thread a bunch of folks said they use Loopy & Drambo together. I'm wondering what folks see as the benefits of that workflow are. I can see that Drambo has a sampler, but I take it that clips in the clip view are midi only. Is Drambo like NS2 in that audio has to be hosted inside a sampler device? Maybe that's where the preference comes from, that you're working with rendered audio rather than midi??
Sir, this is a GitHub wiki.
Jokes aside, I could see 2. Benefits having their placement within the documentation. I find that Michael has done a bang up job (assuming he wrote it - correct me if I’m mistaken) when coming to striking a balance of informative yet attention keeping with his documentation for Loopy Pro on the website.
But marketing terms don’t always benefit the learning curve for users, but there should be a balance struck between the two in some regards. Either way I appreciate the input and it’s well worth considering. Was this your own thoughts or ChatGPT? (Forgive the question, just clarifying, not making any assumptions nor judgements)
Overall, my own experience I mean, being a green musician is that a lot of terms fly right over my head and took a fair amount of research to find out. Acronyms being the largest of issues within modular communications.
It took me FOREVER to learn that CV meant control voltage which, in hindsight, doesn’t really matter but it is a thing that brings confidence in understanding any tool/projext. I now realize in software, CV is more of a carryover term from hardware. Now I can mentally link that to the next idea and start to think of hardware/software in music being more intertwined than I might have believed at first glance, in some cases. MIDI to CV IE means MIDI notes turn to CV, etc.
With apps being so accessible and affordable (iPhone - Drambo - $20 - $35 (IAP)) it leaves the ease of accessibility giving a false sense of ease in ability to being able to understand the terms, functions, ideas, so on. Where as a person diving into modular hardware is spending 100s of $ and they’re gonna research a bit more. Usually lol.
Granted, any hobby should be considered a slow learning process and people should be okay with learning about x or y when taking on a new project/ hobby.
But I think the solution / docs idea with the linked terms / articles ala wiki style can be a really nice bridge for both grasping Drambo, and eurorack in general considering that’s the modular foundation it’s evolved.
To end this jaunt, everyone has different learning styles. I am more of a person who learns from doing, but I am also one who loves to know what so on and so forth means for it to be fully interpreted and grasped. Others can just create and not worry about so on and so forth and I wish I had that version of a brain but it is what it is lol. I just hope to provide a quick, accessible, and valuable tool for the community.
I would have thought of Loopy Pro as the audio recorder in the first place, but I'm sure there are many possible combinations here...
Wrong thread
As @rs2000 has suggested I, in broad terms see Loopy as an audio looper and Drambo as a midi looper and sound generator.
I don’t currently use the timeline in loopy. I use it more like live performance Korg Gadget. I have 4 Drambo patterns associated with a one audio loop each with some loops common to all patterns.
It works great for creating multi part composition on the fly.
The two compliment each other really well. Loopy has more extensive capabilities for audio, Drambo has more extensive capabilities for sequencing and automation. That's a VAST over simplification because both have far more capabilities than that, but it's the main reason I use them together. They're both excellent AUv3 hosts, so I don't feel like that's a differentiator.
As for which hosts which? To me that comes down to which seems more central in one's workflow.
Thanks all for sharing about workflow with Loopy. I'm getting a clearer picture. I usually use IOS apps as a sketch pad and finish in Ableton, so I might use Drambo to sketch then render stems for further editing and processing.
Acronyms are certainly an issue.
lololol
Exactly this.
Before midi was CV.
The beauty of dRambo is that it simplifies a lot of eurorack terms and forms a base for delving into Eurorack.
Combine MiRack and dRambo and the learning curve for real modular becomes far, far less
without spending a huge amount in the actual hardware.
To certain degree you can use both of these apps and you would be abe to cover
most of the ground of real eurorack hardware and then some.
What dRambo and MiRack do not satisfy is G.A.S and that's for another thread.
Note the acronym
It's the same for professionals the only difference is that professionals are adding to their toolboxes.
Agreed.
Agreed.
Some people learn visually, for instance youtube, some learn by doing and some learn by reading manuals.
Combine all three and and learning speeds up tremendously.
Looking forward to what you and the others are going to do.
@offbrands
This could be useful for github.
@tk32 put these together ages ago which can be found in this thread
https://forum.loopypro.com/discussion/38019/drambo-by-beepstreet-released/p1
Oh cheers to the other responses and to sharing this! I actually just recalled finding these images a while back but didn’t see any updates to them after a bit. I probably have them on my Mac. Good looking either way! I completely forgot about em.
I’m going to implement a dark / light mode in the docs website and hoping I can sort out a site that reads the browser preferences and the light / dark switch will just be fallback.
Mind if I DM you @Gravitas ?
@tk32 has been quiet for quite awhile however they kindly left
these images for us to use and I think that they're good templates.
Not at all.