https://github.com/TRaSH-/Tutorials-FAQ/blob/master/RadarrV3/Collection-of-Custom-Formats-for-RadarrV3.md#evo-except-web-dl

Needs to be the same points (but positive) that is set for the low quality groups or remove EVO from BLOCK4

BLOCK4 prevents EVO WEB-DL from DLing

Try creating a new account for Discord
Follow "join discord" from your trash-guides.info site
HawkBot asks you to give a 👍 reaction to agree to the rules
Impossible to do so -- click on Reactions for that post and you cannot add anything to it, including a: thumbsup:
=> cannot join discord channel

Bot logic for discord is very sensitive - tons of configuration challenges by channel owners on stack exchange. Entirely possible, though, that the issue is just a dumb user (me), hence I suggest you try the above to see whether you have better luck. Thx.

For which application would like to see this Guide ?
Sonarr and Radarr

Describe what you would like to see in the Tutorial/Guide

Users often wish to prefer h265 over h264 and yet still prefer 1080p over 720p.

However they prefer encoding over quality.

Add a guide that details merging all qualities and then using preferred words to identify and order qualities and encodings

This should also be done for Radarr but with Custom Formats

not you, its me

Origin user: nitsua
Origin message: Discord Server Link
Reporting user: TRaSH
Reporting message: Discord Server Link

** Which Guide **
Radarr

Describe the Error in the Guide
Currently it only finds 5.1 and not "5 1" (with a space); This is also a very common writing in file name

Expected behavior
for the regex filter to identify both 5.1 and 5 1 as 5.1 surround sound

Additional context
The solution is to change the reggex to: [^0-9]5[.|\s][0-1]

https://trash-guides.info/Sonarr/V3/Sonarr-Release-Profile-RegEx/

If you compare the "P2P Groups + Repack/Proper" guide to the green 'example' below, the last line says "/\b(repack|proper)\b/i" with a score of [10].

