You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use yt-dlp often, and with the commands --add-metadata and --parse-metadata, I'm able to add the description of a video to the comments field of a video's metadata. It would be nice if Stash would add it to the details field.
I'm pretty confident it used to work this way natively, as I have multiple scenes with their details filled by the comments metadata in their video files. From a little digging, these scenes were created in late 2021 -- so maybe it worked around then and something changed.
In case it could potentially cause conflicts somewhere, it might be ideal to have an opt-in setting.
The text was updated successfully, but these errors were encountered:
deprecated useFileMetadata and stripFileExtension scan options. These are probably better suited as scrapers, plugins or scripts.
useFileMetadata was the scan option that enabled the feature you're referring to. I think I agree with the reasoning given for the deprecation - a scraper that pulls from file metadata would be more versatile than something built into the scan task. You'd be able to set metadata at any time, rather than only during the initial scan, for example.
I don't know if someone has already written such a scraper, so you might have to write it yourself. I'm sure there are many python libraries to get every possible kind of metadata out of a video file though, so I don't think it should be too difficult.
I use yt-dlp often, and with the commands
--add-metadata
and--parse-metadata
, I'm able to add the description of a video to the comments field of a video's metadata. It would be nice if Stash would add it to the details field.I'm pretty confident it used to work this way natively, as I have multiple scenes with their details filled by the comments metadata in their video files. From a little digging, these scenes were created in late 2021 -- so maybe it worked around then and something changed.
In case it could potentially cause conflicts somewhere, it might be ideal to have an opt-in setting.
The text was updated successfully, but these errors were encountered: