Disadvantages of DAWs in comparison to others

[pdxindy]

My I7 10th gen 8 cores don't care about CPU pig DAW, it can eat everything

I could kill your 8 core easily.
And I'm not a 50 tracks per song person even.

It would be easy to do with 8 tracks and Reaktor Blocks!

[dupont]

They probably didn't need a convolution reverb though

no need, reverb on the moon is fantastic

[dupont]

My I7 10th gen 8 cores don't care about CPU pig DAW, it can eat everything

I could kill your 8 core easily.
And I'm not a 50 tracks per song person even.

So you are a 50 plugin per tracks ? If a plugin uses so much CPU power so it is a bad coded one and I will avoid it !

[machinesworking]

My I7 10th gen 8 cores don't care about CPU pig DAW, it can eat everything

I could kill your 8 core easily.
And I'm not a 50 tracks per song person even.

So you are a 50 plugin per tracks ? If a plugin uses so much CPU power so it is a bad coded one and I will avoid it !

Yes, Repro-5, Reaktor, Diva, some Falcon and Pigments patches... these are terrible sounding things that can easily be replicated in synth 1.

The fact is developers will take advantage of whatever CPU is out there. I'm happy you're happy with what you have, but it's anecdotal and subjective to think that what you do is best, or that someone can't take advantage of 30% more CPU without it being due to bad coders.

Or more succinctly, is Bitwig badly coded because it takes more CPU? this is what you suggest.

[juno987654321]

Wait what?

I don't even use Live -but claiming to be interested in facts yet linking to a Musotalk-vid...

Don't worry.
I didn't mean that YOU helped me to be more informed about Ableton and the other DAWs.
I was only referring to the other users. So don't be confused.

Let me say it like this: I MUCH prefer that Musotalk vid to your information so far.

[BONES]

Any criticism of anything is in the end personal preference, but you can glean objective truth from it.

It's not. e.g. Criticising a Reliant Robin for being unstable in corners is a simple fact, born of it only having three wheels.

DP and Bitwig win that game with their super fast search and select feature you don't even have to remember the key command, just the name that DAW decided to call that function..

I hate that kind of stuff because it makes people lazy. I work with a generation of artists who have no idea where any effect or plug-in resides within the folder structure of After Effects. They rely 100% on the search function and to me that means they never really learn the application and, as a result, they don't think the same way as those of us who learned the software before that search function was added. Because of that they are much worse at problem solving and, for my money, our job is all about solving problems, so they are measurably worse at their jobs.

[MuzikFreq]

Cubase (i still love it but) : audioengine drop out when adding a new track

That one is a big advantage of Bitwig and Live to me. All the other DAWs I've used are likely to stutter or throw up a warning when adding a new instrument or audio tract etc. The uninterrupted audio engine that truly lives up to it, but at least in those DAWs you pay for it with higher CPU usage.

So make up your mind

Because that's the price of Bitwig being "CPU pig" (which it really isn't), i.e. a single realtime buffer, instead of a hybrid / double one.

Bitwig a cpu hog? It's probably one of the lightest.

[dakkra]

Bitwig and Mulab don't have ARA.

Studio One and Logic Pro don't work with multi-input/output VST effects, and barely handle multi-timbral in a very non-elegant way.

Studio One's default compressor is... not so great. It feels like it does too much averaging to my ears, almost like the RMS time is too large.

Pro Tools and Logic don't support VST/3. I mean seriously, everyone but these two support VST at the minimum, and many support VST3.

Reapers audio routing is flexible, but very unintuitive to a graphical modular user like myself. I'd much rather have a graphical router (I know it somewhat exists, but it's still not intuitive) than a channel matrix.

FL-Studio, while very pretty, had very basic mixing and channel routing, and depends too much on channel sends for audio and MIDI routing. I wish there was a way to use track lanes instead of patterns for working with MIDI. Would me much more intuitive in relation to the rest of the DAW market.

Waveform has far too many bugs, and is hampered down by a cluttered and confusing GUI.

Waveforms default plugins are akin to freeware. I'd rather use better free VSTs than Waveforms standard library.

[antic604]

Cubase (i still love it but) : audioengine drop out when adding a new track

That one is a big advantage of Bitwig and Live to me. All the other DAWs I've used are likely to stutter or throw up a warning when adding a new instrument or audio tract etc. The uninterrupted audio engine that truly lives up to it, but at least in those DAWs you pay for it with higher CPU usage.

So make up your mind

Because that's the price of Bitwig being "CPU pig" (which it really isn't), i.e. a single realtime buffer, instead of a hybrid / double one.

The ugly head of Reaper has entered the chat. Reaper for the most part manages to do both things, uninterrupted audio and low CPU consumption. So it's possible to do both. You just have to accept a "build your own DAW" approach, at least for now.

That's not my experience with Reaper at all. Just a simple project with few VSTs would cause the playback to fall appart all the time when I'm tweaking / adding / removing stuff or even editing the MIDI. It felt like every track is in its own tempo and sync. I can't even imagine how it would all sound with complex chains I do in Bitwig... I'm willing to pay the price of peak performance, to have great every-day reliability.

[dupont]

Or more succinctly, is Bitwig badly coded because it takes more CPU? this is what you suggest.

In fact, that's what I explained i my post, my I7 CPU is soo powerfull, I don't even compare the CPU usage between DAWs.
I used to make track 6 month ago with a 2007 core2duo CPU so I7 is a huge step for me (and for humanity)

I tried a pigment preset because a poster said it was CPU hungry, far stab if I remenber well, on my CPU, 20 % of 1 core is used only.

[Passing Bye]

20% for 1 instance is still huge chunk.

[antic604]

20% for 1 instance is still huge chunk.

That's 2.5% of the whole CPU. That's nothing.

[Passing Bye]

My bad, I taught DAW meter showed 20%...wait, that doesn't change much, DAW core utilization and meters doesn't work like OS one anyways, if you overload one core it will pretty much crackle...

[BONES]

Yes, Repro-5, Reaktor, Diva, some Falcon and Pigments patches... these are terrible sounding things that can easily be replicated in synth 1.

Don't change the context - those are also things that any octa-core CPU will handle easily so what you are really doing is helping dupont make his point.

The fact is developers will take advantage of whatever CPU is out there.

Right, but they won't have a clue that people will need to use their product in a DAW with other plugins. Does that seem likely to you?

I'm happy you're happy with what you have, but it's anecdotal and subjective to think that what you do is best

No, it's not. It is a perfectly reasonable position to take, assuming he has put any effort into finding the best way to do something, rather than throwing his hands in the air and saying it can't be done. Anyone reading the thread will have one question - who has more credibility here, the guy who can make it work or the guy who can't?

[trusampler]

Presonus Studio One, now on version 5, still can't understand sysex is a thing for musicians. just saying, it's become a headache now Presonus