musicpd.org No paid content found

MP3 is a lossy compressed audio format that shrinks music and other audio to a fraction of its original size by discarding sound data most listeners can't easily hear. You use it when you want small files that play almost anywhere — on phones, cars, old MP3 players, and computers. You should choose a different format when you need studio-grade fidelity or plan to edit and re-export audio repeatedly, because MP3 throws away data permanently each time it's encoded.

What MP3 actually is

MP3 stands for MPEG-1 Audio Layer III. It's a lossy format: the encoder analyzes the audio and removes frequencies and quiet details that are masked by louder sounds, a principle called psychoacoustic modeling. What's left is a much smaller file that still sounds close to the original to most people.

The trade-off is controlled mainly by bitrate, measured in kilobits per second (kbps):

Higher bitrate means bigger files and better fidelity. There's also variable bitrate (VBR), which spends more data on complex passages and less on simple ones — often a better quality-to-size ratio than a fixed rate.

MP3 vs. other audio formats

Use the same dimensions to compare, then pick based on your goal:

Choose MP3 if compatibility matters most — nearly every device and app plays it. Choose AAC if you're inside Apple's ecosystem or streaming. Choose FLAC or WAV if you're archiving a collection or doing audio production and don't want to lose data. Converting a lossy MP3 to FLAC won't restore quality — it just makes a bigger file.

How to get MP3 files legally

• Digital stores — Platforms like Amazon Music, Bandcamp, and 7digital sell MP3 (and sometimes FLAC) downloads outright. You keep the files.
• Streaming services with downloads — Some subscription services let you download tracks for offline playback, but those files are usually locked inside the app and not portable MP3s.
• Public domain and Creative Commons sources — Internet Archive, Free Music Archive, and Jamendo host MP3s you can download and often reuse under stated licenses. Check each track's license.
• Your own CDs — Ripping a CD you own to MP3 with software like Exact Audio Copy, dBpoweramp, or iTunes/Apple Music is a common legal route in many jurisdictions for personal use. Rules vary by country.
• BitTorrent and P2P sites — Sites like The Pirate Bay index torrents across categories including music (mp3), movies (avi), games, and applications. Downloading copyrighted material without permission is illegal in most countries and carries real risks: malware in bundled files, ISP notices, and legal exposure. If you use torrents at all, stick to content that's explicitly licensed for free distribution.

How to play and manage MP3s

Playing:

• On phones and computers, any default player works — VLC, Windows Media Player, Apple Music, or a browser.
• On dedicated MP3 players, drag files into the device's music folder via USB.
• In cars, use a USB drive, aux cable, or Bluetooth depending on the stereo.

Managing tags and metadata: MP3 files carry ID3 tags (title, artist, album, artwork). If your files show up as "Track 01" with no artist, use a tag editor like Mp3tag, MusicBrainz Picard, or Kid3 to fix them in bulk. Consistent tags are what make a library searchable and sortable.

Converting other formats to MP3: Use a converter such as Audacity (with the LAME encoder), FFmpeg, or a dedicated tool. The input is your source file, the action is encoding at your chosen bitrate, and the expected result is a smaller MP3. Remember: converting from a lossy format to MP3 loses quality again.

Common MP3 problems and fixes

• Missing or wrong tags — Re-tag with a metadata editor; enable automatic tagging from an online database if your tool supports it.
• Won't play — The file may be corrupted or mislabeled. Try VLC, which handles many damaged files; if it still fails, re-download or re-rip.
• Corrupted files — Partial downloads are a frequent cause. Verify the file size and re-download from the source.
• Choppy playback — Usually a slow drive or overloaded device, not the file itself.
• Suspicious downloads — Files from untrusted sources can carry malware. Scan downloads, avoid executables disguised as audio, and prefer official stores or known archives.

Safe downloading practices

• Prefer stores, artist pages, and established archives over random file hosts.
• Check the license before reusing anything, especially for public performance or uploads.
• Keep a backup of your library; lossy files can't be recovered once corrupted.
• If a "free MP3" site asks you to install a codec, run a program, or enter payment details for a free track, treat it as a red flag.

MP3 remains the most compatible audio format you can carry. Pick your bitrate by how you'll listen, get files from sources you trust, and keep your tags tidy so the library stays usable.

MPD (Music Player Daemon) is a server-side music player that runs in the background and plays audio on demand, with no graphical interface of its own. You control it from a separate client program, which can run on the same machine or over the network. It fits situations where you want one always-on music engine — a home server, a Raspberry Pi, or a hi-fi setup — that several devices can share and control at once. It is not a desktop app you double-click to start playing a file.

The client–server split

MPD separates two jobs that ordinary music players bundle together:

• The daemon (server): owns the music library, the audio output, and the playback state. It starts at boot, keeps running, and does nothing visible.
• The client: a separate program that sends commands ("play this album", "skip", "set volume") and displays what's happening. It can connect locally or remotely.

