Export Release:
The PlenioExportRelease node is designed to facilitate the exportation of music tracks from the Plenio Music Production System into various high-quality audio formats, including FLAC 24-bit, MP3 V0, and WAV 32-bit float. This node not only ensures that your music is saved in these formats but also enriches the files with metadata such as tags and cover art. Additionally, it generates a comprehensive release record in JSON format, which documents essential details like hashes, seeds, settings of the executed graph, reports, loudness, and model licenses. This record serves as a valuable reference for the production process. Furthermore, any stems marked as 'save' in a Stem Mixer are exported alongside the main track into a dedicated folder, ensuring that all components of your music production are neatly organized and preserved.
Export Release Input Parameters:
collision
This parameter determines how the node handles file naming conflicts during the export process. It offers three options: "number," "overwrite," and "error." Choosing "number" will append a number to the file name to avoid overwriting existing files, "overwrite" will replace any existing files with the same name, and "error" will halt the process and raise an error if a conflict is detected. This parameter is crucial for managing file versions and ensuring that important data is not inadvertently lost.
tag_mode
The tag_mode parameter specifies how metadata tags are applied to the exported audio files. It provides three options: "title only," "tags," and "copy from loaded file." "Title only" will apply minimal metadata, "tags" will include a comprehensive set of metadata fields, and "copy from loaded file" will replicate the tags from an existing file. This parameter allows you to control the level of detail in the metadata, which can be important for organizing and identifying your music files.
Export Release Output Parameters:
release_record
The release_record is a JSON file that contains detailed documentation of the music export process. It includes information such as file hashes, seeds, settings of the executed graph, reports, loudness levels, and model licenses. This output is essential for maintaining a thorough record of the production process, which can be useful for future reference, troubleshooting, or legal purposes.
exported_files
This output parameter lists the paths to the exported audio files in the specified formats (FLAC, MP3, WAV). It provides a clear reference to where the files are stored, making it easy to locate and use them in subsequent workflows or for distribution.
Export Release Usage Tips:
- Ensure that you have set the collision parameter appropriately to avoid accidental overwriting of important files. If you are unsure, using the "number" option can help maintain multiple versions of your exports.
- Utilize the tag_mode parameter to manage metadata effectively. If you are exporting files for distribution, consider using the "tags" option to include comprehensive metadata, which can enhance the discoverability and professionalism of your music.
Export Release Common Errors and Solutions:
"Song.plenio.json already exists"
- Explanation: This error occurs when a release record with the same name already exists in the output directory, and the collision parameter is set to "error."
- Solution: Change the collision parameter to "number" to automatically rename the new file, or to "overwrite" if you intend to replace the existing file.
"Invalid file name"
- Explanation: This error is triggered when the export process encounters a file name that contains invalid characters or reserved words.
- Solution: Ensure that your file names do not contain special characters like <, >, :, ", /, , |, ?, *, or any reserved words such as "CON" or "PRN." Adjust the file name to comply with these restrictions.