
Tyler Bay
Members-
Posts
6 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
nerdine reacted to a post in a topic: Reasons for Switching Back to Photoshop
-
PaoloT reacted to a post in a topic: Reasons for Switching Back to Photoshop
-
I've been on a shoot before where the photographer used a full screen window in photoshop to go over some edits. It was a couple days of shooting, he had done some skin smoothening edits that received feedback from the director, he quickly pulled up the edit file while the director was there, popped the canvas over to the other screen, and went full screen mode to adjust it right on the spot. Also, anyone who digitally paints would appreciate a full screen mode as well. The point is - full screen mode should be full screen and not partially full screen. I'm sure there's other uses for this that myself (or you) are not even thinking of right now as well.
-
Yeah, it's exactly that - I'm recording video and revealing layers as I'm teaching. It works much better than a powerpoint presentation because I can just design everything I need and not worry about re-assembling everything again in powerpoint. Outside of that though, I imagine this would be a requested feature for times when a photographer wants to show clients their work. Isolating the canvas without anything else does look cleaner than having bars on the top / bottom.
-
Hey James, Thank you for the detailed reply. I do have the taskbar hidden, and when I do fullscreen mode, there are still the top and bottom bars visible on the screen. When recording live video, that means I need to crop it in and degrade the quality of the video in order to only show what's on the canvas. In photoshop, they have a presentation mode that removes everything on the screen except for the canvas, however, the fullscreen mode in Affinity doesn't seem to have that option. With the anti-aliasing, is that a new feature in v2? I've been using v1 and haven't upgraded to v2 yet in Affinity. With OCIO, what I'd like to accomplish is this: 1. Render out an exr. 2. Pop it into Affinity for some 32 bit edits 3. Send out a jpg to display on web or send a co-worker an image file that's easily accessible. The problem comes in when going from 32 down to 8 bit. In photoshop, the solution is... 1. Select the 8 bit format and 2. Change the "Method" setting to "Exposure and Gamma." And the colors / tones will remain consistent. In Affinity, you need to go through a lot of complications in order to compensate for the ICC Transform, and it's always difficult to remember how to do this because the OCIO transform options are a mile long with options. I've been able to get this working with a combination of OCIO transforms + baking the layer to compensate for the transform that occurs with the ICC, but it's always a big pain in my workflow when I'm just trying to send out a rendered image real quick. With blend ranges and/or live luminosity masks, I don't see this as an option when making an adjustment layer or under the layer fx options. Would this be a new feature in v2 as well? Or is this located somewhere else? The tool cycling is a big help as well. I was looking under the hotkey options for that, but it's good to know where that is now. Thank you again for the help, have a nice day, - Tyler
-
Tyler Bay started following Reasons for Switching Back to Photoshop
-
Hey everyone, I don't like to say it, but today I went back to Photoshop for my work due to a few features that are lacking in Affinity. I really want to return back to Affinity and upgrade to v2, but there's a few things that have added up for my workflow that just don't cut it right now. 1. Affinity Photo doesn't allow for full screen mode (and I mean FULL screen) - I need this because I often create diagrams for teaching. This requires that I record my screen, and I need to have everything but the work area hidden. 2. The magic wand tool doesn't perform as well as Photoshop does. With photoshop, I can most often click the tool, click the area I want to cut out, press delete, and it gives me a pretty clean cutout every time. With Affinity, you have aliasing issues along the edge and the refine selection performs slowly + has a hard time giving me crisp looking results even after adjusting. 3. Converting 32 bit images to 16 or 8 is complicated and difficult to achieve. With Photoshop, I can click the defaults and everything looks the same when I convert. With Affinity, I need to remember a complicated, multi-step process each time I want to convert from 32 to 8 bit when exporting a render from a 3D application. I can do it, but it's always a huge pain when I need to remember all the OCIO conversions, ICC display transforms, and complications that need to take place. 4. It's not as easy to blend layers based on tonal ranges as it is with Photoshop. In photoshop, you can double click a layer and and adjust the black / white sliders to exclude or include tonal ranges non-destructively with clipped and feathered values. With Affinity, I've found it much more difficult to control this, and defining tonal zones isn't as easy as it is in Photoshop. 5. Pressing shortcut keys multiple times will cycle through all the variants of a tool, and it's not something I've been able to get used to. Often, I'll be in a tool already and hit the hotkey again by mistake. Then, I'll try to use the tool, it doesn't work as I expect it, and I have to undo and spam the hotkey again to get back to the variant of the tool I'm looking for. I've tried to get used to it, but after years of using Affinity, it's still annoying. I'd love to see these improvements in the future, and if it happens, I'll gladly switch back to Affinity again. But, for now, these user experience / feature issues are adding up for me. I just want to let you all know what's up before I leave. All the best, - Tyler
-
Hello Affinity, I am trying to convert a 32 bit image - rendered with Redshift/Houdini - into an 8 or 16 bit image with the proper OCIO/ACEs transformation baked into the ICC profile. At the moment, I am forced to rely in the ICC profile instead of ACEs when doing this transformation to 8 or 16 bit. This is, however, an incorrect workflow because of the fact that it will clip highlights, does not account for the change in ACEs CG primaries which results in desaturation, and is generally not as accurate as what is implemented with ACEs due to the order of operations during the transformation. I am aware that there is a suggested fix for this by converting to 8/16 and then applying a 2.2 gamma curve reduction once the sRGB ICC has been applied via a live filter layer. However, as mentioned above, I am still left with clipped highlights and desaturation. Is there a way to apply an ICC profile which does nothing to the image? Or, ideally, a way to convert to 8/16 bit without altering the pixel data in any way. Thanks in advance, - Tyler