Leaderboard

For those anxious to try this out, here is a native M1 build of latest beta server (4.8.0.13): https://github.com/MediaBrowser/Emby.Releases/releases/download/4.8.0.13/embyserver-osx-arm64-4.8.0.13.zip Please note that unlike the x64 build, there's no tray icon yet. I still need to build that for the M1 architecture, but everything else is there and it's enough for you to try it out. We'll be issuing a 4.7.9 maintenance stable release and we'll have that for M1 assuming this goes well.

Emby for Android TV 2.0.83 is now live in the Google Play Store. Thank you all for being patient with this.

nope - if it’s not ticked then nothing will be written to NFO file Gotcha

Many people appear to be missing the entire point of 2FA for emby, believing it's magically going to stop the bad guys - the simple answer is it's not, not even close. If you are naive enough to use the same password for multiple systems, then 2FA is going to get you some more protection when (not if) your password is available from a data breech. But the real risk to emby is not it's data or media, it's simply an 'entry point' into your home network that is now available and for the bad guys to wait for an 'emby toolset' vulnerability. It could be the emby web server, ffmpeg, it's database etc - if one of those gets compromised and remote code is executable from the internet - then bang, the attacker has access to whatever network your emby server is on. For those with experience on cyber security/networks - yes there are all sorts of extra protections available - Reverse Proxies, VPN's, Isolated DMZ networks, IPS etc - these would all sit 'in front' of the emby web service - which should sit 'inside' a reasonable protected perimeter 'defence'. So going back to the question - is 2FA going to add protection - my personal belief is it's not a priority - especially when HTTPS is not enforced, password strength is not enforced, brute force lockouts are not enforced etc. These are things which could be done with relative ease - and provide better basic security out the box. Once the basics are done - THEN maybe think about 2FA for the Admin account .. Just my 2p.

Install went smooth and it went over the old Emby and everything seems much faster. I did not do a lot of streaming to my AppleTV 4k devices or other devices of course as its has only been overnight.

You could try using DB Browser for SQLite to access the database and check for the show and episodes that weren't marked as WATCHED. I'm no expert, but as long as you don't change anything, you should be OK. Take a copy of the database (library.db) first (shut down Emby beforehand) in case you change something accidently, then you can always copy it back.

So i've added options now. You can save to JSON or Save to NFO you can see below that the info is written to the NFO file also now.

7.9.3 addressed the music art. Thanks quickmic!

Are we sure inotify will even work on a mounted drive. Linux Filesystem Events with inotify | Linux Journal The inotify interface does have limitations—it can't monitor remote, network-mounted filesystems (that is, NFS); it does not report the userid involved in the event; it does not work with /proc or other pseudo-filesystems; and mmap() operations do not trigger it, among other concerns.

The Problem I have a reasonably aggressive automation system that can process new episodes relatively quickly. This means they can end up in Emby sometimes within 10 minuets or so of them airing. What this means is you are usually stuck with the metadata that was available at the initial import time, sometimes missing titles, ratings, overviews. Yes there is an refresh every 30 days option in the library but that was not fast enough for me and I did not want to refresh the 10K plus episodes I have in my lib, just the recently aired ones. The Solution Refresh the newly aired episodes, say in the last 7 days, nightly. That is what this plugin aims to do. Source here: https://github.com/faush01/EpMetaRefresh The plugin is now in the Emby Server Plugin Catalogue under the Metadata area.

Welcome to Top Picks Top Picks will create a custom movie library with ranked items to share with your user base. Enabling settings in the top pick configuration will allow you to create a library based on your user engagement, and also customize what's being shown in the library. Note: Larger movie libraries will have the best chance at generating user engagement top pick items. Smaller libraries may only generate a couple top picks automatically. Critic rating, and community rating do play a part in choosing top pick items, along with User Likes/Favorited Items, and also Watched States. Creating, and editing the Top Picks List: After enabling, and running the scheduled task for user engagement (which will populate an initial list, but is also completely optional), you can also customize the library by adding movies of your choosing, and add-to/edit the top picks list to a maximum number of 9 items. It is important to note that users of the Top Picks library should not hide watched content from their home screen. This will ensure that all the content added to Top Picks is shown in the home screen layout. Pinning Items to the list: These items remain during the engagement rotation. This means that only auto generated items will be replaced weekly. Note: List item rotation will only happen when items are available in the library which meet the engagement criteria. This may lead to some manual up keep of the list. (In the image above, only the 2nd, and 9th item are allow to change, because they are not pinned to the list. However, the item changes will be based on the engagement results, and may not change based on the current state of the library and user engagement stats.) The more your users engage with the library, the more dynamic top picks will create lists. Favor custom thumb images over primary images: Favor custom primary images: Mobile: Android Enhanced Home Screen Layout Entering the Top Picks library you should choose to "Sort by Date Added" to have the images order themselves. There is a week long trial to test it out, after you install it from the catalog. If there are any questions please post them here in this thread. Please be kind, a lot of time, and work went into this. I'm open to further discussions regarding things that might make Top Picks better in the future as well. - chef Version 1.0.0.20 theme media is now added if it exists for a library item. Version 1.0.0.19 Current NFO files that exist in the library are now successfully used and properly altered for top pick items. This stops Emby from having to try and identify items which are already properly identified in the library. The ability to target a specific library for top pick creation. Version 1.0.0.18 Library items now have the option to show the top pick tag or not. Top picks drawing classes now attempt to draw custom thumb/primary images in memory without saving assets until complete. Version 1.0.0.17 Library is created with servers language for metadata retrieval. Top Picks will now search providers for missing resources to draw custom images for the library

