Suggestion: Implementation of a "SuperCache"
Isn't it annoying when you compare images that C1 always needs to re-render the image? this only takes one second, but sometimes I want to switch back-forth images very fast to see the differences. sometimes I have 10 shots with the same content, the differences are subtle but they are there!
Besides, most of us professional users have big workstations. I for example are proud to own a 48 GB Ram Workstation. Sadly, 90% of the memory is never used in C1!
Lets implement a SuperCache!
C1 detects the amount of free Ram and uses everything except 10% for caching rendered images. this means I have 40 GB of unused memory. Of course thats special, but I am sure many users have 8-16 GB machines. Imagine just 4 GB of a SuperCache and you can lightning-fast switch back-forth the images!
If something like that is already implemented, please tell me. I did not find any method so far to compare photos in full-screen mode fast. Selecting 10 photos and comparing them in a little grid is no option!
Besides, most of us professional users have big workstations. I for example are proud to own a 48 GB Ram Workstation. Sadly, 90% of the memory is never used in C1!
Lets implement a SuperCache!
C1 detects the amount of free Ram and uses everything except 10% for caching rendered images. this means I have 40 GB of unused memory. Of course thats special, but I am sure many users have 8-16 GB machines. Imagine just 4 GB of a SuperCache and you can lightning-fast switch back-forth the images!
If something like that is already implemented, please tell me. I did not find any method so far to compare photos in full-screen mode fast. Selecting 10 photos and comparing them in a little grid is no option!
0
-
There is software available to allow you to create a virtual hard drive in RAM. How you would use it with C1 I am not sure as you may have to copy the current folder to it. Priced at about $30 but I have no experience of it.
Bear in mind that however it is achieved a system crash/ power glitch would wipe ALL work and data on that drive or in that RAM based cache.
I used something similar many years ago before fast large hard disks were available or much data was on floppies. Really floppy disks - none of those fancy hard plastic shells!
Personally I will settle for a little slower and more robust. But then a CENTRAL cache on a solid state disk would be good especially if working on data over a network.0 -
Thats not what I mean. The bottleneck is not the IO but the missing cache version. Compare it with Adobe Lightroom for example. It renders the whole image when you zoom to pixel-to-pixel view (which takes a few seconds) but then you can pan around ultra fast without the annoying focussing process C1 always has to make. In fact, C1 always has to convert the disk data to screen data. This process is usually fast, but by caching the screen data directly, it would be even faster. (Of course this needs more ram, but who hasn't?) 0
投稿コメントは受け付けていません。
コメント
2件のコメント