Leaderboard

While I agree with most of your points there, @cayars, I don't quite share your understanding for contributors and their moaning. If not all, then most (or not?) of us have at some point or another uploaded a bit of two there, but the amount of data retreived is infinitely larger, at least in my case. Granted, I'm positive there is/was a number of serious content uploaders there, with ratio reversed, albeit I'm also positive that content consumers are vast majority, by far. And therein lies the problem: "We created content there, so it's ours." No, it ain't. Nor it ever was. Nobody was prevented to create their own site, service or whatever. And be in total control. (And likely fail graciously). And all this uproar for - where I come from - price of HALF cup of coffee is beyond me. Even contemplating that to be a deal-breaker for me is, sincerely, ridiculous. And the choice of having that data for miserable sum (while in the same time overpaying for number of services which I use by an order of magnitude less than TVDB data) or not having it at all - is no choice at all. My 2c.

I think I was the last one to touch it but any member of the community can pitch in and help maintain them. Both plug ins are community plugins now that iXsystems has dropped maintaining the Emby plugin. I put all the pkgs that the instructions at: https://emby.media/freebsd-server.html but didn't think about the order. If no one beats me to it I'll fix the order in the json files.

I have many commercial products which are not supported a fraction as well as Emby is. Paul

I just setup nvidia encoding in my home kubernetes and it was easier than it was getting it working on a desktop, install gpu-operator via helm.. wait a few moments and it self installed drivers on all nodes that had the hardware, then I edited my emby workload to use a gpu resource and that was it. I deployed a database cluster backend much the same way, few simple commands and full highly available setup deployed across nodes thats self healing.. Before K8's this used to the the stuff that took a ton of time to spin up and made no sense for anyone to do at home for anything personal. Much of the desire here with container orchestration is it scales nicely and once you got a highly available setup going, deploying highly available workloads into it is a piece of cake.. and it makes creating a HA setup with common off the shelf hardware feasible for the home workloads like emby.. Its not so much the performance aspect for me as any one of my nodes is more than enough, its that moving to a home video solution like Emby has put great demands on me to keep it up and online because the very moment it dont work someone's here at my door complaining about it.. so some automated self healing love spread behind my existing load balancers and nodes would be very much appreciated here.. it takes time to detect a problem and spin up new instances, or roll out new changes/upgrades, Ive got to stay up late at night to keep the impact to a minimum when in a K8's cluster I could roll it out w/out interrupting anyone. my media is already hosted on NFS server, and mounted to the emby container as read only.. I've got multiple nodes capable of running an emby instance on every node. Its not uncommon for the home lab to have a database server provisioned and tuned specifically for performance. I think a common audience here is power users, someone saw enough justification to add in LDAP auth support to Emby then there is plenty of demand for a generic database backend IMO. Let us mad scientists cookup whatever creations in our basements that we want, and few will complain about code licensing.

I would love the option to store Emby's database in MySQL - I have a setup that serves around 30 people and I feel that there would be real performance gains by using a proper relational backend over SQLite (I'm presuming). On top of this it would make life easier for me when reporting on watched status a cross users.

Hello, I would really like to be able to record all programs with the keyword golf in the title (for example). Thanks, Erik

Not that I know of. I ended up using tvheadend behind Emby to solve this issue. Little more setup but once you have it going it’s very smooth.

Normally it was more about QSV (Intel Media SDK) providing more options and somewhat better quality, but recently I had compared both on a Tiger Lake CPU and QSV was 1.5 times faster than VAAPI doing the same task. Now, that was just a single test on a single system and that doesn't say much. But I'm curious to see what users will report in this regard.

I don't know if this helps but I went back to 18.9 with a fresh install and installed emby-next-gen. This time it worked and it showed me all of the deps that it was going to install which it did not do on 19. Once it was installed and i made sure everything worked I upgraded to 19 and everything seems to be working.

I personally don't believe performance to be as big of an issue regarding SQLite alternatives, when compared to concurrent connections/externally hosted gains. SQLite is performant enough to be considered negligible unless you have an insane amount of content and even then I'd wager that any slowdowns could be caused by a multitude of other factors before SQLite itself, even possibly disk read speeds when querying the db. You may see (probably undetectably) small performance gains using something other than SQLite, but my guess is that you could see much larger gains by hosting it on another machine entirely. But please correct me if I'm wrong. All this is obviously still recognizing, as stated, that this falls out of scope of current user interests. Just thinking about it aloud.

