Leaderboard
Popular Content
Showing content with the highest reputation on 06/06/25 in Posts
-
Whelp, I am not going to be able to look into this anymore, because I can't recreate the problem now Something must have been screwy in the DB and then getting it to identify fixed it or something?2 points
-
I had playback issues with my LG as well with network lag... The LG only has 10/100 network so go onto Amazon and buy a Cable matters brand of usb to ethernet adapter..around 16 bucks You must disable wifi on your tv before you plug it in with an ethernet cable attached. I am now getting no more lag because the local network is now a gigabit connection. I'm also getting around 350 mbps speed online with a high speed fttp internet connection... Certainly speeds up the foxtel app loading... Another couple of hundred on top of that if your tv has a usb 3.02 points
-
If you want DVP5/HDR10 HDR support in the Emby app, these rules still apply. Your media file needs to include only the listed audio formats and subtitle formats, be properly tagged, and stored inside an mp4 container. If you satisfy those criteria, you can in fact watch HDR content using the Emby app for Apple TV. Could this be better? absolutely. I'm still totally baffled as to why we don't have fMP4 support, and strict(er) transcoding rules for Apple [TV, iPhone, iPad] clients. And, for whatever reason, it seems as though the Emby devs are reluctant to comment on this issue. But you CAN have native player support of HDR content using the Emby App, as long as the media file is compatible. You just have to fully understand that Emby Server will refuse to properly condition the file on your behalf, and not inform you as to why it isn't working. Save your money on infuse; transcode your media (and use the proper container) to support the Apple TV direct play requirements (unless you want dolby atmos support... then you're back to infuse) default 16:21:25.347743-0700 Emby.tvOS -[AVSharedDisplayManager setPreferredDisplayCriteria:forScene:]_block_invoke Requesting display configuration <FBSMutableDisplayConfigurationRequest: 0x302e25810> { refreshRate = 23.98; hdrMode = HDR10; } default 16:21:25.377737-0700 PineBoard Received request to update display mode with reason: "Native mode switching", requested mode: <PBSDisplayMode: 0x30227cea0>{ 3840 x 2160 59.94Hz @2x, 16:9, HDR 10 4:2:2 P3 [non-virtual, non-promoted] }, current mode: <PBSDisplayMode: 0x3022cd680>{ 3840 x 2160 59.94Hz @2x, 16:9, SDR YCbCr 4:4:4 P3 [non-virtual, non-promoted] } default 16:21:26.086779-0700 PineBoard Current mode is now: <PBSDisplayMode: 0x30222c2a0>{ 3840 x 2160 59.94Hz @2x, 16:9, HDR 10 4:2:2 P3 [non-virtual, non-promoted] } for display ID: 506C0000-0000-0000-0D1F-0103807A4478~::~FwB9AwPnAA==2 points
-
Your answer effectively amounts to, 'it will come when it comes'. the current beta updates are minor...there is zero visibility on when 4.9 is no longer beta. There is zero visibility on when TVNext features will be released. If you consider that to 'fully answer' the question, well then, we have different definitions of 'fully answered'.2 points
-
I'd really like to have 2 Factor Authentication added to the login screen. It's just this (optional) extra layer of security to help secure the server (which, especially if people use camera uploads) contains pretty private data. There are for every type of programming language quite a few libraries available, so implementation on a server shouldn't be too hard to realise1 point
-
It is, as moving/renaming items effectively clears the item from the db and re-adds it as new. The only way to preserve Date Added is by saving NFOs next to media, whereupon existing (i.e. original) date added NFO tag will be honored.1 point
-
Yes, that was the intention: So, if you want to dig deeper, you'd have to repeat the process (remove library-delete NFOs-recreate library) with each meta-provider separately and compare the behavior/narrow down the issues, see which provider with which settings work and which one does not - or if that satisfies you, use TMM for any shows that refuse to "appear".1 point
-
Ah, there it is. Sorry, coming from Plex I was accustomed to the icon. Thank you.1 point
-
1 point
-
Doesn't seem to happen any longer as I tried out Trakt again recently. Can mark this as fixed/no longer an issue.1 point
-
There's two transcoding temp entries. One is for the shared buffer, and this does support the size limit. That's what that option applies to. Then there is one for active playback session of that buffer.1 point
-
We are now 15 months into the 4.9 development cycle. The 4.8 development cycle lasted 22 months. When 4.8 was released the Emby team hinted at smaller more frequent releases but only time will tell. There are some key features promised as part of 4.9 that we have yet to see so I suspect it will be some time before a stable 4.9 is released.1 point
-
1 point
-
Kodi & JF addressed the issue by ignoring the HDR10+ metadata from the stream. Alternatively, there are free online / command line tools that can simply strip the HDR10+ metadata from the MKV in seconds, leaving the DV and HDR10 intact that plays without any issues. I've used this solution since the original problem, and have had zero issues. DV plays on a DV capable device and HDR10 plays on a HDR only device. The same tools could also be used to simply remove DV, leaving HDR10/HDR10+ but I have not needed (or tested) those.1 point
-
crap...It's been a long time since 2016 and nothing....It'll probably be in 2100..1 point
-
I have infuse lifetime but I don’t like the design and it doesn’t support live tv and multi user. ive also tried Conflux, vidhub and senplayer with Emby but none of them are 100%. They all trigger hdr and dv though…1 point
-
I didn't know it was time for our ~quarterly revolt. Let me go grab my pitchfork!1 point
-
1 point
-
Come on, Emby team—why is two-factor authentication (2FA) still not implemented? This is a must-have feature, not a luxury. In 2025, it's shocking that a media server platform like Emby still doesn’t support basic security tools like 2FA. Your users have been asking for this for over seven years, and yet there’s been no serious progress or clear communication about it. Security should be a priority, not an afterthought—especially for systems that many of us expose to the public internet. Please take this seriously and let the community know when we can expect 2FA support.1 point
-
1 point
-
It was not improved in either 4.7 or 4.8.1 point
-
Wrong! Channels DVR, Infuse and Plex apps can play Dolby Vision content. I have used all 3 - and in the last month.0 points
