I have an Internal NVME and SATA SSD drive.
Would placing cubase projects and running from there be more beneficial in terms of performance/load times? Or does it not matter so much?
Where should i store/run cubase projects- Internal NVME or SATA SSD?
-
- KVRian
- 833 posts since 18 Jun, 2013
-
- KVRAF
- 16804 posts since 8 Mar, 2005 from Utrecht, Holland
In theory NVME has better performance, but I doubt you see much difference on practice for project files and a few audio tracks.
If you are a heavy sample library user, then put these on the NVME drive.
If you want to get to the bottom of it, you can actually measure it. Windows has all the diagnostics tools built in.
If you are a heavy sample library user, then put these on the NVME drive.
If you want to get to the bottom of it, you can actually measure it. Windows has all the diagnostics tools built in.
We are the KVR collective. Resistance is futile. You will be assimilated. 
My MusicCalc is served over https!!
My MusicCalc is served over https!!
-
- KVRian
- Topic Starter
- 833 posts since 18 Jun, 2013
I'm a heavy sample library user like kontakt, omnisphere,etc . Should I store the libraries in nvme and projects in sata ssd then?
-
- KVRAF
- 2140 posts since 16 Jan, 2013 from USA
NVMe. Everything is faster by a lot. Will you notice it subjectively? Barely, but the more stuff you load, the more time you save.
Caching should absolutely be set to the NVMe drive. That will affect DAW performance quite a bit. Not that SATA is that slow mind you, but seeks are about 10 times longer and sustained throughput 4-5 times slower minimum.
Caching should absolutely be set to the NVMe drive. That will affect DAW performance quite a bit. Not that SATA is that slow mind you, but seeks are about 10 times longer and sustained throughput 4-5 times slower minimum.
-
- KVRian
- Topic Starter
- 833 posts since 18 Jun, 2013
So I heard its better to use NVME for sample libraries. So you mean to say it's better for cubase project files to also be on NVME?
-
- KVRian
- Topic Starter
- 833 posts since 18 Jun, 2013
bump
-
Starship Krupa Starship Krupa https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=337746
- KVRist
- 303 posts since 13 Sep, 2014
It's generally considered unnecessary to put DAW project files on the NVME vs. SATA SSD. I see no difference myself.
DAW project files usually consist of instructions that tell the DAW to stream audio from a drive and/or load virtual instrument plug-ins and tell them what notes to play. The instructions themselves take up very little space in the great scheme of things, so they tend to load quickly, even from a spinny drive.
Streaming audio files is similarly low overhead as far as disk access is concerned.
Virtual instrument plug-ins are in charge of loading their own data, which can be a LOT of data in the case of sampled instruments, and they usually pre-load it into RAM rather than streaming it. That's why we want those libraries on the fastest drive possible, with plenty of RAM to use.
Audio data that the DAW is using less so, and the actual project files least of all. In most cases, people want their DAW project files and their associated audio files in the same folder tree, which means putting them on the same drive.
As with so many things, there are exceptions to what I'm saying, which is why I used words like "usually."
So if you're trying to free up space for your samples on your NVME, it's okay to move the DAW projects and their associated audio files (if any) to a SATA SSD. NVME slots are still limited, while SATA ports are plentiful.
DAW project files usually consist of instructions that tell the DAW to stream audio from a drive and/or load virtual instrument plug-ins and tell them what notes to play. The instructions themselves take up very little space in the great scheme of things, so they tend to load quickly, even from a spinny drive.
Streaming audio files is similarly low overhead as far as disk access is concerned.
Virtual instrument plug-ins are in charge of loading their own data, which can be a LOT of data in the case of sampled instruments, and they usually pre-load it into RAM rather than streaming it. That's why we want those libraries on the fastest drive possible, with plenty of RAM to use.
Audio data that the DAW is using less so, and the actual project files least of all. In most cases, people want their DAW project files and their associated audio files in the same folder tree, which means putting them on the same drive.
As with so many things, there are exceptions to what I'm saying, which is why I used words like "usually."
So if you're trying to free up space for your samples on your NVME, it's okay to move the DAW projects and their associated audio files (if any) to a SATA SSD. NVME slots are still limited, while SATA ports are plentiful.
-
- KVRian
- Topic Starter
- 833 posts since 18 Jun, 2013
that's helpful Krupa. Thanks.