What is difference in saving/exporting a file as a .tiff w. layers vs .afphoto?

[Rich]

I use Bridge as a DAM to manage & search my photoshop and RAW image files. I want to switch from Photoslop to Affinity Photo, but I noticed that .afphoto files only generate an AP icon in Bridge, no image (see below).

But when I export the layered image file from AP as a layered 16-bit .tiff file, it appears normally in Bridge. And when I open the .tiff file in AP again, all the layers are present for further editing.

Question: Are there any disadvantages to saving image files edited in AP as layered .tiff files instead of .afphoto files relative to compatibility, future editing and final image quality? Thanks.

[Alfred]

Use the native *.afphoto format unless you’re happy to lose any adjustment layers, live filters, etc.

[walt.farrell]

2 hours ago, Alfred said:

Use the native *.afphoto format unless you’re happy to lose any adjustment layers, live filters, etc.

A "TIFF with Affinity Layers" export maintains all those when re-opened in an Affinity application, so I'm not sure what you mean by "lose", in this case. The TIFF file basically contains a .afphoto file, too, in that case.

It's only readable by Affinity applications, of course, and every other application will see it flattened. So I suppose there's a risk of editing it in some other application and Saving, which would "lose" the Affinity data. Is that what you meant?

[Alfred]

58 minutes ago, walt.farrell said:

A "TIFF with Affinity Layers" export maintains all those when re-opened in an Affinity application, so I'm not sure what you mean by "lose", in this case. The TIFF file basically contains a .afphoto file, too, in that case.

It's only readable by Affinity applications, of course, and every other application will see it flattened. So I suppose there's a risk of editing it in some other application and Saving, which would "lose" the Affinity data. Is that what you meant?

Yes, that’s what I had in mind. But you’re right, of course: if the OP simply wants to be able to continue editing the exported file in an Affinity app then I don’t suppose there are any significant disadvantages. However, I don’t think there are any significant advantages, either!

[NotMyFault]

3 minutes ago, Alfred said:

However, I don’t think there are any significant advantages, either!

Depends on perspective. Having a thumbnail in DAM could be significant for OP.

[walt.farrell]

1 minute ago, NotMyFault said:

Depends on perspective. Having a thumbnail in DAM could be significant for OP.

The thumbnails are available from a .afphoto file, too, for any DAM that cares to extract them. Few DAMs seem to, however.

[Alfred]

2 minutes ago, NotMyFault said:

Depends on perspective. Having a thumbnail in DAM could be significant for OP.

Good point! I believe some utilities (XnView MP springs to mind) can be persuaded to display Affinity thumbnails, but TIFF is obviously much more widely recognized.

[Rich]

3 hours ago, walt.farrell said:

A "TIFF with Affinity Layers" export maintains all those when re-opened in an Affinity application, so I'm not sure what you mean by "lose", in this case. The TIFF file basically contains a .afphoto file, too, in that case.

It's only readable by Affinity applications, of course, and every other application will see it flattened. So I suppose there's a risk of editing it in some other application and Saving, which would "lose" the Affinity data. Is that what you meant?

Thanks Walt. My initial tests showed me that the variety of layers I originally saved as a .afphoto test file were preserved and still editable in AP after being exported as a "TIFF with Layers" file. Just wasn't sure if I was missing some disadvantage for me in doing this. I now plan on using Affinity Photo exclusively.

Being able to use Bridge was the final issue for me that I had to resolve in switching to Affinity Photo from Photoslop. I work almost exclusively in multi-image HDR/Pano sets, and Adopy Bridge (free) is the only DAM I have been able to find that will automatically stack these image sets together (see below). This saves me hours each week compared to manually tagging & grouping each of hundreds of multi-image sets.

[walt.farrell]

12 minutes ago, Rich said:

My initial tests showed me that the variety of layers I originally saved as a .afphoto test file were preserved and still editable in AP after being exported as a "TIFF with Layers" file.

You're welcome.

I have a vague memory of having found something that is saved in a .afphoto file that is not preserved when exporting a TIFF with Affinity layers. But I cannot remember what I found, and I haven't been interested enough to do the research again.

[Old Bruce]

10 minutes ago, walt.farrell said:

You're welcome.I have a vague memory of having found something that is saved in a .afphoto file that is not preserved when exporting a TIFF with Affinity layers. But I cannot remember what I found, ...

You and me both.

[Rich]

3 minutes ago, walt.farrell said:

You're welcome.

I have a vague memory of having found something that is saved in a .afphoto file that is not preserved when exporting a TIFF with Affinity layers. But I cannot remember what I found, and I haven't been interested enough to do the research again.

Well, I hope it's manageable for me as a temporary solution.

Ultimately, like many other Affinity users, I am hopeful that Serif will publish their own "Bridge-like" DAM. Then there will be no question of compatibility, as with other multi-platform DAM software. And when their RAW Develop Module evolves further, then there will be little reason for photographers to continue enduring Photoslop & Lightsloth.

