Drew13 had this to say:
Little Endian and Big Endian is how the data is stored with the most signifcant byte on one end or the other (taken from Gulliver's Travels and how the egg should be cracked.(ETA) One of the conflicts in the book is between people who preferred cracking open their soft-boiled eggs from the little end, and the people who preferred the big end.). For the most part you do not need to concern yourself with this (unless you like finding out about those things more) it is transparent in your workflow on the Mac using these apps.(FCP, FCE etc.)
PPC Mac > Big Endian (default)
WIndows PC > Little Endian (default)
• Endianness
This is all well and good
except when it comes to the Intel Macs and Dolby AC3 creation with Compressor.
At the moment there's a byte-order compatability Problem mixing UB versions of AC3 with PPC versions of AC3 within the same DVD SP 4.1 project.
Read this:
http://discussions.apple.com/thread.jspa?messageID=3130608�
MaxR says:
Apple's developer site specifically cites byte-order as a concern for developers of Universal binaries, but seems to have let this slip out anyway. Shame, shame, Apple.
G5 1.8 DP (PCI-X) Mac OS X (10.4.8) ATI X800 XT, 4GB RAM, 20" & 23" ACDs, M-Audio Revolution 5.1, Fostex D15 DAT