![]() ![]() But as it's totally focused on audio, I think the results are generalizable and applicable for many.Īnd here's the setup in Cubase for most tests This maybe a bit more powerful than many of the computers in use here. Windows 10 professional, no tweaks other than Ultimate Performance.No other disturbing software (no games and ****.).Computer from Scan audio, setup for DAW use.AMD Ryzen 3900X 12 core CPU, no overclocking.As long as it is a good quality 7200 RPM disk (look for WD Caviar Black, 1TB or less).Now comes the meat and potatoes of this thread: how Cubase works. What you should do is to install another internal drive and use it only for cubase projects. My second suggestion, since you are forcing your disk to work harder by keeping all your Cubase stuff on a single drive (OS, plugins, projects, samples).Even if you have different partitions, it's still one disk. I doubt RAM is the problem, because your OS and Cubase are 64bit and you have 8GB installed - not to mention Cubase streams some content from disk instead of loading the entire project into RAM. See how Cubase runs with HT and SS off, maybe your current setting is causing problems. Ĭheck if you have hyperthreading and Speedstep on. I think it is unrelated to the disk cache that every hard disk has, but to be safe you should go to In Device Manager. I believe the "disk cache" that cubase is referring to is the location it stores track freezes and other recorded material before dumping it in the project folder. I'm almost at the end of the road here and I can't see the light at all.Įdit 1 for listing the computer specs in bullet form If anybody has people they know in the area that we can pay (assuming it's within our budget and they are verifiable) to come take a look at what is going on, that's one thing.If not, I could upload the project for someone to review this situation over the internet-maybe just to see if this project causes problems on another system. I have another project, started at the same time as this one, with less recorded but a bunch of edits, and that project runs just fine. Should I endure the bad playback and just keep completing and freezing edits so that they are not processed in real-time? Are all of these time-shifted instances of the same referenced file(s) the problem? 3-I have edits (reverse, time-shifts, cross-fades) that are all still being processed in real-time. I had not completed cross-fading->bouncing selections->deleting unused files from pool, and I kept recording new tracks. ![]() Here are things that I believe could be the cause: 1-Project is set to 96khz, 32-bit WAV 2-I have large wav recordings cut and pasted to adjust single note hits here-and-there. I've exported the drums already so that I can disable all of the individual drum tracks with inserts and sends. I've removed unused files through the pool. ASIO usage stays around 50% while the disk cache overload meter is at a constant spike. ![]() This project, I know it's huge already but I feel like something fixable is causing the cache overload. WD VelociRaptor 10000RPM 64 MB Cache Hard DriveĢ other HDD, nothing pertinent on them (backups, program update files, etc.) Windows 7 圆4 SP1 installed with AHCI enabledĭecent Video Card (1 GB RAM, PCI x16, etc.) I seem to have a single project that I have screwed up in some way that no matter what I do I have a constant Disk Cache Overload and playback is heavily affected. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |