I’m absolutely impressed with the speed of getting the A7RIII Pixel Shift version to a level where you have a test version for users. I asked about the possibility of getting work done and in 4 days you are there. Leads me to say this about the code that it is reapproachable (new word for software that is easy enough to quickly modify) and that the developers understand what they are doing. This is not standard FOSS but rivals top level pay-for-software.
Well, some parts of RT are quite nice (pixelshift is one of them). Some others… I’ll just say that you can see that there have been many different developers doing many different things at different times and with different goals
I don’t know that, but there are many FOSS projects with excellent code bases (including many of the popular ones around here – e.g. darktable)
If it were not for top quality, Free Software solutions like the Linux kernel, apache, nginx, mySQL, postgres, and tons and tons of other things, we wouldn’t have the internet as we know it, android, macOS, Firefox, Chrome, Roku boxes, many of your camera firmwares, or many many other great pieces of technology.
Thanks! I just played around with this for a while. Here are some thoughts…
I had to add the ARQ file type manually in the preferences to get the file browser to show ARQ files. But at least there was an option to do it…
The motion correction is pretty amazing! Even if you have not tried to optimize parameters for the Sony, it looks great. I really didn’t see any issues at all.
It did take quite a lot of sharpening to get it to look like the Imaging Edge output. So the presumed resolution gains of PS still seem rather small.
I have the Dell 5K monitor (218ppi). To get the image to look the right 1:1 size, I had to use a zoom of 50%. Is the UI applying a 2x fudge factor for my monitor? This has the added disadvantage that I can’t see sharpening effects unless I zoom in to what is effectively 2:1 to me.
A request… It’s really slow to pan around at 1:1. It would be great if RT rendered the whole image at 1:1 and allowed instant panning. I have plenty of memory in my machine–and Lightroom does this.
Anyway, thanks for making the special build so quickly. It looks like it will be easy for RT to support Sony pixel shift and motion correction.
Another gimmick is the possibility to use the median of all demosaiced frames instead of just one demosaiced frame for the parts with motion. You can use that to eliminate things which are at different positions in the frames or to get a long time exposure effect (especially with water).
I tried it with your 2 seconds waterfall image.
Left is using one frame for the parts with motion, right is using the median of 4 frames
@agriggio wouldn’t “.arq” appear only if the options file was deleted? People updating from previous RT versions with an existing options file will not see “.arq”