WEBVTT

00:00:01.680 --> 00:00:08.639
all right guys welcome to the WAN Show we've got our special guest Ryan Shrout

00:00:06.319 --> 00:00:12.880
with us here this week and you may or may not have noticed that he has

00:00:10.240 --> 00:00:19.119
completely taken the place of that guy that I have evidently once and for all

00:00:15.679 --> 00:00:21.520
finally fired finally it's about time

00:00:19.119 --> 00:00:26.240
right i know right he's been with me for like 3 years now it's actually That's

00:00:23.760 --> 00:00:29.359
too long kind of incredible yeah yeah i mean that's that's too long for I I

00:00:27.920 --> 00:00:37.840
should just let everyone in my life know that I've had a relationship with for more than 3 years like wife see you

00:00:33.440 --> 00:00:39.600
siblings see you eventually kids right

00:00:37.840 --> 00:00:43.920
sorry three years that's it that's it yeah yeah my my son's going to make it

00:00:41.680 --> 00:00:51.039
to to three in you know the next sort of seven months or so time to hit the road

00:00:46.559 --> 00:00:52.879
kiddo get a job or we're gone

00:00:51.039 --> 00:00:57.680
all right guys so we've got a bunch of great topics for you we are going to I'm

00:00:56.000 --> 00:01:04.799
assuming Ryan's going to be with me on this but maybe he's going to play devil's advocate for me over here but I

00:01:00.879 --> 00:01:07.280
am planning to lay into Ubisoft over the

00:01:04.799 --> 00:01:12.640
whole 30 FPS is more so yes that's that's the smile I was looking for

00:01:10.000 --> 00:01:16.000
30 FPS so cinematic so we are definitely going to be tackling that we're also

00:01:14.479 --> 00:01:23.119
going to be chatting about NVIDIA's brand new 970M and 980M mobile graphics

00:01:19.680 --> 00:01:25.119
cards that are surprisingly interesting

00:01:23.119 --> 00:01:30.400
i mean usually the mobile graphics card comes out and it's kind of

00:01:27.880 --> 00:01:36.159
like this time around there's actually really something to say hp is splitting

00:01:33.439 --> 00:01:39.759
up into two companies and we've got another really good one here that I'm

00:01:38.000 --> 00:01:44.320
scrolling through this list as fast as I can to find cuz I can't remember what

00:01:41.520 --> 00:01:48.960
the bloody thing was right HTC launches two selfie optimized phones so we'll

00:01:47.280 --> 00:01:52.880
have some chat and we'll definitely do some Twitter interaction on that one

00:01:50.799 --> 00:01:57.360
find out what you guys think of selfie phones but in the meantime here's the

00:01:57.880 --> 00:02:04.560
intro if it ever

00:02:00.920 --> 00:02:06.640
rolls oh there's no audio again i can

00:02:04.560 --> 00:02:09.040
never remember which one has the audio i'll just

00:02:13.640 --> 00:02:22.319
singot you know it's actually it's hard to talk with um with my voice in my ear

00:02:19.520 --> 00:02:25.599
with a slight delay it's impossible to sing

00:02:23.840 --> 00:02:29.360
so you get yourself back in your ear right now when you when you do this yes

00:02:27.599 --> 00:02:33.720
I do hold on let me just uh thank our show sponsors our first sponsor today is

00:02:31.520 --> 00:02:38.560
linda.com visit linda.com/wanshow to actually get a

00:02:35.760 --> 00:02:43.280
pretty super sweet free trial of their excellent courses kind of a funny story

00:02:40.800 --> 00:02:48.160
we had a stream that we did um earlier this week where someone who actually

00:02:45.840 --> 00:02:52.800
founded a potential competitor to some of linda.com services called them out by

00:02:50.640 --> 00:02:56.800
name as an excellent service for learning things whether it's programming

00:02:54.560 --> 00:03:01.599
or digital photography or whatever else the case may be our second sponsor today

00:02:59.680 --> 00:03:07.200
and it helps if I don't lay them over top of each other like that is Phantom

00:03:03.599 --> 00:03:09.840
Glass their little tagline is the last

00:03:07.200 --> 00:03:14.480
screen protector you'll ever need and I totally disagree with that because you

00:03:12.640 --> 00:03:18.400
actually do need different screen protectors if you ever change your phone

00:03:16.959 --> 00:03:21.840
but it is the last screen protector you'll ever need for your current model

00:03:20.000 --> 00:03:25.760
of phone because it's made of Gorilla Glass 3 just like the screen of your

00:03:23.840 --> 00:03:30.200
phone probably is if you've got a good quality phone it's extremely difficult

00:03:27.440 --> 00:03:36.080
to scratch it's olophobic and it uses a fantastic like nano BS thing that they

00:03:34.480 --> 00:03:40.879
got going on there to somehow be completely bubble free very cool stuff

00:03:38.319 --> 00:03:45.840
so I think that's pretty much it for all that me doing nothing but talking

00:03:42.879 --> 00:03:52.239
constantly why don't we jump right into Assassin's Creed dev thinks the industry

00:03:48.959 --> 00:03:55.280
is dropping the 60fps standard this was

00:03:52.239 --> 00:03:56.799
posted on the forum by the crazed child

00:03:55.280 --> 00:04:02.720
and there's actually uh there's a couple good articles there's one from techraar.com there's one from GameSpot

00:04:00.640 --> 00:04:08.000
i'm just going to pop these up here so you guys can have a look while uh Ryan

00:04:05.519 --> 00:04:13.920
gives his thoughts is Is 30 FPS enough is it more cinematic Ryan no that's

00:04:10.159 --> 00:04:16.000
that's pretty much a a crap excuse for

00:04:13.920 --> 00:04:19.440
uh not being able to render at 60 frames per second obviously i mean if you

00:04:17.840 --> 00:04:24.000
really wanted to make it cinematic you just drop it all the way down to 24 frames per second right like if you're

00:04:22.320 --> 00:04:27.840
going to if you're going to claim that's the reason then go ahead and and do it

00:04:25.759 --> 00:04:33.360
all the way damn it Ryan take your take your logic and and go go back to the

00:04:31.120 --> 00:04:37.000
Midwest or M East or wherever it is you live that's pretty close it's pretty

00:04:34.639 --> 00:04:40.880
It's close enough i mean anybody who has actually used a machine that's locked at

00:04:39.440 --> 00:04:45.360
30 and used a machine that's locked at 60 frames per second can easily tell the

00:04:43.280 --> 00:04:51.120
difference like it's that is not a debate really anymore and um to to have

00:04:49.520 --> 00:04:55.520
a developer of a major game kind of come out and say "Oh we don't really think it's important." What what's the exact

00:04:53.840 --> 00:04:59.360
quote here you don't gain that much from 60 frames per second and it doesn't look

00:04:57.600 --> 00:05:05.919
like the real thing it's a it's a bit like The Hobbit movie that's that's

00:05:01.919 --> 00:05:08.080
crazy like that's painful i mean okay

00:05:05.919 --> 00:05:13.039
the the thing about the whole cinematic look argument is one there's motion blur

00:05:11.280 --> 00:05:19.280
okay and this is something that I think a lot of people either don't understand

00:05:15.840 --> 00:05:21.479
or do understand and hope that other

00:05:19.280 --> 00:05:28.000
people don't understand because if you wanted Okay so

00:05:24.960 --> 00:05:30.400
motion blur is a natural effect of the

00:05:28.000 --> 00:05:35.199
iris of a camera opening and closing iris or shutter or what whatever it is

00:05:32.000 --> 00:05:38.560
you want to call it and what happens

00:05:35.199 --> 00:05:40.880
with games is there is no iris there is

00:05:38.560 --> 00:05:47.039
no camera there is no natural motion blur now the thing is if you have enough

00:05:43.520 --> 00:05:49.520
GPU horsepower you can actually add fico

00:05:47.039 --> 00:05:54.080
motion blur after the fact to the game if you really want that cinematic look

00:05:51.840 --> 00:05:57.280
but dropping the frame rate isn't the answer because unless you have motion

00:05:56.000 --> 00:06:01.600
blur you're not getting any of that effect and even if you do have some at a

00:05:59.680 --> 00:06:06.160
lower frame rate you're getting like I said a cheapo after the-act effect not

00:06:04.479 --> 00:06:10.160
proper motion blur that makes it look properly smooth yeah and and you got to

00:06:08.560 --> 00:06:15.680
think like all these TVs and all these displays um are are being built for

00:06:13.199 --> 00:06:20.080
lower persistence you know uh which takes away some of that inherent

00:06:17.360 --> 00:06:23.440
blurring uh effect that would be native with some of these displays and monitors

00:06:22.000 --> 00:06:28.160
right or TVs whatever you happen to be playing it on so um it it just it

00:06:25.840 --> 00:06:34.319
doesn't make any sense to me like the the whole the whole the whole debate of

00:06:30.880 --> 00:06:36.560
why is it running at 900p or or 1600 by

00:06:34.319 --> 00:06:41.199
900 on both consoles and then oh yeah it's also going to run at 30 frames per

00:06:38.400 --> 00:06:45.759
second because of it 60 isn't good for a shooter uh or whatever this bull crap

00:06:43.840 --> 00:06:50.160
they're talking about is it I mean it just doesn't make any sense like every

00:06:47.759 --> 00:06:55.680
everybody who's a PC gamer a PC gamer who's looked at this quote or reads this

00:06:52.280 --> 00:06:57.440
quote they all aim for above 60 and it's

00:06:55.680 --> 00:07:02.400
not because we're all crazy it's because there's actually valid reasons to want

00:06:59.759 --> 00:07:07.919
to run at higher frame rates so I don't know people and the thing is I like this

00:07:05.759 --> 00:07:11.280
game is coming out on the PC it's are they going to lock it at 30 frames per

00:07:09.440 --> 00:07:15.759
second on the PC i bet they don't for a better experience i bet they don't i bet

00:07:13.039 --> 00:07:18.880
if NVIDIA has their say because it's a it's a GameWorks title it will

00:07:17.440 --> 00:07:23.919
definitely not be locked at 30 frames per second can you can you imagine

00:07:21.039 --> 00:07:28.560
NVIDIA putting a Game Works and like way it's meant to be played in front of a 30

00:07:26.000 --> 00:07:32.960
FPS logs title that would be that would that now that would be worth controversy

00:07:30.400 --> 00:07:37.120
and discussion right so you know it's it's limitations of the consoles that's

00:07:34.960 --> 00:07:43.440
why it's going at 30 frames per second so speaking of the Okay speaking of the

00:07:40.880 --> 00:07:48.720
controversy and how I mean you just sound exasperated just talking about

00:07:45.919 --> 00:07:53.039
this topic because we've been around and around and around again why is Lionus

00:07:50.800 --> 00:07:58.440
making me talk about this stupid damn non-debate that has nothing to do with

00:07:55.280 --> 00:08:01.680
reality at all and the answer is because

00:07:58.440 --> 00:08:04.560
Ubisoft keeps on digging why don't they

00:08:01.680 --> 00:08:09.120
just tell their devs to shut the hell up and let this thing kind of settle a

00:08:07.280 --> 00:08:13.520
little bit what are they doing there there are there are plenty of console

00:08:10.560 --> 00:08:16.319
games that are locked at 30 okay and there are reasons for it because they

00:08:14.879 --> 00:08:20.879
don't want to drop visual fidelity in order to get to 60 frames per second and

00:08:18.560 --> 00:08:23.680
on a TV and on a console where you're kind of you're you know you don't want

00:08:22.080 --> 00:08:26.800
to have VSYNC issues you either have to run at 30 or you have to run at 60 and

00:08:25.199 --> 00:08:30.879
anything in between that is a really big problem so there there are games that

00:08:28.960 --> 00:08:34.320
run at 30 and it's fine that they're not great experiences but they also don't

00:08:32.800 --> 00:08:40.640
come out and say "Well 30 is really what we targeted." Because it's not nobody

00:08:36.719 --> 00:08:43.360
targets 30 right no it's absolutely

00:08:40.640 --> 00:08:50.320
absolutely ridiculous um people are telling me that the audio might be out

00:08:45.279 --> 00:08:52.160
of sync which is very very strange um oh

00:08:50.320 --> 00:08:57.680
no I've got other people saying it's just fine so I think it might be a uh

00:08:55.440 --> 00:09:01.200
yeah I think it might be a bit of an issue apparently there's a very slight

00:08:59.279 --> 00:09:04.399
delay on source so you guys might want to turn yourselves down to uh to

00:09:03.200 --> 00:09:10.399
something else if you're having a little bit of trouble so if it's just me let me

00:09:08.080 --> 00:09:13.680
know no I've got a lot of people do about it but got a lot of people saying

00:09:11.920 --> 00:09:17.760
it's fine uh so I'm not going to not going to can the stream now all right so

00:09:16.160 --> 00:09:23.120
I guess I I'll just see if there's anything else here that we didn't mention like yes I'm extremely

00:09:20.720 --> 00:09:30.320
disappointed that the the upcoming Assassin's Creed is going to run at 900p

00:09:26.240 --> 00:09:34.640
although 900p I find is less of an issue

00:09:30.320 --> 00:09:36.160
for me than 30 FPS because frankly I

00:09:34.640 --> 00:09:41.680
didn't notice that much of a difference with I think it was Battlefield 4 no no

00:09:40.240 --> 00:09:47.760
I think it was the last Assassin's Creed that launched at 900p on PS4 then got a

00:09:44.560 --> 00:09:49.200
patch almost immediately to 1080p um

00:09:47.760 --> 00:09:54.560
didn't really notice the difference compared to 720p but 30 FPS really is

00:09:51.839 --> 00:10:03.600
very noticeable and Ubisoft needs to just stop talking immediately about

00:09:58.839 --> 00:10:06.080
this um on on on that note uh the Halo 2

00:10:03.600 --> 00:10:13.680
Anniversary Edition campaign also will not be running in 1080p uh it's going to

00:10:08.480 --> 00:10:16.000
run at 1328x 1080 60fps though Ryan

00:10:13.680 --> 00:10:21.279
given that the technological constraints here are that they appear to have to run

00:10:18.160 --> 00:10:23.200
both game or both sound and physics

00:10:21.279 --> 00:10:27.200
engines simultaneously um do you think this is an okay

00:10:24.560 --> 00:10:33.160
compromise killing some horizontal resolution for the sake of 60 FPS so

00:10:31.120 --> 00:10:39.360
they're they're taking away horizontal resolution um I'd like to see what that

00:10:36.640 --> 00:10:45.200
looks like visually I guess how how much of a of a of a theater effect are you

00:10:41.519 --> 00:10:47.839
getting on either side i mean I don't

00:10:45.200 --> 00:10:52.399
know probably i mean so this is the Halo 2

00:10:48.600 --> 00:10:54.959
anniversary yeah I don't know i think

00:10:52.399 --> 00:10:57.600
maybe you give the consumer an option um so they're rendering both in the

00:10:56.320 --> 00:11:02.240
background so you can do what they did with the first one which where you have that one button push to swap between

00:11:00.560 --> 00:11:07.279
them right which was a really cool effect but if it's if it's accounting

00:11:05.279 --> 00:11:12.079
for that performance issue then I'd rather just say "Hey don't bother

00:11:09.040 --> 00:11:14.000
rendering the other physics other

00:11:12.079 --> 00:11:19.040
graphics other audio in the background just let me actually run at 19 by10."

00:11:16.800 --> 00:11:24.320
Because I mean it's kind of embarrassing that the Xbox One won't be able to run

00:11:20.720 --> 00:11:26.000
Halo 2 at 1080p uh regardless of what

00:11:24.320 --> 00:11:32.160
the reason is you you would think they would be able to get that full resolution out of that so you you would

00:11:29.120 --> 00:11:35.120
think that wouldn't you

00:11:32.160 --> 00:11:39.120
silly Ryan Trout i mean here I am looking at things like graphics

00:11:36.800 --> 00:11:42.959
performance and gigaflops and and realizing that hey you've maybe you made

00:11:40.880 --> 00:11:47.920
the wrong decisions on these consoles as it turns out maybe you should have spent

00:11:45.360 --> 00:11:52.560
a little bit more money on hardware and you know I've got to wonder if they

00:11:50.640 --> 00:11:55.839
spent less money on hardware because they knew it was going to be a short

00:11:54.079 --> 00:11:59.600
life cycle or if we're going to end up with a short life cycle because they

00:11:57.920 --> 00:12:02.880
realized after the fact that they didn't spend enough money on hardware and then

00:12:01.279 --> 00:12:07.680
the truly baffling thing about it is that Microsoft and Sony at exactly the

00:12:05.120 --> 00:12:11.920
same time spent not enough money on hardware in pretty much exactly the same

00:12:09.440 --> 00:12:15.560
way yep i guess that's all there is to say isn't

00:12:13.120 --> 00:12:21.200
there yeah i mean it's it's it's they both did it and and you know

00:12:18.720 --> 00:12:25.519
you can't blame AMD AMD just built what they asked for right but they could have

00:12:23.600 --> 00:12:30.959
asked for more hardware both companies so yeah um I think I had something else

00:12:28.720 --> 00:12:34.399
to say about that but I guess that's uh I guess that's pretty much all there is

00:12:32.240 --> 00:12:40.720
to it i mean one thing that they said was that they were running at 720p and

00:12:37.120 --> 00:12:42.639
everything was fine 720ps 60 FPS uh they

00:12:40.720 --> 00:12:49.519
wanted to push it further so you know they they managed to get to 1328x 1080

00:12:46.079 --> 00:12:51.680
but would you would you rather than

00:12:49.519 --> 00:12:57.120
running an upscaled resolution be given the option to run a native resolution

00:12:54.079 --> 00:13:00.079
even if it's a lower one

00:12:57.120 --> 00:13:05.839
uh yeah I think so i I I'm curious how you upscale 1328 by 1080 like I don't

00:13:04.240 --> 00:13:11.680
like I don't really understand how you could how you would able be able to do

00:13:07.839 --> 00:13:13.040
that um you know algorithmically I guess

00:13:11.680 --> 00:13:17.920
because you're you're simply just cutting off sides of the of this of the