Having just lost all of my previous Introskip data from the old Plugin due to a corrupt db, needing me to create a new TV library (subsequently needing hours/days worth of re-detection using the Core Introskip) - would it be possible to include the Introskip 'hidden' chapter markers in the standard metadata/nfo emby processes ? ie 1. Save the Introskip MarkerType=IntroStart,EndEnd and CreditStart in the episode NFO file. 2. On a episode/show/library import - just read the NFO as you do now, and if the data is present, then use that in the Chapter Table instead of re-detecting it. 3. Ideally allow us to see/edit that data in the standard metadata editor for that episode, but the main concern is the ability to recreate it without the need for the emby db/chapter table / ItemId dependency. Thanks.

Hello, I'm facing a problem on my Apple TV app since yesterday, I have some (many) movies not starting ... The browsing is ok, everything is fine when I enter the movie screen, but whe I hit the play button, the screen turns black and nothing happens. The counter remains blocked on 0:00 ... I have to add the playing works fine for some movies, but fails for other ones. I tryed to move the file to another location to get rid of a disk problem : I still have the issue when playing from this other location I tryed to play the same failing movie from the web interface : OK I tryed playing it with dome other apps : OK too. I ffprobed the movie : h264. I updated the server to last version (I noticed the problem on v4.7.6.0) : v4.7.8.0. On Apple TV, I see I have v1.6.4 (dated Oct 13, 2022) - a few days ago, maybe the update broke something. I see nothing special in the server logs whith the last version : When starting : a5efc768&StartTimeTicks=0&IsPlayback=true&AutoOpenLiveStream=true&MaxStreamingBitrate=140000000&X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&X-Emby-Client-Version=1.6.4 (1)&reqformat=json 2022-10-15 10:47:17.001 Info Server: http/1.1 GET http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/videos/452012/stream.mkv?DeviceId=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&MediaSourceId=ad1371f7c3a70250e00951a4cac43a4f&Static=true&PlaySessionId=23c57f7daa4447098b600c64b0951f36&SubtitleCodec=subrip. Accept=*/*, Connection=close, Host=192.168.0.133:8096, User-Agent=libmpv, Range=bytes=0-, Icy-MetaData=1 2022-10-15 10:47:18.017 Info Server: http/1.1 GET http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/videos/452012/stream.mkv?DeviceId=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&MediaSourceId=ad1371f7c3a70250e00951a4cac43a4f&Static=true&PlaySessionId=23c57f7daa4447098b600c64b0951f36&SubtitleCodec=subrip. Accept=*/*, Connection=close, Host=192.168.0.133:8096, User-Agent=libmpv, Range=bytes=2137266289-, Icy-MetaData=1 2022-10-15 10:47:18.022 Info Server: http/1.1 Response 206 to <200c><200d><200d>192.168.0.172<200c>. Time: 6ms. http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/videos/452012/stream.mkv?DeviceId=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&MediaSourceId=ad1371f7c3a70250e00951a4cac43a4f&Static=true&PlaySessionId=23c57f7daa4447098b600c64b0951f36&SubtitleCodec=subrip 2022-10-15 10:47:18.027 Info Server: http/1.1 Response 206 to <200c><200d><200d>192.168.0.172<200c>. Time: 1026ms. http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/videos/452012/stream.mkv?DeviceId=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&MediaSourceId=ad1371f7c3a70250e00951a4cac43a4f&Static=true&PlaySessionId=23c57f7daa4447098b600c64b0951f36&SubtitleCodec=subrip 2022-10-15 10:47:18.039 Info Server: http/1.1 GET http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/videos/452012/stream.mkv?DeviceId=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&MediaSourceId=ad1371f7c3a70250e00951a4cac43a4f&Static=true&PlaySessionId=23c57f7daa4447098b600c64b0951f36&SubtitleCodec=subrip. Accept=*/*, Connection=close, Host=192.168.0.133:8096, User-Agent=libmpv, Range=bytes=6781-, Icy-MetaData=1 2022-10-15 10:47:18.124 Info Server: http/1.1 POST http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/Sessions/Playing?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&X-Emby-Client-Version=1.6.4 (1)&reqformat=json. UserAgent: Emby/1 CFNetwork/1391.3 Darwin/22.0.0 2022-10-15 10:47:18.125 Info Server: http/1.1 POST http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&X-Emby-Client-Version=1.6.4 (1)&reqformat=json. UserAgent: Emby/1 CFNetwork/1391.3 Darwin/22.0.0 2022-10-15 10:47:18.133 Info Server: http/1.1 Response 204 to <200c><200d><200d>192.168.0.172<200c>. Time: 8ms. http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/Sessions/Playing/Progress?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&X-Emby-Client-Version=1.6.4 (1)&reqformat=json 2022-10-15 10:47:18.135 Info SessionManager: Playback start reported by app Emby for Apple TV 1.6.4 (1) playing ******. Started at 0 ms 2022-10-15 10:47:18.136 Info Server: http/1.1 Response 204 to <200c><200d><200d>192.168.0.172<200c>. Time: 12ms. http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/Sessions/Playing?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&X-Emby-Client-Version=1.6.4 (1)&reqformat=json 2022-10-15 10:47:18.140 Info PlaybackReporting - EventMonitorEntryPoint: _sessionManager_PlaybackStart : Entered 2022-10-15 10:47:18.140 Info PlaybackReporting - EventMonitorEntryPoint: Adding PlaybackInfo to playback_trackers : A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB-ae1dde9e986942abb6c97c3ba5efc768-452012 2022-10-15 10:47:18.140 Info PlaybackReporting - EventMonitorEntryPoint: Saving PlaybackInfo to DB The movie won't start, so I stop it : 2022-10-15 10:47:25.325 Info Server: http/1.1 Response 206 to <200c><200d><200d>192.168.0.172<200c>. Time: 7285ms. http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/videos/452012/stream.mkv?DeviceId=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&MediaSourceId=ad1371f7c3a70250e00951a4cac43a4f&Static=true&PlaySessionId=23c57f7daa4447098b600c64b0951f36&SubtitleCodec=subrip 2022-10-15 10:47:25.788 Info Server: http/1.1 POST http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/Sessions/Playing/Stopped?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&X-Emby-Client-Version=1.6.4 (1)&reqformat=json. UserAgent: Emby/1 CFNetwork/1391.3 Darwin/22.0.0 2022-10-15 10:47:25.792 Info SessionManager: Playback stopped reported by app Emby for Apple TV 1.6.4 (1) playing ******. Stopped at 0 ms 2022-10-15 10:47:25.794 Info Server: http/1.1 Response 204 to <200c><200d><200d>192.168.0.172<200c>. Time: 6ms. http://<200c><200d><200d>192.168.0.133<200c>:8096/emby/Sessions/Playing/Stopped?X-Emby-Client=Emby for Apple TV&X-Emby-Device-Name=Apple TV&X-Emby-Device-Id=A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB&X-Emby-Client-Version=1.6.4 (1)&reqformat=json 2022-10-15 10:47:25.794 Info PlaybackReporting - EventMonitorEntryPoint: _sessionManager_PlaybackStop : Entered 2022-10-15 10:47:25.794 Info PlaybackReporting - EventMonitorEntryPoint: Saving final duration for Item : A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB-ae1dde9e986942abb6c97c3ba5efc768-452012 2022-10-15 10:47:25.818 Info PlaybackReporting - EventMonitorEntryPoint: Removing Old Key from playback_trackers : A80BD1B6-A21F-487E-BDA6-C5FD97C2C3EB-ae1dde9e986942abb6c97c3ba5efc768-452012 Anybody else facing the same issue on Apple TV ? Best regards ! Patrick

