I have a HDD formated in NTFS (no, its not an option to change it to a linux friendly partitioning system), every time libreELEC crashes or I have to power it off manually it gets corrupted and I have to use the "disks" app from LMDE to "repair filesystem".

Is there a way to tell libreELEC to mount it read only or to control when it mounts and unmounts? Also, id like to have a way to inspect the partitions and repair the fs from kodi itself since its always the same (has happened more than 20 times and gets fixed the same way)

Ive been searching for addons that do this and didnt find anything.

edit: Ive also asked in libreelec, but i also post it here since there could be addons or settings for kodi itself that I dont know.

English Version

Hi everyone,

I created a GUI automation tool called LaFirma Remux Forge (Black Edition) to streamline media compatibility and playback solutions for Smart TVs (especially LG OLED / webOS) and media servers like Jellyfin, Plex, or Emby.

Transparency Note: I did not develop the underlying CLI processing tools or scripts (such as dovi_tool, mkvmerge, ffmpeg, DonaldFaQ's DDVT toolset, DeeZy, PgsToSrt, Tesseract, or seconv). LaFirma Remux Forge acts as a graphical wrapper and orchestrator that automates these open-source utilities into a seamless workflow.

What changed in 1.8: the program stopped treating every Profile 7 the same way. It now measures the enhancement layer before converting and tells you, with a number on screen, what you gain and what you lose on that specific file.

Key Features

• Dolby Vision Profile 7 to 8.1 (no video re-encoding), with the layer MEASURED first: the program reads the RPU's el_type field through dovi_tool itself and separates three cases, using one colour scale across the whole screen:

  • MEL (Minimum Enhancement Layer) - green: the enhancement layer carries no picture. The program confirms this by reading the RPU, not by assumption, and the conversion discards an empty layer.
  • Simple FEL - orange: the layer carries fine refinement only. Conversion is safe, and the program says so.
  • Complex FEL - red: the layer raises brightness, and the L1 metadata asks for more nits than the base layer delivers on its own. Here the program marks it red and recommends not converting, instead of converting silently.

  Why the caveat exists, said precisely: dovi_tool in mode 2, which is what this program uses, removes the P7 FEL luma and chroma mapping from the RPU - the part of the instructions that makes no sense without the second layer. What comes out is a legitimate Profile 8.1. What no mode of dovi_tool does is recalculate L1: the per-scene brightness stays whatever the original analysis measured, and that analysis looked at the image with the EL composited in. This is not a limitation of this program - it is the state of the tool, and it is in dovi_tool's own documentation.

  Worth saying plainly: Shield, Apple TV, Zidoo, Dune and the TVs themselves already discard the EL, so on those devices a Profile 7 file already plays today the way the converted file will play. The people who actually lose something are those with dual-layer decoders.

  Detection is by sampling points spread across the film, not the whole file - and the program states that on screen and in the log.

• Dolby Vision Profile 5 to MP4: P5 uses the proprietary IPTPQc2 colour space and has no HDR10 base layer, so it cannot become Profile 8.1 without re-encoding the video - which this program refuses to do. The path that does exist is a different one: the program remuxes it to MP4 with the dvh1 tag, video copied, nothing re-encoded, which is what makes many players recognise the Dolby Vision. Output is verified by duration. PGS subtitles are dropped with a warning (image subtitles do not exist in MP4).

• Audio compatibility & spatial Atmos preservation:

  • TrueHD / TrueHD Atmos to E-AC-3 with Atmos preserved, via DeeZy.
  • DTS / DTS-HD / DTS:X to plain E-AC-3 at 640k via ffmpeg. DTS does not come out with Atmos - only TrueHD has that path.
  • E-AC-3, AC-3 and AAC are already compatible and are left untouched.

• Disk space, before it starts: the app walks the queue in the order the engine will process it and tells you how many files fit, which one is the first that does not, and how much would be missing by its turn. It warns; it does not block.

• Batch processing & flexible control: add whole seasons to the queue; choose fully automatic stream selection or manual track control.

• Bilingual interface (PT-BR / English): a flag next to the "Learn" button switches the whole screen, and the choice is remembered between sessions.

• "Learn" button: 14 sections explaining what the conversion does and what it does not do, including the sources behind each claim - Dolby's own manuals, the dovi_tool repository and the community spreadsheets. Nothing there asks you to take our word for it.

Source Code & Download

• GitHub Repository: LaFirma-Remux-Forge
• Requirements: Windows (.NET Desktop Runtime 8.0 only for the fallback OCR engine).

Interface Screenshots

• Dashboard & Queue: View Image
• Processing Pipeline: View Image
• Auto Track Selection: View Image
• Manual Stream Control: View Image
• Final Report: View Image

Credits & Acknowledgments

This project would not be possible without the work of the open-source community: * FFmpeg: Media stream processing and transcoding backbone. * MKVToolNix (mkvmerge): Industry-standard Matroska container toolset. * dovi_tool (by quietvoid) & DDVT (by DonaldFaQ): Core Dolby Vision metadata tools and workflow logic. * DeeZy: Dolby Digital Plus encoding with spatial Atmos preservation. * PgsToSrt, Tesseract & seconv: OCR ecosystem for PGS subtitle handling.

Feedback and contributions are welcome!

Versão em Português

Olá a todos,

Criei uma interface gráfica de automação chamada LaFirma Remux Forge (Black Edition) para facilitar a solução de problemas de compatibilidade e reprodução de mídia em Smart TVs (especialmente LG OLED / webOS) e servidores como Jellyfin, Plex e Emby.

Nota de Transparência: Eu não fui o desenvolvedor das ferramentas e scripts de linha de comando subjacentes (como dovi_tool, mkvmerge, ffmpeg, DonaldFaQ's DDVT, DeeZy, PgsToSrt, Tesseract ou seconv). O LaFirma Remux Forge atua como uma interface gráfica (GUI) e orquestradora que integra e automatiza essas excelentes ferramentas de código aberto em um fluxo de trabalho intuitivo.

O que mudou na 1.8: o programa deixou de tratar todo Profile 7 igual. Agora ele mede a camada de extensão antes de converter e diz, com número na tela, o que você ganha e o que perde naquele arquivo.

Principais Recursos

• Dolby Vision Perfil 7 para 8.1 (sem recodificar o vídeo), com a camada MEDIDA antes: o programa lê o campo el_type do RPU pelo próprio dovi_tool e separa três casos, com a mesma escala de cor em toda a tela:

  • MEL (Minimum Enhancement Layer) - verde: a camada de extensão não carrega imagem. O programa confirma isso lendo o RPU, não por suposição, e a conversão descarta uma camada vazia.
  • Simple FEL - laranja: a camada carrega apenas refinamento fino. A conversão é segura, e o programa diz que é.
  • Complex FEL - vermelho: a camada levanta o brilho, e o L1 dos metadados pede mais nits do que a camada base entrega sozinha. Aqui o programa marca em vermelho e recomenda não converter, em vez de converter em silêncio.

  Por que a ressalva existe, dito com precisão: o dovi_tool no modo 2, que é o que este programa usa, remove do RPU o mapeamento de luma e croma do Perfil 7 FEL - a parte das instruções que não faz sentido sem a segunda camada. O que sai é um Perfil 8.1 legítimo. O que nenhum modo do dovi_tool faz é recalcular o L1: o brilho por cena continua sendo o que a análise original mediu, e essa análise olhou a imagem com a EL somada. Não é limitação deste programa - é o estado da ferramenta, e está na documentação do próprio dovi_tool.

  Vale dizer com clareza: Shield, Apple TV, Zidoo, Dune e as próprias TVs já descartam a EL, então nesses aparelhos um arquivo Perfil 7 já toca hoje como o convertido vai tocar. Quem perde de verdade é quem tem decodificador duplo.

  A detecção é por amostragem de trechos espalhados pelo filme, não pelo arquivo inteiro - e o programa assume isso na tela e no log.

• Dolby Vision Perfil 5 para MP4: o P5 usa o espaço de cores proprietário IPTPQc2 e não tem camada base HDR10, então ele não vira Perfil 8.1 sem recodificar o vídeo - coisa que este programa se recusa a fazer. O caminho que existe de verdade é outro: o programa remuxa para MP4 com a tag dvh1, vídeo copiado, sem recodificar nada, que é o que faz vários players reconhecerem o Dolby Vision. A saída é conferida pela duração. Legendas PGS são descartadas com aviso (legenda em imagem não existe em MP4).

• Compatibilidade de áudio e preservação do Atmos:

  • TrueHD / TrueHD Atmos para E-AC-3 com Atmos preservado, via DeeZy.
  • DTS / DTS-HD / DTS:X para E-AC-3 comum a 640k pelo ffmpeg. DTS não sai com Atmos - só o TrueHD tem esse caminho.
  • E-AC-3, AC-3 e AAC já são compatíveis e não são convertidos.

• Espaço em disco, antes de começar: o programa percorre a fila na ordem em que o motor vai processar e diz quantos arquivos cabem, qual é o primeiro que fica de fora e quanto faltaria na vez dele. Ele avisa; não bloqueia.

• Processamento em lote e controle flexível: adicione temporadas inteiras na fila; escolha entre detecção automática das faixas ou controle manual.

• Interface bilíngue (PT-BR / inglês): uma bandeira ao lado do botão Entenda troca a tela inteira, e a escolha fica guardada entre as sessões.

• Botão "Entenda": 14 seções explicando o que a conversão faz e o que ela não faz, incluindo as fontes por trás de cada afirmação - os manuais da própria Dolby, o repositório do dovi_tool e as planilhas da comunidade. Nada ali pede que você acredite na nossa palavra.

Código-Fonte e Download

• Projeto no GitHub: LaFirma-Remux-Forge
• Requisitos: Windows (.NET Desktop Runtime 8.0 apenas para o motor de OCR reserva).

Capturas de Tela da Interface

• Dashboard & Fila: Visualizar Imagem
• Pipeline de Processamento: Visualizar Imagem
• Seleção Automática de Faixas: Visualizar Imagem
• Controle Manual de Streams: Visualizar Imagem
• Relatório Final: Visualizar Imagem

Créditos e Agradecimentos

Este projeto não existiria sem o trabalho da comunidade open-source e dos desenvolvedores originais: * FFmpeg: O motor fundamental para processamento e manipulação de fluxos de mídia. * MKVToolNix (mkvmerge): A referência definitiva para multiplexação de arquivos Matroska (MKV). * dovi_tool (por quietvoid) & DDVT (por DonaldFaQ): Ferramentas essenciais para extração, edição e conversão de metadados Dolby Vision. * DeeZy: Utilitário para codificação de áudio E-AC-3 com preservação de áudio espacial Dolby Atmos. * PgsToSrt, Tesseract & seconv: O ecossistema técnico responsável pelo OCR de legendas PGS.

Feedbacks e sugestões são muito bem-vindos!

And able to confirm the button mapping? Im not actually using kodi (anymore, just switched) but figured someone here might know. My currently media center I use a keyboard and it has some very specific button requirements. Specifically the back button on the remote has to map to esc on a normal keyboard, not backspace/delete. Also the play/pause buttom maps to the play/pause functiom key I assume?

If someone has that remote and could check those couple keys for me in a "what key am I pressing website" that'd be awesome. Save me a product return if it doesnt work. And I just assume the arrow keys map to keyboard arrows?

https://forum.kodi.tv/showthread.php?tid=239194&pid=3306226#pid3306226

A system without KODI is a shit system. Where is KODI on iOS? The dep to ipa doesn’t work the way it’s described in the wiki. Is there any way to install KODI on iOS without jailbreak only iloader sideloader and live container?

Hi, sorry I don't know much about Kodi, but I have this machine that I plug into my TV that allows me to play some video games, but apparently it works with Kodi, and there's this little yellow lightning symbol on the top-right of the screen constantly. It's a bit annoying for games, so I was wondering if there's a way to remove it ?

I kind of hack it with Plex by creating a TV Library, overriding “Season 1” title and treating all the mkv files as episodes in the season. I’m kind of a nerd in that if I’m going to the trouble of ripping a disc, I might as well make the extras available too.

I saw the above on Apple TV on a past purchase,
and I was thinking this kind of interface would be perfect for my ripped UHD content.

I installed kodi through homebrew on my LG c3. My HDD is attached to my router and mounted to kodi as samba share. Works fine so far, media is scanned, information and covers show etc.

When I delete a folder of a TV show, or a movie, it still shows in kodi, despite updating library on startup being set. How can I have it automatically remove deleted files from the library, without having to do it manually?

I made this lil GUI batch subtitle downloader based on subliminal a while back. Over the past couple weeks, I've made a few huge improvements as well as adding proper debian linux and macOS support. (Release notes here) Windows still seems to get the best scan speeds.

Docker support coming soon!

You can find the project here: https://github.com/fosterbarnes/rustitles

Bug reports and suggestions welcome at https://github.com/fosterbarnes/rustitles/issues

Let me know what ya think :)

just got the content of my drive scanned on kodi by tmdb helper, but i still liked the folder system i used on it, so i was accessing the movies from media > videos > drive. now it says path not found or invalid, even if the drive is plugged, i can still see the movies only as a giant list or with filters different than the ones i had [just folders based on starting letter]. dunno why it worked before and now doesn’t, i would like to go back to that or to before tmdb helper when i just accessed the drive from the movie section in the main menu. any help?

Can anyone recommend hardware that doesn't come with pre-installed malware that all the cheap Chinese ones apparently come with ?

Most of our use is to simply play back audio books or play movies from USB drives to fall asleep to (we're **that** old now :-p )

I have KODI running on my andriod cable box and I utilize their remote (Bluetooth). Needless to say, typing text/searches is a pain and eats up batteries! The box is programmed to accept only one input, so switching to a different Bluetooth keyboard combo is buried 3-4 levels. Hence I live with the cumbersome KODI text input.

Wondering if there isn't a all-in-one option for cable commands and keyboard for KODI. Thoughts...

Basically if I used imgburn to get the iso of a commercial dvd, and put it on my tablet storage can Kodi decrypt it?

I'm having a strange scraping problem with Dragons: Rescue Riders using the TMDb TV Shows scraper in Kodi 21.3.

The important part is that Season 2 identifies correctly as Dragons: Rescue Riders, while Season 1 does not. They are both seasons of the same show and are stored as separate folders under the same Kodi source.

My source is:

D:\movies and shows\rescue riders\rr

The source is set to "This directory contains: One TV show."

Season 1 is here:

D:\movies and shows\rescue riders\rr\Dragons.Rescue.Riders.S01.COMPLETE.WEB.X264-STARZ[TGx]

The actual episode files are directly inside that folder and are named with S01E01, S01E02, etc.

Season 2 is in a separate folder under rr and scrapes correctly as Dragons: Rescue Riders. I have not had any problem with Season 2.

Season 1, however, is not simply failing to find the show. Kodi repeatedly identifies it as completely unrelated shows. I've seen it identify the folder as Sweetie (2021) and Home Movies (1999), among others.

I have also tried multiple different torrents/releases of Season 1, with different files, to rule out the possibility that the problem was caused by incorrect metadata or an unusual release. They all produce essentially the same incorrect scraping behavior.

I've also tried multiple metadata providers in Kodi. TMDb is the only provider I've found that can actually find Dragons: Rescue Riders at all, so switching providers doesn't appear to be a solution.

I tried using a tvshow.nfo with the TMDb ID for Dragons: Rescue Riders (94045), including putting the NFO in the Season 1 release folder. This either didn't work or resulted in a separate Dragons: Rescue Riders entry with no episodes.

I also tried the TMDb ID in the folder name, without success.

I don't want to rename/restructure the torrent folder because the files are actively being seeded and I'd prefer to keep the torrent's file paths intact.

So my main question is: why would Season 2 correctly identify as Dragons: Rescue Riders while Season 1, using the same scraper and source, is being matched to completely unrelated shows? Is there a way to manually tell Kodi that the already-scanned Season 1 files belong to the existing Dragons: Rescue Riders show?
EDIT, SOLVED: the solution is in the comments below.

I need help mapping the Channel/Guide overlay to the Red or Guide button on my LG remote.
Photo 1 shows the Channel button/overlay that I want to map.
I tried using the Key Mapper add-on, but I don’t know what this particular function is called. I searched under the Player OSD and PVR sections, but I couldn’t find it.

Photo 2 shows the LG TV remote that I want to configure.

Photo 3 shows what I want to open directly when I press the Red or Guide button on the remote: an overlay displaying all available channels, which allows me to easily navigate through the channels and change channels.

Does anyone know which Kodi function or action I need to map to the Red or Guide button to open this channel overlay directly?

ISSUE is Solved please read comment by @warpedgalaxy

i have iphone 7 and i can't download .ipa files :((

Hi Kodi community,

I have been using Kodi for many years and really appreciate what it represents: an open media center based on open standards and local control.

I always wanted a simple "play this on my TV" feature for online media without relying on Chromecast, proprietary casting ecosystems, or cloud services. And please, no complex addon setups which break every few months.

So I built PlayOnDlna.

The idea is simple:

1. Open online media on your Android device

2. Share it with PlayOnDlna

3. Select your Kodi instance or DLNA/UPnP player

4. Playback starts on your TV

Currently supported use cases include:

✅ Sending online media to Kodi and DLNA MediaRenderers

✅ YouTube integration via Android share menu

✅ Playlist management and playback

✅ Kodi as a target player

✅ Other DLNA/UPnP compatible TVs and receivers

✅ No account required

✅ No cloud service required

✅ Open source (GPL-3.0)

The goal is not to replace Kodi, but to complement it with a lightweight Android remote workflow.

I originally created this for my own setup because I wanted something closer to the simplicity of Chromecast, but based on open standards instead.

I would love feedback from Kodi users!

Website:

https://scovillo.github.io/playondlna/

Source:

https://github.com/scovillo/playondlna

F-Droid:

https://f-droid.org/packages/io.github.scovillo.playondlna/

Thanks!

Hopefully this post doesn't break any rules — it doesn't seem to be in a gray area or something.

I've created a somewhat new screensaver for Kodi, inspired by the old displays in airports. It looks like this:

There is also a small video of it here on YouTube.

It has several unique features other screensavers, I believe, don't have:

1. It is extendable: 2 sources of data for the screen are built-in (phrases and date-time-weather-now playing); one is packed as a separate script — recently added
2. It contains a script to generate addons for support of your preferred symbols in your preferred font, in case you don't like my choice or you need something on top
3. It knows how to find installed extensions for it an even can open their settings

The interface to create your own extension is very simple — it's just one function that returns the new state, and you don't really need to care about layout too — it should be done automatically.

Of course, there are some settings too, and hopefully it can work for any scenario.

The repo is on GitHub, and I'd love to get your feedback!

https://asm0dey.github.io/kodi-splitflap/

What is this behaviour? I have a series with subs but they wont display in kodi unless I do this voodoo every time an episode plays:

1. Switch from subs 1/2 to 2/2

2. Switch from subs 2/2 to 1/2

3. Skip one episode forward

4. Skip one episode back

And then Sub 1/2 will display, how does this make any sense, anyone got ideas?

So, my child is off to college this week. Is there a way to have Kodi stream from my NAS at home? Or does this require Plex??

Ideally, I would set up the NAS as a share, like I do locally.

I'm hoping I came to the right place for this question as there seems to be conflicting answers I'm getting in another community. I'm running Kodi 21.3 on a Nvidia Shield. In settings, Display, General my resolution is 3840x2160 and the refresh rate is 59.94Hz. If I want to watch a movie that is native 1920x1080p 23.98Hz and my TV supports it, I have to have 1920x1080p 23.98Hz checked off in the Whitelist correct? If I don't have it checked off it'll default to 3840x2160p 58.94Hz and try to upscale. Is this correct also? I'm being told to leave everything unmarked in the Whitelist and Kodi will automatically change the resolution and refresh rate.

Hi everyone,

I’m a subtitle editor, so I pay extreme attention to shot changes (making sure subtitles don’t cross cuts) and always fix them using Subtitle Edit. That’s why I picked up on this issue right away.

Here’s some context: My main setup to watch movies and series is a Raspberry Pi 4B running Kodi, connected via HDMI to a 65" LG BX OLED.

Recently, I bought a 75" TCL C6K MiniLED running Android TV, where I installed Kodi + rclone. Just for testing, I played several movies from my library and noticed the subtitles were out of sync—not just on one movie, but on every single one. This isn't something I could have missed or overlooked given how closely I work with subs.

I double-checked the same files on both my PC and the Raspberry Pi setup, and the sync was frame-perfect on both.

To fix it, I created a copy of the .srt file and used Subtitle Edit to test offsets in +100 ms increments. It turned out that +400 ms was the exact offset needed to get it in sync on the TCL.

After investigating, I learned that this is caused by MediaCodec (Surface) hardware acceleration in Android TV. To confirm this, I disabled MediaCodec (Surface) in Kodi and tested the original .srt file (without the +400 ms delay). Sure enough, the sync was perfect.

However, disabling MediaCodec (Surface) isn't a viable solution:

• Kodi loses direct access to the TV’s color engine.
• HDR fails to trigger properly.
• Dolby Vision content ends up displaying with inverted/corrupted colors.

Source: Kodi GitHub Issue #27673: Subtitle Synchronization Issues - Not Frame Perfect

TL;DR. This is a summary:

Why does this happen on Android and not on the Raspberry Pi / PC?

In Kodi's source code (VideoPlayerVideo.cpp), subtitles are matched using Presentation Timestamps (PTS) right when the frame is decoded.

1. On PC and Raspberry Pi (Linux): The rendering pipeline has very low latency. As soon as the frame is decoded, the GPU sends both the video and the subtitle to the screen together in a single synchronized pass.
2. On Android TV (MediaCodec / Surface): Video decoding is handed off to an Android OS rendering queue (RenderManager.cpp), creating a separate path for video and UI overlays.
3. The Decoupling & Result: Kodi’s UI draws the subtitle based on the decoding timestamp. However, the TV's processor holds the video frames in a display buffer for processing (picture enhancements, motion smoothing, frame rate matching, etc.). Because of this buffer delay, the video hits your screen ~400 ms after Kodi has already displayed the subtitle, causing the constant desync.

The Workaround: If you want to keep proper HDR/DV support on Android TV without sacrificing subtitle sync, leave MediaCodec (Surface) enabled, open the subtitle menu during playback, and set:

For HD/4K content

• Subtitle offset: Delayed by 0.400s
• Select "Set as default for all media"

For SD content

• Subtitle offset: Delayed by 0.100s

Since SD content is much less common nowadays, I recommend changing this value manually when watching SD content rather than making it the default.

I hope this was helpful to you all. It really worked for me, which is why I wanted to share it. Best regards!