If you look in the green example below, the same line says "/(repack|proper)/i" (without the \b before and after the expression.

In the "Low Quality Groups" guide the score of [-100] all ends with "\b", but in the green example below the "/(-VIDEOHOLE)/i" don't end with "\b".

Should my final result look like the green 'example' or the guide above?

Which Guide
Radarr

Describe the Error in the Guide
Dolbyvision regex code captures unwanted words like "Adventure" (dv|dovi|dolby[ .]?vision)

Expected behavior
should only capture dv, not dv contained within a word.

Which Guide
Collection of Custom Formats

Describe the Error in the Guide
The 3D Custom Format doesn't match uppercase
The 3D Custom Format doesn't match before the Movie Year

E.g. Thor.Tag.der.Entscheidung.3D.2017.German.DL.1080p.BluRay.x264.RERiP-STEREOSCOPiC doesn't get matched because it's 3D and not 3d

Expected behavior
Ignore case and match 3D too
Match 3D before the Movie Year

Screenshots

Additional context

** Which Guide **
https://trash-guides.info/Sonarr/Sonarr-Release-Profile-RegEx-Anime/

Describe the Error in the Guide
A clear and concise description of what the bug is.
The bluray regex

/\b(?:(BluRay|Blu-Ray|BDMux|BD(?!$))|(BDRip)|(BRRip))(?:\b|$|[ .])/ix

does not capture popular release scheme with groups like DB and Cleo

Expected behavior
the expected behavior is to match BD1080p in the string

Screenshots

Additional context

by changing the regex pattern to this im able to capture them

/\b(?:(BluRay|Blu-Ray|BDMux|BD(?!$))|(BDRip)|(BRRip))(?:\b|$|[ .])|BD[0-9]{4}(p|i)/ix

Which Guide
Collection of Custom Formats

Describe the Error in the Guide
the BR-Disk custom format doesn't match / block the following release:
The Fifth Element 1997 Blu-ray UHD HDR Disc TrueHD 7.1 -HDRINVASION

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
https://i.imgur.com/VNvlUxR.png

Additional context
Add any other context about the problem here.

I'm personally unfamiliar with scenes/groups. First of all, there's a lot of terminology so it would be great to see all of that outlined.

I think the most important benefit of this guide would be explaining how you came to understand what you want out of your releases/downloads, how do you educate yourself on which groups are good or bad for releases on usenet/torrent? After going through your guide on recommended release profiles and custom formats, it became very apparent to me that there's a LOT to sift though. You have a lot of low quality groups you exclude. There are preferences for some groups over others, for lots of reasons: Quality, size of releases, timing of releases, how they name their files, etc. And finally, I'm sure this changes a lot. Groups may come and go. How do you keep up to date with this and understand which groups you like or don't like?

This is a "teach a man to fish" moment: Your guides are excellent for getting someone started, but I think long term it makes sense to be equipped with the tools and knowledge necessary to make my own updates and personal touches to the framework you have started.

https://trash-guides.info/Sonarr/V3/Sonarr-Release-Profile-RegEx/

Should the guide give a HDR show a higher score so HDR i prioritized over non HDR?

As you can see on the attached screendump the Servant S02E05 has a score of 250 both with and without HDR.

Which Guide
Sonarr-Release-Profile-RegEx-Anime.md

Describe the Error in the Guide
In the section Suggested naming scheme, the Series Folder Format has a typo in the suggested naming scheme: "{Series TitleTheYear} [tvdb-{TvdbId}]". This will not produce the sample title "The Series Title! (2010) [tvdb-12345]" but rather "Series Title!, The (2010) [tvdb-12345]"

Expected behavior
The suggested naming scheme for the Series Folder Format should be "{Series TitleYear} [tvdb-{TvdbId}]"

Screenshots

vs.

Which Guide
Radarr

Describe the Error in the Guide
The "No-RlsGroup" format will often exclude releases from indexers who use spaces in their formatting.

Expected behavior
Keep these releases.

Screenshots

Same releases, but one is marked as not having a release group.

The Radarr guide currently suggests, for good reason, to use HDR and FraMeSToR with equal score since FraMeSToR don't include HDR in their release names. Once a FraMeSToR release is on disk however, a scoring issue occurs. Oh no!

Since Radarr also detects custom formats based on filename, and the recommended naming scheme adds HDR to it, both the HDR and the FraMeSToR formats will match the file once its renamed. This results in the release suddenly having a higher score compared to when it was first downloaded.

I'm not entirely sure how to fix it. The main problem is that FraMeSToR releases aren't always in HDR, otherwise it would be as easy as adding the FraMeSToR regex to the HDR format.

Another option is to add a negating HDR regex to the FraMeSToR format. This won't prevent anything from being downloaded (since FraMeSToR never includes HDR in their release names anyway), but it will prevent a file on disk from matching both HDR and FraMeSToR. If the release isn't in HDR however, the FraMeSToR format will sadly still be applied and give it a "HDR-like score". Not to mention that this prevents FraMeSToR's actual HDR releases on disk from matching the FraMeSToR format - which makes the format a bit of a lie.

The third option that comes to mind is to add a new HDR (indeterminate) format that is more or less option 2 but with another name. In similar fashion to how there's the ATMOS (indeterminate) format to leave proper detection to the filename matching, this format could mark all FraMeSToR releases (and other groups in the future) as potential HDR releases. It still has the same problem as option 2 though, namely that if it turns out to not be in HDR it will still get the extra score from HDR (indeterminate).

This seems to be the recurring theme here. How do you handle and score something that could be what you want? Something to figure out, or maybe it's just not worth the hassle :)

For which application would like to see this Guide ?
Radarr

Describe what you would like to see in the Tutorial/Guide
At the moment I'm having to delete a custom format and re-add it, which involves resetting a custom format score in the profiles. Although I guess this isn't something that Radarr supports? Editing the custom formats should allow you to paste in the new text and it should override the previous value without losing the scores.

Actually was thinking of raising an issue in the Radarr repo about this configuration approach. To my mind it should just be a directory that Radar reads with a bunch of text files in it with all my configuration changes, it's then trivial to update/backup/store in a git repo etc.
It seems that at the moment we have a binary SQL database which needs zipping up and backing up somewhere.

I've started using your CF guide for Radarr and I'm having issues with the BR-Disk CF. It's tagging mkv releases as BR-Disk which obviously we do not want. Why? For example:

That release is an mkv file but based on the conditions in your BR-Disk CF, the strings in the release title is causing it to be tagged as a BR-Disk. Is this a bug on that CF?

For which application would like to see this Guide ?
Radarr / Sonarr

Describe what you would like to see in the Tutorial/Guide
Updated guides for the WEB-DL releases that have DoVi with HDR Fallback. When DoVi is unsupported these will play fine without the green picture DoVi would else cause. Would like to see the option that WEB-DL with DoVi (DV) and HDR in the title would be preferred over regular WEB-DL with HDR and when only DoVi is in the title the release will be ignored, because of the green picture it causes on devices that don't support DoVi.

Radarr is pretty straight-forward; Just created a new Custom Format that needs DoVi (DV) and HDR in the title and updated the profiles score so they are preferred over regular HDR. But maybe there is a better way i don't know off.

But to accomplisch this in Sonarr with profiles is another levell of experience i don't have, so therefore the request.

Thanxs in advance

Thanks for this awesome profile!

I'd like to know what the intention of this one is: \.S\d+\.(?!E\d+\.)

For me it causes issues because it prefers Season packs over regular episodes which I don't want. Is this intentional or a side effect?

Here's an example:

The.Last.Dance.S01.1080p.NF.WEB-DL.DDP5.1.x264-NTb
The.Last.Dance.S01E10.Episode.X.1080p.NF.WEB-DL.DDP5.1.x264-NTb

Here it matches .S01. of the first example.
It does not match .S01E10. of the second example

Thank you for your nice guides.
I have setup my Radarr and Sonarr according to your guide.
When I enter your guide a month later I can see it says "Last update: 3 days ago".
Do you have a 'history' where I can see what is updated / changed, so I can enter the latest updates into my Radarr and Sonarr?
Regards
Michael

Identification of IMAX Enhanced format

Describe the Error in the Guide
Since 19th Nov Disney+ streams IMAX Enhanced.
https://help.disneyplus.com/csp?id=csp_article_content&sys_kb_id=ae2b1af1dbab30981830269ed3961944
https://www.techradar.com/news/disney-plus-will-offer-imax-versions-of-marvel-films-including-shang-chi
https://www.howtogeek.com/769609/what-is-imax-enhanced/
It seems only disneyPlus is offering this IMAX Enhanced format that is compatible with all players.

At this moment only the following movies:
Ant-Man and the Wasp, Avengers: Infinity WarAvengers: Endgame, Black Panther, Black Widow, Captain America: Civil War,Captain Marvel,Doctor Strange,Guardians of the Galaxy 1 & 2,Iron Man,Thor Ragnarok,Shang-Chi and the Legend of the Ten Rings

Currently the custom formats only identify IMAX, which often is not the IMAX enhanced.

Expected behavior
A custom fornat with a difference between IMAX and IMAX Enhanced.

Additional context
Looking at the titles it seems when both the word IMAX and DSNP is included it's IMAX Enhanced.

EOL; Not Supported; Nuke it

I suggest splitting Atmos to Lossy and Lossless. Here is what I use:

TrueHD Atmos (lossless)
truehd.*atmos|atmos.*truehd

DDP 5.1 Atmos (lossy)
\bDDP5.1\b.*atmos|atmos.*\bDDP5.1\b

I added | just in case the title doesn't follow the correct format.

Add json template for h265 10bit

** Which Guide **
Bazarr/Basic-Guide

Describe the Error in the Guide
Redundant Language on step four.

"Meanly used when you use a reverse proxy." can be removed outright.

Additional context
The blurb stands on its own without the last sentence.

wouldn't it be (name).?web.?(dl|rip) to match on both radarr and sonarr?
they don't get tagged here with just (name).?web.?dl

example:

Some.Movie.2020.1080p.AMZN.WEBRip.DDP5.1.Atmos.x264-NTG
Some.Show.S01E01.1080p.AMZN.WEBRip.DDP5.1.x264-NTG

Which Guide
Sonarr

Describe the Error in the Guide
https://discord.com/channels/383686866005917708/383687854057979906/932796301370880040

not sure if you'd call it a bug-ish or a feature request

/\bS\d+\b(?!E\d+\b)/i season packs are preferred; however, given the folder name is ignored the error/warning/issue occurs as the file names would not be a season pack of course.

keep in mind this is the only way to prefer season packs if you have preferred words due to the long standing bug.

Preferred Words overrule season pack preference
Sonarr/Sonarr#3562

Expected behavior
add warning about season pack upgrades/loops

Screenshots

Additional context
above

For which application would like to see this Guide ?
Prowlarr

Have some new potential groups to be added to the Sonarr v3 Release Profile you have:

https://sharex.tronflix.app/zORI8/PaPiJOJe09.png

https://sharex.tronflix.app/zORI8/fIBuveGI64.png

https://sharex.tronflix.app/zORI8/deJiLuYU99.png

The optional season pack regex /\.S\d+\.(?!E\d+\.)/i is explicitly looking for . separators. I found this resulted in it favouring one source of another that use whitespace separators instead. Suggest changing it to use word boundaries instead:

/\bS\d+\b(?!E\d+\b)/i

just an idea

Here are some name suggestions for more consistency in naming conventions:

• 4k Remaster -> Remaster (4K)
• Basic DTS -> DTS
• Basic Dolby Digital -> DD
• Dolby Digital Plus -> DD+
• DD+ ATMOS (lossy) -> DD+ ATMOS
• DTS-HD/DTS:X -> DTS (HD or X)
• Dolby Vision (Single Layer) -> DoVi (Single Layer)
• EVO except WEB-DL -> EVO (no WEB-DL)
• HDR (indeterminate) -> HDR (guessed)
• HQ-P2P -> Release (high quality)
• Low Quality Releases -> Release (low quality)
• Streaming Services -> Streaming
• Surround Sounds -> Surround Sound
• TrueHD (not ATMOS) -> TrueHD
• TrueHD ATMOS -> TrueHD (ATMOS)
• 720/1080p no x265 -> x265 (720/1080p): the profile regex matches only 265, it's dis-preferred by using a negative score.

Need to create; these may also be covered under the new wiki and may no longer be necessary?

I believe

/(nf|netflix).?(dl|rip)/i

should be

/(nf|netflix).?web.?(dl|rip)/i

As it's not adding the preferred words into the file name without the "web.?"

-FRAMESTOR$ For the regex to fix that

Origin user: bakerboy448
Origin message: Discord Server Link
Reporting user: TRaSH
Reporting message: Discord Server Link

Which Guide
Please add which Guide you found a Bug/Error with.
Radarr
Describe the Error in the Guide
A clear and concise description of what the bug is.

block The.Last.Blockbuster.2020.1080p.BD.AVC.DD2.0-Liber8 it's BR-DISK that's poorly labeled.

Expected behavior
A clear and concise description of what you expected to happen.

Above

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

The new regex for blocking h265 releases (/(?=(1080|720)).*((x|h)265|hevc)/i) isn't blocking releases that have it named "1080p.AMZN.WEB-DL.DD5.1.H.265-SiGMA" I assume because of the period between H and 265. I don't know enough about RegEx to know how to correct it unfortunately.

For which application would like to see this Guide ?
Radarr

Describe what you would like to see in the Tutorial/Guide

it would be nice if you could put together a guide to import the radarr custom formats in one go.

For example using the radarr api to add/update the profiles with the latest ones avaliable.

The way I gone about doing this is cloning the repo then iterating through the json folder and making an api call for each file but a method that doesn't require the cloning would be awesome.

Please, add the the json files to the guide for download in zip for easy importing instead of copy/pasting to make files.

For which application would like to see this Guide ?

Radarr

Describe what you would like to see in the Tutorial/Guide

Add details for importing existing
Radarr/Radarr@eecd4e4

I updated to the new Recyclarr release and was noticing some strange releases getting downloaded that didn't seem consistent with what I was getting before the upgrade. It appears that Recyclarr is not syncing releases past the first 'term' in the streaming.json (I haven't checked any profiles past this).

