#.

1 messages · Page 1 of 1 (latest)

safe stump
#

Do you need single thread high power or multithreaded?

#

No gpu needed for that price just cpu?

#

13900K would be a nice bet for one of the fastest single threaded cpu.

vapid obsidian
#

what exactly is your workload? what software, what OS?

rotund hinge
#

Gaming or other things?

safe stump
#

@sacred surge ? 🙂

#

well price wise best one would be 13900K if you want to go for high single CPU and money is no issue.

vapid obsidian
#

even a crazy project in FL studio shouldn't require a top shelf CPU

#

or maybe you've got the 100% CPU usage bug?

vapid obsidian
#

I guess it's like compiling large codebases - once a project gets over a particular level of complexity, no amount of desktop computing power is going to bring the compilation time back to the happy place

#

you could throw as many cores as possible at it, like using threadripper

#

a 13900k isn't too far away from a 5600x in the grand scheme of things - neither have the compute power of server tier multicore

#

you should ask FL studio directly, given you're about to throw $2k at the problem

#

ask them if they would recommend fewer but higher clocked cores (13900k) or more cores at a slightly lower clock (threadripper or 5950x/7950x or something else high core count)

#

5600x -> 13900k may only halve your project time, at best

tidal flower
#

As an audio engineer who's worked on similarly-sized projects, I can promise that a best-in-class CPU is not going to give you the boost in performance you're expecting. Almost always it's a RAM limitation, and given enough ram, it's often a software bottleneck, not CPU.

#

To answer your question, it would be a 13900k. Technically more stable than ryzen, DAWs are not well-multithreaded so raw clock speed is preferable to core count. But, $2k is not enough to produce a balanced CPU/GPU build, if you're looking to do any video rendering or gaming while keeping up with that i9 CPU I see you already have a 3090, disregard this bit

You're better off dumping money into more RAM before a fancy CPU.

#

My only advice is to avoid corsair vengeance. Lots of stability issues. I tend to buy G.skill
As for DDR5 speeds, I don't think there's a surefire answer to what speed is best for you. Really just depends on how much you want to spend

topaz orchid
#

I was going to comment earlier, but didn't know enough to weigh in on the CPU side of things. Will 2nd Sanic on the RAM advice though, you could find significant improvement just doubling your current DDR4 sticks for 128GB total.
Sounds ridiculous, but I know DAWs can be that hungry for memory

tidal flower
#

Whoever told you that got it like 50% right
Using 4 sticks is often more unstable/unreliable rather than 2 sticks, but that's not specific to AMD. It happens on Intel too. Sometimes they work fine, but not with XMP (i.e. full advertised clock speed) other times they don't work at all.
Lots of folks (myself included) use 4 sticks without issue. It's a toss-up really.

#

128GB would be ideal. I'd buy two pairs of 2x32 of identical sticks. If all four work fine, then stick with it. Otherwise just return one of the pairs.

#

like keep my old sticks in and add new ones in
No, you can't use 8 sticks on consumer platforms, and shouldn't mix ram if you want good stability

#

i dont know many people who would as massive projects that i use lol
It sounds pretty normal actually, at least in the professional scene. Our projects often exceeded 30 gigs
So you're saying you've done everything mentioned in that article, including cranking up the buffer size?

#

Yeah that ram looks decent

#

I guarantee you 80% of your performance issues come down to the software config & inherent bottlenecks to FL studio

#

This would be ideal

#

The issues you're describing just sound like your buffer size is way too small

#

You're not gaming so it really, really doesn't matter. Technically, the higher speed (e.g. 6400) and lower the latency (e.g. 28) the better. But, the higher speed sticks will also have a higher latency, but will still have a faster round-trip clock. Ignore the PCS number

#

Again, you really shouldn't consider any of these purchases until you've confirmed that your buffer size wasn't too small.
Also, you might wanna look into guides about optimizing your workspace. Half the battle of composing well in a DAW is to arrange your project efficiently.

#

The only time you should be using hundreds of tracks is if you're scoring a feature

#

The prices will always fall down and in retrospect it'll always cost you more, this is guaranteed

#

Are you not using buses to consolidate those plugins?

#

You will have to replace everything

#

You will have to replace everything

#

Nothing except your GPU, storage, and (possibly) your power supply can transfer over

#

For build questions, ask #build-a-pc
Until you're in front of your computer and look into FL's settings, I can't help you

#

To reiterate, you need to focus on optimizing your project flow before anything else

tidal flower
#

Yeah that's fair

vapid obsidian
#

you're likely experiencing the 100% CPU bug, or some other optimisation problem - contact FL studio

#

they can also tell you whether more RAM will even help

sacred surge
#

.

tidal flower
#

Huh?

vapid obsidian
#

he didn't like any of the advice he'd asked for, in any of the places he asked, and ended up going his own way anyway

#

and is now deleting all reference to the original problem