wjgo

Is there a way to get assets to automatically update to whatever is in a folder location? Instead of find images and adding them, I'd just like an asset folder to just use and update to whatever is in a folder.

What's happening is when I select the picture frames, its selecting the image, and I do not get a context toolbar for the frame. In other frames that I have since added and placed images, I do. Did these frame get some setting wrong? I did not do anything different. I placed them, then was trying to figure out how to add a border.

I created several picture frame in Publisher (1.8.3) , and have placed images in them. I would now like to add borders to the frames, but nothing so far is working in the stroke panel. I can create NEW picture frames and adjust the borders, but it seems I can not add any borders to existing frames already created. I can create new frames without borders and then add some, but for some reason, 4 existing frames seem to be immune from adding a border.

Opening a 23mb .nef file, and then saving it as an .afphoto file - is 137Mb. This seems nuts to me. No changes. Nothing done to it. Open ned as 16 bit from Assistant,, save as, confirm develop, then save and explosion in file size. Almost triple the size of .tiffs made with these .nef files. Is there a way to operate with reasonable file sizes with just small adjustments to them?

Thanks for replies. I was getting very bad, dark, flattened raws when loaded. It seems that while I change the RAW output to 16 bit, and reloaded the image (as per AP tutorials), my copy of AP actually wanted me to restart AP. Since I had only one option in the drop down selection for a RAW engine and an empty lens profile folder, I was looking at this as a problem. But AP is loading the images OK now, and does identify the lens I used. Thanks.

Thanks. The ICC Display was set. I was setting the RAw output to 16 bit, tone curve applied and "do nothing" and each change, was reloading the image (there is an AP Tutorial that says those changes only take place on the next image load). But that wasn't not working. Them it seems that I needed to restart AP each time or soemthign to that effect, image reloading was not working. Thanks for help.

I am trying to diagnose why AP is unable to properly convert a Nikon .raws of mine. In the Assistance Manage, there is an option to select a raw engine. In these forums, many have said to pick a a different raw engine. My drop down gives me only one option, Serif. Other have posted to use ACR. How can I get that option? If it makes a difference, using a Nikon D7500, and these particular nefs are from a Tamron 10-24mm HLD. In preferences, if I ask it to show me my lens profile folder, its an empty folder.

So, what settings should one be using? I open a .nef in AP, and its horrible. Its dark, and flat. In fact, there is just a small block where a flowing histogram (of a not bright photo) should be. All my other editors can see it (Even Corel Photo Paint!). I know there is some develop assistants, but I don't like to stray too far from default settings and screw the editor up for something that should be so basic, and default. Is the "assistant manager" I change the option to RAW output 32-bit HDR, and the impact is very minimal, the histogram changes very little. And, how is one supposed to do highlight and shadow recovery now, if its been improved? At one point in history, AP could by default open nef's, but its highlight and shadow recovery was awful, so I never used AP for raw editing, but its been a couple years now and I have read people say its better I know on this .nef, it will not work and is not acceptable, seems more like a gama slider. I have seen some conversations about using live filters and such instead of the Highlights and Shadows under the "Basic" tab. But neither of them work. Luminar can do this, but not AP? So, what weird setting am I missing because I would have seen other complaints. And why would it not be a default setting? 1 .nef opened in AP 2. Opened in LR 3. Shadow Recovery in AP 4. Shadow Recovery in Luminar for lolz.

It still destructively editing the layer and not preserving control points.

They are still not compatible. Nik Plugins work as smart objects when used by PS. And can be re-edited again. Not able to do that with Affinity Photo despite AP claiming to be able to import PS smart objects.. Changes are permanent and control points are lost when it comes back to AP and can not be used again.

My work around is to either stick with Corel Draw, or go to Xara. Mesh, is simply not going to happen in Affinity Design. Serif does not care for it and will not devote any time for it. If Serif wanted it to happen, this tool would have been included, years ago. Its clear it will not happen, and Serif has chosen to limit itself to photo and publishing tools. Its old Designer application just never had the energy to compete with other applications, and Affinity Designer never will either. Mesh and distort tools have been on their roadmap - FOR 5.5 YEARS!. The first post by Serif about the Affinity Design roadmap, listed "Mesh fill tool" as the FIRST design and illustration tool, immediately followed by "Mesh warp/distort tool." ON AUGUST 21st, 2014! It was roadmapped during the original beta. roadmap so old, use the wayback machine to see it

I have having this issue in two areas. Bot batch converting .nef files to .tiff, the convert to srgb macro step does not have any positive effect. When create a stack, and process the stack, the images are also coming out as dark as a batch conversion job.

It seems to me what is happening is that AP is not batch converting raws correctly. I can export a .tiff from a raw and get a good exposure. But if its in a batch job of converting a folder, (using 16 bit), or a conversion that takes place in a stack, the exposures are way too dark.

OK. I think I know what happened. AP shows opened raw images with one exposure, and when exported to a tiff, it has a much lower exposure. And exported .tiffs do match my results. I am mostly new to AP, so what is the best workflow for this? Use the raws, then edit the resultant .tiff or convert the images to .tiffs first - and then stack them? But, both Lightroom and DxO export to .tiffs from raws, a much more acceptable exposure level, and far closer to what I saw through the viewfinder. What is going on. If Ap somehow not exporting .tiff correctly? Will exported .tiffs from AP loose dynamic range if its from an already dark raw file?

I stacked 17 raw files, and used median, and mean. The resultant image is much darker and any of the images in the stack. Is this to be expected? These are exports of the stack, and an export of a raw used in the stack. I might expect the water to become darker, averaging pixels, but the stream/river bank is also much darker, even the light grey fence.