SoundExchange Meeting With Webcasters to Address Royalty Concerns

Authored by Mark Hefflinger on April 19, 2007 - 11:44am.

Washington - SoundExchange, the entity set up by the recording industry to collect and distribute digital royalties, said on Thursday it is in discussions with some webcasters to "explore mutually beneficial business arrangements," in the wake of higher royalty rates announced by the Copyright Royalty Board (CRB) that many webcasters say will put them out of business.

SoundExchange said it contacted some services several weeks ago to seek information and schedule possible discussions, and is willing to meet with additional commercial and non-commercial webcasters.

"We sought a dialogue with these services in order to determine if there is an appropriate business solution that addresses their concerns while still ensuring fair compensation for artists," said SoundExchange general counsel Michael Huppe.

Despite its willingness to hear the concerns of webcasters, the organization maintains that it believes the CRB's decision was sound and reflects the fair value for music in the market.

"We recognize that there may be certain needs and expectations, as expressed by webcasters in recent days, that might possibly be addressed through direct discussions," said SoundExchange executive director John Simson.

 

Related Links:
http://www.soundexchange.com/news/news.html

Comments

SoundExchange Royalty Concerns

I agree with both SoundExchange and the Copyright Royalty Board. Everybody wants to use our music but they don't want to pay us! Finally, the Copyright Royalty Board under new leadership has seen the light and is actually trying to remedy that long-standing wrong. Next step it to tackle ASCAP and BMI's longstanding practing of collecting License Fees under false pretendes from the Live Venues that we perform at. Money that is never distributed to us but to the songwriters and publishers of major label songs as radio airplay bonuses and other awards.

Post new comment

The content of this field is kept private and will not be shown publicly.