Jump to content
You must now use your email address to sign in [click for more info] ×

Affinity Files Not Shown in file open menu


Recommended Posts

Greetings all!  New Affinity Photo user here 🙂

I did a search on this topic, but did not find anything.  I apologize if it has already been discussed under some other heading or keywords.

Very odd behavior when attempting to open an Affinity file.  I am running Windows 10.  I have 5 photos edited and ready for HDR merging.  When I select file -> HDR Merge, the file ADD/REMOVE submenu pops up.  When I select ADD, the file selection explorer (for lack of better words) pops up.  The filetype is set for Affinity files, but no Affinity files are visible.  Only NEF files (I shoot Nikon) show up.  The NEF files should not be visible at all since I am filtering for Affinity files.  It's working the opposite way!  

Now when I select Open in Affinity, the Affinity files appear along with every other filetype in the selection list.  But not in the HDR or new STACK selection lists.  Here are some partial screenshots to help explain what I am experiencing:

Here I am opening an existing Affinity file:

image.png.cd7d60dd47ba37eae88dd01e6f402e1c.png

The Affinity files show up in the list.  Here I am attempting to ADD files to HDR merge:

image.png.100b427f9c312a805d57727fc1ef01b5.png

No Affinity files appear even though the filter is set for Affinity files.  What gives? 🤷‍♂️

Anyone have any idea?  It must be a simple fix!

Jeff

 

Link to comment
Share on other sites

Welcome to the forums @WhiteStone

I don’t think you can HDR Merge Affinity documents – e.g. AFPHOTO, AFDESIGN, AFPUB – so I think, in this case, “Affinity Files” means “just the types of image file which the HDR merge function can handle”.
If I’m wrong – quite possible – then someone will say so.

Link to comment
Share on other sites

1 minute ago, GarryP said:

Welcome to the forums @WhiteStone

I don’t think you can HDR Merge Affinity documents – e.g. AFPHOTO, AFDESIGN, AFPUB – so I think, in this case, “Affinity Files” means “just the types of image file which the HDR merge function can handle”.
If I’m wrong – quite possible – then someone will say so.

Ah!  Gerry are you saying the HDR merge files must be RAW?  You are probably correct!  What is throwing me off is the HDR Merge list is filtered for Affinity files as a default.  That is a bit misleading for sure.  I will follow the RAW path and see how it goes.

Thanks a bunch!

Jeff

Link to comment
Share on other sites

You’re welcome.
I don’t use the HDR Merge functionality myself so I can’t say which image types are valid but RAW would certainly seem to be one of the ones it should work on.
I think I’ve seen this “Affinity Files” file-type problem elsewhere and it has been reported as being confusing, not just for this functionality.
I’m not sure if you should be exporting your documents as ‘HDR files’, but if that’s working for you then that’s great.

Link to comment
Share on other sites

2 hours ago, GarryP said:

I don’t use the HDR Merge functionality myself so I can’t say which image types are valid but RAW would certainly seem to be one of the ones it should work on.

I don't use it either, but from the general way that RAW files are processed in Affinity Photo I suspect the better workflow would be to Develop the individual images, export as TIFF, and run the HDR Merge on the TIFF files.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

James Ritson also addressed this a little while ago:

 

Edited by walt.farrell
Sorry; mistyped James's name.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

5 hours ago, walt.farrell said:

I don't use it either, but from the general way that RAW files are processed in Affinity Photo I suspect the better workflow would be to Develop the individual images, export as TIFF, and run the HDR Merge on the TIFF files.

Hi Walt,

As you know, I am new to Affinity.  Can you expound on why you believe the TIFF route might be a better work flow?  I am just curious, and desire to use the most efficient path to a successful HRD result.

My experiment last night proved very successful however!

Best regards,

Jeff

Link to comment
Share on other sites

1 hour ago, WhiteStone said:

Can you expound on why you believe the TIFF route might be a better work flow?  I am just curious, and desire to use the most efficient path to a successful HRD result.

Basically for the reasons explained by James Ritson in the post I linked to.

RAW files go through the full advanced Development process only when you use them:

  • In the Affinity Photo application, not Publisher nor Designer; and
  • Via File > Open (into the Develop Persona) or File > New Batch Job

Any other usage of a RAW File in Photo (File > New Stack, File > New HDR Merge, File > New Panorama, File > New Focus Merge, File > Place) and any usage in Designer or Publisher goes through a shortened Develop process which does not include the Develop Assistant functions (Lens Correction, Noise Correction, Tone Curve, Exposure Bias). So, unless you always run with the Develop Assistant disabled, or those options disabled, you'll get different results if you try to use a RAW file directly in something like HDR Merge, than you'd get if you Developed the file through File > Open and Export first.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

There are some goblins in this forum who play with user names :-)

 

14 hours ago, WhiteStone said:

OK Gerry.

Screenshot_2021-10-30-01-23-42.png.8d6d6884539f937f0d33500962d49963.png

 

10 hours ago, walt.farrell said:

James Ruston

Screenshot_2021-10-30-01-27-01.png.f8b378a69461dd25103ea8fdede571ad.png

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.3.1.2217
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

6 hours ago, walt.farrell said:

Basically for the reasons explained by James Ritson in the post I linked to.

RAW files go through the full advanced Development process only when you use them:

  • In the Affinity Photo application, not Publisher nor Designer; and
  • Via File > Open (into the Develop Persona) or File > New Batch Job

Any other usage of a RAW File in Photo (File > New Stack, File > New HDR Merge, File > New Panorama, File > New Focus Merge, File > Place) and any usage in Designer or Publisher goes through a shortened Develop process which does not include the Develop Assistant functions (Lens Correction, Noise Correction, Tone Curve, Exposure Bias). So, unless you always run with the Develop Assistant disabled, or those options disabled, you'll get different results if you try to use a RAW file directly in something like HDR Merge, than you'd get if you Developed the file through File > Open and Export first.

Thanks Walt.  This is very helpful!

Jeff

Link to comment
Share on other sites

6 hours ago, WhiteStone said:

Oooops!

Only for information - best way for using users name into forum is type "@" and gradually enter the letter of his name. A list of usernames will be displayed, which will be filtered as you enter more letters until you select the correct one. The selected name is then inserted into the text of the post as an object,

Screenshot_2021-10-30-09-16-16.png.d2ca21934246d29617766f595a0feda4.png

that can be clicked and bounced into the user's profile. The user also receives a message that his name has been quoted and that he should read the post. And if the user changes their nickname over time, this link will also change, so the displayed name will always be consistent.

Edited by Pšenda

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.3.1.2217
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.2506.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

3 minutes ago, Pšenda said:

Only for information - best way for using users name into forum is type "@" and gradually enter the letter of his name. A list of usernames will be displayed, which will be filtered as you enter more letters until you select the correct one. The selected name is then inserted into the text of the post as an object,

Screenshot_2021-10-30-09-16-16.png.d2ca21934246d29617766f595a0feda4.png

that can be clicked and bounced into the user's profile. The user also receives a message that his name has been quoted and that he should read the post.

@Pšenda Hey!  It works!  Very cool.  Many thanks!  As a newbie, I have a lot to learn here; but I do appreciate the gentle guidance as I go along.  👍

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | 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.