Atmos content is being missed #2331
Replies: 1 comment
-
In the case of ATMOS, Kometa runs these regex:
Kometa/defaults/overlays/audio_codec.yml Line 64 in 83dd84c Against:
Kometa/defaults/overlays/audio_codec.yml Line 98 in 83dd84c The The filepath is checked because most of these overlays expect TRaSH file naming; this sort of thing:
Kometa doesn't access the actual media file itself at all. If this "commercial title" is available via PlexAPI, of course support could be added, it's only typing, but I don't see it mentioned here: |
Beta Was this translation helpful? Give feedback.
-
I am using the latest version of Kometa in Docker. I have hundreds of Dolby Atmos Media files, but only 12 are correctly categorized and receive the appropriate poster modification regarding the Atmos audio format. As far as I can tell from the docs, Kometa only uses "audio_track_title" (that corresponds to Title in the metadata as listed by MediaInfo). Most of my media lists the Atmos descriptive title in the field called "Format_Commercial_IfAny" of the Audio metadata (this field is also referred to as "Commercial Title" by MediaInfo. If I copy the value of the "Format_Commercial_IfAny/Commercial Title" field to the "Title/audio_track_title" field, the media then appears in both my Atmos categories list and with the correct (Atmos) audio info on the poster. I am trying to avoid writing a script to do this. Is there a way to alter Kometa to check both fields to more accurately determine the type of audio contained in the media?
Beta Was this translation helpful? Give feedback.
All reactions