Yes, Eric, I do... Adding a few hundred thousand music tracks to Emby slows the whole server down to a point it becomes a real pain and it's getting worse with newer server versions. I've been through the whole "get rid of plugins", is Emby on separate storage, where is the cache folder, new installs, etc. with you guys a few times already, but somehow it always dies off... This is happening on various flavours of Emby (NAS, Windows, Linux and on various pieces of hardware) and only when adding a large amount of music tracks this really becomes an issue... Would this happen with another "flavour" of SQL? Possibly... but it's less likely that if I have Emby installed on 1 server and the database on my dedicated SQL machine with a 2.5Gbit connection, that I have these issues...

Correct, for a real high availability solution with load-balancing and auto-failover, the following steps would be required: Support storing the data in an external database You will need two DB servers in a cluster/failover configuration supporting transactional replication (bye bye MySQL...) Change the server to store all session state in the database Introduce "Roles" for the server so you can have for example a server that is responsible only for library management and metadata retrieval, servers for servicing user requests (http) and finally servers that are doing transcoding and serving the media to clients. The ability to offload transcoding to "transcoding slave servers" would surely be a reasonable part here, even though not necessarily required for "High Availability". On the other side, the ability to offload transcoding alone would be much easier to implement and surely useful for certain deployments.

Very well said and worth more than 2c.

I didn't know the name until I saw his pic. 47 movies. 0 movies for Nicholas Cage but Nicolas Cage shows up in 91 Movies. 110 Movies This is even higher then the person I thought had the most movies on my system. Now that you bested me, I had thought Bruce Willis with 102 movies was likely the most.

No problem. Let us know if you run into any other issues. Thanks.

DDNS points to your domain name via a C-name record - that's a pretty normal setup. That way you can use a free DDNS provider and point to your domain. SSL works fine as it's the endpoint where the SSL is challenged, not the journey to get there.

While I prepare my media in much the same way as @cayars - you are probably using a sledgehammer to crack a nut here. If all you want to do is remove the internal subtitles, then a simple remux is all you need to do as post processing. If the files are 60Gb, then I assume they are 4K HEVC with HD Audio anyway - so just removing the PGS subs is a matter of leaving them out of the remux command. ie ffmpeg.exe -i "inputfile.mkv" -c:v copy -c:a copy "outputfile.mkv" This will COPY (not transcode or degrade in any way) all the Video and Audio tracks in the input MKV into a second(copy) MKV without any subtitles. Depending on the disk I/O - it will take maybe 1-2 minutes if on the same disk, if you split the input/output onto separate disks, it will be much faster than that. If you need to do a batch, then just repeat the above command with a recursive directory scan of all MKV files. Shout if you want the syntax/batch file for this. This is effectively using a fraction of what can be done using sickbeard (or other tools) but as I said - those tools can be overwhelming if you just want to so something simple. I hope that helps.

I'm pretty sure they were in the situation of - either we shut this down, or we find a way to keep it going. Put it this way - if you'd been working for free for several years and finally run out of savings, you might be forced to take a job that pays.

Hi Quickmic. Nope all power management is turned off and kodi is configured with all power saving off. Funnily enough I had also rebooted the NUC as an attempt to resolve the problem which didn't help. That's why I was surprised that disabling and re-enabling the plugin helped. Edit. I've swapped out the NUC with a spare for the moment but the unit that was having problems is now working since the add-on was disabled/enabled. Even after a reboot. This is the log file for the working system. It may look different as it's plugged into a PC monitor instead of the TV. https://paste.kodi.tv/etiropivol

For example on my system I can drop a file into a watch folder and it doesn't matter where the file originated from. It gets an SRT forced sub file based on a hash if available. It get's the video converted to H.265 with specs I want. I strip out all non-English audio and subtitle tracks UNLESS there was no English then I leave the audio as is. I pull subrip from files and create SRT files. I pull Closed Captioning nd create SRT with that data as well. I look for and remove commercials if the file was a TS file (usually a DVR recording). I create a 2 channel 256Mb AAC audio track and mark it as the default if it doesn't exist. I normalize the audio of the 2 channel track above while creating it. I rename all files correctly I can pull down theme songs and theme videos for the movie or show I can pull down trailers so they're local I create the sub folders with everything in the correct folders. I then move the folder to the correct library on the correct drive for my media. I don't lift a finger to do any of this and it's fully automated.

Nah, nothing to worry about on that front. Your router will take care of all of that. Think about it. Do you think you can't run a webserver or two in a small company along with 50 people all using ports 80 and 443 all day long. The major advantage in general is http = port 80 and https = port 443 when no ports are specified in URs. That makes it easy to just type your domain name in a browser and boom, Emby loads. The downside to this as always is using KNOWN ports makes your server an easier target to identify via any remote port scan and port 80 is a default port to scan. If you switched ports to something random in the correct range then it's slightly harder to find this way as it won't show up in a scan only checking common ports but anyone doing a scan of all ports would stll find it. Well worth the trade off IMHO. But as always there is no right or wrong way to set this up.