Because the daemon holds the playback state, closing a client doesn't stop the music. You can disconnect from one machine and reconnect from another, and the same track keeps playing. That is the core difference from a desktop player, where quitting the app ends the session.

The site describes MPD as "a flexible, powerful, server-side application for playing music," which matches this model.

What it can play

MPD handles both local files and network sources. According to the project's own keywords, supported material includes:

So a single MPD instance can serve a local FLAC collection and an internet radio stream through the same control interface.

How a session actually works

1. MPD starts as a background service and reads its configuration, including where your music lives and which audio output to use.
2. You connect a client. The client talks to MPD over its control protocol, either on the same host or across the network.
3. You build or browse a queue. The client asks MPD to add tracks, albums, or streams to the current playlist.
4. MPD plays. Audio comes out of the machine running the daemon — not the client. This matters: if MPD runs on a headless server, the sound comes from that server's audio output, not from your laptop.
5. State persists. Pause, skip, or change volume from any connected client; every other client sees the same state.

The practical consequence of step 4 is the most common source of confusion. Controlling MPD from your phone does not route audio to your phone — it routes commands to wherever the daemon and its speakers are.

Clients

MPD itself has no interface, so you always need a client. The project's news section, for example, notes that "myMPD 26.0.0 has been released," referring to one such client. Clients range from terminal-based controllers to web interfaces to mobile apps, and different clients suit different devices — a phone-friendly one for the couch, a keyboard-driven one for a terminal.

When MPD is the right choice

MPD tends to make sense when:

• You want one music library shared across several devices rather than separate copies.
• The playback machine is always on — a server, NAS, or Pi — and you control it from elsewhere.
• You prefer low resource use and a headless setup over a full desktop application.
• You want to keep playing while switching controllers, or have multiple people control the same output.

It tends to be the wrong choice when you want a single self-contained app on one computer, when you need the audio to come out of the device you're holding, or when you'd rather not configure a service and pick a client before hearing anything.

The short version

MPD is a background playback engine plus a control protocol. The daemon plays; clients command. It supports common lossless and lossy formats plus radio and streaming, and it's built for always-on, multi-device, remotely controlled listening rather than single-app desktop use. If that split matches how you listen, MPD is a strong fit; if you want one app that does everything on one machine, a conventional desktop player will be simpler.

本地音乐播放器解决的核心问题只有一个：把你硬盘上已有的音乐文件，变成一个能搜索、能整理、能跨设备播放的私人音乐库。如果你有大量 FLAC、MP3 或高解析音频文件，又不想把播放行为交给带账号和遥测的流媒体服务，那么选择标准应该落在四件事上：库管理能力、播放质量、隐私与离线可用性、以及是否能远程访问。Audion 是一个可参考的开源样本——它覆盖了这四项，且明确标注免费、无广告、无追踪、可离线使用。

本地播放器和流媒体服务的区别

流媒体服务提供的是"内容访问权"，本地播放器管理的是"你已经拥有的文件"。这个区别决定了后续所有功能取向：

• 文件归属：本地播放器扫描你的文件夹、读取标签、自动整理，文件始终在你自己的磁盘上。
• 账号要求：Audion 明确写的是"no accounts, no sign-in"，播放不需要登录。
• 网络依赖：离线可用是本地播放器的默认状态，而不是需要额外付费解锁的功能。
• 内容边界：你能听什么，取决于你拥有什么文件，而不是平台曲库的授权范围。

如果你的音乐主要来自购买、CD 抓轨或 Bandcamp 等渠道，本地播放器是更匹配的工具；如果你依赖平台推荐和即时曲库，本地播放器不能替代流媒体。

选择开源音乐播放器时看哪些维度

库管理与元数据

播放器应该能扫描指定文件夹、读取音频标签并自动组织。Audion 的描述是"scans your folders, reads tags, organizes automatically"。选择时确认它是否支持你现有的目录结构，以及是否能通过 MusicBrainz 这类来源补全元数据和封面。

播放质量与音频处理

关键指标包括支持的格式和采样率上限。Audion 支持 FLAC、WAV 等高解析格式，最高 192 kHz 且不做重采样，同时提供 10 段均衡器、交叉淡入和 gapless 播放。如果你的文件以无损为主，重采样会直接损失音质，这一项值得优先确认。

歌词与界面

逐行同步歌词（line-by-line lyrics that follow playback）和主题定制是体验层面的加分项。Audion 支持自动获取歌词，并允许用完整 CSS 控制主题，或直接使用社区预设。

隐私与开源属性

开源意味着代码可审查，隐私承诺可以被验证而不是只能相信。Audion 的表述是无遥测、无登录、文件保持本地。对于在意播放数据去向的用户，这是与闭源播放器的主要差异点。

