All Activity

Is there any more information needed for this report? This is the main issue keeping me from using the universal version instead of the for AndroidTV version. I just experienced some media playback issues using the old for AndriodTV version. To get around it for a certain video, I had to assign an external player. I'm not sure why the video is having issues with playback in Emby for AndroidTV. It want's to convert the video for some reason even though direct playback of the video does work in other players like NovaPlayer and Kodi. That's a diiferent issue, but would be moot if the OP issues was resolved.

Yea right - in the grid it's possible, but it's more like an icon in a table cell, not like a free-standing single image - that's why I hadn't even thought about it. If that satisfies your needs, I'm glad that you found it.

escobarlarios

Hi. What app version?

Hi. Providing a better logo is going to be the best option. Does it look any different in the other apps?

Hi. Unfortunately, that is an option that is bespoke only to that app. It was implemented quite a while ago and none of the other apps have it. Given enough support, we may consider it across the board. Add your support here:

Hi. Neither. It is something that is possible for the future. Also, there's already an open request for this or something functionally equivalent. Please join in and contribute to the existing discussion at:

Hi @LukeSorry I couldn't tell by your statement. Is there ALREADY a way to do this in Emby? Or this this something that is being worked on?

@EriksUsername Turns out, I using "stay awake". I using for backup pc. apt install sdparm sdparm --clear=STANDBY /dev/sdX -S I created bash script: /usr/local/bin/stay-awake-hdds.sh #!/bin/bash for i in {b..z} ; do echo $i; sdparm --clear=STANDBY /dev/sd$i -S; done Then I added to crontab (crontab -e): @reboot /usr/local/bin/stay-awake-hdds.sh Hope this will help. Sorry about two posts, was unable to edit again.

Hi, I would like for every user to get their own section on the homescreen that recommends series/movies based on their watch history. Right now i get it to work but i have to do it manually for each user. Is this how it works, or is there a more efficient way to do this? Thanks!

Ha ok je savais pas je vais voir j'ais un compte chez TVTB je n'ais jamais vu cette fonction merci

This has been fixed in latest update. Thanks

Il suffit de créer un compte sur les sites en question et de compléter les infos manquantes sur les pages des séries ou épisodes dans la langue souhaitée (tu peux en général trouver les infos sur le site de l'éditeur ou du studio de la série en question). Tu peux aussi si tu as les 2 sources de configurées pour une bibliothèque d'utiliser le bouton avec les 3 petits points sur la page de la série et choisir Identifier et tu peux aller choisir la version qui te parait la meilleure au niveau métadata. Dernière solution, tu peux éditer toi-même les métadata dans Emby et les compléter pour celles qui sont manquantes ou pas dans la bonne langue (Pour Texas Walker Ranger je te confirme qu'effectivement au delà de la saison 3 les descriptifs sont dispos qu'en anglais actuellement !). Un truc qui peut être bien à faire c'est de configurer le rafraichissement périodique des métadatas (perso j'ai mis 90 jours) et comme ça à l'issue de ce délai périodiquement,Emby va revérifier si y'a eu des mises à jours des métadata et va les faire à ce moment là

Some channel logos only have dark logos making them invisible in the Roku tv guide. What recommendations are to improve the contrast between the background theme and logo?

Bonjour soumettre les donnes manquante je ne sais pas du tout comme faire merci quand même

Hola, supongo que lo que se mostraba es el error. Saludos

I have tried rebooting the complete system, server, tuners, tv, rokus many times. Nothing changes.

Bonjour Oui cela n'est pas un problème d'Emby mais des bases de données utilisées. En général TMDB est bien au dessus en terme de qualité et de quantité de contenus que tvdb Perso c'est tmdb d'abord et tvdb ensuite et ça va bien pour la plupart. Les 2 DB sont participatives donc tu peux aussi soumettre les données manquantes

The plug-in has been abandoned for years.

Thank you very much The Emby Windows app was launched at 08:49 am on 22nd June. The crash dmp was at 08:51 But the Emby Windows app process appears to have continued to run until it was closed at 08:56 Do you remember exactly what you did / what happened / what was showing between 08:49 and 08:56 ? (I have referred the dump and associated log to the Emby development team)

Hi, I was evaluating live tv sources. I have always used a m3u url for years.. I was trying out a new service and had to use xtream api... Everything was working fine. The test didnt improve the performance issue. I believe the buffering and other hicups are from my inet service. Moving to fiber soon. But when I added the xtream live tv device, I deleted the m3u device. (i have been able to delete and add back with no issues) but now when I try to add back my m3u, I get an error. "There was an error saving the TV provider." I am confused by this. can anyone help me resolve it? I want to just add back my existing m3u url live tv device. I have always used Emby in a windows environment, but now running via Unraid through a vpn tunnel. Everything is started and testing fine. I just cant add the m3u url. This url does work in VLC on my windows computer. I have the log file, but need to know what to remove so not to reveal personal info.

So i got the 2.1.8.1 dev version and tried the Native live mode. I noticed a difference between sdr and hdr. When playing sdr content: playback will always start from the beginning no matter the time. When playing hdr content: playback will start at the correct time the TV guide suggests. I believe that's because of the delay when the TV is switching to hdr. That would mean having a delay option for Native live would help in this case. I'd like to create a channel only with shows and/or movies I have specified in the include fields.

