Talk:FourCC

message: I think this page should be merged into OSType, since the idea originated on the Mac. Ldo 22:40, 19 Sep 2004 (UTC)
replies: text: Done.  Made FourCC a redirect to OSType.  Changed a few things on OSType.  Hope you don't mind.  AlistairMcMillan 00:18, 20 Sep 2004 (UTC)
replies: text: Nope, I don't mind at all. Looks good! Ldo 04:11, 20 Sep 2004 (UTC)
replies: text:  If you put ~~~~ at the end of your comment, it'll automatically enter your Username and timestamp. AlistairMcMillan 05:11, 20 Sep 2004 (UTC)
replies: text:  Thanks for making the suggestion of a merge.  For some reason that hadn't occurred to me.  AlistairMcMillan 05:11, 20 Sep 2004 (UTC)
thread_title: Merge

message: FourCC has since been unmerged with OSType by MCoder.  The idea did not originate on the Mac as Ldo has suggested and a merge is not appropriate.  See Talk:OSType.  – Andyluciano 18:08, 27 February 2006 (UTC)
replies: text: While the concept did originate with Apple, OSTypes are now a specific case of FourCCs (for instance, the MacRoman encoding semantics are specific to Mac OS usage). On the other hand, there’s more information in OSType. Keeping them separate seems sensible. -Ahruman 15:18, 27 February 2007 (UTC)
thread_title:  Un-merged 

message: Shouldn't FourCC redirect to FOURCC instead of the other way around? I've never seen it with mixed caps ever. —Zachary talk 16:26, 11 April 2007 (UTC)
thread_title:  FOURCC vs. FourCC 

message: Really, now.
It would yet be pompous to insinuate that Ken Thompson came up with the "TwoCC" code, such as #! denoting a shell script.
Likely, such devices were in use in the 1950's and 1960's already.
How about in-memory type fields: Lisp, 1958.
Putting a few bits at the very beginning to identify type is completely obvious and trivial.
The processing software can just read the first few bits, and dispatch a routine to deal with the rest, without having to seek around in the stream.  —Preceding unsigned comment added by 192.139.122.42 (talk) 18:57, 29 September 2010 (UTC)
thread_title:  Header magic numbers originated on the Macintosh? 

message: The Magic Number for a WAV file is "RIFF", a 4-byte hexadecimal sequence. Each of the sub-chunks of a WAV file also use a 4-byte identifier, such as "WAVE", "LIST", "INFO", "fmt ", or "data". There are no two-byte identifiers in a WAV file. Please re-write that paragraph to reflect this fact.
Hpfeil (talk) 15:23, 15 February 2020 (UTC)
thread_title:  WAV files use a two-byte identifier? 

message: The section on compiler support goes on and on about the endianess of a fourcc code, yet no where is there any definition that has any endianess attached to the concept and frankly, it makes no sense, since this is just four bytes in order -- there is no most significant or least significant byte. The entire section is just wrong.  — Preceding unsigned comment added by 188.176.25.249 (talk) 18:05, 29 April 2020 (UTC)
thread_title:  Compiler support is rubbish 

message: IIRC, this article used to contain a lot more information that I used regularly when I was doing low level programming. It contained a chart that had a list of all know FourCCs, and included ELF. and COFF to designate executables in Linux and Windows respectively. I'd really appreciate it if that information were returned to the article. It wasn't published in one convenient location anywhere else. 108.222.118.213 (talk) 03:10, 20 July 2022 (UTC)
thread_title:  List of FourCCs