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

Recommended Posts

I photo merged images in Affinity..what a brilliant feature,  saved the combined image on Desktop and tried to open it with NX-D but  NX-D didn't show up in the "open with" drop down menu.

How can I get Affinity to recognize NX-D

Link to comment
Share on other sites

Not sure I understand at all what you mean here, which "open with" drop down menu, where do you see this menu option in APh?

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

Ok that's a Mac OS related selection choice and nothing AP specific. - Try to find NX-D then via the bottom "Other..." menu entry under "Open with ->" submenu and if it's shown access/select it.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

4 hours ago, titch said:

Affinity image

As far as I understand, it's not Affinity file (afphoto), but exported TIFF, for which Affinity gives the *.tiff extension. While in the first case it is a TIFF with a *.tif extension. All you have to do is set the N-XD to open with *.tiff (v_kyr).

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
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.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
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

Still not sure what the OP means with Affinity image, so if an .aphoto or .tiff file here in this case (?).

12 hours ago, Pšenda said:

As far as I understand, it's not Affinity file (afphoto), but exported TIFF, for which Affinity gives the *.tiff extension. While in the first case it is a TIFF with a *.tif extension. All you have to do is set the N-XD to open with *.tiff (v_kyr).

However, you can't setup NX-D to how to treat itself TIFF files, aka in this case the TIFF file extension handling. One can only setup how it deals with opening in other files via it's own (Open with application) functionality. Thus NX-D recognizes in it's internal file browser/previewer as default only the three letter TIF vs the TIFF extension (at least in my used version here).

Another point is that APh TIFFs are shown in a messed up way...

aph_tiff.jpg.d0d0190693666c51e598e3ec61cbb0d8.jpg

...so APh tiffs aren't really (re)usable here.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

15 hours ago, v_kyr said:

Ok that's a Mac OS related selection choice and nothing AP specific. - Try to find NX-D then via the bottom "Other..." menu entry under "Open with ->" submenu and if it's shown access/select it.

Thanks for replying, tried that but it didn't work.

Link to comment
Share on other sites

13 hours ago, Pšenda said:

As far as I understand, it's not Affinity file (afphoto), but exported TIFF, for which Affinity gives the *.tiff extension. While in the first case it is a TIFF with a *.tif extension. All you have to do is set the N-XD to open with *.tiff (v_kyr).

I couldn't find anywhere on NX-D where to make your recommended changes.

Link to comment
Share on other sites

1 hour ago, v_kyr said:

Still not sure what the OP means with Affinity image, so if an .aphoto or .tiff file here in this case (?).

However, you can't setup NX-D to how to treat itself TIFF files, aka in this case the TIFF file extension handling. One can only setup how it deals with opening in other files via it's own (Open with application) functionality. Thus NX-D recognizes in it's internal file browser/previewer as default only the three letter TIF vs the TIFF extension (at least in my used version here).

Another point is that APh TIFFs are shown in a messed up way...

aph_tiff.jpg.d0d0190693666c51e598e3ec61cbb0d8.jpg

...so APh tiffs aren't really (re)usable here.

The good news is that NX2 will work allowing me to use their u-points for "dodging and burning" areas of the image. Thanks again for replying with you comments

Link to comment
Share on other sites

33 minutes ago, titch said:

I couldn't find anywhere on NX-D where to make your recommended changes.

This is the OS setup, not the individual applications. Read again the first post from v_kyr.

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
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.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
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

1 hour ago, v_kyr said:

Still not sure what the OP means with Affinity image, so if an .aphoto or .tiff file here in this case (?).

Check out the pictures from OP.

File name from menu item Compress, Burn, Copy ...

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
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.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
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

37 minutes ago, Pšenda said:

Check out the pictures from OP.

File name from menu item Compress, Burn, Copy ...

Ok I see it's a "tif" file and that should also be handled by NX-D, two other Nikon apps Capture NX2 and ViewNX-i are already associated to "tif" there. It might be that NX-D doesn't propagate itself to the OS to use/support that file extension, even it can handle this, since all Nikon DSLRs (and thus their software too) can deal with NEF(RAW), JPEG, and TIFF files.

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

Some of the Nikon programs won't handle TIF files unless the extension is .tif, but Affinity produces .tiff. We can see that in the OP's screenshot.

-- 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.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

4 minutes ago, walt.farrell said:

but Affinity produces .tiff. We can see that in the OP's screenshot.

 

 

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
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.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
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

I now tested that on my older OS X system here and here it works for "TIF" files ...

nx-d_tiff.jpg.339cd47ed9f30ed57a3f2bcf1b1994ed.jpg

But APh's batch conversion (which saves as xxx.tif and not xxx.tiff) does generally really do strange things when generating TIF/TIFF files here ...

APh_tif.jpg.fd082e1643295a23d81231c42112e96b.jpg

Thus I don't generate or export TIFF-files with APh at all on OS X, since it always messes up things. Instead I use GC or PSE etc. here then.

 

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

21 minutes ago, v_kyr said:

But APh's batch conversion (which saves as xxx.tif and not xxx.tiff) does generally really do strange things when generating TIF/TIFF files here ...

Yes, it's a nice tiff / tif confusion :-)

 

 

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
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.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
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

5 minutes ago, Pšenda said:

Yes, it's a nice tiff / tif confusion :-)

Yip it's pretty inconsistently handled. :(

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

3 hours ago, v_kyr said:

Yip it's pretty inconsistently handled. :(

How's this for inconsistency? On Macs you can rename the file extension from .tiff to .tif or visa versa & the Affinity apps open them without issues. That includes files exported to the TIFF format from an Affinity app. O.o

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

37 minutes ago, R C-R said:

How's this for inconsistency?

So you think it's pretty fine and normal that in APh exporting creates "four_letter_ext.tiff" files, but batch processing instead then "three_letter_ext.tif" files. - Well maybe they should write out .tiffy files ... 9_9

batch_tif.jpg.62362cfe067c0b3974e3a94382a2a6b8.jpg

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

3 hours ago, v_kyr said:

but batch processing

Is it schizophrenic also with JPEG (*.jpg vs *.jpeg), or is it okay?

Affinity Store (MSI/EXE): Affinity Suite (ADe, APh, APu) 2.4.0.2301
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.3155.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 23H2, Build 22631.3155.
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

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.