Disadvantages of DAWs in comparison to others

[dupont]

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.

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

[dupont]

Still ugly, though, and that's a deal-breaker for anyone with a shred of self-respect.

Nnot music related, NASA sent a rocket to the moon with a 1024 k ram computer !
I'm not the kind of guy who like a track because there are sexy girls on the video clip.
And most important, who cares if the music is good ?

On the other side, Reaper can be time consuming, there are always a theme, a script, to test.
Most added features are not usefull for my workflow (zillions of wilcards render format...) and several users FR has yet not been implemented : split arrange view, clips launcher (native, not playtime), better enveloppe window layout (a mess when a plugin has hundrers of parameters, hard to find which are currently activated)

[SLiC]

Still ugly, though, and that's a deal-breaker for anyone with a shred of self-respect.

Not music related, NASA sent a rocket to the moon with a 1024 k ram computer !

They probably didn't need a convolution reverb though

[Googly Smythe]

Disadvantage of using Logic: ya gotta use a Mac.

Disadvantage of all the others: ya gotta use a PC.

[chk071]

Still ugly, though, and that's a deal-breaker for anyone with a shred of self-respect.

Nnot music related, NASA sent a rocket to the moon with a 1024 k ram computer !

Which probably was a super computer at that time.

[bazwillrun]

Still ugly, though, and that's a deal-breaker for anyone with a shred of self-respect.

Nnot music related, NASA sent a rocket to the moon with a 1024 k ram computer !

Which probably was a super computer at that time.

It only had one job to do...crunch numbers...no graphics etc

[jens]

Here it is and the latency issues are being discussed towards the end. It was a video contribution that had some CONTENT to it:


ated.

Musotalk is really the worst of the worst - "non-Eric" really has little clue about anything and a profoundly limited set of skills.... it tends to be more satire than anything.

[EnochLight]

I'm not the kind of guy who like a track because there are sexy girls on the video clip.
And most important, who cares if the music is good ?

Clearly you’ve never seen a good classic porno.

[juno987654321]

Here it is and the latency issues are being discussed towards the end. It was a video contribution that had some CONTENT to it:


ated.

Musotalk is really the worst of the worst - "non-Eric" really has little clue about anything and a profoundly limited set of skills.... it tends to be more satire than anything.

First of all thanks to machinesworking for adding his in-depth information. It's been quite informative!
Bones has after all added at least one interesting reason why Studio One may have its more serious faults because I'd also find it rather annoying if any VST settings get totally lost in a project (if you transfer it to another computer) and I wouldn't have known or expected that. You could only tell that from long term experience so thanks for sharing that. I've never tried this DAW so far and if so I'd test it with special emphasis on this kind of issue you've made me aware of.

Now for the above comment: it's just funny in my opinion. I was asking myself: Who and how much more experienced are you then to just judge like that without giving any reasons? I trust that those guys from Musotalk know quite a bit about music productions and that the latency issues they were talking about actually DO occur. I have only seen this one episode so far because I often search for topics being discussed that catch my interest - rather than watch something arbitrarily - but this one was both entertaining AND educational, and hence I liked it. So why not just face it as true problems you might actually encounter if you use those DAWs in the exact contexts they were referring to and for the purposes they mentioned? Pah! If you, however, think the latency issues do not appear as suggested then tell us where they made the wrong assumptions and if there's any "tricks" YOU know of how YOU would bypass those issues that THOSE professionals couldn't think of (for years and years of experimenting and trying to optimize their productions). To me they added a real important aspect to think about while most people just ignore latency issues as if they wouldn't matter at all!...
Maybe you just didn't like one of those guys but that's besides the point because in this thread it's only the facts that matter to me.
(Of course I would still have to test the DAWs for myself if I plan to change from Cubase to, say, Ableton Live for EDM in the future, but I'd have a better starting point knowing what I should focus on with the demo versions of the other DAWs. BTW: I still like Cubase but I'm no longer so convinced of it as I used to be for the reasons given at the beginning...)

[chk071]

