Multi-core iOS DAWs besides Cubasis 3?

wim

@dendy said:
i think also FLSM amd nTrack, and it was on roadmap of Loopy Pro but no idea if it was added

Not added to Loopy Pro yet. Other features have higher priority right now.

wim

Loopy is first and foremost a live performance tool. Multi threading is of far lesser benefit there because of the latency it generally adds.

Synthi

@wim said:
Loopy is first and foremost a live performance tool. Multi threading is of far lesser benefit there because of the latency it generally adds.

What latency?? IME with miRack for live use there is no added latency compared to single treaded audio

wim

@Synthi said:

@wim said:
Loopy is first and foremost a live performance tool. Multi threading is of far lesser benefit there because of the latency it generally adds.

What latency?? IME with miRack for live use there is no added latency compared to single treaded audio

Tbh, I’m just regurgitating something someone else that I consider to be a lot better informed than me has said concerning Loopy Pro. I don’t actually know anything about it myself.

I do know that no matter how much you speed up processing by splitting across concurrent threads, you still have to wait to assemble it all in order at the end before recording it and outputting it. My guess is that’s where it can potentially be of less use for a highly live performance standpoint (and not just playing back the usual sequenced stuff you’d normally do in something like miRack).

Just guessing though.

But I do know that it’s not near the top of the Loopy Pro pipeline at this time.

jwmmakerofmusic

@dendy said:

@jwmmakerofmusic said:
I'm unsure if any other iOS DAW has multithread support. Does Logic Pro have it?

yes, iLPX supports it.

Good. As it should. LP4i and CB3 are definitely the top two DAWs on iPad.

i think also FLSM amd nTrack, and it was on roadmap of Loopy Pro but no idea if it was added

I love FLSM! Oh man it's been a few months since I last took a look in it, but I had fun making music in it last year. Even built a ten-track album in it on Android of all things.

About Loopy Pro, the roadmap is still online.

https://roadmap.loopypro.com/

sigma79

Multi-core DAW and its super duper expiallidocious. Saw Synth.

Synthi

@wim said:

@Synthi said:

@wim said:
Loopy is first and foremost a live performance tool. Multi threading is of far lesser benefit there because of the latency it generally adds.

What latency?? IME with miRack for live use there is no added latency compared to single treaded audio

Tbh, I’m just regurgitating something someone else that I consider to be a lot better informed than me has said concerning Loopy Pro. I don’t actually know anything about it myself.

I do know that no matter how much you speed up processing by splitting across concurrent threads, you still have to wait to assemble it all in order at the end before recording it and outputting it. My guess is that’s where it can potentially be of less use for a highly live performance standpoint (and not just playing back the usual sequenced stuff you’d normally do in something like miRack).

Just guessing though.

But I do know that it’s not near the top of the Loopy Pro pipeline at this time.

In real Life is not like that, also I don’t sequence in miRack. I performing using MIDI keyboards live playing synths and Instruments I develop in miRack layered with AUv3 instruments and lot of AUv3 realtime effects as sends and inserts. All in realtime, live played with my hands. no latency added. In real life use I have less latency because I can have much more AUv3s loaded (almost 6x the amount than in AUM ) so I can use 64 samples latency without cutouts for the same project that fe. I must use 256 in other host because processing power is reaching max.

richardyot

Logic Pro definitely supports multi-core processing, but with the caveat that the maximum latency you can set is 512.

Cubasis can go to 1024 so will be able to run more instances of plugins and instruments when the latency is set higher.

cdnalsi

What about GarageBand? Is there any proof either way?

(or does a tool/app exist with which we could test ourselves?)

sigma79

@richardyot said:
Logic Pro definitely supports multi-core processing, but with the caveat that the maximum latency you can set is 512.

Cubasis can go to 1024 so will be able to run more instances of plugins and instruments when the latency is set higher.

I dont notice latency with apps and with app controllers.

Its just when I use piano external controller to a piano app. So I guess there will also be key type synth patches that are like piano ( attack wise ) that need low buffer.

and obviously recording external instruments.

Grandbear

@wim said:

@Synthi said:

@wim said:
Loopy is first and foremost a live performance tool. Multi threading is of far lesser benefit there because of the latency it generally adds.

What latency?? IME with miRack for live use there is no added latency compared to single treaded audio

Tbh, I’m just regurgitating something someone else that I consider to be a lot better informed than me has said concerning Loopy Pro. I don’t actually know anything about it myself.

I do know that no matter how much you speed up processing by splitting across concurrent threads, you still have to wait to assemble it all in order at the end before recording it and outputting it. My guess is that’s where it can potentially be of less use for a highly live performance standpoint (and not just playing back the usual sequenced stuff you’d normally do in something like miRack).

I'd like to know more about that explanation, I think I read it in passing in this forum a while ago. But waiting for a workload to happen in a single core would seem to take longer that waiting for the same workload spread across four, with the understanding that there is some overhead with thread management. Ableton Live (clearly a live performance tool) does this, for example:

How many threads are used per Live track?
Live uses one thread to process a signal path. A signal path is a single chain of audio flow. In tracks where instrument or effect racks are used, with multiple chains in parallel, Live may use one thread per chain depending on how CPU-intensive each chain may be. If two tracks are "chained" by routing, for instance by a side-chain routing, they are considered dependent tracks and count as one signal path. Any dependent set of tracks will use one thread each.

https://help.ableton.com/hc/en-us/articles/209067649-Multi-core-CPU-handling-FAQ

