The meter is still moving
Picture the end-of-night studio desk: a bounce bar crawling, one headphone pad still warm, a distributor dashboard open behind the session. A fresh industry total lands like a master-bus reading. According to first-half figures reported by Music Business Worldwide, premium subscription streaming generated $3,100,000,000 for rightsholders in the US during H1 2026. That was 7.8% higher year over year. Overall industry wholesale revenue reached $5,970,000,000, up 6.9%.
Using the two published totals, premium subscriptions represented roughly 52% of the cited wholesale figure. The category also grew 0.9 percentage points faster than the overall total. The national meter is moving, while the artist-level channel remains harder to read. Aggregate rightsholder revenue cannot reveal one catalog’s share, ownership position, deal terms, or reporting delay.
Open the next statement beside the headline, and the labels on both meters immediately matter.
Two numbers, two gain stages
Premium subscription revenue isolates one revenue category. Industry wholesale revenue is the broader industry reading supplied in the same report. Their labels tell us where the measurement sits in the circuit.
Rightsholder can describe a label, a self-releasing artist, or another entity that owns or controls the relevant right. An aggregate for rightsholders therefore cannot be read as a direct artist-pay total. What reaches a given participant depends on the rights they hold and the agreements attached to those rights.
The 0.9-point difference establishes that premium subscription revenue grew faster during the period. It offers no explanation for the cause. Listener counts, service mix, pricing, and allocation cannot be inferred from these two totals alone. Treating the wholesale figure as a forecast for one musician would be like reading the mix-bus meter and guessing the vocal level.
Share is the quiet fader
A growing pool can coexist with a flat or falling result for one catalog. The catalog’s share of relevant activity may change. Release timing, territory, service mix, ownership, and listed deductions can also move an individual statement differently from the national total.
Start by aligning the comparison:
- Match H1 2026 with H1 2025, rather than a quarter or a payment date.
- Include the same masters and versions in both groups.
- Separate territory and service categories wherever the statement allows.
- Compare amounts tied to the same right, with composition and recording income kept apart.
- Note any contractual deductions exactly as the statement presents them.
Use the earning or usage period when it is supplied. Payment dates can trail the underlying activity, so mark incomplete periods as provisional. Then ask one bounded question: did the matched catalog’s revenue rise, fall, or hold steady? A clean answer is useful. Forcing one release to mirror a 7.8% national increase only muddies the comparison.
Draw the royalty signal path
Open a blank page next to the session notes and map each release as a signal path. On the recording side, list the master owner, delivery route through a label or distributor, statement account, collaborator splits, and payment destination. On the composition side, list writers, agreed shares, registration route, publisher or administrator where applicable, and the account receiving statements.
Keep those branches separate even when the same person appears in both. A songwriter who also owns a master can receive information through different systems and on different schedules. Depending on role and territory, other rights collections may need their own branch too.
Add a contact and last-checked date to every box. If a box is empty, ask the relevant collaborator, distributor, label, publisher, administrator, or society what belongs there. A blank route is easier to fix while the release folder is open than months later, when the session is archived and the email thread has gone cold.
Metadata is the patchbay
Metadata helps systems match a use with a claim. It cannot create ownership or settle a disputed split. Its value is routing. Keep one dated release record with the canonical artist name, exact track and version titles, contributor names, agreed splits, recording and release identifiers, composition registration references when assigned, delivery date, and the destination service.
Version control deserves its own lane. The album mix, clean edit, radio edit, live version, and remix should be distinguishable in the archive and in delivered data. Record which file went with which title and identifier. If anything changes after delivery, preserve the earlier entry and log the amendment instead of overwriting history.
At 2 a.m., `Mix_Final_Final2.wav` looks harmless. On a royalty statement months later, an unlabeled version can become a routing puzzle. A release sheet beside the session folder gives the next person something firmer than memory and waveform shape.
Build a dashboard that can disagree with you
A spreadsheet is enough for the first pass. Give each row a statement source, usage period if provided, payment period, territory, service or revenue category, release, track version, amount reported, listed deductions, amount payable, currency, and payment date. Preserve the source’s original category names. Add normalized labels in separate columns, so later sorting never destroys the original wording.
Keep the source statement untouched in its archive. Link each dashboard row back to a file name or statement ID. When a service combines categories or omits a field, mark it as undisclosed. A blank cell and a zero are different signals.
Per-stream calculations can serve as local diagnostics only when the service, territory, period, and right all match. The H1 headline supplies no universal per-stream rate. Combining unlike rows may produce a neat decimal with very little explanatory value.
Review quarterly. Flag a missing release, a territory that suddenly disappears, duplicate titles carrying different identifiers, an unexpected deduction, or a period that has not arrived. Treat every flag as a data-quality question first. Check the rights map, metadata record, and reporting window before assigning a story to the anomaly.
What the next report should answer
The next half-year figures will be most useful when definitions stay consistent. Watch whether premium subscription revenue continues to outpace total wholesale growth, whether the 0.9-point gap widens or narrows, and whether any published category detail explains the movement. Those are industry questions. An individual catalog needs its own matched-period answer after reporting lag is accounted for.
The current numbers cannot settle the argument over fair compensation, and they cannot predict a release’s result. They establish a narrower fact: the US premium subscription pool for rightsholders grew in the first half of 2026, alongside growth in overall wholesale revenue.
When the next statement arrives, place the H1 2025 and H1 2026 exports side by side. Trace recording and composition lines separately, circle any missing version or unmatched period, and leave unresolved cells visibly unresolved. The bright national meter can stay at the top of the page. Your own signal path belongs underneath it.
Written by Avery Knox
Comments
No comments yet.