Leaderboard

So much better...

Yes fingers crossed on this as it's my feeling that softworkz has brought not only technical expertise but order and method to Emby

Be kind. We all started ignorant; and the actions of streaming protocols are perhaps rather esoteric for those not directly concerned with them. I myself am unclear about the details of modern streaming. I have been working with computer software since 1970, and even wrote the networking layer of a commercial communications product around 1985; but things change, and it can be hard even for those relatively knowledgeable to keep up with things which are not one's own direct concern. My concern and sadness is not for people's ignorance, but for their unwillingness to accept expert advice and to learn from those whose job is dealing with the problems they face. It is necessary to accept (in all parts of life) that the answer is not always what you think it "should" be. Paul

The issue is solved. It was a network problem. My DHCP table was getting full as devices moved in and out of my network. I expanded the table and everything resolved itself. Embyforkodi was set up to direct play and never experienced issues. Still not sure why the phone always worked, but I have now given my Shield TV a static IP and made sure that there are plenty of available IP addresses for the device to grab instead of fighting over. Thank you for all your help.

I am being kind by not attacking them directly. I am not going to hold their hand and tell them it's alright to be ignorant and ignore the explanations from experts just becase they believe diffrerently. Covid has made it so people embrace their stupidity and to attack those who have knowledge. I won't stand for it as Idiocracy should not be the prophecy it has turned out to be.

You've already been told the reasons, but you don't want to accept it because it doesn't make sense to you. It's like explaining the fact the Earth is round to flat Earthers, who then do their own experiments to prove the Earth is flat, only to have those experiments prove the Earth is round, and then question the results of their experiments because they didn't get the results they wanted. You have it set in your mind that there is some conspiracy afoot, and you won't accept anything but the answers you want. The technical ignorance on the forums has been getting a little too strong lately with the ignorant touting their ignorance as a strength while telling those of us who are knowlegeable that we're wrong because they said so.

I moved from Plex to Emby and even though I think Emby is superior in its flexibility there are some things I like better with Plex, especially in terms of its looks. This theme is trying to fix that by making it a bit more similar to Plex but with some, in my opinion, improvements. The CSS is attached to this post for anyone interested and below are some screens to show it off Good to know I only use Chrome so I can't guarantee this CSS works as expected in other browsers. If you want the sidebar menu to look like in the screens, make sure to pin the sidebar. Watched badge/banderoll is inverted which means that the badge will not be shown if media have been watched, like in Plex. For desired look, please use the "Dark" theme for both Theme & Settings theme in the display settings. Emby-Stable-style-v3.6.txt

@EliteGroupI can speak from experience that the Gen 3 Amazon Firecube 100% supports AV1, as does the Firestick 4k MAX line (though the Firesticks have issues with hybrid DV/HDR10+ files, Firecube does not). I made my comment as even on Doom9, where some of the devs of AV1 hang out, when we ask them for instructions on how to encode things and WHY we should use such switches, we are told "use this, and STFU" with no explanations on what those switches do, why they do it etc. It's really frustrating. I would like to do more AV1 encoding myself, but some don't respect threading so it runs single threaded, others if you use too much threading it drops the quality, to grain synthesis not being supported on some devices, etc.

@Luke I read it in the Emby log. I will try and recreate the event and send you the log. I have been watching via log messages each time the server calls anything in the Tuner code trying to understand why the next channel is found OK in Chrom but not with Android. Sometimes even Edge goes to the next program OK. As a temporary fix I was considering sending a playlist to the client when a program is requested. I know @pünktchenhas this working. I am only interested in this solution for my own use. Do you have any ballpark idea when this problem will be solved? Vic

