Admin of lemmy.blahaj.zone

I can also be found on the microblog fediverse at @ada@blahaj.zone or on matrix at @ada:chat.blahaj.zone

  • 26 Posts
  • 211 Comments
Joined 2 years ago
cake
Cake day: January 2nd, 2023

help-circle



  • So, in its current form, lemmy sends federation packets in serial form. It can send them to multiple instances in parallel, but the feed between any two given instances is serial.

    And serial means that the second packet doesn’t get sent until the first packet has been processed. Add in geographic latency, which is relevant at multiple steps of resolving any given AP packet, which adds to the per packet processing time, and now, lemmy.world is producing packets faster than it’s possible for a geographically remote instance to process them, no matter what hardware they’re running on.

    The problem would be resolved with parallel sending, but that’s not currently a thing that lemmy allows for, and apparently, is not trivial to implement either.







  • It’s a computational mode in the camera. It takes an initial photo, and then a series of photos of equal length, and composites any new light on the subsequent photos on the first. In this case, from memory, it’s 5 photos at one second exposure each.

    Basically, it lets you do a long exposure, without blowing out static light sources.

    There’s a slight post processing change to the colour, to bring out the orange/teal effect, but it’s pretty subtle

    Edit - FYI, your reply was tagged as German, which means that non german speakering lemmy users probably won’t see it, because most instances hide replies of languages the user doesn’t speak









  • I use digikam with sidecar files on my main photo editing PC.

    We sync this directory with a media server on the local network that enables all of the local devices to access the photos and tags. In theory, it means we could run digikam on another device as well, and sync data between them via updates to the sidecar files, but in practice, we don’t do this and the media server is effectively read only.

    Then, we sync the media server images with a photoprism instance that we have running on external hosting. Photoprism recognises the keywords and sidecar data from digikam, which lets me search and access the images from anywhere.









  • The r50 can do electronic shutter or second curtain shutter, but it doesn’t have a global shutter or full mechanical shutter.

    So, some ELI5 background on camera sensors. Most sensors read the data from the sensor pixel by pixel, line by line. So what that means is that a small amount of time passes between reading the top lines of the sensor and the bottom lines of the sensor. Most of the time, this doesn’t make much difference. But for fast moving objects (or if you’re panning the camera really fast) it means that the scene can change during that passage of time, which is what gives you trains that lean to one side and propellers that look like they’re made of rubber.

    To get around that, you can use a physical shutter. Cameras with “second curtain” shutters physically close off the light to the sensor before they start reading data from the sensor. This means that even though time passes between reading the top and the bottom of the line, the light captured by the sensor does not change during that time, and so the wobbly subjects don’t happen.

    A camera with a full mechanical shutter puts a physical shutter at the beginning of the process and the end, but the gains over second curtain only are negligible.

    In theory, there is also “global shutter” which is a camera that reads the entire sensor at once, but in practice, this technology doesn’t exist at the consumer mirrorless camera level.

    Electronic shutters aren’t all bad though, because they let you do faster shutter speeds than are possible with physical elements, and they let you do higher fps when shooting in burst mode. And electronic shutters are also silent