Pictures to more clearly demonstrate what I am talking about:

Streaming.json from github. Bordered in red is the 'term' that is not syncing to Sonarr.

My Recyclarr.yaml showing which trash_ids I have configured.

Sonarr release profile for streaming services.

recommend splitting into 2 groups
1 that should be included in renaming (i.e. sources) to prevent loops
and 1 that is not to be included in renaming to prevent garbage naming
assumption: group is included in ones naming schema

I recently added your profiles to Sonarr, great work and fantastic resource! With the new setup, I'm seeing more downloads than I'd like, due to upgrades.

For currently airing shows, I'd love to see just two downloads:

• First release ASAP (or slight delay to skip 720 when 1080 lands a few minutes later).
• Second release 12-24 hours later: if I didn't watch the show immediately, let's wait for the best version

Do you think there's a way to accomplish this using delay profiles or other tricks?

Describe the Error
Currently the revision time for every page is the time of the most recent commit to the master branch.

Expected behavior
Revision time for every page is what it is supposed to be.

Solution
When checking out the code in the deploy workflow, set fetch-depth to 0.

Example:

https://github.com/timvink/mkdocs-git-revision-date-localized-plugin/blob/ccf498bab42e085b7190eed4a0aa48c4c807e3a0/.github/workflows/pythonpublish.yml#L11-L13

