All Activity

I don't think you're missing anything. Probably related to my post about the spotlight. Works everywhere else but the Samsung app and I'm running the beta. I'm running the latest beta server, but there's nothing in the release mentioning a certain version is required. However, it might help if you posted your TV model number. I made another post about the progress bar which Luke says may be an issue with older models.

Ok this is getting ridiculous. I've been asking since 2023 for you to add TITLOVI.com. It's been almost 4 years now. As a paying customer, I think I'm finally moving away from emby, I'd rather give money to Plex. KODI has titlovi.com as an option since 2014!!! You couldn't add it by now!!?? Opensubtitles sucks, and seems to be the only one still working, barely. I have a feeling for a while that emby was better when I wasn't paying. Just a big disappointment. When you finally add Titlovi.com, let me know. For now, I'm done with emby. At least I'll be saving 9€ a month till then.

Hi. I have created some additional sections on my Emby Home Screen which work and display within a web browser and on my Android app, but these additional sections do not display on the Emby app on my Samsung TV, using the same user profile? Is this by design? Or am I missing something? I'm running server Version 4.10.0.40 TV is running Emby for Samsung 2.2.8

LibreELEC from the Raspberry PI installer. The Pi i use is a small RaspBerry Pi 3, it's fine for the old 1080p TV in my bedroom. I havn't tested it with anything 4K so i can't comment on it being good enough for that. Edit: Also note that i don't think Dolby Vision is possible on the Raspberry Pi in case that's important to you.

Hi, I’ve finished a broad review and update of the Japanese translations across EmbyApps, EmbyClient, and EmbyServer, and uploaded the revised translations through Weblate. From the Japanese localization side, the work is now almost complete. I reviewed untranslated strings, inconsistent terminology, mistranslations, invisible characters, placeholders, and a number of technical strings, and also checked many of the changes against the actual UI where possible. There are only a few points where I would like confirmation from the developers before considering the Japanese translation fully complete: EmbyClient – aspect ratio / video scaling strings There are seven strings related to aspect ratio or video scaling that I could not locate in the current UI, so I could not confirm their actual behavior or the best Japanese wording. Examples include: Fit Window Cover Window Dynamic Fit Dynamic Cover Fill Stretched 1:1 Unscaled For now I left these untranslated rather than guessing from the names alone. Are these strings still used in any current Emby client? If so, could you tell me where they appear, or briefly describe the behavior of each mode? EmbyApps / AlexaCommands I intentionally did not translate the AlexaCommands component. Many of these strings appear to be Alexa utterances, intent phrases, or speech-model data rather than ordinary UI text. I was concerned that translating them like normal application strings could change the command model itself rather than simply localize its presentation. Should AlexaCommands be translated for Japanese at all, or is this component intended to remain in English unless a complete Japanese Alexa language model is supported? EmbyServer Core – source strings that may need confirmation I found a few places where the English source itself appears inconsistent: Subtitle font size The setting description says: Enter a value from 5 to 50 to enforce a specific font size but the validation message says: The font size needs to be a value from 5 to 80 Is the correct maximum 50 or 80? Subtitle margins The setting description says: Enter a value from 1 to 200 to override margins but the validation message says: The margin size needs to be a value from 0 to 200 Is the correct minimum 0 or 1? Closed captions One source string says: Options for EIA-607/EIA-708 captions which are used in ATSC broadcasts... Is EIA-607 intentional here? I wondered whether this was intended to be EIA-608/EIA-708. For the Japanese translation I kept the values and terminology exactly as written in the English source rather than trying to correct them on the translation side. Other than these points, the Japanese localization is essentially complete from my side. Thanks for making the translation resources available through Weblate. It made it possible to review not only the missing translations, but also terminology and consistency across the different Emby components.

Thanks, I'll look into it. I thought Google was locking down all of their devices to disallow side loads though.

Hey yocker, I can deal with a Raspberry pi. What os, software, and remote control are you using?

In that case, you could just get a Google Streamer.

I don't believe this is an app-side issue so moving to server section...

I don't disagree with you but from my experience Dolby Vision is a pain to get working on PCs (specially if using Windows). The Shield for me is just a much simpler product that does and have all i need. For my bedroom TV i just use a cheap raspberry pi i got thrown my way.

Yes, that is almost certainly the case.

Full library scan was done few times since (I don't have RTM enabled but I do full scan on any new media added), latest one done now, just for fun - no change. Refreshed both collections following full library scan - no change. embyserver-63926899676.txt Also, after reading this: went to check it on my test instance (incremental updates from early 4.9 version) - same result as my main server, no change when new content added to library. After that, downloaded and spun vanilla portable 4.10.1.0 instance - again same result, no change. So I don't quite get how did Luke got that result, as I can't reproduce it on either of my servers: main, test or clean portable (all three 4.10.1.0 versions).

Also, a suggestion: when I click on the button to delete a group, I get a popup that asks “Delete this tag group?” It would be better if it used the name of the tag group in that popup, just in case I've accidentally clicked on the wrong group to delete.

hey guys. sorry to resurrect this old thread, but I'm having the exact same problem. When I am at work, I can access Emby fine via using the direct url method, however, it does not recognize my premier key. It will say, "Thank you. Your Emby Premiere key has been updated." however the spinning blue circle never goes away. I can play media fine but cannot access any premier features. Can I just assume that something about my work network is blocking the key confirmation?

Or, perhaps, refreshing the collection itself...?

Of the plugin? I don't get why it asks you to update then.

Hello, First thank you for this add on because at least for me it works really great. . Second I was running into an issue and was not sure if maybe I needed to do something different. The link works great on pc and android phone. But for some reason I cannot make it visible on Android TV. Even if I use Emby for Android rather than the Emby for TV which has limits I cannot seem to make the links visible. Do I need to be doing something different or is just the way it is for television. Thanks again Doug

Observations include 12,122 threads and approximately 3.4 GiB of swapped-out memory, with threads waiting on futexes. This indicates a contention for shared resources or a request backlog, but does not definitively point to database locks or thread pool sleep states.

i m on stable release

VCLibs was already installed. .Net Framework gave me an error with Microsoft.GamingServices and eventually i skipped it as i installed 4.8.1 and Core 8.0.31. Xaml gave me an error that a newer version is already installed. So basicaly the AppRuntime needed and the Emby Theater. So far so good. It is connected with my server with manuall settings.

The red ones are not needed:

Would be really nice to get a Vidaa app

After installing all the below i managed to make it work.

I agree and have been thinking the precise same thing. That said, if you are on a stable release emby shouldn't automatically download a beta. I might need some dedicated testers. But yeah, I might also need to keep minimal updates for later releases, no reason to release something that just improves the speed by let's say a second per detection when that can easily wait for next version. The catalog is the easiest way to share and test something though. While i agree with you i also have to suggest you stick to the stable versions if you want to avoid rapid updates. The betas are not meant for every day deployment.

I have already found the msixbundle. Along with some dependencies VClib, .Net, UI.Xaml. But it is not fair to have all this search and downloads etc. It should be provided directly from the EMBY site in an executable format.