-
Notifications
You must be signed in to change notification settings - Fork 156
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
Support for TubeArchivist #481
Comments
For movies or series libraries?
No scanner logs to see how it is currently being detected as... Scanner code could have regex added to transform as: Tube Archivist [CHANNEL-ID] the series foldername passed to the agent, but not in the plans for now but if you submit a pull request with the fix in the scanner I would add it to the master |
TubeArchivist, \-o sets the output parameter for yt-dlp, example:
-o "Output/Video/%(playlist_title)s
[%(playlist_id)s]/S01E%(playlist_autonumber)s - [%(upload_date)s] -
%(title)s - [%(id)s].%(ext)s
Le dim. 4 févr. 2024 à 21:25, Nick Artman ***@***.***> a
écrit :
… It'd be awesome if the app supported a more basic naming convention, as
used by default with TubeArchivist.
Spec: [channel_id]/[video_id].mp4
Ex: UCL_f53ZEJxp8TtlOkHXXXXX/DB15tXXXXX.mp4
Note: There are no brackets in the file name, literally just the ID name.
Is this currently possible?
—
Reply to this email directly, view it on GitHub
<#481>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHMWZKTFBTAKDMAMFMJGRDYR7VEXAVCNFSM6AAAAABCZD2BSOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTOMRYHE4TGNY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It'd be awesome if the app supported a more basic naming convention, as used by default with TubeArchivist.
Spec:
[channel_id]/[video_id].mp4
Ex:
UCL_f53ZEJxp8TtlOkHXXXXX/DB15tXXXXX.mp4
Note: There are no brackets in the file name, literally just the ID name.
Is this currently possible?
The text was updated successfully, but these errors were encountered: