This page describes the technical interface between the FUGA platform and the platform of a content owner/licensor to enable automatic content ingestion to the FUGA system.
Content ingestion can be done either by uploading content to FUGA's FTP server or by sending us hard drives with it.
By content we mean audio files, cover art images, and (optionally) metadata files. The audio files must be in the lossless FLAC or WAV format, Microsoft PCM, little-endian, 16 bit, stereo 44100 Hz. Cover arts must be either in the JPG RGB or PNG format and have a minimal size of 600 x 600 pixels. The requirements for metadata and folder structure are listed below.
The server address is ftp.vault.independentip.com. Login credentials are the same as to the FUGA application itself. The ingestion will be triggered for each release directory after it is completely uploaded. The content owner will be notified by e-mail about the result of the process.
There are two options of how the content can be structured:
Content is uploaded by creating one directory for each release. This directory contains one lossless FLAC or WAV file for each track, cover art image file, and a confirmation file.
The directory name will become the release's name in FUGA. The name of the cover art must end with a jpg or png extension (e.g. cover.jpg). The track names can be arbitrary as long as they are prefixed with two-digit track numbers. For example, 01.wav and 01_first_track.wav are both valid names. The confirmation file name must be called upload.ready.
For example, if the content required for ingestion were two releases with names "Best tunes" and "Greatest hits", this would be the required file structure:
The confirmation file has zero byte size and must be uploaded as the last file in its directory. The completed transfer of this file signals that the directory has been uploaded completely and the ingestion of this release can be started.
Content is uploaded by creating one directory for each release. This directory contains one lossless FLAC or WAV file for each track, cover art image file, metadata XML file, and a confirmation file.
The directory must be named after the release's UPC. The directory contains the cover art file named [UPC code].jpg, the metadata file named [UPC code].xml, the track files named [UPC code]_[disc number]_[track number].wav, and the confirmation file [UPC code].complete.
For example, if the content required for ingestion were two releases with UPCs 8717306932202 and 8717306944526, this would be the required file structure:
The confirmation file has zero byte size and must be uploaded as the last file in its directory. The completed transfer of this file signals that the directory has been uploaded completely and the ingestion of this release can be started.
Metadata is delivered in the XML format for each release. An example of a FUGA ingestion document instance can be found here. Note that this example reflects only a subset of the full FUGA metadata set. For a complete listing, refer to the XSD.
Please follow these guidelines to prevent issues when delivering your products to stores.
If you send us content on hard drives, you'll have to use the FTP ingestion first and successfully upload at least three releases in the format you choose. The content you then send us on the hard drives must have the same structure you used for the FTP ingestion (you may omit .complete or .ready files). The hardware requirements for the discs are:
Hard drives following the requirements above can be sent to the following postal address:
Independent IP
Kraijenhoffstraat 151
1018 RG Amsterdam
The Netherlands