What ports you choose to use are up to you but 80/443 or just 443 is likely the best choice. Any browser will use these two port as the default. These two ports will work with any proxy or CDN service like Cloudflare that Emby default ports will not. If using Alexa or Google Home and want to playback audio on the device itself 443 is a great choice. In an update to Remote Setup that will cover some advanced topics these will be used as the default ports as they have advantages other ports don't have. I agree with everything Sammy said above except the DDNS which you don't want with SSL but want a domain you control instead. So DDNS or Domain & SSL.

Excellent. Thanks.

Just installed the app you supplied and initial testing it plays back the 10bit files without tranacoding now.

Serialize and edit the chapter xml, sounds like something to look into.

These folks will never implement TVE. Your best bet is to run Channels on an RPi and use Channels as an m3u tuner for Emby. I've been running that for a few months now and it works fine. Although I must say if you only want to pay for one product then install Jellyfin. Emby is not supported like a commercial product and frankly I wish I never paid for it.

Note for others who can't read, like me. Use 989 and not user 'media' as displayed in one of the screenshots, this is important!

This should apply to those that have already upgraded to matrix and embuary has been automatically disabled. Copy the addon.xml (located in the skin.embuary-leia folder in the add-ons folder within your kodi userdata folder) from your kodi install to a computer. Your userdata folder will be different depending on what you have kodi installed on. Check the kodi wiki if you don't know where it is. Open the addon.xml file in either notepad++ or notepad. Find the line that says <import addon="xbmc.gui" version="5.14.0"/> And change it to <import addon="xbmc.gui" version="5.15.0"/> Then copy the addon.xml back to the same location for your kodi install in step 1. Restart your box and/or kodi. You can now enable/select the skin in settings.

I know this isn't Emby's fault, but is this update ever going to come through?

Check out the next version, should be a bit brighter. Also check with multiple different videos. The current is a quick and lightweight solution. It has taken great effort to achieve the quick image extraction that we have and I don't want to unnecessarily load it with something that adds again. We'll see how it works out and revisit this subject if it doesn't. BTW: HW acceleration for image extraction is totally pointless (for our quick-image-extraction at least). I've explained the background somewhere here in the forums.

MariaDB is free, fully compatible with MySQL, and not owned by Oracle! It's my go-to database these days (after a brief flirtation with PostgreSQL). Paul

It is five years old and still an issue. Some things are nitpicky (playback speed) but some things are relatively breaking. To this day if I download an audiobook offline it starts over every single time, only streaming through the library (the online version) saves progress. Like OK so I guess I will use emby to download the book offline and play it in a different player that is actually functional because my choice is either use my data or start my book over every time I play it. Try listening to Wheel of Time offline see how well that works for you.

I agree. I was just saying that for importance of features, ones with workarounds like this are generally less important than issues with no workaround.

There is no need for uniformity, in my opinion the application design should match the target platform, the problem of Emby for Apple TV is another, the lack of functionality, to name a few: Native player: Lack of visual seek and visual chapter navigation, while direct streaming or transcoding Native player: Lack of fMP4 streaming (server limitation), so MKV HEVC streaming is not supported for Apple devices MPV Player: Lack of framerate and dynamic range match MPV Player: Lack of HDR passthrough MPV Player: Lack of DTS decode MPV Player: Lack of visual seek and visual chapter navigation It has been many years with these requests. Users tend to use Infuse or Plex. Just note that there are fewer and fewer active users on the Emby Apple TV beta forum. It is true that the application has been improved, but not enough.

I think they just made that up lol. As you stated there's no "buying licenses" to use the APIs. Also 100% agree that the technical part should be completely ironed out before worrying about the UI. At the same time, when launching a "finished" product, they should go hand in hand to some extent. When a client looks completely different from your others, as the Apple TV version of Emby does compared to Fire TV, Smart TVs, Android, Roku etc, it looks almost like a half ass attempt to put something together just to have it there. I'm not saying that's the case with Emby... but that is how a lot of Apple TV Emby users feel.

Correct it will stop you before you play, but it won't interrupt you while playing. That's something that needs to be improved.

As I understand it, the time limits control logging in, but do not, for instance, prevent continuing to view something started before the end time. The OP is hoping for much stronger control than that, I think. Paul

I think in that above example though, the standard version would be slightly easier to stream. It's got a slightly lower bitrate in both video and audio. Plus the audio stream is 2ch which should make it most compatible. But as @Baenwort mentioned, 3D viewing is getting hard now a days. It was a technology that was really only out for a period of a few years and has been mostly abandoned by most major tv manufacturers. I wouldn't see much purpose in spending development time to try to tell that the video is in 3D and forcing it to the bottom of the version list. It would be like trying to go to market with a new design on a bluray/vhs player! In my personal opinion, having the 3D files mixed in with the normal files isn't the best approach anyways. I would personally create a separate 3D library. If I want to sit down with the family and watch a 3D movie on the 1 3D capable tv I have left, I don't want to flip through the thousands of movies in my library trying to remember which ones are in 3D and which ones aren't. Or worse, sit down in front of my non-3D tv's and having a 3D movie start. I'd much rather pull up the library with only 3D movies and be able to quickly see what's there.

