Separate drive for render cache files...

Just dawned on me - as I wait for my timeline to re render again, upon startup - that I have the render cache files on the same drive as the source media. It's an M.2 drive right on the mobo, so it should be the fastest drive in the box (and it's already not the system drive, fwiw), but would I benefit at all from choosing a separate SSD for the render cache?

I know in the audio world it's generally recommended that you don't read/write to the same drive via separate processes simultaneously, so I figure that might apply here as well.

Are you guys using a separate drive for render cache?

I'm hard pressed to believe as SSD would speed things up, given that they're generally 4x slower than M.2 drives.

On a separate subject, are you able to get real time playback with those Cache files? I just can't make it work.

I'm hard pressed to believe as SSD would speed things up, given that they're generally 4x slower than M.2 drives.

On a separate subject, are you able to get real time playback with those Cache files? I just can't make it work.

Yeah, I haven't benchmarked the various drives in the box for a while, but the SSDs I have in there are 850 Pros, so they should be fine. I'm just curious whether or not having the render cache on a separate drive from the source files would matter. I'll try it and see what happens.

I might try deleting the optimized media and re optimizing with Cineform, to see if there's a difference. I had been using DNxHR LB, on the recommendation of a friend.

As for real time playback, it works fine, once the rendering is done. Problem is, it seems as though every time I sneeze, a portion of the timeline has to be re-rendered. It also re-renders entirely now, every time I start up the application, but that may be because I have certain layers (film grain, light burn, etc.) that run the whole way across the 10 minute timeline.

I'm trying to exhaust every possibility that this is just operator error, as I'm relatively new to the program (having come from Adobe land), or I just haven't found the right combo of render settings yet.



I have to say though - even with the quirks and fits - this is a pretty remarkable program, and they've done quite a lot in a short amount of time, in the effort to turn Resolve into a legit NLE.

Terry;
that is not normal behavior, both caches and optimised media should persist between re-starts

first thought is the target drive for caches and optmised media changeing mapping between restarts, not likely if it's mounted internaly tho

i normaly keep cam orig media on a NAS and render caches / optmised media to a local DAS, in my case mutiple spinning disks attached via SAS to a raid controler

i rarely -to- never have issues with caches/ optmised media not persisting between restarts

i rarely -to- never have issues with caches/ optmised media not persisting between restarts

Well, now I'm jealous.

I'm going to try putting the source media on one of the other SSDs and working from a render cache on the M.2. See if that changes anything.

While I'm at it - does anyone know if there's a way to tell (visually or otherwise) what source media has had optimized versions made of it and what hasn't? I don't see any indicators anywhere after generating optimized media.

You can add that column to the list view at any time and move it close to the clip name if needed.
Or make a smart bin.

As for real time playback, it works fine, once the rendering is done.

Damn, I was hoping my issue was a broad based bug. Now I don't know what to do.