跨平台一致性

Audion 覆盖 Windows、macOS、Linux，并声称"one codebase, same features everywhere"。如果你在多系统间切换，需要确认功能是否真的对齐，而不是某个平台被削减。

插件与集成生态

插件决定播放器能否接入你已有的工具链。Audion 的集成包括 Last.fm 记录播放、Discord 显示状态、MusicBrainz 元数据、Plex、Jellyfin、Navidrome 同步，以及 Spotify 歌单导入。社区插件还覆盖 Last.fm scrobbling 和 Discord Rich Presence。

自建远程访问：把本地库变成私人流媒体

如果你希望在外也能听家里的音乐库，可以自建服务端。Audion 提供 Audion Server，可运行在家庭服务器、树莓派或 VPS 上，通过浏览器或 Audion 应用访问。官方给出的启动方式是一条 Docker 命令：

docker compose up -d

预期结果是启动 audion-server 和 audion-frontend 两个容器，服务在 :8080 就绪。

服务端能力包括：

适用条件：你需要一台常开的设备、基本的 Docker 使用能力，以及接受自行维护服务端。如果只是单机听歌，不需要这一步。

免费与付费的边界

Audion 的定位是"free for everyone"，免费版包含完整音乐播放、同步歌词、主题和插件，以及默认包含的基础账号同步。页面同时存在一个 Pro 入口和"Supporter"捐赠档位，说明捐赠用于维持项目独立并解锁账号同步相关权益。具体价格页面未在资料中给出，因此无法判断 Pro 的收费标准和功能差异——如果你需要账号同步的完整能力，应直接查看其 Pro 页面确认。

怎么判断它是否适合你

• 适合：你有成规模的无损或本地音乐收藏，重视隐私和离线使用，愿意接受开源工具，或希望自建服务远程访问。
• 需要额外确认：你依赖账号同步、需要特定平台独占功能，或不愿维护 Docker 服务端。
• 不适合：你的音乐主要来自流媒体平台曲库，且没有本地文件。

一个具体的判断方法是：先整理出一个音乐文件夹，用播放器扫描一次，检查标签识别、封面补全和搜索速度是否符合预期，再决定是否投入时间搭建远程访问。

Ogg Vorbis is a free, open-source lossy audio codec, usually stored in .ogg or .oga files. MPD (Music Player Daemon) lists Ogg Vorbis among the formats it supports, so you can add Ogg Vorbis files to your MPD library and play them like any other track — provided your MPD build includes a Vorbis decoder. Choose Ogg Vorbis when you want smaller files than FLAC and a patent-free alternative to MP3; choose FLAC when you need lossless audio, or Opus when you want better quality at low bitrates.

What Ogg Vorbis actually is

Ogg Vorbis is two things commonly referred to by one name:

• Vorbis — the audio codec that compresses sound by discarding information the ear is unlikely to notice (lossy compression).
• Ogg — the container format that holds the Vorbis stream, along with metadata such as track title, artist, and album.

Because it is open source and free of the licensing restrictions that historically surrounded MP3, Ogg Vorbis became a common choice for open-source projects, game soundtracks, and independent music distribution.

Typical file extensions:

A .ogg file is not automatically Vorbis — the Ogg container can also carry other codecs — but in practice most .ogg music files are Vorbis.

How MPD handles Ogg Vorbis

MPD is a server-side music player: it runs as a background process, indexes your music library, and plays audio on request from a client. Its documented format support includes Ogg Vorbis alongside MP3, FLAC, WavPack, and Opus.

The practical flow looks like this:

1. You place Ogg Vorbis files in a directory MPD can read. MPD scans configured music directories and builds its database from the files it finds.
2. MPD detects the format. When it encounters an .ogg file, it identifies the stream and routes it to the Vorbis decoder.
3. The decoder produces audio. MPD sends the decoded audio to its configured output (local sound device, network stream, etc.).
4. A client controls playback. You use an MPD client — the project's news mentions myMPD, for example — to browse, queue, and play tracks.

The key dependency is the decoder. If MPD was built without Vorbis support, the file will be recognized as a file but cannot be decoded into sound.

Common playback problems and how to troubleshoot

No sound, but the track appears to play

• Check that MPD has an audio output enabled and that the output device is correct.
• Confirm the file is actually Vorbis and not another codec inside an .ogg container.
• Verify the file plays in another player; if it does not, the file itself may be corrupt.

"Unsupported format" or the track is skipped

• The MPD build likely lacks a Vorbis decoder. Rebuild or install a package compiled with Vorbis support.
• Check the MPD log for decoder-related messages — MPD reports why it rejected a file.

Files exist but do not appear in the library

• The directory may not be included in MPD's music directory configuration.
• The database may need to be updated after adding new files.

Metadata is missing or wrong

