Exactly - if content providers aren't even willing to send enough bitrate through the pipe to deliver a satisfactory experience by today's HD standards, who on Earth would imagine they'd do justice to 16x the bandwidth requirement just a few years from now? Some broadcasts are still MPEG-2; some others are MPEG-2 but get passed through a last-leg AVC transcoder to save bandwidth; and while AVC's enjoying healthy adoption, there's no way to expect most companies will pay the hefty fees to adopt HEVC equipment in time for this Great Leap Forward. 4K's swell for going to a theater or a similarly large exhibition area, but for most consumers the upgrade will be pretty trivial.
Late in getting back to this, but yes: the HD 5000's definitely hobbled a bit by the 15W TDP restriction of the i5-4250U. Amnesia: A Machine for Pigs probably wouldn't be sexy on the HD 3000, but should be manageable at low to medium quality settings and conservative resolutions.
OpenGL 4.1 already has full API compatibility with OpenGL ES 2.0. Let's not go throwing out decades of hard work for a little bit of convenience with regard to video games, especially when hardware going forward will all be capable of transparently handling the API you wanna switch to. As for throwing out X11 and tossing in the Android graphics stack for everybody, that's madness for a thousand reasons.
It probably won't hurt across-the-board performance, so even titles you've played 'til now may benefit. Give the new Amnesia a try - if my Macbook Air's Intel HD 5000 can push it along at 1440x900, you may have luck at 720p on the HD 3000.
By that metric AMD doesn't "make" its chips either. Nor do many companies, even if the IP is firmly theirs and the designs were entirely in-house. That's a strange, argumentative kind of quibbling.
Ergh. Looks like Intel's managed to close the gap with Bulldozer in that stronghold through sheer clock ramping. You got me - I hadn't looked at Haswell benchmarks much.
Technology and economies of scale have come a very, very long way from the 3DO. From what I've seen and heard I wouldn't bet against it, and I'd certainly place better odds on it than the 3DO.
First: yes, it's clearly a joke. How can you copy something done ten years earlier?:P
Second, Apple does make their own ARM CPUs these days. They build and design licensed ARM CPUs for their iOS devices these days, which includes AppleTV, iPhones, iPads, and iPods, but for their Mac / OS X business they are still 100% Intel. Their latest design is starting to turn some heads.
The misleading thing about benchmarks is that they're generally prebaked - there's no chance for "surprise" physics interactions or various pipeline-stalling things that tended to trip up the Pentium 4. From personal experience I'll tell you that my old 2.8 GHz Pentium 4 generally didn't do as well as my Athlon XP 2400+ in Doom 3, Bioshock, or Unreal Tournament 3. The latter two should have been poster children for the Netburst chip by comparison. Also, the Pentium D 820 was a 2.8 GHz chip: it was the miserably hot 130W TDP 840 that ran at 3.2 GHz. But you're correct on the other counts - the higher IPC and integrated memory controller were both HUGE advantages over a latency-crippled, deeply pipelined architecture. The Pentium D was itself a flailing, mostly failed response to the surge in mindshare the Athlon 64 X2 created until the Core architecture could be prepared.
It depends an awful lot on the workload, though. For gaming it's one-sided in Intel's favor to the tune of around 2/3 more work done per clock on average (sometimes more), but for video encoding with x264 the sheer core count makes it better than competitive with Intel unless you're willing to pay noticeably more. It's a behemoth for virtual machines, it plays video games well enough, and for scientific computation I really haven't found myself wanting. Granted, I'm an edge case...
Before, as best I recall. It went something like Geocities -> LiveJournal -> Friendster -> MySpace -> Facebook, not counting the various Diarylands, Xangas, and other strains of internet funk that bloomed and withered on the sides like little fungus gardens.
The answer's simple: Facebook wants their interface to be gobbledygook because that means you're spending more time on the site, and having to mentally filter relevant content from the ads they want you to see. By the logic of someone creating an attractive nuisance, interfering with this kind of product makes a perverse sense because it's making the product better for users but worse for Facebook's actual customers - advertisers and marketers.
In BeOS R5 you could drag 'n' drop audio tracks from a CD (and with a decent drive you could do it quite quickly), but I don't remember CDDB integration. Still pretty handy for huge batch LAME encoding jobs, though.
Blu-ray's variable, but video bitrate alone will sometimes jump over 36 Mbit/sec. Audio's also variable - Blu-ray supports everything from 0.1 Mbit Dolby Mono all the way up to 7+ Mbit lossless 24-bit PCM. Worst-case scenario you could expect something pushing 50 Mbit/second, which is definitely not within range of the typical American's broadband connection. 4K will be impressive, but assuming a linear doubling (as HEVC will be twice as efficient, but have to deal with four times the video data)... yep, your math checks out. There's also the problem of product segmentation between different streaming video providers and studio bickering, lapsing of rights, seasonal variability, &c. Until and unless that gets sorted out, I'm buying physical copies of my favorite movies.
The problem isn't just surfacing for DTS Master HD films - my Blu-ray player connected via HDMI to the same TV grunts through everything fine, and the audio problems have happened with AAC and Dolby Digital from Netflix streaming as well. We'll see what happens after I rebuild the system.
Yeah, I've been wondering about that. The configuration's pretty vanilla: the Radeon uses an HDMI cable to connect to a late 2011-era Philips HDTV that hasn't given a pinch of trouble otherwise, and there aren't amps or optical audio to complicate the pipeline any at this point. While the glitch appears during video playback, it's surfaced in both Netflix (where I'd expect Silverlight to be a possible culprit of a DRM snafu) and VLC (where I definitely wouldn't). Fingers crossed hoping the issue disappears going into a clean install, and fingers crossed extra-hard that AMD finally releases the first official, non-beta driver in months soon...
Short of using it for OpenCL at lower rates than FirePro cards or gaming across multiple high-res monitors or a numbingly high-res projector, I've got to agree. But if its generous margins help subsidize ongoing research into cards mortal humans can use and appreciate, I can't complain either.
The only issue I've run into with the Radeon 7750 I snagged last year for my home theater PC has nothing to do with 3D rendering. For some reason, there is a very occasional glitch with the card's HDMI audio during video playback that causes a weird, harsh, and intermittent kind of sound artifacting, and after a couple of seconds the audio rolls off into silence... and then goes back to normal. If the problem persists after a fresh install onto mostly new hardware (goodbye Athlon X2 5050e, hello Ivy Bridge Celeron), I'm just giving up on the HDMI audio altogether and going back to a mini-stereo cable. Overall I'm pretty happy, but that's an irritating unpolished edge on what's otherwise been a terrific bargain and a reliable performer. It sure as hell didn't make me eager to grab a Radeon for my Linux workstation...
Sure, and heaven forbid any of those "users buying commodity computers with 64-bit CPUs and OSes" could ever use their hardware to begin tinkering with high-resolution video editing, or programming, or playing with the full capabilities of the hardware with which Moore's Law has blessed them. The fact that I do real work that can use more than 4 GB RAM doesn't mean the average user of whom you clearly think very little is incapable of doing so.
Look, I like bashing straw man lazy programmers as much as anybody. But in scientific computing in the year 2013 - say, where you need to store 50 cubic miles of subsurface 4-dimensional seismic reflector data for 3D visualization and modeling density change over time - you run into the limits of 4 gigabytes very quickly. Never mind large-scale simulations run in TOUGH2-MP... Don't paint with such a large brush. People may piss memory on stuff that ran in less RAM back in 1996, but we're not there any more, and adventurous, relevant, and efficient uses of RAM really do exist.
Nah - your primitives are doubled in size, which realistically represents something closer to a 25-33% size increase on average. But between the abilities to manipulate MUCH larger quantities of data at once and addressing >3.5 GB RAM, it's an easy choice unless you absolutely need 16-bit support.
Slashdot Mirror
Timer coalescing's been a feature in x86/x86_64 versions of Windows since Windows 7, and was added to Linux a bit before that.
Exactly - if content providers aren't even willing to send enough bitrate through the pipe to deliver a satisfactory experience by today's HD standards, who on Earth would imagine they'd do justice to 16x the bandwidth requirement just a few years from now? Some broadcasts are still MPEG-2; some others are MPEG-2 but get passed through a last-leg AVC transcoder to save bandwidth; and while AVC's enjoying healthy adoption, there's no way to expect most companies will pay the hefty fees to adopt HEVC equipment in time for this Great Leap Forward. 4K's swell for going to a theater or a similarly large exhibition area, but for most consumers the upgrade will be pretty trivial.
Late in getting back to this, but yes: the HD 5000's definitely hobbled a bit by the 15W TDP restriction of the i5-4250U. Amnesia: A Machine for Pigs probably wouldn't be sexy on the HD 3000, but should be manageable at low to medium quality settings and conservative resolutions.
OpenGL 4.1 already has full API compatibility with OpenGL ES 2.0. Let's not go throwing out decades of hard work for a little bit of convenience with regard to video games, especially when hardware going forward will all be capable of transparently handling the API you wanna switch to. As for throwing out X11 and tossing in the Android graphics stack for everybody, that's madness for a thousand reasons.
It probably won't hurt across-the-board performance, so even titles you've played 'til now may benefit. Give the new Amnesia a try - if my Macbook Air's Intel HD 5000 can push it along at 1440x900, you may have luck at 720p on the HD 3000.
By that metric AMD doesn't "make" its chips either. Nor do many companies, even if the IP is firmly theirs and the designs were entirely in-house. That's a strange, argumentative kind of quibbling.
Ergh. Looks like Intel's managed to close the gap with Bulldozer in that stronghold through sheer clock ramping. You got me - I hadn't looked at Haswell benchmarks much.
Technology and economies of scale have come a very, very long way from the 3DO. From what I've seen and heard I wouldn't bet against it, and I'd certainly place better odds on it than the 3DO.
Man, that Doom port sucked.
First: yes, it's clearly a joke. How can you copy something done ten years earlier? :P
Second, Apple does make their own ARM CPUs these days. They build and design licensed ARM CPUs for their iOS devices these days, which includes AppleTV, iPhones, iPads, and iPods, but for their Mac / OS X business they are still 100% Intel. Their latest design is starting to turn some heads.
The misleading thing about benchmarks is that they're generally prebaked - there's no chance for "surprise" physics interactions or various pipeline-stalling things that tended to trip up the Pentium 4. From personal experience I'll tell you that my old 2.8 GHz Pentium 4 generally didn't do as well as my Athlon XP 2400+ in Doom 3, Bioshock, or Unreal Tournament 3. The latter two should have been poster children for the Netburst chip by comparison. Also, the Pentium D 820 was a 2.8 GHz chip: it was the miserably hot 130W TDP 840 that ran at 3.2 GHz. But you're correct on the other counts - the higher IPC and integrated memory controller were both HUGE advantages over a latency-crippled, deeply pipelined architecture. The Pentium D was itself a flailing, mostly failed response to the surge in mindshare the Athlon 64 X2 created until the Core architecture could be prepared.
And in AMD64 MMX (along with 3DNow!) is officially deprecated in favor of the SSE instructions. Like a twisting of the knife.
It depends an awful lot on the workload, though. For gaming it's one-sided in Intel's favor to the tune of around 2/3 more work done per clock on average (sometimes more), but for video encoding with x264 the sheer core count makes it better than competitive with Intel unless you're willing to pay noticeably more. It's a behemoth for virtual machines, it plays video games well enough, and for scientific computation I really haven't found myself wanting. Granted, I'm an edge case...
Before, as best I recall. It went something like Geocities -> LiveJournal -> Friendster -> MySpace -> Facebook, not counting the various Diarylands, Xangas, and other strains of internet funk that bloomed and withered on the sides like little fungus gardens.
The answer's simple: Facebook wants their interface to be gobbledygook because that means you're spending more time on the site, and having to mentally filter relevant content from the ads they want you to see. By the logic of someone creating an attractive nuisance, interfering with this kind of product makes a perverse sense because it's making the product better for users but worse for Facebook's actual customers - advertisers and marketers.
In BeOS R5 you could drag 'n' drop audio tracks from a CD (and with a decent drive you could do it quite quickly), but I don't remember CDDB integration. Still pretty handy for huge batch LAME encoding jobs, though.
What would YOU say if you'd been through what he has? Who can say if he's sincere? This is just another part of the dog and pony show. Keep fighting.
Blu-ray's variable, but video bitrate alone will sometimes jump over 36 Mbit/sec. Audio's also variable - Blu-ray supports everything from 0.1 Mbit Dolby Mono all the way up to 7+ Mbit lossless 24-bit PCM. Worst-case scenario you could expect something pushing 50 Mbit/second, which is definitely not within range of the typical American's broadband connection. 4K will be impressive, but assuming a linear doubling (as HEVC will be twice as efficient, but have to deal with four times the video data)... yep, your math checks out. There's also the problem of product segmentation between different streaming video providers and studio bickering, lapsing of rights, seasonal variability, &c. Until and unless that gets sorted out, I'm buying physical copies of my favorite movies.
The problem isn't just surfacing for DTS Master HD films - my Blu-ray player connected via HDMI to the same TV grunts through everything fine, and the audio problems have happened with AAC and Dolby Digital from Netflix streaming as well. We'll see what happens after I rebuild the system.
Yeah, I've been wondering about that. The configuration's pretty vanilla: the Radeon uses an HDMI cable to connect to a late 2011-era Philips HDTV that hasn't given a pinch of trouble otherwise, and there aren't amps or optical audio to complicate the pipeline any at this point. While the glitch appears during video playback, it's surfaced in both Netflix (where I'd expect Silverlight to be a possible culprit of a DRM snafu) and VLC (where I definitely wouldn't). Fingers crossed hoping the issue disappears going into a clean install, and fingers crossed extra-hard that AMD finally releases the first official, non-beta driver in months soon...
Short of using it for OpenCL at lower rates than FirePro cards or gaming across multiple high-res monitors or a numbingly high-res projector, I've got to agree. But if its generous margins help subsidize ongoing research into cards mortal humans can use and appreciate, I can't complain either.
The only issue I've run into with the Radeon 7750 I snagged last year for my home theater PC has nothing to do with 3D rendering. For some reason, there is a very occasional glitch with the card's HDMI audio during video playback that causes a weird, harsh, and intermittent kind of sound artifacting, and after a couple of seconds the audio rolls off into silence... and then goes back to normal. If the problem persists after a fresh install onto mostly new hardware (goodbye Athlon X2 5050e, hello Ivy Bridge Celeron), I'm just giving up on the HDMI audio altogether and going back to a mini-stereo cable. Overall I'm pretty happy, but that's an irritating unpolished edge on what's otherwise been a terrific bargain and a reliable performer. It sure as hell didn't make me eager to grab a Radeon for my Linux workstation...
I didn't know that! Some time soon I'm gonna have to get some very old games up and running in Linux soon... Thank you!
Sure, and heaven forbid any of those "users buying commodity computers with 64-bit CPUs and OSes" could ever use their hardware to begin tinkering with high-resolution video editing, or programming, or playing with the full capabilities of the hardware with which Moore's Law has blessed them. The fact that I do real work that can use more than 4 GB RAM doesn't mean the average user of whom you clearly think very little is incapable of doing so.
Look, I like bashing straw man lazy programmers as much as anybody. But in scientific computing in the year 2013 - say, where you need to store 50 cubic miles of subsurface 4-dimensional seismic reflector data for 3D visualization and modeling density change over time - you run into the limits of 4 gigabytes very quickly. Never mind large-scale simulations run in TOUGH2-MP... Don't paint with such a large brush. People may piss memory on stuff that ran in less RAM back in 1996, but we're not there any more, and adventurous, relevant, and efficient uses of RAM really do exist.
Nah - your primitives are doubled in size, which realistically represents something closer to a 25-33% size increase on average. But between the abilities to manipulate MUCH larger quantities of data at once and addressing >3.5 GB RAM, it's an easy choice unless you absolutely need 16-bit support.