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.
Tera pro DSP consumption
I didn't know how DSP hunger it is, since I started to play around it spikes my DSP usage to sky high, then continues to use large amount of CPU for itself even for basic presets. Is there a way to use Tera pro with less power?
Comments
Have never had even the hint of a problem but I suppose it depends on your device. You could maybe try restarting though?
You might try turning off Tera Pro's Reverb effect (in FX); it is kinda inefficient. Also, the FM7 module is a bit special. Are you using it?
You can lower the polyphony in the settings, that will probably help a good deal
I'm on 2020 pro, guess have to upgrade my device 🥲😅😅
I turned off all, just hit few notes and 70% DSP usage
Oh yes, it was on 128 max voices, drop it to 32 😆 now it's around 20-30% DSP, I guess it's not too bad
What is your buffer size?
As others have said, definitely reduce max polyphony in the settings. I think it defaults to 128, which is a real CPU hog, but if you reduce it to 32 or 16 you should see a big difference. I'm still using a 2017 iPad Pro but I get decent performance from Tera Pro by doing this.
You mean sampling or polyphony? I don't see buffer size like other synts
I reduced it to 32 and dsp usage went down to 20-30%, not bad but still plenty. Maybe should reduce to 16
Buffer Size is a setting in your host’s settings. it has a huge impact on DSP usage.
Yeah I leave it at 16
It’s mainly a problem for me when using the FM module. If you add an ADSR envelope after it, you can reduce the amount of active voices (the dev said it was by design and provided this as a solution, otherwise the voices keep active all the time!)
.
Never bought it because of that issue. I used teraverse sparingly. Older devices handle it well.
@Johanso See what your buffer settings are in AUM, as mentioned above by espiegel123. I’m also on a 2020 iPad and found Tera Pro too much until I raised the buffer to 1024. You’ll find it from the hamburger menu top right in AUM, then choose the gear icon. Second row from top is Buffer Size setting.
I’m able to run 3 instances and hover around 25-30% DSP. On my 9.7 iPad, 3 Tera Pro in AUM run about 35-40% DSP, so coupled with a lower polyphony, increasing the buffer size should make things usable for you.
Got it. I need to increase or decrease the buffer in order to reduce DSP use?
@Johanso said: Got it. I need to increase or decrease the buffer in order to reduce DSP use?
Decrease polyphony in the synth to either 8 or 16.
Increase the buffer in AUM to either 1024 or 2048.
I find 1024 gives me enough to run 3 instances of TP just fine.
Oh.. so buffer works as using more hardware source? I mean higher the buffer more hardware used? I thought opposite
Correct: smaller buffer → lower latency → higher CPU consumption
No.. it works this way:
During bufer time, DSP code of plugin has a small portion of that buffer size timee to calculate it's stuff .. all other running plugins are competing for slot in this time frame (for example within 5 ms bugger) .. If plugin doesn't manage to calculate stuff fast enough, you start hearing dropouts.. by increasing buffer you give plugins bigger time interval to calculate all their stuff.. So when you are let's say on 5ms buffer, and you start hearing dropouts, indreasing to 10, 15 or even 20ms allows you to have smooth playback again and even add a bit more (until you again reaches the limit)
There is other problem - many plugins are suffering by this problem, for example Model D and looks like Terra at some conditions - they are eating CPU even for voices which are not playing. This is something which IS fixable in plugin with proper optimalisation techniques, so this is really weakness in plugin which IS avoidable.
To be exactly precise - higher CPU consumption on bigger buffer is simply result of fact that when buffer is bigger, plugins have more time to do all their calculations (which stop in middle on smaller buffer) properly so they a actually do MORE calculations (which obviously in most cases means CPU consumption goes up - but not always)
It also depends on the DSP design of the plugin.
If "calculations" are done at the block level, then they will occur less frequently for a larger buffer size.
For any "calculations" performed at the sample level, the buffer size has no effect.
That's just one reason why some synths benefit from buffer size twiddling more than others.
there's more than one way to skin a cat...
👍
Virsyn stuff has often been intense in use. The Only one that doesn’t need much babying is microTERA. I love all dude’s stuff but there has been some struggles…