00:13:15.600 --> 00:13:23.839
window right so if they are rendering at 1328 by 852 or something odd like that

00:13:21.839 --> 00:13:26.880
that was of the same aspect ratio then I might believe that they'd be able to

00:13:24.959 --> 00:13:31.440
upscale it well as it is now I just I feel like they're just going to have black bars on the side but surely you

00:13:29.040 --> 00:13:35.040
wouldn't do that that's not what they're doing they were really clear about that

00:13:33.120 --> 00:13:39.519
it will definitely be some kind of an upscaling

00:13:36.959 --> 00:13:43.040
huh whatever that ends up looking like hope they're not just zooming in or

00:13:41.120 --> 00:13:48.000
something either i don't know it might be worthwhile to do a um like actually

00:13:46.079 --> 00:13:52.079
it might be worthwhile to to to check out this game do some do some capture of

00:13:49.920 --> 00:13:55.519
it and and have a look at it i mean it'd be convenient if we actually got a PC

00:13:54.240 --> 00:13:59.680
version of the game so that we could really compare it against something meaningful but uh weren't there rumors

00:13:58.320 --> 00:14:03.760
that that was going to happen wasn't there rumors i don't think there's

00:14:01.519 --> 00:14:07.920
anything confirmed yet but Twitch chat is pretty great about uh correcting me

00:14:06.320 --> 00:14:11.600
about these things if I ever get anything I get anything wrong the chat

00:14:10.240 --> 00:14:15.920
rooms are great for that aren't they yeah they really are um speaking of the

00:14:14.000 --> 00:14:20.079
chat they've been giving me a really hard time about launching right into the

00:14:18.000 --> 00:14:24.320
show and not explaining who the hell you are and not explaining where the hell

00:14:21.920 --> 00:14:30.079
Luke is so I'll do both of those things guys luke has taken his first decent

00:14:27.920 --> 00:14:35.279
vacation pretty much since he started working with me so he and I went over to

00:14:32.639 --> 00:14:42.720
Germany i was actually there and back in just over 4 days worth of hours um but

00:14:39.839 --> 00:14:46.240
Luke and Brandon both uh decided to stick around so we toured the Cherry

00:14:44.800 --> 00:14:50.079
Tour you know the guys that make mechanical keyboard switches and we

00:14:48.079 --> 00:14:54.720
toured the Sennheiser did I say toured the Cherry Tour factory and we toured

00:14:52.480 --> 00:14:59.839
the Sennheiser factory as well we actually did Oh man we got a really

00:14:56.800 --> 00:15:02.720
great opportunity to uh to film the

00:14:59.839 --> 00:15:07.680
assembly process station by station of the HD800 headphones and Brandon got

00:15:06.000 --> 00:15:13.600
some amazing footage of it we are going to bring that to you guys everything

00:15:09.600 --> 00:15:16.079
from just stamping out diaphragms all

00:15:13.600 --> 00:15:21.440
the way to putting it onto artificial ears and then like an artificial head

00:15:19.040 --> 00:15:26.079
going on a track into a into a noise isolated chamber where it t Yeah no it's

00:15:24.399 --> 00:15:31.279
freaking amazing where they take they test every single unit and then record

00:15:28.240 --> 00:15:32.320
the the um the response curve really

00:15:31.279 --> 00:15:36.639
really cool we're going to bring all that content to you guys but I jetted

00:15:34.480 --> 00:15:40.079
back here and Luke is sticking around in Germany for a week and a half and

00:15:38.160 --> 00:15:45.760
Brandon's with him for a week as well so I am on my own for a couple weeks worth

00:15:43.120 --> 00:15:50.079
of WAN shows so I that leads us to this poor substitute for Luke this is Ryan

00:15:48.160 --> 00:15:54.000
Trout from PC Perspective maybe you want to introduce yourself here because I'm

00:15:51.920 --> 00:15:59.519
clearly not doing a great job the poor sub uh the poor substitute is uh owner

00:15:56.959 --> 00:16:04.560
operator at PC perspective pcpurro.com and basically I review PC hardware for a

00:16:01.839 --> 00:16:10.480
living and I have for the last god 15 years oh god competitor get rid of him

00:16:07.040 --> 00:16:12.480
yeah click hang up hang up hang up uh so

00:16:10.480 --> 00:16:15.880
we the website has been around forever we used to cover just AMD hardware for

00:16:14.720 --> 00:16:19.759
until like 2004ish or something yeah we were

00:16:17.920 --> 00:16:23.519
AMDMBB.com uh focused on like AMD processors and

00:16:21.600 --> 00:16:28.240
motherboards uh and then I didn't even know that that's before my time i always

00:16:25.600 --> 00:16:31.360
knew you as PC PC Perspective yeah 2004 we launched as PC Perspective basically

00:16:29.839 --> 00:16:36.800
I graduated college and I said "All right if I'm going to actually make this a job let's let's try to make this a

00:16:34.560 --> 00:16:42.240
job." So I've been doing that since then and uh we've got a good team of people

00:16:38.880 --> 00:16:44.480
that that do good work and uh I'm

00:16:42.240 --> 00:16:50.480
practically family with Lionus now i mean we have we've hula hooped together

00:16:46.639 --> 00:16:52.560
and uh uh also done the limbo together

00:16:50.480 --> 00:16:59.040
so it's it's like a bonding thing that we did so um that's what I do i we test

00:16:56.240 --> 00:17:04.319
hardware graphics cards processors SSDs all that random crap

00:17:01.519 --> 00:17:07.600
so yeah i mean I guess the the thing the way that I would I I made that joke

00:17:05.919 --> 00:17:12.559
about us being competitors before we're not really i mean Ryan has a podcast i

00:17:09.839 --> 00:17:17.039
have a podcast uh Ryan makes videos i make videos okay hold on a second here

00:17:15.360 --> 00:17:21.520
no okay the main difference is that Ryan's going to get more nuts and bolts

00:17:19.360 --> 00:17:26.720
into if you actually want to know how the SM within an NVIDIA GPU work and how

00:17:24.959 --> 00:17:30.160
that impacts the way that it's going to perform in this game versus that game or

00:17:28.640 --> 00:17:34.320
with this setting dialed up versus that setting up ryan gets really nitty-gritty

00:17:32.640 --> 00:17:41.039
into the details with those kinds of technologies whereas I see ourselves as

00:17:37.280 --> 00:17:43.039
more of a a general overview style of of

00:17:41.039 --> 00:17:46.880
of content so it's just different strokes for different folks and the one

00:17:45.280 --> 00:17:53.039
thing that we definitely know is that stroking is good so let's

00:17:50.679 --> 00:17:57.919
go yeah you pretend you don't know what I'm talking about over there i got a

00:17:55.039 --> 00:18:02.799
monkey so speaking of getting into nuts and bolts this was originally posted on

00:17:59.840 --> 00:18:06.559
the Linus Tech Tips forum by WTO 165 thanks WTO you get a shout out guys make

00:18:05.200 --> 00:18:11.679
sure you're posting all the latest awesome news in the Linus Tech Tips forum after of course searching to make

00:18:09.840 --> 00:18:15.919
sure no one's already posted it uh cuz you will get shoutouts on the show and

00:18:14.240 --> 00:18:19.360
uh there are articles all over the place about this of course PC perspective have

00:18:18.160 --> 00:18:25.520
you got you you guys have covered them i'm sorry I haven't I've been traveling i haven't looked at your site for which

00:18:23.360 --> 00:18:28.320
this this MSI graphics do you have one i I think I I

00:18:27.360 --> 00:18:34.320
think I have the one that they're talking about here is this Oh no uh sorry i jumped to the next topic 980m

00:18:32.640 --> 00:18:39.200
and 970M oh yeah yeah yeah i actually have one of those in here too okay see

00:18:36.799 --> 00:18:45.840
awesome which one's that oh you got the Oh that's the MSI GT72 i don't have one

00:18:42.559 --> 00:18:49.520
of those i've got an Aoris X7 Pro and

00:18:45.840 --> 00:18:52.160
then I've got the G751 from ASUS yep so

00:18:49.520 --> 00:18:57.840
um the X7 Pro is one impressive piece of machinery dual 970M and SLI

00:18:55.679 --> 00:19:02.320
nice nice this I mean this is kind of the more traditional single GPU variant

00:19:00.080 --> 00:19:07.120
of it uh it's actually it's a big machine it's a 17.3 in machine but it's

00:19:05.360 --> 00:19:12.000
it's not very heavy like you can tell it's not overly bogged down by heat

00:19:09.360 --> 00:19:16.799
sinks yeah that's the one MSI is using the um the magnesium alloy shell on

00:19:15.039 --> 00:19:20.880
right okay yeah I think I think it is yeah we just got it in a couple days ago

00:19:18.720 --> 00:19:26.960
so um but it's it's been pretty impressive performance-wise so let's

00:19:23.039 --> 00:19:29.039
talk about it so GTX 980M and 970M

00:19:26.960 --> 00:19:34.640
NVIDIA is touting them they had this wonderful graph at the editor's day and

00:19:31.280 --> 00:19:37.760
NVIDIA is touting them as the closest

00:19:34.640 --> 00:19:40.520
mobile variants to their equivalent

00:19:37.760 --> 00:19:44.559
desktop variants ever

00:19:42.120 --> 00:19:49.520
and would you say from your testing that that is a valid statement from NVIDIA uh

00:19:47.200 --> 00:19:55.600
I think it is i I I think that graphic they showed is maybe uh a little bit

00:19:52.320 --> 00:19:57.520
skewed just because Is it ever not well

00:19:55.600 --> 00:20:00.799
exactly but it's a little bit closer together on that graph than it actually

00:19:59.280 --> 00:20:05.120
turns out to be i mean don't get me wrong the 980M is still an awesome part

00:20:03.280 --> 00:20:08.480
uh especially considering you know its power efficiency and that's what makes

00:20:06.400 --> 00:20:13.440
it great in laptops but it's I mean there's still definitely a gap like the

00:20:10.799 --> 00:20:19.360
the GTX 970 desktop is faster than the GTX 980M mobile right so of course that

00:20:16.880 --> 00:20:24.640
means that there's going to be a 15 20 25% gap between the 980M and the 980

00:20:22.559 --> 00:20:29.840
itself so I mean it's still it's still really good but it's not it's you know

00:20:27.840 --> 00:20:34.559
their naming scheme still throws it off some that and I think part of the issue

00:20:31.919 --> 00:20:38.799
for NVIDIA is that whenever they compare anything they're going to be using a

00:20:36.480 --> 00:20:46.400
reference 970M which is a part that doesn't exist so the only 970 that I was

00:20:42.960 --> 00:20:49.600
or sorry 970M uh a reference 970 this is

00:20:46.400 --> 00:20:51.600
so confusing the only 970s that I'm

00:20:49.600 --> 00:20:55.840
aware of are aftermarket ones most of which are overclocked and the way that

00:20:53.120 --> 00:20:59.760
GPU Boost 2.0 works is even if you were to underclock your card to a reference

00:20:57.919 --> 00:21:03.120
clock speed that card might still overclock itself to something that a

00:21:01.280 --> 00:21:08.240
reference card wouldn't have achieved so it makes comparing 970M which could also

00:21:06.400 --> 00:21:12.000
be a non-reference design because to my knowledge board partners or notebook

00:21:10.320 --> 00:21:16.000
partners are able to kind of play around with with settings there so comparing

00:21:14.799 --> 00:21:20.400
one thing that's non-reference to another thing that's non-reference compared to NVIDIA's graph which is

00:21:19.039 --> 00:21:23.679
reference to reference I mean who even knows what's going on yeah it's it's

00:21:22.400 --> 00:21:30.000
interesting because if you if you looked through all that information on the mobile parts they never give you a TDP

00:21:27.440 --> 00:21:33.880
uh for the GPUs and the reason is it's not that they don't have a number uh it

00:21:32.799 --> 00:21:40.799
is that each notebook like the GT72 or the

00:21:38.640 --> 00:21:45.600
ASUS machine that you have like they're allowed to tweak those clock speeds

00:21:44.000 --> 00:21:49.440
individually to make sure they are within the thermal envelope of whatever

00:21:47.760 --> 00:21:53.200
uh you know heat sink and fan combination they're using in the laptop

00:21:50.880 --> 00:21:58.320
so there there's really not a reference clock speed for the mobile parts like

00:21:55.679 --> 00:22:02.640
there is on the desktop parts um because it is kind of a casebyase basis so yeah

00:22:01.360 --> 00:22:06.480
I think you'll see different clocks throughout the notebooks i mean that was

00:22:04.880 --> 00:22:10.880
the other thing I noticed was that they only specify a base clock they actually

00:22:09.200 --> 00:22:15.280
don't have a boost clock in the spec it just says base clock is this plus quote

00:22:13.200 --> 00:22:18.799
unquote boost mhm and that's all we really know about it yeah you got to

00:22:16.640 --> 00:22:23.280
open up something like GPUZ or something that will give you what it is what the

00:22:21.039 --> 00:22:27.600
uh the firmware of the GPU is actually set at for its typical boost but again

00:22:25.760 --> 00:22:31.760
you've been doing this long enough the typical boost does not really tell you

00:22:29.919 --> 00:22:36.240
what the boost clock is going to be at anyway right it just gives you some

00:22:33.200 --> 00:22:38.080
minimum that it won't go below unless of

00:22:36.240 --> 00:22:42.960
special cases right it's all very complicated yeah unless of special cases

00:22:40.480 --> 00:22:46.640
in which case it will go below yeah and then we don't know really anything of

00:22:44.799 --> 00:22:50.320
what's going on unfortunately and then we have that thing called the base clock

00:22:48.000 --> 00:22:54.240
so that's actually what we mean so um but I I have to say so we we ran some we

00:22:52.960 --> 00:23:00.880
ran a bunch of benchmarks the article is not up yet on the website but the GT72

00:22:56.559 --> 00:23:02.960
with that 980M um is at the wall i think

00:23:00.880 --> 00:23:07.200
we're we're pulling like 200 to 210 watts with the AC plugged in uh and

00:23:06.000 --> 00:23:13.360
that's that's not a lot of power considering using a quad core hyperthreaded part you got a 980M

00:23:10.480 --> 00:23:17.679
running at probably 1.1 gigahertz at its typical type of clock speed that it's

00:23:15.200 --> 00:23:22.640
running at and it's got a 1080p screen and there's basically no game that maybe

00:23:20.880 --> 00:23:27.039
except for Crisis 3 at its top settings that can really make it you know work

00:23:24.720 --> 00:23:31.600
overboard to to render at 1080p so it's it's actually pretty impressive and the

00:23:28.799 --> 00:23:35.360
fans don't get super loud and uh it's it's a pretty good mobile gaming

00:23:33.200 --> 00:23:39.120
experience I think so far now speaking of the mobile gaming experiences uh

00:23:37.280 --> 00:23:45.600
experience is this a bit of a strange trend to you i've noticed that for all

00:23:42.480 --> 00:23:48.679
of the sudden we were seeing 3K and 4K

00:23:45.600 --> 00:23:52.799
notebook displays and we were getting

00:23:48.679 --> 00:23:54.799
860M or in some cases 870M in the in the

00:23:52.799 --> 00:24:00.400
case of stuff like the ASX 3 or the Razer Blade and then all of a sudden we

00:23:57.840 --> 00:24:06.240
get these super powerful GPUs in the 970M and the 980M that could really

00:24:02.880 --> 00:24:08.480
drive a 3K display properly and it seems

00:24:06.240 --> 00:24:12.159
like everyone all at the same time met in a back room somewhere and decided to

00:24:10.240 --> 00:24:17.919
bail and go back to 1080p what the heck happened i I think the reality is is

00:24:15.760 --> 00:24:24.080
neither the 980M or the 970M could really push a 3K display okay not in

00:24:20.799 --> 00:24:26.640
Crisis 3 but Shadow of Mordor high

00:24:24.080 --> 00:24:30.400
details maybe not max maybe maybe you'd be able to and I think that's what you

00:24:28.880 --> 00:24:34.960
know from from NVIDIA's point of view they want to be able to say max out

00:24:32.559 --> 00:24:40.000
everything on this laptop right and so 1080p is the right resolution for that

00:24:36.880 --> 00:24:42.960
and again you're talking about a 17inch

00:24:40.000 --> 00:24:46.320
screen that is a little bit further away from you maybe uh and so 1080p just kind

00:24:45.120 --> 00:24:50.480
of makes sense now you could hook it up to an external display which we did um

00:24:49.039 --> 00:24:55.679
you could this has DisplayPort connections on it we hooked up uh that

00:24:52.400 --> 00:24:57.520
ASUS swift G-Sync monitor and it works

00:24:55.679 --> 00:25:01.600
Right so if you want to use an external display for higher resolutions you can

00:24:59.600 --> 00:25:07.600
um but I just I don't know i I didn't see the benefit of those ultra high

00:25:04.720 --> 00:25:11.600
resolution notebooks really because in Windows it's not very useful because you

00:25:10.000 --> 00:25:14.640
you've got to turn up the scaling to a certain amount so that you pick so that

00:25:13.120 --> 00:25:21.039
your icons and your text is actually readable and then in games um you know

00:25:18.480 --> 00:25:28.799
there's when your native resolution is 25 by 14 or or 32 by 16 or whatever it

00:25:26.159 --> 00:25:32.000
was whatever that one works to and you downscale it to 1080p it's not going to

00:25:30.559 --> 00:25:36.799
look as sharp as if it were running on a native 1080p screen so I'm sure we'll

00:25:34.480 --> 00:25:41.360
see those and something like a machine that has 2980s in it would be kind of

00:25:38.960 --> 00:25:46.159
the perfect candidate for that yeah a two and a half two and a halfK display

00:25:43.200 --> 00:25:50.720
with two 980ms is probably an excellent sweet spot i mean I guess the thing that

00:25:48.720 --> 00:25:54.240
it just baffles me that we get these underpowered notebooks with these high

00:25:52.400 --> 00:25:58.080
resolution displays and then we get these overpowered notebooks with

00:25:56.000 --> 00:26:02.159
probably the right display even though really that's not NVIDIA's messaging