• Note that it should be fetch-depth and not fetch_depth; fetch_depth gives a warning: https://github.com/timvink/mkdocs-git-revision-date-localized-plugin/actions/runs/1579704317

Resources

• https://timvink.github.io/mkdocs-git-revision-date-localized-plugin/index.html#note-when-using-build-environments

** Which Guide **
Radarr

Describe the Error in the Guide
Found a new missing label,. DTS X; which is used in file names
https://www.whathifi.com/advice/dtsx-what-it-how-can-you-get-it

Expected behavior
A label added that detects DTS-X

Additional context
Below the filter. Note,this DTS-X als need to be excluded from the existing DTS, DTS-ES, DTS-HD MA, DTS-HD HR

{
"name": "DTS X",
"includeCustomFormatWhenRenaming": false,
"specifications": [
{
"name": "DTS X",
"implementation": "ReleaseTitleSpecification",
"negate": false,
"required": true,
"fields": {
"value": "dts[-. ]?x(?!\d)"
}
},
{
"name": "Not Basic DTS",
"implementation": "ReleaseTitleSpecification",
"negate": true,
"required": true,
"fields": {
"value": "DTS[ .]?[1-9]"
}
},
{
"name": "Not Basic Dolby Digital",
"implementation": "ReleaseTitleSpecification",
"negate": true,
"required": true,
"fields": {
"value": "\bDD(\b|\d)|(?<!e)ac3"
}
},
{
"name": "Not Dolby Digital Plus",
"implementation": "ReleaseTitleSpecification",
"negate": true,
"required": true,
"fields": {
"value": "[^-]dd[p+]|eac3"
}
},
{
"name": "Not TrueHD/ATMOS",
"implementation": "ReleaseTitleSpecification",
"negate": true,
"required": true,
"fields": {
"value": "TrueHD|\bATMOS(\b|\d)"
}
},
{
"name": "Not FLAC",
"implementation": "ReleaseTitleSpecification",
"negate": true,
"required": true,
"fields": {
"value": "\bFLAC(\b|\d)"
}
},
{
"name": "Not AAC",
"implementation": "ReleaseTitleSpecification",
"negate": true,
"required": true,
"fields": {
"value": "\bAAC(\b|\d)"
}
},
{
"name": "Not PCM",
"implementation": "ReleaseTitleSpecification",
"negate": true,
"required": true,
"fields": {
"value": "\b(l?)PCM(\b|\d)"
}
}
]
}