[user_0815]

One difference is file size. Tiff files can be significantly larger than aphoto files. Especially if it contains several pixel layers. 

[JohnZeman]

Another is the Save History with Document option only works with the .afphoto format, not the TIF format.

[Rich]

8 minutes ago, JohnZeman said:

Another is the Save History with Document option only works with the .afphoto format, not the TIF format.

Thanks John. The Save History option sounds useful.

What I may look into is creating an action that will save my edited file as both .afphoto and TIFF format. Then I will stack them together in Bridge, with the TIFF file on top so I can see the image, not just an AP icon. Besides viewing, the TIFF file can also serve as a backup of the edited composite image I am creating.

[JohnZeman]

Rich this is just a follow up comment regarding what you said up above about only being able to find a DAM (Bridge for you) that will automatically stack image sets together.

I've been using IMatch for years, and if you configure it to use file relations it will also automatically stack image sets too.  You have to confirm the stacking to do it but it works great.

IMatch is not free however but it has top notch support and I've been very happy with it as my DAM since 2006.

[Rich]

11 hours ago, JohnZeman said:

I've been using IMatch for years, and if you configure it to use file relations it will also automatically stack image sets too.  You have to confirm the stacking to do it but it works great.

Thanks John. I was just checking out iMatch a few days ago. Lots of good reviews. I wasn't able to get on their forum to ask about stacking, but thanks to you now I know.

My other concern is that iMatch runs on PC only. I have been a Mac guy, but recently built my own PC workstation since I can't afford $20k for a decently configured Mac Pro. My other two computers are Macs. So, I would prefer a dual-platform DAM. But now iMatch is certainly on my short list of options.

[Fixx]

16 hours ago, Rich said:

I have been a Mac guy, but recently built my own PC workstation since I can't afford $20k for a decently configured Mac Pro.

It is not very hard to install OSX to PC hardware. Or to make dual boot system.

[Rich]

19 hours ago, Fixx said:

It is not very hard to install OSX to PC hardware. Or to make dual boot system.

Thanks Fixx. I seriously considered doing that prior to building my present PC workstation. The main concern I had was hearing that every time Apple issued a new OS update (once a year) many people had to troubleshoot, patch & tweak their "Hackintoshes." I just don't have time for that, but for those who do, it sounds like a great option. Windows OS is a constant pain to use compared to MacOS.

[Fixx]

2 hours ago, Rich said:

The main concern I had was hearing that every time Apple issued a new OS update (once a year) many people had to troubleshoot, patch & tweak their "Hackintoshes."

Mojave is stable OS, no need to update anything.

[R C-R]

11 hours ago, Fixx said:

Mojave is stable OS, no need to update anything.

It may be stable but Apple no longer issues security updates for it & a lot of Mac apps no longer will run on macOS versions that old if they are updated to more current versions. There also may be driver & other hardware related issues to sort out with "Hackentoshes" regardless of which macOS version they run, particularly with printers, network adaptors, & other peripherals.

[HerrBill]

For what's its worth Rich, I found working with Affinity photo in Bridge very frustrating. I did some research and came across XnView. It can read AF Formats so I changed over to it.

Give it a try it might and see does it suit your workflow.

[Rich]

11 hours ago, HerrBill said:

For what's its worth Rich, I found working with Affinity photo in Bridge very frustrating. I did some research and came across XnView. It can read AF Formats so I changed over to it.

Quote

Quote

 

 

Thanks Bill. I found that iMatch will show .ifphoto files, but only as small rez jpeg files and w/o any metadata. That was a deal breaker for me.

Can XnView display the original rez & metadata of an .ifphoto flie? Can keywords be assigned to files and then later searched. Those are my main needs. Thanks again.

[HerrBill]

Rich,

Yes it will do all what you asked for. But don't take my word for it. Down load it, its free for non commercial users and play with it

Have fun.

 

[Fixx]

11 hours ago, HerrBill said:

Yes it will do all what you asked for.

It will not show hires version of original affinity file, only lores preview. There is no sw that can display affinity format except affinity's own apps. 

Serif is not going to open affinity formats to other developers. I wish though that they would do that by agreement with select DAM developers so that there would be better support for affinity in DAM sector. I suppose option to have larger previews would help also..

[Rich]

5 hours ago, Fixx said:

Serif is not going to open affinity formats to other developers. I wish though that they would do that by agreement with select DAM developers so that there would be better support for affinity in DAM sector. I suppose option to have larger previews would help also..

Yes, this lacking in Affinity Photo (not fully compatible with DAM's) has been the greatest deterrent for me in switching to AP from Photoshop/Bridge. It's just too disruptive to my workflow. Every year, I try for a while, then go back to using Adobe.

Hopefully, this limitation that Serif is imposing upon its users (and potential users) means that they have plans to publish their own DAM. If so, I encourage them to do it quickly. It would significantly increase their user base and satisfy their existing users enough to fully recommend Affinity products for professional use.