Will my PC run the V Collection?

I want to buy the V collection X bundle during Black Friday, but in looking at the requirements on the Arturia site, it says:

  • Win 10+ (64bit)
  • 4 GB RAM
  • 4 cores CPU, 3.4 GHz (4.0 GHz Turbo-boost)
  • 32GB free hard disk space (V Collection X Bundle)

My PC is a newer HP laptop running Windows 11 (64 bit), AMD Ryzen 5 7530U processor, 2GHz (Up to Turbo Boost 4.5 GHz, 6 cores, 12 threads), 32 GB RAM (DDR4 SDRAM), AMD Radeon R5 (Graphics Processor).

I meet the minimums except for the clock speed (2 Ghz v. 3.4 Ghz, but with turbo boost, I’m over 4). Is this likely to be a problem? Thanks.

Have your laptop connected to AC power, and running in High Performance mode (Windows setting), then take a look in Task Manager and see what speed it runs at.

I believe you should see it hit 4.5GHz when you load and run apps, so it should be fine.

You could download some Arturia VSTs to try them out first before buying the whole V Collection. Pigments can be quite demanding so perhaps try that.

Thanks. I contacted Arturia support with the same question and they suggested the same thing - downloading demos to test it out, so that makes a lot of sense.

1 Like

Yeah. Give it/them a try. I’d be interested to see how it goes, actually.

I downloaded Wurli and Analog Lab and ran them both together in FL Studio for about 20 minutes. I had no problems. According to task manager, CPU stayed in the 20-25% range, so I think my PC can handle the V Collection.

2 Likes

Hey @sxian

Great news!
And welcome to The Sound Explorers Forum too!

You might come unstuck when you’re using some of the more CPU-heavy Arturia VSTs inside a DAW, which is already consuming computer resources itself and is playing other VSTs at the same time. If that’s the case, use whatever option your DAW has to ‘freeze’ the tracks in your project which you have already finished. Freezing the tracks (or whatever your particular DAW calls it) renders them as audio inside your session. Playing rendered audio is about a billion times less resource-intensive than rendering the VSTs live.