Playback Architecture
How Mossca processes your music — from file to output.
The Playback Chain
Every audio player follows a signal path:
Music File → Decode → Process → Output → Device
What matters is not just what exists in this chain, but how it is handled.
Mossca is designed to make every step explicit, controlled, and predictable.
What Actually Affects Sound Quality
Source Material Comes First
The recording and mastering define the upper limit of sound quality.
No playback software can restore missing information.
Mossca focuses on helping you understand your library — not masking its characteristics.
Sample Rate Handling
When file and device sample rates differ, conversion is required.
This can happen:
- Inside the player
- Inside the system
Uncontrolled conversion introduces unnecessary processing and inconsistency.
Mossca performs conversion explicitly, in a known place, with predictable behavior.
Signal Processing
Many players introduce:
- EQ
- Loudness normalization
- DSP effects
- Automatic upsampling
These may be useful, but they alter the original signal.
Mossca avoids all signal-altering processing in the default path.
What Software Can Control
- Decoding accuracy
- Resampling behavior
- Signal path consistency
- Output routing
What Software Cannot Control
- Recording quality
- Mastering decisions
- DAC analog design
- Headphones, speakers, room acoustics
Mossca Playback Architecture
Mossca is built around one principle:
Keep the signal path minimal, visible, and deterministic.
No Hidden Processing
No EQ. No enhancement. No automatic DSP.
What you hear is the decoded signal — not post-processed audio.
Bit-Perfect Integrity
Mossca preserves integrity in two stages:
- Decode integrity: accurate PCM from source
- Output integrity: unchanged delivery to device
When conditions allow, both are preserved end-to-end.
Controlled Sample Rate Conversion
Conversion is not avoided — it is controlled.
Mossca ensures:
- Conversion happens in one place
- Behavior is predictable
- No hidden system interference
Shared vs Exclusive Output
On macOS, audio can follow two different paths:
Shared Path (System Audio)
- Routed through Core Audio
- Mixed with system sounds
- May involve system-level resampling
Best for:
- Built-in speakers
- Casual listening
- General system usage
Exclusive Mode (Direct Output)
- Bypasses system audio layer
- Direct hardware access
- No system mixing or interference
Best for:
- External DAC setups
- Critical listening
DSD and High-Resolution Playback
Mossca supports both:
- DSD -> PCM (for built-in output)
- DoP (for external DACs)
Playback behavior adapts based on your device.
Signal Path Visibility
Mossca exposes the full playback path in real time.
You can see:
- Source format
- Conversion steps
- Output mode
- Device path
No hidden stages. No assumptions.
Design Philosophy
Transparency
You should always know what happens between file and output.
Respect the Source
Playback should reflect the recording — not modify it.
Reduce Unnecessary Processing
Every extra step can alter the signal.
Mossca keeps the path as simple as possible.
In Practice
The goal is simple:
Respect the recording.
Deliver it accurately.
Avoid unnecessary processing.