Consider two add-on tools - Custom Nodes and SQL Editor - then adapt the following SQL (an example result to follow in a separate post).
Album Artist with more than ?? Albums
Purpose
The objective of this query is to provide a curated view of "Power Artists" while filtering out compilation-heavy entries. By excluding "Various Artists" and similar tags, the node focuses strictly on individual performers or bands who have a significant, dedicated presence in your collection (over ?? albums), preventing soundtrack or "Best Of" collections from cluttering the results. Vary the threshold value to suit your library.
Clean SQL
/* Select all columns from the Albums table
excluding generic 'Various' artist tags
*/
SELECT * FROM Albums
WHERE Artist NOT IN ('Various', 'Various Artists', 'Compilations', 'Unknown')
AND Artist IS NOT NULL
AND Artist <> ''
AND (
/* Threshold Filter: Only artists with more than 50 albums */
SELECT COUNT(*)
FROM Albums AS Sub
WHERE Sub.Artist = Albums.Artist
) > 50
ORDER BY (
/* Sort Logic: Most prolific artists first */
SELECT COUNT(*)
FROM Albums AS Sub
WHERE Sub.Artist = Albums.Artist
) DESC,
Artist ASC,
Album ASC;
Limitations
SQL Editor limits its output to 1000 records AND the central output area does not allow cut & paste.
Custom Nodes displays "Album" queries with album tiles AND therefore looses the sort order of the previous query.
Using DB SQLite can be used (on a back-up copy of your MM5..DB) to over-come these limitations i.e. will show more than 1000 records sorted as defined AND can be exported to a CSV.
Provenance & Compatibility
Designed for SQLite environments (like MediaMonkey), this script avoids the need for complex GROUP BY statements that often break "Album" node displays. The core logic uses a correlated subquery in the ORDER BY section; it dynamically calculates the total album count for each artist and uses that integer as the primary sorting weight. One issue with have here is that the Album display used for Custom Nodes over-rides our sort order.
The
Clean SQL above will cut & paste into both Custom Nodes 1.1.5 and SQL Editor 1.0.2
References:
https://www.mediamonkey.com/addons/brow ... ql-editor/
https://www.mediamonkey.com/addons/brow ... tom-nodes/
SQL061 in my document Media Monkey SQL Deep Dive
Consider two add-on tools - Custom Nodes and SQL Editor - then adapt the following SQL (an example result to follow in a separate post).
[b][u]Album Artist with more than ?? Albums[/u][/b]
[b][i]Purpose[/i][/b]
The objective of this query is to provide a curated view of "Power Artists" while filtering out compilation-heavy entries. By excluding "Various Artists" and similar tags, the node focuses strictly on individual performers or bands who have a significant, dedicated presence in your collection (over ?? albums), preventing soundtrack or "Best Of" collections from cluttering the results. Vary the threshold value to suit your library.
[b][i]Clean SQL[/i][/b]
/* Select all columns from the Albums table
excluding generic 'Various' artist tags
*/
SELECT * FROM Albums
WHERE Artist NOT IN ('Various', 'Various Artists', 'Compilations', 'Unknown')
AND Artist IS NOT NULL
AND Artist <> ''
AND (
/* Threshold Filter: Only artists with more than 50 albums */
SELECT COUNT(*)
FROM Albums AS Sub
WHERE Sub.Artist = Albums.Artist
) > 50
ORDER BY (
/* Sort Logic: Most prolific artists first */
SELECT COUNT(*)
FROM Albums AS Sub
WHERE Sub.Artist = Albums.Artist
) DESC,
Artist ASC,
Album ASC;
[b][u]Limitations[/u][/b]
SQL Editor limits its output to 1000 records AND the central output area does not allow cut & paste.
Custom Nodes displays "Album" queries with album tiles AND therefore looses the sort order of the previous query.
Using DB SQLite can be used (on a back-up copy of your MM5..DB) to over-come these limitations i.e. will show more than 1000 records sorted as defined AND can be exported to a CSV.
[b][i]Provenance & Compatibility[/i][/b]
Designed for SQLite environments (like MediaMonkey), this script avoids the need for complex GROUP BY statements that often break "Album" node displays. The core logic uses a correlated subquery in the ORDER BY section; it dynamically calculates the total album count for each artist and uses that integer as the primary sorting weight. One issue with have here is that the Album display used for Custom Nodes over-rides our sort order.
The [i][b]Clean SQL[/b][/i] above will cut & paste into both Custom Nodes 1.1.5 and SQL Editor 1.0.2
References:
https://www.mediamonkey.com/addons/browse/item/sql-editor/
https://www.mediamonkey.com/addons/browse/item/custom-nodes/
SQL061 in my document Media Monkey SQL Deep Dive