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
The other files have the same problem, I can not only hear the distortion but it can be easily shown in any audio editor.
The default volume of any app you load in Cubasis/Aum/Auria or whatever DAW you use is not necessarily the right one. Although it’s usually ok, there are some apps in which the default volume level is too loud and needs to be ajusted for a proper recording.
Here’s a screen capture from Audacity with the problematic tracks. You can see the clipping in red color, that means that the volume in those peaks was too high. That can be seen in the waveform in the picture you posted from Cubasis. The only way to solve that is to go to the sound source app and lower down the volume.
@tja Yes I did, it's almost right except for a few spikes. It's the last file in my picture._
Out of curiosity, did it work properly in Auria Pro?
There are two different problems, one is related to the volume level and eventual clippings (I insist it has nothing to do with Cubasus/Auria but the volume level of the sound source app), the other is related to the freezing feature in Cubasis introducing longer audio tracks as if they had been streched out. The latter has been discussed in this forum and other forums and Cubasis was fixed in some way to avoid the problem, but it seems there are still some issues pending. The problem is related to apps that make intensive use of the CPU during the freezing operation and the way Cubasis handles this feature.
Hi tja, Hi all,
After exchanging with our development please allow me to reflect on this topic.
Since tja has published the similar topic in a different thread, you will find this answer copied there as well.
In general, using third party instruments and/or effect plug-ins always bears the risk for issues, that are often unrelated to Cubasis - as already mentioned by other users here.
The same applies for other DAW’s, no matter if mobile or desktop. In this context, running into issues, also can lead to consequential errors, when the iPad/apps in use aren’t restarted, once a problem arose.
We’ve tried our best to state the limitations of Cubasis’supported third party standards in the following articles:
Limitations of Audio Unit
https://www.steinberg.net/forums/viewtopic.php?f=183&t=92984
Limitations of Inter-App Audio
https://www.steinberg.net/forums/viewtopic.php?f=183&t=104551
Limitations of Audiobus 3
https://www.steinberg.net/forums/viewtopic.php?f=183&t=115199
In commenting your topics, Rodolfo sums it up quite well (Thanks @Rodolfo!):
“There are two different problems, one is related to the volume level and eventual clippings (I insist it has nothing to do with Cubasis/Auria but the volume level of the sound source app), the other is related to the freezing feature in Cubasis introducing longer audio tracks as if they had been streched out. The latter has been discussed in this forum and other forums and Cubasis was fixed in some way to avoid the problem, but it seems there are still some issues pending. The problem is related to apps that make intensive use of the CPU during the freezing operation and the way Cubasis handles this feature.”
(1) Track freeze and audio file length
Depending on the third party app instrument/effect plug-in and its associated values, the use of track freeze can lead to long files in some cases, making sure to prevent audio file signal loss.
(2) Audio file clipping
So far, we are not aware of any audio related problems related to Cubasis, when using track freeze.
Therefore we expect issues such as distortion or similar to be related to either, the third party app in use, the chosen format (IAA, AU), consequential errors or other problems.
If the problem persists and is reproducible, please provide the individual instrument developer and us with the steps, to allow the evaluation.
(3) Track freeze settings and further options
In a nutshell, working with third party apps and Cubasis works best with regular 44.1 kHz projects and ultra low latency.
Furthermore, if track freeze fails with specific effects or instruments using the standard setting, Cubasis provides additional real-time rendering options located in the setup (Mixdown / Share section).
Please make sure to have a look at the relevant articles that explain the limitations of AU, IAA and AB3, that are linked above.
In our opinion, Apple’s Audio Unit format can be more or less seen as the successor of Inter-App Audio.
In general, IAA seems more unstable, compared to Audio Unit, which provides more options and has recently updated by Apple (CPU time out bugfix in iOS 11.3).
Important:
If you experience issues, please make sure to send reports to the individual instrument and/or effect plug-in developers. As we did in the past, of course we're at hand and willing to exchange with them, if required.
Best,
Lars
I think this important Poll is dying a slow death due to too many choices and some production issues.
If you're short on time listen to 7,10,16,23, 27,28,40 and vote on your favorite.
@tja
Hi tja,
Thanks for your message.
As stated before, track freeze and mixdown should work fine straight out of the box for many instrument and/or effect plug-ins apps. For those instruments/plug-ins failing (e.g. due to not having update for some time, other issues) there is the real-time mixdown option.
If you run into track freeze/mixdown issues, please make sure to file a proper bug report to inform the instrument/effect plug-in vendor and us about the problem.
Best,
Lars
Agreed...I haven’t listened yet due to time it takes to compare 42 samples. It’s too much for my brain to compare that many and remember which one I like best. Also, some samples are not rendering properly due to tech issues. But I’d like to listen to them once it’s ironed out.
Also I think the song is a bit complex to compare samples. Maybe a forum member could play a song and send out the midi file? Just an improv tune with soft, med, and loud dynamics with some slow chords and some fast runs? Just thinking out loud
Hold in mind that the many synth-guys on this forum is busy with all new software that have come lately...
And, today, Synthmaster One came out and that one will occupie many many forum member the next couples of days and weeks!
And, as someone else said, more than 40 pianos is probably to ambitious;-)
I like no 10, very much!!
Just listen to 7,10,16,23, 27,28,40 and vote please. A lot of effort went into this and it's scrolling off the Forum without comments. worts case thank jta for the effort involved... hours of setup.
McD
Just trying to get more people to vote and so far those are the pianos with plus votes. 2 poll results don’t tell us much. Anything with 2 votes wins?
I listened to all 42 (and voted) but that was before the clipping was fixed. Anything that clipped I just treated as though there was something wrong in the gain structure during the creation of those samples and hence never voted for them.
Thanks tja and whomever else involved for the amazing amount of work! Really appreciate it!
Hold on, pianos is not just a hype that will die... It's been around for 300 years ;-)