Hacker News Reader

Comment by monocasa | Hacker News Reader

Probably got a really good deal on it.

The Tegra X1 was also originally, rumoredly, not meant for Nintendo.

https://nvidianews.nvidia.com/news/nvidia-launches-tegra-x1-...

It was going to be for "Deep Learning," "Computer Vision Applications," "NVIDIA DRIVE car computers," and robots. As we know, outside of some Tesla models, that didn't really happen.

Rumoredly, according to people who have read the leaked Nintendo documents (Modern Vintage Gamer has implied it in replies to comments on his videos), NVIDIA had found the bug with the recovery mode before the Switch's launch; but Nintendo couldn't just move the announced Switch launch date to wait for a chip revision, especially after the Wii U financial performance. So, off it went and they just had to cross fingers and hope nobody found it. Nintendo probably got a good discount for that mistake too.

> As we know, outside of some Tesla models, that didn't really happen.

As YOU know.

The Tegra X1 (which the switch used) was never used in any production automotive application, correct. But you mentioned Tesla, so let's talk about other Tegra generations.

Other Tegra generations were used in Teslas in varying quantities (Tegra 2, 3, and K1). Mercedes has been shipping Tegra in their "MBUX" cars for a few years now as well. A couple of Chinese companies are shipping Tegra via NVD. Volvo, Land Rover, and Jaguar are also going to be shipping it shortly as well.

I don't know why you accuse me as though I said something wrong, and then immediately admit that, yes, the Tegra X1 was never used in any production automotive application. That's what I was talking about - not Tegra as a whole. The only mistake I made was that the Tegra X1 wasn't used in any Tesla models.

This is news for nerds. Precision is important! So they fixed your statement. I found it interesting.

Precision may be important, but is accuracy? ;)

Sorry, I said you were correct, when in fact you weren't.

A whole lot of the switch's design was about driving down costs as much as they could. That's why it has no mic, camera, and didn't get bluetooth headphone support for years after launch. Plus chipmakers really want those console contracts, even if they make a loss on the first few hundred thousand sold, they're assured sales as long as the console sticks around. AMD made out like bandits with the ps4/xbone.

And they're likely making a killing with the Steam Deck.

and soon will be with the PS5 and XBS(S/X) as well, if they aren't already

Sony has broken even with the PS5 in 2021 so I wouldn't be too surprised if on the AMD end of things they are profitable.

Bluetooth audio is kinda ass for gaming anyway unless you have low latency codec support on your source and consumer which is almost never the case.

Sony has their own such codec which is why the audio jack on the PS controllers works so well..

I actually use my AirPods with my Switch all the time, and latency isn’t really noticeable. I’m really glad they added the feature.

I think its fine unless you are playing something like Taiko no Tatsujin. (And you don't really use hit sound when playing hardest level anyway, it's already too late when you hear it) Most games don't really need such immediate response.

The latency of non low-latency(LL) codecs is objectively poor though. Switch supports the SBC code:

> SBC operates at a latency of between 170 and 270 milliseconds (yanked from the web so it may be a bit off)

Stacked on top the typical input latency and you talking somewhere in the neighborhood of 1/4, 1/3, or even pushing 1/2 seconds latency from an input to hearing a sound that plays in response to the input.

An individual might get used to it, or it might not bother them, but it's still there and measurably poor. Even for straight video, Amazon Firestick and other devices will add video latency to compensate.

LHDC and aptX-LL on the other hand can hit 30ms of latency.

Hmm, don't see why leaving out Bluetooth headphone support would save on costs. They enabled it with a software patch so the hardware was always there.

I've assumed the chipset was cheaper and they had to do less development/testing trying to get 8 controllers and a headset working at the same time. (it may support fewer controllers when a headset's connected)

Reply on news.ycombinator.com