imported>WaybackImport: Imported from Wayback via edit

2022-05-16T08:16:31Z

Imported from Wayback via edit

New page

== Who’s On First? ==

''Where files live, sync, and play''

Unlike [https://docs.google.com/spreadsheets/d/13NCYwEKh-VgJ_gdpAcQhNoa12TEg27An_scWyHYDC08/edit#gid=0 several other] automation systems, Rivendell “''owns''” its audio assets (aka audio files). With some of those other automation systems, one simply points the “library manager” (or player) to a folder full of audio files. Rivendell is different. You must first '''import''' the audio assets into the Rivendell Library. It works this way for several reasons:

:* '''audio quality'''
:: Rivendell [[wikipedia:Transcoding|transcodes]] your audio files into a professional-grade audio format; you [http://opsguide.rivendellaudio.org/html/sect.rdadmin.manage_hosts.html#sect.rdadmin.manage_hosts.configuring_rdlibrary set this format] on a “per-host” basis, then all audio files are converted to this format when you [http://opsguide.rivendellaudio.org/html/sect.rdlibrary.alternative_methods_of_audio_ingestion.html#sect2_rdlibrary_importing_audio_from_a_file import audio] (note, that, while it is unusual, you ''can'' have a Rivendell audio library containing files in different formats)

:* '''organization'''
:: importing audio assets affords you the opportunity to organize your library and make sure things like metadata are in proper order before putting an asset into production

:* '''work flow support'''
:: many stations have adopted a [[wikipedia:WorkFlow|work flow]] in which they import audio into a “holding tank”, or temporary category ('''[http://opsguide.rivendellaudio.org/html/sect.rdadmin.manage_groups.html Group]''' in Rivendell terms); this gives staff (volunteers) a chance to preview the audio (for things like explicit language), clean up the metadata, and set '''[http://opsguide.rivendellaudio.org/html/sect.rdlibrary.library_maintenance.html#rdlibrary.editing_markers Markers]''' (like segue points, talk points, fades, etc.) before placing the audio into production

:* '''data integrity'''
:: Rivendell keeps track of the integrity of the audio files by maintaining a [[wikipedia:SHA1|SHA1 Hash]] of all the audio files‘ contents; this ''hash'' is stored in the Rivendell database

=== Asset (Audio File) Storage ===

Rivendell users (show hosts, traffic managers, music directors, etc.) don’t really need to know this, but as a Rivendell administrator you should know where the audio files “live”. True to the Linux tradition of flexibility, the audio library can physically reside anywhere on your network. By default, Rivendell expects audio assets to reside in the folder (directory) '''<code>/var/snd</code>'''.

This folder may represent a physical disk partition or a volume shared over your network (with any Linux-support network file system, like [[wikipedia:NFS|NFS]], [[wikipedia:CIFS|CIFS]], [[wikipedia:IPFS|IPFS]], etc.).

(Temporary not by drew Roberts: I am fuzzy, but I think the safe bet is NFS. I think I recall seeing that CIFS/SMB can get you in trouble as it lacks abilities Rivendell uses. I don't recall seeing IPFS mentioned in relation to Rivednell)

'''(Temporary note by drew Roberts: I am fuzzy, but I think the safe bet is NFS. I think I recall seeing that CIFS/SMB can get you in trouble as it lacks abilities Rivendell uses. I don't recall seeing IPFS mentioned in relation to Rivednell)'''

=== Metadata Storage ===

Rivendell audio files '''DO NOT''' contain metadata. All the data ''about'' the audio tracks (e.g., title, album, composer, record label, etc.) is stored in the [http://opsguide.rivendellaudio.org/html/chapter.rdlibrary.html#sect2_rdlibrary_carts Rivendell database].

[[Category:Cookbook]]

This separation of metadata from the audio assets has consequences.

:* '''consistent metadata editing'''
:: using the Library manager, it is simple and straight-forward to change metadata for individual tracks or groups of tracks

:* '''sharing with other apps'''
:: it is difficult, though not impossible to share the Rivendell audio library with other (non-Rivendell) audio applications. You will have to be comfortable with the idea that you have to use Rivendell in order to play a track in the Rivendell library

=== Playing Audio ===

Rivendell supports several ways to output your audio:

:* '''[http://opsguide.rivendellaudio.org/html/chapter.rdairplay.html#sect.rdairplay.overview RDAirPlay]'''
:: this is the “normal” way to play audio; that is, it is the most common way to play Logs that have been prepared using [http://opsguide.rivendellaudio.org/html/chapter.rdlogmanager.html RDLogManager] or [http://opsguide.rivendellaudio.org/html/chapter.rdlogedit.html RDLogEdit] (the Rivendell playlist creation tools)

:* '''[http://opsguide.rivendellaudio.org/html/sect.rdcatch.automating_playouts.html RDCatch]'''
:: allows you to programatically schedule playout of audio

:* '''[http://opsguide.rivendellaudio.org/html/chapter.rdcartslots.html RDCartSlots]'''
:: similar to an old-fashioned [https://en.wikipedia.org/wiki/Fidelipac cart] [https://www.radioworld.com/tech-and-gear/be-cart-machines-the-first-and-the-last machine], this player enables you to stack up a bunch of tracks and play them one after the other

:* '''RDPanel'''
:: a dedicated “panel” of buttons used to play specific tracks (or fire specific [http://opsguide.rivendellaudio.org/html/chapter.rml.html Macros])

:* ''Advanced'': '''rdvairplay'''
:: this is Rivendell’s so-called “headless” player -- it is functionally equivalent to RDAirPlay, but has no graphical user interface with which to control the player; as of early 2020 this player is relatively new to the scene: while you can control some aspects of its operation more Macros are needed to fill out the control side of this player

CookbookChapter02 - Revision history

imported>WaybackImport: Imported from Wayback via edit