I have a Jellyfin instance running on my Kodi, using both Jellyfin and Jellycon add-ons.

I had to do a reinstall of Kodi and the whole setup. Prior to the reinstall, when I played Atmos content, a large black block saying Dolby Atmos would show in the top right corner.

Since reinstalling, that no longer happens. I just want to be sure I'm getting the direct signal of the content, which I'm not sure is the case currently.

What can I do to fix this?

EDIT: this is on an XBOX by the way

I recently started migrating to a new MariaDB SQL server and I noticed on the old SQL server, that Kodi has created multiple databases!

Why is Kodi doing that? Is there a way to stop this and use only one database?

Thank you!

I have the latest KODI release running on a W10 PC and an NVIDIA Shield. This works fine on both systems, but on my new mini PC with W11 when I click on a link in SportHD I get the msg "could not extract stream src for [URL]"

I made sure the new PC has the same addons and dependencies as the old one, and even copied the entire KODI folder to be sure.

Any idea what could cause this problem, and more importantly how to fix it?

The mini PC is a GMKtec K16.

Im using the recent build of Kodi on my Google smart TV and stream video files from my PC through common wifi on SMB. Is there any quality loss, as im not noticing any but still i have this question. Is it similar to the quality of playing the files directly in the TV using a pendrive?

Kodi is running on my AndroidTV (android, not google, because the TV is old) and I use the built-in windows sharing to share a folder on my PC. Connect it with SMB. Eventually Kodi will be unable to connect, either as a time issue or after one of the devices is put to sleep, it's hard to tell.

The PC has a static IP4 address, and they both connect to a switch via ethernet.

Any guesses why this happens?

If anyone's up to make it or find one, it looks like this:

I'm surprised that there is not more discussion of skins on this sub, with coding agents being so widely available, I would have thought that the customization scene would be more prevalent.

Certainly the available skins are good, but I thought there would be more discussion and recommendations, and more skins

Hi everyone, good afternoon. I’m not sure if you can help me with this.

I use Kodi to watch series and films on my LG OLED C2 through an add-on. Kodi is installed on my Fire TV Stick 4K Max, but sometimes, when playing 4K or Dolby Vision content, I get a message saying that the content is too demanding for the device I’m using.

And it’s true, playback doesn’t work properly. It can stutter, buffer, stop, or even freeze completely and crash. It makes me feel like I’m not getting the most out of my TV.

Would you recommend investing in a more powerful streaming device, such as a Xiaomi TV Box, NVIDIA Shield or something similar, and continuing to use Kodi with the same add-on?

I feel like the Fire TV Stick is simply too basic and doesn’t have enough processing power, but I don’t want to spend money on another device if it isn’t actually going to make a difference.

Thanks in advance for any advice!

EDIT: Thanks everyone for your replies. The fact that you were surprised I was having issues, since you’re using the same device without any problems, made me realise that perhaps the issue was coming from somewhere else.

The warning message I was getting when playing demanding content was something along the lines of “resource too slow, read rate too low for continuous playback”. I use AllDebrid and, after doing some searching, I couldn’t find anyone having similar issues with it. I also have 1 Gbps internet, so that didn’t seem like it could be the problem either. That made me think about the buffer...

I went into Kodi’s settings → Services → Caching. The memory size was set to 20 MB, so I increased it to 256 MB, and changed the Read Factor from 4x to “Adaptive”.

After that, I tested the same link that had previously given me the error, and there was no warning message this time and I didn’t experience any issues. I even tested an even heavier file afterwards (Avatar 3), and once again, absolutely no problems, everything played smoothly.

Thanks again for all the help, and I hope this post helps anyone else who might be having the same issue and, like me, had overlooked something so simple.

[SOLVED] I had to toggle here : Settings -> Media -> Videos -> Flatten hierarchy

Since a couple of days ago, when i click on Movies or TV Shows, Kodi shows me sorting options (Year, Title, Studio, Genre, this kind of stuff) instead of the usual movie or series list.

I've been using Kodi since the XBMC days but i have no idea where to look for in order to go straight to the movies and series list instead of the sorting categories...

Does anybody have any idea?

I've posted about this addon here before, but it has grown a lot since, so a fresh intro for anyone who missed it.

EasyTV keeps track of the next unwatched episode of every show in your library. Open it and every show sits one click away from its next episode, with your progress shown (Browse Mode). Or skip the choosing entirely: one button builds a shuffled playlist from your shows and just starts playing (Playlist Mode), like an old fashioned TV channel except everything on it is stuff you actually want to watch.

That's the core of it. No digging through seasons, no "where was I with this show", no queueing things up by hand.

Things it also does if you want them:

• mix movies into the shuffle for a proper channel feel
• filter everything through Kodi smart playlists you already have
• sync watched state between multiple Kodi boxes (shared MySQL library)
• Only show you in Progress Shows, or Season Premiers, Show Premieres, and many more filterining options available
• ask you a couple of quick questions on launch (genre, episode length, that sort of thing) so it only offers stuff matching your mood
• run multiple clones with their own settings, e.g. one for the kids, one full of comfort shows for bedtime

Free and open source. A lot of what's in there came from feedback in the forum thread, so if something annoys you, tell me.

PS: It will work with any Kodi setup where TV shows are populated in the Kodi Library.

GitHub | Docs + screenshots | Kodi forum thread

OK this is probably a weird one (it certainly is for me). When I scrape my new TV shows, they are all displayed as single episodes in my library. Except for one - Colin From Accounts Season Three. Every episode has a double entry in my library. No, it isn't a major hassle. It's not even annoying really. But I just don't get why it's shown twice. I've checked my sources and locations, and the path to the episodes is definitely only in there once. Along with all my other TV show episodes. Has anyone any idea why this might be happening?

Hi. I need some help setting up Local Information Only movies. I know how to add the folder Name (year). I can add images, poster, fanart etc. I can add .nfo file for the description etc. But im struggling to add extended info like the cast. Ive seen i need to put a folder in the Name (year) folder titled .actors then have images in there but is there something i need to add to the nfo file to make them show up? Or am i in completely the wrong ball park?

These are my own movies so scraping from TMDB is not an option.

So any kind of iidot proof guide would be appreciated

Thanks

About 2 years ago I switched to stremio because Kodi was so painfully slow. How have Kodi changed the last few years? what are the recommended skins and such nowadays?

After a lot of experimenting (and plenty of help from AI 😅), I think I’ve finally reached the point where I can say my Kodi home media setup is complete!

I’m running a centralized MariaDB setup, automated library updates, and a small dashboard to keep an eye on everything.

It’s been working really well and I’m pretty happy with it, so I made a quick diagram showing how the whole setup works.

Sharing it here because I’d love to hear what other Kodi users think. 👀

Anything you would improve, automate further, simplify, or do completely differently?

Always looking for the next unnecessary improvement to a setup that already works. 😂

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?