Speaking as an encoder, AV1 is still in its infancy for support so this will probably take a while. It also doesn't help that the documentation is rather lacking and that there is so much fragmentation. It's highly possible that Emby is throwing the entire stream under the bus to take the easiest/safest route out. For example, AC3 in an mp4 container is not really standard, so they may be taking the safest approach to make everything "standard", ie video and audio codec. I know it's not the answer someone wants to read, but that is a possiblility from a playback standpoint. It's "always best" to bring things to the safest possible standard (ie lowest common denomintator) when something isn't supported or as expected. I would say give the devs more time to understand the handling of AV1 and it's dumbness. We will more than likely see the same thing happen with VVC and AV2.

You won't be surprised to hear I'm not sure what you mean, except if it this (which also works) - div.detailImageContainer-main.detailImageContainer-small {max-width: 10vw;} div.detailImageContainer-main.detailImageContainer-portrait {max-width: 10vw;} But the good news is I'll be trying to change the radius of the corners and add a border to that poster soon, so I hope you've got your Patience hat on...

Hi, none that I'm aware of. Thanks.

Where do you shuffle genres from? Search>Genres results or Movie library>Genres?

yes! mp3tag did everything for me. even the renumbering of tracks. now I'm happy with emby and my selfmade playlists. thank you for the hits. Michael

Thanks again.

Just an update, been running 4.9.7 beta (x86 version) for the past 10 days with no crashes.

Most collection type albums need an Album Artist tag to tell Emby it is a collection and not a series of individual singles by individual artists. You can use Various or Various Artists etc. You'll probably need to manually edit the metadata tags with a tool like mp3tag

A new Build of the WMC UI is available: https://github.com/EmbySupport/Emby.WMC.UI/releases/tag/0.112.0. Changelog:0.112.0 Fix GenericUI tabs Fix theme name 0.111.0 Maintenance only 0.110.0 Maintenance only

Probably because some of us have over 100tb of media and it would literally take years and cost thousands of dollars in cooling and electricity bills

It is also our goal but the number of store policies and procedures we have to juggle with all of our different app platforms sometimes puts us in the position of having to decide between an inconvenience for a time for a small subset of users vs holding back (even longer) a server release for everyone.

There are whole posts dedicated to Starlink. They use CGNAT and Emby is absolutely not setup to handle the way Starlink mangles (yes mangles, not manages) your data as that would be far too much overhead and cost way too much. Starlink is a YOU problem, period. You need to setup everything on your end for it to function properly, or move to Plex who has everything go through their servers before it gets to your friend's system. The one thing users like about Emby is the devs don't spy on you..so unless you want them to start routing traffic through their servers to inspect everything and monetize as much data as they can about you and your users, setup everything on your end for Starlink to work properly.

First two are common as Emby looks for the files whether they exist or not. @Luke I know my (old) beta has empty json files there but my new install does not and gets the same System.IO.DirectoryNotFoundException: Could not find a part of the path for "seriestimers.json" and "timers.json"

In several clients, like all the Rokus, the playback and the buffer are controlled by the client itself. That is Emby provides properly formatted streams and some basic info and then the client plays it. Emby, in many cases, has no control over playback after setting things up except to provide. I also think that the "problem" is real but directly related to the client device or to the route the data takes to get to your client from your server. Utilities like any of the speed test apps do not always use the same route to make their tests that the server/client uses. I once, many years ago, had a bad buffering problem on one of my clients and all the others worked fine. What I finally found was that a different device was throwing noise, due apparently to a defective cable, and the noise was clogging my network so bad that some clients connected to my router could not recover from all the lost packets. It turned out that the wireless side of my network was not effected so instead of replacing the cable I made that misbehaving client's connect wireless and, thankfully it was really the cable and everything performed great after the switch. Normally I recommend connecting most everything wired but, in this case, going wireless was the moved that fixed the problems. BTW: The noise might not have actually been the cables fault. It could have been the Ethernet port generating the noise. I have never had a reason to go back to wired for that client so the actual source of the noise has not been determined. Heck, it could have been just some dirt in the connection. It does not really matter now as everything is working and I am a firm believer in: "If it ain't broke don't fix it" and, right now my network and the clients and other devices connected to it "ain't broke."