Synology Automated script.

When running the automated script I received the following error and the script halted

"ERROR get "Https://cr.htoio.dev/v2/"; x509:certificate has expired or is not yet valid"

So I'm still trying to wrap my head around your guide but I'm not a 100% clear on how the best way to use scores for the different CF's is. Like what you put as an example in your guide, I do want to implement the audio format order that you have there except I don't want FLAC, PCM, MP3, and OPUS.

My goal is to have the best 2160p release, of course. When I say best, my end target is TrueHD ATMOS plus Dolby Vision. I prefer DV vs. HDR10/HDR as my TV supports it. So my preference is a mix of both audio and video. I don't care about number of channels for now because higher channels almost always come with the higher quality audio formats anyway.

I'm setting up the hierarchy now based on what you said here:

But I'm not confident in what I did and I can't, for the love of God, figure this out. Here's what I have:

What is your suggestion with my scores? And as for the Upgrade Until CF Score value, would making it equal to the sum of all positive CF scores be wise?

It's a bit unnecessary to have to expand "V3" to see the Radarr guides now that v2 support has been dropped. The guides should be all at the root level now and clickable without expanding a tree node first.

Please AAC for Radarr v3.

Info

https://docs.docker.com/compose/cli-command/

Compose V2 and the new docker compose command🔗
Important

The new Compose V2, which supports the
compose command as part of the Docker CLI, is now available.

Compose V2 integrates compose functions into the Docker platform, continuing to support most of the previous docker-compose features and flags. You can test the Compose V2 by simply replacing the dash (-) with a space, and by running docker compose, instead of docker-compose.