Leaderboard

Here is the latest list of versions for Emby software across the server and clients. Emby Server Stable: v4.9.3.0 (2026/01/08) Release Notes Beta: v4.10.0.8 (2026/03/27) Release Notes For other platforms, please refer to the download page. Emby for Android TV Google Devices Stable: v2.1.23 (2025/12/27) Beta: v2.1.44 (2026/03/18) Amazon Devices Stable: v2.1.23 (2025/12/27) Beta: v2.1.44 (2026/03/18) Stable Release Notes Beta Release Notes Universal Android app Stable: v3.5.16 (2026/01/26) Beta: v3.5.31 (2026/03/24) Release Notes Download the latest Beta here. Emby for Kodi See here for the latest information. Emby for Roku Stable: v4.1.54 (2026/01/12) Release Notes Beta: v4.1.58 (2026/03/27) Release Notes Emby for Windows (Windows Store for PC & Xbox One) Stable Release Notes Beta release notes Emby for Linux Beta Release Notes Emby for Samsung Smart TV (Orsay) E-series to H-series TVs only Stable: v2.3.1 (2026/01/29) Beta: v2.2.3 Release Notes Emby Theatre for Samsung Smart TV (Tizen & Orsay) Stable: v2.3.4 (2026/03/23) Release Notes Emby Theatre for LG Smart TV Stable: 1.0.50 (2026/01/19) Emby for iOS Stable: v2.2.51 (2026/03/06) Stable Release Notes Beta: v2.2.34 (2025/01/10) Beta Release Notes Emby for Apple TV Stable: v2.0.3 (2025/12/26) Announcement Beta: v2.0.5 (2026/03/05) Release Notes Emby for tvOS (Apple TV) Stable: 2.1.6 (2022/12/23) Release Notes - TBA Beta: 1.5.1 (10) (2021/03/02) Beta Release Notes Emby For MacOS Stable: 2.1.6 (2022/05/09) Details here. I will keep this post up-to-date as much as possible, but please send me a PM about anything I haven't updated, or is missing. Special thanks to @Borskfor supplying a lot of the updated information. Thanks.

Ahh, I see your point. Yes in the UK SD material is mpeg2 generally, while hd material is h2.64

Luke - I went ahead and updated from 4.9.0.35 beta to 4.9.0.38 beta successfully. I did this by (first shutting the server down, and..) renaming the existing server From Emby Server.app to Emby Server 4.9.0.35, and then after downloading the updated server, I renamed that one to Emby Server 4.9.0.38.app before launching it. Everything seems to be working fine.

Nope, as I don't have any issues. But nevertheless, great explanation.

Hi Luke, It works fine. Thanks.

Your incomplete NextPVR logs don't show why your tuner is failing in NextPVR.

感谢.填写587，勾选启用 SSL / TLS，重启后终于测试成功了

Not sure how I missed this, it's exactly what I needed! Please go ahead and mark this request closed, if that's a thing.

I asked for the server logs and he said let him look. and … I can now see trakt in my connected apps! Whatever they did, it worked. appreciate the help. How do I close the thread?

I guessed these HDMI modulator wouldn't be perfect. There isn't a lot you can change on them in terms of settings. As you say they encode an AVC into an RF stream to the Dvb-t standard. However, they encoding would suggest that either they are not quite to Dvb-t spec, or FFMPEG isn't configured optimally? I've actually acquired another device (Edison HDMI modulator) and this seems to behave much better. Things trip up occassionally and require a reboot along the chain, but it appears to be much more stable to view. Recordings don't appear to produce truly compliant streams (what ever I mean by that), but there are a few workarounds I'm working on. For these, my use case is rather specific and only want to be able to record for time shifting so I can view something when I'm travelling.

I guess i had not checked it from the start. I had tried to toggle it on and off rescanning the library a few times but that never worked. I ended up deleting the entire movie library and starting over, that seems to have worked.

I restarted the server, removed and re-added my connect email to my user disabled and re-linked the skill ta-dah! No idea what is different now, but alexa is singing at me so I'm happy nothing to see here, please move along. thanks for your help.

Thanks Luke! It'd be useful to implement syncing of downloaded items

Thank You Luke.. that did the trick! I am not sure why but this time I could navigate to the path w/o problems. Currently, I am running a integrity check on a backup so might had some pull in it. /volume1/SynologyBackup/Packages/Emby now, with that being said, should I still give r/w access to emby to the shared folder? I plan on just using this only for backup and not utilizing this for media. letting hyper backup do the rest. please advise and again Thank You! tvos

I actually fixed the remote issues instead of doing the port forwarding on my NAS I did it on the router and it has been stable

MESSAGE FOR LUKE Hi Luke, big apology from me for my post earlier today. I currently have two active issues and mistakenly thought I was dealing with my other post. So the reply above does not respond to your question by my other post which is here: Sorry about the To answer your question, I agree there were two recordings scheduled. We only scheduled programmes through the main Emby programme guide so I don't understand how this is happened. However, when investigating this issue myself, I did find that the programme appeared twice in the listing of series set to series record, but only once in the list of scheduled recordings. There were others that also appeared twice in the list of series to be recorded, and I have now removed these duplicate items. I would be very grateful if you could look at my second issue, noting my posting from earlier today provides more information about this, and if you look at the logs with that posting, there are error messages in the Emby logs which I think relate to this failed recording that hopefully mean something to you. Apologies again form my mistake. Regards Paul

