All Activity

OK so E is empty. The playback errors are related to your F drive. Did the library scan finish after setting these up? Try running another one.

Hello, After updating the application on both TVs and mobile devices, one user somehow lost the email address that was previously bind to the server. However, none of the users (4 in total) are able to connect anymore. The public IP is working, and the port forwarding is configured correctly. When I test the connection locally using the external/public IP, everything works as expected. Before the application update, all users were able to connect without any issues. I also tried reconnecting two users using their PINs and the email addresses I have on file. The application reports "PIN confirmed", but after approximately one minute, it displays the error "Unable to reach server."

Hi, Indeed, it seems that last version of Emby has a problem with TOS7 Since i migrate to TOS7 3-4 days ago, i'm unable to transcode anything. On web browser or in the app. I will try beta version to see if it works or not.

Attached are screenshots of both E and F open in explorer. E is the empty USB I mentioned above, F is the Media Server hard drive where all the movies and shows are stored (The Emby folder in Quick Access is just a local folder where I'm storing things like a few playlist images and such)

Thank you! I hope that anyone who’s had problems with Xnoppo will be able to enjoy their home cinema with this new app

@Trufa2011?

Yes this is a good question.

@CasualChuckHi, can you please show us a specific example using screenshots? Thanks !

Are you sure you enabled theme songs in the emby app?

Hi, what features do you feel are half finished?

Thanks for sharing.

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

Hi there, please attach the Emby server log from when the problem occurred: How to Report a Problem Thanks!

Hi yes, there is room for improvement there. Thanks.

Well what is the original size of your image file?

https://emby.media/community/topic/146539-changelog-emby-server-beta/#findComment-1525789

Hi, does the help text underneath the option help answer this for you?

HI, please try Emby for macOS 2.2.45. Thanks !

Hi @Luke, thanks for trying but unfortunately also version .54 crashes at launch. I can see the black screen with emby logo for less than one second than the app quit. If I double click the home button I can see the app is open but it doesn't work. So nothing changes from previous version .53. Please find a solution

Yes, 4.9.5.0 The log shows the strm being refreshed, but nothing plays. e.g. 2026-06-25 16:04:33.028 Info LibraryMonitor: Joseph LoDuca - Army of Darkness (1993) (\\NAS2\MOVIES\!!SpecialEditions\Army of Darkness (1992) [tmdbid=766]\theme-music\Joseph LoDuca - Army of Darkness (1993).strm) will be refreshed.

Though for some shows, "correct" is a multi-valued thing, and their main choice might simply be different from yours. I guess in some cases alternate orderings can get round that, but of course Emby is behindhand in implementing these. Paul

Yes but if you can show you have the correct data, they have no problem unlocking or editing it.

I love to give this a try.

Recently switched over from Emby for Android TV to Emby for Android and notice the images (movie posters, movie backgrounds) on the main screen and mostly everywhere else is a pretty low resolution so much that the images look kind of blurry. This is more noticeable on my larger tv than a smaller one. Is this normal? I don't see any settings to adjust the quality of the images. I can only find settings to adjust the size and even if make it smaller, it's still not great quality.. just smaller. Running Emby for Android 3.5.36. I took a photo on my tv display but it's hard to tell in a photo vs looking at it directly in person.

Thanks, that explains the current behavior. I understand that entering https:// is currently required for SSL connections, and I can use that as the workaround. That said, I think this could still be improved in the app. In most modern clients, if a user enters a bare hostname like "emby.example.com", the app either tries HTTPS first, follows the HTTP to HTTPS redirect correctly, or at least shows a clear message saying that https:// must be included. Right now the failure is a bit misleading because the app just shows "Access token is invalid or expired", but the actual issue is that the app is not using the correct HTTPS URL/not handling the redirect correctly during login. The proxy logs show that the login request becomes a GET ... AuthenticateByName ... 401 when using the bare hostname, while entering https://emby.example.com produces the correct POST ... AuthenticateByName ... 200. So a checkbox would definitely help, but I think the best behavior would be for the app to either: -default to HTTPS when a normal domain is entered without a scheme -correctly handle HTTP to HTTPS redirects during login -or show a clear validation message together with the checkbox such as "Secure connection is required, use the checkbox and choose the https" or something along those lines That would make the setup much less confusing for users behind reverse proxies or Cloudflare as well as for people without the most technical know-how and the ability to actually troubleshoot these sort of things.