barninga
-
Posts
451 -
Joined
-
Last visited
Posts posted by barninga
-
-
-
1 hour ago, Return said:
I think it should reset to a default brush and let the user decide whether he/she wants to use another brush.
Like said it caught me by surprise sometimes that if I brush on a Monday with a masking brush on a mask to find on Thursday my inpainting brush still uses the masking brush I used Monday and it doesn't seem to work correctly especially since there's no indicator as it would during current session.Exactly what I experimented
-
Just now, Return said:
This has taken me by surprise sometimes, that it uses the last brush even though the program has been closed.
I think it should reset on close.well, from my point of view the relaunch of the program can or cannot reset brush settings, provided that the behaviour is the same for all the tools; in addition I would expect a uniform behaviour for all the settings of the tools, while it looks like for the inpainting brush AF behaves in a way, and for example for the clone tool in a different way.
-
Today I suddenly found that the inpainting tool had its hardness control set at 20% and grayed out. After some investigating, I found that its brush was set to a texturing brush I used in a previous editing session. I chose the basic brush with the inpainting tool selected, and the hardness control became available again. Now, a couple of reflections about that:
1) the inpainting tool seems to remember any setting between sessions, even if affinity photo is quit and restarted. The only setting that is reset to the default for every single image apparently is the choice "current layer / current layer and below". This seems to be inconsistent, also because other tools (i.e.: che clone tool) remember the setting used last time the tool was used. This partial reset approach is confusing.
2) the brush option window that opens clicking "more" does not show the name/category of the brush. It would greatly help to immediately see what brush is active for the active tool, and even more when similar brushes are used time after time.
I hope the two point abowe will be taken into consideration by the developers. Adding other users' experience to this thread could help.
tahnk you for your attention
stefano
-
11 minutes ago, walt.farrell said:
In V2, in general, Hardness cannot be set via the Context Toolbar for most brushes. It is available for basic brushes, but otherwise in most cases it can only be set by editing a brush, in my experience. That may explain what you saw with it being grayed out.
Within the current session, the Brushes panel will show what brush you last used. Outside the current session, Affinity does not know what the brush is.
If you're requesting a change (as you seem to be) rather than asking a question, you need to use the Feedback forum, not the Questions forum, as the planners don't look here in Questions.
hello walt, thank you for your reply.
i tried to edit the brush at first, but the hardness slider was grayed out in the brush features window.
thanks for suggesting the feedback forum, i'll replicate the post there.
stefano
-
Today I suddenly found that the inpainting tool had its hardness control set at 20% and grayed out. After some investigating, I found that its brush was set to a texturing brush I used in a previous editing session. I chose the basic brush with the inpainting tool selected, and the hardness control became available again. Now, a couple of reflections about that:
1) the inpainting tool seems to remember any setting between sessions, even if affinity photo is quit and restarted. The only setting that is reset to the default for every single image apparently is the choice "current layer / current layer and below". This seems to be inconsistent, also because other tools (i.e.: che clone tool) remember the setting used last time the tool was used. This partial reset approach is confusing.
2) the brush option window that opens clicking "more" does not show the name/category of the brush. It would greatly help to immediately see what brush is active for the active tool, and even more when similar brushes are used time after time.
I hope the two point abowe will be taken into consideration by the developers. Adding other users' experience to this thread could help.
tahnk you for your attention
stefano
-
hello @MEB,
three years and a half later the bug seems to be still there, in affinity photo version 2.2 (mac os 11.7.10).
I have a multi-layered file, containing both vector and pixel layers. a group of vector layers has a perspective live filter applied. when i resize the document, that group gets placed in a wrong position; if i press cmd-z to undo the change, the document returns to its original size, but the group is placed in a new, different wrong position.
if i disable the perspective live filter before resizing, the group apparently stays in its correct position, but as soon i re-enable the filter again, the group goes to the same wrong position as before. the only way to avoid this behaviour is to delete the live filter, resize the document and then apply the filter again. Cutting (cmd-x) the filter and pasting it back (cmd-v) after resizing does not work: the group goes to a wrong position anyway.
Below you can find three screenshot that describe the problem: they were taken before resizing, after resizing and after hitting cmd-z. I also uploaded the afphoto file.
thank you for any help.
stefano
-
UPDATE: my problem was related to 32 bit hdr and tone mapping management. Unless @pedro6 's image is 32 bit hdr too, it cannot be the same issue.
-
1 hour ago, NotMyFault said:
Another Option:
- Merge Visible
- Activate Tone Map Persona
- Activate "Clamp to SDR"
- set Tone Compression to 0 - then adjust to taste.
Yet Another Option
- Export to JPEGXL
Next gen Option:
- Add levels or exposure adjustment
- Reduce Exposure by 1 stop (-1)
- merge visible
- Activate Tone Map Persona
- Set Tone Compression and local Contrast to taste
@notmyfault,
I tried the solutions you suggested. the first one simply clipped the rgb values and I got back to the image with a white sky (overexposed).
Exporting to JpegXL is not usable for me, since my DAM cannot handle jpgxl files currently.
the third one did the trick.
I also tried to do the hdr merge from scratch and found that "clamp to sdr" can help in finding whether the chosen compression level is high enough to avoid clipping pixels later. If this is the case, it is possible to lower the exposure of selected areas using overlays before leaving the tonemap persona.
thank you so much!
-
1 hour ago, ,,, said:
You have the Extended Dynamic Range option enabled in the 32-bit Preview panel when the brightest part of the sky looks orange rather than yellow.
That option is enabling the display of R, G or B values that are greater than the range that can be encoded in a JPEG export or a screenshot, which are standard dynamic range formats.
In the case of your HDR sky, all G and B values are not greater than 1.0 (equivalent to 255 in an integer 8 bits per channel image), and so they get exported intact to a standard dynamic range image. Some R values also are not greater than 1.0, and these get exported intact to a SDR image. However many R values are greater than 1.0 and get clipped when exported to a SDR image, hence the diminished redness (a shift from orange to yellow) of the brightest part of the sky in the JPEG export and screenshot
Disable the Extended Dynamic Range option in the 32-bit Preview panel to display only the standard dynamic range that is exportable in a JPEG (or a screenshot).
that was exactly the problem. In the tonemap persona I originally lowered the tone compression value to 40% to get more contrast and this happened to keep some pixels out of the 8 bit boundary. I found that checking and unchecking "clamp to sdr" gives a visual indication of the areas that will be clipped when switching to 8 bits during export.
thank you very much!
-
hi,
I hope I'm not messing things up. The problem @pedro6 describes sounds somehow similar to mine, as in
in my image, it looks like an adjustment layer effect only partially affects the exported image, whereas it is fully visible while editing in Affinity Photo.
My export preview also shows the adjustment as if it were applied only to a smaller portion of the image than it actually is.
I really can't understand what's happening.
-
Hi all,
I've been using AFphoto since its beginnings and it's the first time I have this kind of problem.
The DJI_0452x5.jpg file was exported from Affinity Photo 2. It shows a large yellowish area in the sky around the spot where the sun had just set down.
The weird thing is that while editing the image in Affinity Photo, that area looks orange, just like the sky on its sides: I can't understand why exporting the image, colours change, and they change only in that area.
Some more details about the workflow:
- the orange colour of the sky is yielded by a HSL layer (yellow shift and saturation): the sky originally look all yellowish
- the image comes from an HDR merge of 5 tiff files, done in Affinity Photo
- each tiff image comes from the same DNG raw file, exported to tiff 5 times with 5 different exposure settings, in order to cover a -2...+2 stop range (this step was not done in AFPhoto)
- more than weird (to me): if I take a screenshot of Affinity Photo while editing the afphoto file, the screenshot looks exactly like the exported jpg and has the yellowish area in the middle of the sky, while the same area, in the same moment, is orange in Affinity Photo.
- Affinity Photo 2.0.4 + MacOS Big Sur 11.7.2 on Apple M1 chip
I could not attach the afphoto file, I guess it's too big (220 MB): it can be downloaded through this link:
https://drive.google.com/file/d/16wIC5zlyBDsSE3BK4w6cyHTizeOwUoNd/view?usp=share_link
Thanks a lot in advance for any suggestion.
Stefano
-
still true on macs as today jan 5, 23
-
10 minutes ago, barninga said:
Please I need help, I can't get nik plugins 4 working with affinity photo 1.10.
on a brand new macbook pro with up-to-date big sur, i installed affinity photo 1.10 from the app store and donwnloaded nik plugins 4. I followed the instructions from the tutorial you linked (thank you!). In detail:
1) created a Nik Collection folder in Applications
2) launched the installer
3) accepted the default /Applications/Nik Collection folder
4) clicked on + and selected the /Applications/Nik Collection folder as host
5) got the fake photoshop enrtry in the applications list and continued
6) at the end of the installation, I had the standalone programs and a DxO folder in the /Applications/Nik Collection folder; the /applications/Nik Collection/DxO folder contains the plugins
7) launched one of the standalone programs and registered my license
8 )opened affinity photo, then preferences => photoshop plugins
9) in the plugins folders I selected the DxO subfolder
10) then selected authorise globally, without selecting any folder: Now I have "/" in the support folders list -- like with previous versions of affinity and nik, but differently from the screenshot in the tutorial, where the DxO subfolder is listed two times (weird)
11) checked "allow unknown plugins"
12) closed the preferences panel and restarted Affinity PhotoWhen I load a jpg, select the pixel layer (the only one I have) and go to "Filters=>Plugins=>Nik Collection=>any plugin" nothing happens.
However, when I exit affinity, it asks me to save the image, as if it had been modified.I can't figure out what I am doing wrong.
I also repeated the affinity configuration process selecting the Nik Collection as plugins folder (instead of DxO), with no result
I also tried manually selecting /Applications/Nik Collection/DxO as support folder, but this way color efex and analog efex are no more listed in the plugins menu (and the other plugins do not start as well)Any help will be deeply appreciated.
Stefano
well, in another thread I found a post by @MEB where he suggests to improve compatibilty by running Affinity Photo through Rosetta Emulation
I tried just now and it apparently works, so I suppose that those of you who did not have my problem are running a pre-M1 mac.
Just to spread the word.
I opened a ticket to DxO but got no answer yet.
-
On 6/8/2021 at 4:22 PM, MEB said:
Hi @artofmtl,
Go to the Applications folder, right-click the Affinity Photo app, select Get Info then tick Open Using Rosetta in the General section to force Affinity Photo to run as an Intel application instead (to ensure compatibility with photoshop plugins). This should make it work. If not can you post a screenshot of the Photoshop Plugins panel in Affinity Photo Preferences please? Thank you.Nik Collection 4 only supports Apple M1 chips via Rosetta 2 emulation.
Hi MEB,
I just installed affinity 1.10 and nik 4 on a brand new macbook pro with big sur (updated). When i select any nik plugin from the filters menu, nothing happens, they just don't start. I tried the "open with rosetta" trick and the apparently launch and work correctly. more than 2 months have passed since nik 4 was released. Do youi have any feedback from dxo?
thank you very much
stefano
-
On 6/2/2021 at 6:17 PM, MarvinR said:
Nik Collection 4 was released today (June 2, 2021) and the install procedure has changed. I found the steps at the following URL:
https://help-nikcollection4.dxo.com/install_activate
I hope this helps someone avoid the frustration getting the Nik Collection 4 installed to Affinity Photo. I was fouled up because I tried to follow the steps for Nik 2.5 and 3.0. However, the new release is installed for Affinity Photo differently.
Edit: By the way did a quick test and Nik Viveza worked fine.
Peace
Please I need help, I can't get nik plugins 4 working with affinity photo 1.10.
on a brand new macbook pro with up-to-date big sur, i installed affinity photo 1.10 from the app store and donwnloaded nik plugins 4. I followed the instructions from the tutorial you linked (thank you!). In detail:
1) created a Nik Collection folder in Applications
2) launched the installer
3) accepted the default /Applications/Nik Collection folder
4) clicked on + and selected the /Applications/Nik Collection folder as host
5) got the fake photoshop enrtry in the applications list and continued
6) at the end of the installation, I had the standalone programs and a DxO folder in the /Applications/Nik Collection folder; the /applications/Nik Collection/DxO folder contains the plugins
7) launched one of the standalone programs and registered my license
8 )opened affinity photo, then preferences => photoshop plugins
9) in the plugins folders I selected the DxO subfolder
10) then selected authorise globally, without selecting any folder: Now I have "/" in the support folders list -- like with previous versions of affinity and nik, but differently from the screenshot in the tutorial, where the DxO subfolder is listed two times (weird)
11) checked "allow unknown plugins"
12) closed the preferences panel and restarted Affinity PhotoWhen I load a jpg, select the pixel layer (the only one I have) and go to "Filters=>Plugins=>Nik Collection=>any plugin" nothing happens.
However, when I exit affinity, it asks me to save the image, as if it had been modified.I can't figure out what I am doing wrong.
I also repeated the affinity configuration process selecting the Nik Collection as plugins folder (instead of DxO), with no result
I also tried manually selecting /Applications/Nik Collection/DxO as support folder, but this way color efex and analog efex are no more listed in the plugins menu (and the other plugins do not start as well)Any help will be deeply appreciated.
Stefano
-
@R C-R it's not a priority for me either.
I did not trigger serius bugs in AP 1.7.0 yet.
Apparently, they have solved a nasty bug with the clone tool that produced artifacts when the destination area overlapped the source area.
Apparently, also a bug that caused upper pixel layers to be misplaced when there was a live perspective layer under them has been smashed down.
the annoyance that causes macros not to always start when clicked in the library is still there, though. it's just an annoyance anyway.
after updating, my upper toolbar was reset to default, and the studio too had some unwanted changes. nothing so seroius.
it still lacks a haze removal live filter.
I did not tried whether masks can be dodged and burned; the new HSL tool looks more prowerful.
-
On 6/15/2019 at 10:41 AM, R C-R said:
The Rotate button on the context toolbar in Affinity Photo 1.7 rotates the crop box, not the image.
yes that's true, thank you for pointing it out.
but -if i don't fail- there's a difference between rotating the crop box and having crop ratios and their reciprocals in the ratios list: in 1.6.x, when you selected the reciprocal of the current ratio, the crop box was limited to the image boundaries, while in 1.7 it's not, and this means you have to resize it most of the times.
having the reciprocal of any ratio just one click away is really useful, but I don't think this conflicts with the capability to add reciprocals to the list: both features together would enable users to go the way they find more suitable to their need.
-
thank you all for the clues
mac os 10.12.6
AP 1.7
I load an image, select the crop tool, select "custom ratio", input a value for w&h ==> "create preset" in the hamburger menu is still grayed out
apparently, a new ratio can be created only as absolute dimensions, which is not that useful
-
hello all,
in AP 1.7 I can't find a way to add custom presets to the list. in 1.6 version one cold set a new ratio and then add it to the list, givin it a name. in 1.7 the "create preset" item in the drop-down menu of the list is always grayed and the preset manager tool only has a button for adding a category. what am i missing?
thank you
-
@jkehoe, the #7 shows a way to mask/unmask an effect in order to apply it only to certain areas of the image. in AP, any effect layer is also a mask. if you select an effect layer and paint black on it, the effect disappears where you just painted. if you paint white over the black area, the effect reappears.
the exercise instruct to add a hsl layer, then invert it. inverting an effect layer actually means inverting its mask. when you add an effect layer, its mask is white by default: this means the effect is applied to the whole image. if you invert it, its mask becomes black and the effect is not applied anymore. in the exercise, you set the paintbrush to white, and the paint over a specified areas after selecting the hsl layer. this way, you create a white "hole" in its mask, which the effect becomes visible again through.
-
a dedicated graduated nd filter would be an interesting plus, ihmo. easy to use, but limited to its scope.
the ability to create graduated filters of any kind is obviously more powerful.
however, the fact that a gradient affects a mask destructively (as far as i could understand by experimenting) and you need to use a vector shape as a clipping mask to apply a non destructive gradient sounds like a bug to me, or at least like a flaw in AP's mask implementation (it's not the only one; i'd add the inability to dodge and burn in masks).
-
i never used that program, so i cannot make comparisons. however i used other programs and at the beginning i found a bit hard to learn AP's logic. now i'm happy with it.
-
you can apply a gradient mask to adjustment layer: just use the gradient tool on the adjustment layer.
afaik, this technique will blend the gradient into the mask permanently. if you'd like to have a non-destructive gradient, you can use a shape (usually a rectangle) as a vector mask: apply a gradient to the shape and set one of its endpoints' opacity to 0.
Severe problem with PDF export
in V1 Bugs found on macOS
Posted
well it looks like the bug is still there in v2.4: if I export an image to pdf and untick the jpeg compression checkbox, i get a white stripe on top of the exported pdf file that "covers" the corresponding portion of the image. If i tick the jpeg compression box the image is exported right: no whit stripe whatsoever.