00:25:59.679 --> 00:26:09.919
about it at all i mean their slide deck is that 900 series M is suitable for

00:26:06.520 --> 00:26:11.919
1440p but I I think that the actual

00:26:09.919 --> 00:26:16.080
designs coming out reflect the true reality of what's going on and I mean

00:26:14.400 --> 00:26:21.279
you've played around with dynamic super resolution correct mhm so do you think

00:26:18.960 --> 00:26:24.400
that dynamic super resolution is a good balance then if you're going to have a

00:26:22.480 --> 00:26:30.559
1080p display and you just take more samples yep on on a notebook yep we ran

00:26:27.600 --> 00:26:34.640
uh the the Dark Souls 2 demonstration portion or whatever on that on this MSI

00:26:32.960 --> 00:26:39.360
laptop using DSR and it looks great skyrim with DSR looks great um so if

00:26:37.440 --> 00:26:42.480
there are games where you have that capability to run at higher resolution

00:26:40.880 --> 00:26:47.600
you can still do that and take advantage of it on the 1080p display it's kind of

00:26:44.640 --> 00:26:52.960
it is kind of a really nice almost perfect setup for that right so if

00:26:50.320 --> 00:26:56.960
you've got more horsepower down sample render at 4K down sample if you don't

00:26:55.120 --> 00:27:01.760
then you've got a native 1080p display for it uh and and it works out pretty

00:26:59.039 --> 00:27:05.120
well so I guess that's pretty much all there is to say about them they're

00:27:03.200 --> 00:27:09.200
they're power efficient they support all the same features as the as the desktop

00:27:07.200 --> 00:27:15.600
ones i think the only really disappointing thing about it for me is

00:27:12.080 --> 00:27:17.440
that I feel like a lot of the talk about

00:27:15.600 --> 00:27:23.520
um oh you know the desktop and mobile are getting much closer is is spin

00:27:20.640 --> 00:27:29.279
because I really feel like the desktop could have been further ahead if NVIDIA

00:27:25.840 --> 00:27:31.679
hadn't started back with the GTX 680 um

00:27:29.279 --> 00:27:37.039
started kind of releasing their mid-tier chip as a flagship and then their true

00:27:35.120 --> 00:27:42.400
flagship as the next generation flagship chip and now extended this pattern where

00:27:39.440 --> 00:27:46.400
we're not getting full-on Maxwell but it's being sold to us as a top tier chip

00:27:44.720 --> 00:27:50.400
so NVIDIA is effectively getting two gens out of each architecture in terms

00:27:48.720 --> 00:27:54.080
of the numbering scheme when we used to get a full new series of cards with a

00:27:52.640 --> 00:27:57.679
full new architecture or at the very least a die shrink each time they said

00:27:56.399 --> 00:28:02.080
that they were releasing something new to us yeah i mean and it that that's

00:28:00.080 --> 00:28:05.279
that's that's definitely the case but it's it's I don't think they have a

00:28:03.840 --> 00:28:09.360
choice yeah it's a result of the manufacturing process issues that are

00:28:07.039 --> 00:28:14.640
there right it's it's well we're stuck on 28 nmter what can we do and also keep

00:28:11.520 --> 00:28:16.880
in mind that that Maxwell is aimed at

00:28:14.640 --> 00:28:21.039
power efficiency right like that design was really aimed at getting the most

00:28:19.440 --> 00:28:27.840
performance per watt and when you can do that um by definition right because of

00:28:24.559 --> 00:28:29.520
the way physics works you know your GPU

00:28:27.840 --> 00:28:34.240
on your notebook and on your desktop are going to compress they're going to get a little bit further right because that

00:28:32.000 --> 00:28:40.159
sweet spot for performance for the 980 is 165 watts where for the 980M it's

00:28:37.720 --> 00:28:46.960
like 120 watts or whatever it actually is so right um whereas on the you know

00:28:43.200 --> 00:28:50.640
the GTX 680 it was 200 210 watts versus

00:28:46.960 --> 00:28:52.240
110 watts so um it's it it's getting

00:28:50.640 --> 00:28:57.200
closer but I think it's not nearly as close as they would like you to believe

00:28:54.240 --> 00:29:02.240
based on their fancy marketing graphs i mean I did find some games where it was

00:28:59.679 --> 00:29:07.039
only a 10 15% delta but these were situations like Tomb Raider where I

00:29:04.240 --> 00:29:11.279
really wasn't that limited by the uh by the GPU itself i was more limited by the

00:29:09.520 --> 00:29:15.600
CPU because they were both running the game incredibly well even at ultra

00:29:12.799 --> 00:29:21.360
details whereas in games like Crisis 3 I was seeing as much as a 40% delta

00:29:18.080 --> 00:29:23.200
between the 970 and the 970M

00:29:21.360 --> 00:29:29.120
yeah there there's going to be those and and and I think you know if you look at

00:29:25.200 --> 00:29:33.440
just the specs the the the the 980M has

00:29:29.120 --> 00:29:35.440
fewer shaders than the 970 desktop part

00:29:33.440 --> 00:29:41.440
does yep right and the memory clock runs significantly lower 5 GHz instead of 7

00:29:38.039 --> 00:29:42.640
GHz uh so there there's fundamentally

00:29:41.440 --> 00:29:48.159
there is going to be a difference there so I think the the closest analog to the

00:29:44.640 --> 00:29:51.200
980M is probably the 970 desktop and

00:29:48.159 --> 00:29:54.559
it's kind of between the 680 well we'll

00:29:51.200 --> 00:29:57.200
say the 770 and the 970 is kind of where

00:29:54.559 --> 00:30:02.000
performance sits there all right so let's talk about the new Unreal Engine

00:29:59.679 --> 00:30:06.960
bringing eerily realistic skin to your games does eerily realistic skin even

00:30:04.640 --> 00:30:11.520
sound like something we want no not me personally ethnod posts this on the

00:30:09.360 --> 00:30:15.679
forum thanks for that and uh the original article is either from ngadget

00:30:13.520 --> 00:30:20.960
or unrealengine.com if you prefer to get it straight from the horse's mouth and

00:30:18.320 --> 00:30:26.799
um basically Ryan do you want to explain what subsurface scattering is exactly

00:30:23.600 --> 00:30:28.799
and how that makes things like skin or

00:30:26.799 --> 00:30:33.440
candles or especially any objects that are slightly translucent look more

00:30:30.960 --> 00:30:38.159
realistic in games so I mean subsurface scattering is not I I I don't think it's

00:30:35.840 --> 00:30:43.279
a graphics rendering specific term but the idea is pretty simple where you have

00:30:39.840 --> 00:30:46.240
a semi-t translansucent layer in this

00:30:43.279 --> 00:30:51.120
case your skin right and the light will penetrate one or more layers of the skin

00:30:48.880 --> 00:30:56.000
and then bounce out in a different way right so you may have some portion of

00:30:54.000 --> 00:30:58.960
that light going hitting your skin and bouncing back you may have some portion

00:30:57.279 --> 00:31:04.480
of the light going a couple of layers deep and bouncing out and the result is

00:31:01.039 --> 00:31:06.640
a different um kind of shade or look or

00:31:04.480 --> 00:31:11.039
style to how skin actually looks and it's something that you know we're used

00:31:08.640 --> 00:31:13.840
to seeing every day when you when when we're sitting here recording a video and

00:31:12.559 --> 00:31:19.120
you just look at yourself on the camera and you see a little bit of sheen on that part of your forehead there that

00:31:17.039 --> 00:31:25.440
you you know that that is something that is very hard to render accurately and do

00:31:22.080 --> 00:31:28.799
it in a fast you know real time method

00:31:25.440 --> 00:31:32.399
so uh Unreal Engine what is it the 4.5

00:31:28.799 --> 00:31:34.399
update 4.5 yeah yeah i mean these guys

00:31:32.399 --> 00:31:40.640
they just do everything awesome right like the the tech they build is

00:31:36.399 --> 00:31:42.480
impressive as hell um so a subsurface

00:31:40.640 --> 00:31:47.120
scattering basically i'm trying to think the first time I remember hearing that

00:31:43.760 --> 00:31:50.480
uh like some of the uh what was the the

00:31:47.120 --> 00:31:52.720
NVIDIA elf pixie character's name u Oh

00:31:50.480 --> 00:31:56.320
shoot it wasn't Dawn was it yeah I think it was Dawn yeah I think you're right

00:31:54.480 --> 00:32:00.559
and that was like they were like showing off subsurface scattering for the very

00:31:58.159 --> 00:32:03.919
first time but now you think about it how long has it been since we saw that

00:32:02.399 --> 00:32:08.000
demo and now we're finally getting it into an engine that can operate that

00:32:06.159 --> 00:32:10.799
technology in a real-time manner it's been six or seven years hasn't it yeah

00:32:09.760 --> 00:32:17.200
there's I mean there are several iterations of Dawn so I can't tell you exactly which one Yeah had that demo to

00:32:15.120 --> 00:32:22.240
begin with but yeah i mean the funny thing about it is it puts us sort of

00:32:19.399 --> 00:32:26.240
tech you know podcasters or journalists or whoever else puts us in a really

00:32:23.760 --> 00:32:30.960
weird position because NVIDIA and AMD for that matter are both always

00:32:28.559 --> 00:32:36.640
trumpeting about this stuff whether it's uh VXGi or whether it's um you know

00:32:33.919 --> 00:32:41.039
physics simulations interfacing with each other in real time or whatever the

00:32:39.440 --> 00:32:47.039
newest coolest thing they're showing us is where we kind of sit there and we go

00:32:43.200 --> 00:32:50.320
well [ __ ] guys it's going to be eight

00:32:47.039 --> 00:32:51.679
years before you can actually do any of

00:32:50.320 --> 00:32:55.519
this in real time in a game engine because you look at something like that

00:32:53.360 --> 00:33:00.240
lunar okay here before I talk about the lunar lander guys in the corner here on

00:32:58.320 --> 00:33:05.039
the left you've got no subsurface scattering so his face looks kind of too

00:33:03.039 --> 00:33:08.399
harsh in the middle you've got a little bit of subsurface scattering so the

00:33:06.559 --> 00:33:12.559
reflections off of his face and the the tone of his skin looks a lot more

00:33:10.159 --> 00:33:16.320
natural and then on the very far right you've got an exaggerated effect where

00:33:14.159 --> 00:33:20.080
they've cranked it up too much kind of like oversaturating your TV and it just

00:33:18.320 --> 00:33:24.000
his face looks like it's made of melted wax so I just wanted to show you that to

00:33:21.919 --> 00:33:30.080
you guys so a great example of this would be NVIDIA's Lunar Lander demo

00:33:27.440 --> 00:33:38.840
where they've got their VXGI realtime global illumination running and on two

00:33:33.440 --> 00:33:42.960
GTX 980s with a static scene that is not

00:33:38.840 --> 00:33:45.120
moving and with what what is it two

00:33:42.960 --> 00:33:48.159
models of people where we're and we don't even have anything that's

00:33:46.080 --> 00:33:51.360
complicated to render they're in suits they're They're not even They don't even

00:33:49.679 --> 00:33:57.679
have skin or anything and then we've got a ship that's mostly hard edges and that

00:33:55.200 --> 00:34:02.320
thing's still chugged just moving the camera around a little bit i mean how

00:33:59.760 --> 00:34:06.000
far are we away from a having any hardware that can run this reasonably

00:34:03.679 --> 00:34:09.599
well and b a game dev actually implementing this technology it makes it

00:34:07.679 --> 00:34:15.520
tough to talk about this stuff when it's actually like futuristic tech not really

00:34:13.119 --> 00:34:20.399
that meaningful for the GTX 980 no game will ever run on the GTX 980 that uses

00:34:18.320 --> 00:34:25.040
that technology it's it's been that way really since I

00:34:22.879 --> 00:34:28.960
have ever covered graphics cards right from the very first time we saw TNL

00:34:26.960 --> 00:34:31.760
lighting and and and then you know programmable shaders and geometry

00:34:30.480 --> 00:34:37.280
shaders and all this stuff they always had these amazing demos you never really knew what the implementation timeline

00:34:35.599 --> 00:34:41.919
was and right you know part of that comes back to

00:34:39.520 --> 00:34:45.440
people that have this distaste for something like GameWorks NVIDIA's goal

00:34:43.520 --> 00:34:49.280
with that is to get that tech into games as quickly as possible now it means they

00:34:47.119 --> 00:34:55.760
sacrifice compatibility and kind of broad industry support for prop for

00:34:52.159 --> 00:34:58.720
proprietary stuff but you know like they

00:34:55.760 --> 00:35:03.920
say that VxGI is in the current iteration of the Unreal Engine but when

00:35:02.079 --> 00:35:07.920
will you actually see it in a game is still up in the air and then to what

00:35:06.000 --> 00:35:13.119
degree right there's a whole lot of resolution options for VxGI and I mean

00:35:11.280 --> 00:35:16.800
the thing about that is to what degree is really going to depend on the

00:35:14.560 --> 00:35:20.440
adoption of cards that support it and if we've got two cards each of which cost

00:35:19.359 --> 00:35:25.760
more than $300 then we're a long way away from

00:35:23.520 --> 00:35:29.200
from any game dev actually investing the time and resources that it would take i

00:35:27.440 --> 00:35:34.079
mean I mean you look at game devs not even not even porting their existing

00:35:31.680 --> 00:35:38.160
games to DirectX12 or not even taking games that are currently in development

00:35:35.680 --> 00:35:42.560
and bothering to move them to DirectX12 or Mantle or whatever the case may be

00:35:39.920 --> 00:35:47.359
where you're going to have an enormous market a built-in user base for these

00:35:45.320 --> 00:35:52.240
technologies and then you take something like VXGI where it's limited to one or

00:35:49.280 --> 00:35:55.839
two cards i mean come on i mean having it in a game engine like UE4 will help

00:35:54.079 --> 00:36:00.880
with that and it needs to be one of those things that you can enable disable

00:35:57.520 --> 00:36:04.320
it doesn't affect uh your game play per

00:36:00.880 --> 00:36:06.320
se but more about visual style um I

00:36:04.320 --> 00:36:11.119
don't know it I we want to see that kind of stuff in there and so I I applaud any

00:36:09.599 --> 00:36:16.800
company whether it be a hardware vendor or software vendor that is willing to

00:36:12.720 --> 00:36:18.960
stick their neck out and do more work uh

00:36:16.800 --> 00:36:23.200
to push the technology forward right if we only stuck with things that worked on

00:36:20.880 --> 00:36:27.839
GPUs today we would never actually develop the tech that would allow us to

00:36:24.640 --> 00:36:30.640
do even newer better cooler things on

00:36:27.839 --> 00:36:35.280
GPUs next year right so somebody's got to start at hardware or software um it

00:36:33.280 --> 00:36:38.560
used to be at software that pushed it right and now it's kind of the hardware

00:36:36.800 --> 00:36:43.920
developers saying "Hey guys try this hey guys try this." Speaking of hardware

00:36:41.520 --> 00:36:49.040
developers this topic isn't actually in the document but AMD reached out to me

00:36:46.400 --> 00:36:53.440
i've got a pager email from uh from Robert over there in my inbox saying

00:36:51.359 --> 00:36:58.560
that they watched the October 4th WAN Show yay people watch my show um and

00:36:56.880 --> 00:37:04.640
wanted to address some points I made about Freync uh okay you acknowledge at

00:37:02.079 --> 00:37:09.240
2551 that G-Sync monitors are extremely expensive we are hoping that Freync will

00:37:07.200 --> 00:37:16.240
help with this you say there is misinformation concerning Freync but AMD

00:37:12.800 --> 00:37:18.400
does offer a comprehensive FAQ so uh

00:37:16.240 --> 00:37:25.200
they had just asked me to go ahead and show you guys the AMD FAQ that exists

00:37:21.599 --> 00:37:25.200
about Project Freync so it's

00:37:28.040 --> 00:37:35.320
support.AMD.com-uskb-article/pages/freync-faq.aspx really easy to remember guys just go ahead key that into your browser right

00:37:32.320 --> 00:37:35.320
now

00:37:35.440 --> 00:37:43.760
um but the main thing that I wanted to clarify is that I wasn't saying that the

00:37:41.000 --> 00:37:48.880
misinformation that's there right now is coming from AMD AMD has their FAQ and

00:37:47.200 --> 00:37:53.280
that's fine and that's great what I was saying is that there's a lot of

00:37:50.760 --> 00:37:58.400
misinformation out there and I think that it's a lot of people repeating

00:37:55.760 --> 00:38:02.640
things that they heard earlier on in the Freync development process back when we

00:38:01.200 --> 00:38:08.720
really didn't know what the heck was going on and AMD wasn't communicating as

00:38:05.040 --> 00:38:10.400
clearly as they are right now so Ryan

00:38:08.720 --> 00:38:15.920
you're pretty familiar with Freync correct uh as familiar as I can be yeah

00:38:13.520 --> 00:38:19.920
yeah well given that we don't have products in our hands yet right but I

00:38:17.920 --> 00:38:27.440
mean can you can you explain what the heck it is exactly and how it relates to

00:38:22.720 --> 00:38:31.280
G-Sync so um the the initial So the way

00:38:27.440 --> 00:38:32.560
I understand it now Freync is a is a

00:38:31.280 --> 00:38:37.280
name I don't know if it'll be the final name a brand associated with the

00:38:34.760 --> 00:38:44.960
implementation with AMD's specific implementation of the Visa DisplayPort

00:38:41.119 --> 00:38:47.520
1.2A to a adaptive sync technology so

00:38:44.960 --> 00:38:52.640
adaptive sync was adopted by uh the the visa foundation into DisplayPort 1.2A

00:38:49.920 --> 00:38:59.440
revision 2 or whatever they call it um as an optional part of the specification

00:38:56.480 --> 00:39:02.960
and all it does is it gives the uh hardware and software vendors the

00:39:00.800 --> 00:39:08.640
ability to understand that there is a potential for the ability to withhold a

00:39:05.839 --> 00:39:14.160
um a vblank signal right so you basically can control a monitor's

00:39:10.960 --> 00:39:17.760
refresh cycle through a system through