Ok - this time, I started the script with Emby server running, stopped and restarted Emby, and waited for the kill, which, this time, was "oom-kill". embyserver-memory-20250226a.csv

tvg-shift has been supported for a few years now.

@Carlo Short answer: No. I have never used an alternative start/stop time. In the recording settings all my recordings are set to start 1 min early and stop 2 min late. More details: My setup has always been pretty default. Standard recording start and finish times. I have never deliberately set an advance of more than 1 minute for any recording. SOP for me is to just record what is on the same channel after if I need to extend the recording. Sports is the best example because they can run long. I don't go into the recording setting and adjust start and stop time for extensions and never really have. I just record a certain amount of shows on the same channel following the program. This way I'm not limited to 90 min or any cap. I also remember trying to adjust it after the recording had started and was going to run long and it didn't work (probably expectedly) so I just said, that's not for me. Not mad about it. Just use my own method for reliability My thinking on this is that maybe this isn't global. Maybe there is just a corruption in my server. If no one can reproduce this. It has definitely been happening for a long time I just wasn't really registering it. As I think back now when I would record sports (auto racing) I'm most likely watching live, because sports. Sometimes I'd have to go somewhere and would end up watching the recording. Those recordings, I want to say, also exhibit this issue. There is a carry over of recording that bleeds into the front of the next recording. I never really focused on it. Just fast forward to where I am caught up as you would do. Another assumption I have is that this is buffer that is potentially unavoidable? Is there a buffer setting within emby server? In my WinTV tuner the buffer is set to 30 min.

Its from this test HTTP Header Security Test - HTTP Observatory | MDN

Here is some hints, on how I got it working with NPM. I use awsome.domain.com add_header X-Content-Type-Options "nosniff" always; add_header Referrer-Policy "no-referrer" always; add_header X-Download-Options "noopen" always; add_header X-Frame-Options "SAMEORIGIN" always; add_header X-XSS-Protection "1; mode=block" always; add_header X-Permitted-Cross-Domain-Policies "none" always; add_header X-Robots-Tag "none" always; add_header X-Permitted-Cross-Domain-Policies "master-only" always; add_header Pragma "no-cache" always; add_header Cache-Control "no-store" always; Its not pretty and its not secure in anyway, I only get a B, something about "Content Security Policy (CSP)" that I never could get working in the NPM webui. but it works for me.

I'm actually doing that right now. The positive of using the M3U and XML file from Channels is everything automaps, whereas if I use the M3U from the various sources I mentioned previously and the Fubo guide from Emby, I have to map every single channel. I could do it, but because the Emby guide only gives the ACRONYM for the individual, it's a lot more work to do it that way. Even having the ability to map the guide or channels in alphabet order probably would reduce the effort, but for now, I'll just pay the $85 annual fee to Channels so I can get the M3U and XML with minimal effort.

.srt are so small, you could just email them a copy or place it somewhere online and send them a link. They would need file manager software to place it beside their downloaded copy and whatever player they are using to playback the media also needs to be able to see the .srt files. As long as the files have the same name with dot extensions like .en.srt or .en.default.srt, their local player should recognize the srt file. I do not see an option to download the .srt file from inside a user's emby login on the media page, but maybe there is a way. Hope that helps.

https://m3u4u.com is fairly good for editing a playlist while also sync'ing on going changes.

I would like to shed some light on these NBC outages. I lost NBC reception yesterday (February 18, 2025) and it has not come back as of yet. I have reached out to a tech guy over at NBC and learned why these outages are taking place. Normally they broadcast from the WTC. But they switch over to a backup transmitter at 4 Times square when they need to do maintenance. For me, living out in Suffolk County, their signal goes from 100% to no signal at all when they do this. I experimented and determined that I would need to go through extraordinary means to get their backup signal. It just doesn't pay. After the eight days are up, I just go to their App on my Roku. Not really crazy about that solution. After reading other comments online, it appears that the backup signal is very much inferior to their primary signal. I am tending to think that NBC is not aware of how much this is affecting viewers.

It's amazing the dumb stuff you remember like this. I used to read all the FCC TV change logs up until they stopped logging this during the pandemic. Now the database is all messed up.

This is implemented in the latest Windows app now (2.213.0)

Hi, yes it makes sense. Thanks for the feedback.

Hi, we'll take a look at this. Thanks for reporting.

Passthrough for Dolby truehd only works over HDMI to an external device like an Nvidia shield for example if plugged directly into 1 of the HDMI ports. I've tested this on my own LG TVs.

2027 ? ever the optimist...

I have this setup using port 587 (tick use TLS/SSL) and don't have any issues sending a secure email notification. I have not tested (nor plan to) port 25 - SMTP - but would not recommend that anyway as it's not encrypted, some email services may even reject the request. Port 465 is not supported. System Logging could definately be improved though - as all you get (on a debug log) is a GET log from the 'Server' log class with the term 'Notifications' in it - a seperate 'Notification' Log Class should be made for all Notifications imo. @softworkz

I have the exact same issue, AppleTV 18,4, emby premiere 4.9.0.35 IMG_2306.MOV