All Activity

Strict vetting for SSL propagation delay can be around 5 days. Has it been that long, since you activated the SSL? https://sslinsights.com/how-long-does-ssl-take-to-propagate/

Zel, Turning off transcoding can also cause stuttering, depending on the end user's hardware, bandwidth, Wifi, other connectivity issues. Transcoding can actually help stop stuttering if it is setup correctly. Asking about transcoding is sort of only the first step to see what is happening. We need log files and actual settings and media codecs and size when transcoding is turned on. If the media file is too large to be handled through whatever combination you have setup, the playback will pause and crash. Wifi can also cause this with simply too much distance, even other appliances in the house or just being close to large metal items, like a fireplace poker within a few feet of the Wifi receiver. Band width via Ethernet can cause problems if 1GB cable connection is mismatched with a 10/100 switch or Ethernet card.

My test Aired order DVD order per steps above (In my test these would be be wrong for my actual file order) But should work in your case as your files are in that order.

Hi all, I'm running Emby Server 4.9.3.0 natively on Ubuntu Server 24.04 (Intel i5-12500, UHD 770, QuickSync/VAAPI enabled). I have ErsatzTV feeding Live TV channels into Emby via M3U (http://192.168.8.10:8409/iptv/channels.m3u) and XMLTV. ErsatzTV outputs HLS streams at 1200 kbit/s H.264 AAC 720p. The problem: Emby always transcodes the Live TV stream rather than direct streaming it, and the transcode runs at barely above 1x real-time speed, causing buffering and stuttering on all clients. What the transcode log shows: The media source is flagged as: "SupportsDirectStream": false "SupportsDirectPlay": false The transcode reason is ContainerBitrateExceedsLimit, DirectPlayError. The HLS manifest from ErsatzTV reports variant_bitrate: 0, so Emby probes the stream and estimates ~4 Mbit/s. It then decides this exceeds the client's limit and transcodes — even when the client quality setting is set to 4 Mbit/s, resulting in a pointless transcode of a 1200 kbit/s source. The ffmpeg transcode command Emby generates: Input: ErsatzTV HLS at http://192.168.8.10:8409/iptv/session/1/hls.m3u8 Decoder: h264_qsv Encoder: h264_qsv at 10 Mbit/s (or 3.8 Mbit/s at lower quality settings) Speed: starts at ~19x, degrades to ~1.02–1.05x real-time during sustained playback At 1.02x speed there's almost no headroom, so any brief slowdown causes the client to buffer. What I've already ruled out: Local disk I/O is not the bottleneck (NVMe at <2% utilisation) NAS SMB read speed is ~45 MB/s, far above what's needed GPU is not throttling (running at ~1417 MHz) ErsatzTV's own ffmpeg pipeline is healthy and producing segments on time I guess the key question is: Is there any way to force Emby to direct stream (copy) an HLS Live TV source from an M3U tuner, rather than transcoding? The source is already H.264 AAC in an MPEG-TS container, which should be universally compatible. Is the SupportsDirectStream: false flag hardcoded for M3U Live TV sources, or is there a way to influence it via a device profile or server setting? Any help appreciated. A couple of logs attached for your reference. ffmpeg-transcode-3aa1a334-fdde-419f-a931-cb9380d36de0_1.txt ffmpeg-transcode-2c59b904-f3b8-417a-91db-6111478bb332_1 (1).txt

@visproductionthat's the upnp plugin telling emby it can't configure the router. And that's not what this is about.

Did you Refresh on the Series/Show or just the episodes? As this option affect the entire Series not individual episodes. Set Series/Show order option Refresh metadata w/replace images on Series/Show Wait a few seconds for Emby to get new info from provider Refresh web page (info should be in new order) Only way you may/will have issues is if there is Locked metadata at Series/Show or Episode levels. If this does not work, we will need to see the server log showing this process.

I'm not sure what you mean.

Hello, I'm using the Thetvdb module, but even after sorting by DVD, it didn't work. Refreshing the files didn't work either. Do I need to restart the server afterward, or is it immediate? If it's the latter, then it wasn't working. Thanks anyway.

Hi. Hopefully, it is just a temporary interruption. Thanks.

Thanks @FrostByte, Downloaded, Installed and working

Failed to load resource - possible solutions: https://windowsreport.com/error-loading-resource-chrome/

@LukeI need your help

Beton, I think naming the preroll files differently can result in a different video that plays with specific audio or video formats. Of course that can change after a transcoding, depending on the user's equipment and connection bandwidth. Another way to do this would be to use Vantage point, where you can assign a video per media. That's a lot of work creating new videos, but you can always just take a short video of yourself, explaining how wonderful a specific TV episode or film is, like a film critic preview.

