Feat: Smartplaylist: Add dest_regen option for regenerating destination path #5621
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.
Problem
-C -M
options), they will be registered inside the Beets database using their original paths. However, during subsequent processing (e.g., aconvert
operation), a path following the Beets path format can be generated.smartplaylist
plugin, only the path registered inside the Beets database (the original path) can be use inside the output playlist. This block the compatibility with other plugins.Solution
I added a a new optional configuration option known as
dest_regen
(as well as its equivalentdest-regen
on the CLI) to regenerate items' path in the generated playlist instead of using the ones of the library, just like aconvert
or amove
operation would have done. This operation will happen before therelative_to
andprefix
options, which makes sense to do so and not in another order, otherwise this new option (dest_regen
)) would overwrite the desired behavior of the other mentioned options (relative_to
andprefix
). It is then helpful to generate playlists compatible with theconvert
plugin.To Do