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.
CUBASIS: Make Producing Music EASIER (100+ issues & suggestions)
I made over 100 issues, enhancements and also suggestions to improve the UX.
Vote on your desired features or add your own needs -
https://www.steinberg.net/forums/viewtopic.php?f=300&t=199158
Cheers!
Comments
@MobileMusic @LFS that is a seriously impressive list...one more for you to add. The group solo button takes priority over a track solo when you solo one individual track in a mix. So when you unsolo that track everything is muted until you find the group track that the soloed track belongs to.
Actually two - it would be nice that when you have the mixing faders up and you go into an effect from there and you close the effect window that you return to the fader window instead of being thrown straight back into the arrangement....
I do NOT agree on the Background Audio being defaulted to OFF (21) as it makes it a pita to connect it with other IAA apps.
Ie. if Cubasis has background audio turned off by default it's impossible to use it together with AUM or other IAA based apps as there needs to be a handshake between to 'alive' audio threads for things to work, if one of them is 'sleeping'(ie. background audio turned off) things won't work...
I'd say, remove IAA altogether from Cubasis 3.5 and leave it in the deprecated dust it deserves to be left in...
Added to the list. Your point # 2 refers to point # 93 "Flexible display of panels" and explains a specific situation where it is not behaving as expected due to some panels like Mixer being fixed to the bottom overwriting other panels in that place previously.
Amen, brother.
Agreed. I haven't used IAA except for once years ago sending MIDI into GarageBand that recorded only uneditable audio instead of MIDI and I did not like it. I updated the list as not recommended to turn off background audio.
Or maybe Cubasis could sense and make some intelligent decision during its launch to see if background audio is requested by other IAA apps, if possible, and act accordingly (even if background audio was not turned on in the previous session) which may resolve some reported connection issues.
Please add:
Okay, done.
As for migrating v2 projects into v3, have you tried these steps?
https://www.steinberg.net/forums/viewtopic.php?f=300&t=190896
It worked for me.
Yeee yeee!! Great tips! Thank you broski
Until Audiokits Synth One is an audio unit, don’t you dare touch that IAA😋
Fellas, I deeply respect both of you and your saavy, but some of us still use IAA and some people probably prefer it over AUv3, simply because it exists. I for one will miss my IAA apps when that day comes. All opinions are respected.
Updated the list with your suggestions.
Buggy sorting by date already listed.
@MobileMusic thanks for adding the solo thingy to the list. Seriously annoying. I think I understand the logic of what you're saying regarding point 2 - that's seriously annoying too from a workflow perspective. Hopefully these things will get some attention. Agree with the MIDI syncing stuff too.
>
Standalone apps do not have to be IAA to work as long as they have proper import & export functions.
IAA is/was(it's deprecated now) a 'half baked standard' that is a real pita to use in practice when making connections to other apps and knowing no further development is being done on IAA so it's better to mentally prepare that it's going away...
Sure AudioBus still uses IAA as the backbone but too many app rely on the AudioBus IAA implementation and I do not consider those apps 'fully supported' IAA apps as AB only adds an IAA Generator 'for free' forgetting the rest.
Who knows what improvements will be made to CoreAudio over coming the years, we might even get something like SunFlower for iOS but it's highly unlikely at the moment.
Sure I have apps too that are still IAA only but most of them do have some ways to get stuff out of them (render to file, built-in recorders etc) so even if IAA as a protocol would go away I can still use the sounds from the apps just as I do today...
(I prefer create->render->export->import procedure in favor of live recording).
Cheers!
Your both points were added to the list. Point # 2 was cross-referenced to point # 93 proving specific use case where it does not behave as expected or desired.
@MobileMusic thanks for the clarity. I think I just got myself muddled in there.
The bugs/suggestions list has now over 120 items -
https://www.steinberg.net/forums/viewtopic.php?f=300&t=199158
A lot to ask of a $35 (when on sale) app. It's not a desktop DAW. Cubasis 2 is rock solid on an iPad Air 3.
Yes but if you never ask. 😀
Most of what we are asking is - refining and redefining some stuff to make an already easy-to-use app even much easier to use. Many of the listed issues/suggestions also pertain to v2. Some releases of macOS and Windows were purely to refine processes, resolve bugs and make them faster and easier to use.
We are using these $1,000+ pocket computers but still doing a lot of work ourselves (not the actual project content work) and using workarounds that we don’t have to. Why not automate some stuff to make these computers do as much work as possible along with some cool power-user-friendly features to make our lives easy so we can laser-focus on our work and what matters most? Apps that give us a tunnel vision are the best! There is not much tunnel vision when we are required to do other work and workarounds and also use other apps.
Midi mapping and midi external control. Simple wish.
Just added your wish.
125 and counting...
just split the work up. noodle in AUM, transfer the stems to CB3 /Auria/Gadget/BM3/Zen. Be modular
I wonder if/how many of these great suggestions are maybe being tested on a CB3 beta that may or may not be existing right about now.?.
I've added more issues and suggestions to the list and it is 170 now and counting.
Also, I edited and cleaned up many of these suggestions in the thread with more detail and clarity - if you read them before, you may like to read them again.
https://forums.steinberg.net/t/make-producing-music-easier-100-issues-suggestions/156430
I like that Cubasis keeps getting updated. For that I am willing to keep my nose in there and stay interested. I feel that the items on that list and the list itself is an important one as there are a lot of items on there that relate to general workflow that if implemented would make things a lot easier and fluid. It says a lot that the effort has been made to put this list together. I always feel with the updates that there are things done, but just like Apple hardware updates, they just give you enough to stay interested, but never seem to deliver the full enchilada. Having said all that I appreciate the work that has gone into this and I appreciate the communication, but sometimes I feel like it's all just a sales pitch.