Cary Knoop wrote:Jim Simon wrote:I do see the blue line. I don't know how it works for you and not me (on two separate machines).
Are you using the Windows version? Perhaps it's an OS specific issue?
On what kind of a drive are the cache files located and is this drive shared by the source media or the project database location?
This is a very important consideration - one should cache to a separate fast drive, NOT the same as the source drive. Reading the source while writing & again reading the cache - all on the same drive - might exceed the bandwidth of the source drive. I personally keep my source media on a 4x WD Black RAID 0 drive, but cached media go to a 1TB M.2 NVMe SSD drive.
Having said that, sometimes I also am under impression that not all effects have been baked into the cached media as playback from the M.2 drive is just a tad shy below the nominal fps speed of the project.
I would appreciate it if someone from BMD authoritatively explained which caching scenario is supposed to bake all the color page nodes into the cached media. I *suppose* that when auto-caching, only the node(s) Resolve "feels" need caching will be baked in; however I tried the User mode and cached the output, reasoning this will bake in everything - and yet, with lots of nodes/effects - I still happen to not be able to play back full-speed from the cache.
What makes it even more "mysterious" to me is the fact that the cached media playback speed varies from one Resolve version to another. I had this problem in Beta 8, but in Beta 9 (and final DR 15 release) my cached media speed tends to keep the pace. What gives?
Piotr
AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP3200 | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)