@NutsAboutAmiga

Quote:

That's exactly what you don't wont, what you won't is same format as file format your loading. If file was created on little endian CPU, you need treat that file as an little endian file. WAV was invented on PC, there is this file format little endian, you can't do anything about that, you can't invent a big endian wav file, because no program will support it.

The problem is, a file like WAV is bi-endian. It goes both ways. Yes the data is little endian but the header IDs are big endian. For example a WAV header:

52494646 4E738303 5415645 4A554E4B
R I F F           W A V E J U N K 

@Hypex

Quote:

The problem is, a file like WAV is bi-endian. It goes both ways. Yes the data is little endian but the header IDs are big endian. For example a WAV header:

No it does not, a char is byte, and per definition a byte can't have a endian format, as it is the smallest unit. (if we ignore bits, but bits have only one format, just image if need to swap bits, )

The WAV header is in "char", as one byte is one byte on little or big endian it works fine.
only when you have short, int, long long int, will you get a endien problem.

In the example you give, your trying to treat char's as integer, this is the problem.

Last edited by NutsAboutAmiga on 02-Jun-2017 at 05:58 PM.
Last edited by NutsAboutAmiga on 02-Jun-2017 at 05:08 PM.
Last edited by NutsAboutAmiga on 02-Jun-2017 at 05:07 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@WolfpackN64

Quote:

Sometimes I really wonder why Apple ditched their Classic OS

Because NextStep/OSX is infinitely better, at least on newer hardware.
You guys can continue to wax nostalgic about OS9, I wouldn't touch it, anymore than I'd continue to use a Microsoft PC OS introduced before the NT kernel.

@WolfpackN64

The Classic OS 9 environment while useful for old scanners etc on OS X Tiger was a buggy mess as far as I remember it on actual G3 era hardware! Constant spinning beach balls, problems ejecting discs or closing applications. It definitely wasn't a multi tasking OS and was not fit for purpose really with a lot of bloat that ruined performance. The puc-mice were the final straw in me eventually hating the original iMac. It was a computer for those that didn't love computers a bit like the Mercedes for non-car people with too much money. OS X was a massive improvement but then they tried to fuse it with iOS and now it has rubbish OpenGL support (because Metal API is the future ) and now has no killer professional apps anymore that people on PCs can't access since they messed up Final Cut Pro and the Mac Pro design (no powerful single GPU boards are supported due to heat)! Adobe Premiere and Photoshop might as well be used on a PC.

Last edited by BigD on 02-Jun-2017 at 06:31 PM.

_________________
"Art challenges technology. Technology inspires the art."
John Lasseter, Co-Founder of Pixar Animation Studios

@NutsAboutAmiga

Quote:

No it does not, a char is byte, and per definition a byte can't have a endian format, as it is the smallest unit.

That may be so but it happens to fit neatly in a 32-bit space and all code I read loads it in as a pointer and compares it with a backwards number.

Quote:

The WAV header is in "char", as one byte is one byte on little or big endian it works fine. only when you have short, int, long long int, will you get a endien problem.

It may be char but programmers don't seem to know that. They don't treat it as a string. It's too much work to compare with a string.

Quote:

In the example you give, your trying to treat char's as integer, this is the problem.

It's not my problem, it's the problem of open source programmers. But the fact is, this RIFF and AIFF for that matter is derivative of IFF. And on IFF the IDs were assembled as long words in the compiler. However, they were correctly assembled from separate char elements into one long word. So, would in theory, be portable.