00:39:14.160 --> 00:39:19.839
an external system like a PC now that

00:39:17.760 --> 00:39:23.119
doesn't give you the that sync or that the adaptive sync standard doesn't give

00:39:21.200 --> 00:39:26.880
you any information about uh how you handle special cases how you actually

00:39:25.119 --> 00:39:31.359
implement it how it works with your driver how it works with Windows and all

00:39:28.880 --> 00:39:36.079
that other stuff so right the free sync technology as they're calling it is kind

00:39:33.440 --> 00:39:40.880
of AMD's implementation of adaptosync into a product so that's one of the

00:39:38.560 --> 00:39:47.920
biggest misconceptions out there you guys freync is not built into display

00:39:44.960 --> 00:39:54.760
port it's not just a matter of any DisplayPort 1.2A display and any AMD

00:39:52.320 --> 00:40:00.240
GPU that supports Freync you plug them together and magic's going to happen in

00:39:57.760 --> 00:40:04.200
much the same way that NVIDIA's G-Sync relies on the hardware being implemented

00:40:02.240 --> 00:40:09.680
on the monitor in a specific way we will have that same process going

00:40:07.760 --> 00:40:13.119
on with Freync it will have to actually be a Freync certified display now AMD is

00:40:11.760 --> 00:40:20.000
saying that they're not planning to charge a licensing fee for it though correct

00:40:16.520 --> 00:40:23.119
well correct because the the display

00:40:20.000 --> 00:40:26.880
port so the only technology required by

00:40:23.119 --> 00:40:29.760
the display uh scaler vendor is adaptive

00:40:26.880 --> 00:40:34.000
sync right so that is already part of the standard so AMD you know doesn't

00:40:32.160 --> 00:40:39.200
really control so a monitor will come out that will support adaptive sync it

00:40:37.200 --> 00:40:44.960
doesn't necessarily support freync it will be on freync the AMD technology to

00:40:41.920 --> 00:40:47.760
support adaptive sync monitors right so

00:40:44.960 --> 00:40:51.280
but as it turns out because uh uh Tom was on our show and talked very openly

00:40:49.680 --> 00:40:56.640
about the fact that NVIDIA is not going to support adaptive sync monitors you

00:40:53.839 --> 00:41:00.400
will essentially have freync versus G-Sync as opposed to what many had hoped

00:40:58.640 --> 00:41:04.079
which is you would have G-Sync and then this other standard that both vendors

00:41:02.319 --> 00:41:07.520
would support um which and would eventually just be ubiquitous right

00:41:06.319 --> 00:41:13.440
which is not going to be the case anymore so it's disappointing i know and I

00:41:11.040 --> 00:41:19.599
expressed that to him several times uh but you know Freync has the capability

00:41:16.880 --> 00:41:26.560
it has the opportunity to be everything that we love about G-Sync and cheaper it

00:41:22.480 --> 00:41:28.800
has that opportunity um the it will it

00:41:26.560 --> 00:41:32.720
will what they need to do is prove it right NVIDIA's claim has always been

00:41:31.040 --> 00:41:38.000
that hey it's not easy to do if it were super easy to do everybody would have

00:41:34.560 --> 00:41:39.760
done it by now and AMD's stance is that

00:41:38.000 --> 00:41:42.960
we can do it it's pretty easy and we can make it you know we're not going to

00:41:41.040 --> 00:41:46.000
charge kind of the licensing fee and we're not going to charge the markup

00:41:44.400 --> 00:41:50.079
that you see on all the G-Sync monitors out there which is a amicable goal like

00:41:47.839 --> 00:41:54.880
I'm totally for that give us variable refresh displays cheaper than we get

00:41:51.680 --> 00:41:56.800
them today yeah I'm I'm all for it i

00:41:54.880 --> 00:42:01.440
just I have to wonder if they're going to pull it off because they they they do

00:41:58.960 --> 00:42:04.160
they did say that they uh they linked me to uh to

00:42:04.520 --> 00:42:11.440
anchor at Computex um so so that's cool

00:42:08.960 --> 00:42:18.960
but Scott had uh we had Scott Wson on last week um so Scott had expressed some

00:42:14.920 --> 00:42:21.440
some I guess some respect for how

00:42:18.960 --> 00:42:25.920
complicated G-Sync was and he had said that that Tom had told him that they

00:42:24.240 --> 00:42:29.440
actually it was a good thing that they used a programmable chip for the G-Sync

00:42:27.760 --> 00:42:32.720
module because otherwise they would have been doing a hardware refresh that's why

00:42:31.119 --> 00:42:36.960
it took so long from when they showed it to us back in October last year to when

00:42:35.200 --> 00:42:40.800
we actually got monitors because it wasn't working they had to they had to

00:42:39.040 --> 00:42:46.640
actually redesign the functionality of the chip and reprogram it yeah yeah i

00:42:43.520 --> 00:42:48.000
mean it the Yes this the same thing is

00:42:46.640 --> 00:42:52.480
what I've been told as well that it that it's incredibly complicated i mean don't

00:42:50.240 --> 00:42:56.800
I mean clearly you and I were both at that event in Montreal NVIDIA was

00:42:54.560 --> 00:43:01.839
incredibly excited about the the tech they would not have waited until August

00:42:59.359 --> 00:43:05.760
to release a display if there was any re any way they could have not waited till

00:43:03.920 --> 00:43:11.240
August to release a display right yeah and I mean NVIDIA is usually pretty tidy

00:43:09.119 --> 00:43:16.880
as far as announce seed samples get it out the

00:43:14.319 --> 00:43:21.200
door yeah like they're they're textbook execution you know them and guys like

00:43:18.800 --> 00:43:26.240
Apple they they just they do it they nail it um and for NVIDIA to announce

00:43:24.240 --> 00:43:30.000
something and show it and promise it was going to be available on a date you're

00:43:28.000 --> 00:43:35.040
usually pretty sure that they're pretty damn sure it's coming and they were way

00:43:32.319 --> 00:43:38.640
late on it yeah and I I think it's I think I don't know this for a fact but I

00:43:36.800 --> 00:43:45.040
think one of the reasons why NVIDIA will not support adaptive sync displays is

00:43:42.599 --> 00:43:50.880
because to support an adaptive sync display your driver basically has to do

00:43:47.359 --> 00:43:52.880
all of the work in Windows that the

00:43:50.880 --> 00:43:57.680
combination of driver and controller that NVIDIA has on G-Sync will do now

00:43:55.359 --> 00:44:00.240
and if they do that basically they will have to put all of the knowledge that

00:43:58.960 --> 00:44:06.880
they have learned over the last couple of years building G-Sync into their software which will then make it easily

00:44:03.480 --> 00:44:08.800
discoverable by AMD right and so that

00:44:06.880 --> 00:44:14.480
they would get a jump start in that way but um you know like like I said I want

00:44:11.119 --> 00:44:16.480
Freync to be here already uh you know

00:44:14.480 --> 00:44:19.599
we've we've had we've had Richard Huddy and and those guys on our show and

00:44:17.920 --> 00:44:24.319
they've they've promised prototypes at certain times and don't really have them

00:44:21.680 --> 00:44:29.599
yet i was promised one by in September uh and we It's as far as I know it's the

00:44:27.119 --> 00:44:34.720
middle of October now uh well let's be fair it's the 10th of October which is

00:44:31.560 --> 00:44:38.000
the 3rd of October it's It's the first

00:44:34.720 --> 00:44:41.119
3rd of October we We'll go with that uh

00:44:38.000 --> 00:44:42.640
yeah october has 31 days so until we're

00:44:41.119 --> 00:44:48.000
actually No if we're a third of the way through today then No no it is the second third of October but not half

00:44:46.480 --> 00:44:51.839
let's just agree that it's not half okay we got to be If we're going to we're going to make these these these claims

00:44:50.880 --> 00:44:55.760
out here we want to make sure we're accurate so you know I I want it to be

00:44:54.079 --> 00:44:59.440
there and I I think what will I think what will inevitably happen is we'll

00:44:57.200 --> 00:45:03.200
we'll have to wait until CES i think scaler vendors it's not a super quick

00:45:01.760 --> 00:45:08.400
process you know when we first heard about Freync they were talking about oh you'd be able to upgrade some displays

00:45:05.839 --> 00:45:12.640
and that's clearly not going to happen right as it turns out flashing a

00:45:10.160 --> 00:45:15.359
firmware is not going to make a monitor a good experience you can make it

00:45:13.920 --> 00:45:20.800
variable refresh all you want but it will be a good experience right uh and

00:45:18.560 --> 00:45:25.599
and when light is involved in hitting your

00:45:21.560 --> 00:45:28.240
eyes any any degradation in that will be

00:45:25.599 --> 00:45:32.520
noticeable easily so which worries me a lot i mean here's something how cuz Okay

00:45:31.760 --> 00:45:36.880
it's it's well it's not that easy okay so

00:45:35.040 --> 00:45:40.880
let's go back to the old days when it was pretty easy to figure out which

00:45:39.119 --> 00:45:45.680
graphics card delivered the best gaming experience you know you fired up a game

00:45:43.520 --> 00:45:49.760
you recorded your average FPS and you made a bar graph and that was the whole

00:45:47.440 --> 00:45:53.760
story y then all of a sudden we're dealing with runt frames frames that are

00:45:52.079 --> 00:45:58.000
displayed for such a short period of time on your screen that you you

00:45:56.160 --> 00:46:02.079
actually don't even perceive them we're dealing with things like stutters that

00:45:59.760 --> 00:46:07.599
don't actually show up in an average or even necessarily a minimum frame rate

00:46:05.119 --> 00:46:12.880
but that are visually very obvious we actually illustrated this in our

00:46:09.520 --> 00:46:15.680
four-way SLI scaling video very recently

00:46:12.880 --> 00:46:22.000
where we intentionally froze the frame of our video very periodically lowering

00:46:18.720 --> 00:46:23.760
our overall Oh you saw that oh okay yeah

00:46:22.000 --> 00:46:27.920
so we were So for the viewers then we were trying to make a point that just

00:46:25.280 --> 00:46:33.839
because you lower your frame rate 1% or two or 3% doesn't mean that it's only 3%

00:46:31.440 --> 00:46:37.520
less visually smooth you can see a stutter very clearly so that's why and

00:46:36.000 --> 00:46:42.240
this was the first time we ever had you as a guest on the show that's why FCAT

00:46:40.160 --> 00:46:46.480
or actually capturing the output of the graphics card analyzing every frame to

00:46:44.720 --> 00:46:51.680
look at what the viewer was actually seeing became very important but for

00:46:49.200 --> 00:46:57.200
something like G-Sync versus Freync how the hell are we going to qualify or

00:46:53.760 --> 00:46:58.880
excuse me quantify the smoothness of the

00:46:57.200 --> 00:47:04.319
experience so uh it will involve uh basic it's

00:47:02.800 --> 00:47:09.680
basically the same process we use now for capture but with cameras right and

00:47:06.960 --> 00:47:15.839
actually we we have a we we kind of have the ability right now to capture

00:47:11.280 --> 00:47:18.319
variable variable refresh video um

00:47:15.839 --> 00:47:21.920
through DisplayPort it's it's it's like working through some of these ASIC

00:47:19.920 --> 00:47:25.440
manufacturers and it's not working very well and it's the post-processing side

00:47:24.000 --> 00:47:30.000
of it is actually much more difficult post-processing with a static 60 hertz

00:47:28.400 --> 00:47:33.599
video is really easy you know what to account for and what to look for when it

00:47:31.839 --> 00:47:37.839
varies all the time you you really don't know what you're looking for to even

00:47:35.599 --> 00:47:43.200
measure against it right so right uh it's going to take a little bit of I

00:47:39.599 --> 00:47:45.359
think software on the the tested PC side

00:47:43.200 --> 00:47:49.119
to output some here's what I tried to send result right and then a

00:47:47.599 --> 00:47:55.119
post-processing algorithm that says well here's what I actually saw and then we

00:47:50.960 --> 00:47:56.480
get into the issue of are in is NVIDIA

00:47:55.119 --> 00:48:01.920
going to play well with that is AMD going to play well with that are they going to fix that system in some way

00:48:00.480 --> 00:48:05.839
it's going to be really complicated and I think at least initially it's going to

00:48:03.920 --> 00:48:09.520
be a lot of well I have these two monitors sitting next to me and they're

00:48:07.680 --> 00:48:13.599
identical systems you know one's got a 290X and one's got a 980 and I'm playing

00:48:11.440 --> 00:48:19.040
the same game and maybe I have a mouse going into a an HID distributor so that

00:48:16.640 --> 00:48:21.599
you can play the same game with one mouse and try to like see the

00:48:20.560 --> 00:48:26.400
comparisons there's going to be a lot of that crap where it's very objective and

00:48:24.079 --> 00:48:31.440
because it's objective everybody's wrong right if I say better yeah yeah sorry

00:48:29.920 --> 00:48:35.040
because it's subjective everybody's going to be wrong because everybody will

00:48:33.440 --> 00:48:40.400
have a different opinion so basically the hardware review industry of which

00:48:37.359 --> 00:48:43.520
you've been a part for 15 years is going

00:48:40.400 --> 00:48:45.200
full circle from like yeah dude I got

00:48:43.520 --> 00:48:49.760
this graphics card it gets like great FPS and my games run super smooth to

00:48:47.599 --> 00:48:53.040
getting it really down to a science to where we could really figure out which

00:48:51.440 --> 00:48:56.160
one was better and then we're going all the way back to yeah dude I got these

00:48:54.880 --> 00:49:01.520
two graphics cards I'm going to play with them both side by side I'll let you know which one's better yeah I I think

00:49:00.000 --> 00:49:06.400
it will be like that initially and that sucks but uh that's terrible we'll fix

00:49:04.559 --> 00:49:09.839
it we'll we'll figure it out like it it will be an industry problem that will be

00:49:07.920 --> 00:49:13.760
solved because there's too much money and too much pride in both of these

00:49:11.599 --> 00:49:20.559
companies to kind of just let it let it sit there and be determined by our uh uh

00:49:18.559 --> 00:49:24.880
subjective eyeballs I guess by staring at it really hard yeah and no nothing

00:49:23.280 --> 00:49:29.839
good happens once you've stared at a monitor for three hours straight trying to figure out which one is better

00:49:27.200 --> 00:49:34.160
nothing good will happen so uh it needs to be something yeah i had someone tweet

00:49:32.240 --> 00:49:39.119
at me the other day about how easy my job is and uh I was kind of I was

00:49:37.119 --> 00:49:44.319
sitting there last night at 4 in the morning uh benchmarking these new mobile

00:49:42.079 --> 00:49:49.040
graphics cards just kind of going "Dude you have no idea." My wife to this day

00:49:47.359 --> 00:49:52.960
still believes that I sit at the office and play video games all day and I'm

00:49:51.119 --> 00:49:58.240
like "Ah who am benchmarking them hun?" when when

00:49:55.599 --> 00:50:05.359
you play the same 60 to 90 second portion of uh Skyrim for the I think

00:50:02.319 --> 00:50:07.839
40,000th time uh it's not really fun

00:50:05.359 --> 00:50:12.079
anymore you know some benchmarks are okay i don't mind our Tomb Raider run

00:50:10.400 --> 00:50:15.280
cuz it's got some it's got some cinematic bits where you kind of you

00:50:13.920 --> 00:50:20.640
kind of watch some stuff at the beginning then it's got like a slow-mo thing where you like pop two guys then

00:50:18.880 --> 00:50:25.520
you go into a burning building you jump across a chasm you like uh silent kill

00:50:23.839 --> 00:50:30.400
some guy you jump up and then you kill more two more guys like it's actually a

00:50:27.200 --> 00:50:32.559
pretty engaging benchmark but our Shadow

00:50:30.400 --> 00:50:38.160
of Mordor benchmark when I was running that last night Tomb Raider the 2

00:50:34.720 --> 00:50:41.280
minutes flies by shadow of Mordor the

00:50:38.160 --> 00:50:43.520
only way we got it um consistent enough

00:50:41.280 --> 00:50:48.960
cuz we'll do we'll do five or 10 runs once we've locked it down and we'll be

00:50:45.520 --> 00:50:51.200
looking for about 2 to 5 FPS difference

00:50:48.960 --> 00:50:56.640
on the same hardware in order to decide okay this runs okay for our error

00:50:53.920 --> 00:51:01.920
tolerance so Shadow of Mordor the way we got that done because it's got dynamic

00:50:58.319 --> 00:51:04.720
weather it's got dynamic you know roving

00:51:01.920 --> 00:51:08.720
locations yeah yep bad dudes and all this stuff it was really hard so we

00:51:06.800 --> 00:51:13.760
ended up finding an instance that always has the same weather and then always has

00:51:11.119 --> 00:51:16.559
the same baddies that will mostly come and attack you all at the same time in

00:51:15.359 --> 00:51:20.800
pretty much the same way and they'll circle you so the way the benchmark

00:51:18.640 --> 00:51:26.880
works in order to make it equally visually demanding is we attract all the

00:51:23.520 --> 00:51:29.599
baddies and then block for two minutes

00:51:26.880 --> 00:51:33.280
with some nice scenery in the background so we keep we keep our character

00:51:31.280 --> 00:51:36.480
stationary and our camera as stationary as possible and block for two minutes

00:51:34.880 --> 00:51:41.760
and that's how we got the consistency i swear I sometimes I would miss a block

00:51:38.800 --> 00:51:46.319
because I was half asleep half asleep at the wheel there yeah that's I could see

00:51:44.319 --> 00:51:52.240
how that would be pretty bad yeah you know at three in the morning it's like

00:51:48.160 --> 00:51:53.760
oh I have to block this orc again crap

00:51:52.240 --> 00:51:59.359
just get like a What remember when they had the the the controllers with the turbo buttons where you just hold it

00:51:56.400 --> 00:52:02.960
down maybe you could do that no because I have to reposition him i

00:52:01.680 --> 00:52:06.480
actually have to be paying close attention to the block so I keep him in

00:52:05.040 --> 00:52:10.960
the same location so I'm rendering basically the same scene yeah all right

