In this article
Music Assistant separates crossfading into three responsibilities:
- Smart Fades analyzes tracks.
- Queue settings select transition behavior.
- Player output settings handle delivery to the device.
A separate system, Loudness Analysis, measures audio for volume normalization rather than supplying Smart Crossfade data.
This control map explains why enabling Smart Fades does not make every transition smart, why Smart Crossfade can fall back to a timed fade, and why Music Assistant may send a queue as one continuous stream.
Scope: This explanation is based on Music Assistant’s documentation. No playback, performance, compatibility, or listening tests were performed. The cited pages do not identify a specific Music Assistant release.
The control map
| Responsibility | Controlling component |
|---|---|
| Analyze beats, downbeats, key, and energy | Smart Fades provider |
| Select Standard or Smart Crossfade | Queue settings |
| Set Standard and fallback fade duration | Queue settings |
| Allow crossfading within the same album | Queue settings |
| Send the queue as one continuous stream | Player output and capability handling |
| Enable volume normalization | Queue settings |
| Measure values used for normalization | Loudness Analysis provider |
The key distinction is between producing analysis data and choosing to use it. Smart Fades produces track data; the queue’s crossfade mode determines whether a transition uses that data.[^1]
What Smart Fades analyzes
The optional Smart Fades provider analyzes each track for:
- Beats
- Downbeats
- Musical key
- An energy curve
Smart Crossfade uses this information to construct beat-matched, EQ-aware transitions. Music Assistant describes those transitions as beat-aligned and energy-aware, with high and low frequencies blended separately.[^1]
These are capability descriptions, not guarantees about audible results. The documentation does not disclose the analysis model, its accuracy, or how long analysis should take.
Music Assistant says the optional provider is automatically added and enabled when its minimum resource requirements are met. Those documented requirements are:
- An AVX2-capable x86 CPU or an ARM64 CPU
- At least 4 GB of RAM
- At least two CPU cores
- In a virtualized environment, host CPU-model passthrough when the host supports AVX2[^1]
These are eligibility requirements, not measured performance figures. They do not predict resource use or whether analysis will finish before a given transition.
How analysis becomes available
The documentation describes background scanning for tracks supplied by specified local file-system providers, including SMB, NFS, and WebDAV. In-library tracks are also analyzed during playback through the streaming pipeline.[^1]
When an unanalyzed track plays, Music Assistant performs the analysis and stores the result with that track. Completed analysis is reused on subsequent plays.[^1]
Analysis may still be running when playback reaches the next track. If it has not finished, Music Assistant uses Standard Crossfade for that transition.[^1] Smart Crossfade is therefore conditional on the required analysis being available; the documentation gives no completion-time estimate.
Standard and Smart Crossfade are queue modes
Crossfade mode belongs to the queue. It can be configured globally through Player Queues settings or for one queue through that player’s queue settings.[^1][^2]
| Mode | Documented behavior |
|---|---|
| Standard Crossfade | A time-based crossfade with a configurable duration |
| Smart Crossfade | A transition using Smart Fades beat, key, and energy data |
Enabling the Smart Fades provider and selecting Smart Crossfade are distinct controls: the provider produces the analysis, while queue settings select the crossfade mode.[^1]
Fallback crossfade duration
The queue’s Fallback crossfade duration setting controls both:
- The duration of Standard Crossfade.
- The duration used when Smart Crossfade falls back to Standard Crossfade.[^1]
The supplied documentation does not state the default, units, or allowed range for this setting.
Same-album transitions
By default, Music Assistant skips crossfading between tracks from the same album. This applies to both Standard and Smart Crossfade.[^1]
The Allow crossfade between tracks from the same album setting overrides that default.[^1] The documentation does not explain how Music Assistant resolves album identity when metadata is incomplete or conflicting.
Where flow mode fits
Flow mode is a player-output behavior, not an analysis method or crossfade mode. It sends the whole queue to a player as one continuous stream instead of delivering one track at a time.[^2]
When crossfade is enabled and a player cannot provide gapless playback itself, Music Assistant automatically switches to flow mode. The continuous stream lets Music Assistant stitch tracks together so the crossfade can occur.[^1][^2]
Flow mode can therefore support crossfading, but it does not produce the beat, key, or energy data used by Smart Crossfade.
Its availability and defaults vary by player and provider:
- Not every player exposes every setting.
- Providers can choose defaults or hide settings that do not apply.
- Several providers enable flow mode because their devices work better that way.
- A player that always streams the queue in one continuous stream may not expose a flow-mode setting.[^2]
The general documentation does not establish compatibility for any specific player.
Flow mode also has a display trade-off. Because the device may receive the queue as one long track, most players stop showing per-track information. Music Assistant offers optional ICY metadata injection that can restore some information, although handling varies among players.[^2]
Loudness Analysis serves a different purpose
Loudness Analysis measures different properties:
- Integrated loudness in EBU R128 LUFS
- Loudness range in EBU R128 LU
- True peak in ITU-R BS.1770-4 dBTP[^3]
Music Assistant uses these measurements for volume normalization, which is switched on or off per queue.[^3] Smart Crossfade instead uses the Smart Fades provider’s beat, key, and energy data.[^1]
The documented division of responsibility is therefore:
- Smart Fades analysis supplies data for Smart Crossfade.
- Loudness Analysis supplies measurements for volume normalization.
- Queue settings choose crossfade behavior and control normalization.
- Player handling determines when a continuous flow stream is required.
The sources describe these distinct inputs and controls, but they do not provide a complete internal audio-pipeline diagram.
Interpreting unexpected behavior
Several outcomes have straightforward documented explanations:
- A timed transition in a Smart Crossfade queue may mean analysis was unfinished, triggering Standard Crossfade.
- That timed fallback uses Fallback crossfade duration.
- Same-album tracks are not crossfaded by default in either mode.
- Flow mode may activate because the player cannot perform gapless playback itself.
- Volume normalization relies on loudness measurements, not Smart Fades beat, key, or energy data.
The documentation does not establish transition-quality guarantees, analysis completion times, measured CPU or memory use, codec effects, or compatibility with particular players.
[^1]: Music Assistant: Smart Fades Provider
[^2]: Music Assistant: Individual Player Settings
[^3]: Music Assistant: Loudness Analysis Provider
No comments yet