Interesting feature request. It may be easier to have the alert go top center, because pushing down the Play action buttons on mobile, tablets and small browsers may not look good. They could be pushed down the page and no longer appear on the media page until the user scrolls down. Top center may look old fashion, but it will be more easily noticed. Also FYI: Vantage Point 2.0 plugin offers alert type preroll videos, per media. Of course, creating custom videos is a lot more work. https://emby.media/community/topic/111310-vantage-point-20-complete-rework

In latest log Error in GetSpecificMappingAsync occurs 119 times. Linux access rights? Emby issue?

Try searching for "emb"

Yeah, you cant can't reflow the remaining items with CSS since they use absolute positioning with hardcoded inset values; the only way you could close the gaps is with js again; you could add those playlist IDs to an exclusion list in the same script?

Lol looks like 3 of us posted in the same min about this. Wonder whose are going to get closed as dupes. i clicked on the download link on their website and it said not available in my region. Im in the US.

USA as well.

Like the title says, Emby app is missing from the iOS App Store in Canada and UK and could be more regions.

Emby app missing from apple appstore on both iphone and apple tv. As of march 26 830am. whats the dealeo? thx!

The Emby app is no longer available in the Apple App Store. Do we know what’s going on with that?

@GrimReaper This version works much better. Just had to fine-tune a couple of things. Needed my local server number in place of yours and had to change the 202px spacing to 145px. Not sure why (????) as DevTools showed 202px. Also played around a bit with CSS for hiding individual selected Playlists as follows (e.g.) /* 1970s */ .appearsOnListsSection .virtualScrollItem:has(img[src*="/Items/688474/"]) { display: none !important; } But, then the hidden items need to be sorted to the end of all Playlists, otherwise blank spaces occur. Probably not a problem for me though, as my Playlists and Collections are sorted into sub-categories anyway and would only ever be shown or hidden as a set, according to these categories. There's probably some combination of splitting the row into two and hiding selected items on certain pages that will end up being useful. Thanks and Cheers !!

I would like to to request a notification feature that displays a one-line message for a media item (movie or TV show) details page. Admins should be able to manually set a custom message for specific movies or shows. For example, on a TV show like House of the Dragon, the message could be something like “Season 3 is coming soon” or “New episode on Monday.” I have attached images (photoshopped from Android TV and web client screenshots) to illustrate how this should look.

Hi Luke, I do have a workaround and can script around this, so I am not blocked. That is not really the point. The point is that something changed, the manual scan advice does not solve it, and the current behavior for people is not consistent with the behavior for movies. What used to work for me was straightforward: I could manage local people images directly in the metadata folder, refresh metadata, and Emby would pick up the change. That no longer works. What I am seeing now is this: If I manually place a folder.jpg into a person’s metadata folder, using the exact naming and location Emby itself uses, Emby does not reliably honor it. If I add the image through the web interface, Emby writes folder.jpg into that same folder and it displays correctly. If I then replace that same folder.jpg on disk with a different valid image, Emby does not handle the replacement properly. The image either does not update or goes blank. In my testing, scan/refresh behavior does not resolve this and may remove manually managed files instead. So yes, I have a workaround. I can convert the image to base64 and use the API to load it, and that works because Emby then creates the folder.jpg file itself. But that just raises a bigger question: why is there now a mandatory API Kabuki dance specifically for actor art? Requiring admin authentication for a metadata-changing API call is one thing. Requiring base64 conversion and an API-only path for person images, while movie posters and video NFO files still follow a logical local file-first workflow, is another. From the user side, that is an obvious inconsistency. One of the main reasons many of us use Emby is to curate private or local-heavy libraries that do not exist on TMDb or IMDb. I have scripts that build titles, actors, and metadata into NFO files for hundreds of non-mainstream entries. For movies, local metadata still works in a direct and sensible way. For people, it now appears that local filesystem management is no longer treated as authoritative in the same way. That is the actual issue here. Not whether I can hack around it, but that the workflow for people has changed while the workflow for movies apparently has not. And that leads to the documentation problem: if the intended workflow for people is now “base64 the image, authenticate as admin, POST it through the API, and let Emby create folder.jpg itself,” then that is a major workflow change and it is not clearly documented as such. Related to that, is person.nfo even still a meaningful part of the supported workflow for people metadata? There are enough signs now that people NFO/image handling is no longer behaving like the older local workflow, but I do not see that stated clearly anywhere. So my questions are simple: Was this workflow change for people intentional? If so, why is people artwork now handled differently from movie artwork? And is person.nfo still actually supported as a reliable local metadata mechanism for people, or not?