00:52:08.960 --> 00:52:15.359
that's pretty bad yeah and the funny the stupid thing about Shadow of Mordor is

00:52:13.040 --> 00:52:19.520
and I'm sure you're with me on this how much do you wish that video game makers

00:52:17.359 --> 00:52:24.319
would build in benchmarks into their games shadow of Mordor does have a

00:52:22.240 --> 00:52:29.280
benchmark in it it does but here's a problem shadow of Mordor is capped at

00:52:26.480 --> 00:52:34.079
100 FPS and the benchmark runs at whatever frame rate it wants so you

00:52:31.200 --> 00:52:38.720
could get a max FPS value of 280 frames per second because I think it's actually

00:52:36.079 --> 00:52:42.880
recording when the screen is black and the game will never run that way so

00:52:40.319 --> 00:52:46.640
you're not getting a meaningful result yep yep you're right i I didn't see that

00:52:44.960 --> 00:52:50.160
issue because we we were using the capture stuff so we didn't capture the

00:52:48.400 --> 00:52:54.720
the black screen stuff so yeah okay i see what you're saying yep good point

00:52:52.720 --> 00:52:58.800
that and from what I've seen the Shadow of Mordor benchmark is really not that

00:52:57.040 --> 00:53:02.319
representative of in-game performance anyway because you don't get that close

00:53:00.720 --> 00:53:07.119
to any of the models and you don't really have a ton of them on screen at a

00:53:03.920 --> 00:53:10.319
time so when we do our blocking combat

00:53:07.119 --> 00:53:12.400
thing we actually get 10 to 20% lower

00:53:10.319 --> 00:53:16.559
than that fly through which has fires and all the things that should be

00:53:13.680 --> 00:53:20.640
demanding and then when you have adverse weather conditions you actually drop

00:53:18.400 --> 00:53:23.920
another 20% off the performance so that in-game benchmark which is always great

00:53:22.400 --> 00:53:28.640
weather and never gets too close to anything is about 30 to 40% out of the

00:53:27.280 --> 00:53:34.400
performance that people could actually expect to get in the game i think it does rain in the benchmark but it's not

00:53:31.520 --> 00:53:39.200
the most demanding instance of rain in the game when the weather's really heavy

00:53:36.400 --> 00:53:42.559
it it tanks it yep so that was really frustrating for me because I kind of

00:53:40.480 --> 00:53:48.000
went well shoot this isn't that usable actually yep yeah i think what would be

00:53:46.079 --> 00:53:52.240
better is Well I mean in that in your instance there it's all dynamic so being

00:53:50.000 --> 00:53:57.119
able to record and replay USB input wouldn't really help you in that

00:53:53.920 --> 00:53:59.680
instance no no it wouldn't unfortunately

00:53:57.119 --> 00:54:04.000
tough life we have sorry yeah I know playing video games for a living

00:54:02.400 --> 00:54:08.160
or so everyone thinks that's what they think it's all right so here's an

00:54:06.640 --> 00:54:12.720
interesting little piece of news now we all know the iPhone 6 which by the way I

00:54:10.720 --> 00:54:16.800
have finally received one of for those of you who were expecting me to do a

00:54:14.319 --> 00:54:22.960
review here's my uh here's my iPhone 6 that I have obviously totally set up see

00:54:20.720 --> 00:54:28.000
got completely all the stock icons and nothing else on it so I'm not I'm not

00:54:24.640 --> 00:54:29.680
started yet um finally got my iPhone 6 i

00:54:28.000 --> 00:54:35.200
live dangerously got it in my back pocket

00:54:32.240 --> 00:54:40.720
i'm I'm like a I'm like a a badass over here um so we originally thought there

00:54:38.319 --> 00:54:44.240
was a viral video that Marcus Brownley released where he was showing off the

00:54:42.319 --> 00:54:47.200
sapphire glass that was supposedly going to be on the new iPhone 6 and iPhone 6

00:54:46.000 --> 00:54:52.000
Plus we originally thought we were going to get a sapphire glass complete display

00:54:49.760 --> 00:54:56.880
cover turns out we didn't get that at all and GT Advanced Technologies Apple's

00:54:54.559 --> 00:55:00.960
Sapphire Glass supplier has just filed for bankruptcy um so this was posted by

00:54:59.200 --> 00:55:06.000
Querty Warrior on the forum the original article was from Next Powerup and

00:55:04.000 --> 00:55:11.440
basically last year they entered into a big deal uh over $500 million with Apple

00:55:09.359 --> 00:55:16.960
to supply Sapphire Glass they're meant to start actually supplying it in 2015

00:55:14.000 --> 00:55:20.319
and they are now down to 85 million in cash and looking for additional

00:55:18.400 --> 00:55:25.760
financing to continue their operations so Ryan how much of a blow is this to

00:55:23.760 --> 00:55:30.880
the adoption of Sapphire Glass because we all know that Apple really leads the

00:55:28.240 --> 00:55:35.359
charge on materials technology in a way that no one else seems to be willing to

00:55:32.559 --> 00:55:40.400
do the the the issue with Apple is they like to own the materials that they use

00:55:38.400 --> 00:55:45.040
or at least kind of be the almost exclusive buyer from those companies

00:55:42.400 --> 00:55:49.920
right so you know I'm interested so like the the the phone doesn't use sapphire

00:55:46.720 --> 00:55:52.400
but the watch uses sapphire yes right so

00:55:49.920 --> 00:55:58.160
is this indication that they don't expect the the watch to sell as much as

00:55:55.599 --> 00:56:02.000
maybe they had originally or you know are you believe that they were going to

00:55:59.839 --> 00:56:06.960
build the display out of Sapphire and change their mind kind of at the last

00:56:03.359 --> 00:56:09.599
minute i guess on the on the phones I do

00:56:06.960 --> 00:56:14.960
wonder yeah I mean it that seems likely right you have a company who has this

00:56:11.520 --> 00:56:16.960
multi-million deal multi-million deal

00:56:14.960 --> 00:56:20.559
dollar deal with multiple years through Apple and it kind of like all falls

00:56:18.319 --> 00:56:24.640
through um you know clearly they were doing some experimenting and it didn't

00:56:22.240 --> 00:56:29.280
turn out but yeah and I mean someone the size of Corning I think even an Apple PO

00:56:27.359 --> 00:56:33.599
probably doesn't scare them that much so if Apple turns around and goes "Okay

00:56:30.960 --> 00:56:37.520
yeah we need one bazillion orders of Gorilla Glass 3." I think Corning can

00:56:35.520 --> 00:56:42.160
probably turn that around for them okay um so it that really is what it looks

00:56:40.160 --> 00:56:47.760
like um those samples that were floating around may have very well been samples

00:56:44.880 --> 00:56:52.640
that no deal ever got done on and how how disappointing is it then to see that

00:56:49.839 --> 00:56:57.040
sapphire glass is still probably not going to be the standard for a while i

00:56:54.880 --> 00:57:02.720
you know I I I go through a lot of phones i don't really scratch them very

00:56:59.680 --> 00:57:06.000
often and I don't them usually i kind of

00:57:02.720 --> 00:57:08.880
I do sometimes but uh I never I was

00:57:06.000 --> 00:57:12.880
never really sure that it made sense based on the cost difference to have a

00:57:10.720 --> 00:57:18.640
sapphire screen on a phone for my watch it makes total sense because I slam that

00:57:15.200 --> 00:57:20.400
into every wall and door frame and yeah

00:57:18.640 --> 00:57:24.160
and everything right like it gets beat up i have a Samsung Gear Live and I

00:57:22.559 --> 00:57:29.040
don't think it has a sapphire screen and I think you can tell that that is the

00:57:26.720 --> 00:57:32.079
case right so my Pebble Steel is still doing okay is does that one have a

00:57:30.559 --> 00:57:36.079
Gorilla Glass screen at least i don't know actually i'm not It's actually I

00:57:34.400 --> 00:57:39.839
will admit looking at it now in these lights that there aren't really any

00:57:37.599 --> 00:57:42.960
major scratches which is maybe impressive maybe it does have something

00:57:41.119 --> 00:57:47.280
in there good but I mean even if it has like Gorilla Glass 3 that's still a

00:57:46.079 --> 00:57:50.960
pretty good product for scratch resistance so um it just you know it

00:57:49.920 --> 00:57:56.240
makes more sense it's hard to manufacture sapphire is uh it's easier

00:57:54.160 --> 00:58:02.960
to much much easier to manufacture in a small form factor like this than it is

00:57:58.480 --> 00:58:05.359
in a 5.5 in you know iPhone 6 Plus type

00:58:02.960 --> 00:58:09.920
form factor so right I think we'll get there eventually right like they'll

00:58:07.359 --> 00:58:13.920
somebody will have some manufacturing um breakthrough and cost will go down

00:58:12.400 --> 00:58:16.960
and it's just like anything else that you produce or manufacture there

00:58:15.680 --> 00:58:21.760
somebody will eventually figure it out if there is a need for it um I guess it

00:58:19.440 --> 00:58:25.920
just wasn't GT Advanced Technologies this time it was not or maybe it was

00:58:24.240 --> 00:58:30.480
them and they have the best solution possible and Apple was like no we don't

00:58:27.520 --> 00:58:34.880
want to cut into our uh you know our our markup our margins that much so we're

00:58:33.119 --> 00:58:40.880
going to wait for our next generation so maybe the 6S will have sapphire or maybe

00:58:38.240 --> 00:58:44.240
not you know so who knows with Apple yeah that's true speaking of the Gear

00:58:42.240 --> 00:58:48.799
Live how do you how do you find the smartwatch experience without a

00:58:46.400 --> 00:58:53.839
multi-day battery because I've I've stuck by the Pebble Steel especially at

00:58:51.359 --> 00:58:57.920
that new $200 price point And with that new third party app that's giving you

00:58:55.640 --> 00:59:01.680
continuous I think it does continuous fitness monitoring not possibly to the

00:59:00.319 --> 00:59:07.040
same extent that some other stuff can do with heart rate and all that but I

00:59:04.400 --> 00:59:11.599
freaking love this thing and I love that even as a very heavy user I can go four

00:59:09.119 --> 00:59:18.079
days without charging it are you okay with one day um I I would like to not be

00:59:16.000 --> 00:59:24.240
but I think I am you know I guess my general rule is I'm going to charge my

00:59:20.960 --> 00:59:26.799
phone anyway so plugging in the watch

00:59:24.240 --> 00:59:30.960
right next to it doesn't really make it that big of a deal um there have been

00:59:28.720 --> 00:59:35.040
several instances where I've like taken off my watch on my dresser instead of my

00:59:33.440 --> 00:59:38.960
nightstand where my chargers are and forgot about it and woke up the next

00:59:36.720 --> 00:59:43.520
morning and had a dead watch and got well that's stupid uh and wished that it

00:59:42.079 --> 00:59:48.880
had had longer battery life but I wish that for my phones every day as well

00:59:46.319 --> 00:59:54.480
right so but does does better wireless charging address all of this in the next

00:59:51.599 --> 00:59:58.799
six to 18 months anyway depends on what what it is like so wireless charging

00:59:57.280 --> 01:00:01.440
would help right because the main problem with with the Galaxy Gear Live

01:00:00.400 --> 01:00:05.359
at least is that it doesn't have a standard USB port for charging yeah it

01:00:03.920 --> 01:00:10.720
has that stupid cradle right it's got the cradle and it has the cradle because of the water resistant necessary like

01:00:09.760 --> 01:00:15.440
you know you don't want to ruin your watch when you wash your hands yeah so

01:00:13.599 --> 01:00:18.240
uh you know not h only having that one charger means I don't have one at the

01:00:16.720 --> 01:00:24.640
office I don't have one in my car and I don't have one at the house all at the

01:00:19.760 --> 01:00:26.160
same time um scrub yeah exactly yeah i

01:00:24.640 --> 01:00:32.079
don't know if you can buy them extra but I'm sure you can uh but I forgot the

01:00:28.799 --> 01:00:34.720
question now is is a day of battery life

01:00:32.079 --> 01:00:40.440
okay it's okay like it sucks but I would like my phone to go longer as well but

01:00:37.680 --> 01:00:46.000
we all made this sacrifice when I had a Blackberry i could go awesome i could go

01:00:43.040 --> 01:00:52.319
three days yeah on a phone right my old Nokia brick yeah i could I decided to

01:00:49.200 --> 01:00:54.720
sacrifice um features and functionality

01:00:52.319 --> 01:00:59.440
for battery life and now as as people in this office would be able to attend to

01:00:56.960 --> 01:01:03.280
uh I I am desperately looking to go the other direction without sacrificing

01:01:01.359 --> 01:01:07.359
features like I have a GS4 now the battery is getting old uh it's it's

01:01:05.359 --> 01:01:10.240
starting to to lower its battery life i would love to have a phone with the same

01:01:08.720 --> 01:01:14.400
level of performance and feature set that has like two days of battery life

01:01:12.559 --> 01:01:17.760
don't give me a phone that has new stuff i don't necessarily want the new stuff

01:01:16.559 --> 01:01:21.920
right i want a phone that's going to last me and if I get drunk and pass out

01:01:20.559 --> 01:01:25.599
at a friend's house I don't wake up with a dead phone all the time not that I do

01:01:23.920 --> 01:01:29.440
that all the time just you know just in case question for you and you know what

01:01:27.680 --> 01:01:34.880
we we've got to do a we've got to do a straw poll on this let me just uh let me

01:01:32.319 --> 01:01:42.480
just get a get a straw poll going here do you think that anyone will have the

01:01:38.960 --> 01:01:46.079
balls to do a 2-day or a 3-day battery

01:01:42.480 --> 01:01:48.079
phone and sacrifice the thinness and

01:01:46.079 --> 01:01:52.720
sexiness that we've come to expect i was I was really hoping Apple would do it

01:01:50.319 --> 01:01:58.640
because Apple's been such a pioneer when it comes to battery life i was really

01:01:55.359 --> 01:02:00.680
hoping that the 6 series would maintain

01:01:58.640 --> 01:02:05.040
the same thickness as the older phones compromise on weight a little bit

01:02:03.280 --> 01:02:08.960
add a little bit of weight and put a similar size battery to what a flagship

01:02:07.359 --> 01:02:13.680
Android phone is doing so maybe where the 6 Plus would have had a a 3,200

01:02:11.760 --> 01:02:19.440
milliamp battery like something like an Xperia Z2 does where Apple with the way

01:02:17.200 --> 01:02:22.960
that they sip battery especially when idle or with tasks running in the

01:02:20.960 --> 01:02:28.319
background compared to Android would have legitimately been able to deliver a

01:02:25.359 --> 01:02:31.280
a multi-day at least a two-day battery do you think anyone's going to have the

01:02:29.599 --> 01:02:35.760
balls or are we going to have to wait for Project Aura and for people to just

01:02:33.520 --> 01:02:41.599
build it themselves out of modular components i I I I want to believe that

01:02:38.440 --> 01:02:43.680
somebody would have the guts to do that

01:02:41.599 --> 01:02:50.240
because it's not really that I mean as many Android phones as there are out

01:02:45.680 --> 01:02:54.240
there as many options as HTC makes or uh

01:02:50.240 --> 01:02:57.520
Samsung makes like take the Galaxy S5

01:02:54.240 --> 01:02:59.440
and call it you know the Galaxy S5

01:02:57.520 --> 01:03:04.319
business edition or something like that right and you make it a half inch

01:03:02.319 --> 01:03:07.599
instead of whatever else right you maybe make it a quarter inch thicker and you

01:03:05.599 --> 01:03:13.359
give it like a 4500 milliamp hour battery or something like that right uh

01:03:10.160 --> 01:03:16.000
I would buy that phone because I have

01:03:13.359 --> 01:03:20.400
normalized pockets i'm not you know I don't have an issue with uh uh the size

01:03:18.240 --> 01:03:24.640
of phones and I don't carry a purse or anything but I'm okay i would much

01:03:22.240 --> 01:03:29.599
rather sacrifice that um you look at the the super thin iPhone 6 and 6 Plus and

01:03:27.680 --> 01:03:35.119
they're beautiful looking designs they really are beautiful but if add two

01:03:33.599 --> 01:03:40.160
millimeters to it three millimeters to it four millimeters to it how much do you extend that battery life i'd love to

01:03:38.160 --> 01:03:45.280
see some kind of math on that and I'm sure you could do it without too much

01:03:42.640 --> 01:03:48.960
work right how if you add 4 mil of battery to that device what does that

01:03:47.359 --> 01:03:53.039
equate to in milliamp hours and then what does that equate to in actual real

01:03:50.480 --> 01:03:56.880
world usage um and the thing is how many people have MPHI right people buy MPHI

01:03:55.440 --> 01:04:02.880
all the time and it makes your phone a brick they do it for battery life purposes

01:04:00.319 --> 01:04:07.520
exactly and I mean the thing is that you know these these companies a lot of the

01:04:04.720 --> 01:04:11.520
time I feel like guys like Samsung in particular they just kind of throw

01:04:09.440 --> 01:04:14.480
things at the wall and and hope that they stick and they don't really even

01:04:12.960 --> 01:04:19.599
seem to know what they're doing a lot of the time where they just release a dozen

01:04:16.960 --> 01:04:25.359
galaxies and then one of them will have sensient life in it you know what I mean

01:04:21.920 --> 01:04:27.440
and it seems like we're giving it to

01:04:25.359 --> 01:04:31.200
them this time we're handing them the solution consumers are demanding this

01:04:29.839 --> 01:04:35.039
and with the way that charging technology has improved over the last

01:04:32.880 --> 01:04:39.599
few generations where you can charge high-capacity batteries much more

01:04:37.280 --> 01:04:43.520
quickly are we are they just not doing it because it adds so much to the bomb

01:04:41.599 --> 01:04:47.599
cost of the phone like is that the issue we're seeing here um probably some of

01:04:46.000 --> 01:04:52.400
that is right batteries aren't necessarily cheap um and it's uh you

01:04:51.280 --> 01:04:58.160
know depending on how many you're going to make it it's an upfront expense right

01:04:55.520 --> 01:05:03.599
and if it's a huge flop you have to eat that cost um I was one of the people

