text
stringlengths
11
654
[3628.06 --> 3630.16] will allow even 1080p viewers to
[3630.16 --> 3632.32] experience better quality I appreciate
[3632.32 --> 3634.90] that I appreciate that as part of the
[3634.90 --> 3637.66] 4k production workflow we have the
[3637.66 --> 3640.84] flexibility to take a 4k frame that's
[3640.84 --> 3643.90] this big and punch in this small on it
[3643.90 --> 3647.62] and get still a 1080p full HD image so we
[3647.62 --> 3650.08] don't have to necessarily switch lenses if
[3650.08 --> 3651.70] we want to get a close-up that's really
[3651.70 --> 3653.08] cool right so we could just take a bigger
[3653.08 --> 3655.48] image and then punch in in order to do
[3655.48 --> 3657.82] really fantastic close-ups using a digital
[3657.82 --> 3660.76] zoom I appreciate that about it but what
[3660.76 --> 3663.82] I don't really much care for is the fact
[3663.82 --> 3665.38] that it's going to have an impact on
[3665.38 --> 3667.84] bandwidth for Netflix streaming users
[3667.84 --> 3669.64] something that is a concern if you have a
[3669.64 --> 3671.26] provider that limits your bandwidth I
[3671.26 --> 3674.80] don't appreciate that it's already a
[3674.80 --> 3677.66] concern for Netflix to be able to stream
[3677.66 --> 3679.60] 1080p with any reasonable level of
[3679.60 --> 3681.16] quality like I don't know if you guys
[3681.16 --> 3683.20] know this should be a topic for an
[3683.20 --> 3684.82] upcoming fast as possible I don't know if
[3684.82 --> 3687.54] you guys know the mechanisms behind it
[3687.54 --> 3691.30] but there's more to the quality of a video
[3691.30 --> 3693.82] stream than just resolution a lot more I
[3693.82 --> 3696.46] mean I could I could give you guys a video
[3696.46 --> 3702.54] stream that's just 1080 by 1920 black
[3702.54 --> 3705.58] pixels that just refresh and that's not
[3705.58 --> 3708.34] that's not quality that's that's just
[3708.34 --> 3710.42] that's so just because something has a
[3710.42 --> 3711.80] resolution doesn't mean it's a quality
[3711.80 --> 3714.44] video feed so bitrate and color depth
[3714.44 --> 3717.02] which is largely affected by the bit
[3717.02 --> 3719.60] rate of the media actually to me has a
[3719.60 --> 3722.58] very very noticeable impact on the
[3722.58 --> 3724.28] viewing experience and when I'm watching
[3724.28 --> 3728.66] videos on Netflix I just yeah it's
[3728.66 --> 3730.40] really ugly sometimes the way that
[3730.40 --> 3733.14] their dynamic throttling will scale back
[3733.14 --> 3734.42] the bit rate so that you get these
[3734.42 --> 3737.12] blocky chunks of of low color depth and
[3737.12 --> 3739.82] that's a 1080p already so if you were to
[3739.82 --> 3741.56] tell me okay Linus I want you to give
[3741.56 --> 3744.68] up some more color depth so that we can
[3744.68 --> 3746.12] throw more resolution at you that you
[3746.12 --> 3747.98] might not even appreciate from so far
[3747.98 --> 3754.22] away from your TV I'd go and maybe sure
[3754.22 --> 3758.60] no probably not so they're saying right
[3758.60 --> 3761.90] now look guys don't expect a mass roll
[3761.90 --> 3763.58] out of this right off the bat so they're
[3763.58 --> 3765.68] realistic about it and okay and on top of
[3765.68 --> 3767.12] all of this is that it's going to use
[3767.12 --> 3768.38] more bandwidth and Netflix is already
[3768.38 --> 3770.06] having trouble dealing with all the
[3770.06 --> 3772.28] all the service providers to get their
[3772.28 --> 3774.92] service you know actually provided to
[3774.92 --> 3777.02] their customers at a reasonable degree
[3777.02 --> 3778.94] of quality and that sentence didn't
[3778.94 --> 3780.06] actually make any sense but I hope you
[3780.06 --> 3781.46] guys get the point so they're saying
[3781.46 --> 3783.50] don't expect a mass rollout and even by
[3783.50 --> 3785.48] the end of the year the 4k selection
[3785.48 --> 3788.48] will be very small but there you go
[3788.48 --> 3791.90] they've got it so if you were to buy an
[3791.90 --> 3795.92] inexpensive 4k TV from Seiki or check
[3795.92 --> 3797.30] this out this is a review that's coming
[3797.30 --> 3797.60] soon
[3797.60 --> 3801.86] ah an inexpensive 4k monitor from the
[3801.86 --> 3804.26] likes of Samsung so yes guys I have
[3804.26 --> 3807.62] gotten myself the UD 590 from Samsung
[3807.62 --> 3810.44] 4k 28 inch TN monitor available for
[3810.44 --> 3815.12] $700 holy balls then you would be able to
[3815.12 --> 3818.06] map a pixel to every pixel and enjoy that
[3818.06 --> 3820.40] content natively but I'm just not
[3820.40 --> 3822.50] necessarily convinced especially from
[3822.50 --> 3824.36] what I've seen of that monitor so far I
[3824.36 --> 3826.52] did have one open at NCIX today that I
[3826.52 --> 3828.26] was able to check out not convinced that
[3828.26 --> 3829.30] it's really worth it
[3829.30 --> 3833.90] all right DirectX 12 will double Xbox one
[3833.90 --> 3835.52] performance so this was originally
[3835.52 --> 3837.32] posted by top war gamer on the Linus
[3837.32 --> 3838.94] Tech Tips forum thank you very much for
[3838.94 --> 3841.28] posting that and the original article is
[3841.28 --> 3844.58] from bgr.com so they have a game
[3844.58 --> 3846.92] changing update that will double Xbox one
[3846.92 --> 3850.76] performance now my problem with this is
[3850.76 --> 3852.68] comes back to the whole Nvidia
[3852.68 --> 3855.50] discussion earlier where it's are you
[3855.50 --> 3857.66] really going to be providing double the
[3857.66 --> 3859.04] performance or is it going to be like
[3859.04 --> 3860.90] double the performance in one game that
[3860.90 --> 3862.58] was already fairly well optimized anyway
[3862.58 --> 3864.50] and it's not really going to make a
[3864.50 --> 3867.08] difference to most people and other
[3867.08 --> 3868.34] than that is it just going to be a
[3868.34 --> 3872.24] marginal incremental improvement and and
[3872.24 --> 3874.64] I don't know yet there's still a lot of