More people who don't seem to understand how things work, and then questioning the devs when they are told they are wrong. I wonder how much longer it will be before Luke and the team start refusing to answer queeries from users as they get more and more ignorant in their demands for things they just don't want to understand.

Hello and thank you for the reply. I'm making no assumptions at all for someone that has hardware to spare in terms of compute power and limited space availability it makes very little sences to keep a redundant copy of the exact same movie for streaming purposes consistently using space for only being used a few times a year it seems for me at least a very obsolete solution. It make far more sense to be able to utilise my 3090 or 5960wx horse power for on the fly transcoding. Why not have both options as most igpus these days transcode to h265 very efficantly.

Yep sorry didn't realize detail screen all changes to view-item-item. So a higher level has to be targeted in this case dialogContainer for livetv.

How about this as that pop-up is dialogcontainer not view-livetv-livetv. div.view .topDetailsMain:not(div.dialogContainer .topDetailsMain){padding-top: 55em; }

add div.scrollY-mini {scrollbar-width: auto;}

yeah, seems like it was 4.8.x and the older version of virtualtv. all fine now

@Gilgamesh_48I agree with you, but I don’t think it is purely a network problem, as the network does work for other streaming services, and for things like FaceTime. I have tested the network speed and packet loss, and it is minimal but there is some intermittent loss. I’ll be the first to admit Starlink is not the most reliable, but I do think it’s a combination of emby and Starlink together, which is why I suggested there being room to maybe improve emby streaming settings for certain situations where bigger buffers would be useful. Ultimately, other services seem better equipped to deal with minimal network instability, which is why I agree with the OP.

@visproductionI hear what you’re saying. Unfortunately the problem I am describing is not a problem of overloading a server by transcoding multiple streams, it happens with a single user on a 16-core server. There is no “taxing the server with transcoding” - I have eliminated that as a constraint.

Si ya tienes Emby Premiere y has llegado al límite, puedes ampliar el número de dispositivos, de esta forma ayudas al desarrollo de esta magnifica aplicación.

Here's one from today: I'll be cleaning up over the next few weeks though, splitting this into 2 servers... I'm running out of space on my main server and backups are a nightmare

I actually agree with @strichmoand think there is room for improvement here in terms of buffering. Not sure why certain people are throwing their toys out of the pram when we are simply discussing suggestions for improvements, but hey. My emby server is connected to a 1Gbps fibre connection and one family member accessing via Starlink using Android TV client (NVIDIA Shield) has continuous buffering issues. Media on all other services play without issue (Netflix, Prime, Apollo TV, YouTube). Other users on the server don’t have issues. Speed testing the Starlink connection gives results consistently in the 100Mbps+ upstream, and real-time video calls are made relatively uninterrupted on Zoom/Facetime. The problems are consistently with Emby being able to maintain a reliable stream at 15Mbps (max bitrate on the client) on a connection with speeds in excess of that figure, which would suggest a buffer which is simply too small for some connections or there are some other streaming parameters which need to be tweaked. Perhaps there could be two “modes” - one with HLS parameters as they are now, and one with a set of parameters tweaked for slower startup/seeking and with higher buffer? https://www.speedtest.net/result/i/6017479900 https://www.speedtest.net/result/i/6017496455

Somehow, It's working now... So, i guess working on another project for a bit of time helped Have no idea on what changed...

I made an updated version that should fix the issue. This should also be compatible with nested folder structures, the "Top Picks", and the "New Releases" plugin. I also improved the logging a bit. However, I did only very limited testing, so use it at your own risk and please create a backup before you try it. Do not use it if you are unwilling to restore your backup in case something goes wrong. AutoCollections_1.0.0.9-libraryoption.dll

Thanks for the detailed response @Luke. Clearly we are all pretty keen for this to be implemented, so excellent news that it's a go ahead. I for one am eagerly waiting for this so I can finally off load WMC & ServerWMC. I'm hopeful that it won't be another year in waiting. Cheers Chris

