SoundCloud streaming change

SoundCloud is about to limit the # of times a track can be streamed to an external API to 15,000 times. If i'm interpreting that correctly, and since many of use probably use the same sound effects, the current solution won't be viable very long. It may be months, or a year, or sooner, but at some point I won't be able to play most sound effects that I'm using. What would be one workaround would be to update Roll20 to allow people to play private sounds. But that would only work for so long. can't find the official pres release so here are some from the web <a href="https://www.google.com/#q=soundcloud+streaming+limit" rel="nofollow">https://www.google.com/#q=soundcloud+streaming+limit</a> <a href="http://hypebeast.com/2015/6/soundcloud-to-enforce-" rel="nofollow">http://hypebeast.com/2015/6/soundcloud-to-enforce-</a>...

It's 15,000 in a twenty-four hour period... not forever. Soundcloud said: Beginning July 1, client applications will be limited to 15,000 play requests per 24 hour period.

Hopefully this doesn't affect our access to sounds. SoundCloud has been a beautiful thing so far in Roll20 play. Not perfect but it is extremely useful, every game session. I will be following the news. Another bit of SoundCloud news n rumors, a few months ago they announced some deals with major labels of mainstream music. This made it seem that some more popular songs might be added as playable through the SoundCloud.

Gold said: Hopefully this doesn't affect our access to sounds. SoundCloud has been a beautiful thing so far in Roll20 play. Not perfect but it is extremely useful, every game session. Roll20 generally gets somewhere in the neighborhood of 5,000 concurrent users on the VTT, as I recall. Not all games make use of Roll20's sound capabilities at all, and I suspect it would be uncommon for multiple games that do use music to use the exact same track. Glancing over SoundCloud's statement, it seems to me that not only is it 15,000 requests within 24 hours, but that those requests would have to come from the same client (meaning we wouldn't be stacking up our requests with someone else not using Roll20). I don't think this will be a problem for us.

The door creaking and the fart sound are probably the only ones at risk...