Looking to ditch Logic and Apple. Help!

[revvy]

In this ONE, single thread:

You mean the fanboys?

fanboy speculation

if the fanboys wouldn't have jumped here to try to persuade the OP to get back in his intentions.

You are just insulting, as does any fanboy.

I'm not interested in talking to fanboys.

But you seem to be Apple fanboy

Because I called you a fanboy? If you don't want to be called that, don't act like that.

Totally normal discourse.

[fmr]

Totally normal discourse.

Et tu Brutus? Cogitavit hoc dixisset vale. Quam sub separans.

[machinesworking]

Your issues are not going to be solved by a new PC and a different DAW, not in the long run.

Let him find the hard way, there's price to pay for being stubborn.

Does any of you speak from personal experience? Because, as an owner of both Mac and Windows systems, I can assure you that YES, his specific problems will be solved with a new PC. A different DAW is a consequence of the option, since Logic isn't available in Windows (thanks to Apple "vision").

But you seem to be Apple fanboy, so your statement isn't to be taken seriously, is it?

You're not paying attention, because you made up your mind years ago.
His specific problems are not OS related, period.

Everything he mentioned is due to poor track management and attempting to do things no OS or DAW is capable of. He stated he was using two different room attenuation plug ins on his master fader, then complaining that his soft synths were unplayable. The types of plug ins he was using are not designed for playback, they're specifically designed for the mixing stage after you're finished with composition. There's no OS or DAW change that will fix that.
He talked of overloading a single core in Logic, you can do that in any DAW, simply load plug ins on a track, route that track to an Aux, then load plug ins there, which he also mentioned doing. These are track management 101 things, that you and others haven't addressed at all.

Changing OS and DAW will not solve his issues, what will help temporarily is a new computer. So in a year or less, his issues will come back, because he's doing things to cause them that a speed bump will only mask for so long.

Personally I don't care what OS or DAW someone uses, but it's obvious to me that changing them will not fix his issues in the long run, and I cannot imagine a scenario where you explain to me how the OS causes the two situations I mentioned above? I don't expect a rational answer from you on this, I'm mainly typing this for the rest of us. There are valid reasons to use OS X and Windows, but the issues OP described here are due to not knowing how CPU is allocated in a DAW, not due to the OS or computer etc.

I've specifically given my advice on what DAW I would use in Windows, what CPU I would use, and even suggested to him not to get the Mac Pro, that if he's serious about switching, don't bother with Intel, an AMD machine is more way more powerful for the price. but I'm the fanboy. Oh wait, I'm supposed to hate Apple right?

[fmr]

Actually, the post was mainly addressed to Passing Bye, but whatever. It's me not paying attention...

Everything he mentioned is due to poor track management and attempting to do things no OS or DAW is capable of. He stated he was using two different room attenuation plug ins on his master fader, then complaining that his soft synths were unplayable. The types of plug ins he was using are not designed for playback, they're specifically designed for the mixing stage after you're finished with composition. There's no OS or DAW change that will fix that.
He talked of overloading a single core in Logic, you can do that in any DAW, simply load plug ins on a track, route that track to an Aux, then load plug ins there, which he also mentioned doing. These are track management 101 things, that you and others haven't addressed at all.

How can you be so sure? Some problems may be due to the way he uses buses and plug-ins, some problems may be due to Logic specific issues (I know it had some management problems in the past but, as I said, I am away from Logic since the launching of Logic Pro X, therefore I don't know what's the current status), some problems may be due to the computer he is using. To know exactly what's happening one would have to examine closely what's his workflow, and the possible mistakes he is doing. Right now, we are mainly guessing, and I don't like guessing.

Changing OS and DAW will not solve his issues, what will help temporarily is a new computer. So in a year or less, his issues will come back, because he's doing things to cause them that a speed bump will only mask for so long.

Maybe so. Again, I am not so sure. But one thing leads to the other, I think. To change OS and DAW he will probably buy a new desktop, and he can assemble a very powerful machine for the price quoted for the iMac ($2500 USD), or maybe just a little more, if he doesn't go for an expensive graphics adapter (which is not needed for music, anyway).

