starred/Radarr

Fork 0

mirror of https://github.com/Radarr/Radarr.git synced 2026-03-02 22:57:34 -05:00

Radarr doesn't detect Spanish (Latino) #8072

New issue

Open

opened 2026-02-20 00:00:12 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-20 00:00:12 -05:00

Owner

Originally created by @Zorro92 on GitHub (Nov 30, 2023).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

I set up language filters, specifically I look for Spanish + Spanish Latino. Sometimes Spanish tracks are labeled as Latino. I also set up radarr to name the file accordingly to include what language tracks are included, for example [ES + EN]. When a Latino track is detected it does this correctly, the file is tagged with [LA + EN] and if I click the mediainfo button it shows the two tracks there, however, radarr doesn't add Latino as a second language (Spanish Latino) only the English track. Resulting in my scores being lower and likely having the file trumped by another release. For regular Spanish everything works fine.

Expected Behavior

Radarr should detect Spanish (Latino) as a language and keep it's score

Steps To Reproduce

No response

Environment

- OS: Linux
- Radarr: 5.1.3.8246-ls194
- Docker Install: yes
- Using Reverse Proxy: no
- Browser: chrome
- Database: Sqlite 3.41.2

What branch are you running?

Master

Trace Logs? Not Optional

https://privatebin.net/?697046c3ef79765e#GLM1Nzi5dskDaeU35DN2sS8U5TQGhpSzcqJJmEUmgXyZ

Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @Zorro92 on GitHub (Nov 30, 2023). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior I set up language filters, specifically I look for Spanish + Spanish Latino. Sometimes Spanish tracks are labeled as Latino. I also set up radarr to name the file accordingly to include what language tracks are included, for example [ES + EN]. When a Latino track is detected it does this correctly, the file is tagged with [LA + EN] and if I click the mediainfo button it shows the two tracks there, however, radarr doesn't add Latino as a second language (Spanish Latino) only the English track. Resulting in my scores being lower and likely having the file trumped by another release. For regular Spanish everything works fine. ### Expected Behavior Radarr should detect Spanish (Latino) as a language and keep it's score ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: Linux - Radarr: 5.1.3.8246-ls194 - Docker Install: yes - Using Reverse Proxy: no - Browser: chrome - Database: Sqlite 3.41.2 ``` ### What branch are you running? Master ### Trace Logs? **Not Optional** https://privatebin.net/?697046c3ef79765e#GLM1Nzi5dskDaeU35DN2sS8U5TQGhpSzcqJJmEUmgXyZ ### Trace Logs have been provided as applicable. Reports will be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman added the

Type: Bug

Status: Investigating

Area: Tooling

labels

2026-02-20 00:00:12 -05:00

deekerman commented

2026-02-20 00:00:13 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Nov 30, 2023):

Radarr: Latest is not a valid version
logs show nothing relating to radarr parsing anything nor anything that would indication spanish (latino)
LA isn't valid for spanish (latino) currently
github.com/Radarr/Radarr@073d15160d/src/NzbDrone.Core/Parser/IsoLanguages.cs (L49)

provide the ffprobe output

from within the container

/app/bin/ffprobe -v quiet -print_format json -show_format -sexagesimal -show_streams -i "/path/to/file"

@bakerboy448 commented on GitHub (Nov 30, 2023): - `Radarr: Latest` is not a valid version - logs show nothing relating to radarr parsing anything nor anything that would indication spanish (latino) - `LA` isn't valid for spanish (latino) currently https://github.com/Radarr/Radarr/blob/073d15160d259a30d00c448181e76cca7d9995a2/src/NzbDrone.Core/Parser/IsoLanguages.cs#L49 provide the ffprobe output from within the container ```bash /app/bin/ffprobe -v quiet -print_format json -show_format -sexagesimal -show_streams -i "/path/to/file" ```

deekerman commented

2026-02-20 00:00:13 -05:00

Author

Owner

@Zorro92 commented on GitHub (Nov 30, 2023):

Sorry, updated my original post. I couldn't find anything related in the logs either.

https://privatebin.net/?9ad21133aad31868#h4nyiHBryq9QvkmQh4dN9A7CgRdGQq36nq1G9Jth8db

@Zorro92 commented on GitHub (Nov 30, 2023): Sorry, updated my original post. I couldn't find anything related in the logs either. https://privatebin.net/?9ad21133aad31868#h4nyiHBryq9QvkmQh4dN9A7CgRdGQq36nq1G9Jth8db

deekerman commented

2026-02-20 00:00:13 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Nov 30, 2023):

first audio track - ffprobe parses as lat

            "tags": {
                "language": "lat",
                "BPS": "191999",
                "BPS-eng": "191999",
                "DURATION": "01:42:09.128000000",
                "DURATION-eng": "01:42:09.128000000",
                "NUMBER_OF_FRAMES": "175973",
                "NUMBER_OF_FRAMES-eng": "175973",
                "NUMBER_OF_BYTES": "147099062",
                "NUMBER_OF_BYTES-eng": "147099062",
                "_STATISTICS_WRITING_APP": "mkvmerge v19.0.0 ('Brave Captain') 64-bit",
                "_STATISTICS_WRITING_APP-eng": "mkvmerge v19.0.0 ('Brave Captain') 64-bit",
                "_STATISTICS_WRITING_DATE_UTC": "2018-01-25 22:55:10",
                "_STATISTICS_WRITING_DATE_UTC-eng": "2018-01-25 22:55:10",
                "_STATISTICS_TAGS": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES",
                "_STATISTICS_TAGS-eng": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES"
            }

las is what it looks like it latin american should be

lat is latin - github.com/FFmpeg/FFmpeg@a30adf9f96/libavformat/isom.c (L222)

@Qstick - seems either close as encoder issue won't fix or bandaid in servarr FFmpeg?

@bakerboy448 commented on GitHub (Nov 30, 2023): first audio track - ffprobe parses as `lat` ```json "tags": { "language": "lat", "BPS": "191999", "BPS-eng": "191999", "DURATION": "01:42:09.128000000", "DURATION-eng": "01:42:09.128000000", "NUMBER_OF_FRAMES": "175973", "NUMBER_OF_FRAMES-eng": "175973", "NUMBER_OF_BYTES": "147099062", "NUMBER_OF_BYTES-eng": "147099062", "_STATISTICS_WRITING_APP": "mkvmerge v19.0.0 ('Brave Captain') 64-bit", "_STATISTICS_WRITING_APP-eng": "mkvmerge v19.0.0 ('Brave Captain') 64-bit", "_STATISTICS_WRITING_DATE_UTC": "2018-01-25 22:55:10", "_STATISTICS_WRITING_DATE_UTC-eng": "2018-01-25 22:55:10", "_STATISTICS_TAGS": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES", "_STATISTICS_TAGS-eng": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES" } ``` `las` is what it looks like it latin american should be `lat` is latin - https://github.com/FFmpeg/FFmpeg/blob/a30adf9f96254f4870066c98a6dbf13fc74515a3/libavformat/isom.c#L222 @Qstick - seems either close as encoder issue won't fix or bandaid in servarr FFmpeg?

deekerman commented

2026-02-20 00:00:13 -05:00

Author

Owner

@Qstick commented on GitHub (Dec 31, 2023):

@Qstick - seems either close as encoder issue won't fix or bandaid in servarr FFmpeg?

How would be bandaid it? We have no clue if it's right or not if it's lat in the output

@Qstick commented on GitHub (Dec 31, 2023): > @Qstick - seems either close as encoder issue won't fix or bandaid in servarr FFmpeg? How would be bandaid it? We have no clue if it's right or not if it's `lat` in the output

deekerman commented

2026-02-20 00:00:14 -05:00

Author

Owner

@houcros commented on GitHub (Dec 20, 2025):

If I may be allowed to piggyback on this issue, I'm having a similar situation, i.e. trying to download "Español" but Radarr is grabbing "Español Latino" (both these languages are selectable for custom formats). I think at least part of the issue is that there is no ISO 639 code for "Español Latino" (and from the ffmpeg link above I see ISO 639 is used). AFAIU "Español Latino" should be tagged in the audio track as "es-419 for Latin American Spanish" (reference) or es-AR, es-MX, etc. But I don't know if ffmgep supports that, and anyhow it seems that everyone is tagging Español Latino as "spa".

I was wondering if a workaround could be to try to interpret the audio tag title, if available. For example, I have a movie with these audio tags:

            "tags": {
                "language": "spa",
                "title": "Español Latino",
                "BPS": "448000",
                "DURATION": "01:56:33.664000000",
                "NUMBER_OF_FRAMES": "218552",
                "NUMBER_OF_BYTES": "391645184",
                "_STATISTICS_WRITING_APP": "mkvmerge v65.0.0 ('Too Much') 64-bit",
                "_STATISTICS_WRITING_DATE_UTC": "2022-02-16 13:46:59",
                "_STATISTICS_TAGS": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES"
            }

Alas, the language is "spa" as usual, but the title could be used to realise it's "Español Latino". I don't know how feasible this would be to implement, and how effective (I hope the title is given most of the times, but I have no data to support this hope), but I'd be keen to hear your thoughts. :)

@houcros commented on GitHub (Dec 20, 2025): If I may be allowed to piggyback on this issue, I'm having a similar situation, i.e. trying to download "Español" but Radarr is grabbing "Español Latino" (both these languages are selectable for custom formats). I think at least part of the issue is that there is no [ISO 639 code](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) for "Español Latino" (and from the ffmpeg link above I see ISO 639 is used). AFAIU "Español Latino" should be tagged in the audio track as "es-419 for Latin American Spanish" ([reference](https://en.wikipedia.org/wiki/IETF_language_tag)) or es-AR, es-MX, etc. But I don't know if ffmgep supports that, and anyhow it seems that everyone is tagging Español Latino as "spa". I was wondering if a workaround could be to try to interpret the audio tag title, if available. For example, I have a movie with these audio tags: ``` "tags": { "language": "spa", "title": "Español Latino", "BPS": "448000", "DURATION": "01:56:33.664000000", "NUMBER_OF_FRAMES": "218552", "NUMBER_OF_BYTES": "391645184", "_STATISTICS_WRITING_APP": "mkvmerge v65.0.0 ('Too Much') 64-bit", "_STATISTICS_WRITING_DATE_UTC": "2022-02-16 13:46:59", "_STATISTICS_TAGS": "BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES" } ``` Alas, the language is "spa" as usual, but the title could be used to realise it's "Español Latino". I don't know how feasible this would be to implement, and how effective (I hope the title is given most of the times, but I have no data to support this hope), but I'd be keen to hear your thoughts. :)

deekerman commented

2026-02-20 00:00:14 -05:00

Author

Owner

@houcros commented on GitHub (Dec 21, 2025):

and how effective (I hope the title is given most of the times, but I have no data to support this hope)

After checking other movies in my library, I'm afraid this wouldn't be effective at all. :( Out of a couple dozen movies I know are in "Español Latino", there was only one with that as the audio tag title. All the rest just say "Spanish" or (rarely) "Español" (and all are tagged with language "spa"). I'm afraid it's impossible for Radarr to detect "Español Latino" correctly, because (if my particular collection is any indication of the general situation) that language is (almost) never tagged properly.

@houcros commented on GitHub (Dec 21, 2025): > and how effective (I hope the title is given most of the times, but I have no data to support this hope) After checking other movies in my library, I'm afraid this wouldn't be effective at all. :( Out of a couple dozen movies I know are in "Español Latino", there was only one with that as the audio tag title. All the rest just say "Spanish" or (rarely) "Español" (and all are tagged with language "spa"). I'm afraid it's impossible for Radarr to detect "Español Latino" correctly, because (if my particular collection is any indication of the general situation) that language is (almost) never tagged properly.