Support for custom output name

[ManuXD32]

Allow the user to add tags to the resulting subtitles. For exameple, the user can choose if they want the resulting subtitle to be title.es.srt or title.es.lingarr.srt.

Being "lingarr" whatever the user decides

[ManuXD32]

That way is easier to check all the resulting subs if processing a batch

[rowanfuchs]

I like that idea, i will have a look into that

[ManuXD32]

Cool, Thanks!!

[speedycars]

I'm upvoting this. Right now I'm trying to make space for subtitles translated by humans, and to still have machine translated subtitles. This way Bazarr for example wouldn't stop searching for human translated subtitles (forced subtitles are really rare in my language).
So far my strategy is to manually rename the Lingarr translated subtitles to .forced.srt, as this is a tag recognized by players.
title.en.srt -> title.xx.srt -> title.xx.forced.srt
It seems like we need a new standard for machine translated subtitles which should also be recognized by players (i.e. Plex).

[koalaeagle]

This one is crucial for me. I would always want to distinguish between subtitles that were included with a release/obtained by bazarr vs lingarr translated versions. Not only for visibility, but it would enable bazarr to continue monitoring for a (in theory) non-translated version

[speedycars]

Just tested the latest release 0.9.9 where such feature is included.
Unfortunately, the custom tag is added before the language tag which make it incompatible with other software like Bazarr.
Currently: Movie.Name.forced.XX.srt
Should be: Movie.Name.XX.forced.srt
In my case the defined custom tag is "forced".

[rowanfuchs]

forced isn't a custom tag, however, I've investigated the logics and tagging, while Bazarr still doesn't pickup subtitles with any other tags I do see the advantages of putting it behind all tags and I will implement it in the next minor release. Thanks for providing the feedback.

[rowanfuchs]

this feature has been implemented, thank you for the suggestion and thinking with me!