Hi everyone, just to give you a response, yes this will be coming. Stay tuned in the coming months for more information. Currently our focus right now is continued support of the new 4.8 server release, as well as the new Windows app that is imminent. Following that we will be focused on a short 4.9 release to try break away from our history of long releases. Once we get through that, then you can expect things to speed up related to this. Thanks guys.

Also finding my self in dire need of this feature to trancscode and stream in h265 while traveling on holidays or for work. While in limited connectivity camping as well as it’s becoming more and more evident that places and provides are using limiting practices for bandwidth. lets take for example a family of 2-4 trying to stream from a regular Australian connection where bandwidth is limited to only 20mbps upload not to mention that most hotels have a 5-10 mbps download limit it’s quite hard to get anything decent quality wise out of 264 without buffer moments. Been a long time premium member of emby and would love to see this feature finally become available as a server side setting or even as the prefrance and fail back to h264 if client device isn’t compatible for decode. love your product and support guys just want to push my preference for this feature.

They should be, although [tvdbid/tmdbid/imdbid] was the only schema up until latest server version (4.8.x) when others were introduced, I can only assume that parser still needs some refining.

I've been running my emby server like this for a number of years without any issues. Before updating I take a snapshot of the jail (/mnt/pool/iocage/jails/emby) AND the emby user dataset (/mnt/pool/embydb). If there is a problem and I need to rollback, I make sure to rollback both. You are right though, rolling back one and not the other can lead to problems.

Thank you to everyone who took the time to ask the Emby team questions across all of the different platforms including here on the forums. There were a lot of great questions that were thrown our way and we've been excited to get the answers out to you. While some of the questions we were not able to answer, we did our best to give you the most accurate and clear answers possible. Now without further ado, here is the first series of questions and answers for you to look over! Please keep in mind more questions and answers will be coming in additional blog posts in the coming days, so not all questions are being answered today. Who owns Emby? Emby LLC owns the Emby product and is a private entity. The owners are undisclosed but note that the development team has full control over the direction of the product. We are not beholden to or under the influence of any investor or investment group. What is the history of Emby? Emby grew out of an open source project called MediaBrowser. Emby's origin in concept came out of that project but there is actually none of that code base still within it. Emby ended up being completely built from the ground up to be a server-based ecosystem as opposed to just a single app as the old MediaBrowser was. Around 2011 what is now the core development team for Emby were contributors to MediaBrowser. We saw the opportunity to build something more flexible than the WMC environment would allow and embarked on creating what we then called MB 3. The core developers spent over a year furiously writing code before anything was released to the public. It was then probably another two years of dedicated development before anything was truly usable as a system. In 2015 it was decided that we had moved so far away from what MB originally was that we needed a new name. A few of the devs got together and came up with "Emby". There are a few reasons behind that name but one of the main ones was that you needed something that wasn't already trademarked and domained. Emby fit that bill and has the benefit of sounding like "MB" when you say it. With the new name, we needed a new logo and we actually held a contest in the forum taking contributions from users and that finally landed us on the logo you see now. Since 2015 we have expanded the team and worked diligently to try and continue to craft the best truly personal media server system we can. We still have a long way to go but have also come a long way to where we are. What are the most popular Emby clients? We do not have exact data on this, due to sideloading and the such, but through the app store platforms we can gain general ideas. Android is the most popular amongst our userbase (both mobile and TV) with iOS in second place as the most downloaded app. What Emby clients do the development team use most for personal use? Our development team uses a wide variety of apps just as our user base does. We have people on the team using Android on mobile and TV, iOS, Apple TV, Roku and Xbox as well. As you can see our dev team really is as diverse as our user base when it comes to how we use the server. These were just a few of the questions about Emby as a product and who we are. In the next blog post we will be covering a few different things such as some of the future goals of Emby as well as release schedules and more! View the full article

