Jump to content

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

Share this post


Link to post
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.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
Share on other sites

On my Mac desktop.  The left screenshot does not show NX-D from the affinity image but the right hand screenshot shows NX-D from a Photoshop or other software image.

 

 

Screen Shot 2019-03-20 at 8.16.15 PM.png

Screen Shot 2019-03-20 at 8.18.36 PM.png

Share this post


Link to post
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.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
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: Designer 1.7.2.471, Photo 1.7.2.471, Publisher 1.7.2.471.
Windows 10 Pro, Version 1903, Build 18362.295.
Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
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.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
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.

Share this post


Link to post
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.

Share this post


Link to post
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

Share this post


Link to post
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: Designer 1.7.2.471, Photo 1.7.2.471, Publisher 1.7.2.471.
Windows 10 Pro, Version 1903, Build 18362.295.
Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
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: Designer 1.7.2.471, Photo 1.7.2.471, Publisher 1.7.2.471.
Windows 10 Pro, Version 1903, Build 18362.295.
Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
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.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
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

Windows 10 Home, version 1903 (18362.239), 16GB memory, Intel Core i7-6700K @ 4.00Gz, GeForce GTX 970
Affinity Photo 1.7.2.471 and 1.7.3.476 Beta   / Affinity Designer 1.7.2.471 and 1.7.3.476 Beta  / Affinity Publisher 1.7.2.471 and 1.7.3.475 Beta

Share this post


Link to post
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: Designer 1.7.2.471, Photo 1.7.2.471, Publisher 1.7.2.471.
Windows 10 Pro, Version 1903, Build 18362.295.
Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
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.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
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: Designer 1.7.2.471, Photo 1.7.2.471, Publisher 1.7.2.471.
Windows 10 Pro, Version 1903, Build 18362.295.
Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
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.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
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


Affinity Photo 1.7.2, Affinity Designer 1.7.2, Affinity Publisher 1.7.2; macOS High Sierra 10.13.6 iMac (27-inch, Late 2012); 2.9GHz i5 CPU; NVIDIA GeForce GTX 660M; 8GB RAM
Affinity Photo 1.7.2.153 & Affinity Designer 1.7.2.6 for iPad; 6th Generation iPad 32 GB; Apple Pencil; iOS 12.3.1

Share this post


Link to post
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.7.1 ◆ Affinity Photo 1.7.1 ◆ OSX El Capitan

Share this post


Link to post
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: Designer 1.7.2.471, Photo 1.7.2.471, Publisher 1.7.2.471.
Windows 10 Pro, Version 1903, Build 18362.295.
Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080.
OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.