#Using fastrawviewer license key
#Using fastrawviewer update

Similar to decoding RAW images 3 threads is both the minimum for maximum performance and more than 3 threads don't seem to improve performance any further. When it comes to decoding embedded JPGs ('Internal JPEG') then FRV can only match Faststone when at least 3 'RAW decode threads' are used. So with 8 'RAW decode threads' you need to set a minimum of 10 'Decode RAW Cache size' to prevent such delays. The latter is also evidenced by both the total measurable CPU load and the load of the FRV main thread which mostly doesn't max out its core.Д¬uriously FRV limits the number of available threads to 'Decode RAW Cache size' -1, so a cache size of 2 (minimum) would limit the number of 'RAW decode threads' to 1.ДЇurthermore FRV needs at least threads 'RAW decode threads' + 2 for 'Decode RAW cache size' to prevent delays from happening every time you change the browsing direction (forwards to backwards and vice versa). FRV with raw files is at least as fast as using Faststone with embedded previews, if not faster.Д«ut: at least 3 'RAW decode threads' are needed for maximum performance and more than 3 threads don't seem to improve performance any further. FRV has no match when it comes to displaying raw files when enough CPU cores/threads are available. NVidia GTX 780 GHz Edition, using default DX9 mode. XnView was slowest overall and IrfanView is mostly matched or outmatched by Faststone, so I leave these two out from here on.Д¬PU is an AMD 1800X running all cores at 3.95 Ghz + 3333-C14 RAM (tight subtimings). I tested this version using NEF, ORF, RW2 and JPG files versus Faststone, Irfanview and XnView (Classic).

#Using fastrawviewer license key

LIcense key (valid till the end of July) If you are still using a release version, you will find the first batch of changes to Preferences and explanations in 'Preview I' here: 14.3 fps for 'repeat forward browsing' (the raw files from the test set are already decoded and put to cache)ДЇor default video mode (Upsample: Bilinear Downsample: Low res previews) 8.8 fps during sequential forward browsing (limits the unpacking speed) i7-7700K CPU at factory frequencies (no over-clocking)ДЇor fastest video mode (Upsample: No Resample Downsampling: None).This second preview is addressing this, but also improves GUI speed somewhat. I hope you can find 'your go to' culling workflow.We knew it, unpacking JPEGs and displaying them is slow.ДЄfter the speed improvements we've made to displaying raw processing JPEGs became disproportionally slow, taking about half of the time (except for cameras that embed low resolution previews, like Sony). anything not sharp focus goes first and then each image gets a closer look.ДЄs in all things different folks do things their own way. I don't tend to do batch selection (I think I must have tried it but don't remember) I normally work through in more than one pass i.e. I can use ctrl + shift and select them one at a time but I feel there must be a way of selecting a batch.Д®xpert no! I was recommended FRV because I found Faststone too slow and IMO clunky. PS I forgot I had posted earlier in the thread :lol:ДЄre you an expert? Just trying it but getting frustrated by selection, I would normally delete 10 pics by selecting pic 1 and then shift selecting pic 10 but that always selects every picture in the folder. Does not cost a lot in the scheme of things ) I also use FastRawViewer, IMO it is fast and powerful tool for checking & culling as well as checking other aspects. I have tried OM Workspace but it is incredibly cumbersome.

Like you I use Faststone for my review process and it still doesn't do OM1 ORFs.

#Using fastrawviewer update

So I may need to buy it if there's not a Windows update soon. I have tried FastRawViewer and it works and does what I need. The only app which can handle the OM-1 ORF files in iOS is Lightroom, for Windows Capture One works as well. Fastpictureviewer codec pack has not been updated for quite a while. No chance so far to get thumbnail previews in windows.