Add a Dynamic RAM preview for I/O selections.

Add a Dynamic RAM preview for I/O selections / the selected clip on Color page.

I think Cashing and Render In Place sometimes totally unnecessary because it saves a file that you won't even use. In some cases a Dynamic RAM preview would be nice to see what you do in Real time as an example, while no files are saved to the SSD/HDD at all. Yes, this would need more RAM but the user could select how much can be used from it for this kind of preview. In Vegas Pro this is already there.

it saves a file that you won't even use.

Well, you're using it to ease playback.

With this idea, you'd essentially have to rebuild the preview every time you re-open the project, or if it got flushed because the RAM was needed for other things.

And if you didn't have enough RAM installed to hold the preview, you're back to using Cache anyway. (And most everyone has more storage than RAM available.)

I don't think this is a very good idea.

it saves a file that you won't even use.

Well, you're using it to ease playback.

With this idea, you'd essentially have to rebuild the preview every time you re-open the project, or if it got flushed because the RAM was needed for other things.

And if you didn't have enough RAM installed to hold the preview, you're back to using Cache anyway. (And most everyone has more storage than RAM available.)

I don't think this is a very good idea.

This is one of the BEST ideas ever!

I don't want to replace Redner In Place or Optimized media features. I would use dynamic RAM >>>preview<<< as a >plus< feature during the process of grading, only to >preview< the changes in real time >during grading.<
Sometimes I would check like 80 times how a grade looks on a shot during grading and I don't want to save the file for each preview.

If the user doesn't have enough RAM the program previews only a sorter part of the clip. Most who do heavy grading have more than 64 GB RAM.

I don't think it's necessary to save every single PREVIEW during grading to your SSD. This amazing feature would help at seeing your work when you grade without needing 16 TB to store versions that you will never even see again.

With this idea, you'd essentially have to rebuild the preview every time you re-open the project, or if it got flushed because the RAM was needed for other things.

This is exactly the reason for RAM preview. To hold a random piece that does not need to be held onto due to it being just a momentary preview that most probably also gets invalidated soon. User can get more RAM if one runs out of it. Or can maybe get less, as disk caching everything is a way forward so paging the RAM should be good too, slow and steady.

So.... clearly this is a Vegas Pro feature that the OP would like to see in Resolve.

IF it could be implemented properly, that would be OK, but if you look at the history of this feature in Vegas, then the developers may want to run very, very far away!

Barely any faster than renders to disk, inaccurate previews, very short previews, alpha compositing errors, crashes both when used and often suspected in general use (issue seems to be that it messes with RAM allocation.) In the end it has never been fixed, nor made to be especially useful IMO.

Personally, I would prefer that Resolve to stay as it is and not include the user in deciding how to allocate RAM.

Mistika had the same strategy (or similar), in broad strokes:

1) you hit play, the machine start to render the frame and place in the ram in a FIFO configuration and play out of the FIFO to the Decklink.
2) let's assume you can render the frame at half of the time allotted, that means you can render 2 frames per frame, filling the FIFO RAM with the xtra frames creating dynamic buffering.
3) once the buffer is full you render as fast as you are emptying the FIFO bucket. (maintaining the realtime)
4) if you are slower than real-time in rendering, you play from the FIFO the extra frames to maintain realtime
5) either you empty the FIFO and you stutter, or you pass the hump and restart to fill the FIFO.

now, while this can work, you hit the RAM and the BUS one extra time and in stereo or with large files (4k) it can be a bottleneck.

So.... clearly this is a Vegas Pro feature that the OP would like to see in Resolve.

Em, ram preview exists in many softwares...

now, while this can work, you hit the RAM and the BUS one extra time and in stereo or with large files (4k) it can be a bottleneck.

Maybe this would work without becoming a bottleneck with 128 GB+ RAM.

Vegas was terrible at hardware acceleration and stability, this is very true, but had amazing great features I still miss.