text
stringlengths
11
654
[667.60 --> 669.72] which allegedly it will,
[670.06 --> 673.62] we could all of a sudden see basically every display
[673.62 --> 678.00] have this GPU-triggered refreshing enabled on it.
[678.54 --> 679.94] Holy crap.
[680.18 --> 682.34] DisplayPort, you just won.
[682.74 --> 683.96] Like, you just won.
[684.44 --> 686.94] Not only are you ahead of HDMI
[686.94 --> 691.24] because HDMI 2.0 is still not existent,
[691.40 --> 692.86] you can't actually buy anything with it,
[692.92 --> 694.74] and DisplayPort 1.2 has been available forever
[694.74 --> 696.96] and already supports 4K at 60Hz,
[696.96 --> 703.38] now you are going to be in every gaming machine anywhere,
[704.14 --> 705.34] and rightly so.
[705.62 --> 707.56] Like, it's just such a shame
[707.56 --> 710.08] that the Xbox and PlayStation 4
[710.08 --> 712.66] couldn't have something like this.
[712.74 --> 715.92] And I'm not even poking fun at the console gamers right now.
[716.00 --> 718.74] I'm just legitimately sad for them
[718.74 --> 721.38] because I'm sad for the entire industry
[721.38 --> 724.64] because as long as you have to keep trying to design games
[724.64 --> 726.44] to run at like a fixed frame rate,
[726.44 --> 727.10] which you have to
[727.10 --> 728.36] because frame rate fluctuations
[728.36 --> 730.98] will cause either lag or tearing on consoles
[730.98 --> 735.22] where we're stuck with these constant refresh rate monitors.
[735.64 --> 738.44] So as long as the games industry has to account for that,
[738.68 --> 740.66] we can't see them move forward
[740.66 --> 745.08] and push for a little bit more visual quality.
[745.40 --> 747.88] And so what if it dips down to 48 frames per second
[747.88 --> 749.00] or 53 frames per second
[749.00 --> 751.26] because it'll still look really good and really smooth
[751.26 --> 753.14] because that is something that G-Sync
[753.14 --> 759.40] and by extension, I suppose, FreeSync will do very, very well.
[759.68 --> 762.80] So fantastic news right there.
[763.24 --> 766.22] Next up is Android TV.
[766.70 --> 769.18] So The Verge got an exclusive scoop here
[769.18 --> 771.54] where they are showing off
[771.54 --> 774.48] what appears to be the interface of Android TV.
[774.48 --> 777.76] And what I thought was one of the most interesting things
[777.76 --> 779.22] about this article
[779.22 --> 784.92] was how little information it actually seemed to contain.
[785.14 --> 789.08] So we've got quotes from Google saying things like,
[789.14 --> 790.76] here, let me just track this down.
[792.20 --> 796.58] Android TV is an entertainment interface,
[796.58 --> 798.90] not a computing platform.
[798.90 --> 802.30] It's all about finding and enjoying content
[802.30 --> 804.10] with the least amount of friction.
[805.44 --> 807.58] What does that mean?
[810.38 --> 813.28] I mean, we saw Google TV in the past.
[813.38 --> 815.20] I mean, that was a total disaster
[815.20 --> 818.54] just because, I mean, I think they made claims.
[818.58 --> 819.88] This is in The Verge article as well.
[819.96 --> 821.08] So they made claims like
[821.08 --> 824.54] the majority of TVs in 2012 would ship with Google TV.
[824.54 --> 828.20] But what was the difference?
[828.30 --> 830.36] Like, I understand some of the things they're saying here.
[830.42 --> 832.52] So they want the interface to be cinematic,
[833.00 --> 834.46] fun, fluid, and fast.
[834.76 --> 836.98] And they want no more than,
[837.04 --> 838.98] I think they're saying three clicks
[838.98 --> 841.60] in order to go from turning it on
[841.60 --> 843.26] to actually watching content,
[843.34 --> 844.48] which I think is really cool.
[844.96 --> 845.92] But beyond that,
[846.04 --> 848.02] what is the actual difference
[848.02 --> 850.94] between a set-top box that plugs into your TV
[850.94 --> 853.52] that is an entertainment interface
[853.52 --> 856.32] and a set-top box that plugs into your TV
[856.32 --> 858.18] that is a computing platform?
[858.62 --> 860.02] If anything, I would say
[860.02 --> 861.00] if you're going to call something
[861.00 --> 862.12] an entertainment interface,
[862.34 --> 864.44] it would be something more like Chromecast,
[864.56 --> 867.30] where you'll have specific apps developed for it.
[867.32 --> 869.34] But really, it's more about the experience
[869.34 --> 871.56] and not about the Chromecast actually being
[871.56 --> 873.04] a computing platform,
[873.14 --> 874.26] a powerful piece of hardware.
[874.46 --> 876.62] And right now, it's not clear
[876.62 --> 880.88] how Android TV is going to slot into the whole ecosystem
[880.88 --> 883.64] or how Chromecast is going to slot into the whole ecosystem.
[883.92 --> 885.62] But what we do know for now
[885.62 --> 889.02] is that Chromecast will continue to exist.
[889.62 --> 892.30] So screenshots are now showing Google's own apps
[892.30 --> 894.58] like Play Movies and YouTube and Hangouts,
[894.74 --> 897.08] but there are also third-party apps being shown
[897.08 --> 900.80] like Vivo, Netflix, Hulu, Pandora, and games.
[900.80 --> 904.20] So to me, on the surface anyway,
[904.48 --> 905.48] what this looks like
[905.48 --> 908.38] is just developers having to make
[908.38 --> 910.50] multiple different interfaces
[910.50 --> 911.84] for different Google products
[911.84 --> 913.68] because there are plenty of set-top boxes.
[914.34 --> 916.46] Amazon's recent Fire TV
[916.46 --> 918.24] that use Android,
[918.34 --> 920.20] although Amazon is a bad example, I guess,
[920.26 --> 922.18] because it doesn't run stock Android by any stretch.
[922.28 --> 924.12] But there are Android-based players
[924.12 --> 926.30] from even small manufacturers like Pevos.
[926.30 --> 928.60] So you're going to have to have an interface for Android