Pixel shift options in menu RT are not translated into Polish language
@Marek you can help with that once the English strings in the pixelshift branch are finalized: Localization - How To Translate RawTherapee and RawPedia
I do like the function to increase the size of the regions, even though there isn’t much difference between 5x5 and 7x7 the increased size does close up some of the gaps that otherwise are left uncorrected. But even bigger size would be nice if it’s doable.
The red/blue functions do pick up lots of faint checker patterns but also have a habit of picking up the details that you would like to preserve, that is why a lower sensitivity (to the keep the details) and larger blobs to cover the problem areas more effectively is nice, at least when working with the current PS pictures I have right now.
We are currently working hard on some new methods to reduce the number of false motion detections while increasing the number of true motion detections. As soon as the the stuff is worth to be pushed to
pixelshift branch I will do that…
Sounds good. In the mean time I can share yet another pixel shifted image. Nothing extraordinary in any way but it does involve a lot of motions. The car closest to the camera like to leave some artefacts, there is also some on the back of the people to the right in the picture that is hard to remove without removing solid details.
There are some nice details that can be found on the houses in the distance that one like to preserve, for instance look under the black roof for some ornaments on the wall.
Gimbal, thanks for providing a new example file. We really need as many of them as possible.
I had a look at your file using latest (unofficial) development version. The car artifacts are solved and the detail in background is also preserved much better with that version. The artifacts on the back of the people is better but still not good. I will have a look at that now…
Edit: here’s a screen shot of the people artifacts
this artifact is removed by enabling nongreenamaze.
Hi Vitalis, it’s not completely removed. But I have to admit, that I lost the overview what’s in official and non official rt pixelshift test versions…
Vitalis, ok, replicated your settings. But with this settings it fails on this:
It would be nice to be able to apply different settings for various regions. But I feel that this is too complicated to implement.
Vitalis, this settings almost solve all issues for Gimbal’s file
today I had a walk to ravines and made many photos of various kind, involving water, wind in branches, living things etc. Most are in high and low ISO. Hope they will be useful.
seems that the current code easily interprets all the ravine files.
Vitalis, it’s better than before but there’s still some room for improvements.
Today I implemented a hole fill algorithm for the
3x3 new motion mask. I’ll push probably at the weekend.
RT great support of the PS function most certainly will have a lot of people rethink the usability of the PS. Even though the “motion correction” function is there both in camera (for jpeg only) and in the bundled software it isn’t working that great. So in reality PS was usable only for static scenes or you had to do a lot of masking by hand with varying result. This kind of changes things, a lot.
Hi, sorry for not updating status of pixelshift last 12 days. Currently there are some changes (improvements) on hold in pixelshift branch but because rt5 is around the corner we didn’t find the time to officialize them.
In new RT 5 pixel-shift will officialy supported ?