Saving TIFF file BYTE order IBM Pc

[tonypatterson1]

I just installed Adobe CC , photoshop and LR. I have installed it on my laptop and it works as expected . On my desktop PC , a Dell PC , after finishing a edit in photoshop upon saving the save defaults to BYTE order Macintosh and I have to choose IBM Pc every save before saving. Is there a way to have it default to IBM PC. I have after selecting save TIFF and selected IBM PC closed the program hoping it would save the setting but next time it reverts to saving as macintosh. Thank you

[gener7]

I would recommend resetting your preferences. Then see if that fixed it.

[tonypatterson1]

I will try that, Thank you

[gener7]

As I understand it, the tiff options dialog should remember the byte order option you selected.

[tonypatterson1]

I found the setting suggested , closed PS , opened a photo and saved it as a tiff again I changed the selected item was macintosh , changed to IBM Pc and saved the file and closed PS. opened Ps tried another and again it choose macintosh , so selected IBM PC and saved and closed and tried a third time and again macintosh . I can not find how to get it to default to save as IBM PC. any help appreciated

[gener7]

It might depend what device or software the file came from. Maybe it is selecting the byte order for you.

What if you created a new file in Photoshop, or save an existing jpeg as a Tiff with IBM PC byte order? Does it stay there?

[Jeff Arola · Accepted solution]

Even though photoshop should probably remember those settings, now a days that setting makes no difference.

It was only in pretty old software that read tif files that the setting mattered.

Chris Cox, a photoshop engineer, wrote an explanation about it somewhere on these forums

Edit: Found it:

Re: Tiff byte order in PS CS5

the intial question

'i'd like to have the default byte order setting to be Mac and not IBM when saving Tiff files in PS CS5. It seems that it's always defaulting to IBM, is there a way to change that?

the reply by Chris Cox

"There is no way to change the default. But for most software (and all correctly written TIFF code) the byte order doesn't matter.

The default was changed to IBM/LittleEndian because that is the byte order for Intel/x86 processors and offers a slight speed advantage when opening and saving.

Historically, Macintosh (68K and PPC) used BigEndian byte order - which is far easier to read, debug, and work with, but isn't the byte order of current desktop processors."

[Pacoh]

I'm a little uncomfortable with this answer because I forgot to set the byte order to IBM a couple times and later found a couple images in LR that could not be displayed.  Maybe that's just a coincidence but it does make me worry.     

[D Fosse]

That's not the problem.

More likely they are layered files, but you did not set "maximize compatibility" in PS prefs. That inserts a flattened composite layer in the file. Lightroom doesn't support layers and can't read them - but it can read a flattened composite.

If you use Lightroom, always set maximize compatibility.

[Conrad C · Accepted solution]

---

@Pacoh wrote:

I'm a little uncomfortable with this answer because I forgot to set the byte order to IBM a couple times and later found a couple images in LR that could not be displayed.  Maybe that's just a coincidence but it does make me worry.     

---

It probably is a coincidence, due to Jeff Arola’s answer (the one marked Correct) — that any reasonably recent image editing application, from most developers, should read TIFF files of either byte order without a problem. And by “reasonably recent” I mean versions released in the last 15 to 20 years at least. It’s certainly true that Adobe photo applications recognize both byte orders, so there is no wrong way to set it now. I totally stopped paying attention to that setting.

[Test Screen Name]

Ironically, Macs stopped using that order 16 years ago, in 2006. They now use the same order as Windows, because that's what Intel chips use, and M1 chips are the same. But this isn't relevant in any practical way; it's just two choices that apps need to support.