Sorry but you said a 16 core at FOUR ghz won't beat an 8 core at 5. Now you are saying a 16 at 3 ghz and I agree with that too for sure. So we don't disagree after all.Jim Roseberry wrote: Wed Dec 18, 2019 10:29 pmAmelia70 wrote: Wed Dec 18, 2019 8:51 pm Are there plugin synths on the market today that a 4GHZ processor can not cope with? Is this why single core speed is so important? I never had an issue with kontakt which is the sample engine all our libraries use, and it has it's own multithreading. Really, I am at a total loss as to why anyone thinks I would get better performance with a large 200 track project with an 8 core cpu vs a 32. I just flat out don't believe it if I'm to be completely honest.
FWIW, I've tried to explain why high clock-speed is important.![]()
- Not every process in a DAW can be multi-threaded (spread across multiple cores).
A developer from FLS explained this in detail (months back).
- The lower the latency at which you're working, the more important single core performance.
ie: Monitoring in realtime thru software EFX/processing at a 32-sample ASIO buffer size is not something that lends itself to heavy multi-threading. You can verify this by looking at the load of each core.
- I'm not sure if this has changed recently, but UVI's Falcon wasn't able to use multiple cores.
If it comes down to choosing clock-speed or cores, clock-speed is the single most important factor.
Xeon CPUs often have *significantly* slower clock-speed (but significantly more cores).
If you've ever used one for DAW purposes, they're an expensive performance hit compared to a standard CPU (fewer cores but significantly higher clock-speed).
A CPU with 16 cores running at 3GHz will not outperform a CPU with 8-cores running at 5GHz.
At the risk of repeating, performance increase from adding cores doesn't scale 1:1.
IOW, Quadrupling the number of cores does not quadruple performance.
If you're running at higher latency settings... and using a DAW that has "Hybrid Buffering" (where tracks that are merely playing back are using a *large* playback buffer), that's going to make more efficient use of multiple cores. If you're working at the smallest ASIO buffer size (say 32-samples), that's not going to make efficient use of multiple cores.
You can see this for yourself with Cubase.
If your audio interface allows, set it to a 32-sample ASIO buffer size.
Load a project into Cubase... and note the Audio Performance meter.
Now, switch off the Activate Multi-Processing option... and note the Audio Performance meter.
I'll have some specific figures for the 3970x in the next couple of days.
If it can run all 32 cores at 4.5GHz, I'll be amazed... and the performance will be fantastic.
If it can't run anywhere close to all cores at 4.5GHz, it'll be underwhelming.
Details to follow...
I already explained we ONLY use kontakt when using VI, that's IT. The rest is insert effects and external stuff.. It doesn't matter what the general fastest is for most people, here I was asking about my personal way of working.
Well the low sample buffer thing must be a windows problem.. I know for a fact Logic perfectly multithreads across multiple cores at 32 buffer. I never needed to in PT cause of HDX but using HDX as an interface in logic without access to the DSP makes it an ordinary core audio interface. I am able to get extreme amounts of tracks even on this computer at 32 buffer in logic with those tracks armed for record and you can clearly see it spreads the load evenly. One thing I find curious is that Logic will only fill up what seems to be half the cores on it's performance meter for tracks that are monitor armed, and reserves the others for the high buffer for playback, but it works perfectly.
Maybe I am looking at this all wrong and should be getting a more powerful mac and just using Logic which is cheap and cheerful and I can sell all the HD interfaces and get a nice fast core audio interface.
I already SAID Cubase is problematic, I know this, I have been following what tuff cat says (pls is that his name? I Know it's something like that, forgive if wrong).
Cubase is broken wth multithreading with live armed tracks/asio guard disabled and the manufacturer doesn't care which means it's not suitable for me as I will need to stream large numbers of external inputs at a low buffer. TC says Cubase 10 can only use 6 cores for the low latency tracks, which will not be suitable for us and be a total waste of a high core count cpu. We only work at 64 in PT when playing Kontakt.. it has no bearing on the external monitoring as that's all being done via DSP. I could set it to the highest buffer, and the signals coming in would still be low latency at 48k. it's under 2ms at 48K.
If you like I can take a video of me arming 64 external inputs at 32 buffer in Logic, audio streaming into all of them simultaneously, and putting 2 effects on every track and also creating some reverb and delay aux/sends. Maybe you'll be amazed. I have no idea how PT behaves under Core audio as we use the DSP. Is there no windows DAW that can properly multithread at ultra low buffer? If that's the case then I'm not really interested, cause we need the cores for the eventual mix which will be hundreds of tracks with effects and as I said a heavy amount of IK tape. You have to try and not think in general terms but this specific workflow and if you still think a 5ghz 8 core machine will do what I need, we will continue to go around in circles as it will not, not unless I invest in a DSP solution again to aid.
I guess this is why I created the whole topic, which DAW can multithread properly.. I did mean when at low buffer with incoming signals. That's the most important aspect if I am to give up PT. Now I understand why you say high clock speed matters, cause I was going by what I was able to do in OSX on this old slow mac, and it's not an issue here, well certainly not with logic. I presume there would be windows DAWs that could do the same thing. I am starting to think windows might be the wrong way to go, but in any case, I will still try my friend's mac pro that she bought for her video studio when it arrives, but that's 2 weeks away unfortunately as there is a long ship time on them.
After reading this topic I tried the demo of studio one, and it is useless on MAC at low buffer, so maybe that is one where it's different on Windows? It could only input monitor about 1/4 of the tracks Logic could at the same buffer with same effects. Again I can't compare pro tools as that's using DSP. And yes, it makes sense, if the machine was a modern cpu running at a toasty 5ghz, Studio one would have coped much better. I understand that now.
BUT just to finish off once more.. once all these tracks are recorded to audio and the vi's the same, it becomes a mixing challenge with one of the most demanding plugins on the market over a huge number of tracks..Just to clarify, are you saying the 5ghz 8 core will reign supreme even THEN?
And if so, please explain how.. I am sorry you said you tried to explain but really you were explaining in a way that you expected the person to understand exactly what you meant and have sort of disregarded my own personal experiences with the computer in front of me right now, again and again.
Anyway, if this is all the case (what you say), then the answer to the entire topic is a resounding NO really, isn't it?