Implementing Custom Output File Naming for MDX, MDXC, and VR Models #141
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
I've implemented a feature to customize the output file names for MDX, MDXC, and VR models within the
separate
method. However, for the Demucs model, I've left the naming as is, as I'm not entirely sure how to implement this feature for it.#128 (comment)
Here's an example of how to use the new functionality:
In this example,
primary_output_name
andsecondary_output_name
are the custom names that will be used for saving the output files. For instance, the files will be saved asprimary_output_name.wav
andsecondary_output_name.wav
.You can also rename specific stems:
To rename the primary stem:
To rename the secondary stem:
Or do not rename the files:
Screenshots:
I encourage you to test this update, as you have a better understanding of programming than I do. You may be able to find a solution to customize file names for the Demucs model and fix other possible problems if they occur.