In article <thethurmans.com>,
Lorenzo Thurman <com> wrote:
1) Endian is not a byte-stream concept, so it has nothing to do with
positions within the file. It has, rather, to do with how data stored
in shorts, longs, floats, doubles, or Int64s are stored.
2) The layout of an MP3 file is *much* more complex than just offsetting
a certain number of bytes into the file.
3) Quoting from the ID3 specification:
"The bitorder in ID3v2 is most
significant bit first (MSB). The
byteorder in multibyte numbers is most significant byte first (e.g.
$12345678 would be encoded $12 34 56 78), also known as big endian
and network byte order." So there is no endian issue here.
4) If there was an endian issue, you would resolve it in your code using
the various Macros in Endian.h which are provided for helping you with
just such a thing.
5) No framework is going to handle things like this for you when it
deals with low level structures such as files or memory buffers. This
is because the system doesn't "know" about the structure of the buffers