winddk-8.1 VS vircadia-native-core

There is no de facto supported standard because WAV files are de facto not used as anything but intermediate format these days. You could have fifty standards, that wouldn't change much.

WAV files can have any kind of compressed stream inside. A program that used some ancient API like WinMM ACM could theoretically play anything inside WAV as long as audio driver for that compressed format (now commonly called “codec”) was present. In addition, there are all kinds of standard metadata (like author and comment fields), and players in the '90s had no problem with displaying it in their interface if it was present. Old Windows Media Player had some of these status lines shown by default.

By the way, “driver” was an actual driver, with an .inf file, update of win.ini/system.ini or registry, and probably a reboot required to start using the decoder.

Old SDK tells us to look further into MMREG.H, so let's do just that.

https://github.com/tpn/winddk-8.1/blob/f6e6e4da7d1894536cf1f...

https://github.com/tpn/winddk-8.1/blob/f6e6e4da7d1894536cf1f...

(Last line is quite ironic.)

It's interesting to look how all those early '90s ideas that Universal Tagged Formats would be used to hold anything and everything, and dragged-and-dropped into any and all application completely flopped. Mac had those, Windows had those, Amiga had those. You can say that MP4, an international standard, is actually MOV in disguise, but it doesn't support all those early crazy options that could turn the file into poor man's PowerPoint presentation, poor man's Hypercard, or poor man's FMV game. On the other hand, Windows Media Player did support ASF interactivity like “open the link in a browser at this timestamp”, “show user some text at that timestamp”, and the consequences were so bad that it all had to be killed in mid-00s.

Vircadia is an open source (Apache 2.0) metaverse ecosystem consisting of a high performance real-time server architecture (C++), web SDK (TS), and web client (TS).