falkerie71

I'm frustrated about color consistency between programs and devices, making color management so hard to do across platforms. My camera shows a different color to my phone, which shows a different color to my PC. Even on PC alone, the color in the editing program is different to the photo preview software and browser. How do you guys manage this? I'm aware that the Apple ecosystem does a better job at color consistency across devices, and I'm very jealous of that.

My devices include a Fujifilm camera, Google Pixel, Windows PC with non-calibrated LCD monitor, and a Windows laptop with OLED monitor (was factory calibrated, but I lost the file after a system wipe, so not sure anymore). Softwares on PC include Fujifilm X RAW studio, Affinity Photo 2, Photoshop, FastStone viewer, and Firefox (primary browser). Should I stick to the OLED laptop for editing instead?

Focal length range, Optical quality, Size & weight. Pick two.

I've been holding on to this thought for quite some time and don't know where to share this. Too long and not random enough for a shower thought, so here it is I guess.

Car manufacturers really like their LEDs to be as fancy as possible lately, and more and more turn signals on cars have this "sequential lighting" show they do. Basically, the type of turn signal I have a problem with is the one that gradually fills up the turn signal light bar, then turns off everything when the bar is full, i.e. Audi cars in this video

IMO, not only does the animation feel clunky, I also think its a safety issue, albeit a relatively minor one. The point of indicator lights is to tell other drivers your intentions. They should be fully noticeable the moment you turn on your turn signals, and should not be halfway lit first. It probably would also introduce a delay in driver response, but I have no scientific evidence to back this claim up, so take this as just my opinion.

Instead, they should do it the opposite way where the light bar fully lights up first, then gradually shrinks. Or the Mazda way of turning on quickly then dimming down slowly like in this video. Or the combination of these two, where the light bar has a gradient end that tapers away when shrinking. (Seriously, having a gradient or a gradual dim is so much more elegant. Why don't more cars do this?)

Okay rant over. Thanks for coming to my ted talk.

Asphalt used on road surfaces are byproducts from fossil fuel. With the ultimate goal of eliminating the use of fossil fuel to combat climate change, are there any good alternatives for road surfaces? I don't think I've ever heard of a viable replacement of asphalt in the works, or even a plan to replace it in any environmental discussions before. At least, not enough for me to notice.

Extented question would be: what are some products derived from fossil fuel that are used in everyday life, but still lack viable alternatives you don't see enough discussions about?

I've been using the 6a since the start of this year, and alongside it Accubattery to remind me to unplug my phone whenever it reaches 85% charge.

I know Accubattery stats are just an approximation, and I've only been using this phone for half a year, but still quite amusing to see the battery health go up instead of dropping.

I'm on firmware 2.13.18, using a Pixel 6a.

After updating to the latest firmware a few weeks ago, I've been experiencing audio glitches quite often compared to when I got them new, which had no glitches whatsoever. One of the update was adding support for 24bit/96kHz aptX Adaptive, which in hindsight is probably the most obvious thing I should've tried investigating.

There is a toggle in the Sennheiser app that toggles High resolution audio mode. Turning that off does not fix the problem! Looking in the developer options, it's still using 24bit/48kHz aptxHD, and the glitches still happen. Turning off aptxHD in the Bluetooth options fixes the problem, but it will revert back to SBC and not stay at aptX, so it won't do either.

What you should do is go to Developer options in Settings, scroll down to Bluetooth Audio Codec and switch to aptX. It will now switch to 16bit/48kHz and the audio glitch should be resolved. Downside is that it seems you would have to go there and switch to aptX everytime you reconnect to your headphones.

My phone has no problem playing 24bit aptXHD audio using the BTR5, so the issue is most likely with the headphones itself.

TL;DR: I suspect the Momentum 4 couldn't handle 24bit audio, so switch to 16bit to avoid audio glitching.

I was so confused when I was seeing posts 4 years old. "Old" isn't even supposed to be an option lol.

Tested with other options, seems like TopWeek becomes TopDay, TopMonth becomes TopWeek, TopYear becomes TopMonth, TopAllTime becomes TopYear, and Most comments become TopAllYear. Active, Hot, and New are unaffected.

So for now, you can enjoy seeing the creation of the Fediverse and read posts in reverse with this hidden option.

I'm considering setting up a NAS to backup my stuff and replace Google Photos. Currently I'm looking at Asustor AS6704T and Synology DS923+, with the former having more powerful hardware and hardware encoding, and the latter having a better first party software experience.

Some quick comparisons show me that Synology Photos is infinitely better than Asustor Photo Gallery. AI face recognition, content tagging, and reverse Geocoding are features I've gotten used to in Google photos, which Synology has and Asustor doesn't.
I'm also aware of but not really familiar with other photo backup/management solutions, namely Immich, Photoprism, Piwigo, and Lychee. Immich would probably fit me the best, but Piwigo with plugins would support Photosphere photos that I occasionally take with my Pixel.

So I guess I'm asking you guys what your preferred photo backup solution is? I probably should mention that I personally take photos with a Pixel (jpg and MP4 files), but my family uses iPhones (heic and mov files). No RAW photos for now, but for those who do and would edit photos, how would you manage them?