Website profiles · Technology insights · Alternatives

audionplayer.com Paid content

Categories: Music & Audio

A native, community-driven music player for your personal collection. Synced lyrics, beautiful themes, and powerful plugins. 100% free, no tracking, works offline.

Visit website

Updated: 2026-10-01 20:38 Language: English (default) Access: Normal

Profile views 5 Outbound visits 0
Audion - Open Source Home for Your Local Library Full homepage screenshot
Editorial Review

Website Review

What is Audion?

Audion is a free, open-source music player for your own local music files, not a streaming service. It runs natively on Windows, macOS and Linux (with an Android version mentioned on the site) and is built around the idea that you point it at folders you already own, it reads the tags, and it organizes the library for you — no account, no ads, no telemetry, and it works offline.

What it actually does

  • Library scanning and organization — it scans your folders, reads tags and arranges things automatically.
  • Synced lyrics — line-by-line lyrics that follow playback, fetched automatically.
  • Themes — full CSS control, so you can use a community preset or write your own.
  • Plugins — community-built extensions such as Last.fm scrobbling and Discord Rich Presence.
  • Audio features — a 10-band equalizer, crossfade, gapless playback, multiple audio outputs, and lossless formats including FLAC and WAV up to 192 kHz with no resampling.
  • Speed — the site emphasizes instant search across large libraries.

Who it suits

It fits someone with a real music collection on disk — ripped CDs, Bandcamp purchases, a NAS full of FLAC — who wants a fast desktop player without signing into anything. If your listening is mostly discovery through a subscription catalog, this is not that; Audion plays what you already have.

The server angle

There is also an Audion Server component you can run on a home server, Raspberry Pi or VPS, described as a single Docker command. It streams in multiple formats, can transcode on demand (for example FLAC to MP3 via an ffmpeg cache), supports the Subsonic API so clients like Symfonium, Feishin and DSub can connect, and handles multi-user setups with isolated libraries and JWT auth. That turns Audion from a desk-bound player into something you can reach from a browser or the app while away from home.

Trade-offs to weigh

The cost is setup effort and self-reliance: you manage your files, and features like lyrics or metadata quality depend on sources and community plugins rather than a single curated catalog. The payoff is control — your library stays local, formats are not resampled, and the interface is customizable down to the CSS.

A practical next step

Start with the desktop app on one machine and a single music folder to see whether the scanning and tag handling match how your files are organized. If that works and you want access from other devices, add Audion Server later — the Subsonic API support means you can keep using clients you may already have. The project's own pages are at Audion, and if you want to compare self-hosted library servers more broadly, Navidrome is a well-known alternative in the same space.

How do I set up Audion Server to stream my music library remotely?

Audion Server is the self-hosted companion to the Audion desktop player: you run it on a machine that holds your music, and then reach that library from a browser, the Audion app, or any Subsonic-compatible client. The site describes it as a lightweight Rust backend that can run on a home server, Raspberry Pi, or VPS, started with a single Docker Compose command.

