Hi All:
Some information that may be of use, concerning to the WPI rules for
royalties et al in <audio> files.
What we know as rights. Uh,
Meta elements required
* Title : 100%
* Artist ( Interpreter): 12%
* Time: lenght of the <audio> piece. Royalties are assigned by time
sequences.
* Year: (_Objective Reason: It use to happen that some__ <audio> files
have the same name, thus causing a mistake in the attribution to the
artist as it happen in the past_)
* Composer: 20%
* Arrangements: 20%
* Producer: 40%
* Label: It depends on the contract, but as an agent collects all the
rights
* Software: Last but not least, some software use in the production of
audio has its own rights. Uh.
Hope this information it helps for the meta-tag issues
_BTW . There is a new start-up company named orfium.com, which CEOs now
all this issues, there is the cahnce ask them for more info._
Cheers
---
Delfi Ramirez -- At Work
My digital signature [1]
0034 633 589231
del...@segonquart.net [2]
twitter: @delfinramirez [3]
IRC: segonquart
Skype: segonquart [4]
http://segonquart.net
http://delfiramirez.info
[5]
On 2017-04-15 13:46, Roger Hågensen wrote:
> On 2017-04-14 22:23, Andy Valencia wrote:
>
>> Ok. Note that this data structure suffices to encode the baseline
>> information from Shoutcast/Icecast. It does not, for instance,
>> encode "Label", needed to do licensing reporting in the USA.
>> "Year" is another datum often of interest.
>
> Only "artist" and "title" are required for royalties reporting for internet
> radio.
> But "album" and "year" provides additional information that helps.
> Commercial radio and TV uses at minimum the artist and title, and if lucky
> the listener (digital radio) and viewer get to also see album and year.
> Also royalty reporting is done in a earlier stage, what a listener sees is
> not what is logged/given for royalties reporting.
>
> Ogg (Vorbis or Opus) should in theory be easily supported as metadata is
> given in a sidestream right? So is therefore independent of the audio stream.
>
> Mozilla has audio.mozGetMetadata()
> https://developer.mozilla.org/en/docs/Web/API/HTMLMediaElement
>
> I have no idea if that fires once or each time more metadata is passed in the
> stream.
>
> https://developer.mozilla.org/en-US/docs/Web/Events/loadedmetadata
> Only says that it is fired when the metadata is loaded.
> I'm assuming it's only at stream start though.
>
> So with a few "tweaks" Firefox could support Icecast Ogg metadata, if the
> browser is compliant with the Ogg standard then support is very easy to add.
>
> Shoutcast v1 would require parsing of the audio stream, Shoutcast v2 is a
> little different and can pass info like album and year and artwork.
> The only Shoutcast v2 compatible player I'm aware of is the aging Winamp, the
> majority of Shoutcast streams are v1 streams.
>
> So while Firefox almost is able to provide stream meta updates, all the other
> browsers do not though and would require polyfill which as you point out has
> it's own issues with having to reset the stream as the buffer fills up.
>
> Maybe support for enabling a large cyclic buffer could be used, triggered by
> a "stream" parameter for html audio maybe.
> There would still be a issue with metadata possibly being partly in the
> current buffer and partly in the next buffer so any javascript would need to
> splice that together.
>
> Ogg seems simple enough
> https://www.xiph.org/ogg/doc/oggstream.html
> And parsing of this metadata should be in the ogg source (libogg?) so any
> browser that supports Ogg should be able to get that metadata.
>
> --
> Roger Hågensen,
> Freelancer, Norway.
Links:
------
[1] http://delfiramirez.info/public/dr_public_key.asc
[2] mail:%20del...@segonquart.net
[3] https://twitter.com/delfinramirez
[4] skype:segonquart
[5] http://delfiramirez.info
