DannyBCreative

Thanks, Nathan. It does seem to have gone nowhere. Shame too, as that's the one thing keeping me from fully adopting AP in my workflow.

I'm guessing the answer to my question is, no, AP is not capable of using cryptomatte layers in multilayer EXR files.

This is what I use in Photoshop currently. I have spoken to the developers of EXR-IO and they tell me that it will not work currently with Affinity Photo, but they are interested in making a plug-in explicitly for AP. I made a post about this a while back. They asked if Affinity Photo has an SDK that they could use. My post on the subject received no traction.

I could, but if someone knows the answer already, that takes less time and storage on my system. I know Photoshop can already do this via a powerful and free plugin. This is what I'm currently doing, but I was hoping that AP could do this by now.

Hey All, I've been away from AP for a bit due to work assignments requiring the "other" guys software, but I'm slowly trying to reintegrate AP back into my pipeline. I know AP has always had the ability to work with 32 bit linear multilayer EXR files, but can it recognize Cryptomatte layers yet? I'm currently not using Ver. 2 on my PC so I can't test this, which is why I'm asking. Thanks for any feedback you can provide!

Same question. Are you processing jpeg and tiff files in the develop persona? I get that the crash shouldn't happen for something so trivial, but why not just work the tiff and jpeg files in the standard photo persona? Keep the develop persona for developing RAW files. Unlike Adobe Camera Raw, there is little to no need to take already converted RAW files (jpeg, tiff, png, etc) into the Develop Persona.

Is it crashing while trying to process jpeg files in the develop persona? I'll try this, but why are you processing jpeg files in the develop persona?

Well, I figured if I really wanted to test it out thoroughly, what better way than to purchase a $4,500.00 laptop and really run it through it's paces? Now that I've confirmed that it doesn't crash, I can go back to using my regular laptop.

I did search for that and did not find it. But thank you for confirming that this old bug is still being ignored.

Shouldn't be long now, it's been a problem since V1 but I'm sure it's nearly fixed at this point.

I know this was an issue in V1, and I was hoping it would be fixed by now, but it seems to be broken still. Macros will not run when selecting them with my WACOM Intuous Pro. Mouse clicks are fine, they just don't respond to the tablet. Anyone else experience this?

AP 2.0.3 on M1-Max running Monterey - no such crash. I keep trying to crash the app, but I can't. Using a SONY RAW file in develop mode, I've adjusted every single slider available, multiple times, and I just can't get the app to crash.

No crashes here at all. What are you system specs?

Works perfectly fine with no crashing on my M1-Max, running Monterey.

Interesting. I can't replicate this at all, at least not in 2.0.3. Has it been fixed perhaps?

Right, but this wouldn't be saving anything outside of an aphoto file. The plug-in allows you to open an OpenEXR Multilayer file in Affinity Photo, which for 3D artists is super helpful. A single file can contain all render passes, alpha channels, cryptomattes, etc... In Photoshop this will open the file into layers. From there you work the image just as you would with any other layer stack, but you'd have a 32 bit, linear file. The developer is willing to make this popular plug-in for Affinity Photo. Again for 3D artists this is a big deal, and would really eliminate the need to keep Photoshop on hand when working on composites.

I'm posting this here, because I'm unsure of where else to post it. Does anyone know how to get into directly to the appropriate people at Serif about 3rd party developers wanting to develop plug-ins for Affinity Photo? I'm talking to a dev who created an amazing plug-in for Photoshop that handles OpenEXR files. He's expressed interest in wanting to develop this same plug-in for Affinity Photo and has asked me if I could pass this info up the chain. Any help would be greatly appreciated. Thank you!

For those who are interested in the build process.

Ideas, ideas ideas....

The shadows of the foreground elements are cast by the same light casting the shadows of the background elements. They are all placed in scene so they pick up the same light. The thing that is impossible to see here is the distance. If you were to look at this from the top down, you'd see the shadows are very, very long. The buildings are very far from the subjects and by the time the shadow length reaches the foreground subjects, it has begun to soften. The shadows from the foreground elements are very close to the camera, but if you were able to zoom out to see them fully, you'd see that they too soften near the end. The color of the sky and haze were added after the fact of course, and yes, you could argue that they might affect the brightness of the suns (tatooine has two), but this place, or universe doesn't exist and we really don't know what having two suns would mean in an atmosphere, so it'll stand as completed.

Problem is UI. Publisher is a layout tool at its core, like InDesign, which I wouldn't use either for high-end photo manipulation or compositing work. I do own all three apps, and I do know how they can all be accessed from Publisher, but workflow would be drastically different, and in my opinion, counter to that of a professional workflow for this particular type of work. I do appreciate you taking the time to offer the suggestion, I just don't feel it's necessarily the right approach for the work I do. Thanks Walt!

So, as part of a timelapse video I'm making for YT, I went back and redid this image. This time with some custom assets and a wider aspect ratio. I like this one better.

Thanks, Walt. But for the work I do, jumping to Publisher doesn't seem like a reasonable option. I do own Publisher by the way, but I use it for what it it's intended for, and not that often. I use AP for high-end composite work, so jumping into Publisher, to scale an image layer just doesn't work well. Thanks for chiming in though. At least now I know that I can scale down and back up any layer without losing image quality. That was the more important question I had. For now, I can just eyeball the scale if/when needed.

Is there a way to see what the original dimensions were? For example, I have a layer that is 400x400px and I scale it down to 120x120, but then decide later that i want it back to its original size. Do I have to remember what my original size was, or is there some info setting that will show me its original size?

Interesting. Ok, so image layer or pixel layer, whatever the dimensions of the layer when the image is added to the scene, they'll remain constant and quality will not degrade if resized down, then back up, so long as the project is not exported? I imagine rasterizing will commit the resolution as well, which is probably why I was confused about this, seeing that pixel layers are rasterized layers. Thanks Old Bruce.