Proposed naming scheme for future flexibility

[activ]

This naming should be compatible with most media servers and not just Plex and support having multiple versions in one folder. Both different resolutions and actual editions.

In arr format:
{Movie CleanTitle} {(Release Year)} {imdb-{ImdbId}} - {edition-{Edition Tags}} {[Custom Formats]}{[Quality Full]}{[MediaInfo 3D]}{[MediaInfo VideoDynamicRangeType]}{[Mediainfo AudioCodec}{ Mediainfo AudioChannels]}[{Mediainfo VideoCodec}]{-Release Group}

Example:
Example: A Good Day to Die Hard (2013) {imdb-tt1606378} - {edition-Theatrical Cut} [MA][WEBDL-2160p Proper][DV HDR10][DTS-HD MA 7.1][h265]-FLUX.mkv

[dreulavelle]

Do we want to include edition by default? Off the top of my head I'm thinking the usual year and imdb id.. but also resolution, quality and audio?

Something closer to:

A Good Day to Die Hard (2013) {imdb-tt1606378} {edition-Theatrical Cut} [2160p] [DV HDR10] [DTS-HD MA 7.1].mkv

Not sure on the edition part..

[activ]

Don't think there is any downside and it prepares for the option to have different editions. So why not?

[activ]

Note the - in this format {imdb-{ImdbId}} - {edition-{Edition Tags}} that is needed I think for compatibility

[JourneyOver]

Honestly wouldn't mind seeing an option to set a custom naming scheme tbh, so the end user can either leave the default naming scheme that comes with riven or make their own as I personally do not care for nor want the imdb nor edition information.

Only thing really stopping me from setting up riven myself (unless I decide to fork and rework the naming scheme stuff for personal use)

[ninow7]

Agree with the different naming scheme, arr format will do for me. But custom would be amazing as well of course. I cant customize my library the way I want without this. This functionality would make me use Riven for sure.

[dreulavelle]

we could adopt a similar strategy that Arrs do for naming. Like in our settings users could do this format the same way, like so:

%t (%y)

for Title (year)

As a quick example.. but having users mess with naming can be pretty scary from a dev point of view. We prefer to keep that control on our side so that less issues come up. It would be better if it was the same naming scheme across the board.

[dreulavelle]

the imdb id has to stay there. It's the only way to import the symlinks back into the database on a fresh startup if a user was to reset the database.

Edition isn't a big deal, just to keep the names short, might be better to get rid of it probably..

[ninow7]

we could adopt a similar strategy that Arrs do for naming. Like in our settings users could do this format the same way, like so:

%t (%y)

for Title (year)

As a quick example.. but having users mess with naming can be pretty scary from a dev point of view. We prefer to keep that control on our side so that less issues come up. It would be better if it was the same naming scheme across the board.

Aah yes I can imagine that can become a mess... I think default arr scheming is already more than enough information to have in the name and keeping it easy without too much customization. Appreciate your work, it looks like a beautiful tool/application!