SloCan

@MEBObrigado! If it is a bug that can be remedied, that would be great! In the meantime, at least I have carl123's workaround.

@firstdefence : rasterizing is definitely not the way to go if one wants to still be able to change the fill color on the fly. @carl123: I tested your suggestion by adding the adjustment to the group instead of to the fill layer (or separate mask), and got it to work. If I've understood this all correctly with the little amount of testing I did, this means that I'll need a new group for every fill layer I add where I need an adjustment applied to it. This also means that when you already have a number of layers grouped into a certain category you're focusing on (like for editing skin or hair, for example), you will now have groups within groups. It may be a bit convoluted, and I have no idea how it affects file size or performance in the long run, but if that's the only way, then that's the only way. It works, and that's what matters. At least this is one way to achieve what I wanted to, which is, specifically, to be able to change a fill layer color's saturation accurately and on the fly using a slider or directly entering the percentage in HSL, and also to still be able to change the fill layer color on the fly if required. It would be great if it was a one step process to quickly allow the adjustment to affect the fill layer directly and nothing else like it can be done in PS, or like it can be done with layers other than fill layers in AP (if I'm not mistaken). Thanks for the suggestions and the help. Much appreciated.

For me, nested/clipped adjustments added to (Color) Fill layers don't work, whereas nested/clipped adjustments added to pixel layers do. If I pull the adjustment layer out of the nested/clipped position and place it over the (Color) Fill layer, it works, but affects the whole document below it, which is not desirable. I just don't get it. Either this is something I'm not doing correctly, or I'm missing steps in the process, or it's in AP by design (I hope not), or it's a bug. So what gives here?

This is an old thread, but rather than creating a new one, I thought I'd revive it and add my: +1 My eyesight isn't what it used to be, so having the option to change the thumbnail sizes would be great. Perhaps even the icons on the toolbar as well. I use the PC version of AP.

My request is to either move the Develop persona icon to the first or to the second position and/or allow persona icons to be customized like the other toolbar icons. Right now, you can only (customize) move the entire persona toolbar in as a default group, unlike the other groups where you can do the entire group or each component individually. My logic is that process-wise, the Develop persona would be first, then the Photo persona for editing, or vice versa. After that, the Tone Mapping, Liquify, or any future persona, then Export persona in the last slot (as it already is), since it would most likely be the last thing someone would do in a process. What's happening to me is that when I want to use the Develop persona, I find that I immediately go the the Liquify icon on the toolbar, stumble a bit, stare at or hover over the icons to see which is which (my eyesight isn't what it used to be), then move to the Develop persona. I never use Liquify and can't see the importance of it to be lying in the second slot instead of the Develop persona. I would imagine that Develop is used more often than Liquify, but that's just my guess of course, so who knows. Having said that, at the very least, the ability to customize the Persona order would be a benefit. Cheers!

Thanks @Leigh! PM sent! What I have learned along the way is that I can still change the color of the merged fill layer, but if I want to alter the mask, it's best to CTRL + click on the merged layer to get the original selection, then create a new mask that I can then manipulate. I think I got that right, although it still needs more testing. In regards to the different hex numbers, at first, I thought it was a profile issue, but I have found that the same problem exists whether the profile is an sRGB or 1998. As mentioned to Leigh in my PM, it could be a settings issue on my end, although I don't have a clue at this point. The converted hex numbers are close, but not the same. I also added a fill layer on it's own that matches the color used in the fill layer that was merged. Interestingly enough, that number is slightly different than the other when converted. Since getting AP, I've also been racking my brains in regards to the HS layer that is clipped to a color fill layer that I use to accurately change saturation on the fly. When converted, the HS layer goes in below the fill layer (which is now merged with the mask layer as per my OP), the way it's done in AP (which I now understand). The problem is that the HS, or rather HSL layer now, doesn't have any affect on the fill layer, regardless of which slider you adjust (Hue, Saturation, or Luminosity). I have read countless threads, and tried many different things since starting this thread, but to no avail. Last night, I tried to simply unclip and move the HSL layer to a position over the fill layer. Immediately, the fill layer was affected by the HSL layer. But the problem is, so is the rest of the image, of course. So why does the HSL layer affect a fill layer when used separately, but not when clipped or masked directly to the fill itself? Workarounds such as rasterizing the fill layer after moving the HSL out are undesirable, since you remove the ability to change the layer's color "on the fly". I've spent too many hours trying to figure this one out, and am at wits' end at the moment. By the way, I read somewhere that the adjustment layers also act as masks, so I tested out creating a fill layer, then adding the HSL layer to it, and then masking directly to it. The thumbnail looks like it is masking, but it wasn't actually having any affect on the fill layer whether used in the clipped or masked position, as noted earlier. Thanks!

@Alfred: Ah! I see it now. I wouldn't have ever thought to look there. Thanks (again)! I see that my thread has been up for a week, but no responses. If there's anyone out there who has any answers to my OP questions, please let me know. Cheers!

@AndrejS: thanks for the thread. I also like Suzette's method, so I was curious too. @James Ritson: I didn't have much success with your method. The video method leaves a lot of detail lost and still a whole lot of dust and scratches to deal with. Thanks, regardless. @toltec: I tested your method out with a very old photo, and found that it worked very well. I realized with that photo, it was even able to clean up some grain issues as a bonus along the way. Many thanks for your suggestion!