01:05:00.720 --> 01:05:09.119
that when I had a Palm Prix way back in the day like I bought You're so young

01:05:05.520 --> 01:05:11.599
and hip i know i bought like the the

01:05:09.119 --> 01:05:16.400
giant uh I forget who made that battery the off-brand CDIO

01:05:14.240 --> 01:05:20.000
sure never heard of it off brandand battery ext it was like a a big battery

01:05:18.480 --> 01:05:23.440
and it had a different back on it that was way fatter than everything else and

01:05:21.760 --> 01:05:28.400
I thought "This is dumb looking but man I can go two and a half days uh without

01:05:25.920 --> 01:05:31.039
having to recharge the phone." So this types of things still exist i'm trying

01:05:29.680 --> 01:05:37.599
to think was the last phone I did that on uh the Nexus uh 5 no no Nexus 4

01:05:35.760 --> 01:05:42.400
Google Nexus one of those i bought like a an extra-large battery that had to

01:05:39.280 --> 01:05:44.079
have a different back case to it um that

01:05:42.400 --> 01:05:47.680
made it look dumb because it was very obviously not what it shipped with uh

01:05:46.000 --> 01:05:52.079
but it was a much more usable device because of it you know at least okay I'm

01:05:50.400 --> 01:05:56.960
going to I'm going to end this topic on on with an anecdote here at least it's

01:05:54.880 --> 01:06:02.799
not as bad as the really old days did you ever have a pocket PC uh I did yes

01:06:00.880 --> 01:06:07.200
okay did you ever have one of the pocket PCs that actually didn't have persistent

01:06:05.599 --> 01:06:14.480
storage i don't think I did have one of those i

01:06:10.400 --> 01:06:16.720
had an HP pack that actually the the

01:06:14.480 --> 01:06:22.559
onboard storage not the RAM I'm talking storage the onboard storage did not

01:06:19.920 --> 01:06:28.319
retain data if the device fully discharged and so it actually it

01:06:25.920 --> 01:06:32.160
actually had two um it actually had two battery meters on it there was like the

01:06:30.000 --> 01:06:37.520
usable battery meter and then there was the reserve auxiliary battery meter so

01:06:34.559 --> 01:06:41.280
once you ran out of battery it would the device would power off just like it was

01:06:39.119 --> 01:06:46.720
off but then it had a reserve there that would last for about 5 days I think or

01:06:43.920 --> 01:06:51.280
something like that and if you you lost all of that you had to plug it in and

01:06:48.160 --> 01:06:52.720
charge it and it was factory reset wow i

01:06:51.280 --> 01:06:57.520
did have an iPad i don't know if I ever had one that did that but I would have I

01:06:55.359 --> 01:07:02.200
don't remember that ever happening so I don't know that's weird yeah it was it

01:06:59.680 --> 01:07:07.480
was super super stupid um speaking of super super stupid

01:07:05.760 --> 01:07:14.160
I'm going to do our sponsor segments here so what's not stupid is linda.com

01:07:12.079 --> 01:07:18.960
you can actually make yourself smarter actually you okay I I shouldn't say that

01:07:16.880 --> 01:07:22.400
making yourself smarter is a little bit is a little bit challenging you can

01:07:20.480 --> 01:07:26.960
actually increase your IQ by exercising your brain and you can exercise your

01:07:24.480 --> 01:07:31.039
brain by using linda.com to learn new things but linda.com is more about

01:07:29.039 --> 01:07:35.359
acquiring new skills whether that new skill is digital photography or whether

01:07:33.760 --> 01:07:39.680
that new skill is something like video editing or programming you can learn all

01:07:37.920 --> 01:07:43.920
kinds of great stuff on linda.com courses are being refreshed all the time

01:07:41.839 --> 01:07:47.760
they're taught by experts they have guided uh paths that you can follow

01:07:46.079 --> 01:07:51.039
through to to learn new things and become truly proficient at them to the

01:07:49.440 --> 01:07:55.280
point where you might even get a new career out of it it's super affordable

01:07:53.359 --> 01:07:59.920
and if you're not sure if it's right for you all you got to do is go to

01:07:57.160 --> 01:08:04.240
linda.com/wanchow for a free 7-day trial it's all you can eat you can try out as

01:08:02.160 --> 01:08:09.920
much different stuff as you want and if you don't find anything that excites you

01:08:06.799 --> 01:08:12.160
then hey you cancel it if you do find

01:08:09.920 --> 01:08:17.279
stuff that excites you then great sign up for a membership and start learning

01:08:13.839 --> 01:08:19.279
we've actually got now three employees

01:08:17.279 --> 01:08:24.960
at Linus Media Group who use the skills they learned with linda.com daily at

01:08:22.000 --> 01:08:28.799
their jobs so it really does work it's really awesome it's one of the actually

01:08:26.960 --> 01:08:33.440
it's one of the sponsors that I get the most uh testimonials about people

01:08:31.359 --> 01:08:37.359
tweeting at me hey I'm on linda.com thanks for the recommendation it's

01:08:34.560 --> 01:08:42.000
awesome so there you go now this one Phantom Glass I don't get nearly as many

01:08:40.319 --> 01:08:47.120
people telling me that they have it and it's amazing um so my guess is that you

01:08:45.520 --> 01:08:51.839
guys haven't tried it yet because it really is awesome i've got phantom glass

01:08:49.520 --> 01:08:57.040
on my 1m8 you would never know it from touching it i was actually showing this

01:08:53.759 --> 01:08:58.719
to someone um where was I it was it was

01:08:57.040 --> 01:09:03.679
at one of the factory tours yeah it was at Sennheiser we were talking about

01:09:00.560 --> 01:09:06.960
using highquality materials in in

01:09:03.679 --> 01:09:09.520
hardware and uh for some reason yes we

01:09:06.960 --> 01:09:13.679
were talking about some device that had a touch sensitive glass thing glass

01:09:12.239 --> 01:09:17.679
panel on it that was in the room where we were getting our presentation and I

01:09:16.159 --> 01:09:22.159
forget how we got on the topic but they were talking about how screen protectors

01:09:19.440 --> 01:09:28.239
or really anything but Gorilla Glass or similar high-grade glass coatings really

01:09:24.679 --> 01:09:29.920
feels awful when you're using it and uh

01:09:28.239 --> 01:09:33.759
so I pulled up my phone and I went "Well I bet you don't know that I actually

01:09:31.440 --> 01:09:37.040
have a screen protector on here that's uh that's made of Gorilla Glass." So the

01:09:35.520 --> 01:09:41.279
way that it works and we did a review video of it that ended up being the

01:09:39.520 --> 01:09:45.600
springboard for the sponsorship relationship because I loved the product

01:09:43.520 --> 01:09:48.480
so much that we decided to reach out to them and go "Well hey should we work

01:09:46.960 --> 01:09:52.799
together?" Because I'm totally willing to endorse this stuff it's freaking

01:09:50.000 --> 01:09:57.120
awesome it's got a nano coating on the backside that's actually removable and

01:09:55.040 --> 01:10:00.800
can be reapplied if for whatever reason you wanted to do that but it never comes

01:09:59.120 --> 01:10:04.320
up on its own it's actually quite hard to take off the only reason I took it

01:10:02.320 --> 01:10:07.360
off once was cuz when I was putting it on in the first place I put it on in the

01:10:05.920 --> 01:10:11.679
wrong spot and I was like "Oh crap there's no way I'm going to be able to take it off put it back on it's actually

01:10:09.760 --> 01:10:16.560
going to work." It did and then the front of it has the same olophobic

01:10:14.520 --> 01:10:21.040
scratchresistant properties as Gorilla Glass 3 because that's exactly what it's

01:10:18.960 --> 01:10:24.640
made of the only thing you give up is that there is going to be a slight ridge

01:10:22.719 --> 01:10:28.320
around the edges of the screen but it's thin enough at least that you can use it

01:10:26.400 --> 01:10:32.480
with most cases in fact I think they advertise all cases but I I hate to say

01:10:30.880 --> 01:10:35.920
that cuz I'm sure someone somewhere will find a case that it doesn't work with

01:10:34.159 --> 01:10:40.640
but it'll work with most aftermarket cases without any gaps or any sort of

01:10:39.120 --> 01:10:44.239
any sort of weirdness so guys check it out

01:10:42.280 --> 01:10:48.880
store.fantom.glass they're actually uh they're going to be sponsoring us at CES

01:10:46.080 --> 01:10:52.800
this year and uh we're going to be doing either I'm not quite sure which it'll be

01:10:50.800 --> 01:10:57.040
yet but we're either going to do a dedicated video where Luke and I run

01:10:54.960 --> 01:11:01.600
around just going into booths and rubbing our phones on crap and getting

01:10:58.960 --> 01:11:05.199
people's reactions uh or we're going to do uh we're just going to do that

01:11:03.199 --> 01:11:10.159
randomly during interviews with people and just kind of cut that together into

01:11:07.120 --> 01:11:12.400
a funny montage because it's that

01:11:10.159 --> 01:11:16.560
protective not only is it very scratch resistant but you can actually replace

01:11:14.080 --> 01:11:19.760
it and your screen underneath will be perfect of course still just like any

01:11:18.000 --> 01:11:23.199
other screen protector except that it doesn't look like ass and feel like ass

01:11:21.840 --> 01:11:28.719
because you know if it looks like ass and feels like ass it's probably

01:11:25.400 --> 01:11:30.080
ass that whole that duck saying looks

01:11:28.719 --> 01:11:35.920
like a duck and quacks like a duck anyway the point is I think we should move on to our next topic here thanks to

01:11:32.880 --> 01:11:37.600
our sponsors linda.com and Phantom Glass

01:11:35.920 --> 01:11:42.159
and will you will you promise to wear a costume when you do that video i

01:11:40.000 --> 01:11:46.870
probably should what what would be like a like like a like a ghost costume like

01:11:44.400 --> 01:11:49.939
phantom glass

01:11:50.159 --> 01:11:56.239
sure maybe Pac-Man ghost you know there you go maybe maybe something more

01:11:54.159 --> 01:12:02.920
comical i don't think people mostly cosplay at CES but we could start that

01:11:58.640 --> 01:12:02.920
trend you could try you could try

01:12:03.440 --> 01:12:09.760
yeah would you do it if we did it would you cosplay CES all your meetings and

01:12:08.239 --> 01:12:16.239
all your show floor visits probably wouldn't i pro probably would not all my

01:12:14.000 --> 01:12:20.880
meetings i don't know maybe once or twice but maybe not all of them i go to

01:12:19.280 --> 01:12:24.719
all the parties with you dressed up like that how's that speaking of Glass Fnod

01:12:23.280 --> 01:12:28.480
posted this on the forum the original article is from Digital Trends i'm just

01:12:26.560 --> 01:12:35.280
going to go ahead and screen share here google Glass can now add closed captions

01:12:32.320 --> 01:12:38.400
to real life absolutely fascinating technology i mean I think we all saw

01:12:37.040 --> 01:12:44.880
stuff like this coming it's just augmented reality that's all it really

01:12:41.199 --> 01:12:48.159
is but the fact that we're getting there

01:12:44.880 --> 01:12:50.640
with this frankly very rudimentary

01:12:48.159 --> 01:12:56.719
hardware that we have now is extremely exciting so the idea is that you would

01:12:53.040 --> 01:12:58.800
be able to um maybe not necessarily

01:12:56.719 --> 01:13:03.199
transcribe an entire conversation perfectly for someone who is let's say

01:13:01.199 --> 01:13:06.640
completely completely deaf has no hearing in either ears but if you've got

01:13:05.120 --> 01:13:10.120
someone who's hard of hearing and misses a word here and there or even in some

01:13:08.800 --> 01:13:14.719
cases people who speak different languages you would be able to

01:13:12.880 --> 01:13:20.239
communicate with each other that's really the killer feature for this right

01:13:16.840 --> 01:13:23.120
is going out of the country i I go to

01:13:20.239 --> 01:13:28.000
China i don't speak Mandarin uh you know I can have a conversation with somebody

01:13:24.800 --> 01:13:29.520
if we are both wearing these devices um

01:13:28.000 --> 01:13:32.719
it requires it's going to require more processing than we have today and it's

01:13:31.360 --> 01:13:36.239
you know needs to be perfected to a certain degree but and roaming needs to

01:13:34.719 --> 01:13:40.960
go away because uh you're not going to be using a feature like this without your internet connection that's true

01:13:39.280 --> 01:13:47.520
that's true um well it's got a long way to go yet but it does um I would also

01:13:45.280 --> 01:13:50.800
they had something when I I had Glass initially and and used it for a little

01:13:49.280 --> 01:13:55.840
while and it had the ability to translate um signs right there was an

01:13:54.320 --> 01:14:01.679
app that could do that right where the idea was road signs or street signs you

01:13:59.120 --> 01:14:04.000
know that gave mileage or or directions or street names or something like that

01:14:02.800 --> 01:14:07.280
in a different language would be translated for you and it worked okay

01:14:06.000 --> 01:14:13.760
but it was something like where you need you needed to be very still and you had to point the camera at a very specific

01:14:10.480 --> 01:14:16.880
way and uh uh this this seems to be like

01:14:13.760 --> 01:14:20.239
to be a more useful implementation of

01:14:16.880 --> 01:14:23.040
that idea right because I mean Google if

01:14:20.239 --> 01:14:28.480
anybody has uh voiceto text transcription down it should be Google

01:14:25.679 --> 01:14:31.760
right all the Google voicemails they do all the close captioning they do on

01:14:29.920 --> 01:14:35.840
YouTube videos uh and all the corrections that they do for that stuff

01:14:34.080 --> 01:14:40.400
they should be pretty good at that you would think that i actually had a pretty

01:14:37.440 --> 01:14:44.800
stupid experience with uh with uh Google Now earlier today i think I asked for

01:14:42.560 --> 01:14:48.960
directions somewhere and it Googled directions to wherever like it still

01:14:46.640 --> 01:14:53.520
does that for me about 40% of the time i hate Google Now really infuriating it's

01:14:51.679 --> 01:14:58.880
It's way better than what Siri does we have this debate in our office all the

01:14:55.120 --> 01:15:00.719
time no no no no yeah it is i'm sure the

01:14:58.880 --> 01:15:05.440
audience doesn't want me to to do the whole Siri versus Google Now thing again

01:15:03.199 --> 01:15:08.800
but I Why don't we just say this i disagree with you and we'll have this

01:15:07.199 --> 01:15:13.360
debate next time you're on the show okay okay all right fair enough all right

01:15:11.280 --> 01:15:18.960
i'll I'll bring my best Google Now phone and we'll have a a a speech off we'll

01:15:16.880 --> 01:15:22.560
have a speech off that what I would actually be interested in that we'll see

01:15:20.239 --> 01:15:26.800
if we can stump each other's phones yeah that'd be good that might be kind of fun

01:15:25.199 --> 01:15:32.400
all right speaking of things that are fun uh customer information compromised

01:15:29.280 --> 01:15:34.560
in an AT&T insider breach this was

01:15:32.400 --> 01:15:37.679
originally posted by Dietrich W on the forum and the original article here is

01:15:36.159 --> 01:15:45.679
from CNET i'm just going to pop this up on the screen at&t warns 1,600 customers

01:15:42.080 --> 01:15:48.719
of data breach so basically this wasn't

01:15:45.679 --> 01:15:51.679
a systemic problem necessarily it wasn't

01:15:48.719 --> 01:15:56.159
that uh AT&T was intentionally collecting this information and sharing

01:15:53.360 --> 01:16:01.199
it with you know crappy folks or whatever the case may be this was a case

01:15:58.320 --> 01:16:07.600
where a rogue employee went and stole this information and I think this

01:16:04.400 --> 01:16:10.320
underlines um one of the real issues

01:16:07.600 --> 01:16:15.120
with data collection the issue is not necessarily the terms of service because

01:16:12.640 --> 01:16:20.679
this is clearly against AT&T's privacy policy the issue is that if you're

01:16:17.920 --> 01:16:26.320
collecting the information someone somewhere may have access to it and

01:16:24.320 --> 01:16:32.800
they're the problem that's not a policy issue that's just a people are people

01:16:29.280 --> 01:16:34.159
and bad people are bad people um so I

01:16:32.800 --> 01:16:40.320
don't I don't really know what to say the employees been fired and everyone affected has been contacted but uh I

01:16:38.239 --> 01:16:43.760
mean what do what do you think Ryan do should we should we go tinfoil hat here

01:16:42.400 --> 01:16:47.199
are we afraid of people having our information or should we should we trust

01:16:45.679 --> 01:16:52.400
companies i mean this is really the oldest form of this that you'll ever

01:16:49.120 --> 01:16:54.719
find right go back i mean bankers have

01:16:52.400 --> 01:16:59.600
had access to your money for a hundred years right and and and and this this is

01:16:57.600 --> 01:17:05.440
not going to go away if anything the computerization of these processes will

01:17:03.120 --> 01:17:10.320
take people out of the process out of the out of the pipeline of these things

01:17:08.560 --> 01:17:14.400
occurring and so you have less instances of this that doesn't make you more safe

01:17:11.760 --> 01:17:20.239
of course as we've seen data breaches in other ways um this is more of a hey you

01:17:17.520 --> 01:17:24.000
had a really crappy employee uh but that could happen at a hospital that could

01:17:21.600 --> 01:17:28.480
happen at a bank that could happen at a a restaurant where the waitress has a

01:17:26.080 --> 01:17:33.760
skimmer in her pocket right like right yep th those are all personnel issues

01:17:30.640 --> 01:17:36.320
and there's always going to be uh people

01:17:33.760 --> 01:17:41.440
in this world that are trying to do those types of things right so so would

01:17:38.159 --> 01:17:42.960
you prefer a digital system versus a

01:17:41.440 --> 01:17:50.080
human intervention system in this case then man I don't know i got to say the

01:17:46.560 --> 01:17:53.040
the the scope of the theft here is so

01:17:50.080 --> 01:17:58.920
small compared to what happens when something goes wrong with a digital

01:17:55.679 --> 01:18:01.120
system true they only got 1,600 right

