All Activity

I´ve reviewed my collection and i´ve around 45 titles in vc1 format that i´ll convert to h265 to avoid issues and save save. Thank you for your support and patiente.

To get a full tv guide using emby is the only / best way to go, other methods will take days so yeah emby is #1 IMO

Some services that sell tv using mac addresses with your ip address they work so good it never glitches but they don't give you a username or a password they just ask you for your ip addy and mac address from your mag box. The thing is in order to add that service to emby which needs an m3u you need to be crafty to make it work and since some of the real good stuff has no m3u and you can't install vlc player on mag boxes because of it being a closed linux OS you need to jump through hoops. The hoop is using tivimate which I'm not a fan of however on android tv or firestick you can install vlc player and set tivimate to open using external player. So I add in the url and mac then after playing a channel I look in vlc player for last links played and grab the link. I tried with emby it works great loads instant but time consuming making a channel list takes hours and it's all manual and sucks but works. I need to do like so #EXTM3U #EXTINF:-1, A&E http://link here to channel #EXTINF:-1, AMC http:// link here to channel works but horrible takes hours and is why I like to see this added in emby to add tv with mac etc instead of needing mag boxes.

Attah boy, keep up the good work M8

Thank you working perfectly

I could just do it the old fashion way I suppose even though I'm no fan of TVH or running stalker portal homemade proxy servers to get tv going on Emby just to get a full epg guide but I will, why not. Uncle Frank.mp4

Anyway back to the original example. This is an edge case due to the cropped resolution so we will have to account for that. Thanks.

Hi. That’s just your quality setting. I would set that back to auto. That’s strange though. I’m surprised it’s not causing a transcode.

Seriously? Do I really have to explain to YOU how that’s connected?

Sorry, but I have no idea what you are talking about nor how it relates to this thread - which concerned display modes not transcoding at all...

@ebr These problems all stem from the fact that you no longer want to integrate DirectPlay. You’re simply sticking stubbornly to your concept, regardless of what users want. Proper quality on Emby is now only possible with Kodi itself. Your app may look nice, but if the basic functionality isn’t there, you can forget all your fancy talk.

@PeteGul Why not install Kodi as a trial, use the EmbyCon or EmbyNextGen add-on for Kodi, and don’t forget to install the Emby Kodi Companion plugin; set everything to DirectPlay, and see for yourself the difference between the app and proper, smooth playback.

Okay, that makes sense. Then it was the "match resolution" setting that was causing this item to switch to 1080. It was due to the cropping of this particular item which fooled our logic into thinking it was 1080. We are addressing that to have more leeway and that should address this case. Thanks.

Ok, here is my follow-up. Stats for nerds says it now plays in 4K, when Shield is set to 4K. But it says 1080p in the settings "quality", add pictures of both. @visproductionMy gear i relatively new, and generally new cables and everything is HDCP 2.2 compatible, I don't see this as a problem. I do think my stuff dances good together. @TeddyknuddelThat's right, nothing is changed on my side. This is a question to find what's going wrong, when everything says it is an 4K movie. Why does that not that movie show in 4K. Should not need to "trick" the system to do so.

Yes. The problem exists in both modes. app_version 26.0.15 (working) TV display mode ON, the details section is selectable. TV display mode OFF, the details section has a selectable "More" link. app_version 26.0.16/17 (broken) TV display mode ON, the details section is not selectable. TV display mode OFF, the details section has no "More" link.

Hi is that TV display mode?

Remote access problems with Emby can be particularly frustrating because everything may work perfectly on the home network while suddenly becoming unreachable from outside. I like troubleshooting guides that approach this systematically—checking the server settings, network configuration, port forwarding, firewall rules, and whether the connection is actually reachable from the internet rather than changing random settings. It’s also a good reminder that reliable remote access depends on several layers working together, much like communication tools such as TextNow APK, where connectivity needs to remain dependable across different networks. Which part of the setup turned out to be the main cause of the remote-access issue?

As of update 26.0.16, the details section on the Details Screens are not selectable using navigation keys or mouse. This happens on all Detail Screens (Actors, Movies, ...). The details in question are highlighted in red. app_version 26.0.15 works correctly. Example Actor: Example Movie:

