On 31 January 2012 10:31, Casper Bang <[email protected]> wrote: > > >> Now I don't care for YouTube (which I don't use anyway), but if >> you are looking at a movie or a picture exhibit this makes a big >> difference. >> > Sure, some of us who care about image quality may buy good panels (i.e. I > care greatly about black-levels so I still watch movies on Plasma) and take > the time to calibrate. Your average Joe however, will just leave the > over-saturated color and contrast which the manufacturers and stores use, > in order to draw attention. So you can argue that users should be able to > calibrate their smartphone/tablet screens as they see fit, but I still > maintain that the majority of users have no clue about this. The same goes > for sound btw. where enthusiasts like George Lucas came up with the THX > certification, yet most people are contend with their crappy Sony system > made from cheap IC's and resistors. > >
Too true, just take support for lossless codecs as an example. Prior to V3.1, you had to root your mobile and install cyanogenMod to get built-in FLAC support (although PowerAmp was a handy workaround). Even then, you won't find a bluetooth solution that supports lossless audio, especially damning when you consider that bluetooth is the only route for digital audio output on the vast majority of devices, and the line out/headphone out are most definitely not going to be using the best DACS and amplifiers known to mankind. So long as we're talking phones and not tablets, can we please get the sound right first, because listening to music is a very common use-case. Being able to enjoy a bit of high-fidelity jazz while commuting is much more important than the exact shades of red, blue and white I see when playing angry birds. On those occasions where I am concerned about image quality, then I'll attend to the screen size and resolution before colour balance. So fix the audio first, then give me 2048x1536, and *then* we can sit down and discuss white balance. It's also happening with monitors and TV equipments, of >> course, since color management is not a common practice, but with >> Google's >> lack of care in this area things will go worse. It's the typical case in >> which technology for the masses damages culture and frankly it's quite >> delusional that Google doesn't care. >> > I think "damages culture" is put a little extreme, for a number of > reasons. First of all, colors are not perceived equally by everyone so that > makes it rather hard to say "this is right". Secondly, nothing stops you > from pursuing high fidelity products yourself, as is the case with so many > other things i.e. sound. Third, new technologies (OLED) are subject to > tremendous pressure to deliver and evolve. For the record, the brand new > Nokia Lumia 800 running Windows Mobile 7.5, exhibits the same odd color > temperature issue which the user is not able to calibrate. There can be > little doubt, that as technologies get better and better, so will the mass > marked products using these. > > You could always open a bug with AOSP and request a calibration API be > made available, but I am not convinced this can be solved with software > given the plethora of technologies and drivers in use today. > >> -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
