#Emby client tv#
There are some video codec support differences due to the SoC difference between the Shield TV and FireTV models as well. Likewise, h.264 hardware acceleration was limited to 1080p30 (720p60) before on the FireTV (Shield TV supports 2160p60 for both HEVC and h.264). For example, the newly-released iteration of FireTV finally supports HEVC 2160p60, but the prior generation was limited to 2160p30. I am curious, other than HD audio what does the Shield TV support that the FireTV does not?ĭepends on the generation of FireTV. In any case it seems to me that creating a table that actually does a good job could be quite the daunting task and could also be frustrating as almost all the platforms are in constant evolution so it will be like trying to hit a moving target on a car running on a race track using a slingshot while riding a skittish horse over a hundred yards away. Now, having said all that, it might be enough to include a good link to some kind of independent spec.
#Emby client android#
The Android devices also have most of what the Roku has but there is too many that overlap and too many that don't to make it reasonable to list them all. I know that will complicate both the table itself and the creation thereof but I think it needs that kind of info.ĭevices that have additional abilities, like all the apps the Roku has, also needs to be indicated although details of those apps can be omitted. Because of that difference I believe that they should have separate entries in any table of comparisons.įor a comparison to be of maximum value differences in the way the interface presents itself to the user both internal to Emby and external need to be included. I guess Fire TV and its various models does / will come under Android TV ?Īlthough it is Android the parts of Fire TV and Shield TV that are external to Emby are quite different. But I guess a table of feature does help narrow the choices down a bit. For me once you get to the point where a client will do what is needed it all comes down to the aesthetics of the device's interface and the client that runs on it and that cannot be quantified in a table. Of course my preferences are not what everyone wants but it does come from a long time user of many diverse playback devices.Īs far as a table goes it only goes so far. My recommendation to Emby users is to use the Shield TV or the Fire TV as your primary client. I am still exploring options on both the Shield and the Fire to get them even closer to my ideal. That is difficult with the Fire probably due to the Fires tight integration with Amazon. Everything else is either hidden or off the screen. I have managed to get all the suggestions and other "found" clutter off the main page so all I see when I go to the Shield's main screen is Emby and a few other apps that I use to its right. The main reason I like the Shield better than the Fire has to do with the ability to customize the front end. In defense of the Roku it is quite good but, through no fault of the developer, it does not direct play part of my library and I would just as soon not re-encode the ones that are involved. I do not like everything about either one BUT even my dog does not like everything about me.īoth the Shield and the Fire with Emby are good enough for me that I am no longer looking for clients. On Plex both the Shield and the Fire were quite close to unusable for me but with Emby I find both of those quite good. The primary reason for having my PI at all was to have a solid backup player to the Roku on Plex that I actually liked using. I have not, at least yet, set up my PI to use Emby. Rasberry PI (Running Plex media player) - 10%Īfter using Emby for a few weeks that has changed (for Emby) When I was using Plex my clients were in order of preference with aprox percentage of use:
0 kommentar(er)
