Your body does not measure a lack of oxygen. It measures an abundance of carbon dioxide. If you hyperventilate, you can hold your breath considerably longer, not because you actually have any more oxygen in your system, but because you flush out any carbon dioxide in your blood stream, and it takes longer for your body to register that it needs to breathe again.
The Society of Motion Picture and Television Engineers (SMPTE), Engineering Guideline 18-1994. That has since been retracted and replaced with 196M-2003, which now phrases it in terms of picture height, stating you should be no more than four heights back, or roughly seven feet.
They hold their value because people place move value on them than a simple utility. A PC is for utility. A Mac is a fashion item. The equivalent era Mac is no more capable than the equivalent era PC, considering they're made with the same exact parts.
Why 32bpp? Monitors and televisions (and our eyes) only have three color channels, so you have 24-bit, or 30-bit, or 36-bit, for 8, 10, or 12 bits per channel, respectively. When you're talking commercially distributed video, it's almost always YUV420 rather than RGB. You have your one intensity channel at full resolution, and two color channels running at quarter resolution, so a cluster of four pixels shares one color. 24-bit color becomes 12bpp, 30-bit becomes 15bpp, and 36-bit becomes 18bpp. It was originally designed to allow B&W and color television to coexist on the same transmission, but was found to be a good psychovisual compression mechanism. The only time you would use 16-bit or 32-bit color is inside your graphics pipeline prior to compositing, where the three-channel image is accompanied by a fourth transparency channel.
That might have been when the average TV was 20", and standard definition. The recommendation these days is for the horizontal viewing angle to be roughly 30, which would mean you should sit roughly 6.5' back from a 42" television.
That's a very bad idea. It's common for television sets to overscan and crop the video inputs. It's hard to find one that will actually do 1:1 display.
No, he's complaining that the HDTV he bought 12 years ago wasn't supported properly as much as 8-10 years ago.
Because the HD spec kept changing, the early adopters got screwed. Before HD was available to most people, the first two generations of display devices were already obviated. By the time you actually got any HD content the spec had said "oh, you aren't supported at full resolution or with this connector".
Now back to reality, the ATSC spec was published way way back in 1995, and was accepted and standardized by the FCC just a year later, long before even the "enhanced definition" sets hit the market. An HDTV purchased 12 years ago will have a component input, and will be able to receive an analog HD signal from a modern Bluray player.
The televisions gain market share because it's a feature put into just about every half-way decent television. It's hard to get a TV these days that isn't stereo. Now, how many people actually use that feature, and how many people reluctantly have it shoved down their throat?
Wut? Raw 1080p30 is ~1.87Gbps so 18.2Mbps MPEG2 is already over 100X compression.
Technically, it's only half that (plus your math is off somewhere). Nearly all video transmission techniques convert the color space from three color channels to an intensity and two color channels, and then quarter the resolution of those color channels. A 1920x1080 video frame will only store color information at 960x540. Even analog formats do that. With two of three channels down to a quarter the data, it averages to only 12 bits per pixel, rather than 24.
You have a point, but you lost credibility when you included OTA in that list. OTA is uncompressed 18.2mbit MPEG.
Did he now? I surely hope you're not employed by that IPTV/Satellite service in a technical fashion. Please tell me you're in sales or something...
Do the math. 1920 x 540 x 60 x 12 = 750Mbps. That's quite a bit higher than 18.2...
There is no point in compressing an OTA broadcast because the bandwidth is functionally unlimited
Or it's limited to around 18.2Mbps, as you just stated... It's actually typical to see the primary channel only running 12-16Mbps, with the excess used for one or more secondary channels.
When you see artifacts on an OTA broadcast it is most emphatically *not* from compression, it's usually from interference or a badly tuned/aligned antenna.
When you see large chunks of missing or corrupted video, THAT is from interference or an insufficient antenna. Compression effects are things like color banding, or easily discernible macro-block boundaries, and you absolutely do see those as your scene complexity or motion increases beyond the codec's ability to handle it.
That's just not true. You're taking one measurement of average human perception, and using it where it does not apply.
The standard "good enough" resolution people quote assume 20/20 vision, or roughly one arc minute of perception, when determining the width of a monochrome line with one eye. If we were viewing monochrome monitors, or ones that at least had their colors in the same physical location, that might make sense, but we don't. A good percentage of the population can see well below 20/20 vision even in this measurement, with the best somewhere around 20/10. That means if 2K is "good enough" for average vision, then 4K would be necessary for those with exceptional vision.
However, that's still wrong. That resolving ability of our eyes might be around one arc minute, but vernier acuity has been measured around eight arc seconds, and stereo acuity has been measured all the way down to two arc seconds. So, maybe once we get another three orders of magnitude pixels, we won't be able to improve it further.
For $189, you're going to get a shitty TN panel. If you actually like the nice image you get from a CRT, or like to view the screen from anywhere but straight on, you won't be happy with it.
If you look at the tvs out there many that are '4k' are actually 2160p. They have conveniently flipped it on end and call it 4k.
Huh? No one has flipped anything. That's just what 4K is. It's a cinema format describing a long axis of roughly 4K pixels. Your current 1080p television could be considered a 2K display.
Not television specifically, no, but we have built crude holographic displays. Now it's just a question of resolution and data rate. Those stored interference patterns are oppressively large.
Higher resolution beyond a certain point no longer becomes about displaying more data, but displaying it better. The font remains the same physical size, but more pixels are devoted to it, leading to much crisper, clearer text, without reverting to tricks like anti-aliased and sub-pixel rendered fonts.
Overlay, xv? that's a nice feature thanks. It used to use a fixed fonction scaler I think, at least in S3 Virge, ATI Rage Pro, and took YUV as input. It's what made our PCs smooth at full screen video till flash video tried to ruin it, requiring a 1GHz and faster CPU to play low quality vids. Did they remove the old scaler, while adding new fixed function stuff? (h264 etc.). That would feel stupid to me.
There's a bit of confusion over the meaning of background noise. In this example, it's not stray sound or RF, but reflections from things you don't care about. For dolphins, they're talking about air bubbles in the water. For this RADAR system, they're talking about brush and rubble. The idea of differential signalling does not apply here.
Basically, they're sending two pulses, shifted 180. They both bounce off the target, come back, and cancel each other out at the receiving antenna, yielding no response. It acts like a material discriminator, in that certain interesting materials, such as wires or micro-circuitry, invert only one of the reflections, so instead of cancelling each other out, they amplify.
Why this inversion of only one of the reflections happens, rather than both... I have no idea. I'm merely repeating the claims in article.
As you say, it does need time to mature, but the library of games is already there. This is the actual Unreal 3 engine, with limited modifications. It uses WebGL and asm.js. WebGL is a means of accessing graphics hardware through Javascript, and is based on OpenGL ES. asm.js is a subset of Javascript, limited to structures that are highly optimization, and generated by a custom backend to a C compiler.
Basically, with limited effort, you can port any C/C++/OpenGL game to the web browser.
Slashdot Mirror
Your body does not measure a lack of oxygen. It measures an abundance of carbon dioxide. If you hyperventilate, you can hold your breath considerably longer, not because you actually have any more oxygen in your system, but because you flush out any carbon dioxide in your blood stream, and it takes longer for your body to register that it needs to breathe again.
Willing? Sure... Capable? Probably not.
I think the only thing I would have trouble with would be lobster. They scream if you do it wrong.
The Society of Motion Picture and Television Engineers (SMPTE), Engineering Guideline 18-1994. That has since been retracted and replaced with 196M-2003, which now phrases it in terms of picture height, stating you should be no more than four heights back, or roughly seven feet.
They hold their value because people place move value on them than a simple utility. A PC is for utility. A Mac is a fashion item. The equivalent era Mac is no more capable than the equivalent era PC, considering they're made with the same exact parts.
Why 32bpp? Monitors and televisions (and our eyes) only have three color channels, so you have 24-bit, or 30-bit, or 36-bit, for 8, 10, or 12 bits per channel, respectively. When you're talking commercially distributed video, it's almost always YUV420 rather than RGB. You have your one intensity channel at full resolution, and two color channels running at quarter resolution, so a cluster of four pixels shares one color. 24-bit color becomes 12bpp, 30-bit becomes 15bpp, and 36-bit becomes 18bpp. It was originally designed to allow B&W and color television to coexist on the same transmission, but was found to be a good psychovisual compression mechanism. The only time you would use 16-bit or 32-bit color is inside your graphics pipeline prior to compositing, where the three-channel image is accompanied by a fourth transparency channel.
That might have been when the average TV was 20", and standard definition. The recommendation these days is for the horizontal viewing angle to be roughly 30, which would mean you should sit roughly 6.5' back from a 42" television.
That's a very bad idea. It's common for television sets to overscan and crop the video inputs. It's hard to find one that will actually do 1:1 display.
No, he's complaining that the HDTV he bought 12 years ago wasn't supported properly as much as 8-10 years ago.
Because the HD spec kept changing, the early adopters got screwed. Before HD was available to most people, the first two generations of display devices were already obviated. By the time you actually got any HD content the spec had said "oh, you aren't supported at full resolution or with this connector".
Now back to reality, the ATSC spec was published way way back in 1995, and was accepted and standardized by the FCC just a year later, long before even the "enhanced definition" sets hit the market. An HDTV purchased 12 years ago will have a component input, and will be able to receive an analog HD signal from a modern Bluray player.
The televisions gain market share because it's a feature put into just about every half-way decent television. It's hard to get a TV these days that isn't stereo. Now, how many people actually use that feature, and how many people reluctantly have it shoved down their throat?
Why 16bpp?
Wut? Raw 1080p30 is ~1.87Gbps so 18.2Mbps MPEG2 is already over 100X compression.
Technically, it's only half that (plus your math is off somewhere). Nearly all video transmission techniques convert the color space from three color channels to an intensity and two color channels, and then quarter the resolution of those color channels. A 1920x1080 video frame will only store color information at 960x540. Even analog formats do that. With two of three channels down to a quarter the data, it averages to only 12 bits per pixel, rather than 24.
That said, the OP is still a complete dunce.
Right. We're still a long way off before those tricks stop being useful.
You have a point, but you lost credibility when you included OTA in that list. OTA is uncompressed 18.2mbit MPEG.
Did he now? I surely hope you're not employed by that IPTV/Satellite service in a technical fashion. Please tell me you're in sales or something...
Do the math. 1920 x 540 x 60 x 12 = 750Mbps. That's quite a bit higher than 18.2...
There is no point in compressing an OTA broadcast because the bandwidth is functionally unlimited
Or it's limited to around 18.2Mbps, as you just stated... It's actually typical to see the primary channel only running 12-16Mbps, with the excess used for one or more secondary channels.
When you see artifacts on an OTA broadcast it is most emphatically *not* from compression, it's usually from interference or a badly tuned/aligned antenna.
When you see large chunks of missing or corrupted video, THAT is from interference or an insufficient antenna. Compression effects are things like color banding, or easily discernible macro-block boundaries, and you absolutely do see those as your scene complexity or motion increases beyond the codec's ability to handle it.
Most cable companies have long since dropped analog cable. Time Warner is the only large MSO still offering it.
That's just not true. You're taking one measurement of average human perception, and using it where it does not apply.
The standard "good enough" resolution people quote assume 20/20 vision, or roughly one arc minute of perception, when determining the width of a monochrome line with one eye. If we were viewing monochrome monitors, or ones that at least had their colors in the same physical location, that might make sense, but we don't. A good percentage of the population can see well below 20/20 vision even in this measurement, with the best somewhere around 20/10. That means if 2K is "good enough" for average vision, then 4K would be necessary for those with exceptional vision.
However, that's still wrong. That resolving ability of our eyes might be around one arc minute, but vernier acuity has been measured around eight arc seconds, and stereo acuity has been measured all the way down to two arc seconds. So, maybe once we get another three orders of magnitude pixels, we won't be able to improve it further.
For $189, you're going to get a shitty TN panel. If you actually like the nice image you get from a CRT, or like to view the screen from anywhere but straight on, you won't be happy with it.
If you look at the tvs out there many that are '4k' are actually 2160p. They have conveniently flipped it on end and call it 4k.
Huh? No one has flipped anything. That's just what 4K is. It's a cinema format describing a long axis of roughly 4K pixels. Your current 1080p television could be considered a 2K display.
Not television specifically, no, but we have built crude holographic displays. Now it's just a question of resolution and data rate. Those stored interference patterns are oppressively large.
Higher resolution beyond a certain point no longer becomes about displaying more data, but displaying it better. The font remains the same physical size, but more pixels are devoted to it, leading to much crisper, clearer text, without reverting to tricks like anti-aliased and sub-pixel rendered fonts.
This is a three year old article? This is a much worse than normal delay for slashdot....
Decades? Plural? Linux has barely even existed for plural decades.
Overlay, xv? that's a nice feature thanks. It used to use a fixed fonction scaler I think, at least in S3 Virge, ATI Rage Pro, and took YUV as input. It's what made our PCs smooth at full screen video till flash video tried to ruin it, requiring a 1GHz and faster CPU to play low quality vids. Did they remove the old scaler, while adding new fixed function stuff? (h264 etc.). That would feel stupid to me.
Xv is still around.
There's a bit of confusion over the meaning of background noise. In this example, it's not stray sound or RF, but reflections from things you don't care about. For dolphins, they're talking about air bubbles in the water. For this RADAR system, they're talking about brush and rubble. The idea of differential signalling does not apply here.
Basically, they're sending two pulses, shifted 180. They both bounce off the target, come back, and cancel each other out at the receiving antenna, yielding no response. It acts like a material discriminator, in that certain interesting materials, such as wires or micro-circuitry, invert only one of the reflections, so instead of cancelling each other out, they amplify.
Why this inversion of only one of the reflections happens, rather than both... I have no idea. I'm merely repeating the claims in article.
Make that "highly optimizeable"...
As you say, it does need time to mature, but the library of games is already there. This is the actual Unreal 3 engine, with limited modifications. It uses WebGL and asm.js. WebGL is a means of accessing graphics hardware through Javascript, and is based on OpenGL ES. asm.js is a subset of Javascript, limited to structures that are highly optimization, and generated by a custom backend to a C compiler.
Basically, with limited effort, you can port any C/C++/OpenGL game to the web browser.