Additionally, there are desktop plugins, like U-He Diva, which just spread out voices across cores when multi-core is enabled, and they do this regardless of multithreading support in the host. We could pester plugin devs as well

yellow_eyez

@iamspoon said:

Between all this mention of VS which I love, you made me go back and check out BAM and I gotta shout out @sinosoidal for an amazing groovebox … I love the interface. It is very cool to work within the LK looking workflow because I always loved the Imaginando interface style. One thing they do is sleek, elegant and beautiful. I want more time with it and i look forward to the roadmap and what it brings in the future because it has the potential to grow to a gr2 like level.

I was surprised to see it had multi core but sure enough it does on Mac, too. But as it is, it’s an awesome all in one + the benefit of adding auv3.( It is kind of like a bitwig for iOS, but much more manageable and it has a very nice Matrix view to work with your patterns.)

espiegel123

Cubasis uses additional buffers for its multithreaded audio rendering (which adds latency):

https://forums.steinberg.net/t/cubasis-3-2-multicore-rendering-latency-settings/678593

AEM adds latency too, but I the developer said that he was able to add less latency than Cubasis does..

I have no idea if miRack uses additional buffers (which would add latency) to accomplish the multithreaded audio rendering. It would be interesting to test. People's sensitivity to latency is highly variable. I've seen discussions where the latency is easily measurable where some people find it unnoticeable but others find it intolerable.

AkiVilla

Hi. Sorry, I have to vote for Loopy pro as a best daw. After creating a few templates for Loopy pro with flexible recording studio for creating layers of auv3 synths (aum like mixer), with lots of effect buses to bake in the effects. Then ableton live like interface to record loops/ tracks and trigger scenes. Also a separate lab page for mic and drums.. I feel that I dont need the midi feature to Loopy pro, or any other daw at all - I have experience of all the daws for Ipad and also for desktop e.g. Ableton live, Cubase, Mixcraft and logic pro with desktop. I think the main point for loopy pro is the intuitive interface you can build on it - e.g I have four Ipads easy to sync or split or multiply the capabilities

wim

I don't miss multi-core audio in Loopy because it makes it so easy to render things to audio, then idle the plugins, freeing up virtually all the processing, but leaving the option open to tweak things or add new parts. I can go virtually without end even on an iPad 9th gen. No way could I do so much even with multi-core on a more powerful iPad.

yellow_eyez

@AkiVilla said:
Hi. Sorry, I have to vote for Loopy pro as a best daw. After creating a few templates for Loopy pro with flexible recording studio for creating layers of auv3 synths (aum like mixer), with lots of effect buses to bake in the effects. Then ableton live like interface to record loops/ tracks and trigger scenes. Also a separate lab page for mic and drums.. I feel that I dont need the midi feature to Loopy pro, or any other daw at all - I have experience of all the daws for Ipad and also for desktop e.g. Ableton live, Cubase, Mixcraft and logic pro with desktop. I think the main point for loopy pro is the intuitive interface you can build on it - e.g I have four Ipads easy to sync or split or multiply the capabilities

There’s no doubt about the power of LP; it is unrivaled in many ways; but the coolest thing to me is the nature of catching a live loop and allowing it to become the basis for a song, it’s really freedom in a loop lol

@wim what do you mean? Like you can render songs to audio even if the plugin i idled? That is so cool if so, and you know something in that regard your right, it may not need it but I would love to see it as a potential feature that is already roadmapped I think, but it isn’t a necessity ofc by any means as it runs efficiently as is…

Loopy pro is the one DAW I really want to learn how to use well…Cubasis is face value simple but loopy pro has depth to it that I really want to come to understand to fully appreciate it and use it to the max but it’s so powerful it’s crazy

wim

@yellow_eyez said:
@wim what do you mean? Like you can render songs to audio even if the plugin i idled? That is so cool if so, and you know something in that regard your right, it may not need it but I would love to see it as a potential feature that is already roadmapped I think, but it isn’t a necessity ofc by any means as it runs efficiently as is…

No, that's not what I mean.

Say you're building a song. You're sequencing plugins from midi FX and (once midi looping is available) recording midi loops to play synths. You keep adding and adding instruments and FX. The CPU usage starts to go up. You're a cheapskate, so you have an pitifully underpowered device. You have to do something.

You can set up an audio loop and record the output to it for a plugin, then mute the midi and the plugin. Loopy can idle the plugin and any FX you were using and just play back the audio, freeing up virtually all the resources they were consuming. Since the plugins are still sitting there with all their settings as you left them, you can always un-idle them to tweak things or to add new parts.

I don't have to do this as much with my newer 9th gen iPad, but up until a year ago I was using an iPad Air 2, and that thing couldn't do much. With this freeze as you go approach I could work even with that iPad virtually indefinitely.

sinosoidal

@yellow_eyez said:

@iamspoon said:

Between all this mention of VS which I love, you made me go back and check out BAM and I gotta shout out @sinosoidal for an amazing groovebox … I love the interface. It is very cool to work within the LK looking workflow because I always loved the Imaginando interface style. One thing they do is sleek, elegant and beautiful. I want more time with it and i look forward to the roadmap and what it brings in the future because it has the potential to grow to a gr2 like level.

I was surprised to see it had multi core but sure enough it does on Mac, too. But as it is, it’s an awesome all in one + the benefit of adding auv3.( It is kind of like a bitwig for iOS, but much more manageable and it has a very nice Matrix view to work with your patterns.)

Thanks for the feedback. BAM is a work in progress. Anyone can track feature implementation and suggest new futures in our public roadmap -> https://imaginando.canny.io/