Welcome < Configuration < System Configuration < Auto Load
Users can set up one or many Auto Load instances from which Zetta® will automatically import audio based on the Priority set for each Auto Load instance. This audio can be from sources such as NexGen Digital®, RCS News® and Smart Ripper®. The Auto Load process will process up to eight audio files concurrently from the defined import location.
Click any area in this image for help
Click any area in this image for help
In this Topic: show/hideshow/hide
There are two operations that can be performed from the Auto Load tab, Add Auto Load and Delete Auto Load.
Add Auto Load – Clicking Add Auto Load will create an Auto Load instance that can be configured. |
|
Delete Auto Load – The Delete Auto Load button will delete the selected Auto Load instance. |
Important Note! |
If an asterisk (*) is displayed next to the system <Name>, it indicates there are unsaved changes. |
The top grid of the Auto Load configuration window shows a list of configured Auto Load instances that have been added. This list can be sorted by clicking on a column header. The Custom Filtering field below the column headers can be used to filter the list. Simply type into the field to narrow the list to the Autoload instance needed. See the Custom Filtering section of the guide for additional help using the filtering.
The Active checkbox tells Zetta that the Auto Load is active and the service can check for new audio, in the Import Location specified, for import into Zetta.
The Name field can be used to give the Auto Load instance a name. The Auto Load grid list can be sorted by Name by simply clicking the Name column header.
The Description field can be used to describe the Auto Load instance. A Description is optional.
When the Add Auto Load button is clicked, the following configuration options are available in the General tab of the Auto Load System Configuration window:
In this section: show/hideshow/hide
The Processed by drop-down is used to select a configured computer that will process the audio files that are to be loaded into Zetta. Only computers configured in the Computers Configuration window will appear in this drop-down. Anytime the Auto Load configuration is changed the Miscellaneous Services and Content Management Services in the Zetta Startup Manager for the associated computers must be restarted.
The Location drop-down allows the user to select a pre-configured location for Zetta to watch for files. Locations are configured in the Locations tab of the System Configuration window. When an Import Location is selected the details of the configured Location are shown in the Import Location Details section of the Auto Load instance.
The Add New Location and Edit Location buttons open a window allowing the user to create or edit a Location instance. The fields in this window vary based on the Type of Location specified. See the Locations topic for additional help with the fields in these windows.
The file type drop-down menu will define what file types to look for and Auto Load. Auto Load can import all the Supported Audio Formats. Zetta can Auto Load from a Selector 15 XML file. Zetta can Auto Load .pkt (packet) files sent from NexGen Digital and RCS News. Zetta will Auto Load a NexGen .pkt file that only contains metadata. If the asset does not exist, Zetta will create the asset with no audio. If the asset does exist Zetta, will update the metadata and leave the audio unchanged. That is, if Auto Load is set to match on External Id and the metadata file specifies the external id of an asset or if it matches on Title & Artist then the metadata must specify the title and artist of an asset found in Zetta. Zetta will also Auto Load a NexGen audio backup with XML data file using the default AMU Mapping Template to match the fields from NexGen to the Zetta metadata fields.
Important Note! |
In previous versions, Zetta supported the playback of M4A files and, using AFC, supported the import and conversion of M4A files however, Zetta did not support the parsing of metadata from AAC/M4A files. In Zetta 4.1, there was a change to the Audio Metadata logic to attempt to read metadata from AAC/M4A files. The logic utilizes BASS in order to read the metadata. Due to the different types of AAC/M4A files, Zetta may not handle all files. But if the metadata follows the usual standards and it is an AAC/M4A file supported by windows (not a 3gp or other variation), it will handle the reading of the metadata. |
The Fallback Type drop-down will define what asset type will be imported if the asset type is not defined in the metadata of the asset being imported. An Asset can be imported as a Song, Link, Spot, Voice Track, Quick Record or Custom Asset type as defined in the Asset Types tab of the System Configuration window.
Match On, is like the options in Tools | Media Import. Users can select matching criteria for cases where the user wants to prevent or allow duplicate audio. Choices are Title and Artist/Sponsor, Filepath, External ID, File CheckSum, Filename or Do Not Match.
If Match, is like the options in Tools | Media Import. Users can select what happens to an audio file if defined matching criteria are met. Choices are Do Not Import, Replace, Replace Audio Only, Merge Changed Fields, Replace Station or Cut Fields. The Replace Station or Cut Field options are only available when the GSelector and ZCast features are both disabled in the General tab of the System Configuration and at least one Asset Type is set to the metadata scope of Cuts.
When this option is checked, the filename without the extension will be put into the External ID field on the asset unless the Automatically Generate Asset External ID is setup in the External ID tab of the System Configuration. If the Automatically Generate Asset External ID is setup then the External ID will be based on that setting. If the Match on = External ID option is set, Zetta will automatically enable this checkbox (as the External ID must be populated if Match on = External ID is set). This option can be used when importing audio from NexGen or V15.
Packet files (.PKT) include a cut number for the audio asset called for in the .PKT file. The 'Append Cut to Cart for External IDs' option can be used when importing assets into an Asset Type that has a metadata scope of Station or Global to append the cut number to the cart number for the External ID. When this option is deselected and the metadata scope for the Asset type is Station or Global the cut number will not be included in the External ID when the asset is imported into Zetta. If the metadata scope of an Asset Type is set to Cuts then the cart in the packet file will be used as the asset external id and cart-cut will be used as the cut external id regardless of this setting. The default setting is unchecked.
The bottom section of the import window is used to Add a Station to Activate the Media for and optionally select the Category to place the media. Used the Remove Station button to the left of the activate checkbox to remove the station activation instance.
Click any area in this image for help
Click any area in this image for help
In this section: show/hide show/hide
The Polling Interval setting is used to set how often Zetta will check the Import Location for new files. The default setting is 0.5 Minutes. The Auto Load process will process up to eight audio files concurrently from the defined import location.
The Companion File Delay is the amount of time Zetta is to wait for a companion file before it imports the asset into Zetta. Some audio files may be paired with a metadata file. Therefore, when Auto Load detects a new audio file in the Import Location, it needs to wait for a while to see if the metadata file appears and vice versa if the metadata file appears first. This value can be set to 0 if metadata files are not used.
For Example: When receiving NexGen audio files for import, there will be an audio file and an XML metadata file.
The AMU (Audio Metadata Utility) Mapping Template is used to select a template to match metadata such as Composer, Arranger and Musician from an XML file to specific fields in Zetta. Templates can be created to match asset metadata tags to Zetta fields for import of the metadata. The Default Template, maps fields found in NexGen to fields found in Zetta. When an import occurs using the Default template, Zetta first looks for a NexGen XML file for the asset. If present, it will use only the XML file to read the NexGen Metadata. If no associated NexGen XML is used, Zetta will then check to see if the audio file is an MP3 file. If the file is an MP3 file, Zetta will read the ID3 metadata, if any from the file. If there is no NexGen XML and no MP3 ID3 metadata, Zetta will then use AFC to read the AFC metadata. Contact RCS Support for assistance in creating an AMU Mapping Template.
The following table shows the mapped NexGen fields and the corresponding mapped Zetta fields that will be used when an asset is imported using Default as the selected AMU Mapping Template.
NexGen XMLDAT Elements |
Zetta Field |
Album |
Album Title |
Artist |
Artists - The NexGenXML InputMetaDataType maps "Artist", "Artist_2"...."Artist_6" tags to the same "Artist" target tag. When mapped this way, the tool will fetch all the artists as an "Artist" Collection. |
Artist_2 |
|
Artist_3 |
|
Artist_4 |
|
Artist_5 |
|
Artist_6 |
|
Audio_Formats |
Audio Format - This will import 1 for PCM, 80 for MPEG, etc. This field is typically not imported. This field is displayed in Zetta by adding the Audio Format column to the Library Module. |
Cart |
External ID and Cut External ID - If the metadata scope of the Asset Type is Cuts, then this attribute will be added to the Cut External ID field in the Cut Specific tab of the Metadata Card. |
Channel |
Mono or Stereo - Use 1 for Mono and anything else for Stereo in the Metadata imported. |
Client |
Sponsors – Used for non-song asset types. |
Comments |
Comments |
Composer |
Participant\Composer - Added to the Participant tab as a Composer. |
Cross_Fade |
Segue Point |
Cut |
External ID in some situations - The Cut External ID is only used if the assets metadata scope is set to Cuts in the Asset Types tab of the System Configuration window. When the metadata scope is Station or Global and the Append Cut to Cart for External IDs is selected, the Cut will append to the Cart for the External ID. The format will be Cart-Cut and both the Cart and the Cut will be placed in the External ID field of the Extra tab. The Append Cut to Cart for External IDs option is found in the Auto Load tab of the System Configuration window. |
Ending |
Ending – This is a two letter code. |
End_Time |
End Date / Hour |
Erase_Time |
Kill Date |
Fade_Up_Start |
Trim In |
Fade_Up_Length |
Fade In |
Fade_Down_Start |
Fade Out, Trim Out - FadeDownStart & FadeDownLength are used together to determine Trim Out. |
Fade_Down_Length |
Fade Out, Trim Out - FadeDownStart & FadeDownLength are used together to determine Trim Out. |
HookStart |
Hook In |
HookEnd |
Hook Out |
Intro_1 |
Intro |
Intro_2 |
Intro |
Intro_3 |
Intro |
ISRC |
ISRC |
ISCI_Code |
ISCI |
Label |
Label |
Length |
Resource length - This field is typically not imported. |
Opening |
Opening – This is a two letter code |
Publisher |
Publisher |
Sample Rate |
Sample Rate - This field is typically not imported. This field is displayed in Zetta by adding the Sample Rate column to the Library Module. |
Start_Time |
Start Date / Hour |
Title |
Title |
Type |
Load respects SONG or SPOT types; otherwise the asset will be imported as the Auto Load Default type. Spot = 1, Song = 2 Enum(NexGen) to String(Zetta) type |
Use the Priority drop-down to set the priority of the imported audio. This allows the most important audio to be imported first as it arrives in the defined location. Select between P1-P9 (the lower the number the higher the priority) The default is P5.
For Example: One might set News and Traffic audio to import first at a P1, but Music to a P5 and Fill material to a P9. If Music is currently auto loading into the system and an audio file arrives into the News and Traffic location, the system will pause the importing of the Music, and import the News and Traffic before proceeding with the Music.
The Auto Load process will process up to eight audio files concurrently from the defined import location.
When the Perform Marks Analysis option is selected, the audio loaded will be analyzed based on the Marks Analysis Settings configured in Configuration | System | Audio Processing tab. If this option is deselected, no analysis will be performed and the audio will not be marked.
In the After Import section of the Auto Load window, users can define the action that will happen after an Auto Load import.
The Upon Successful Import drop-down is used to set what Zetta is to do with the files in the Import Location once they have been imported successfully.
Delete Immediately - The 'Delete Immediately' option will delete the original file(s) from the Auto Load Import Location immediately after successful import.
Keep and Delete Later - The 'Keep and Delete Later' option will keep the file(s) in the Import Location for the defined Delete After Hours.
Never Delete - The 'Never Delete' option will never delete the original file(s) in the Import Location.
The 'Archive File' option is used to Archive the original files from the Import Location. The Archive Files section is separate from the actions of the Upon Successful Import. This means if the Upon Successful Import is set to Delete Immediately but the Archive File is enabled the file will be removed from the Import Location but saved to the Archive Directory specified.
Archive Directory - The 'Archive Directory' is the location to save the files that has already been imported into Zetta. This directory can be a Local folder on the computer or a UNC path to a network location. Use the Browse Folder button to browse to the desired directory.
Purge From Archive After x Days - The 'Purge From Archive After x Days' field is used to specify the number of days to keep archived files. Leave the field blank to never purge the files. This field can be expressed in decimal to account for partial days. For example: 9.5 would be 9 days and 12 hours.
To add an Auto Load instance to Zetta, perform the following steps: |
Welcome < Configuration < System Configuration < Auto Load
© 2007-2024 RCS All Rights Reserved.