Here it is and the latency issues are being discussed towards the end. It was a video contribution that had some CONTENT to it:


ated.

Musotalk is really the worst of the worst - "non-Eric" really has little clue about anything and a profoundly limited set of skills.... it tends to be more satire than anything.

I think he actually knows more about the stuff than it appears. I know... he has a certain "appeal" which makes that hard to believe. But, AFAIK, he also was involved in the software development at Steinberg (or something... at least he used to work for Steinberg), and, he also made some pretty knowledged videos 30 years ago, or something. I watched one of those, and, it wasn't bad really.

Might have done a bit too many drugs in the time where he performed live etc. though.

[revvy]

Here it is and the latency issues are being discussed towards the end. It was a video contribution that had some CONTENT to it:


ated.

Musotalk is really the worst of the worst - "non-Eric" really has little clue about anything and a profoundly limited set of skills.... it tends to be more satire than anything.

I think he actually knows more about the stuff than it appears. I know... he has a certain "appeal" which makes that hard to believe. But, AFAIK, he also was involved in the software development at Steinberg (or something... at least he used to work for Steinberg), and, he also made some pretty knowledged videos 30 years ago, or something. I watched one of those, and, it wasn't bad really.

Might have done a bit too many drugs in the time where he performed live etc. though.

I like non-Eric when he's on Sonic Talk, he makes me smile.

[Guenon]

Nnot music related, NASA sent a rocket to the moon with a 1024 k ram computer !

No no, not even close! Even the mighty Commodore 64 had sixteen times the RAM of the moon mission computer. According to NASA, the final configuration for RAM (erasable memory, not fixed) was 2k words, the wordlength being 15 bits plus one parity bit. In bytes, that's 4096 total. In other words, four kilobytes. Any way you look at it, not 1024 k anything

https://history.nasa.gov/computers/Ch2-5.html

[jens]

Now for the above comment: it's just funny in my opinion. I was asking myself: Who and how much more experienced are you then to just judge like that without giving any reasons? I trust that those guys from Musotalk know quite a bit about music productions and that the latency issues they were talking about actually DO occur. I have only seen this one episode so far because I often search for topics being discussed that catch my interest - rather than watch something arbitrarily - but this one was both entertaining AND educational, and hence I liked it. So why not just face it as true problems you might actually encounter if you use those DAWs in the exact contexts they were referring to and for the purposes they mentioned? Pah! If you, however, think the latency issues do not appear as suggested then tell us where they made the wrong assumptions and if there's any "tricks" YOU know of how YOU would bypass those issues that THOSE professionals couldn't think of (for years and years of experimenting and trying to optimize their productions). To me they added a real important aspect to think about while most people just ignore latency issues as if they wouldn't matter at all!...
Maybe you just didn't like one of those guys but that's besides the point because in this thread it's only the facts that matter to me.
(Of course I would still have to test the DAWs for myself if I plan to change from Cubase to, say, Ableton Live for EDM in the future, but I'd have a better starting point knowing what I should focus on with the demo versions of the other DAWs. BTW: I still like Cubase but I'm no longer so convinced of it as I used to be for the reasons given at the beginning...)

Wait what?

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

[machinesworking]

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.

The caveat: in my experience Reaper does uninterrupted audio, until it doesn't. Meaning it will mostly not mess with the audio stream when you're heavily messing around with things, adding synths etc. but occasionally it drops the ball. I found that to be true of Live sometimes as well. I haven't noticed that in Bitwig but I might be biased because it's new and I tend to think I might be doing something wrong etc.

In the bigger picture I'm willing to accept some stutter in the audio for the 20-40% increase in CPU performance you experience using Reaper, DP, Logic etc. especially in larger compositions with more tracks etc. It will be interesting to see what the next gen MacBook Pro and it's very obviously brutally powerful M1x (or whatever they call the 12 for that's coming) does to my decision making about DAWs.

Without any CPU concerns will I stay in Bitwig for everything? I think it really depends on whether I'm doing orchestral stuff or not. Logic is there with articulation mapping, and DP will likely get it in the next update so.

[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.