01:17:58.920 --> 01:18:06.000
1,600 people had their information compromised and it sucks to be you like

01:18:03.120 --> 01:18:10.960
it sucks for those people but we're not talking 100,000 or 160,000 people with

01:18:09.440 --> 01:18:16.560
information compromised like what will happen uh who was it crap was it Target

01:18:14.560 --> 01:18:19.679
that had a major problem with their POS system thousands and thousands of

01:18:18.159 --> 01:18:23.679
customers information was compromised what was it credit card numbers yeah I

01:18:21.840 --> 01:18:27.679
think so yeah can't remember the exact details but

01:18:25.840 --> 01:18:32.159
I recently it was Home Depot and Jimmy John's like my my my bank called me a

01:18:31.040 --> 01:18:35.840
couple weeks ago and said "Hey we're sending you a new checking account card." And I was like "Why?" He said

01:18:34.320 --> 01:18:38.960
"Well we looked and you've shopped at Jimmy John's and Home Depot in the last

01:18:37.440 --> 01:18:43.760
60 days so you're getting a new card." I was like "That sucks but hey thanks for

01:18:41.360 --> 01:18:47.280
being proactive about it I guess uh it's it's interesting like there's uh there

01:18:45.520 --> 01:18:51.199
was a service that I saw a Kickstarter for recently i can't remember the name

01:18:48.560 --> 01:18:56.239
of it where it automatically generated a unique credit card number for each

01:18:53.600 --> 01:18:59.840
merchant that you shopped at for example and then if that merchant ever had a

01:18:58.159 --> 01:19:04.239
security issue that number would be automatically canled right and nobody

01:19:02.320 --> 01:19:07.360
else had access to it so you didn't have to go through and change your card

01:19:05.520 --> 01:19:10.560
information and change who pays your bills or or change all those other

01:19:09.040 --> 01:19:13.880
companies just because one merchant screwed up uh it was a interesting idea

01:19:12.719 --> 01:19:18.560
i don't know exactly how it worked necessarily uh but that that really

01:19:17.120 --> 01:19:21.520
interesting yeah i I'm trying to remember what it was called uh I'm sure

01:19:20.159 --> 01:19:29.199
somebody in the chat will will know eventually level I want to say level uh

01:19:25.800 --> 01:19:31.840
uh level credit card i don't remember

01:19:29.199 --> 01:19:35.920
what it was um but it was a it was a Kickstarter that basically had this

01:19:33.920 --> 01:19:40.000
service right so anywhere you shopped online or even if you called somebody on

01:19:38.080 --> 01:19:44.000
the phone you could generate a unique number for that merchant through their

01:19:42.080 --> 01:19:47.520
app and and give it to them that way obviously if you have to swipe your card

01:19:45.280 --> 01:19:51.280
I don't think that would work right but um it seemed like a good idea be cool i

01:19:49.760 --> 01:19:54.719
mean I think we're going to have an issue with there only being so many

01:19:53.120 --> 01:19:59.760
credit card numbers available and we might have kind of an IPv4 versus IPv6

01:19:58.080 --> 01:20:04.560
type of issue here we're going to have to start adding like um you know alpha

01:20:03.120 --> 01:20:10.480
characters to credit card numbers i mean this is going to happen eventually anyway but I mean I would that's a

01:20:09.040 --> 01:20:16.239
really interesting approach it would have to be done by more than just one app maker like it would have to be the

01:20:14.320 --> 01:20:21.040
banking system actually implementing this at a much higher level where each

01:20:18.080 --> 01:20:24.880
individual has you know a thousand or tens or even hundreds of thousands of

01:20:22.800 --> 01:20:30.159
potential credit card numbers applied to them and that would be a much faster way

01:20:27.199 --> 01:20:33.600
to uh to narrow down data theft and uh and particularly financial data theft i

01:20:32.320 --> 01:20:37.120
think it would be much less likely to happen in the US than Canada though just

01:20:35.600 --> 01:20:40.800
because our central banking system allows us to do pretty much everything

01:20:38.880 --> 01:20:46.000
faster than you guys you know whether it's uh chip based cards or even uh or

01:20:43.920 --> 01:20:49.440
even pins versus signatures and all that kind of stuff

01:20:47.840 --> 01:20:54.480
yeah we don't have chip and pin here yet they always say it's coming soon but

01:20:51.360 --> 01:20:55.920
yeah sure whatever i I encountered one

01:20:54.480 --> 01:20:59.840
and this is actually kind of a funny story uh if you don't mind if I just

01:20:57.600 --> 01:21:04.080
kind of sure amble for a bit here i was down at PAX and I was on my way back and

01:21:02.400 --> 01:21:07.040
I realized I didn't have enough gas to get home so I wanted to get something

01:21:05.840 --> 01:21:12.480
while I was in the city i went to the gas station and I I went to pay at the

01:21:09.840 --> 01:21:16.719
pump and it prompted me for my zip code of course I don't have a zip code i'm

01:21:13.840 --> 01:21:19.679
not American so I was like "Oh crap write this this song and dance again."

01:21:18.239 --> 01:21:23.600
So I have to go back I have to go into the station and I go to pay the guy he

01:21:22.159 --> 01:21:28.880
asks "How much do you want?" I say "Oh I don't know man phillip." And so I he he

01:21:26.480 --> 01:21:33.120
hands me the card thing and I go to swipe it and he says "Oh no no don't."

01:21:31.520 --> 01:21:36.560
Right we're having a conversation before this and he asks where I'm from i tell

01:21:34.719 --> 01:21:42.000
him I'm from Canada right so he hands me the thing i go to swipe it and he says

01:21:39.360 --> 01:21:46.239
"I know you're not Canadian." And I kind of went "What?" He says "No I I know

01:21:44.719 --> 01:21:49.920
you're not Canadian." I'm like "No I'm I'm Canadian." And like here here we've

01:21:48.640 --> 01:21:54.639
got someone I'm trying to use a credit card with telling me they don't believe

01:21:52.320 --> 01:21:59.199
my identity so I I I feel like I have a bit of a problem here right now and so

01:21:57.199 --> 01:22:04.000
he says "Do you know how I know?" I'm like "Sure humor me." He goes "Because

01:22:02.239 --> 01:22:09.920
you didn't try to put the chip reader in." And I go "Well okay Sherlock i'm in

01:22:08.159 --> 01:22:14.560
America where they generally don't have chip readers." And so I went to swipe it

01:22:12.960 --> 01:22:19.080
it's really You're not that much of a detective so he but he looked at my ID

01:22:16.800 --> 01:22:26.239
really closely wow i was just like "Okay whatever man

01:22:23.600 --> 01:22:29.120
we'll we'll get those one day sure you guys will catch up to you guys will

01:22:27.520 --> 01:22:33.199
catch up to Canada someday good luck with that story of our life." Speaking

01:22:31.040 --> 01:22:38.639
of catching up with Canada this segue makes no sense bridgestone releases

01:22:35.440 --> 01:22:41.760
airfree tires you never have to inflate

01:22:38.639 --> 01:22:43.679
this was posted by 13ca 350 on the forum

01:22:41.760 --> 01:22:50.239
and the original article here is from CNET this is actually not the first time

01:22:47.280 --> 01:22:55.360
we've seen any kind of you know airless tire attempted but this is the first

01:22:53.040 --> 01:23:01.040
time that uh Bridgestone is really saying that hey these might actually be

01:22:59.040 --> 01:23:05.679
not that bad this is their second gen tire and if you guys have a look at the

01:23:03.199 --> 01:23:11.600
at the images here on CNET it actually looks pretty cool every part of it is

01:23:08.360 --> 01:23:15.679
recyclable and um shock absorption is

01:23:11.600 --> 01:23:18.199
handled by the by the shape hm of the

01:23:15.679 --> 01:23:22.800
spokes here and uh yeah I wonder do they I'm sure they

01:23:21.360 --> 01:23:28.360
do talk about it because they mentioned shock absorption but like I have run

01:23:25.120 --> 01:23:31.320
flat tires on one of my car and they are

01:23:28.360 --> 01:23:37.840
noticeably less uh let's say good in terms of ride

01:23:34.960 --> 01:23:41.199
quality right uh especially when there's no air in them because I've had a flat

01:23:39.280 --> 01:23:46.000
tire and a run flat before and it's it's very stiff after that so I I imagine I

01:23:43.360 --> 01:23:49.440
mean the design looks pretty cool so they're I'm sure they're taking that

01:23:47.199 --> 01:23:52.960
into consideration yeah they have a replaceable tread on them which is

01:23:51.120 --> 01:23:58.239
another really cool thing i mean this is this looks like as much a sustainability

01:23:55.520 --> 01:24:02.320
improvement as it is a a car maintenance and potentially safety improvement i

01:24:00.800 --> 01:24:05.280
mean I think it'll be a long way before we see any kind of a commercial product

01:24:04.000 --> 01:24:10.239
like something that you would put on a semi-truck like this but for consumer

01:24:08.320 --> 01:24:14.960
vehicles other than the fact that it's so ugly I would never consider putting

01:24:11.920 --> 01:24:18.600
it anywhere near even my car um it's

01:24:14.960 --> 01:24:18.600
pretty exciting technology

01:24:19.199 --> 01:24:25.199
uh you know you could I'm sure they could make it look better they could

01:24:22.400 --> 01:24:30.239
hide the the weird stuff on the side with uh with with you know some kind of

01:24:27.360 --> 01:24:35.840
design return of hubcaps let's do that return of hubcaps yeah yeah we if we hit

01:24:32.880 --> 01:24:41.120
it enough that could probably work and then the return of hubcap theft uh yeah

01:24:38.800 --> 01:24:44.480
okay that too yep or when they fly off on the highway and smash into somebody

01:24:42.800 --> 01:24:48.560
else's windshield there's that too so yeah or that maybe we could have like

01:24:46.320 --> 01:24:52.480
like a really nice plastic hub cap that just looks metal like maybe we'll really

01:24:50.320 --> 01:24:58.719
get the hang of fake metal we'll finally figure that out yeah just paint it it's

01:24:56.080 --> 01:25:03.280
fine so speaking of things that we're finally figuring out um we still haven't

01:25:01.679 --> 01:25:07.880
finally figured out that people want more battery life in their phones but

01:25:05.199 --> 01:25:14.800
HTC and this was posted on the forum by OP Monkey Matthew 78 HTC has finally

01:25:12.400 --> 01:25:19.600
figured out that some people use their selfie cameras more than they actually

01:25:17.120 --> 01:25:23.760
use their other cameras anyway so why don't we just produce a camera that has

01:25:21.760 --> 01:25:31.440
a front-facing camera that's just as good as the back one the HTC1

01:25:26.840 --> 01:25:33.920
M8i has two 13 megapixel cameras one on

01:25:31.440 --> 01:25:40.000
the back on the front it takes 1080p video it even has a two-tone flash on

01:25:37.679 --> 01:25:44.480
the front so you can really take pretty much almost the same quality photos with

01:25:42.960 --> 01:25:50.320
the front camera as you can with the back one

01:25:47.199 --> 01:25:53.440
brian do you take a lot of selfies uh no

01:25:50.320 --> 01:25:56.239
I do not however this makes a lot of

01:25:53.440 --> 01:26:00.320
sense like I think what's funny is I think this makes way more sense than the

01:25:58.159 --> 01:26:04.639
phones that had the tiny screen on the back of it you remember those there was

01:26:02.639 --> 01:26:09.360
Which one was it uh that had a a small screen on the back so you could see what

01:26:07.040 --> 01:26:15.600
you were taking a picture of i remember maybe it wasn't a phone maybe it was a a

01:26:11.360 --> 01:26:18.719
snapshot camera no I um I I had one i

01:26:15.600 --> 01:26:21.840
had a um ah shoot what was it called i

01:26:18.719 --> 01:26:23.120
don't know but the the fact that we even

01:26:21.840 --> 01:26:27.040
went through that process was like I know we'll put a screen on the back and

01:26:25.679 --> 01:26:31.679
when in reality what we should have done is put a better camera on the front i

01:26:29.840 --> 01:26:37.920
guess determines which one was more expensive this is the Samsung Jive i had

01:26:34.880 --> 01:26:39.440
one of these and it was a flip so here's

01:26:37.920 --> 01:26:42.880
the uh here's the camera here i know this is really small image and it had a

01:26:41.360 --> 01:26:48.000
small screen on the front for previewing messages and seeing the time and I

01:26:45.199 --> 01:26:53.360
believe I could also use that front screen to line up photos yeah I think

01:26:51.440 --> 01:26:57.520
there was I think there was like a uh a nonphone

01:26:55.040 --> 01:27:00.960
um snapshot camera that had that as well maybe by Canon or Nikon or somebody that

01:26:59.520 --> 01:27:03.920
had like a little screen on the front right next to the lens so you could see

01:27:02.560 --> 01:27:10.480
what you were pointing it at when you did that um but yeah I this makes way

01:27:08.960 --> 01:27:15.440
more sense so you've got a really nice screen already on the phone and just

01:27:13.199 --> 01:27:19.360
take that camera and add another one I guess and I don't know is this an

01:27:17.040 --> 01:27:22.880
exceptionally expensive phone by any measure i don't know i don't I don't

01:27:21.600 --> 01:27:26.320
think so i don't think it really affected the cost too much at all i'm

01:27:24.880 --> 01:27:30.639
setting up a straw poll here though guys i want to hear from you how many selfies

01:27:28.400 --> 01:27:35.920
do you take per week if you're willing to admit it remember these straw polls

01:27:32.960 --> 01:27:40.960
are anonymous yeah or as anonymous as anything is I guess somewhat anonymous

01:27:39.120 --> 01:27:45.280
um so anyway let's just uh see if there's anything here I have to Okay so

01:27:42.560 --> 01:27:50.560
it's gone quietly on sale in China for the equivalent of

01:27:47.080 --> 01:27:53.120
$652 and will apparently only be a China

01:27:50.560 --> 01:27:57.159
and India release at least for the foreseeable future why do they get

01:27:55.199 --> 01:28:02.000
cooler stuff than us dual SIM better selfie cameras okay at least

01:27:59.920 --> 01:28:07.040
dual SIM is cooler but why do they get better stuff than us uh our cell phone

01:28:04.960 --> 01:28:10.239
carriers are a pain in the ass oh yeah yeah I guess there's that right so it

01:28:08.560 --> 01:28:15.520
kind of it's kind of wild west out there is my understanding so

01:28:12.719 --> 01:28:20.159
all right so it features autofocus um the Oh there's another camera too

01:28:17.360 --> 01:28:25.920
there's the Desire Eye so that one is also a selfie optimized uh optimized

01:28:23.760 --> 01:28:29.280
phone so they're they're both uh they're both coming out now we got to have a

01:28:27.440 --> 01:28:34.719
look at the straw pull this was the one straw pull that I knew I had to do in

01:28:32.159 --> 01:28:40.639
this video wow i bet I can predict the results so

01:28:37.679 --> 01:28:46.000
the number of you that um maybe this is why we're not getting these cameras

01:28:42.400 --> 01:28:48.840
because 83% of you say none you in

01:28:46.000 --> 01:28:55.679
response to I think our audience on this show is uh very different than the

01:28:52.639 --> 01:28:57.280
audience for any of these uh phones uh

01:28:55.679 --> 01:29:01.440
however I know there are a lot of 12year-old girls out there that do this

01:29:00.000 --> 01:29:05.679
all the time because I have a niece that does it and every time she sees me she's like "Oh let's get a picture." and she

01:29:04.159 --> 01:29:10.239
holds it up and she puts it on Instagram and I go I don't know what's going on

01:29:07.440 --> 01:29:14.080
anymore kill me now i'm I'm I'm 32 years old what are you doing to me that type

01:29:11.840 --> 01:29:19.600
of thing uh I don't feel like I should feel this old

01:29:16.080 --> 01:29:22.800
yet yeah yes exactly that uh but I I I

01:29:19.600 --> 01:29:27.040
bet there's a pretty big market for it i

01:29:22.800 --> 01:29:29.520
don't know you can sell anything why not

01:29:27.040 --> 01:29:35.760
and yet we get the selfie phone but not the high high battery capacity phone

01:29:31.760 --> 01:29:37.600
like are you freaking kidding me

01:29:35.760 --> 01:29:42.639
so sad speaking of things that are sad Steam

01:29:39.679 --> 01:29:48.080
releases Canadian pricing some game prices increased others remain the same

01:29:45.679 --> 01:29:53.600
and some games currently unavailable for purchase in Canada no I don't know what

01:29:51.040 --> 01:29:57.520
the issue is with Steam pricing just being in US dollars i mean maybe you

01:29:55.679 --> 01:30:02.400
know what great opportunity to do a Twitter blitz guys hit me at Linus Tech

01:29:59.760 --> 01:30:07.679
and let me know if you can think of some reason why it's not perfectly okay if

01:30:06.480 --> 01:30:11.120
ultimately they're just going to be converting the pricing and then

01:30:09.760 --> 01:30:15.440
displaying it in your own native currency anyway why it matters at all

01:30:13.760 --> 01:30:19.040
that they don't just have US pricing because at least if it's a straight

01:30:16.800 --> 01:30:23.600
conversion it's ultimately up to my credit card uh my credit card company

01:30:22.080 --> 01:30:28.000
how much I'm paying in terms of fees which is usually not more than a couple

01:30:25.360 --> 01:30:31.679
percent um over whatever the the nominal exchange rate is that you would get at

01:30:29.600 --> 01:30:35.560
the bank why why do I need them to display it in my currency i mean they

01:30:32.960 --> 01:30:40.400
were already displaying a conversion um well okay no no I don't think they

01:30:38.080 --> 01:30:45.920
did actually but whatever xe.com is not exactly a difficult site to remember

01:30:43.199 --> 01:30:51.360
what so before this you just purchased it in US dollars right yeah and then my

01:30:48.239 --> 01:30:52.920
my credit card statement would say you

01:30:51.360 --> 01:31:00.239
know 5721 Canadian $54.99 US in brackets now

01:30:57.199 --> 01:31:03.199
you said that there were some games that

