All Activity

Great, thanks for confirming!

Suspect possible file access rights affected after power outage on Linux systems. see: https://unix.stackexchange.com/questions/191682/ubuntu-broken-after-power-failure-how-to-fix

v1.3.0 is out - this one's mostly a response to feedback in this thread, thanks again for pushing on it. Media NFO integration - @crusher11's point a few posts back was right: writing a separate NFO file (different name, different schema than what your scraper already produces) is clutter, and easy to lose track of during renames. So instead, there's now an option to insert markers directly into the NFO your metadata scraper (NfoMetadata plugin, etc.) already writes next to each episode - same file, same schema Cheese's plugin used (<markers><introstart>/<introend>/<creditstart>), nothing extra created. I decompiled Emby's own NfoMetadata plugin to check whether this was actually safe (i.e. does a metadata refresh wipe out markers it doesn't recognize?) before shipping it. Short answer: no - it uses XmlWriter.WriteNode to pass through any element it doesn't own, so a refresh preserves the <markers> node. Tested this live across a full library refresh and confirmed it holds up. It's also read as a fallback on restore if no JSON backup exists for an episode - so if you've got old backups sitting in NFOs from the original commercial plugin, this plugin can restore straight from them, no conversion needed. (There's still a separate migration script in an earlier post here if your setup needs the source/output-folder-remapping flexibility that gives you.) Restore matching bug fixed - found this on a second server with a translated (non-English) library: restore was silently missing episodes because it matched by rebuilding the exact expected filename from the episode's current title, and a scraper's title in your library's display language obviously won't match a filename written in whatever language it was backed up in. Now it matches by TVDB ID + season + episode number only, via a filename glob - title no longer matters. Config simplified - dropped the standalone "write our own separate NFO" option now that the integration above covers that use case properly. Three settings now: JSON backup path, save JSON to media folders, and insert into media NFO. Release (with a prebuilt DLL) and full notes here: https://github.com/guilty57/credits-intros-backup-restore/releases/tag/v1.3.0

My server was working just fine before the power went out yesterday Morning. Ever since the power came back on every time I go to watch something it keeps giving me a blue circle going around and around and keeps saying too many errors and a quit message and I don’t know what is going on. I am using Linux Mint and my media is on an external hard drive

can someone please help with this topic. I do not understand SSH, and would like to install the Xtreme Tuner plugin. Emby is installed via package on my Synology DS423+. If someone could please provide step by step instructions on how to accomplish this I'd greatly appreciate it. I have downloaded the .dll file. Thank you in advance.

I have 2 2023 tvs that just recieved that big one ui update and a 2025 tv and all tvs can only download the 2025 December emby app. How is it that all the big streaming apps are up to date??? Im gonna assume samsung charges for that.

Hey Fam. Recently encountered issues with media playback on LAN. Nothing has changed on the server end, though it is running v.4.9.5.0. I cannot recall when that was installed. Anyway, almost everything buffers or stalls early and often. The funny thing is the same content plays fine via the browser on the server itself. I did some ping tests, thinking this may be network related, but everything checks out - plus other streaming content plays fine on the same TVs. attached embyserver log captured some systemservice errors shortly after restarting, but no errors captured during playing of media. Hardware detection log capture "Message": "Failed to load AMF library dll". There has been zero changes to my hardware. Any ideas would be appreciated. hardware_detection-63920219630.txt embyserver.txt

Does the server log attached show anything? I only sent that Roku debug log because I was able to finally move past the timeout and login screens, one time. at all other times , I can't get even to a place to send roku debug logs because it won't progress to the home screen. it alternates between the error shown above , and this one (attached). this has now persisted for 36+ hours, and again, is only affecting the roku device.

@Eshkroft The next ipdate will have the "Auto" setting working, so that it will use the current Windows language setting.

And this is why we experts have stopped answering questions on this forum. We get responses like this. People embracing their ignorance and their reliance on AI. Have a great day and I hope one day you don't decide to put glue on your pizza or to eat a rock a day because AI told you to when human experts said not to do it, as you'll obviously think the humans are lying and AI is correct. Idiocracy was not supposed to be a documentary.