yes, that and updating the ratings for X days after release so when you go to watch it it has a title and usable ratings.

Multi-versioning works just fine with this Plugin if your versions (which can be in multiple folders) are in the same library - we have have done some extensive testing on this As an example - I have SD, HD and UHD folders in a 'Movies' library - and this works fine. What hasn't been tested (as I removed the Multi-grouping plugin a while back when library multi-version worked in the Core) - is multi-version across libraries - and I think this is what is causing the recursion issues - as I've seen it before when using strm files on my own 'recommendations' initial script. You can re-create the issue @chef by just creating a STRM file that links to a different library.

Thank you for a again! very detailed answer. Sure, the responsibility is mine. The API key seems to be a general key, it is probably used to track my series, to show me as a result which series on TV plays an episode. With the plugins it is not so easy to find out who "calls home" and creates logs there. The Emby server also seems to encrypt the files, it converts the paths into HashTags, so that even I can not recognize by the path, which file is behind it. I guess you always have to make a compromise. So thanks for the help!

There are server topics on this as it happened back when collections migrated from /data to /metadata. But you have to hack the Collections options.xml to be able to Delete the library and allow it to rebuild.

Oh... its probably my reverse proxy header configuration... let me check on it after work today for you.

Yeah I understand this. In Resources monitor/Process is mono and "Emby Main Thre" for a while and after that it probably crashes. I will delete it. Thanks for your help!