What you need first

  • A machine that stays on and can reach your music files — a home server, a Raspberry Pi, or a VPS.
  • Docker and Docker Compose installed on that machine.
  • Your music library organised in folders on that machine (Audion's scanner reads tags and organises automatically).
  • A decision about access: same network only, or over the internet.

The basic setup path

  1. Put your music on the host machine and note the folder path.
  2. Create a docker-compose.yml that mounts that folder into the server container and exposes a port (the site's example uses :8080).
  3. Run docker compose up -d. The site's sample output shows an audion-server and audion-frontend container starting, then "Audion Server ready on :8080".
  4. Open the web interface at that address, create your account, and point the server at your music folder if it isn't already mounted.
  5. Add users if other people need their own libraries — the server supports JWT auth and multi-user setups with isolated libraries per user.
  6. Connect a client: the Audion app itself, a browser, or a Subsonic-compatible app such as Symfonium, Feishin, or DSub.

Reaching it from outside your home

The site mentions tunnel support specifically so you don't need port forwarding. That matters because opening a port to the internet exposes the service directly; a tunnel keeps the connection outbound from your server. If you'd rather not run a tunnel, a VPN into your home network is the other common route. Either way, treat the login as the only thing standing between the internet and your files, so use a real password and keep the server updated.

Practical trade-offs

Choice Good for Cost
Raspberry Pi at home Low power, cheap, always on Limited CPU for on-demand transcoding
Home server / NAS Large libraries, fast local access You manage uptime and backups
VPS Reliable remote access Storage cost, and your music leaves your home
Tunnel vs. port forward Simpler, safer remote access Extra moving part to configure

On-demand transcoding (the site gives FLAC → MP3 via ffmpeg with a cache) is the feature that decides your hardware. If you stream lossless to a phone on mobile data, transcoding saves bandwidth but costs CPU; a Pi can struggle with several simultaneous streams, while direct-playing FLAC avoids that entirely.

A concrete scenario

Say your library is 400 GB of FLAC on a NAS. Run Audion Server on a Pi 4 with the NAS folder mounted read-only, expose it through a tunnel, and use the Subsonic API from a phone app. At home, direct-play FLAC; on the road, let the server transcode to MP3. Your desktop Audion install keeps using the local files directly, so nothing changes there.

If you want the exact compose file and configuration options rather than this outline, the project's own documentation is the place to start: Audion.

What plugins are available for Audion and how do I install them?

Audion's plugin system is community-driven, and the site names Last.fm scrobbling and Discord Rich Presence as examples. It points to a plugin browser ("Browse all plugins") rather than a fixed list, so the exact catalog grows over time — check that page for the current set. Separately, the site lists built-in Integrations (Last.fm, MusicBrainz, Plex, Jellyfin, Spotify playlist import, Discord, Navidrome). Those are not the same as plugins: integrations appear to be supported connections handled by the app itself, while plugins are add-ons you install.

What the site confirms

  • Plugins: community-built; Last.fm and Discord Rich Presence are the named examples.
  • Integrations: the services listed above, described as working with tools you already use.
  • Themes: full CSS control, with community presets or your own — a separate customization path from plugins.
  • Server/streaming: Audion Server runs via Docker (one command shown), supports the Subsonic API, and works with clients like Symfonium, Feishin, and DSub.

How to install plugins

The page shows a "Loading plugins..." state and a "Browse all plugins" link but does not document installation steps in the supplied material. Practical route:

  1. Open the plugins section in the app (or the plugin browser on the site) and pick a plugin.
  2. Install or enable it from there, then configure it — for scrobbling or Discord presence you'll typically authorize your account once.
  3. Restart or reload if the plugin doesn't appear immediately.

If a plugin needs account credentials (Last.fm, Discord), expect a one-time sign-in flow; Audion itself requires no account for playback.

Choosing between a plugin and an integration

Need Likely path
Scrobble plays, show Discord status Plugin
Connect Plex, Jellyfin, Navidrome, import Spotify playlists Integration
Change look and feel Theme (CSS)
Stream to other devices/apps Audion Server + Subsonic API

Next step

If you're setting up a home server, decide first whether you need plugins at all — the Subsonic API and Docker server cover most remote-listening needs. For desktop-only use, start with the plugin browser, enable Last.fm or Discord, and confirm playback and lyrics work before adding more. Compare against Navidrome if you mainly want a lightweight server, or Jellyfin if you already manage video and music in one library.

Can Audion sync lyrics and fetch metadata for my local music files?

Yes. Audion is built around local files, and the page lists both automatic synced lyrics and metadata lookups as core features. Lyrics are described as line-by-line and time-synced to playback and fetched automatically, while MusicBrainz integration is listed for retrieving metadata and high-resolution cover art. Your files stay on your machine; there is no sign-in requirement for playback.

H3 What this looks like in practice

  • You point Audion at your music folders, and it scans them, reads existing tags, and organizes the library.
  • For tracks with lyrics available, the player fetches timed lyrics and scrolls them with the song.
  • For metadata, MusicBrainz integration fills in artist, album, and cover art where your tags are incomplete or inconsistent.

H3 Important trade-offs

  • Synced lyrics depend on an external lyrics source, so obscure, self-released, or non-English tracks may come back without timing or without lyrics at all. Unsynchronized text is a common fallback.
  • Metadata matching works best when your files have at least rough artist and title tags. Untagged files, compilations, and classical box sets are where automatic matching usually needs manual correction.
  • Fetched lyrics and metadata are not the same as embedded tags. If you move the library to another player, corrections you make inside Audion may not travel unless you write them back to the files.

H3 A quick test before committing Copy 20–30 representative tracks into a separate folder, point Audion at it, and check three things: how many tracks get timed lyrics, how many get correct cover art, and how many need manual fixes. That ratio tells you more about your library than any feature list.

If you want a second opinion on how well your library matches, MusicBrainz's own database is the source Audion queries, so checking a few problem albums there first shows whether the data exists to be fetched: MusicBrainz. If you also keep a server-based library, the page notes Jellyfin, Plex, and Navidrome integrations, which let Audion act as a client alongside your existing setup.

Is Audion a good alternative to Spotify for playing my own music collection?

Yes, for a local library it is a strong alternative to Spotify — with one important caveat: it is not a streaming catalog. Audion plays files you already own, while Spotify gives you access to millions of tracks you do not. If your goal is to play, organize and stream your own collection without ads or accounts, Audion fits that job well. If you want discovery and new releases, it does not replace Spotify.

Where Audion fits

  • Your own files: it scans folders, reads tags and organizes the library automatically, so you point it at a music drive rather than manage playlists by hand.
  • Sound quality: FLAC, WAV and high-res up to 192 kHz are supported without resampling, which matters if you have lossless rips.
  • Lyrics and look: synced line-by-line lyrics are fetched automatically, and themes are fully CSS-customizable — useful if you want a player that matches your setup.
  • Offline and private: no accounts, no telemetry, works offline. Good for a laptop used on planes or a machine you would rather not tie to a cloud account.
  • Extras: a 10-band EQ, gapless playback, crossfade, Last.fm scrobbling and Discord presence via plugins.

Audion vs. Spotify for a personal collection

Need Audion Spotify
Play your own files Yes, core purpose Local files only, awkward
Lossless/high-res FLAC, WAV, up to 192 kHz Limited by plan and device
New music discovery No catalog Core strength
Accounts/tracking None required Required
Offline Native Downloaded tracks only
Remote access Audion Server, Subsonic API Spotify Connect

The streaming question

Audion Server is the piece that makes it competitive with Spotify's convenience: run it on a home server, Raspberry Pi or VPS with one Docker command, then reach your library from any browser or the app. It supports on-demand transcoding (for example FLAC to MP3 via ffmpeg cache), the Subsonic API, JWT auth with multi-user libraries, and tunnel support so you avoid port forwarding. That is the difference between a desktop player and a genuine Spotify substitute for your own music.

A concrete scenario

You have 400 GB of FLAC on a NAS. Install Audion on your desktop for home listening, run Audion Server on the NAS, and use the Subsonic API to play the same library through Symfonium or Feishin on your phone. Last.fm scrobbling keeps your listening history intact, and nothing leaves your network unless you choose a tunnel.

How to decide

Choose Audion if your library is already large, you care about lossless playback and privacy, and you are willing to run a small server for mobile access. Stay with Spotify if discovery, shared playlists and a catalog you do not have to maintain are the point. Many people reasonably run both — Spotify for finding music, Audion for owning it.

How does Audion handle privacy and offline playback compared to other music players?

Audion's privacy and offline story is simple: it is a local-first player with no accounts, no telemetry and no sign-in, so your library stays on your machine and playback does not depend on a connection. That differs from streaming-first services such as Spotify, where offline listening means downloading licensed tracks inside a logged-in account, and from cloud locker products that require uploading your files before you can hear them anywhere.

Offline playback. Audion scans your folders, reads tags and plays local files directly, including lossless formats such as FLAC and WAV. Gapless playback, instant search and the 10-band EQ all work without a network. Lyrics are fetched automatically, so treat synced lyrics as the one feature that may need a connection the first time; cached lyrics should then display offline. For a commute or a flight, that means no "unavailable offline" gaps as long as the files are already on the device.

Privacy. No accounts, no telemetry and no tracking are stated product features. Your listening history lives locally unless you deliberately add a plugin such as Last.fm scrobbling or Discord presence, which shares data with those third parties. The optional Audion Server changes the picture: it is self-hosted on a home server, Raspberry Pi or VPS, with JWT auth and isolated libraries per user. Your music then leaves the house only through infrastructure you control, and tunnel support avoids opening router ports.

Where it fits against alternatives.

Need Audion Streaming service Cloud locker
Plays your own files offline Yes, local-first Only downloaded catalogue Usually needs upload/sync
Account required No Yes Yes
Data leaves your device Only if you enable a plugin or self-host Yes, by design Yes, to the provider
Synced lyrics Automatic Varies by track/region Often limited
Cross-platform Windows, macOS, Linux, Android Broad Broad

Decision criterion. Choose Audion if you already own a music collection and want playback, lyrics and theming without an account or an internet dependency. Choose a streaming service if discovery and a licensed catalogue matter more than file ownership. Choose a self-hosted setup only if you are comfortable running Docker and maintaining a server; otherwise the desktop or Android app alone covers most offline listening.

Next step. Install the desktop app, point it at one music folder, and confirm that tags, artwork and lyrics resolve correctly before moving your whole library. If you later want browser access from other devices, evaluate Audion Server separately, since it introduces the only real privacy trade-off: your files become reachable over the network you configure.

Related questions

More questions →
Spotify Alternatives: What Do Free Music Streaming Services Actually Offer?

If you want a Spotify alternative, the first thing to check is what the free tier actually gives you — not what the marketing page promises. Most free music streaming services cap audio quality, insert ads, limit skips, or block offline playback. Octave, a free streaming service described on octavestreaming.com, claims to remove those specific limits: no ads between songs, no paywall on lossless, and no cap on skips. That makes it a useful reference point for judging any alternative. Below is how to compare options on the dimensions that actually affect daily listening, plus what to verify before you switch.

The four limits that define a "free" tier

When comparing Spotify alternatives, ignore the feature list and check these four constraints first. They determine whether a free service is usable as a daily driver.

Limit What to check Why it matters
Ads Ads between songs, or only before/after a session? Mid-song ads break albums and mixes
Audio quality Highest bitrate on the free tier; is lossless included? Free tiers often cap at 128–160 kbps
Skips Per-hour cap, or unlimited? Caps make playlists unusable
Offline Can you download for flights or dead zones? Determines whether it works without signal

Octave's page states its free tier includes lossless FLAC and Dolby Atmos (where a track was mixed for it), no ads, and no skip cap, with quality options at 128 kbps (Data Saver), 320 kbps (High), and FLAC lossless. Treat those as claims to verify in the app rather than guarantees — but they are the right questions to ask of any alternative.

Quality tiers: what "free" usually means

Most free tiers sit at the bottom of the quality ladder. A service that offers lossless for free is unusual, so it is worth understanding the tiers before you commit.

  • Data Saver (128 kbps) — for weak signal or long commutes. Audible, but compressed.
  • High (320 kbps) — the ceiling for most free tiers elsewhere.
  • Lossless (FLAC) — bit-for-bit what the studio sent out, per Octave's description.
  • Dolby Atmos — spatial audio where the song was mixed for it.

If lossless matters to you, confirm it is available on the free tier and not gated behind a "premium" label. The word "premium" appears in Octave's own branding ("Premium music, always free"), so read the pricing page rather than assuming — no payment details are listed in the available material.

Features worth checking beyond audio

Sound quality is only half the decision. These are the features that show up in daily use:

  • Synced lyrics — word-by-word timing that follows the singer syllable by syllable, with tap-to-jump on a line. Octave also offers a "Sing" mode that pulls vocals down via a slider, using real instrumentals where available.
  • AutoMix — beat-matched transitions between tracks.
  • Listening parties — a shared link where everyone hears the same second of the same song.
  • Podcasts — Octave says it carries the Apple Podcasts catalogue in the same player, with the same queue and speed controls.
  • Wrapped-style stats — top songs, artists, and hours available on demand, not once a year.

For a straight Spotify comparison, the migration path matters as much as playback. Octave states you can paste a Spotify export or a CSV to bring your library over, and download it for offline listening. That is the feature to test first, because a failed import is the most common reason people abandon a switch.

How to migrate and verify in practice

  1. Export your playlists from Spotify. Use Spotify's export option or a CSV of your library.
  2. Paste the export into the new service. On Octave this is described as a paste-and-import flow.
  3. Check the match rate. Look for missing tracks — catalogue gaps are the most common failure point, and no service matches 100%.
  4. Download a playlist for offline use. This confirms offline playback works on your device before you rely on it.
  5. Test on a second device. Cross-device sync is where free tiers often quietly break.
  6. Play a lossless track and check the quality indicator. Confirm you are actually getting FLAC, not a downscaled stream.

Common traps when switching

  • Catalogue gaps. Smaller services miss tracks, especially regional or niche releases. Check your most-played albums before committing.
  • Regional limits. Availability and quality tiers can differ by country; the page does not list region restrictions, so test from where you actually listen.
  • "Free" with a premium label. A service can brand itself "premium" while offering a free tier — read the pricing page instead of inferring from the tagline.
  • Offline caps. Some free tiers allow downloads only on paid plans. Verify before a flight.
  • Podcast and queue behavior. If you listen to podcasts and music in one queue, confirm the alternative handles both in the same player.

Who should switch, and who should not

Switch if your main complaints are ads, skip caps, or quality ceilings — and you are willing to re-check your library for missing tracks. A free tier with lossless, no ads, and no skip cap addresses exactly those pain points.

Stay if your library is deep in regional or niche catalogues that a smaller service may not carry, or if you depend on Spotify-specific social features and integrations that do not transfer. The migration tools move playlists, not everything around them.

The practical move: run the six-step migration test above on a free alternative, compare the match rate against your real listening, and decide from that — not from the feature list.

What Does "Open Source" Mean for a Zen Cart Online Store?

Open source means the software's source code is publicly available, so anyone can inspect, modify, and redistribute it. Zen Cart, the platform running this reptile supply store, is open-source e-commerce software: the store owner can read and change the code, and no license fee is paid to a vendor. That matters to a small shop because it removes per-sale or monthly software fees and allows deep customization — but it also means the owner (or a developer they hire) handles hosting, updates, and security. Note that "open source" here describes the store software, not the reptile foods and supplements sold on it.

Open source in plain terms

Proprietary store platforms typically charge a subscription or a percentage of sales and keep their code closed. Open-source platforms publish the code under a license that permits use and modification. In practice, for a store like this one:

  • No license fee. You pay for hosting and your own time, not for permission to run the software.
  • Full access to the code. Layouts, checkout flow, and product pages can be changed beyond what a theme editor allows.
  • Community development. Fixes and add-ons come from contributors and other store owners, not only from one company.

What it looks like on this store

The page evidence shows a typical Zen Cart storefront: category navigation (Bee Pollen, Cat Grass, Chia Seeds, Dandelion, Sprouting Seeds, Supplements), an "All Products" listing, reviews, and an information block with About Us, Shipping & Returns, Privacy Notice, Conditions of Use, Order Status, Site Map, Gift Certificate FAQ, and Discount Coupons. That structure — categories, reviews, coupons, gift certificates, order status — is what the platform provides out of the box. The store also publishes care guides (Russian Tortoise Care, Box Turtle Care, Redfoot Tortoise Care) and growing instructions, which are content pages the owner added rather than built-in store features.

Benefits for a small pet supply shop

  • Cost control. No platform subscription means a low fixed cost that doesn't scale with order volume.
  • Custom catalog logic. A shop selling seeds, dried weeds, and supplements by weight can adjust product options, units, and shipping rules directly in the code.
  • Content and commerce in one place. Care guides and growing instructions sit alongside the catalog, which supports the store's stated role of helping customers find foods for herbivore reptiles.
  • No vendor lock-in on data. You can export and migrate your catalog if you decide to move.

Trade-offs to plan for

Concern What it means in practice
Hosting You arrange your own web host and domain; the platform doesn't host the store for you
Security updates You apply patches yourself or pay someone to; skipping them is the main risk
Technical maintenance Theme changes, add-ons, and upgrades need someone comfortable with PHP-based code
Support Help comes from forums, documentation, and paid developers rather than a single support line
Add-on quality Third-party modules vary; test before relying on them for checkout or payments

Deciding whether it fits your store

Choose an open-source cart like Zen Cart if you want no license fees, need code-level customization, and have either technical skills or a developer you can call. Choose a hosted subscription platform instead if you'd rather not manage hosting, patches, and upgrades, and you're comfortable paying monthly for that convenience. A middle path works for many small shops: run the open-source cart on managed hosting that handles server updates, and keep a developer on retainer for store-level changes.

If you're evaluating this specific store as a model, the useful signal is that a niche reptile supply shop can run a full catalog, reviews, coupons, and care content on open-source software without a platform fee — the cost shifts from subscriptions to maintenance.

本地音乐播放器能做什么?如何选择适合自己的开源音乐播放器?

本地音乐播放器解决的核心问题只有一个:把你硬盘上已有的音乐文件,变成一个能搜索、能整理、能跨设备播放的私人音乐库。如果你有大量 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 就绪。

服务端能力包括:

能力 说明
多格式流式传输 FLAC、MP3、AAC、OGG 等
按需转码 通过 ffmpeg 将 FLAC 转为 MP3 并缓存
Subsonic API 兼容 Symfonium、Feishin、DSub
远程访问 支持隧道,无需端口转发
认证与多用户 JWT Auth,每个用户库相互隔离
资源占用 Rust 后端,可跑在树莓派上

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

免费与付费的边界

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

怎么判断它是否适合你

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

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

What Is Local Music and How Do You Play Your Own Collection?

Local music means audio files stored on hardware you control — your computer's drive, an external disk, a NAS, or a home server — rather than tracks streamed from a subscription catalog. You play it with a music player that scans folders, reads embedded tags, and builds a library from those files. The main trade-off: you supply and organize the files, but in return you get offline playback, no ads or tracking, and lossless formats like FLAC or WAV up to 192 kHz without resampling. This guide covers what counts as local music, how to pick a player, how to set up remote streaming, and where things commonly break.

What counts as "local music"

A file is local music when it lives on storage you own and the player reads it directly, with no streaming account in the loop. Common formats include FLAC, WAV, MP3, AAC, and OGG. Your player identifies each track by the metadata tags inside the file — artist, album, title, track number, cover art — not by the folder name, which is why clean tags matter more than a tidy folder tree.

Two things are worth separating:

  • Playback — a desktop or mobile app opens the files on that device.
  • Streaming your own library — a server process runs on one machine and sends your files to other devices over your network or the internet. The files are still yours; only the delivery changes.

What a local player actually does

A capable local player handles more than pressing play. Based on what Audion documents, the typical feature set looks like this:

Capability What it means in practice
Library scanning Watches your folders, reads tags, organizes automatically
Synced lyrics Line-by-line lyrics that follow playback, fetched automatically
Lossless support FLAC, WAV, high-res up to 192 kHz, no resampling
Playback quality Gapless playback, 10-band EQ, crossfade, multiple output options
Themes Full CSS control — use a community preset or write your own
Plugins Last.fm scrobbling, Discord presence, and other community add-ons
Accounts None required; files stay local, no telemetry, no sign-in

Not every player offers all of these. When comparing options, check the rows you actually care about rather than the longest feature list.

Choosing a player: match it to your setup

The right choice depends on your operating system, how large your library is, and whether you want to reach your music from other devices.

  • Desktop-only, single machine — any solid local player works. Prioritize fast search across large libraries and gapless playback if you listen to albums.
  • Cross-platform consistency — Audion runs on Windows, macOS, and Linux from one codebase with the same features on each, plus an Android app. If you move between machines, that consistency saves reconfiguration.
  • Remote access — you need a server component, not just a player. Audion Server runs on a home server, Raspberry Pi, or VPS and is reachable from any browser or the Audion app.
  • Ecosystem fit — if you already run Plex, Jellyfin, or Navidrome, check whether the player integrates with them before switching. Audion lists integrations with Last.fm, MusicBrainz, Plex, Jellyfin, Spotify (playlist import), Discord, and Navidrome.

If privacy and offline use are your priorities, favor players that state plainly that no account or telemetry is involved. Audion describes itself as free and open source with no accounts, no ads, and offline operation.

Setting up remote streaming from your own library

If you want your collection available outside the house, the pattern is the same across server-based players: run a server on always-on hardware, point it at your music folders, then connect from a client.

With Audion Server, the documented flow is:

  1. Run the server on a home server, Raspberry Pi, or VPS. The docs give a single Docker command:
    docker compose up -d
    
    Expected result: the server and frontend containers start, and the server reports ready on port 8080.
  2. Confirm it's reachable by opening the server in a browser or connecting the Audion app.
  3. Authenticate — the server uses JWT auth with multi-user support and isolated libraries per user, so each account sees only its own music.
  4. Stream — the server handles multi-format streaming (FLAC, MP3, AAC, OGG and more) with on-demand transcoding, for example FLAC to MP3 via an ffmpeg cache when a client can't handle the original.
  5. Connect other clients — the Subsonic API means apps like Symfonium, Feishin, and DSub can talk to the same server.

For access from outside your network, the docs mention tunnel support so you don't need to open ports. The backend is written in Rust and is light enough to run on a Raspberry Pi.

Common problems and how to check them

Files don't show up in the library. The player reads tags, not filenames. Check that the files carry proper metadata and that the folder is inside a scanned location. Unusual or corrupted tags are a frequent cause.

A track won't play or sounds wrong. Verify the format is supported. Lossless files like FLAC and WAV at high sample rates are handled by players that explicitly support them; a player that resamples will still play the file but not at full quality.

Remote streaming fails. Work through it in order: is the server process actually running, is the port reachable, are the credentials valid, and does the client support the file's format or need transcoding enabled? Transcoding settings and authentication configuration are the two most common culprits.

Lyrics don't appear. Synced lyrics are fetched automatically by players that support them, but the match depends on track metadata. Inconsistent artist or title tags break the lookup.

What you give up, and what you keep

Going local means you're responsible for acquiring files, backing them up, and keeping tags consistent. In exchange, playback works offline, there are no ads or tracking, lossless and high-resolution audio play without resampling, and the files remain yours regardless of what any service does with its catalog. If you also run a server, you get the convenience of streaming without handing your library to a third party.

Audion is free to download and use, with donations supporting development and unlocking account sync perks; the free tier includes full playback, synced lyrics, themes, plugins, and basic account sync. Check the current download page for your platform — Windows, macOS, Linux, and Android are listed — and confirm the feature set matches your priorities before committing your library to it.

How Do You Play Arx Fatalis on Linux With Arx Libertatis?

Arx Libertatis is an improved, cross-platform, open-source engine for Arx Fatalis, the 2002 first-person RPG/dungeon crawler/immersive sim from Arkane Studios. To play on Linux, you install Arx Libertatis (official Linux builds are provided), then point it at a copy of the original Arx Fatalis game data — the engine itself does not include the game. You need to own or otherwise obtain Arx Fatalis or its demo before you can play.

What Arx Libertatis actually is

Arx Libertatis is a port and modernization of the Arx Fatalis engine, based on the publicly released Arx Fatalis source code and available under the GPL 3+ license. Version 1.2.1 supports modern systems, brings the game to new platforms, and removes bugs and limitations of the original release.

Two things follow from that:

  • The engine is free and open source. You can download, inspect, and redistribute the code under the GPL.
  • The game data is not included. The license covers the engine only. The art, audio, levels, and other assets remain part of the commercial game, so you must supply them yourself.

The game itself features crafting, melee and ranged combat, and a distinctive spellcasting system where you draw runes in real time to cast the spell you want.

What you need before installing

Requirement Why
A copy of Arx Fatalis (full game or demo) Provides the game data Arx Libertatis loads
Arx Libertatis for Linux The engine that runs the game on your system
A Linux desktop with working graphics drivers The engine renders the original 3D game

The original game is sold through storefronts such as GOG.com, the Microsoft Store, and the Bethesda Store, and it also has a demo. Any of these gives you the data files the engine needs.

Installing Arx Libertatis on Linux

Arx Libertatis provides official builds for Windows and Linux. Beyond those, it has been packaged for macOS (Homebrew), FreeBSD, DragonFly BSD, NetBSD, OpenBSD, Haiku, and Pandora, and will likely compile and work on other operating systems.

On Linux, you have two practical routes:

Option 1: Use a distribution package

Check whether your distribution ships Arx Libertatis in its repositories. If it does, install it through your normal package manager. This is the least manual path and keeps updates tied to your system.

Option 2: Use the official Linux build

Download the Linux build from the project's download page and unpack it. This works regardless of whether your distribution packages the engine, and it lets you run a specific version such as 1.2.1.

If neither fits, the source is available on GitHub, so you can build it yourself — the project notes it will likely compile on other systems too.

Pointing the engine at your game data

The engine needs to find the Arx Fatalis data files. The general flow is:

  1. Install or unpack Arx Libertatis using one of the routes above.
  2. Locate your Arx Fatalis data. If you bought the game from a storefront, the installer places the data files somewhere on disk; if you have the demo, it comes as its own set of files.
  3. Tell Arx Libertatis where that data is when you first launch it, or place the data where the engine expects it.
  4. Launch the game and confirm it reaches the main menu.

The expected result at each step is simple: the engine starts, finds the data, and loads the game rather than exiting with a "data not found" style error.

If the game does not run

Check these in order:

  • Data path is wrong. The most common failure is the engine not finding the Arx Fatalis data. Re-check the path you gave it.
  • You installed the engine but not the game. Arx Libertatis alone cannot run — it has no assets of its own.
  • Graphics/driver problems. Since the engine targets modern systems, most rendering issues trace back to drivers or to running an old build. Try the current release (1.2.1).
  • Wrong build for your system. Make sure you grabbed the Linux build, not the Windows one, if you installed manually.

Where to go next

The project plans to keep improving and modernizing the engine and to enable community customizations and mods. If you want to follow development or get help, the project links to its GitHub repository, Mod DB page, and community forums such as the TTLG Forum and the GOG.com forum. There are also community projects built around the game, including the Arx Insanity Mod and other Arx mods.

Website Overview

Several search or sharing settings need attention. Together they may make snippets, preview images or preferred URLs less consistent across platforms.

Domain and Registration

The domain was registered less than a year ago and has limited historical evidence to assess. Transfer-protection status is present, helping reduce the risk of unauthorized domain transfers. The domain uses the common .com extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by dns-parking.com, indicating managed DNS hosting. MX records point to the Hostinger Email email service. SPF and DMARC are configured. DKIM status is unknown. TXT records include verification markers for Google. Such markers may also remain after a service stops being used. DNSSEC signatures were not detected, so this additional DNS authenticity protection is not confirmed.

TLS and Certificates

The certificate uses an RSA 2048-bit public key, offering broad client compatibility. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The response lacks these common security headers: CSP, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, clickjacking protection. CORS permits any origin to read this response. This is common for public resources; sensitive responses need narrower handling. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value Vercel.

Technology Stack Analysis

The public page identifies Next.js, Google Analytics, Vercel without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

The meta description has 163 characters and may be shortened in search results. The canonical URL points to another host: https://audionplayer.com. Search engines may consolidate indexing signals there. Twitter Card metadata is configured. The title has 48 characters, within a common display range. The observed directives allow indexing and link following.

Hosting and Email

DNSdns-parking.com
HostingVercel
EmailHostinger Email
Location United States flagUnited States 216.198.79.65

User reviews (0)

  • No reviews yet.

Pages, Search and Sharing

Meta descriptionA native, community-driven music player for your personal collection. Synced lyrics, beautiful themes, and powerful plugins. 100% free, no tracking, works offline.
Canonical URLhttps://audionplayer.com
LanguageEnglish (default)
Twitter Cardsummary_large_image
All bots 1 allowed · 0 disallowed
  • Allow/

Registration details RDAP / WHOIS

RegistrarHOSTINGER operations, UAB
Registered2026-01-14
Expires2027-01-14
Domain statusclient transfer prohibited
Nameserversns1.dns-parking.com、ns2.dns-parking.com
DNSSECunsigned

DNS records

TypeNameValueTTLPriority
Ae62a584a626eabcb.vercel-dns-017.com216.198.79.65300—
Ae62a584a626eabcb.vercel-dns-017.com64.29.17.65300—
MXaudionplayer.commx1.hostinger.com144005
MXaudionplayer.commx2.hostinger.com1440010
NSaudionplayer.comns1.dns-parking.com86400—
NSaudionplayer.comns2.dns-parking.com86400—
TXTaudionplayer.comgoogle-site-verification=r_xQd4LBX8X791eD6_UGa4dQFhOejo2CtOcB4UDDzlI14400—
TXTaudionplayer.comv=spf1 include:_spf.mail.hostinger.com ~all14400—
CNAMEwww.audionplayer.come62a584a626eabcb.vercel-dns-017.com14400—
DMARC_dmarc.audionplayer.comv=DMARC1; p=none3600—

TLS and certificates

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectwww.audionplayer.com
IssuerLet's Encrypt
Valid until2026-11-07T01:31 · Remaining when checked: 36 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HeaderValue
content-typetext/html; charset=utf-8
cache-controlpublic, max-age=0, must-revalidate
serverVercel
strict-transport-securitymax-age=63072000
access-control-allow-origin*

Identified technologies

Next.jsGoogle AnalyticsVercel