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.
a calm winter inspired jam
made with 3 instances of solderbox
- Reverb - SpaceFields
- Sequencing - Solderbox
- Hosted - Drambo
- (literally just hosting could have been done in AUM)
- Video - VS synth
- Effects - FAC Punchlab
Edited - “Rarevision”
An inspiring app.
Figuring out the pulsesequncer has been fun!
(I like to experiment though)
I’ve never posted anything musically created by me on here. First time for everything. Why wait until the new year? 🙏🏽🤘🏽
** Edited to add “Effects - FAC Punchlab”
Comments
Absolutely sublime! I'm glad you posted.
Cheers @jwmmakerofmusic - Happy Holidays 🤘🏽🙏🏽
Happy holidays my friend. ❤️ Listened again. It really is sublime. Honestly I need to learn a bit more about Drambo. I bet Ioniarics would work great in that environment.
I love it ! Awesome work
I was wondering about some solderbox Jams
Nice! Got yourself a new subscriber 👍
I got @reasOne back into Drambo with my going on about it lately haha. It really is such a great place to create music.
Truly this track could have been made in AUM. I’m working on a variation of this in AUM right now and in some ways it’s a bit better for live performance for mixing with those sliders and set up. With that clock division update It’s going to help with this little vision I have for this project. Stoked!
Thank you again for listening and for giving support. It means a ton. 🙏🏽
Cheers! Thank you for listening. 🙏🏽
That’s too kind @Edward_Alexander - Cheers! 🙏🏽
Of course mate. Now, I do have a pretty stupid question. Does Drambo do multicore processing? I used Cubasis for my latest track "Krampusnacht", because it has multicore processing (which is definitely needed when using some FabFilter plugins). Just curious.
Thanks in advance.
Great question. Not stupid at all. I think @Gravitas might be better suited to answer that question whenever he sees this tag.
I will say that Drambo as a whole is very efficient. Small footprint if you prefer. I haven’t run any of the fabfilter plugins in or out of Drambo as I don’t have any but if I did I would test it!
What apps have multicore? Logic I imagine. I don’t think AUM has it right?
Forgive my ignorance but doesn’t iOS just switch on cores if and when it’s needed? Like if you’re pushing a device hard it’ll add more as they go. At least that’s what I’ve come to understand of the way it works.
Something I’ve realized is in AUM it will look like I’m 60-70% dsp but I’ll add something else and the dsp will jump down instead. So I don’t know enough about this but I’m somewhat curious now!
Sounds like AUM may have multicore processing to be honest. That's quite interesting. But I hope @Gravitas and others will be able to sort us out proper. ☺️ Cheers mate, and sorry for overtaking your thread like this.
Noooo stop. No apologies. It’s a forum for music app users, bound to drift here and there. Ain’t much action anyways as it’s the holidays so I’m grateful for the chat!
No, it doesn't.
I think @wim and @espiegel123 could answer this in much more detail than I could.
I don't think that is to do with the app being multicore.
iOS operating system makes processing adjustments, the way I describe it is like it switches up a gear
when it gets pushed and then plateaus for a few more instances of apps and then keels over and says no more.
I got the tag....
Is dRambo multicore???
I actually don't know, what I do know is that the coding is super efficient.
@giku_beepstreet has chosen to get the most out of the cpu for our purposes
and whether that involves using multicore or a single core doesn't matter,
what does matter is that we have all available cpu power for when we need to create.
Note that the Layer Switch module has "CPU save".
The one app that I know that offcially has multicore support that I've used so far is Cubasis 3.
When multicore is switched on there's a huge increase in latency which is not
so good for performing or recording however it's really good for mixing because it frees up processor power.
Thanks for clarifying all this mate.
Yeah, Cubasis 3 is great for mixing down and mastering. As well as producing tracks in.
Good to hear your music.
I like the build up.
It sounds smooth and seemingly effortless
and the outro is just as smooth.
Pleasing to the ear.
Thank you for sharing.
Cheers @Gravitas - I’ll be riding high on these comments from everyone towards the next chapter in this project, adding yours to this is a very welcome addition. Means a ton. 🙏🏽
See Jonatan's excellent rundown:
https://forum.loopypro.com/discussion/comment/1369610/#Comment_1369610
Cool @espiegel123 ! Thanks for the link. I somehow missed that. Hope you and the fam had an excellent holiday season so far.
You’re right about cores allocation. The OS does take care of that. In fact, the developer has no control over core allocation. Multi-core audio is actually an inaccurate term. Multi-threaded audio processing is really what this is about.
Before multi-threaded audio processing support was introduced an audio app had to process all audio in one stream of operations. Because of that only one core at a time could service that single thread. Other threads could handle things like the UI, so the operating system could distribute those to other cores. In that sense, apps have always been multi-core capable. But audio could not be before.
Multi-threaded audio introduced the ability to split up some audio processing tasks into independent threads, in turn making it possible for the OS to allocate those tasks to separate cores. The developer has no control over that allocation (other than to request a high performance core). Allocation is up to the OS.
The rub is: with audio, no matter how efficiently you split up and process the audio, it all has to be assembled in order before output. So, there’s a certain amount of waiting at the end to put it all into order. That’s the added latency people have mentioned.
A live performance oriented app is likely to prioritize latency differently than a production DAW.
What that means is the operating system noticed the situation and reduced throttling or switched in a more powerful core. IOS prioritizes battery life and heat reduction, so it dynamically makes less and more power available to apps. The apps themselves can only report the percentage they’re using of what’s available to them, not of total device power.
Makes a lot of sense. Appreciate the thorough breakdown put in a way that’s easily accessible to the avg lay person. Cheers.
Your first but hopefully not your last, a very relaxing piece of music 👌
That’s very kind of you @GeoTony!
I could have sworn I had already followed you on SoundCloud but I think I just had some of your music saved to my phone.
Your “Music to Watch Sloths By” piece you shared is brilliant and inspiring and coupled with this comment, a reminder for me to finish this idea for this project and to keep going.
Thank you 🙏🏽