Jump to content

HuniSenpai

Members
  • Content Count

    112
  • Joined

  • Last visited

About HuniSenpai

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I know this would be extraordinarily difficult to program, but I'd love to see some settings to not smooth over these cusps and corners. Basically, a slider like this: Maximum angle. Similar to auto smooth (formerly edge split) in Blender; it decides the maximum angle that smoothing will occur on. It's difficult to program because this is raster, but perhaps you could divide the selection into a series of regression lines, the length of which lines would be specified by the user (higher lengths = ignoring little bumps more in this search, smaller lengths = finding angles everywhere, hence disabling smoothing all over the place). In other words, (behind the scenes) turn the selection into a polygon in order to find where these sharp angles exist. Again, this is a difficult thing to code, but it sure would be great to have. Green check is where I want the smoothing, red x is where I don't want it:
  2. Is it introducing noise of accentuating noise that is already there? If it's accentuating noise that's already there, that's to be expected. Increased local contrast at high spatial frequencies tends to do that, I don't think there's any way around it. However, if it is actually creating noise that wasn't there before, then that's a problem. Maybe you could give an example of what you mean, show a before and after.
  3. Have you tried using the color selection in HSL? It's not as good as the replace color tool in Photoshop but it's close enough for my work, at least. This feature was added after this thread was created. Back when I started using Affinity Photo, there was nothing like this.
  4. There isn't a whole lot to test for a feature like this. I guess I'd try thing like letting go of crl while doing the center-locked cropping, double tapping crl, pressing crl after I start moving an edge, try crl on edge vs vertex, etc. Really it's just a matter of having a play around with the tool in a few different scenarios. 10 minutes. It doesn't need to be perfect at this stage because it will then be tested again by hundreds of people (including me) once the beta is released -- free bug testing! Secondly, if Serif has done this right, they would update their documentation across different languages in bulk. That is, once every major update. You don't call up your translator and have them translate just a sentence or two (on a feature that is still in development and may be adjusted later). Rather, you have them translate things after you have finished a significant portion -- i.e., finished the update or a large amount of it. As for adding this feature to the English documentation, this is literally a sentence or two mention. As much as you are trying to claim otherwise, this really isn't all that time consuming -- and my opinion is as good as yours, because neither of us are Serif devs. Moreover, the devs are updating the documentation dozens of times throughout the update; this addition to the documentation is just a drop in the bucket. Anyways, to be clear, no hostility here. I'm glad we're having a (civil) conversation about the implications of adding this feature. Certainly better than when my thread was sitting here silent for around half a year, lol!
  5. You assume that photographers only know photography? Are you really going to insult me like that? I am actually familiar with Java and have done some programming. To be fair, it's simple stuff -- basic GUIs, bots to control my computer and do silly stuff like a graphing calculator in ms paint, bot to auto list items and scan screen, click on buttons, etc. But, to be clear, I am not saying I know anywhere near as much as these devs. However, am I wrong to say that it wouldn't take longer than maybe an hour? Maybe 30 minutes? Correct me if I'm wrong, but this does not seem like it is a hard thing to add. Of course sometimes the most deceptively simple things can be complicated to implement -- I have learned that from my (slight bit of) coding experience. Still, I doubt this would be a multi-day project...
  6. Yeah I was going to say that he should be using Affinity Designer, too, but I still 100% agree that the crl modifier for crop and other tools is necessary with his job. You need to be able to symmetrically crop in from all sides. I'm a professional product photographer and it is the same story for me. I think the devs at Affinity Photo have no idea how important this feature is. Because they don't have it, I have to click and drag from each edge, one by one (or on the two vertices, but that offers less control for me). It is so, so painful. You see, I usually have my item centered directly in the frame, and I always shoot wider rather than tighter (in case I need to do a square crop or something weird). So I always have to crop... ergo I always have to deal with Affinity Photo's awful lack of a crl modifier. This would take the devs half an hour -- maybe minutes -- to add. Please just add it. Even if I have to buy Affinity Photo 2.0 for it, I will. Also, don't even talk about workarounds. The whole point of crl to center lock if for convenience. You lose all convenience when you have to place down rulers to do it.
  7. You've gotta click on the colored dot that you used when you originally made the HSL adjustment.This is not a bug.
  8. I agree with you! My only question is on the last one. I do 8K images just fine in Affinity Photo? I've even done some more thorough edits on 10K panoramas. I also regularly do 6000x6000px edits for Amazon images (that's 36mp; 8K is about 33 mp). That includes graphic design for the infographic shots, along with high resolution photos and plenty of adjustment layers. The only thing that I don't touch in Affinity Photo are live sharpen and the other live filter adjustment. Those things slow down the program a lot. I also try to not use too much LAB, although sometimes I just can't help it (LAB is much slower than RGB). Aside from those, though, it seems like I can edit as high resolution and with as many adjustments & layers as I want. I'm just running it on a mid-range PC; Ryzen 5 1600 (6 core 12 thread), 16gb RAM, GTX 970. What are your specs? And is this just when opening photoshop files or something weird?
  9. I mean it's not really a hotkey, but you can press " 0 " twice to set the selected layer's opacity to 0%. You can then press " 1 0 0 " to set it back to 100. Maybe there should be a hotkey though, idk. Just some additional info for those who use Photo. This behavior is slightly different in Affinity Photo (which is the Affinity product I use most). Using the numpad will normally set opacity of the selected tool. So if you're using stamp or brush you'll change the tool's opacity, not the layer's. You need to make sure you have a tool selected that doesn't have an opacity setting. So just press "v" first to pull up move tool.
  10. Sorry for the late reply. For some reason I failed to publish the video, hence it being private. It's unlisted now, if you still want to view it. Sorry about that!
  11. I really do agree with you. Both Capture One and Davinci Resolve have more control in their color range selection. I made a post on here about a year ago asking a similar thing as you, I just recommended Resolve's instead of Capture One's (I haven't used the latter). Both are similar, though. I'm thinking Photo should mix both Resolve and Capture One. They could use the same color wheel graphic as Capture One with the distance from the center of the circle representing saturation, and they allow selection of lightness ranges in a slider-like-thing, just like the sliders in Resolve that let you change selected ranges, change their feather, etc. And instead of having these colorful dots: Affinity Photo should use a feed to show the list of changes done within the HSL adjustment, like Capture One:
  12. That is not what HSL adjustment layer does. HSL adjustment currently only lets you "mask" based on hue. That's what the big circular color wheel thing is for. That way you can change what was a blue hue into a red hue, for example, while the greens and yellows remain unchanged. HSL adjustment, ever since a version or two ago, is a "replace color" tool in addition to a tool you'd use to boost saturation, change hue of image overall, and change lightness. All of this is lacking one major thing though: the target color selection currently only lets you target a specific hue range. I want to specify not only a certain target hue range, but also a target saturation range and a target luminosity range. This would allow me to increase the saturation of desaturated areas in my photograph, for instance. Or it could let me decrease the saturation in the dark, desaturated yellow regions and no where else. In other words, the color range selection in HSL only has one variable: hue. I agree with Zeel, we should add one or two more variables to this feature.
  13. I see what you mean. My personal expectation for vectorization is just to be as good as Inkscape because I haven't used Illustrator in a long, long time. But I recognize that Designer will, hopefully, be able to compete with Illustrator some day. For people moving from Illustrator to Designer, they are going to expect a similar quality of vectorizing. It doesn't have to be identical, but close. As it is now, though, Designer's vectorization meets absolutely no ones expectations because there isn't vectorizing in the first place. Just implementing something as good as Inkscape's will satisfy 75% of us, and maybe 99% will be satisfied if Designer can match Illustrator. Only those who have unrealistic expectations of what vectorizing should do will be disappointed, that's the 1%. On something like this, I feel like it's about just getting the feature implemented sometime in the near-ish future. Unless Serif is able to use some new technique to vectorize like machine learning, I doubt they will ever meet that 1%'s unrealistic expectations. In my opinion, Designer should put a rough version of vectorizing into the program to start, and refine it until it is similar to Illustrator's. If Serif doesn't want their only selling point of Designer to be "price," then they can focus on countless things other than vectorizing. For example, Designer has an excellent system for isometric work and an isometric grid that far exceeds anything in Illustrator, that's a selling point. Spending years on trying to perfect a vectorizing feature is ineffectual. This stuff has been around for decades without massive improvements. It's much better to focus on areas where you can make big changes.
  14. That's not true though. It has to be roughly the same as what we are currently using for it to be beneficial, it does not have to be better. If Designer does an identical job as Inkscape (which is that other tool i'm using right now) then I will certainly choose Designer over Inkscape. The idea is to not have to keep switching between programs. Ideally, Designer's vectorizing feature should be about equivalent to Adobe Illustrator's. That's the expectation. They should aim to meet that expectation because I don't think it's reasonable to try to exceed this expectation. If they can match Ai's vectorizing feature (alongside shapebuilder and the other missing tools 😕), then i'm sure many people will consider moving to Designer because of the price. Especially hobbyists and illustrators who don't need to open files in the .ai file format constantly.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.