(2015-06-08, 22:25)nickr Wrote: [ -> ]In any event never buy a tech product based on what the developers promise will be available in the future.
While this is true, I'm more trusting of nVidia than the dozen or so nameless (looking at you TronSmart) Taiwan/Chinese Android STB makers.
Is anyone using a different remote with their Shield? If so, what brand? I tried pairing the FTV remote using Efile explorer. It finds it, but won't allow me to pair it. It's funny, because I pushed a couple of the buttons, and it did have an affect on one of the screens. (not really control, mind you, but it made the icons blink)
Fire TV remote should work on it. The FTV remote is really just a Bluetooth keyboard, so there are no special drivers required.
Using Logitech Harmony Hub as BT keyboard (Paired as Windows computer)
(2015-06-08, 21:10)hifiaudio2 Wrote: [ -> ]Update from my Amazon review of the Shield:
Hi,
We currently support hardware decode of VP9
@Koying, can you tell us if Kodi can support both 8-bit and 10-bit VP9 hardware decode via MediaCodec API on Android when the codec is exposed by Nvidia for this Tegra SoC?
And if so then what about VP9 hardware decode on other SoCs that also expose that codec via MediaCodec API or StageFright on Android? Does Kodi already support VP9 in HW?
VP9 is developed by Google and YouTube is owned by Google, and I believe that a VP9 hardware decoder will be a must for playback of YouTube 10-bit VP9 videos in 2160p resolution?
YouTube today encodes encodes all videos in H.264, HEVC, and VP9 for maximum compatibility, with VP9 now standard for playback on Chrome browser via HTML5:
http://www.animafelina.it/test-video-qua...s-youtube/
YouTube encodes 2160p (3840×2160) videos with VP9 codec at a bit rate equal to 10.4 Mbps
YouTube encodes 1440p (2560×1440) videos with VP9 codec at a bit rate equal to 6.522 Mbps
YouTube encodes 1080p (1920×1080) videos with VP9 codec at a bit rate equal to 2.182 Mbps
YouTube encodes 720p (1280×720) videos with VP9 codec at a bit rate equal to 1.378 Mbps
You can download a sample compressed to 2160p at 15 Mbps with Google VP9 encoder here
http://www.reduser.net/forum/showthread....-HD-Sample
FFmpeg features a native 8-bit VP9 decoder, but I don't believe that it support 10-bit or 12-bit VP9, nor is Kodi built with libvpx
http://wiki.webmproject.org/ffmpeg/building-with-libvpx
Software decoding of both 10-bit and 12-bit VP9 can now be achieved via libvpx
https://github.com/webmproject/libvpx/
(2015-06-09, 09:17)RockerC Wrote: [ -> ]@Koying, can you tell us if Kodi can support both 8-bit and 10-bit VP9 hardware decode via MediaCodec API on Android when the codec is exposed by Nvidia for this Tegra SoC?
No idea, someone will just have to try.
I personally doubt youtube would skip hevc to use vp9, but hey...
(2015-06-09, 10:12)Koying Wrote: [ -> ] (2015-06-09, 09:17)RockerC Wrote: [ -> ]@Koying, can you tell us if Kodi can support both 8-bit and 10-bit VP9 hardware decode via MediaCodec API on Android when the codec is exposed by Nvidia for this Tegra SoC?
No idea, someone will just have to try.
I personally doubt youtube would skip hevc to use vp9, but hey...
As I mentioned, Google encodes all videos in H.264, HEVC, and VP9 for maximum compatibility, the stream selected for playback depends on which user agent / web browser is detected:
http://www.animafelina.it/test-video-qua...s-youtube/
But what is interesting with VP9 is that they claim better quality at lower bit-rates, which I assume is why Google encode the VP9 streams at a lower bit-rate than HEVC as standard.
Again, VP9 is primary developed and promoted by Google, and YouTube is owned by Google, so why would they not prefer and promote VP9 before their competition that is HEVC?
Anyway, as VP9 is a royalty-free codec it does not cost Nvidia a dime to enable it, so they did, and they already use it in their YouTube app for 4K videos, question is if Kodi can too...?
(2015-06-09, 10:15)Tinwarble Wrote: [ -> ]Apparently someone on XDA got MPEG-2 and VC1 decoding working on a rooted SATV: http://forum.xda-developers.com/showpost...stcount=47
Based on this... I am very tempted to root and unlock the bootloader, If OTA Updates break because of rooting, I am sure that most updates can/will be available from a third party; but I do not want to tamper with any DRM keys or anything else that will preclude me from using Netflix 4k or other VOD services. Does anybody have a comment about this?
Has anyone else had issues with ES File Manager and accessing via ftp with the Remote Manager interface?
I want to place the advacedsettings.xml & sources.xml files into the correct location. I have installed Kodi via ES and Google Drive, now I am trying to copy accross the two xml files.
I Turn On the remote Manager, and enter the supplied IP and port details into Forklift (ftp app) and it won't connect.
I can switch HDMI input to the Nexus Player, do the same thing and connect straight away.
What does seem odd to me is the IP ES Remote Manger is asking me to access. The static IP on the Shield is 192.168.1.50, in DHCP form it comes through as 192.168.1.7.
When I fire up Remote Manager on ES, it gives me an IP to go to off
ftp://192.168.49.0:3721/.
Every attempt fails. I reset the Shield, same IP request, I switched to WiFi form Gigabit, and it asks for the same IP.
Anyone have any idea?
Can I force ES to chose another IP for the ftp connection? I can't find one.
Hey all, I'm pretty excited about this box, but I'm curious if anyone has managed to get amazon instant video working on it. There are a few posts earlier, where it seems people were trying, but not having any luck. Just curious if that has changed at all.
Also, I found this a post on the android police found that looks promising, if it's still not working:
http://www.androidpolice.com/2015/05/13/...-download/
I'd try it myself, just haven't bought a shield yet.
(2015-06-09, 23:56)ngergely Wrote: [ -> ]Hey all, I'm pretty excited about this box, but I'm curious if anyone has managed to get amazon instant video working on it. There are a few posts earlier, where it seems people were trying, but not having any luck. Just curious if that has changed at all.
Also, I found this a post on the android police found that looks promising, if it's still not working:
http://www.androidpolice.com/2015/05/13/...-download/
I'd try it myself, just haven't bought a shield yet.
It works if you install the Amazon Store app and the mobile Instant Video app.
It's not the same Sony Google TV experience though
(2015-06-09, 04:37)Ned Scott Wrote: [ -> ]Fire TV remote should work on it. The FTV remote is really just a Bluetooth keyboard, so there are no special drivers required.
I tried in the settings section and it wouldn't even detect it. Then I tried in es file explorer and it detected it but then when I clicked on it, it said loading for a while and came back saying Fire tv remote not found. I tried it a number of times while holding down the home button to put the remote in pairing mode. The funny thing is, when i exited es file explorer and pushed the ftv remote buttons, it did have an effect on the icons on the shield screen. Nothing significant though. Someone mentioned that a ftv update may have fixed it so the remote only works with a ftv.
Has anyone got this to work?
(2015-06-09, 17:10)poluxproject Wrote: [ -> ] (2015-06-09, 10:15)Tinwarble Wrote: [ -> ]Apparently someone on XDA got MPEG-2 and VC1 decoding working on a rooted SATV: http://forum.xda-developers.com/showpost...stcount=47
Based on this... I am very tempted to root and unlock the bootloader, If OTA Updates break because of rooting, I am sure that most updates can/will be available from a third party; but I do not want to tamper with any DRM keys or anything else that will preclude me from using Netflix 4k or other VOD services. Does anybody have a comment about this?
Rooting shouldn't effect Netflix since the same version of the app runs on the AFTV and rooting doesn't effect it. However, there are other apps that will probably not work correctly, like Flixster.
But unless you are just in a hurry I wouldn't bother rooting. They are already going to add MPEG-2 in an update this month:
https://forums.geforce.com/default/topic...th-shield/ and there's no telling what else will be added.