Hi Luke, Thanks for looking into this. I no longer have the Shield's Emby Server running (I've reverted to my WD My Cloud's own Emby Server instance for stability in the meantime), but I have full netstat output and process data captured live during the incident last night, before I restarted the Shield's Emby Server. Here's everything in detail: Total SMB connections on the NAS at the time of the crash (port 445): netstat -an 2>/dev/null | grep :445 | wc -l Result: 397 Breakdown by source IP: netstat -an 2>/dev/null | grep :445 | awk '{print $5}' | cut -d: -f1 | sort | uniq -c | sort -rn Result: 393 192.168.178.27 1 0.0.0.0 1 (empty/malformed line) 192.168.178.27 is the Shield TV's static local IP — the sole client running Emby Server. So 393 of 397 total SMB connections on the NAS originated from this single device. System state at the time (top -n 1), showing the load and blocked smbd workers: Mem: 1017344K used, 19328K free, 32K shrd, 45728K buff, 134240K cached CPU: 0.0% usr 76.9% sys 0.0% nic 0.0% idle 23.0% io 0.0% irq 0.0% sirq Load average: 443.45 342.40 170.92 7/641 21724 Dozens of smbd worker processes were stuck in uninterruptible sleep (D state), e.g.: 15012 5792 nobody D< 78016 7.5 1 0.0 smbd -D 28608 5792 root D< 77984 7.5 1 0.0 smbd -D 27096 5792 root D< 77984 7.5 1 0.0 smbd -D 16220 5792 root D< 77984 7.5 1 0.0 smbd -D 7304 5792 root D< 77984 7.5 1 0.0 smbd -D 29096 5792 root D< 77984 7.5 1 0.0 smbd -D 7374 5792 root D< 77984 7.5 1 0.0 smbd -D 27912 5792 root D< 77984 7.5 1 0.0 smbd -D 7335 5792 root D< 77984 7.5 1 0.0 smbd -D 7241 5792 root D< 77984 7.5 1 0.0 smbd -D 26611 5792 root D< 77984 7.5 1 0.0 smbd -D 27812 5792 root D< 77984 7.5 1 0.0 smbd -D 8485 5792 root D< 77984 7.5 1 0.0 smbd -D 25262 5792 root D< 77984 7.5 1 0.0 smbd -D 27848 5792 root D< 77984 7.5 1 0.0 smbd -D 16258 5792 root D< 77984 7.5 1 0.0 smbd -D 26505 5792 root D< 77984 7.5 1 0.0 smbd -D 29201 5792 root D< 77984 7.5 1 0.0 smbd -D (This is only a partial list — the full process table had dozens more smbd instances in the same state, all children of the same smbd parent process, PID 5792.) Confirmation that Emby was the cause, not something else on the NAS: I restarted Emby Server on the Shield via its own web dashboard restart function — nothing was touched on the NAS side. Immediately afterward: netstat -an 2>/dev/null | grep :445 | wc -l Result: 0 All 393 connections from the Shield dropped to zero the moment Emby Server restarted, and the NAS's load began recovering shortly after. I did not restart or touch the NAS itself between the "397" measurement and the "0" measurement — only the Emby Server process on the Shield was restarted. Let me know if you need the RAID status (/proc/mdstat, both arrays were healthy/[UU], no rebuild in progress) — I still have those saved from that session. Thanks, Ingmar

I don’t think the thread starter has changed anything about their cables that could be causing these problems! The problem is simply that nothing is being properly tested here before the release is made available to users.

It's finally working for me too! I've received the update on both of my LG TVs. Thank you so much, Emby team, and sorry for the delay; it took far too long.

Apple only, and no Android plans for Atrium. Let me answer the follow-up too, because it's a fair one: I do have a cross-platform app, so why not this one. Atrium is a personal project with two aims — learning technologies I need in my day job, and having an Apple TV player that behaves the way I want one to. The second is Apple-shaped by definition, and the first one was Swift, SwiftUI and the native tvOS player. Android serves neither. The other app, Embeat, is a music player for Android and iOS, and it has three aims of its own: a music player I actually want, a cross-platform app, and a shared Kotlin Multiplatform client — the last two are things I need at work. Same rule, different answer. The aims pick the platform, not the other way round. That's the pattern, really: when I set out to learn something new I build a real app I'll use every day, because that's the only way the awkward parts turn up. Atrium is what came out of learning Apple's stack. An Android version wouldn't be a port — it'd be a third app, in a stack I've already learned elsewhere, serving neither aim.

I too am getting Ear Wax reached the Emby address, but Emby returned HTTP 403 during the server test message. Any assistance is appreciated.

Apple only? are you planning to get this running on android any time?

Are you or have you thought about adding support for adding live tv from mac address like STB stalker portals?