4 ms·

To add to this, they can't even properly display screen saver photos on Chromecast from Google photos. My 4:3 photos get the top and bottom cut off instead of

by treis 8y ago

To add to this, they can't even properly display screen saver photos on Chromecast from Google photos. My 4:3 photos get the top and bottom cut off instead of being letterboxed.

Godel_unicode 8y ago
Who's to say that your idea is proper? Letterboxing causes burn-in on OLEDs, not exactly ideal for a screen saver.
- lstamour 8y ago
  (a) watching movies letterboxed has yet to cause burn in on my OLED and (b) you could make the backdrop a frosted glass version of the same photo... Not to say that every point is spot-on, but it’s true that Google in general makes their software and UIs complicated enough that outside of perhaps search or betas, they don’t update or change them all that frequently, maybe every two years at best. Apple or Microsoft could by now show them a thing or two on how to iterate user interfaces annually to evolve UI instead of making drastic changes folks might not like or sticking with the status quo forever with rollouts via obscure settings panels.
- treis 8y ago
  >Who's to say that your idea is proper I will fight to death anyone who says different. >Letterboxing causes burn-in on OLEDs, not exactly ideal for a screen saver. They letterbox the portrait photos correctly. Well, sort of. They have a small gap between the top/bottom of the TV and the top/bottom of the photo. The letterbox area uses part of the photo so there's no additional risk of burn in. Even if they did just use black, I don't think black can be burned in.
therealx 8y ago
You act like anyone at Google has any 4:3 photos.
auiya 8y ago
Properly displaying screen saver photos is the absolute least of the bugs affecting Chromecast. Ever try casting a 'watch later' queue of long-form YouTube videos from an iPhone? It loses audio sync constantly, drops frames excessively, loses connection to the chromecast device periodically, plays videos out of order; it's a complete disaster. I don't see how it ever left QA and went to market tbh. Google support exhausted all possibilities with me and left me with a "Sorry, nothing else we can do. #YOLO". They know it's busted, they don't care.

by treis 8y ago

To add to this, they can't even properly display screen saver photos on Chromecast from Google photos. My 4:3 photos get the top and bottom cut off instead of being letterboxed.

Godel_unicode 8y ago

Who's to say that your idea is proper? Letterboxing causes burn-in on OLEDs, not exactly ideal for a screen saver.

lstamour 8y ago
(a) watching movies letterboxed has yet to cause burn in on my OLED and (b) you could make the backdrop a frosted glass version of the same photo... Not to say that every point is spot-on, but it’s true that Google in general makes their software and UIs complicated enough that outside of perhaps search or betas, they don’t update or change them all that frequently, maybe every two years at best. Apple or Microsoft could by now show them a thing or two on how to iterate user interfaces annually to evolve UI instead of making drastic changes folks might not like or sticking with the status quo forever with rollouts via obscure settings panels.
treis 8y ago
>Who's to say that your idea is proper I will fight to death anyone who says different. >Letterboxing causes burn-in on OLEDs, not exactly ideal for a screen saver. They letterbox the portrait photos correctly. Well, sort of. They have a small gap between the top/bottom of the TV and the top/bottom of the photo. The letterbox area uses part of the photo so there's no additional risk of burn in. Even if they did just use black, I don't think black can be burned in.

therealx 8y ago

You act like anyone at Google has any 4:3 photos.

auiya 8y ago

Properly displaying screen saver photos is the absolute least of the bugs affecting Chromecast. Ever try casting a 'watch later' queue of long-form YouTube videos from an iPhone? It loses audio sync constantly, drops frames excessively, loses connection to the chromecast device periodically, plays videos out of order; it's a complete disaster. I don't see how it ever left QA and went to market tbh. Google support exhausted all possibilities with me and left me with a "Sorry, nothing else we can do. #YOLO". They know it's busted, they don't care.