Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
title3. Why RIN?

Many of the established processes that were commonplace in the analogue world - from the proper labelling and archiving of music files to documenting the necessary information regarding how, and by whom, those files were made - have been lost during the transition to digital music, which often makes crucial information about recordings inaccessible..

RIN was created to address this problem. It allows content creators to collect notes and data related to an individual recording, at the earliest instance (ie. within the Studio), while also addressing contributor and role information and providing essential information for the archiving of the recorded material.

Those overseeing recording projects are able to review the RIN data at intermediate stages and validate progress. Those seeking to repurpose recordings after they have been released will have a wealth of both technical and contextual metadata to work with as they create, for example, re-mixes and derivative recordings.

...

Expand
title7. Who can implement RIN?

Anyone can implement the RIN specification into their systems or platforms, without cost, by obtaining a free implementation licence from DDEX. They can then be sure that any changes to the specification are made in accordance with the DDEX regulations, which protect implementers and ensure that specifications represent best practices without convolution of the RIN specification.

There is no licensing cost for implementing or using RIN. A free implementation license must be obtained from DDEX by the software creator. Users creating or reading RIN files do not need to obtain any licence to use software that implements RIN.

See http://ddex.net/implementing-ddex-standards for further information or to obtain an implementation licence.

NB. Users of software or tools utilising RIN do not need an implementation licence – this is only applicable to the technical implementers (such as Digital Audio Workstation and software manufacturers).

...

Expand
title9. Who is behind RIN and when was it established?

RIN was officially released as a “candidate standard,” in 2016. It was developed by DDEX members, under the DDEX remit, specifically by members of it’s its ‘Studio Working Group’. The DDEX Studio WG includes representatives from the three major labels, independent labels, media companies, music licensing organisations, leading digital music service providers, software developers, trade organisations and independent professionals.

Expand
title10. How did RIN come to be?

The genesis of RIN was in a project developed in 2007, under the auspices of the U.S. Library of Congress, through the National Digital Information Infrastructure and Preservation Program (NDIIPP). At that time, NDIIPP embarked on a three-year project with VeVaSound (formerly BMS/Chace) and its industry partners (the three major record labels and The Recording Academy Producers & Engineers Wing) to create a structure for collecting and deploying metadata related to commercial multi-track recordings. NDIIPP recognised that many U.S. recordings would ultimately reside with the Library of Congress, and that born-digital material would be difficult for any entity to manage due to the proliferation of differing recording formats and delivery methodologies. 
The NDIIPP project deliverables included a metadata specification and a proof of concept data collection tool. As DDEX was the only international standards setting organisation working on creating standards for the business side of the music industry, it was selected as the obvious choice to further develop and manage the NDIIPP deliverables. 


With the metadata specification under the DDEX umbrella, the Studio Working Group was created to work on developing a standardised message in the DDEX format, using terminology developed by DDEX and which is common to all DDEX messages. When no existing DDEX field was available for a specific metadata parameter, one was created in line with DDEX specifications. Additional fields and flexibility have been added to the original NDIPP metadata specification in order to provide an even more comprehensive metadata set.

...