音频元数据存储
我检查了 SO 上关于音频元数据提出的问题，但找不到可以解答我疑问的问题。音频文件的元数据到底存储在哪里以及以什么形式存储？是文件形式还是数据库形式？这个文件数据库存储在哪里？
I checked through the questions asked on SO on audio metadata, but could not find one which answers my doubt. Where exactly is the metadata of audio files stored, and in what form? Is it in the form of files or in a database? And where is this database of files stored?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
谢谢米歇尔。我的基本困惑是元数据是存储为文件的一部分还是存储在文件系统中其他位置的单独文件中 - 就像类 Unix 系统中的 inode 一样。 ID3表明它作为字节块与文件一起存储在文件的实际内容之后。
这是大多数其他文件类型的元数据存储方式吗？
Thank you Michelle. My basic confusion was whether the metadata is stored as a part of the file or in a separate file which is stored somewhere else in the file system - like inode in case of Unix like systems. ID3 shows that it is stored with the file as a block of bytes after the actual content of the file.
Is this the way of metadata storage for most of the other file types?
据我所知，音频文件格式：
可能支持元数据标准（例如 ID3v1、ID3v2、APEtag、iXML）
也可能有自己的原生元数据格式（例如 MP4 盒/Quicktimeatoms、OGG/FLAC/OPUS/Speex/Theora VorbisComment、WMA 原生元数据、AIFF/AIFC 原生元数据...）
=>在这两种情况下，元数据直接存储到音频文件本身中。
HydrogenAudio 维护最常见格式之间的字段映射表：http://wiki.Hydrogenaud。 io/index.php?title=Tag_Mapping
也就是说，许多音频播放器（例如 iTunes、foobar2000）允许其用户编辑任何文件中的任何元数据字段，无论底层是否支持所述字段标记标准（例如，在 S3M 文件中添加“专辑艺术家”字段）。
为了做到这一点，这些音频播放器将元数据存储在其内部数据库中，从而给人一种音频文件已被“丰富”的错觉，而其实际内容保持不变。
音频播放器数据库的另一个经典用途是存储以下字段：
=>在这种情况下，您将在音频播放器的内部数据库中找到元数据
As far as I know, audio file formats :
May support metadata standards (e.g. ID3v1, ID3v2, APEtag, iXML)
May also have their own native metadata format (e.g. MP4 boxes / Quicktime atoms, OGG/FLAC/OPUS/Speex/Theora VorbisComment, WMA native metadata, AIFF / AIFC native metadata...)
=> In these two cases, metadata is stored directly into the audio file itself.
HydrogenAudio maintains a field mapping table between the most common formats : http://wiki.hydrogenaud.io/index.php?title=Tag_Mapping
That being said, many audio players (e.g. iTunes, foobar2000) allow their users to edit any metadata field in any file, regardless of whether said fields are supported or not by the underlying tagging standards (e.g. adding an "Album Artist" field in an S3M file).
In order to do that, these audio players store metadata in their internal database, thus giving the illusion that the audio file has been "enriched" while its actual content remain unchanged.
Another classic use of audio player databases is to store the following fields :
=> In that case, you'll find metadata in the audio player's internal database