glootech

I have OpenCL acceleration on. However under that toggle it says Intel(R) HD Graphics 530. I've just installed 466.27 driver (the newest one) and the problem persists. I'm also using Windows Home compilation 19042.928 (I'm on the release preview ring).

I'm using different blending modes (mostly soft light/screen) with gaussian blur effect over them. The image is rendered and exported incorrectly - some of the image is too light (or straight white), as you can see on the attached example. The same happens when I don't use layer effects but instead use filter (or live filter). This is not visible when the entire photo fits on screen (you need to either zoom in or export to see the result). Depending on gaussian blur settings you need to zoom in a little (when using 100px) or a lot (when using just a small radius), but the problem is still visible on the exported image. I'm using the GPU rendering on a mobile Nvidia Geforce 950M card. The problem persists both in the newest stable version 1.9.2.1035 and beta 1.9.4.1048. Attached is the afphoto and jpg files so you can see the bug. I've tested it on multiple photos and the bug is there. Can anyone confirm they can see the bug when they export the afphoto file I've attached? P4280685.afphoto

I can confirm that sometimes when using sliders the whole UI becomes unresponsive (to the point that standard window decorations start to show). It usually happens not long after launch and gets better over time.

Hi, Using the newest beta and encountered two bugs so far: When I go into tone mapping and create new overlay (let's say a gradient), the tone mappping controls are greyed out. However, you can still tick/untick the controls and use the sliders (however they don't work). And the second one - some time ago I posted that dodge and burn brushes don't work as intended. They didn't take into account the lightness of the area when choosing shadows/middletones/highlights, instead the effect was applied more or less (but the entire brush area was affected - everything just gets lighter or darker depending on the option you choose). It was fixed in a previous release, but I think it's back in the current beta.

Can anyone please confirm that when using dodge and burn tools, when I select the tonal range it should allow me to specifically target highlights/midtones/shadows on the source layer? If so, then it seems that it doesn't work at all - instead when choosing highlights, the dodge tool works with more intensity, but ignores the tonal range setting I chose. Can anyone confirm this behaviour? I'm really confused and when watching tutorials it seems that it should work in a very different way.

Hi, More than a year later, the problem is still there. If someone is looking for a workaround solution then I can provide one: After developing the RAW I use selective colour adjustment layer. Then I make the following changes in Yellows: * Yellow: -35% * Magenta: +65% With this adjustment layer the colours look a lot more similar to the ones in Olympus Viewer 3. Of course you can tweak the values as per your preference. Would love to see it fixed in the RAW engine.