All Activity

Hi, what exactly do you mean by bullet screen?

I still have a Fire TV Box model 2014, the little flat one with a built in RJ45 port. Still rocking Emby on it on a non-smart TV.

What manual scan are you referring to?

Thank you for your feedback, Ive updated the documentation with more information for the plugin. Regarding your 500 error, I guess that you have entered your Emby user name in the config. Kometa was expecting a user id. I've updated the documentation and also added a check and id retrieval, so that this shouldn't stop Kometa any more.

Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!

Yeah I can - but I have like 8 users each of which have emby on phones, TVs, web clients... It'd mean getting everyone to do it, right?

HI, what makes you think bif is being deprecated?

Hi, yes an option for this is certainly possible. Thanks.

HI, yes it does make sense. Thanks for the feedback.

With a TV show you have three layers of NFO files: Series Season Episode This works great for my custom collections because I can modify / move / delete / rename any of the seasons and episode files and the show never leaves the custom collections I have. With movies, we have only the movie NFO per movie file we have. So if my file is replaced by a different version, my custom collection assignments are wiped out. I suggest having the NFOs be split: Movie Version In the Movie NFO, we would have all the basic metadata (Name, release date, description, cast, collections, etc.). In the version we would have pretty much just the run time and stream details. But it would mean that my time spent adding items to custom collections isn't wasted, or won't need to be redone.

Should this be marked as In Progress, then?

English clearly isn't their first language, so I wouldn't read too much into the use of “customers,” but if your family has 80 people in it...

Seeing as hes talking about customers in another thread i doubt that hes using at it as such.

OK we will have a new ffmpeg build on the server beta channel soon so we’ll see if that resolves this, thanks.

Hi, can you check again? Thanks.

OK we’ll take a look at it. Thanks.

Is there a reason why you can't set your bitrate cap to a value that covers direct play for all of your media?

i did switch locations and reverted back. although the recordings still act the same, i have set up some stuff to record to see if it acts the same. will report back. thanks

Thanks for the suggestions... I’ve been digging into this a bit more and it looks like the issue isn’t really my client settings after all. ErsatzTV is advertising a correct BANDWIDTH= value in the HLS manifest, but Emby is still detecting the stream as much higher bitrate than it actually is. For example, a 1.2 Mbps stream is being interpreted as ~4 Mbps, which then triggers ContainerBitrateExceedsLimit even though the real bitrate is well below any reasonable threshold. This seems to match a known Jellyfin/Eamby issue (ErsatzTV issue #2022) where MPEG‑TS/HLS streams have their bitrates inflated during detection, causing unnecessary transcoding or preventing direct stream. ErsatzTV and Dispatcharr both report the correct bitrate, but Emby’s Live TV pipeline overestimates it. So while setting a higher client bitrate can mask the problem, the underlying issue is that Emby is misreading the source bitrate and refusing to direct‑stream a feed that should already be compatible. I guess I'll make a proper bug report... unless this already constitutes one? @Luke?

@LukeI am also experiencing the same problem. I just got a new tv and have it hooked up to a Sonos Arc soundbar using dolby atmos. Plex, Sling, Youtube, have sound, EMBY does not. I have attached logs, please let me know if there is something else you need. Apple tv 26.4 running Emby Version 2.0.3 (2) Fails to play audio from live tv and server media. embyserver.txt

and? will it ever be fixed? watching a show with 20m episodes to change the sub every 16m is not so much fun and while were at it. I wrote already 10 times. In the lg app you cannot adjust the delay of the sub because the timing box is hiding the whole sub. who's testing that??

Thanks, I get what you mean about Live TV being stuck at 1× and Auto being unreliable. Does that explain why Emby is overestimating the bitrate of the stream coming from ErsatzTV. Because the source doesn’t advertise a proper bitrate, Emby probes it and assumes it’s around 4 Mbps, even though the actual output is only 1.2 Mbps. So Auto ends up enforcing a limit that the stream never actually exceeds, it’s just Emby’s estimate that’s too high. If I switch off Auto and pick a fixed bitrate, that becomes a global cap and forces transcoding for everything else I watch, which I’m trying to avoid. So I’m not sure the client setting alone solves it... the underlying issue is that Emby is misreading the source bitrate and refusing to direct‑stream a feed that should already be compatible. Does that make sense?

HI, it is possible for future updates. Thanks.

By restricted user I mean I've set the user to "Block items with no or unrecognized rating information" for all libraries. The user is set maximum allowed parental rating of "TV-Y/APPROVED/G/E/EC/TV-G." I've gone in and set the parental rating on a bunch of albums/tracks/artists to "APPROVED." When I go into the user's Music library and look under "Albums" there is nothing. When I go to songs it appears all the expected tracks are there. This started while I was using the ASUSTOR and on version 4.8.10.0, before that it seemed to work fine. At that time, it wasn't all of the albums, only new ones or ones that I updated the metadata for. When I moved over to Debian and Emby version 4.9.3.0 there has never been anything in the "Albums" area of the music library for that user. Users that don't have such restrictions see everything as expected. let me know if there is anything I can do to help -HS

For starters live-tv, being live, is always 1x. It can't transcode into the future. Increase the client bitrate limit. Auto is effectively broken on most if not all platforms.