All Activity

Sorry that I missed that in your initial reply. what would you suggest as next steps?

Glad you got it working. I have the same phone, great phone. Let me know if you have any suggestions or improvements, or bugs. And thanks for testing!

Well I am leaving for work so I have to get them when I get back home

@Lukeis there any way to give Samsung a nudge on the approval process? Either from your side as the app developer or a way for us to push them on your behalf?

Definitely not related to the 1 app authorization. I have VIP and have for years and have the same issue. Definitely an issue with using an authentication method that Trakt no longer supports.

3.8.6 installed. Logs look much different embyserver(3).txt

Not sure if it's related but according to a Reddit post you can only authorize now 1 app with the free Trakt account. https://www.reddit.com/r/trakt/s/tB2Y1w6TkG

They have partner status and that gives them priority.

Hi, please try the 2.4.3 update. Thanks.

Hi,Wondering which version should I be running on CoreElec 21.3 using a Ugoos AM6B+box with Emby as a Client? Tia

sorry, was away for a bit. But yes, my issue has been resolved with this latest version. Thank you.

Se some of these guides. Showing results for 'synology' in content posted in Tutorials and Guides. - Emby Community

Guess devs will need logs.

I don’t understand what I am post to do with that link you gave me

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.