Almost there! Only 3 and a half more years guys But serious now, dont you think its time to get this "Killer" feature now? Mark it as "Experimental" or hide it in a "Expert" section to enable, in case is would confuse ppl (tbh we are all enthusiast here, be real! We know what we are doing/looking for, even IF, thats a big if, ppl get problems with this feature, it would be the minority... ) Its about time to get H.265 as Transcode option, since the new Codec AV1 is already getting supported and with that pretty much any device since 2020 (Wild guess) supports H.265. Something funny here, I saw the question in this thread: "Why do ppl use Emby instead of JllyFin, when they can support feature like that?" Simple Answer: JellyFin got NO Apps on all divices like Emby does, other wise no one would use Emby! <- My opinion.

There is no fix for Samsung apps transcoding DTS. Samsung TVs haven't supported DTS since 2017. There should be a chart in your user's manual like in the link below. That is a list of all audio codecs your TV supports. Anything else will need to be transcoded. https://developer.samsung.com/smarttv/develop/specifications/media-specifications/2023-tv-video-specifications.html For best results always preselect a compatible audio codec if available. Otherwise, you can see buffering which gets worse the higher the bitrate of the input.

NEWS! A final decision is imminent now. All I can say is that it will be either yes or no - but nothing half-way. No matter how the outcome - at this point I want to say a big thanks to all of you for your interest and for supporting this. Thanks to all the testers who participated in the initial beta for all your work and effort in helping this to become a successfull parrt of Emby. Also thanks to all the nice and friendly users and community members, moderators, admins and fellow developers who I've had the chance to work with and talk to so far, during the past few years! Best wishes, softworkz

Assuming on same network (port forwarding will do nothing for this) identify your server ip address first. You mentioned emby apps work on streaming devices (streaming apps self discover the server anyway), so click on the the little user icon on top right and goto manage server, it should tell your internal ip address. Note it. Now goto a computer, shell to dos (start, run, CMD hit enter) then try to ping the Server ip address. Command is "ping xxx.xxx.xxx.xxx" remote the quotes and put in the ip instead of xxxx. If successful, then goto the web browser and http://xxx.xxx.xxx.xxx:8096 Push come to shove, install Angry IP Scanner on a computer, refer to my Lasp post here ( )

Hey Luke, No both Apple TVs are local LAN connected. Increasing the internet video quality in the app did however solve the problem. As soon as I increased it to or above the quality of the video being played it started playing it through direct play instead of transcoding. This gave me the clues required to find the root cause for the issue.My Emby server runs as a Kubernetes pod behind a traefik loadbalancer, which results in the server having an internal cluster IP. This subnet was not being considered as a local network by Emby so remote polices where being applied for all connections. Thank you so much for looking into this and great work on the 4.8 release!

Since I'm running my server from my house on a dynamic IP from my internet provider, support for Dynamic DNS was a requirement. Google domains had worked great for me for a long time, but with the change to Squarespace with no DDNS support it's a no go for me now. I just transferred my domain name registration from Squarespace/Google to Namecheap. Cost me $13 for the transfer, and was super easy, all done in a few minutes. The namecheap interface for managing the domain was simple and actually very similar to Google, so it was familiar and easy. With google domains, my ASUS router directly supported DDNS which was very convenient (although it didn't always work 100% reliably). Namecheap isn't supported by my router directly, but they have a Windows dynamic DNS client that I set up to run on my Emby server which is always on anyways, and it seems to be working just fine. For those with more experience than I, namecheap dynamic DNS also works with DDClient (primarly a linux tool, but there is apparently also a windows install). I'm by no means an expert and make no claim that this is the best solution, but I did just make this change and it seems to be working well so at least this is one working option to consider.

the whole point on why emby is better is none of your stuff goes through their servers. plex has access to all your stuff.

If you think adaptive streaming is a quick fix - then best of luck. I'll leave it with you.