Bonjour j'ais une serie walker texas il y a 9 saisons mon soucis est que les 4 premières saison sont bien traduite en Français dans les métadonnées et le reste est resté en langue origine d'autres on le meme soucis mais j'ais pris cette exemple je ne parvient pas à trouver la solution la seule solution trouvée est de supprimer la bibliothèque et de la recréer et mettre en avant la recherche par TMDB au lieu de Thetvdbd je n'ais pas de soucis sur un log concurrent très connu merci

My minimal understanding is start to butt up against achieving a nice UI experience and i was hoping people could part the clouds of understanding a little and establish some relevant ground truths (for me to direct my efforts and learning).if you would be kind enough to spare some time. This is an AIs understanding of the Emby genericedit framework (im probably not using the right term..maybe genericUI?PluginUI?). Would people support the key bottom line points / disagree with any of it? The main issue i want to get an understanding of is; how much 'liveness' is realistic to try and achieve in the UI whilst maintaining a reasonable user experience. Are the suggested patterns good ones to adopt? 'Issues' i am hitting Being returned to the top of the page when clicking on checkbox in a dxgrid. Rows in genericitemlist members bouncing in and out of view whilst a task which is working on them and moving them to 'completed' is processing them. Different UI states when nothing is happening and i navigate away and backagain (Understanding the lifetime of data in the framework perhaps) I am talking about plugins with what i assume are trivially small 'UI data sets'. I want the UI to be responsive, live and survive page navigations back to main emby and back to plugin but i wonder if my expectations are unrealistic and where I should focus efforts. 1. Does Emby require “full DOM model refreshes”? In practice: yes — functionally it behaves that way. But not in the literal browser-DOM sense. What actually happens is: Your EditableOptionsBase model is re-serialized server-side The client receives a full updated view model The UI is re-rendered from that model snapshot So when people say: “Emby sends the whole DOM model” What they really mean is: “Emby re-renders the entire page from a full server-provided model each time it updates” There is no stable virtual DOM diffing system like React/Vue. 2. Are incremental UI updates supported? Short answer: not really There are only two “update modes”: A. Full model refresh (your main tool) Triggered by: RaiseUIViewInfoChanged() property updates on the view model command execution returning updated state This causes: ✔ full UI rebind ✔ full list regeneration ✔ full status refresh This is what you are using now. B. Limited partial updates (very constrained) Some Emby UI components can update more surgically: progress bars (PercentComplete) status fields some list item properties (depending on client implementation) BUT: This is inconsistent across: Emby Web UI versions mobile apps different GenericEdit controls So it is not safe to build architecture assumptions on it. 3. The key architectural truth (important for your design) Your mental model should be: “I am not patching UI. I am re-declaring UI state.” NOT: “I am updating a live UI tree.” This is the single most important shift. 4. Why your current architecture actually works (and is close to optimal) Your system already does something Emby-friendly: You are doing snapshot rendering: RebuildMovieList() full replacement: ui.MovieList = newList; This aligns perfectly with Emby’s expectations. 5. Why you are seeing “bouncing / redraw pain” The real issue is not Emby. It is this: You are mixing 3 state streams Emby library state (Coming Soon rows) Tracker state (live progress) User transient state (toggledOn) And you rebuild everything on: timer tick task events commands So you get: “full recompute + full rebind every second” That feels like instability, but it is actually correct behaviour for this framework. 6. Can you avoid full redraws? Strict answer: not reliably You can reduce frequency, but you cannot safely eliminate it. What you can do: Option A (recommended): “diff-lite model discipline” Instead of trying to avoid redraws, you: Only allow redraw when signature changes You already do this: if (signature != lastPolledSignature) This is the correct strategy in Emby land. ✔ This is effectively your “manual diff system” Option B: split “fast UI” vs “slow UI” This is where you can gain performance and stability: Fast updates (polling only): progress % status text active rows only Slow updates (full rebuild): Coming Soon list analysis results toggles history rebuild This reduces UI churn massively. Option freeze structural list during runs Big improvement pattern: Do NOT rebuild Coming Soon rows every tick Instead: build rows only on: load refresh retry only update tracker overlay on timer This alone removes ~80% of UI redraw noise. 7. What Emby does NOT give you To be very explicit: no virtual DOM no diff-based rendering guarantees no stable component identity model no incremental list patch API no client-side state retention across full refreshes So anything like: “update only row 3” “patch one field in list” “incrementally mutate UI tree” …is unreliable or not supported consistently. 8. What Emby does give you (and what you should lean into) ✔ deterministic full-state rendering ✔ server is source of truth ✔ UI = pure function of state (conceptually) ✔ timer-driven refresh is acceptable pattern ✔ stateless UI rebuild is expected pattern 9. The mental model you should adopt This is the key shift: Treat every UI render as: “If I lost all UI state right now, could I reconstruct it from memory?” If yes → your design is correct If no → you’re depending on unsupported incremental behaviour 10. Bottom line ✔ Emby does NOT support true incremental UI updates in a reliable way ✔ Full model refresh is the intended design pattern ✔ Your current approach (RebuildMovieList + RaiseUIViewInfoChanged) is correct ⚠ The risk is not redraws — it’s over-redrawing too frequently ✔ You should optimise by reducing rebuild frequency, not trying to avoid rebuilds I have no training in development. i am learning by osmosis, the reference docs where they can help, and the forum. I am only a beginner understanding c# (but ai can help with that), i think UI is a few steps beyond that, so be gentle . Thanks in anticipation.

Yeah thanks, that's why I was wondering if there was any known settings I should make to improve performance