I've specifically given my advice on what DAW I would use in Windows, what CPU I would use, and even suggested to him not to get the Mac Pro, that if he's serious about switching, don't bother with Intel, an AMD machine is way more powerful for the price.

I intentionally left out your mocking to try to be constructive here. I agree with you right now in what concerns AMD. And I also agreed already with you in what concerns REAPER, and for him to start using REAPER and VSTs right now in order to soften the transition.

[Passing Bye]

Actually, the post was mainly addressed to Passing Bye

Why, because I advised him to leave stubborn guy to do whatever he thinks is best for him and find out the hard way that he wasn't right ultimately? You are really lost cause...

So you are advising a guy to change DAW and OS, drop money on new PC, so if guy encounters problems again, are you gonna give him his money back or what?

Guess not, but that's rightly deserved than, by rejecting genuine informed objective advice's and listening to ex-fanatic that have vendetta against same company...

[machinesworking]

Everything he mentioned is due to poor track management and attempting to do things no OS or DAW is capable of. He stated he was using two different room attenuation plug ins on his master fader, then complaining that his soft synths were unplayable. The types of plug ins he was using are not designed for playback, they're specifically designed for the mixing stage after you're finished with composition. There's no OS or DAW change that will fix that.
He talked of overloading a single core in Logic, you can do that in any DAW, simply load plug ins on a track, route that track to an Aux, then load plug ins there, which he also mentioned doing. These are track management 101 things, that you and others haven't addressed at all.

How can you be so sure? Some problems may be due to the way he uses buses and plug-ins, some problems may be due to Logic specific issues (I know it had some management problems in the past but, as I said, I am away from Logic since the launching of Logic Pro X, therefore I don't know what's the current status), some problems may be due to the computer he is using. To know exactly what's happening one would have to examine closely what's his workflow, and the possible mistakes he is doing. Right now, we are mainly guessing, and I don't like guessing.

Because he stated more than once his examples of why Logic was "broken", and all of them are due to his lack of understanding of how to manage CPU in a DAW. You're guessing when you look past what he wrote.

Had he stated things that led me to believe that Logic was broken or OS X, or that he needed a new computer etc. I would come to a different conclusion. This isn't a specifically Logic or Mac OS, or Windows issue, people come to the wrong conclusion trying to fix issues all the time.

The absolute first thing that should happen is to get a grasp on how to allocate CPU in a DAW. After that if the issues are still there, then move on.

[Fabriciom]

Right because it's totally normal to have and empty track selected as to not have a thread kill your projects. Thats basic knowledge in DAW music production.

Can this thread be erased?

Im tired of the fanboys and the clueless know it alls.

[antic604]

I agree with @machinesworking that from the start of this thread it's apparent you don't know a lot about computer technology and DAW optimisation. Nothing bad with this. I'd prefer to be a brilliant musician / producer instead. But perhaps you should more humbly listen to what others say and suggest?

Can this thread be erased?

As an OP you can lock it.

[machinesworking]

Right because it's totally normal to have and empty track selected as to not have a thread kill your projects. Thats basic knowledge in DAW music production.

Can this thread be erased?

Im tired of the fanboys and the clueless know it alls.

I've absolutely said nothing to warrant this from you. Almost everything you've stated as reasons for Logic's issues are basic issues in any DAW and any OS. This is literally the first thing I've seen you post that isn't, (Logic automatically arms selected tracks, but it's in a weird semi armed state), and it's still incomplete information. I'm sorry, but it's that attitude that makes it impossible to help.

FYI, Logic automatically arms selected tracks, taking them out of pre buffering. This would increase CPU use on the track that's selected. This is true in Reaper and DP as well here. Live and Bitwig take a hit up front CPU wise, and do not give CPU back nearly as much to tracks that aren't selected or record armed.

Again, this is basic CPU management, once you understand that, regardless of whether you switch or not, life will be easier.