@mickle026 might have a hint or two as he did exactly that with his Custom Provider plugin.

I think an alert rather than a line of text. I have come to learn over all the plugins I’ve written, that about 3% actually read anything on the config ui. cheers fellas I’ll pop that on now.

Right - ok, thought that might be the case, thus the question mark. Yea I would simply put on the Plugin page that this plugin requires the use of NFO files and leave it at that.

Preach, brother!! That's why I recommend using an ssh tunnel. If the attacker can't even get to the process bound to the tcp port, it's more secure. I also think rauraido's approach is at least significantly more secure than emby outside a docker where all the exploits you mention above are a much bigger concern.

Hm, I've seen users that deliberately don't want NFOs to be written - just as I've seen those that don't know that that option even exists. Not to impose NFO writing on the first group and educate second group - I'd say warning notice should be the way to go.

Install it last night, and it has been working really well!!

Hi, this is a 2011 NAS? I don't think we have a compatible package for something this old, sorry.

I'm sure you can get creative and figure something but it's not something we've tried ourselves.

NFOs are saved with media only, if library option is unticked - no NFOs are created, it's db-only setup in that case.

Yes, I agree. This is exactly why I do not think that 2FA is necessary for me. I'm pretty confident, when my Emby server gets compromised, not much can be done inside docker container bridge network with read only access to media. I'm willing to take that risk, if Docker gets a security hole, I'm F***ed, but still I'm pretty confident that patch arrives before someone's trying to hack my system thru emby-docker combined vulnerability.

I did a test on the latest version 1.4.6. I used the same .ass file and made 3 files with different language sufix. Loading times: undefined: *.ass = 45sec english: *.eng.ass = 5sec croatian: *.hr.ass= 50sec Non english times are huge.... But this is not all: then I tried Croatian subtitles (with č š ć đ ž ...) and renamed the file from *.hr.ass to *.eng.ass and loading time this time was around 5 sec and all the special letters were shown correctly. So a workaround for me is to use *.eng.ass filename regardless of the original language in the file.

Just so it is out there, I have Zero issue with playing MKV in Emby on my Apple TV.

Hello Chef... I watched the video and read the articles on building Emby plugins. While I was doing this I started to feel like I was back at work again I just don't have the time at the moment to do this level of work. My family commitments come first. Don't take this as a criticism. I value your comments. My problem is a lack of time to bridge the learning curve for building and maintaining a plugin. Now, if you could do all of the work to make the plugin, where all I have to do is maintain the javascript when you are finished, then I would be agreeable. Thanks Chef for all of your good ideas.... Vic

