GITNUXSOFTWARE ADVICE
Music And AudioTop 10 Best Music Manager Software of 2026
Ranked roundup of music manager software for libraries and playlists, with technical comparisons of Roon, MusicBee, MediaMonkey, plus Mp3tag.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Mp3tag is the best pick if you manage a local music library that needs repeatable, precise tag and artwork normalization, whereas AIMP fits when you want Windows playback plus efficient file-level tag and playlist maintenance in one desktop app.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Mp3tag
Expression-based batch operations that generate or transform tag fields at scale from filenames and existing values.
Built for fits when local libraries need repeatable tag normalization and artwork updates..
JRiver Media Center
Editor pickMedia Center’s rule-driven playlist generation and library views keep listening lists aligned with tag changes.
Built for fits when a local library needs one tool for playback, metadata, and streaming sync..
MediaMonkey
Editor pickSmart playlist criteria use evolving library data like play state and tags to keep playlists current.
Built for fits when a Windows-based music library needs repeated tag cleanup and rule-driven playlist updates..
Related reading
Comparison Table
Mp3tag
vertical specialistUniversal audio tag editor for editing metadata of audio files.
Expression-based batch operations that generate or transform tag fields at scale from filenames and existing values.
Mp3tag is built around batch normalization of tags across many files at once, including common ID3 fields and format-specific tag sets. Artwork can be embedded per item or applied from a folder source, and tag values can be derived from expressions that combine existing fields and filename patterns. Duplicate detection and tag conflict handling help when a library contains multiple near-matches from different sources.
A practical tradeoff is that Mp3tag does not act as a full media server or player, so it does not handle playback logic or server-based library synchronization. It fits best when a local library or portable device needs rapid metadata cleanup, such as standardizing album names and writing consistent artwork before playlist creation in another application.
- +Batch tagging runs on folders and file selections without extra tooling
- +Expression-driven fields help derive tags from filenames and existing metadata
- +Artwork embedding updates tag images directly inside audio files
- +Duplicate scanning surfaces likely repeats for targeted cleanup
- –No built-in music library database for cross-app synchronization
- –Automation relies on scripting and expressions that take time to learn
- –Rules can misapply tags when filename patterns are inconsistent
- –Advanced workflows are less convenient than single-field editors for quick edits
Audio archivists
Normalize tags across imported collections
Cleaner library ordering
Home library managers
Embed artwork in lost-cover files
Correct album art everywhere
Show 2 more scenarios
Playlist curators
Fix metadata before playlist rules
Fewer playlist misfires
Resolve tag conflicts so downstream playlist generation can rely on consistent fields.
Collectors migrating libraries
Deduplicate near-matching tracks
Reduced redundancy
Use duplicate detection to identify likely repeats and then apply controlled tag corrections.
Best for: Fits when local libraries need repeatable tag normalization and artwork updates.
More related reading
JRiver Media Center
vertical specialistMultimedia application for organizing and playing audio and video files.
Media Center’s rule-driven playlist generation and library views keep listening lists aligned with tag changes.
JRiver Media Center is a strong match for users who want the library, playback engine, and metadata editing tools inside one local application instead of chaining multiple utilities. Its library can ingest folder hierarchies, apply metadata updates, and keep playlists and views consistent as files change. The platform also supports transcoding for playback compatibility when endpoints require different formats.
A tradeoff appears in governance and ongoing maintenance, because large tag and playlist rule sets benefit from careful configuration to avoid unintended propagation. JRiver works best when the library has consistent file naming or a clear mapping scheme, and when regular watch-folder ingestion is used to bring in new music without constant manual intervention.
- +Single app covers cataloging, playback, metadata editing, and sync workflows
- +Rule-based playlists help maintain consistent listening rotations
- +Transcoding supports playback compatibility across mixed output devices
- +Network streaming uses the same library rather than duplicating databases
- –Complex configurations can require repeated tuning for large tag rule sets
- –Advanced workflows depend on understanding JRiver-specific configuration screens
- –Large media catalogs can make UI responsiveness feel slower during edits
- –Some automation scenarios require more manual validation than expected
Home audiophile households
Stream one curated library to multiple rooms
Consistent playback across devices
Music librarians
Normalize tags and fix conflicts at scale
Fewer tag errors over time
Show 2 more scenarios
Collectors with large libraries
Maintain playlists as the folder structure evolves
Less playlist rework
Automated playlist rules and ingestion keep views updated as new files enter the library.
Users managing mixed formats
Convert on demand for endpoint support
Fewer playback interruptions
Transcoding enables playback of files that do not match an output device’s supported formats.
Best for: Fits when a local library needs one tool for playback, metadata, and streaming sync.
MediaMonkey
vertical specialistMedia player and music library organizer for Windows.
Smart playlist criteria use evolving library data like play state and tags to keep playlists current.
MediaMonkey manages a local music library by reading audio files, indexing metadata, and mapping files into navigable collections like artists, albums, and custom playlists. The tool’s tag editing and metadata normalization workflow covers practical operations such as ID3 tag edits, batch actions, and resolving tag inconsistencies during rescan or import cycles. Playlist generation supports criteria-driven smart playlists, which is useful for maintaining rules that track changes when tags or play counts change.
A tradeoff for MediaMonkey is that its strongest automation and integration depth target Windows library lifecycles, with less consistent cross-platform coverage than some alternatives. It fits best when the primary need is repeated local library cleanup and playlist rule maintenance, not server-grade multi-user governance or API-first orchestration. For example, maintaining a deduplicated and normalized tag set can be more efficient when the same ingestion and rescan steps are reused across library updates.
- +Smart playlists update from tag changes and play history
- +Batch tag editing workflow reduces manual cleanup time
- +Add-ons extend library automation without rebuilding core setup
- +Strong library indexing for large local music collections
- –Windows-first workflow can complicate multi-OS library habits
- –Advanced automation often depends on add-on availability
Home music listeners
Keep playlists current after tag edits
Less manual playlist maintenance
Music library curators
Normalize tags across folders
Cleaner, consistent metadata
Show 2 more scenarios
Windows-based media power users
Iterative library cleanup and resync
Fewer stale library entries
Repeated scans and synchronization workflows help keep files and library indexes aligned.
Tinkerers and automators
Extend behavior with add-ons
More workflow coverage
Add-ons can add automation around ingestion, organization, or playback management tasks.
Best for: Fits when a Windows-based music library needs repeated tag cleanup and rule-driven playlist updates.
foobar2000
vertical specialistAdvanced freeware audio player for Windows with extensive tagging capabilities.
Smart playlist engine driven by metadata fields plus reusable selection rules, with advanced formatting control for views.
foobar2000 is a local-first music manager for Windows that focuses on fast library browsing, playback, and tag editing inside a highly configurable desktop app. The core workflow centers on a metadata-first data model with reusable selection logic for library views and smart playlists.
Its extensibility via add-ons supports advanced DSP chains, conversion workflows, and ingestion patterns such as folder-based importing. For large libraries, it offers strong throughput through native indexing, efficient search and filtering, and granular formatting controls for tags and lists.
- +Extensibility through add-ons for DSP, conversions, and playlist tooling
- +Highly configurable library views with flexible tag formatting
- +Efficient indexing and search for large local music libraries
- +Scriptable behavior via community components for batch operations
- –Automation and governance depend on external add-ons rather than built-ins
- –Best workflows require careful configuration of tags and file layout
- –Cross-device sync is not a first-class built-in workflow
- –Some advanced capabilities arrive through community components
Best for: Fits when local libraries need precise tag editing, smart playlists, and add-on driven automation without a server.
Strawberry Music Player
vertical specialistAudio player and music collection organizer for Unix and Windows systems.
ID3 tag editing integrated into the library workflow, so changes update the same browsing and playlist context without exporting data.
Strawberry Music Player is a desktop music manager that builds and maintains a local library index, then drives playlist playback from that index. It supports metadata workflows like ID3 tag editing, cover art display, and genre and artist browsing that follow the tags Strawberry finds on disk.
It also includes ingestion workflows such as folder hierarchy mapping and library synchronization so additions and changes propagate into the library view. Automation is handled mainly through repeatable library scans and playlist rules rather than a server-side API or governance controls.
- +Fast local library scanning with incremental rescan behavior
- +ID3 tag editing workflows for artists, albums, and track fields
- +Playlist generation that uses stored metadata for repeatable criteria
- +Stable folder hierarchy mapping that mirrors disk organization
- –No published automation API for playlist provisioning or external governance
- –Limited library deduplication controls for near-identical files
Best for: Fits when a local music library needs tag editing, organized browsing, and offline playlist playback.
Quod Libet
vertical specialistGTK-based music player and library manager with advanced search capabilities.
Metadata tag editor paired with Python plugins enables custom batch transformations beyond built-in tools.
Quod Libet is a local-first music manager built around a flexible tag editing and library browsing workflow. It supports playlist creation rules, keyboard-driven navigation, and automated scanning of local collections so metadata stays current during daily use.
Media handling centers on reading and writing tags and performing library actions through extensible Python plugins. Quod Libet is also tied to a specific audio-player and tag-focused user model rather than a server-based media management stack.
- +Python plugin system enables custom tag workflows and UI extensions
- +Rule-based playlists operate from metadata fields without external tooling
- +Library scanning updates tags from folders and file metadata sources
- +Tightly integrated tag editor supports multi-field edits quickly
- –GUI navigation and tag rule syntax can feel rigid for non-power users
- –No built-in server-grade remote sync for mobile-first playback
- –Automation depends on plugin knowledge for advanced batch operations
- –Complex media management features require third-party components
Best for: Fits when tag-heavy libraries need fast local editing, rule playlists, and Python-based automation.
Audirvana
vertical specialistHigh-resolution music player and library manager for macOS and Windows optimized for audiophile playback quality.
Audirvana’s playback pipeline controls reduce processing steps during streaming from local libraries.
Audirvana focuses on local-first music playback management with tight control over audio output, rather than building a media-server ecosystem. Library ingestion emphasizes tag-driven organization and local synchronization so that playlists and playback remain consistent across typical desktop setups.
The app supports metadata editing workflows and audio playback tuning features aimed at minimizing processing during playback. Compared with tools that center on server-based syncing, Audirvana’s strength is the hands-on playback and library management loop on a single machine.
- +Playback-focused library loop with audio output controls that stay close to files
- +Tag editing and organization workflows support practical metadata hygiene
- +Good fit for offline desktop use without needing a server layer
- +Playlist handling stays straightforward for folder-based music collections
- –Limited enterprise governance controls like RBAC and audit logs for shared libraries
- –Fewer automation hooks than media-manager competitors aimed at complex normalization
- –Not designed around server-based media serving and multi-client synchronization
- –Automation for large-scale migrations and deduplication is less comprehensive
Best for: Fits when a single desktop setup needs reliable tag management and playback-centric library control.
AIMP
consumerFreeware audio player for Windows with a built-in music library organizer, tag editor, and format converter.
Configurable DSP effects chain that stays tied to playback output across formats and tags.
AIMP is a Windows desktop music manager built around file-level playback control, audio processing, and tag maintenance.
ID3 tag editing supports multi-file operations and cover art updates that reduce manual cleanup time.
Playlist creation and refinement are handled in-app, with playback consistency aided by ReplayGain tagging and gapless playback behavior.
- +ID3 tag editing with bulk actions and multi-file workflows
- +DSP chain supports repeatable playback sound shaping
- +ReplayGain handling helps normalize loudness across files
- +Cue sheet parsing improves compatibility for disc-oriented audio
- –No built-in cloud sync or server-based library coordination
- –Advanced library deduplication controls are limited
- –Smart playlist criteria can feel less expressive than database-driven managers
Best for: Fits when local libraries need efficient file-level tag and playlist maintenance.
beets
API-firstCommand-line music library manager that automatically tags, organizes, and enriches local music collections using MusicBrainz metadata.
Config-driven ingestion rules that can rerun safely for consistent metadata cleanup and file layout changes.
beets performs automated music library normalization by scanning folders, matching tracks, and applying tag and file changes through repeatable rules. It is distinct for its rule-based pipeline that can rename files, deduplicate entries, and resolve tag conflicts during ingestion.
It also supports playlist generation from criteria and integrates external metadata sources through configurable plugins. Its local-first workflow emphasizes batch operations and repeatable reruns instead of interactive management alone.
- +Rule-based ingestion can normalize tags and filenames in batch runs
- +Library deduplication reduces duplicates using configurable matching heuristics
- +Playlist generation uses configurable criteria tied to library metadata
- +Plugin architecture extends metadata sources and transformation steps
- –Initial configuration of rules and plugins takes time for stable results
- –Complex tag conflict resolution can require careful rule ordering
- –Advanced automation workflows depend on Python-based plugin development
- –Remote orchestration and cross-device sync control are limited
Best for: Fits when local music libraries need repeatable tag normalization and playlist rule automation.
Lidarr
vertical specialistMusic collection manager that monitors artists, automatically downloads new releases, and organizes library metadata.
Release quality profiles combined with per-artist monitoring drive repeatable selection and synchronization decisions.
Lidarr manages music collections by syncing artists, albums, and releases based on configurable search and download rules. It organizes library ingestion around a folder hierarchy mapping and keeps your library synchronized through continuous monitoring of download status and filesystem changes.
Automation centers on RSS feed monitoring, release scoring, and per-artist quality profiles so new material lands with consistent naming and tagging workflows. Admin control relies on a local web UI plus an API that supports programmatic management of configured artists, folders, and history.
- +Quality profiles and release scoring apply consistent standards across artists
- +Folder hierarchy mapping keeps files aligned to artist and album structures
- +API supports automated artist management and monitoring integrations
- +RSS feed monitoring reduces manual checks for new releases
- –Library health depends on correct path mapping and consistent naming inputs
- –Advanced automation often requires careful rule tuning and iterative configuration
- –Playlist and listening workflows are not the focus compared with library management
- –Multi-source metadata normalization coverage can be uneven across releases
Best for: Fits when collecting large music libraries needs automated downloads, folder mapping, and API-driven governance.
Conclusion
After evaluating 10 music and audio, Mp3tag stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
How to Choose the Right music manager software
Music manager software in this guide focuses on local library organization and repeatable metadata hygiene through tools like Mp3tag, MediaMonkey, and MusicBee-style workflows reflected across the list. The covered options include Mp3tag for expression-based batch tag transformation, JRiver Media Center for rule-driven playlists inside one catalog and playback app, and beets for config-driven ingestion and deduplication.
This guide also contrasts Windows-first libraries like MediaMonkey and cross-OS, extensible approaches like foobar2000 and Quod Libet. Lidarr is included for folder mapping and API-driven release collection governance, while Strawberry Music Player and Audirvana represent local-first tag editing and playback-centric library control.
Music manager software for libraries, tagging, and rule-based playlist maintenance
Music manager software is the set of tools that builds and maintains a music library by scanning files, normalizing metadata, and updating playlists when tags or play history change. Tools like Mp3tag and beets emphasize repeatable tag normalization from filenames and existing tag values, including batch operations that can transform many fields at once.
For playlist behavior and ongoing consistency, JRiver Media Center and MediaMonkey use rule-driven playlist logic that stays aligned with library changes, including tag edits and listening history updates. Local-first editors like Strawberry Music Player and Quod Libet keep tag editing inside the same library context, so updates show up immediately in browsing and rule-based playlists without external exports.
Category evaluation criteria for music manager software
Music manager software earns its place by keeping library metadata and playlists consistent after changes in filenames, tags, or play history. The most decisive capabilities are repeatable batch operations, rule-driven playlist criteria, and integration paths that prevent tag drift between tools.
This guide treats playlist maintenance as a system behavior, not a single UI feature. It also weights automation and extensibility surfaces like expressions, rule engines, and plugin APIs because they determine how far metadata workflows can scale without manual edits.
Expression or rule engines for batch tag normalization
Mp3tag supports expression-based batch operations that derive or transform tag fields from filenames and existing values. beets applies config-driven ingestion rules that rerun safely for consistent metadata cleanup and file layout changes.
Playlist generation that stays aligned with tag and play-state changes
JRiver Media Center uses rule-based playlist generation and library views so listening lists stay aligned with tag changes. MediaMonkey smart playlists update from tag changes and play history, which keeps playlist membership current.
In-editor tag editing that updates library context immediately
Strawberry Music Player integrates ID3 tag editing into the library workflow so browsing and playlist context reflect edits without exports. Quod Libet pairs metadata tag editing with Python plugins so rule playlists operate from metadata fields inside the same local workflow.
Extensibility through add-ons or plugins for automation and transformations
foobar2000 extends automation and conversions through add-ons for DSP, conversions, and playlist tooling. Quod Libet extends metadata workflows with a Python plugin system that supports custom batch transformations beyond built-in tools.
Deduplication and conflict handling for library migration and cleanup
beets includes library deduplication using configurable matching heuristics, which reduces duplicate entries during normalization. Strawberry Music Player has limited library deduplication controls for near-identical files, which makes cleanup harder when variants differ subtly.
Governance controls and automation surfaces beyond local playback
Lidarr provides API-driven governance for automated selection and synchronization decisions using per-artist monitoring and quality profiles. Audirvana is playback-centric and lacks enterprise governance controls like RBAC and audit logs for shared libraries.
How to choose based on library workflow, automation depth, and control
Selection depends on the workflow that dominates daily use, either bulk tag normalization or rule-driven playlist maintenance. It also depends on whether the library stays local and file-based or needs API-driven governance for ongoing synchronization decisions.
The strongest fit comes from matching automation philosophy to the library’s pain points. Some tools focus on local-first editing and playback loops, while others focus on rule engines and repeatable ingestion to reduce drift over time.
Choose the normalization engine that matches the source of truth
Pick Mp3tag if tag values must be derived from filenames and existing metadata using expression-driven batch transformations on selected files and folders. Pick beets if the source of truth is a repeatable config and rerunnable ingestion rules that normalize tags and filenames while also supporting deduplication.
Align playlist behavior with how the library changes day to day
Pick JRiver Media Center if playlists must stay aligned with tag changes inside one catalog and playback app using rule-based playlist generation and library views. Pick MediaMonkey if playlist membership must update from both tag changes and play history through smart playlist criteria.
Decide between local-first tag editing inside the same browsing context and exported workflows
Pick Strawberry Music Player if ID3 tag editing must update the same library browsing and playlist context without exporting data. Pick Quod Libet if Python-based plugin automation is required for custom batch transformations while rule playlists run from metadata fields.
Select extensibility based on whether automation must be built from code or from built-in tooling
Pick foobar2000 if add-on-based DSP, conversions, and playlist tooling must be orchestrated without a server. Pick Quod Libet if Python plugins must extend UI and batch tag workflows beyond built-in operations.
Account for governance needs when music collection decisions go beyond a single machine
Pick Lidarr if release quality profiles and per-artist monitoring must drive automated downloads with folder hierarchy mapping under API-driven governance. Pick Audirvana if the objective is playback-centric control over processing steps and local tag hygiene without RBAC or audit logs for shared libraries.
Check platform constraints against library habits before committing
Pick MediaMonkey if a Windows-first workflow fits repeated tag cleanup and rule-driven playlist updates on that platform. Pick foobar2000 if add-on driven local workflows fit flexible library views and tag formatting control without depending on server coordination.
Who this music manager software category fits best
Music managers in this guide fit users who maintain large local music libraries with ongoing changes to tags, filenames, and listening behavior. The best candidates are people who need repeatable metadata cleanup and rule-based playlists that keep updating after library edits.
The list also serves collectors whose workflow spans download, folder mapping, and governance decisions that continue after initial setup. Tools like Lidarr fit that model more directly than playback-centric local managers.
Local library owners running repeatable tag cleanup pipelines
Mp3tag and beets both focus on batch normalization so libraries remain consistent after filename or tag edits. beets adds library deduplication heuristics that reduce duplicates during normalization runs.
Listeners who rely on smart playlists that must track tag and play-state changes
JRiver Media Center keeps listening lists aligned with tag changes through rule-based playlist generation. MediaMonkey smart playlists update from tag changes and play history so playlist membership stays current.
Tag editors who want edits to reflect instantly in the same browsing and playlist context
Strawberry Music Player integrates ID3 tag editing into the library workflow so changes appear in browsing immediately. Quod Libet keeps rule playlists operating from metadata fields without exporting data.
Users building automation through add-ons or Python plugins
foobar2000 relies on add-ons for DSP, conversions, and playlist tooling that extend beyond built-in automation. Quod Libet uses a Python plugin system to implement custom tag workflows and UI extensions.
Collectors who need API-driven governance and monitored downloads
Lidarr applies quality profiles and release scoring while per-artist monitoring drives ongoing synchronization decisions. This model depends on folder hierarchy mapping and correct path inputs for library health.
Common mistakes when adopting music manager software
Many library problems start with choosing the wrong automation philosophy for the current library state. Another failure mode is assuming a local editor will handle governance or cross-tool synchronization without an integration plan.
The following mistakes show up repeatedly when users scale from small manual tag fixes into rule-based library maintenance at volume.
Buying a local tag editor and expecting cross-app synchronization
Mp3tag edits tags in files but has no built-in music library database for cross-app synchronization, so tag changes do not automatically propagate into other catalogs. For persistent coordination, choose a tool with library-wide views and rule-based behavior like JRiver Media Center.
Overbuilding playlist rules without testing how tag edits change membership
JRiver Media Center playlist rules can require repeated tuning for large tag rule sets, which breaks expectations when tag normalization is still evolving. MediaMonkey smart playlists update from tag changes and play history, so membership changes can appear after normalization rather than staying static.
Assuming automation is built-in when the workflow requires add-ons or plugins
foobar2000 makes automation and governance depend on external add-ons rather than built-ins, so automation coverage depends on what add-ons get installed. Quod Libet provides Python plugins, but GUI navigation and tag rule syntax can feel rigid when rules are complex.
Ignoring library health risks from path mapping and naming inputs
Lidarr library health depends on correct path mapping and consistent naming inputs, which can cause downloads to land in wrong folders. beets can reduce duplicates with matching heuristics, but complex tag conflict resolution still needs careful rule ordering.
Expecting enterprise governance controls in playback-centric tools
Audirvana focuses on a playback pipeline with audio output controls and lacks governance controls like RBAC and audit logs for shared libraries. Lidarr provides API-driven governance instead of relying on manual coordination.
How We Selected and Ranked These Tools
We evaluated Mp3tag, JRiver Media Center, MediaMonkey, foobar2000, Strawberry Music Player, Quod Libet, Audirvana, AIMP, beets, and Lidarr by scoring features at 40%, then ease and value at 30% each. Features emphasized whether the tool can keep playlists and metadata aligned through rule-driven playlist logic, expression-based batch operations, or config-driven ingestion.
Ease and value emphasized workflow fit such as Mp3tag running batch tagging directly on folder selections and beets rerunning ingestion rules for consistent cleanup without manual rework. Mp3tag placed highest because its expression-driven batch tagging can transform many tag fields from filenames and existing values in repeatable runs, which reduces cleanup effort while staying local-file focused.
Frequently Asked Questions About music manager software
How does Mp3tag handle batch metadata edits compared with beets ingestion rules?
Which tool is better for keeping playlists aligned with tag changes over time: JRiver Media Center or MediaMonkey?
What breaks if a user relies on local scans only for library synchronization: Strawberry Music Player vs Lidarr?
How does foobar2000’s metadata-first data model affect smart playlist performance in large libraries?
Which tool supports Python-based metadata automation out of the box: Quod Libet or Mp3tag?
How does beets deduplicate tracks and resolve tag conflicts during ingestion?
When does AIMP’s ReplayGain tagging matter compared with Audirvana playback pipeline controls?
What security and admin governance features differ between MediaMonkey and Lidarr for multi-user control?
How do watch-folder style ingestion workflows compare between Lidarr and Strawberry Music Player?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→In this category
Music And Audio alternatives
See side-by-side comparisons of music and audio tools and pick the right one for your stack.
Compare music and audio tools→