Leaderboard

Disclaimer: If you decide using the delete option, IT'S YOUR RISK! If you are using fileops on Kodi, LOOK and VERIFY what Kodi is about to delete or modify. The affected folder is clearly shown in a Kodi popup message. Release Notes: removed Kodi 19 support: ONLY FOR KODI 20 for Kodi 21 use public testing versions 10.X STABLE VERSION 9.4.21: Download Link: https://kodi.emby.tv/Public testing/plugin.video.emby-next-gen-9.4.21.zip fix multiversion episode delete issue fix strm file issue fix websocket close issue fix 'FreeTypeFont' object has no attribute 'getsize' -> python pillow api change fix playertracker issue fix library removal issue for edge case fix player crash fix Studio sync issue fix BoxSet sync issue backport MusicAlbum bugfix from 10.X fix extracted bluray and dvd playback fix sync issue for invalid episodes metadata fix nextepisodes synced node fix SesaonId detection by PresentationUniqueKey -> compatibility with 4.9.X Emby server exclude photos fix virtual tv fix books and games library issue fix stream sync issue fix invalid year values sync issue fix database option set fix favorites remove fix content date fix musicgenre removal fix dynamic node fix minor sync issue fix dynamic nodes folder selection, when folder has multiple content types included (e.g. pictures) fix delete after played option fix player crash when content was playerd from an external source (not Emby) fix nodes fix initial xmls configuration remove overlay from photos add bookmark workarounds for episode widgets fix cinemamode via widget playback fix native mode widget playback fix multiversion fix player issues fix upgrade issue from 8.X version fix boxset update issue fix favourites update fix artwork cache fix player issues fix minor player issue unified player code fix sources.xml fix artwork cache/remove fix player timing issues (stability) fix Boxsets synced via Emby server stable version fix livetv issues fix database vacuum fix MusicGenre updates fix playlists keep advancedsettings.xml on factory reset add options to adjust the context menu fix watched status fix context menu options remove (library) label extension from tags fix server busy notification when server is shutdown or restarting fix favorites issue added additional database consitency checks fix multipart content fix artwork caching fix delete downloaded content change downloaded content label from downloaded to download fix database I/O issue fix queue issue/hibernate issue support subscontent donwload (via season, tvshow) add support for season favorites fix favourites "remove" action via Kodi's default favourite view add translations fix numeric check (e.g. aspect ratio value was not detected) fix dynamic node subcontent issue (e.g. movies -> genre) make paging factors adjustable by content fix dynamic nodes content reports to Emby server fix native mode Windows path issue fix queue timing issue new tvtunes integration remove emby server -> clean content settings and nodes fix several minor issues unify code lower MusicAlbum paging value (Emby server > 4.8.0.58 (beta) has performacne issues with subcontent queries) fix Kodi nightly database issue fix file delete issue fix virtual content issue e.g. for upcoming episodes fix database reset for Windows Fix search cache issue Fix minor musicvideo issue Fix minor sync issue Block .tbn file queries in addon mode, if not a picture query Block invalid queries in addon mode Add Download option Fix player issues Fix remote mode issues Add additional caching for mixed content in dynamic mode Add search option in dynamic nodes Fix dynamic nodes issue add additional image fallbacks for landscape fix minor sync issue for BoxSet updates fix smb pathes (native mode) autoupdate Kodi settings for addon mode (myvideos.extractflags=disabled, myvideos.extractthumb=disabled, myvideos.usetags=disabled, musicfiles.findremotethumbs=disabled, musicfiles.usetags=disabled, myvideos.extractchapterthumbs=enabled (if path subsitution is enabled, otherwise myvideos.extractchapterthumbs=false) fix picture load issue fix realtime (library) update issue under for edge case fix favorites content playback use helper folder for dynacmic nodes including mixed content fix sync issue for mixed content libraries fix dynamic node for audio content fix music sync issue option to sync livetv channels on Kodi start fix delete option via context menu fix sort order for dynamic nodes fix sync issue for Videos fix kodi source -> http://kodi.emby.tv fix Kodi shutdown when Emby server connection was down fix dynamic node sort options code unification fix homevideo/photos dynamic node fix init sync crash option to disable favorites sync clean code fix crash on Kodi exit fix remote playback issues improve plugin startup fix BoxSet updates on Kodi startup add support for realtime updates of boxsets fix/support sync issue for virtual content like BoxSets, MusicAlbum, MusicArtist, Tags, Persons, Genres, MusicGenres etc. change Kodi events to a more reliable threading/queueing system fix issue with different actors but similar names support playlist sync added sync tag nodes for collections fix sync node issues support favorites for all sorts of Emby content support MusicGenres for Musicvideos less ram usage while sync in progress clean and restructure (code) modules Subcontent unification changed (Genre, MusicGenre, Tags, MusicArtist, Studios, MusicAlbum) Boxsets (Collections) to Tags as Option Fix Artwork issue for MusicAlbum xml python api plugin replaced by code. Plugin is a source of issues and not very stable. Some livetv sync fixes fix/improve cache for dynamic content updates fix timeouts (CCurlFile::Stat) new mixed in-progress node Patching requests python lib to disable Nagle add dynamic node links as xml fix release date information add continue-watching node change default sort option for Episodes fix folder playback

I know we can filter our favorites but I'd like to request a feature to group our favorites into different, custom collections (i.e.: Documentaries, Wrestling - WWE, Wrestling - AEW, Kiddo's Movies, etc.). It would make the experience of finding something to watch a lot more convenient!