Hey @MikePlanet If you ever do make it back to the community forums and read this. I think that in the auto grouping plugin that you created (which is an awesome utility, and very useful) there may be an issue when attempting to combine items in the library with multiple media sources. For example, if an item already has multiple Media Sources attached to it, your plugin seems to want to try and recombine the media sources again... if that makes sense. Perhaps (and this is totally a guess, forgive me if I'm incorrect) it might be possible to add a check on the library items' media source count prior to acting upon it? //Where item is the current BaseItem. var libraryOptions = LibraryManager.GetLibraryOptions(item); //we need to pass in lib options for the item in the GetMediaSources method. var mediaSources = item.GetMediaSources(true, true, libraryOptions); //There are all the media sources attached to this item. if (mediaSources.Count >= 2) return; //does this BaseItem already have multiple sources attached to it? if it does we can ignore it and move on. Thanks so much in advance... I realize you've been @'d several times over the last couple days LOL! Thanks also for the awesome plugin utility. Excellent work sir

Wow. First language I learned and on that same hardware. How in the world does that still exist in 2022...?

i did not use the beta in the first place to avoid situations like this obviously i have to do now though i do not have much time atm, but ill test as soon as possible and let you know

Hi Dave - only just seen this. @Cheesegeezer Great that you are working on a solution, but I'm a little confused why you are exporting to an external JSON file - taking the process outside of emby ? Emby already has the handlers to 'write' this NFO (and save any other 'custom' metadata you may have modified) and subsequently it also reads the NFO during a metadata refresh, restore or library relocation. The NFO's use the standard provider Id's as you know, they are not 'tied' to emby ItemId's. Saving the Intro/Credit data in this file seems a logical place to save it. If you don't use NFO's in your emby config - then you are also relying on the Emby dB to save all your custom metadata anyway - so you probably have an alternate way of backing up this custom metadata (or you are not backing it up at all...) An EDL file is also a reasonable option as previously mentioned - but Emby does not support EDL files - so while this would be great for external players that do - it doesn't benefit Emby at this time. Keeping it all within Emby means that when you refresh metadata on an item - it automatically pulls the Introdata (if available) at that time, using an external source, means I then need to go and find that item and recover it's Introdata (if I remember to do so..) - which then somewhat defeats the purpose of having it available vs being re-detected.

HI, it should be resolved for the next update to the app. Thanks.

"Today will be a day long remembered" Thank you Luke !

Danke schon

I made lemonade out of lemons, I learned how to sideload on my CCWGT ..

I don't know the exact functionalities of Embuary skin. I'm using a different skin. Anyway I assume you can remove the trakt api key, but usually you need a trakt account to sync watched content (a personal api-key). So not sure what Embuary skin actually does with this key. I only used Embuary skin for test cases. If you install custom skins (or other 3rd party Kodi plugins) it's up to you protecting your privacy. I can only speak for next-gen plugin/Emby server. Also if you install additional Emby-server plugins you need to review them carefully what they are actually doing. Kodi companion plugin (on Emby server) is save. It just (locally) keeps track of the deleted content for sync reasons.

I just installed the M1 beta now and will try it out.

I redid my folder structure to eliminate the disc level folders and the video_ts folders, and so far everything is being read correctly. I have another issue which seems like it may be a Roku problem, but I'll make a new post for that one. For the library issue, simplifying the folder structure seems to have been all I needed to do. Thanks again for the help!

Previous builds were trying to probe subtitle streams individually and that has been removed. So that's pretty substantial.

Ok, thanks, then I was told wrong. Ok Found and install now- Thanks for Idea Thank you, that reassures me. There is a registered API key for track.TV in the Emby skin "Embuary". Should I delete it to avoid any risk? Thats now clear, thanks Done.

New version available 7.9.3: Delta changelog: add translations fix item/library remove issue fix playback crash when Emby content is invalid fix dynamic nodes for identical content assinged to multiple Emby libraries add emby options context menu support for dynamic nodes fix music fanart Comment: Full db reset is required to change the music artwork Be carefull using the dynamic nodes context menu delete option. Probably take a content backup first, due to limited testing.

For a https conection, redirect port 443 to 8920 with the code iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 8920 and dont forget open ports 8096 and 8920 in firewall ufw allow 8096 ufw allow 8920 ufw disable ufw enable check for firewall info with ufw status

You seem to be right. I swapped stream locations and it still plays fine on Roku, so now I’m not sure what to think. I’ll just use Tdarr to automatically put the streams in a nicer order which seems to fix the problem.

Everyone on cf should plan for a contingency in case the worst happens. Have a roll back solution so you can keep your remote users operational. If like me you ported to cloudflare from an nginx / letsencryot solution, or a direct to emby with Certs config, then dust off that doco you (hopefully) made and prepare for the worst. Saves having a busted system that then you have to piece together under duress with unhappy remote family and friends. Easiest way I had was to roll back to a new basic nginx working solution for emby, then I moved to cloudflare tunnels which does not need nginx (as it is also a proxy server), so should cf stop working, I just re-enable the port forwards and deactivate the emby dns entry to point back to the nginx reverse proxy. No more cf then. Until someone with more skills that me can come up with a cdn that works with emby.

Make sure to remove delete privs from all users but the admin account so no one else can make that mistake.