Thanks Mark! I went ahead and bought from you guys. In retrospect, I should have loaded the trial version before opening this thread. I would have at least known myself that it works in Windows 7. While trying to figure out things relating to PSD files opened in AP (which I have an open question thread for), I began to learn things and became more familiar with AP, enough to help me decide to buy before the trial was up. Sometimes we learn more while in troubleshooting mode, so that may have helped me. That or the clock that Alfred mentioned was probably ticking in my head. Cheers!

I did a lot of reading as well as exploring within AP, but couldn't find the correct info to help me, so I'm posting here. Forgive the amount of info, but at least you'll know what I'm driving at. Please bear with me. I have a PSD template I use for colorizations in PS. I would like to open that (or any other preexisting file) in AP and maintain all layers, associated masks, colors, and clipped adjustment layers, as well as groups, blending options, etc. What I'm getting is that the groups seems ok. I noticed that the icon displays effects of what is within that group, whereas in PS, it was a simple Group icon. This is a nice touch in AP. Blending modes and opacities are the same. The Solid Color fill layers and their associated masks are merged when loaded into AP, instead of having a fill layer and separate mask underneath it like when creating a fill layer, then adding a layer mask if it was done directly in AP. The layer icon background is black and the revealed area is a color similar to what was masked in PS, but the RGB Hex number for the Solid Color fill layers in PS do not match the RGB Hex number in AP. Note that the color profile is set the same in preferences, but could be different in the template file, which I've had for a long time, and since it doesn't happen in something like the example below. I will use a simple example here without groups, one that can be recreated by anyone rather than me uploading a picture: In a PS PSD file, layers tab, we have: - a locked background picture - let's say of two green balloons. - a Solid Color fill layer - let's say blue, and named "Blue Balloon". - the associated layer mask that PS automatically added when choosing the Solid Color fill layer. This is inverted to all black except for the white portion set to a selection of one of the balloons to allow us to change the color to blue or any other color we want thereafter, and to allow us to change or adjust the masked area later on as well. - a Hue Saturation layer clipped to the Solid Color fill layer below it - let's say we set Hue to +25 and Saturation to +50 for the sake of this example. Save the PSD file, then open it in AP. In AP, layers tab, we have: - a locked background (Pixel) picture of the two green balloons. - a layer named "Blue Balloon (Fill)". It appears to be a merge of the blue Solid Color fill layer and the associated layer mask created in PS. - a Hue Saturation layer that looks clipped (is under the fill layer), but seems to have no affect on the Solid Color fill layer above it. Also, Hue Shift has the color under cyan at +25 as compared to blue in PS. Saturation Shift appears to be the same. So at first glance, it appears we have a few problems: the fill layer and mask are merged, the RGB Hex number is different (in my colorization template but not any other file I start from scratch), and the HS layer does not appear to be active, nor does the hue amount match when loaded into AP. First, how can I ensure that the color hex numbers are the same when loading a PSD file in AP? Next, are there solutions and/or workarounds to loading PSD files into AP, especially in the case of merged layers and masks, and if so, what are they, and what have you users been doing in these types of situations? Cheers! p.s. Is there a preview post option on this forum? I just get Cancel and Submit Topic.

Very true. Thanks Alfred!

Thanks for the quick response and the welcome! I downloaded the trial and am testing it out. I see that there are a lot of similarities to PS, but a lot of new things to learn about and get used to. For starters, I need to figure out things like how to get a PS psd file to load into AP complete with color adjustments layers and their masks intact, because I wasn't successful in my first attempt, and I need to figure out how to set black/white points and all sorts of different things like that. I will check the tutorials, do searches, and read up on things first before I post any questions if I need to. Having said all that, 10 days might not be enough time to decide. I will say before I go that I already am not a fan of the "save as" function being changed from its traditional longtime use. The use of "save as" here is actually a misnomer, since it only allows saving as an .afphoto file type. Perhaps either leave "save as" in its traditional use rather than using export (which was given a new tasks so to speak) to minimize our confusion due to familiarity and habit, and then add a third iteration for "save as .afphoto" with its own new shortcut, or worse case if it's too late to change that, is to change the name of "save as" to "save as .afphoto", so that it clearly defines it as being save as afphoto only and not anything else. This issue is not an earth shattering thing, since it has nothing really to do with the meat of AP itself, but needs mentioning nonetheless. In addition, I also saw that the panel thumbnail sizes cannot be changed, which is difficult for those of us with poorer eyesight, so I hope that can eventually be remedied as well. Anyway, I'm digressing and should leave that for other threads where things like this are already being discussed. Apologies. Happy New Year to everyone!

Greetings! Some questions: Why are the Affinity Photo system requirements on Affinity's site different than on the MS store site? Their site states that it is Win 10 only, whereas Affinity indicates Win 7, 8, and 10. I trust the latter, since it is from the developer after all. Is there a difference with the program MS store is selling or are they just continuing to try to shove Win 10 down our throats? Judging from some forum posts i read, it indeed works on Win 7, which is the OS I use, so I can't see why MS isn't being forthright about the requirements for a product that doesn't belong to them. How come the MS store price is a few bucks cheaper than Affinity's? I can't take advantage of this, since I get the message "This app does not work on your device" (due to not having Win 10), which greys out the "Get the app" button.