The dev team is small and the problems with Apple TV are monumental, from every single post about it. They have been working on the problem for 2+ years. Using Infuse is the best way to watch HDR content on an Apple TV. Infuse paid Apple for the licences they need in order to have their app working 100%. Even Plex still has issues, and only has HDR available for plexpass users. Jellyfin HAHAHA. This is what happens when you purchase a device from a company that locks you out of your own content and controls everything with an iron fist and refuses to allow you to play your own media. If you want a better experience, I would personally suggest an Android device like a Shield or FireTV. As for tonemapping, it's coming, but you need relatively modern hardware and can't have a potato of a server. I am just an informed user who has been here for years and I have over 2 decades of encoding and media experience.

I think a lot of the issue is that the Apple TV doesn't play a lot of those files natively. So if it's an .mkv file (assuming it is for HDR) there's got to be some transcoding going on. Infuse does that by just changing the container (which Emby can do as well). I'm an Apple TV person myself and I hope this is in development for them sooner than later. It should be something that should be done... and then adding in HDR tonemapping so I don't have to have both 4k and 1080p versions of movies/shows would be great too. Lot's of stuff on the horizon that I think Emby is working on. Personally though I love Infuse as I've used it more and more.

I have also 3200g, here my docker img. Ubunutu 20.04, os not need the amd driver https://hub.docker.com/r/gudszent/emby_ryzen dont forget to set the permission from the description ps.: Yes, I know, the img big, but the AMD driver 800MB

Channel groups coming in Emby Server 4.6:

This sort of thing is *almost* available already if you run Emby in docker and create a kubernetes (or docker swarm) cluster. I haven't tried it yet, so I don't know what all of the gotchas are, but I can think of three potential issues I'd expect to run into. Assumptions: You'd want to set up each node in your k8s cluster to use shared storage (shared by all the nodes) to access the same configuration (programdata folder), and the same media files. Ingress is configured (external to Emby itself) for the Emby service to provide round-robin access but also so that any given user would be routed to the same node for the duration of his session (or for the life of the pod on that node, whichever is shortest). That way session cookies should continue to work as they do now. Potential Issues: Shared configuration. The way Emby currently deals with config would mean shared sqlite3 database files accessed by more than one node. Care would need to be taken to make sure DB operations are atomic, roll back in case of an error, and to allow access from more than one node without database file locks. I don't know if that can be done with sqlite files, or if Emby would need to allow something like a mysql database to hold config as an alternative to sqlite. Scheduled tasks. Emby server instances would need to have a way to do some minimal coordination with other instances so that the same thing wouldn't be done twice by concurrently running Emby server instances. For example one instance would say, "I'm going to do scheduled task A now!" and get a "lock" on that task. That should be totally do-able with a shared database (see potential issue #1). If another Emby server instance tries to get a lock on task A before doing it, and that task is already locked, it would assume it's in process by another instance and skip it. Or, better yet, it would monitor the task being performed by the other instance to make sure it's successful, and if it errors or never indicates success, then it would get a "lock" on the task and execute it itself. Hardware accelerated video encoding. If I were to set up kubernetes at home to run Emby, I would set up three worker nodes, but only one is capable of hardware accelerated video encoding. Ideally, it would be possible for an Emby Server instance capable of hardware acceleration to act as an "agent" for other Emby instances that don't have that capability, so that a session handled by one of the non-hardware-accelerated nodes would be capable of doing everything else, but if available, it could ask the hardware accelerated node to do the encoding tasks. If the transcoding-temp directory is on shared storage, maybe that'd be possible without too much additional work by the Emby devs? Also, instead of a whole Emby server instance making itself as an agent to other server instances, maybe it would be easier for the video encoding to be handled by a separate module/program that only does encoding tasks. Those three potential issues are listed in order of the priority I'd give them. I think that looking at a project like this from a birds-eye view it could be overwhelming and hard to begin, but if you didn't worry so much about handling multi-servers or clusters yourself, and let kubernetes take that role, and instead focused on making Emby server play nicely in an environment where there may be more than one instance running and sharing the same config and media, then that would be easier to begin and you could let the users figure out the details of how to manage the multiple nodes. Just my thoughts as I'm in the process of moving just about everything else I run at home into kubernetes (Radarr, Sonarr, Ombi, qbittorrent, sabnzb, and Jackett).