-
-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run yt-dlp post-processors #530
Comments
I can see that this would be useful to some however this looks messy to directly implement inside of tubesync. Do you use a standard set of arguments for these plugins or do you use custom arguments for each download? |
I use a standard set of arguments for them for all downloads, specifically this: FixupMtime: They also have to be done in this order, replaygain before mtime, otherwise the replaygain postprocessor will overwrite the set mtime. Implementing the ReplayGain plugin might be a bit extra work though, as it has external dependencies as you can see on the github page (rsgain, mp3gain, vorbisgain, and metaflac) |
Thanks for the example args. I'll look into this a bit more. I may be against adding this as a relatively complex feature that requires ongoing support (updating external libs and dependencies etc.) for a very small audience. If more people show an interest in this it would bump it up the wishlist. You can always extend the container yourself and hack in |
I want to use tubesync to download mainly music files, and for that I want to run 2 specific post-processors.
The two post-processors this is about is ReplayGain and FixupMtime
I want to run these as I want to first run ReplayGain on any downloaded .ogg file, followed by setting the mtime of the .ogg file to the upload_date from the youtube video. (1. to not blow up my ears in my car when shuffling, 2. to actually get my playlists in release order in navidrome)
Is there any way running post-processors could be added? Or these two functionalities maybe implemented as native functions of tubesync?
The text was updated successfully, but these errors were encountered: