All Activity

Just saw something that I think is worth adding to this conversation. It looks like the dev behind the jellyfin desktop client is breaking off from the main dev team and will continue to develop the client under a different name no longer directly related to the main jellyfin project. From what I saw they plan on coming forward with more information as to why they came to this decision within the next day or so, but it appears to stem from internal conflicts and burnout from what I've read thus far. I've had this opinion for a while now, but Jellyfin's biggest weakness has been their client apps. Their Xbox app went unmaintained for well over a year until fairly recently. Their entire app ecosystem is completely disjointed whether that be first party or third party. There are far too many third party developed client apps that are touted as being the best at this one thing or that other thing. This is less of an issue if you're just hosting a media server solely for yourself, or people only use the web client. When you start inviting friends and family to your server and they want to watch on something other than a browser it becomes a nightmare trying to explain that they should use an app with one name on this platform, a completely different app on that platform, and the actual jellyfin app on this other platform. They've done some interesting things server side (and there are some arguments that can be made that some things might be handled better than emby there), but none of that matters when their app ecosystem is as dysfuntional as it is. I love free/open source software, but sometimes you get what you pay for. I run Jellyfin alongside Emby just to keep up with it. I would pick Jellyfin over Plex any day of the week despite it's issues if for some reason Emby stopped existing or went down too similar of a path as Plex. As long as Emby has an affordable lifetime license you'll never convince me that $0 is better than paying $120 one time (or a couple of times in my case as I have a couple of licenses just because I wanted to) for an overall better and more cohesive experience. IMO most people shouting that Jellyfin is better in every single way than Emby are likely basing their opinion on the price rather than the overall experience or that Jellyfin is open source as the free part is usually the appeal whether they admit it or not. Don't get me wrong, I want to actually see Jellyfin succeed, but it seems like their whole ecosystem takes just as many steps backwards as it does forwards. Emby is just a better overall experience from both the admin and user perspective. Emby on the server-side has progressed fairly well (and not surpisingly still far ahead of Jellyfin on a number of things IMO). Just as importantly the first party app support has been fairly consistently maintained throughout the years. All of my friends/family know to just download the app called "Emby" regardless of what platform they are on. I don't have to go through the explanation as to why they need to switch to this other app or platform because whatever volunteer dev that was working on the project hasn't released an update in over a year and the app is no longer compatible with the new server version. If Emby drops support for a particular app/ecosystem there will at least be a valid argument as to why it's no longer viable from a technical or supportability standpoint. It seems that when you have a dev team that gets paid for the work they do that the project actually has the resources to keep things going fairly smoothly. Who could have ever predicted that?

In case you don't know, in the new(er) app, if you go to fast forward, once its fast forwarding slowly if you click the FF button again and again it gets faster and faster. But I still prefer the old way in the old app where you just hold the button down and it gradually accelerates all by itself.

I don't know my "embyconnect email". I log into emby.media with my standard email address.

8096 per screenshot. Typo

Hello, Tested the next song and it works on single echo device and not the group echo. It seems like it acknowledge the command but doesn't process it. Thanks

Hi, I'm hoping someone can help because I've narrowed this down as much as I can. Environment Emby Server 4.9.5.0 QNAP TS-464 and TS-453D Native QPKG installation (not Docker) Nginx Proxy Manager (latest jc21/nginx-proxy-manager) HTTPS using Let's Encrypt Reverse proxy to Emby on HTTP port 8096 Reverse proxy NPM configuration is very standard: Forward Scheme: HTTP Forward Host: 192.168.x.x Forward Port: 8096 Force SSL: Enabled HTTP/2: Enabled WebSockets: Enabled Cache Assets: Disabled Block Common Exploits: Disabled No custom locations No custom nginx directives Emby Network settings Secure connection mode: Handled by reverse proxy External domain configured Public HTTPS port: 443 Local HTTP port: 8096 Local HTTPS port: 8920 Remote connections enabled UPnP disabled The strange part I have two completely separate Emby servers. Different NAS hardware Different databases Same Emby version Same reverse proxy Both behave identically. Testing results Works Windows browser via reverse proxy Android phone browser via reverse proxy Android phone Emby app via reverse proxy Android TV browser (Edge) via reverse proxy Android TV app via local IP OttoAibox Emby app via local IP Fails Sony Android TV Emby app via reverse proxy OttoAibox Emby app via reverse proxy Both Android TV devices authenticate correctly if I connect directly to: http://192.168.x.x:8096 They fail only when using: https://emby.backup.monitoringcomputers.com.au Emby Connect Emby Connect also fails. The PIN page says: Pin Confirmed. Thank you. but the TV never completes the login. Logs The server receives the authentication request. Immediately afterwards the log shows: GET /emby/Users/authenticatebyname followed by: Access token is invalid or expired. 401 Unauthorized Browser authentication succeeds through the same reverse proxy. Why I think this may be a client issue Everything else works: Browser Android phone app Direct LAN Same reverse proxy Same certificate Only Android TV-style clients fail when connecting through the reverse proxy. Has anyone seen this before? Is there something different about Android TV authentication compared with the Android phone app? Any suggestions would be appreciated.

Not quite sure what you mean pal. The plugin won't be free as you have premium. I'm bound to only allow use of my paid plugins if a user is a premium subscriber but not the other way round. The plugins are $5 each from the catalog or £10 from my website for all 4.

One of the deal breakers for me on the universal android app currently the lack of fast forward/revarse on a remote. I can navigate to the progress bar, but it moves sooo slow and only moves in miliseconds. Also I can't find the option for starting the app with profile selector.

Yes, as shown above, your server has frozen up and quit responding.

With regards to the Referer header, some provides object to Referer abd accept Referrer and vice versa The M3U Tuner plugin has just been updated to allow you to try out the different variants Ensure the m3u tuner plugin is updated to version 1.0.46 or higher and restart the emby server. This version was released today Edit your M3U settings in Live TV setup Try out the different variants by selecting one of the 4 options in the Referer header mode. There are 4 variants: 1. Include both "Referer" and "Referrer" in the header 2. Include "Referer" in the header 3. Include "Referrer" in the header 4,. Do not include any of the two in the header Of course you might also need to specify a different user agent

Yessir it's all working now! Sorry to waste your time, I should have been more thorough.

@AhmedNSane This has now been resolved Ensure the m3u tuner plugin is updated to version 1.0.46 or higher and restart the emby server Edit your M3U settings in Live TV setup There is now an optiin for the "Referer" header giving you 4 variants 1. Include both "Referer" and "Referrer" in the header 2. Include "Referer" in the header 3. Include "Referrer" in the header 4,. Do not include any of the two in the header I believe for your provider, it needs to be set to "Referrer" I will be updating the support article to include screenshots for this

Thanks for the feedback, and I’m glad you like the direction Traxx is taking. Sorting options for albums, especially Date Added and Random, are useful suggestions. DLNA playback is also worth looking into for devices that do not support Google Cast. Tailscale is not supported yet. Traxx currently only accepts the usual private internal IP ranges, while Tailscale uses addresses in the 100.x.x.x range. I will need to adjust that in the app before remote connections through Tailscale can work properly. I’m very busy at the moment, so it may take some time before I have the opportunity to investigate and implement these options. I have added them to the list of things to look into. Thanks again for the suggestions and encouragement.

Did 2 for each of the possibilities i described. First is started on dex screen, second on mobile (but then displayed on dex screen) emby_android_1784322815102.txt emby_android_1784322929512.txt

TYVM! I will test this out on my testing sandbox server today!

I am not sure if you got the right Topic. This is a plugin to create Emby Theme songs and backgrop theme videos that play on each Shows/Movies detail page

More cool ones here https://giphy.com/explore/neon-frame-stickers

Can it add a square box on the outside of all movie posters with something like this?

he restablecido smart hub en la tv, limpiado la cache y dejado quitado de la corriente electrica 30 minutos, he vuelto a instalar la aplicacion desde la tienda de aplicaciones de la tv y sigue saliendo el mismo aviso, Alguna idea?

Thank u.

9096 or 8096?

That is your emby connect email, but that doesn't matter at this point if you can't connect remotely.

OK we'll take a look at it. Thanks.

OK yes that sort of option is certainly possible. Thanks.

Right you need to set the public facing port in emby server for the remote address. Sounds like you've done that now.