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.
Simple Cubasis2 question
Have been having reasonable success tinkering with CB2. I’ve brought a short sample and then copied it to fill out the track. But they are still separate “regions”. I can’t seem to find a way to select a series of regions and join them so they become one bigger region. There MUST be a tool for that, but I haven’t
Found it yet. 🤪. Any hints?
Comments
Tap the Select icon on the toolbar and lasso the regions you want to join (tap and drag around the regions). This will select regions. Now tap the Glue icon in the toolbar.
It works with MIDI tracks. There is no audio glue in Cubasis, yet. What you can do is freeze the track (the snow-flake-looking icon on the track) and it glues the regions into a new audio track as a workaround for now.
Audio glue is on Cubasis' roadmap.
It may be a low-priority for them because there is a workaround for it for now
Boy! It is surprising to find such a logical, basic feature missing from an App as mature as Cubasis 😳
It all boils down to priorities. What issues are blockers/critical, what features are absolute must, what features add the most value to the app, what features can wait, what features are nice-to-have, etc. When a project has multiple issues/deficiencies/feature requests, it is impossible to resolve/implement all of them simultaneously, especially when their iOS team size is small - they need to be prioritized. Not to mention, Steinberg is apparently cautious about not pushing boundaries so the app does not end up maxing out on memory or crapping out or crashing. Its a matter of time before most of these mobile DAW apps would have more or less the same features one day as they do now on desktop.
The major issue is the limits and limitations of iOS and iDevices (iPad is not a full-blown computer like Surface). After squeezing every drop of performance with proprietary hardware and software, Apple offers minimal RAM, processor, etc. which are good when the device is new or a couple of years old - unless you buy the iPad Pro, iPhone X models. I used my old MacBook (2007) for 8 years, my current MacBook (2013) is 5+ years old and going good but cannot imagine using my Air 2 for more than 4 years. Sure, it will work beyond 4 years for normal use with productivity apps such as watching videos, browsing, etc - but not processor-intensive DAW apps. Maybe, if iOS 12 brings back some lost performance (from iOS 11), I can use it for another year or two. Strange - MacBook lasts for just 3 hours on a charge while iPad lasts 10 hours kicking Mac (when new) and yet, MacBook outlives an iPad
If someone asks you why we need high-performance devices when most others are doing fine with basic/old devices, just tell them its because we are abnormal professionals 
Also worth understanding that the more features an app has (and iOS DAWs nowadays are all generously spec’ed), the more complex it is and therefore the greater the risk when introducing new features. To mitigate that risk regression testing needs to be performed - this testing ensures new features don’t break existing ones. So the more features you already have, the more things can go wrong, the more testing needs to be done. It takes time to get it all right, especially with a small team. Rushing a release does nobody any favours so prioritisation is the only way and as @MobileMusic rightly says, Steinberg seem conscious of not wanting to overwhelm the platform. They are all about the user experience and making things simple and stable, which I think is great.
I’m happy to use freeze and spend the dev effort somewhere else.
Another work-around for the missing 'Audio Glue' would be to freeze the track but that will freeze the entire track since there is no option to 'Freeze Selection / Freeze Between Locators'.
It seems that the feature is there, but without a dedicated button labeled ‘merge’.
Apparently, it is more complex than MIDI glue, which they nailed it out of the box (MIDI is just data as you know and may be simpler to glue).
I was gonna suggest that
Or solo the track, mix down between locators and the insert the exported audio file into the track?
Now we see why audio glue is low-priority for Steinberg.
So I found the ‘freeze’ function, but I cannot find the ‘melt’ function.
No dedicated ‘melt’ button? WTF?
I do feel I have a 'clue' as to why AudioGlue might trickier to do...
The 'split' function doesn't create new files, it just creates a new 'window' to the same audio-file (this is why the edges of an audio event can be extended to reveal more of the original file after a split).
The 'Glue' function would almost always have to create a new audio file unless the two events that are next to each other belong to the same file at precisely the same position prior to the split.
I due time we'll get this feature in Cubasis, no doubts about that.
But I'd rather see the Cubasis team focus on bringing the Cubase 'Sampler Track' to Cubasis
Correct! Even video clips work the same way with trim/split in video editors such as Luma Fusion - we can extend the clips to reveal more content on either sides.
(edit) Inserting small portions of an audio/video clip may consume the entire size of the audio/video file for each event in the project even though just a portion of it is rendered.
Not so with MIDI events - we cannot extend them to reveal more content as it is blank if we do.
On another note, audio glue may not work perfectly if related events are adjacent to each other - to create a flawless transition between them - as it was in the original file. Try adding an MP3 song file, split the event and play from one event to its next split event - you would hear some pops/stalls while the playhead passes over the split (which were not there before the split) and so, these flaws may be audible in the frozen track too. This may be another reason why it is more complex to glue audio.
When you split an audio-event in Cubasis it's still the same file on disk, just different 'start/end' points.
(It's a real pita to 'trim' clips that have been split since the events start/end are not reflected in the audio-editor).
So in order to avoid 'clicks' when glueing two separate wav-files together one would need to do some form of cross-fade prior to gluing them together.
Heck, they could enable the Glue button for audio events and automate all of these workaround actions behind the scenes (freeze, delete events, move frozen event, delete frozen track - OR - solo track, mixdown between selected event locators, delete events, insert exported file, delete exported file) - but it won't be a perfect solution due to the flaws discussed and maybe a few other issues
Maybe simply linking audio files in the interface, without all the actual merging going on, moving tracks automatically, deleting original clips, etc. would be easier, and basically accomplish the same thing.
The audio files link to act as a single block, but can be unlinked at a later stage if necessary. No processing or merging, just interface trickery.
Seems way easier to code this, too, but I don’t really know.
Did you try the microwave button?
Dang it! My whole iPad melted!
Not what I wanted, at all.
Now, here is the final step - put it in the blender
Well, that was one TOUGH PAD
They'll blend anything (including diamonds!) - https://www.youtube.com/c/willitblend