• Ogg Vorbis stores tags in Vorbis comments rather than ID3. Some older tools write tags incorrectly; re-tagging the file with a Vorbis-aware editor usually fixes it.

Choosing between Ogg Vorbis, MP3, FLAC, and Opus

Use the same criteria for each: file size, audio quality, compatibility, and licensing.

Conditional guidance:

• Choose Ogg Vorbis if you want a free, open format and your players support it.
• Choose MP3 if you need the widest possible hardware and software compatibility.
• Choose FLAC if you are archiving and want no quality loss, and storage space is not a constraint.
• Choose Opus if you want the best quality per bit and your playback chain supports it.

MPD's documented format list covers all four, so within MPD the decision is mainly about your library's size, quality needs, and how you use the files outside MPD.

A daemon is a program that runs in the background without a user interface, typically starting at boot or on demand and continuing to run until it is stopped or the system shuts down. You interact with it indirectly—through a client, a socket, a config file, or a command—rather than by clicking around inside the daemon itself. Music Player Daemon (MPD) is a concrete example: it is a server-side application that plays music, and you control it from a separate client.

What makes a process a daemon

The defining trait is not what the program does but how it runs:

• No controlling terminal. A daemon detaches from the terminal that launched it, so closing that terminal does not kill it.
• Long-lived. It stays resident and waits for requests or events instead of doing one job and exiting.
• Started automatically or on demand. It can be launched at boot by the init system, or started manually and left running.
• Controlled indirectly. Configuration files, control commands, sockets, or client programs are how you talk to it.

A foreground app, by contrast, owns your terminal or window, shows you output directly, and usually ends when you close it.

How a daemon starts and keeps running

The typical lifecycle looks like this:

1. Launch. Either the system's init/service manager starts it at boot, or you start it yourself.
2. Detach. The process separates from the controlling terminal and often changes its working directory and file descriptors so it is not tied to a login session.
3. Listen or wait. It opens the resources it needs—network sockets, files, devices—and then idles until something requests work.
4. Serve repeatedly. It handles requests or performs its function continuously.
5. Stop. It ends when explicitly told to stop, when it crashes, or at shutdown.

Not every daemon follows every step identically, but the pattern of "start, detach, wait, serve" is the common shape.

MPD as a worked example

Music Player Daemon fits the model well. Per its own description, MPD is "a flexible, powerful, server-side application for playing music." The "daemon" in the name is literal: it runs in the background as a server, and the music playback happens inside that server process rather than in a window you watch.

The split of responsibilities is the useful part to understand:

So when you press play in a client, you are not playing audio in the client. You are asking the daemon to do it. That is the essence of a daemon: the work happens in a background service, and your interface is a thin layer on top.

MPD's ecosystem reflects this. The project's news feed, for instance, announces client releases such as "myMPD 26.0.0 has been released"—a separate front-end that talks to the daemon. The daemon and its clients evolve independently, which is only possible because the daemon is a standalone background service.

Daemons vs. foreground apps vs. system services

These terms overlap, so it helps to separate them:

• Daemon — a background process, traditionally detached from a terminal. The term is about the process's relationship to the user and the terminal.
• Foreground application — a program you run and interact with directly; it typically ends when you close it.
• System service — a broader category of managed background functionality. On modern systems, services are usually supervised by the init system, and many services are daemons. A service can also be something the supervisor manages that is not strictly a classic detached daemon.

In practice, "daemon" and "service" are often used loosely for the same thing. The precise distinction is that "daemon" describes the process style, while "service" describes the role of providing ongoing functionality to the system or other programs.

The trailing "d" naming convention

You will notice many daemons end in d:

• httpd — web server daemon
• sshd — secure shell daemon
• crond — scheduled-task daemon
• mpd — Music Player Daemon

The "d" is shorthand for "daemon." It is a convention, not a requirement—plenty of daemons do not use it—but it is a fast visual cue that a program is meant to run in the background.

Why this matters when you use MPD

Understanding the daemon model explains MPD's behavior:

• Closing your client does not stop the music. The daemon keeps playing because playback lives in the daemon, not the client.
• Multiple clients can connect. Because the daemon is a server, several front-ends can talk to the same instance.
• Configuration is separate from control. You set up the daemon once (music directories, outputs, connection details), then control it repeatedly from clients.
• The daemon must be running first. If it is not started, clients have nothing to connect to.

That last point is the most common practical snag: a client that cannot reach MPD is usually a client looking for a daemon that is not running or is listening somewhere the client is not configured to find.

Quick way to decide if something is a daemon

Ask three questions:

1. Does it run without a window or terminal you watch?
2. Does it keep running and wait for requests or events?
3. Do you control it through a client, command, socket, or config rather than direct interaction?

If the answers are yes, you are dealing with a daemon—and MPD is a clean example of one.