This issue appears to have resolved itself. From the other thread my basic issue was that fanart wasn't loading from the fanart source because I was getting the following error and appeared to be unable to reset request retry limit: "Cancelling connection to https://assets.fanart.tv/fanart/#WHATEVER#.jpg due to a previous timeout." This was after adding my library for first time setup so I assume I was just being rate limited at the fanart.tv end. This was annoying because this error wasn't coming from fanart.tv (I could navigate to the image URL directly and the image would show) and it appeared to me to be Emby having a retry limit for the request URL to stop flooding requests to the fanart.tv website if it gave a timeout from a previous connection. However, after essentially not using Emby for 7 days while on holiday I've come back to it and now every request seems to be working and as such as a navigate through my library fanart is being populated - so there's no issue to fix any more (other than possibly exposing the timeout period in the error message to say something like: ""Cancelling connection to https://assets.fanart.tv/fanart/#WHATEVER#.jpg due to a previous timeout. Will be able to retry in X seconds" Regardless, the issue can be closed I think.

Could you please specify which version exactly the fix was applied to? 3.5.36 seems to be the latest beta version available on Google Play but it does not address this. I think the behavior changed slightly at some point since a login modal seems to pop up, but pressing the back button clears the modal and still logs me into the admin account with no PIN required. This was over 2 hours after pressing "Home" to background the Emby app and then re-launching it from the home screen. I've reviewed the release notes for subsequent versions but there's no mention of a fix for this anywhere.

2.319 Beta of course

Thanks, I'm hoping that Samsung hurry up and complete the approval of the latest build, but I vaguely remember a few years ago that there was a similar block that went on for months until Luke or one of the developers gave them a push. Hopefully version 2.3.3+ will roll out before 4.10 moves out of beta, as I've buried the One Connect box for my TV so accessing USB ports is not an easy task!

I am using Version 4.10.0.20 beta, with Trakt plugin V 3.8.6. When I click on get PIN a browser window opens with this url: https://trakt.tv/oauth/authorize?response_type=code&client_id=<user_id>&redirect_uri=urn:ietf:wg:oauth:2.0:oob - (I replaced user_id) and I get a blank page. According to what I found :oauth:2.0:oob is obsolete for logging in to Trakt. In other words, I'm locked out from using the Trakt plugin till the plugin is updated.

Yes You can always use the latest on GitHub until Samsung is done reviewing and then switch back.

Yeah I noticed that on the forum post too lol. Install numbers might be one thing, but functionality/client support is another as I've already highlighted. Most other selfhosted FOSS projects don't have to deal with as much client app sprawl as a media server does. Typically at most they need an android & IOS app, so development/support isn't so bad. At the end of the day though I think it's probably better to be humble. Look at what became of Subsonic, Madsonic, Libresonic, Airsonic, Airsonic-Advanced, and the fork of Airsonic-Advanced that was basically being maintained by one guy up until a year ago (along with any of other Subsonic forks I'm forgetting) You have a mix of paid (Subsonic & Madsonic) & FOSS variants that are all basically dead now. It's a shame because IMO the *sonic servers were/are pretty much the best music-centric media servers to exist. The last time I looked into Navidrome it was still missing a bunch of functionality and is pretty much completely tag based. I've been going through the painstaking process of moving my music over to Emby, but it's a chore to say the least as my tags are a mess and I never bothered with fixing tags on the *sonic servers since they worked perfectly fine just off of file/folder structure. Not saying that Emby doesn't, it's just far pickier if you want metadata to be correct and don't want to turn your entire music library into a mess. Sorry for the rant, but my point was that regardless of if it's FOSS or paid software, we're all relying on the whole house of cards to not come crashing down so our stuff still works. There's clear precedent that even successful FOSS or paid projects can stop being developed at any time.

What kind of subtitles, .srt, .ass and so on?

Ok then I guess, that's it or transcode the audio to AAC Stereo. But Transcoding audio should be a task it can handle, most potatoes can do this, without breaking a sweat. Did you see what cpu usage it was using when transcoding audio?

I tried Firefox and Chorme.

I believe so, this is my configuration services: emby: image: emby/embyserver:beta container_name: emby runtime: nvidia restart: unless-stopped environment: - UID=1000 - GID=1000 - GIDLIST=44,993 group_add: - video volumes: - emby_config:/config:rw - emby_medias:/data/medias:rw devices: - /dev/dri:/dev/dri networks: - traefik_public deploy: resources: reservations: devices: - driver: nvidia count: all capabilities: [gpu, video]

@LukeI've got a 2025 S95f and it's stuck on 2.2.8, looks like Samsung are taking their time to approve and release the newer versions. Am I right that the new homescreen features in 4.10 will require 2.3.3 or newer to use?

Problem solved with 2.319.0

I think the best codex for browsers are still. video : H264 Audio : AAC 2.0 Subs : text based like srt. So It might be the AC3 is not supported by your browser. What browser are you using and have you tried with another browser?