Thanks, i did rtfm those last 30 minutes... i renamed all files using a quick python script and created the correct library, thanks for help.

Actually it's not really "enhanced" in significant ways. It uses AC-4 audio which ties it to Dolby, it uses HEVC, but that's not something for which ATSC3 is needed for, and it uses a different container format, which makes it incompatible to everything else. It brings in back-channels via internet connection which allows them to display targeted ads and track users for what they are watching, when, how and how long. It's primarily a wet dream of the industry in order to fence their market and push their patents into it. Digital TV has always been driven by DVB and probably they didn't want to be the little brother or passenger anymore, just cooking their own little soup on top of it. Probably it's also an attempt to work around FCC regulations demanding a certain amount of free and non-DRM-protected content in broadcast TV. Technically, there wouldn't have been any need for this (when proceeding in parallel to DVB like usual) Interestingly, LG is no longer including ATSC 3 tuners in their TV models from 2024 onwards. North America, South Korea and Brazil (only testing/consideration), that's pretty much it. For using better video codecs, it doesn't require a new standard. Better radio transmission technologies could have been introduced with a small standard update which would have remained compatible (like DVT-T2 did). Content encryption has always existed for DVB standards. Actually, the first DVB broadcasts were paid services with encrypted content only, which hadn't changed for a while. Encryption exists and is in use for all variants (S/C/T) but there is a reasonable balance between free and encrypted channels. ISDB is a derivate of DVB and used in Japan and Brazil (DVB tuners can be used to receive ISDB with different firmware) Then there's DMB in China, about which I know nothing. All the rest of the world uses DVB (https://en.wikipedia.org/wiki/ATSC_standards#/media/File:Digital_terrestrial_television_standards.svg) It should be noted that these usually cannot compete with broadcast television in quality. A private beta is already behind us. Next-up is a larger-scale beta, involving a broader audience, so it won't be just a few hand-picked people like the previous one. Yet, I can't say when and how. Only thing I can say is that it hasn't been filed dead, and it's surely good to keep asking, even though it's probably the most requested major feature already.

I've spent months evolving my Emby setup to a state where it is able to reliably play live TV streams from an IPTV provider. Sharing my findings here to help the community and gather feedback in case I can make things even better in the future. Up until I added hls-proxy to the mix I was attempting to use Threadfin as a buffer. It helped stabilize things slightly but issues were still present. Emby clients would randomly seem to drop their channel streams and fall back to the previous screen in the app, it was more prevalent with remote clients than with local, but all clients (web/android/roku) experienced the issues. Clients have no playback issues with local, or remote episode/movie media files. The IPTV service provider I use allows 5 concurrent connections to their service. However, I have noticed that I cannot rely on Emby to enforce this limit. If I set "simultaneous stream limit" to 5 in Emby it will eventually end up in a state where no channels can be played even though there are no active streams (verified by looking at the status page of hls-proxy). I don't know why this happens and I can't seem to correlate it to anything specific. After adding hls-proxy to my setup, I will sometimes see Emby make a secondary connection to the same stream even though a second user has not tuned to that channel, but I'm not sure if that has anything to do with the problem. The workaround I've put in place for this is to set the "maxStreamsPerClientDefault" in hls-proxy to 5, and set "simultaneous stream limit" on the TV source in Emby to 0. I've also configured a cron job to restart my Emby server early each morning to clear out any stuck tuners that might exist. When I set up hls-proxy I noticed a couple things. My provider publishes 5 .ts files in the m3u playlist for a channel. If Emby is able to see a list of 5 .ts files, it will read them but start playback in the client at what I believe is the 3rd or 4th file in the list. This means that Emby is only leaving a 1 or 2 file buffer between the playback position in the client and the stream coming from the provider. If the provider experiences a delay in publishing the latest .ts files for the stream to their servers/CDN, the client will overrun the buffer and this may be why the client stops playback at seemingly random times. I was able to configure hls-proxy to show Emby only 2 of the 5 files at the start of playback which seems to start the client playback at file 1 when starting a stream. When it requests the playlist a 2nd time from hls-proxy the first 2, and next 3 pieces are in the playlist for Emby to fetch. At this point hls-proxy already has another 2-3 .ts files in the buffer that haven't been advertised to Emby yet, so not only does the client have a bit of a buffer to work with inside the Emby server, the Emby server has a 2-3 segment buffer in hls-proxy that it can draw from in the event that hls-proxy needs to retry fetching the stream due to a publishing delay or a temporary error on the server side. The only time a stream drops now if if hls-proxy encounters a provider side error that it can't overcome in a reasonable amount of time. Since Emby is still communicating with hls-proxy when this happens, the stream will freeze, and can recover if hls-proxy is able to retry the connection and fetch files before the retry limits or timeouts are consumed. Some notes on how I'm using these apps. I've tested hls-proxy both in front of, and behind Threadfin with the same result on Linux and Windows. Threadfin - used currently with the buffer disabled so the m3u URLs from the provider are passed to the client. I use it strictly to groom/curate the incoming M3U/XMLTV links from the provider. hls-proxy - Used as a debugging platform and a buffer in-between Emby and the provider. This allows me to get a peek at what is happening between the provider and the Emby server. If there are any errors from the provider side I can see it in the logs. You can view streams directly in their web interface. It also has options available to aggregate provider accounts based on the syntax of the URLs they use to serve content. If you have many single line accounts with the same provider hls-proxy can aggregate them into a pooled resource.

Also, It would be cool if we have various m3u lists and have the option to choose/assign each m3u list for each user.. Example. In user settings we can choose which library to give them for VOD so this shouldnt be hard enough to do it for live tv too no? USER 1 - Playlist 1 - Playlist 2 - Playlist 3 USER 2 - Playlist 3 USER 3 - Playlist 1 - Playlist 3 Etc etc.... *** Delete this message from another topic I opened because I posted it by accident there

Is there plans on the roadmap for OpenID. I have searched but not found any indication this is in development. With many admins taking up SSO through Authelia or Authentik to enhance security it would be great for Emby to support it. One of the easier open standards is OpenID which the aforementioned support. Users could continue to use LDAP if they wish while others can use the arguably better SSO experience.

as per title said, is it possible to move this section into the home screen, so everyone can see it? like in some category / section, Now Playing for example and it just listing the episode and users info, as minimum this is not history ones (i've seen the history plugins in the forums) but more to real time ones, since it's help user engagement and all user can see it (without admin access involved, and no need to go to dashboard)

I think its something like - div.virtualScrollItem.epgRow {height: 60px;} or similar but using em ?

One tv is a 2019 and other is a 2020 for me

I reported this problem in another thread with 1.6.6 awhile back. TV is a 2018. Both releases came out back-to-back which is why AnyXH may not have seen it in the previous version.

I have no issues with it running on beta. There is nothing that should cause an error. An example of how to use custom links is in the post 2 above this one.

Hey @Lukeso looks like I might have something to do with v 1.6.7 I had a TV that had an earlier version and back drop was working as soon as I updated it to 1.6.7 backdrop stopped working. Hmm

I actually don't really care about time. Since there aren't many options, I'll continue to use EMBY for many years to come. Even if I don't wait for this feature to be implemented, I'm happy to see that other users who face the same situation as me can have a better experience.

Yep. Apparently after 4 hours of troubleshooting on my end, it was an IBCAK error. Thank you for noticing that! Wish I reached out earlier. Totally saw checking as what to include and every time I read the settings, must have read what I expected to see instead of what was there. I appreciate you.

Hi. I understand what you are asking for and, theoretically, it would be possible but it seems to me that the audience for this feature would be extremely small and it would be a not insignificant complication. So, we'll keep this request open and monitor ongoing feedback. Thanks.

Hi. I'm afraid sharing and utilizing these streams outside of their interface is expressly against their terms. BTW local TV broadcasts are not "free and legal" for the whole world. Organizations such as the NFL depend on that...

With the requested implementation from the other thread, the topic should be settled. Thanks!

If you want to save yourself time renaming them grab a copy of RenamewMyTVSeries and set it up. https://www.tweaking4all.com/home-theatre/rename-my-tv-series-v2/

Why would you add those as Movie library? It should be TV shows-type library. In addition to above, you should use one of the supported episode naming conventions: https://emby.media/support/articles/TV-Naming.html#episode-naming-conventions

I can do that, but you know -> in-progress episodes and next-up may result in doubles. They needs to be filtered. next-up selects by unwatched, but a an episode can be both. unwatched and in-progress.

This has to be the worst idea I've ever seen!! There is a place for this and that's the admin dashboard.. For heavens sake please forget this or put to the bottom of the pile, never to be seen again! Stupid.. Stupid.. people..

Correct.

Too bad infuse does not support users.

I done quite a bit of troubleshooting, and while I'm still not sure _what_ caused the problem, I can relay what troubleshooting I done and what ended up fixing it. Some notes before I get started: The android TV device and my pc use wired connections, my wifi is on v6 and is rather fast. Additionally, there are no firewalls or similar between my client devices and the emby server during this testing 1: The first thing I tried was changing from the stable branch to the beta branch, this yielded the same behavior 2: I then tried it on a variety of clients (PC, Android TV, iPad, Phones, etc). The above testing yielded the same behavior, after about 10 seconds or so the live tv would just pause, additionally, I noticed that after I stopped, emby did not disconnect from the HD Homerun device (this is when I posted here for help) I then had a thought that maybe it was something to do with the software encoder being used by emby (as that was the only error that I saw), and I moved emby server to my desktop and tried it from there; The problem vanished. Euraka! I thought, I put a GPU in my server and used that for transcoding, the behavior returned. Then I thought, um ok?.. After some thought, I installed the official docker image on another docker host, still using software encoding, flawless playback. After this I surmised, it must be _something_ between truenas and emby that was interacting in a bad way, after this I moved emby to a another host it could have to itself, and I've not had any problems since I guess, the moral to this story is, if your having emby playback issues with watching live tv from a hdhomerun AND your server is running on truenas (scale). Try moving your emby server to another host, that may be the problem. I can provide more logs and whatever, if someone is interested, I still have the docker image on my truenas server, its just turned off.

I think we should clear-up the difference between ‘Nextgen TV’ and ‘TVnext’. Nextgen TV (AKA ATSC 3.0): Is a much enhanced OTA broadcasting format currently being tested in the USA and a few other counties. It (potentially) greatly increases the A/V & signal quality over the current ATSC 1.0 that is in use. But unfortunately is being made useless by many broadcasters by implementing DRM. This doesn’t apply to most other countries that are using DVB-xxx (or other?) nor people that are using IPTV/M3U sources. Emby has no control over how any of this is done. TVnext: (See: Tvnext Spreadsheet} Promises a feature rich Implementation and speedy channel tuning for emby to play/record Live TV, including all of the above and more (non-DRM at this point). That has been (mostly?) developed by @softworkz. This for me should be the very next emby public beta. (i’d even be willing for a private beta!)

Yes only on Apple TV for me. Not a problem on any other platform I use, including iOS, iPad and web.

You would need to setup a restreamer server with however many users your server can handle without buffering, I read through some of this but it won't happen on emby. This would need to be something on the end user to setup, thinking emby can do all this is crazy seriously just crazy. Google restreaming software it's not cheap unless you can code your own your out of luck thinking emby will do this setup it just will never happen. I also was reading on the emby forums that you can watch one channel and have more than one person watch the same channel and hide it from the provider of your tv lol not true. @Carloyou said this in different posts and it is not true, if I watch the same channel on 3 tv's the provider can see this easily. That statement is very misleading! If people want to watch the same channels above what their tuners can handle they will need to do research and learn to restream the entire m3u and if your not able to do it yourself by coding then you better have deep pockets for a restreamer. This is why m3u providers limit how many users can watch at once because if your using emby and 20 people are able to watch at once there loosing money, simple. If you email an m3u provider asking for 20 users on one m3u they will say no, they will give you at most one for 5. In vlc you can add 10 channels all the same if one fails because someones on it then it loads the next one, emby can't do that unless they tear down vlc code which will not happen. If I were to guess there are maybe 5 or even less people coding for emby good luck with this happening! I'm all for the under dog it's why I pay for emby but in order for them to eat they stick withing what they can handle as a team, if you want to become a cable tv provider then do it on your own and restream m3u's with high end gpu's This thread should of been closed long ago!

Dear Softworkz, I tested the Remote Control (= Original Microsoft RC with USB-receiver) with both (1) Emby Theater WMC gui and (2) Emby webgui and found identical findings as you: and indeed except button 0-9 and up/down: thus I confirm your findings! In the meantime, the WAFAF* seems to hold up Emby Theater WMC gui!: we are using it since approx. 3 weeks in full production: our family TV in our living room on a NUC (i7/16G/250G SSD/Win11): it is almost OK....besides some RC matters, going-to-sleep/wake-up and some minor matters. *WAFAF = Wife And Family Acceptance Factor. Thanks & best regards, Peter

@JunglejimYou can read more about it here

I use FRP to do NAT traversal. fatedier/frp: A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet. (github.com)

Great, thanks. We'll update the m3u plugin to account for that.

OK we're looking into it. Thanks.

@iiiJoe also ive noticed my timers.json which is where all the recordings are stored. need a lot of cleanup. mostly from me changing the recording folder over time, delete videos outside of emby, etc. but if everything stays the same and do everything thru emby, it does cleanup the list of recordings. so im working on a app to help cleanup. wish me luck !

Thanks. So just for anyone looking at this, I made an interesting discovery today. While the sorting issue still exists, at least the date is shown on the tile when using Emby Theater on my PC, or the Android Emby app on my Chromebook, as opposed to using a web browser. I sorta had a 'slap the head and say DUH!' moment today. Again, while the sort order is still purely alphabetical, at least I can easily see the date. And, files that had to be transcoded to play via a browser Direct Play using the apps, so double bonus! I never realized how the Emby Theater app fit into the architecture....

Hi, it's a neat idea. It's just a question of who maintains it, keeps it up to date, troubleshoots it, etc.

Hi. I think you likely want to use the Live TV M3U tuner feature rather than the IPTV plug-in. How to add and configure an M3U Tuner

The following receivers are supported: Microsoft SB Adaptec BB Dell BB Dell SF ECS BB F21 snowflake emulator FIC BB Formosa21 BB Formosa21 SF Gateway BB Gyration BB Gyration SF Hauppauge BB LG BB Microsoft BB Microsoft SF Mitac SF Mitsumi BB Mitsumi SF NorthStar Systems Corp. Emulator Northstar Systems Corp. Emulator Philips BB Philips SF Ricavision BB Ricavision SF SMK BB SMK RXX6000-0101F SMK RXX6000-0201F SMK SF Samsung BB Shuttle BB Shuttle SF Tatung BB Topseed BB Topseed SF Trojan BB Trojan SF V1 Emulator Wistron BB eMuzed BB But please note that these are low-level manufacturers, it often has nothing to do with what you can read on the remote control or the USB receiver - those are the OEM manufacturers.

@AmateurgottI don't think you mean in Kodi right? Would you like to share your CSS? Is it based on Embuary? In my opinion, this is the very best skin, which also gives us Emby users the Emby insert in Kodi. It's a pity that there is no one in the community to develop it further. Best regards seger

@bruorMany thanks for your helpful information. I am currently testing StreamMaster (SenexCrenshaw/StreamMaster (github.com)) as an alternative to threadfin/xteve and hls-proxy. Very successful so far. Similar to hls-proxy, you can also see the current status of the connections. Docker containers are also available. Possibly also an alternative

HI, we don't have an answer to this yet but we are certainly monitoring the industry to see how things shake out in regards to this.

If anyone here is looking for something more supported than xteve (as it hasn't received any updates for a while now), try out Threadfin, essentially the same thing, just rebranded and actively developed: https://github.com/Threadfin/Threadfin

Is this skin still maintained? Is any Dev working on it?

Yes. The only inbound port open to my home network is tcp/22 (pfsense firewall). My home server endpoint is not technically fixed (though it does tend to stay at the same address for months to years before changing) so I check it every 10 minutes and update accordingly using the godaddy API only when it changes. I posted a how-to for that piece on Instructables a few years ago, https://www.instructables.com/Quick-and-Dirty-Dynamic-DNS-Using-GoDaddy/. My concern is less of traffic hijacking or snooping and more of exploits targeted at the emby web server itself. Admittedly, I don't know if emby (linux) leverages an existing http/s server or if the guys rolled their own. Either way, however, I'm highly comfortable exposing openssh to the world if it is secured with ssh keys (absolutely no passwords!!) because it is tested every single day by millions of servers all over the world. The fact that my traffic is encrypted is just a bonus. I'll put together a quick guide and post. I even made an emby listener that will respond to emby request broadcasts (iPhone app, et al.) to save the user the trouble of having to know/type the ip address of the local endpoint. Some of this is still in development, but the concept works and has been rock solid for roku. Also included a reverse tunnel so I can maintain the satellite when needed without having to config the remote router to allow inbound ssh -- makes for super secure maintenance. To bring this back around to the original post, MFA is really targeted at securing the data from weak passwords, not protecting against exploits. IMHO, exploits are a much MUCH bigger threat than someone guessing a password and using an otherwise legitimate channel to grab my content.

I think this is a great idea and could elevate Emby into the spotlight if you combine it with the ability to click a button in the widget to start watching the same media from the same point - It is suddenly a very intuitive co-watching experience.