01:31:00.239 --> 01:31:06.320
were no longer available after this yeah uh I don't understand why that would be

01:31:04.880 --> 01:31:10.400
the case but they're probably going to get it fixed but my guess would be that

01:31:08.880 --> 01:31:15.280
they rolled it out and it would have to do with something like agreeing with the

01:31:12.800 --> 01:31:18.639
uh with the the game developer on what the price is going to be in the new

01:31:16.480 --> 01:31:22.320
currency for example because a lot of stuff is not actually you're you're

01:31:20.560 --> 01:31:26.239
American you might not know this a lot of stuff is not done just on a straight

01:31:24.400 --> 01:31:30.880
conversion for example books are notorious for this because they'll have

01:31:28.320 --> 01:31:35.280
a cover price right and you probably don't even have the Canadian cover price

01:31:32.960 --> 01:31:41.440
it shows It shows both on our books okay you guys get both as well so you'll see

01:31:37.280 --> 01:31:43.199
$4.99 US $7.99 Canadian sometimes mhm

01:31:41.440 --> 01:31:47.360
significant price differences I suspect i just thought it was the tax for living

01:31:44.800 --> 01:31:52.960
further north i don't know i just No no it's just it's based on some companies

01:31:50.320 --> 01:32:00.840
actually lock their exchange rate as rarely as over multiple years i remember

01:31:56.159 --> 01:32:03.920
back in 200 shoot I think it was 2008

01:32:00.840 --> 01:32:06.960
2009 when the when the currency was all

01:32:03.920 --> 01:32:08.880
over the place um and I forget who it

01:32:06.960 --> 01:32:13.600
was but there was one Canadian company that only redid their um their exchange

01:32:11.360 --> 01:32:17.600
rates I think once every two years or five years or something like that and

01:32:15.280 --> 01:32:22.000
they basically sat there losing money for I think 6 to 10 months before they

01:32:20.000 --> 01:32:27.280
finally wised up and went "Oh this isn't going to change so we should probably do

01:32:23.920 --> 01:32:31.199
something about our pricing." Um so so

01:32:27.280 --> 01:32:34.560
yeah NBA 2K15 went up 16.6% 6% from

01:32:31.199 --> 01:32:36.400
$59.99 to $69.99 um which isn't that

01:32:34.560 --> 01:32:41.920
reasonable overall the transition looks more smooth than when they added euros

01:32:38.560 --> 01:32:45.360
in 2008 um where many games retained the

01:32:41.920 --> 01:32:48.159
same numerical price but just in euros

01:32:45.360 --> 01:32:53.600
when you I'm curious on Steam when you download uh in Canadian packets over

01:32:51.120 --> 01:32:58.080
Steam does it download just as fast as you would expect like does it saturate

01:32:55.199 --> 01:33:02.480
your bandwidth there does it okay yep i mean we're so close i mean we're we're

01:33:00.320 --> 01:33:07.360
like I can spit to Valve i'm closer to Valve than you like

01:33:05.120 --> 01:33:10.719
in terms of server locations there's no there's no penalty for the border and

01:33:08.960 --> 01:33:16.320
the north to south connections are excellent okay yeah like I can play I

01:33:13.520 --> 01:33:21.040
can play on Washingtonbased servers uh in in a game with very very low ping we

01:33:18.880 --> 01:33:24.719
always joke about Jeremy on our podcast uh lives in Vancouver and we always joke

01:33:22.880 --> 01:33:29.840
that whenever he has Skype issues it's because of Border Patrol blocking

01:33:27.360 --> 01:33:34.080
packets across blocking packets the scary thing is that normally I would

01:33:32.480 --> 01:33:37.600
kind of laugh at you and I'd go "Haha Ryan that's a funny joke." Except I with

01:33:36.400 --> 01:33:41.679
all the stuff that's been going on with the NSA in the last year I wouldn't even

01:33:40.239 --> 01:33:45.840
be that surprised to find out that someone is actually manually sorting

01:33:43.360 --> 01:33:49.440
packets at the border well no this one's fine this one's fine this one's fine

01:33:47.120 --> 01:33:52.719
nope not that Linus guy this one's fine yeah now not not this guy who's

01:33:50.960 --> 01:33:58.560
teaagging the other player let's just go ahead and turn these packets off right

01:33:54.320 --> 01:34:00.639
now yeah jackass Canadian

01:33:58.560 --> 01:34:06.400
all right so I've got one more topic that um like to discuss a little bit uh

01:34:03.760 --> 01:34:10.480
this was actually posted by FNOD on the forum uh the original source was a

01:34:09.120 --> 01:34:14.960
little site you may or may not have heard of before called

01:34:12.440 --> 01:34:20.320
pcp.com or something like that i don't know some some American guy runs it or

01:34:17.280 --> 01:34:24.800
something like that um ARM and TSMC

01:34:20.320 --> 01:34:26.639
apparently headed for 10 nanometer

01:34:24.800 --> 01:34:33.280
d what does this mean what's what's going to happen man you know it doesn't

01:34:28.880 --> 01:34:35.800
mean jack uh what the problem is so

01:34:33.280 --> 01:34:41.199
telling Richard Heidi on you yeah well TSMC is a manufacturing facility that

01:34:39.040 --> 01:34:45.600
makes chips for just about everybody AMD on the graphics side and on the

01:34:42.560 --> 01:34:48.159
processor side somewhat um a and also

01:34:45.600 --> 01:34:52.800
NVIDIA and also Apple and others and everybody right um their problem their

01:34:50.800 --> 01:34:56.880
main competitor is actually Intel right Intel fab stuff primarily for themselves

01:34:55.440 --> 01:35:03.920
they have a couple of odd jobs every once in a while so the the issue is is

01:34:59.199 --> 01:35:06.239
we're at 22 nanometer today on Intel's

01:35:03.920 --> 01:35:13.600
front and we're still kind of stuck on 28 kind of 20 nanometer uh on TSMC the

01:35:10.639 --> 01:35:18.320
Apple on Intel's rolled out 14 sort Right broadwell is is 14 right and it's

01:35:16.880 --> 01:35:23.120
just I guess it did kind of just actually start shipping in notebooks uh

01:35:20.719 --> 01:35:29.800
this month so it did you're right um but in and the 20 nanometer from TSMC is

01:35:25.760 --> 01:35:32.719
kind of a it's an odd conversation

01:35:29.800 --> 01:35:36.000
because it's very limited production and it didn't have the benefits that a lot

01:35:34.480 --> 01:35:40.880
of people expected to see for high performance parts that's why the Apple

01:35:38.000 --> 01:35:44.480
A8 is being manufactured on it but no NVIDIA or AMD GPUs are being

01:35:43.040 --> 01:35:51.920
manufactured on it even though you would think those would be the perfect ripe example for what should need a a uh a

01:35:48.639 --> 01:35:53.679
dieice size decrease in process lower

01:35:51.920 --> 01:35:58.800
power consumption faster switching speeds that sounds right up the GPU's

01:35:55.840 --> 01:36:02.800
alley right so uh what what needs to happen now is TSMC and those other

01:36:00.639 --> 01:36:08.080
groups are going into finfet production which is trigate 3D transistors which is

01:36:05.280 --> 01:36:13.679
what Intel introduced in 22nter um and there are still they're still prepping

01:36:10.480 --> 01:36:15.760
like their 16 nanometer finfet parts uh

01:36:13.679 --> 01:36:19.600
TSMC and Global Foundaries and those guys are um and that will be kind of the

01:36:17.920 --> 01:36:24.159
first iteration of it and so I think what happened was uh this was at uh on a

01:36:21.920 --> 01:36:27.840
digit time story kind of came out around the ARM TechCon convention that was

01:36:26.080 --> 01:36:33.120
happening out in Santa Clara that they were hey look we're on track for our 10

01:36:29.760 --> 01:36:34.960
nanometer um taping out possibly in the

01:36:33.120 --> 01:36:40.800
fourth quarter of 2015 and so what a tape out means is that you have you have

01:36:38.400 --> 01:36:47.400
manufactured a chip to a specification that you approve of and so they can

01:36:42.960 --> 01:36:49.679
begin the full manufacturing process uh

01:36:47.400 --> 01:36:53.360
and sometimes you'll tape out two or three revisions before you actually

01:36:50.960 --> 01:36:57.719
start the manufacturing process so right you know that they're talking about end

01:36:54.639 --> 01:37:00.560
of 2015 for 10 nanometer which means

01:36:57.719 --> 01:37:05.040
realistically mid to late 2016 before you actually see parts using that um but

01:37:03.840 --> 01:37:09.360
I think we should be more concerned about how quickly they get to 16 nmter

01:37:07.040 --> 01:37:13.760
and what that actually does will we you know some people predicted that you know

01:37:11.440 --> 01:37:18.800
Maxwell NVIDIA's new chip is built on 28 nanometer um we all thought well six

01:37:17.360 --> 01:37:22.960
months ago that it would be built on 20 nanometer and it wasn't the case uh

01:37:21.119 --> 01:37:27.360
whether it be capacity issues whether it be technology issues some for some

01:37:25.600 --> 01:37:30.480
reason it wasn't built on 20 we I think at this point we all kind of assume that

01:37:28.960 --> 01:37:36.560
they're just going to wait they're going to to leaprog 20 and go down to 16

01:37:33.119 --> 01:37:38.560
whenever that becomes available um AMD

01:37:36.560 --> 01:37:42.560
the rumor is now that their next chip will actually be using 20 nanmter and so

01:37:40.960 --> 01:37:49.360
we'll be able to see a comparison of what a chip can do one way or the other

01:37:45.119 --> 01:37:51.719
uh and we may actually start to see AMD

01:37:49.360 --> 01:37:56.480
and NVIDIA on opposing nodes of uh production right yeah

01:37:55.280 --> 01:38:00.800
that'll be really interesting i mean that hasn't happened for an extended

01:37:58.480 --> 01:38:06.000
period of time in a long time so with AMD at a lower at at a smaller

01:38:03.520 --> 01:38:12.639
manufacturing process than NVIDIA for potentially months right yeah it it's it

01:38:09.600 --> 01:38:16.199
would be very interesting i I Josh who

01:38:12.639 --> 01:38:18.239
is on our show at pcpur.com he is a

01:38:16.199 --> 01:38:21.679
manufacturing guy he knows all about this stuff way more than I do and his

01:38:20.080 --> 01:38:26.320
kind of theory is that the 20 nmter probably doesn't offer a very big power

01:38:24.159 --> 01:38:31.119
consumption or clock frequency advantage over 28 nanometer it's probably very

01:38:28.159 --> 01:38:36.239
small uh and so the complication of moving your product from 28 down to 20

01:38:33.360 --> 01:38:40.239
may not be worthwhile in the long run right so that would be and NVIDIA was

01:38:38.320 --> 01:38:44.719
saying that the that the cost benefit didn't look like it made a ton of sense

01:38:42.080 --> 01:38:47.520
for them as well yeah uh because you know when when they're talking about a

01:38:46.080 --> 01:38:52.480
cost benefit they're not just really talking about the dollar benefit but the

01:38:50.159 --> 01:38:57.280
dollar they have to spend per wafer what your yield is on that wafer determines

01:38:54.560 --> 01:39:02.000
what each GPU's value is and then how much time you have to spend which is you

01:38:58.960 --> 01:39:04.080
know engineering money to convert it

01:39:02.000 --> 01:39:07.520
down to 20 nmter and fix it whereas with 28 they were very comfortable with it

01:39:05.679 --> 01:39:12.159
they already knew it uh and they were able to build I think a pretty

01:39:09.119 --> 01:39:16.080
compelling part based on it so yeah I'm

01:39:12.159 --> 01:39:17.520
I'm surprised at how strong GTX 980 is I

01:39:16.080 --> 01:39:22.000
wasn't I wasn't necessarily expecting them to be able to do that much with it

01:39:19.199 --> 01:39:28.679
without a die shrink um so as much as it's as it's not what I really wanted

01:39:24.560 --> 01:39:28.679
which was uh GM200

01:39:30.320 --> 01:39:37.679
girl can dream right uh it's it's not a bad to wait for 210 just have to wait

01:39:35.119 --> 01:39:41.440
for 210 just wait for GM210 it'll be fine

01:39:39.280 --> 01:39:46.400
fair enough i'm sure it'll be here soon yeah I'm sure i don't know all right

01:39:44.320 --> 01:39:51.760
well I think that's um that's pretty much it what time is it your time right

01:39:48.800 --> 01:39:56.080
now it is 9:18 my time well I'm sure uh I'm sure your wife is

01:39:53.840 --> 01:40:00.400
going to be super thrilled with me and I'll get you know more glares the next

01:39:58.080 --> 01:40:03.679
time I run into her at an event no she was super nice she likes you now now

01:40:02.159 --> 01:40:07.440
that she knows you she's totally fine with it i said "Hey I'm going to go be

01:40:05.280 --> 01:40:12.400
on Linus' show on Friday is that cool?" She said "Oh yeah that's fine." Um you

01:40:10.400 --> 01:40:18.560
know and you did make your show earlier it used to be much later um didn't you

01:40:16.080 --> 01:40:23.119
used to do it 700 p.m pacific instead of 700 p.m eastern yeah I did that was way

01:40:21.760 --> 01:40:28.880
more complicated cuz then I was getting sleepy by the end of it right i'm I'm an

01:40:25.520 --> 01:40:30.480
old man i get tired all right well guys

01:40:28.880 --> 01:40:35.040
thanks so much for watching thanks to our sponsors linda.com and Phantom Glass

01:40:33.199 --> 01:40:38.880
and thanks to our special guest Mr ryan Shrout from PC Purr for those of you who

01:40:37.040 --> 01:40:42.639
are just tuning in later on in the show here Ryan do you want to give them one

01:40:40.239 --> 01:40:46.480
more sort of where to find you i absolutely do i absolutely do so

01:40:44.080 --> 01:40:50.480
pcpur.com is our website with all of our reviews camera self-promoter i'm gonna

01:40:48.719 --> 01:40:54.080
I'm gonna plug my YouTube channel as well because we're on there look you

01:40:52.639 --> 01:40:58.320
have so many more subscribers than me it's not even a competition if you want

01:40:56.000 --> 01:41:01.920
to watch videos about PC hardware our channel is

01:40:59.880 --> 01:41:06.639
youtube.com/pcpur i mean we don't do as cool of videos as Lionus does he doesn't

01:41:04.320 --> 01:41:12.800
walk around on his roof with a 100 foot uh USB cable i did I No I don't I didn't

01:41:09.600 --> 01:41:16.000
do that i did run a 500 foot Ethernet

01:41:12.800 --> 01:41:18.239
cable once okay that worked successfully

01:41:16.000 --> 01:41:22.639
that's almost as cool uh and it got run over by a lawn mower so there was that

01:41:21.119 --> 01:41:26.239
and then it didn't work that's unfortunate go figure so th just those

01:41:25.040 --> 01:41:31.040
places if you I mean if you want to find me on Twitter it's just Ryan Ryan Shrout

01:41:28.320 --> 01:41:34.000
as well so uh anytime you want to have me back on this is fun it's cool i like

01:41:32.560 --> 01:41:39.360
talking with different group i did see a couple people in the Twitter chat asking me to tell you all about the wonders of

01:41:37.520 --> 01:41:44.000
IRC oh oh okay yeah the because you guys use

01:41:41.520 --> 01:41:47.440
IRC for your chat right yeah we do i think it's part of our partner agreement

01:41:45.760 --> 01:41:52.080
with Twitch that we don't use alternate chats fair enough fair enough so there's

01:41:50.320 --> 01:41:55.280
one reason why we might do things the way that we do things something that I

01:41:53.840 --> 01:41:58.960
think viewers a lot of time don't realize is that there's probably a

01:41:57.119 --> 01:42:03.119
hundred reasons behind the scenes why we do something the way that we do it

01:42:00.560 --> 01:42:07.360
versus what's immediately obvious and and apparent but uh yeah that's that's

01:42:05.840 --> 01:42:12.800
that's the reason we don't do it and you know what twitch chat isn't that bad i

01:42:10.239 --> 01:42:17.440
think that I enjoy watching it i enjoy participating in it so I I'm in there i

01:42:15.920 --> 01:42:21.199
My name's popping up every once in a while here and there we go so yeah i see

01:42:19.840 --> 01:42:25.920
a lot of people tweeting about how they hate you and they never want to see you as a guest again so I understand i know

01:42:24.080 --> 01:42:29.440
i get it all the time i see why you're I see why you're trying to invite yourself

01:42:27.440 --> 01:42:32.880
back to try and like counter what they're saying no we'll definitely have

01:42:30.800 --> 01:42:36.960
you back again Ryan thank you very much and uh good night everyone we'll see you

01:42:35.040 --> 01:42:41.040
again same bat time same bat channel next week um I actually don't remember

01:42:39.360 --> 01:42:45.040
who our guest is for next week but I think we might be having Paul and Kyle

01:42:42.800 --> 01:42:48.880
formerly of New Egg TV back so uh stay tuned for that and good night

01:42:51.400 --> 01:43:00.199
everybody sorry it takes a while to switch scenes because uh Oh oh and I've

01:42:56.480 --> 01:43:00.199
got this thing over here

01:43:04.119 --> 01:43:08.880
d ah why is this the one with I got to

01:43:07.119 --> 01:43:14.480
just delete the one with no audio at some point that That would make a lot

01:43:11.679 --> 01:43:18.560
more sense cuz I keep accidentally putting it here and then I never check

01:43:16.000 --> 01:43:23.679
it because I'm usually like throwing myself into my chair here to get the

01:43:21.040 --> 01:43:29.280
show started today I arrived back at the office at 2:30 and I shot an unboxing as

01:43:27.280 --> 01:43:34.080
well as a full line of tech tips and then some B-roll for another one before

01:43:31.440 --> 01:43:39.520
starting the show so like it's just You did good you did fine we did We didn't

01:43:36.480 --> 01:43:42.719
We didn't need a uh a Skype pretest we

01:43:39.520 --> 01:43:44.320
got this stuff down yeah that's right

01:43:42.719 --> 01:43:48.000
skype what could go wrong nothing goes wrong with Skype and turn