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
Now that looks like a developer which is responsive to user feedback. Well done.
Thanks again @Janosax!
Did receive your eMail message and shared it with the team.
To me it looks like that some of the AU plug-in instances unload, but our engineers will have to check.
Please share the feedback from our friends at UVI with us as well (of course we're at hand to exchange).
Best,
Lars
One thing that I'd love to see in Cubasis in the future is 'clip gain' and 'non-destructive normalize' of recorded/imported audio.
ie. use the 'clip gain' to adjust the audio clips level to match a set target (peak or rms) level.
@LFS this should be a pretty easy to thing to add so do feel free to add it to the ever growing to-do list.
This would also make 'level matching' imported audio a breeze...
3.4.1 feels like a very solid update and I'm quite sure things will improve even more over time
Cheers!
@Samu good idea! Also a gain trim for instruments would be similarly helpful, the “normal” output level of instruments can be quite variable…
Agreed, the built-in 'channel strip' plug-in is quite useful for gain-staging sources and ofter overlooked...
...but it irks me that when tweaking it there's no way to see the actual channel level when using it...
@LFS Something like this when using the channel-strip/plug-ins would be very handy!
Cheers!
??
12.9"?
Still it's quite a strange design decision to not have the channel / output level meters present at all times...
Even even if you can view the channel meter in the inspector-area there's no indication of the output level...
i agree, the master output levels should have a way to be visible with other fx/instrument panel open.. but cubasis doesn’t do floating windows like Auria ... maybe something really thin & discreet on the far right of all versions of the slide up panels?? or something in the transport header?
>
There's plenty of ways it can be implemented in non-obtrusive way
A thin vertical 'light bar' on the left or right side on each track (left of M or right of S) or a horizontal one above the track name.
And 'master level' could be horizontal light bar under the BPM etc.
I'm not particularly fond of adjusting levels without numerical and visual feedback especially since I monitor at a quite low volume to protect my ears...
Cheers!
@LFS
When an instrument is switched to another on a MIDI track, the instrument “name” does not change to the name of the newly selected instrument on the track header (left column with instrument icon, mute, solo, etc).
The control above the keyboard with left and right arrows and instrument name should popup instrument drop down when tapped - for instrument selection.
Chord buttons look dark with tiny fonts and look “disabled” (compare them to v2 buttons).
Pressing and holding a chord button and then scrolling the miniature keyboard releases pressed keys. They should be held down while scrolling (see v2).
Chord in the button 10 does not import correctly (has a wrong chord in it) when imported from v2. It imports the chord into button 11.
While editing a chord button, if we switch to another button, it gets overwritten with previously selected chord button’s chord! Noticed this from button 10 to 11.
In edit mode, tapping on keys does not select or unselect the keys for chord button 11.
Trying to edit chord button 12 crashes Cubasis! No error-handling?
Button 11 and 12 are being useless and serving no purpose due to the above glitches.
Use Avenir Next Condensed font for modern looks and to pack more text. See AudioKitPro apps using Avenir. Also Digital D1 app. They look really neat and cool like FL Studio desktop app!
I haven’t used or tested v3 fully so far. The above are from testing chord buttons quickly and import from v2.
I second this! I would love to be able to see the track strip with an AU at the same time!! Is it possible @LFS?
I suggested in my bug list on Steinberg forum - not to close any open panels while opening new ones and let the user close them and also allow them to move them up/down. Only the Setup panel opens and closes as expected without affecting other open panels. Just apply the same behavior to all other panels! There is no benefit in closing open panels while opening new panels. Why deprive users of expected behaviors for no reason?
Keyboard, Media Bay, MIDI/Automation editors and Mixer are always fixed on the bottom. Not closing open panels while opening new panels should be easier than closing/overwriting open panels with superfluous code, right? They just have to comment out the code that closes open panels! It won’t break anything as user can close the panels when done with them - just like the Setup panel. It would be nice to have a button in the panel headers to move the panel to top or bottom for making other panels visible by rearranging them as needed (also suggested in the list).
It is just a software and can be changed anytime as needed - not a fixed hardware that is shipped out to the customers that cannot be changed.
Thx for the overview, @MobileMusic. We need a grass roots movement on this one!
@LFS
In v3, Playhead Scrubbing scrubs all tracks including audio and MIDI. This is unusable as we need separate settings for audio and MIDI scrubbing and not just a common setting. Or simply turn off MIDI scrubbing.
It is usable in v2 as it scrubs only audio tracks.
For me an option to just scrub the selected track would be ideal...
Scrubbing multiple audio/midi-tracks at once just creates a distracting 'cacophony'...
...especially if one is trying to find a specific spot on one track!
Good idea!
Yes, the way scrubbing is implemented in v3 is totally useless as it doesn’t serve any purpose in multi track projects. Most frequently, scrubbing is done only on one track. Selecting tracks to be scrubbed would be a much better option (similar to Solo option on each track). It should be just a simple toggle switch per track.
Dear Cubasis Team (@LFS etc.)
The Cubasis 3 Mini Sampler needs some harsh love & care (ie. kick out the 'bastard').
'Team Cubase' has already solved many of these issues so bring the Cubase Sampler Track to Cubasis ok?
Here's a short sample to play with sampled from my Volca Bass...
https://www.dropbox.com/s/dlj3a1sxrvxm551/VBFSaw.wav?dl=0
Here's the real 'kicker'...
The Sampler in GarageBand imports the *.wav file perfectly with loops and everything already in place!
There are plenty of apps that already support sample loop-meta data.
(In no particular oder GB, NS2, Caustic, BM3, AudioLayer & SunVox just to name a few).
I get that the Cubasis team is 'small' but I do hope there's at least ONE person on the team that has a passion for sampling...
Looking forward to what's in store for Cubasis 3.5 (or maybe we'll see a bunch more 3.4.x updates before it's time...).
I do admit that I have a 'Love & Hate' relationship with Cubasis and with some extra spanking it may behave as expected some day
Cheers!
/Samuel
Not sure if it’s been requested but having floating effects/auv3 windows like pictured below would help the workflow in Cubasis tremendously. It’s quite tedious to go back and forth between effects when making adjustments while mixing. I know that the iPad/iPhone screen doesn’t have the most space but I think it’ll still be a great change.
I just noticed Cubasis now saves stems masterfx included. Quite happy with that (as I can choose to turn them/some off). Before stems were always dry (concerning the masterfx).
Especially handy for stutter fx on master that can now be baked in the stems.
Anyone know whether this was an intended update?
It was suggested earlier not to close any open panels before opening new panels (like how the Setup panel works) and allow the user to move the panels around and resize them. The panels do not need to occupy exactly half the screen or a third of the screen, always fixed to the bottom or top, etc. Commenting out the code that closes open panels before opening new panels would give a BIG BANG for a trivial code change! Try to open new panels where there is no other panel open - if any empty room is available; if not, just open it on the bottom and allow the user to move it around. On iPad, divide the screen into 3 horizontal panels or size the panels into third of iPad screen height while opening the panel and allow the user to move or resize panels (liquid layout is already available in Cubasis 3).