|
lonjil
|
2024-10-19 05:59:17
|
"yeah I need to take these with me to test taking shots of the aurora on the other side of the country be back in a week or two"
|
|
|
RaveSteel
|
2024-10-19 05:59:44
|
Maybe if you give them your firstborn as a guarantuee that you'll come back lmao
|
|
|
|
veluca
|
2024-10-19 06:00:42
|
I'd assume in Switzerland they would be quite willing, mostly because if you never give it back then you have a big problem xD
|
|
|
spider-mario
|
2024-10-19 06:08:05
|
incidentally, I think you’ll have no trouble recognising where the test shots from that day were taken
|
|
|
lonjil
|
|
spider-mario
probably something like that
|
|
2024-10-19 06:25:30
|
but the signal to noise ratio should get better when downsampling, right?
|
|
|
jonnyawsom3
|
2024-10-19 06:39:55
|
Speaking of noise, it was just now I realised that JXL ISO noise influences the encoding choices and changes filesize. I always thought it was just an overlay
|
|
|
lonjil
|
|
lonjil
but the signal to noise ratio should get better when downsampling, right?
|
|
2024-10-19 07:09:32
|
just asking since, if higher resolution sensors aren't (much) noisier than lower resolution sensors on a per area basis, then I would expect downsampling to make the image less noisy.
|
|
|
_wb_
|
2024-10-19 07:15:36
|
There are many ways to do downsampling. Some are smoother, some are sharper, most reduce noise but there are some that attempt to preserve detail including noise.
|
|
2024-10-19 07:16:42
|
Just doing averaging reduces noise but it's also too smoothing to my taste.
|
|
|
AccessViolation_
|
2024-10-19 07:17:53
|
averaging would be like if you had a different sensor of the same size with half the vertical and horizontal resolution, right?
|
|
2024-10-19 07:23:26
|
I've thought about reducing 24 mp shots to 6 MP shots that way if they're not going to be displayed at 100% scale anyway, but image viewers might do downsampling like that themselves so I'm not sure if that'd be worth it. It seems better to take a burst of shots and combine them to reduce noise, for still subjects at least
|
|
|
spider-mario
|
|
lonjil
but the signal to noise ratio should get better when downsampling, right?
|
|
2024-10-19 07:28:21
|
basically, the signal adds up linearly but the noise adds in quadrature (sqrt(a² + b²)) so only grows with the square root of the number of pixels, and therefore the SNR grows with the square root of the downsampling factor
|
|
2024-10-19 07:29:20
|
so if you downsample from 60MP to 15MP, the “new big pixels” have roughly twice the SNR of the “old small ones” (4 times the signal and twice the noise)
|
|
|
lonjil
just asking since, if higher resolution sensors aren't (much) noisier than lower resolution sensors on a per area basis, then I would expect downsampling to make the image less noisy.
|
|
2024-10-19 07:30:46
|
I have the impression that you might be counting the downsampling twice, though
|
|
2024-10-19 07:31:28
|
this effect of downsampling is more or less why we can say that they aren’t much noisier
|
|
2024-10-19 07:31:39
|
(or at least correlates with it in some sense)
|
|
2024-10-19 07:32:12
|
there is the effect of denoising, though
|
|
|
Speaking of noise, it was just now I realised that JXL ISO noise influences the encoding choices and changes filesize. I always thought it was just an overlay
|
|
2024-10-19 07:33:07
|
at efforts ≤7, it should be, but I wouldn’t be surprised if it interfered with the butteraugli loop of efforts 8+
|
|
|
lonjil
|
|
spider-mario
basically, the signal adds up linearly but the noise adds in quadrature (sqrt(a² + b²)) so only grows with the square root of the number of pixels, and therefore the SNR grows with the square root of the downsampling factor
|
|
2024-10-19 07:33:22
|
Oh yeah, of course. Thanks :)
|
|
|
jonnyawsom3
|
|
spider-mario
at efforts ≤7, it should be, but I wouldn’t be surprised if it interfered with the butteraugli loop of efforts 8+
|
|
2024-10-19 07:33:36
|
This was effort 4 and 7
|
|
|
spider-mario
|
2024-10-19 07:33:42
|
oh, surprising then
|
|
2024-10-19 07:34:26
|
I would have expected the ~10 bytes of noise LUT to be the only difference
|
|
|
jonnyawsom3
|
2024-10-19 07:34:28
|
Higher ISO lower filesize, so it seemed to be discarding the pixels somehow
|
|
|
lonjil
|
|
spider-mario
I have the impression that you might be counting the downsampling twice, though
|
|
2024-10-19 07:37:16
|
I don't *think* I am? Just did a double take when you said that the noise increases. Then I realized, oh yeah, but the signal presumably goes up faster. Just needed confirmation cause I'm still rather unsure about this topic.
|
|
|
AccessViolation_
|
|
Higher ISO lower filesize, so it seemed to be discarding the pixels somehow
|
|
2024-10-19 07:38:34
|
Ooo, is this denoising the image to attempt to "replace" the noise with synthesized noise, or is that not implemented yet
|
|
|
spider-mario
|
|
lonjil
I don't *think* I am? Just did a double take when you said that the noise increases. Then I realized, oh yeah, but the signal presumably goes up faster. Just needed confirmation cause I'm still rather unsure about this topic.
|
|
2024-10-19 07:38:48
|
ah, right, I misinterpreted what you meant
|
|
2024-10-19 07:39:01
|
you meant that as “that must logically mean that downsampling reduces noise”
|
|
2024-10-19 07:39:34
|
I thought you might have meant “that would mean that with downsampling, they would be less noisy”
|
|
|
lonjil
|
2024-10-19 07:39:59
|
Yeah, former.
|
|
2024-10-19 07:41:43
|
I wonder if some of the a7S III's performance is simply due to superior electronics compared to the other cameras, rather than the differences in resolution.
|
|
|
spider-mario
|
2024-10-19 07:46:53
|
I’m not fully convinced that the performance of the S series is all it’s cracked up to be in the first place
|
|
2024-10-19 07:47:18
|
also, for what it’s worth, in the α7S III, it’s apparently a quad bayer 48MP sensor
|
|
2024-10-19 07:47:31
|
https://www.sonyalpharumors.com/surprise-the-sony-a7siii-actually-has-a-48-megapixel-quad-bayer-sensor/
|
|
|
lonjil
|
|
AccessViolation_
|
2024-10-19 08:21:08
|
I'm reading up on dual pixel AF and [this article from Canon](<https://www.usa.canon.com/learning/training-articles/training-articles-list/intro-to-dual-pixel-autofocus-dpaf>) says that the two diodes that make up one photocell also have their signals combined during capturing. I wonder if that gives you some free higher SNR as well, at least for area of the sensor that has DPAF pixels
|
|
2024-10-19 08:25:05
|
I'm now *also* wondering if DPAF means you get a free depth map which would be nice for future cameras that natively shoot JPEG XL, but I'm not really sure how signals from these pixels are processed
|
|
2024-10-19 08:25:37
|
Actually, I think the Google Pixel did something like this? I remember seeing a blog about building depth maps from dual pixel autofocus
|
|
|
spider-mario
|
|
AccessViolation_
I'm now *also* wondering if DPAF means you get a free depth map which would be nice for future cameras that natively shoot JPEG XL, but I'm not really sure how signals from these pixels are processed
|
|
2024-10-19 08:35:18
|
[yes, it does](https://www.canon-europe.com/cameras/eos-r5/dual-pixel-raw-mode/#:~:text=By%20comparing%20the%20very%20slightly%20different%20views%20seen%20in%20each%20of%20these%20images%2C%20a%20depth%20map%20can%20be%20embedded%20in%20the%20RAW%20file%2C%20meaning%20subtle%20adjustments%20can%20be%20made%20to%20the%20end%20result%20based%20on%20this%203D%20data%2E)
|
|
|
AccessViolation_
|
2024-10-19 08:35:42
|
Okay I found it, it really is just stereoscopic solving to get a depth map from DPAF pixels
|
|
|
spider-mario
|
|
AccessViolation_
I'm reading up on dual pixel AF and [this article from Canon](<https://www.usa.canon.com/learning/training-articles/training-articles-list/intro-to-dual-pixel-autofocus-dpaf>) says that the two diodes that make up one photocell also have their signals combined during capturing. I wonder if that gives you some free higher SNR as well, at least for area of the sensor that has DPAF pixels
|
|
2024-10-19 08:36:10
|
the whole sensor is DPAF pixels, but each dual-pixel is two smaller pixels, so no free SNR
|
|
|
AccessViolation_
|
2024-10-19 08:42:11
|
I don't understand, doesn't more samples per pixel mean lower noise? You said before that merging 4 pixels into 1 does reduce noise compared to if you had just 1 pixel, no?
|
|
|
CrushedAsian255
|
2024-10-19 08:42:36
|
It’s like averaging multiple samples in science
|
|
|
spider-mario
|
2024-10-19 08:42:45
|
compared to only one pixel like the 4 you are merging
|
|
2024-10-19 08:42:53
|
not compared to one big pixel of the same size as the 4
|
|
|
lonjil
|
2024-10-19 08:43:18
|
A lot of people online say that increasing your ISO only improves the SNR if a camera is iso-invariant *or* dual-gain, and never otherwise. I'm going crazy.
|
|
|
AccessViolation_
|
|
spider-mario
not compared to one big pixel of the same size as the 4
|
|
2024-10-19 08:43:45
|
Ahh right, that makes sense
|
|
|
spider-mario
|
2024-10-19 08:47:53
|
one big pixel that receives 100 electrons on average, with 1 electron of read noise: 10 electrons of shot noise + 1 electron of read noise = sqrt(101) = 10.05 electrons of noise, SNR = 100 / 10.05 = 9.95 = 19.95 dB
four smaller pixels that each receive 25 electrons on average, also with 1 electron of read noise:
before downsampling: 5 electrons of shot noise + 1 electron of read noise = sqrt(26) = 5.1 electrons of noise, SNR = 25 / 5.1 = 4.9 = 13.8 dB
after downsampling: sqrt(104) = 10.2 electrons of noise, SNR = 100 / 10.2 = 9.8 = 19.8 dB
|
|
|
lonjil
|
2024-10-19 08:49:13
|
that's a very small difference
|
|
|
spider-mario
|
2024-10-19 08:50:06
|
it gets a bit larger at very low signal levels where read noise makes more of a difference (but it might be beyond the point you would consider usable anyway)
|
|
2024-10-19 08:52:01
|
what DxOMark calls “Print” SNR/DR is after downsampling to 8 MP
|
|
2024-10-19 08:52:24
|
“Screen” is at native pixel level
|
|
2024-10-19 08:52:53
|
most reviews that claim an advantage for lower-resolution sensors look at 100%, as in the bottom image
|
|
2024-10-19 08:53:19
|
controlling for this paints a different picture
|
|
|
lonjil
|
2024-10-19 08:54:26
|
what's "measured" ISO?
|
|
|
spider-mario
|
2024-10-19 08:55:30
|
to be fair, the α7S III does do slightly worse than the II, which some people have taken as evidence that downsampling a higher-resolution sensor is not as good, but the performance of the α7R V argues against that interpretation
|
|
|
lonjil
what's "measured" ISO?
|
|
2024-10-19 08:56:03
|
a useful metric with a terribly misleading name: pretty much 78 lx·s ÷ _H_ where _H_ is the focal plane exposure at which the raw data saturates
|
|
2024-10-19 08:57:00
|
which means that looking at the SNR at 18% of that lets us compare cameras at the same absolute light level, which accounts for potential differences in light collection efficiency (“quantum efficiency” or QE)
|
|
2024-10-19 08:59:14
|
(historically, one possible method for computing an “ISO speed” for a digital image was 78 lx·s divided by the focal plane exposure that would saturate the output _processed image_, not raw; DxO took that formula and applied it to raw, which has its uses but has essentially nothing to do with ISO)
|
|
|
lonjil
|
2024-10-19 08:59:51
|
what is lx and s?
|
|
|
spider-mario
|
2024-10-19 09:00:02
|
lx is lux, s is second
|
|
|
lonjil
|
2024-10-19 09:00:32
|
ah
|
|
2024-10-19 09:00:33
|
thanks!
|
|
2024-10-19 09:01:11
|
actually, what exactly does focal plane exposure refer to?
|
|
|
spider-mario
|
2024-10-19 09:02:10
|
https://en.wikipedia.org/wiki/Exposure_(photography)
> In photography, exposure is the amount of light per unit area reaching a frame of photographic film or the surface of an electronic image sensor. It is determined by shutter speed, lens F-number, and scene luminance. Exposure is measured in units of lux-seconds (symbol lx ⋅ s), and can be computed from exposure value (EV) and scene luminance in a specified region.
|
|
2024-10-19 09:02:32
|
approximate formula:
|
|
|
lonjil
|
2024-10-19 09:03:31
|
righto, thanks. The "focal plane" qualifier threw me off.
|
|
|
spider-mario
|
2024-10-19 09:04:56
|
when Luca and I were trying to determine what sort of HDR tone mapping his TV performed, we used this formula in reverse to estimate the luminance with my camera 😁
|
|
|
lonjil
|
2024-10-19 09:05:05
|
nice :)
|
|
2024-10-19 09:05:16
|
Gonna pester you with one more question: which graph on photonstophotos is the right one to look at for determining whether a camera is iso invariant, and how should the graph look? I've seen people online in discussions link to all three of dynamic range shadow improvement, read noise in DNs, and input-referred read noise.
|
|
|
spider-mario
|
2024-10-19 09:05:37
|
input-referred read noise should look flat
|
|
2024-10-19 09:06:10
|
“dynamic range shadow improvement” being close to 0 might be an acceptable proxy
|
|
2024-10-19 09:06:47
|
but the dynamic range it refers to is the “photographic dynamic range” metric that Bill Claff came up with, which uses an arbitrary SNR threshold as the lower bound instead of read noise
|
|
|
lonjil
|
2024-10-19 09:09:05
|
huh, which cameras are even ISO invariant then? I've yet to see one that people say is ISO invariant that is flat on that graph.
And people talk about each of the gain ranges in Sony cameras as being ISO invariant to itself. So supposedly setting the a7RV to 320 ISO and brightening in post should look the same as as shooting at a higher ISO. I've seen a few people demonstrate this but they weren't super rigorous.
|
|
|
spider-mario
|
2024-10-19 09:09:07
|
_Physics of Digital Photography_:
> Although figure 5.21 shows that higher ISO gains yield a higher SNR in the low exposure regions of the image, the advantage gradually lessens each time the ISO gain is raised. Eventually a value is reached where the upstream read noise dominates and a higher ISO gain would bring no further advantage. For the Olympus® E-M1 used to produce figure 5.21, all curves above ISO 800 lie almost on top of each other. The precise ISO setting _S_ above which the corresponding ISO gain would bring no SNR advantage compared with applying digital gain in postprocessing is referred to as the _ISO-less_ setting.
> […]
> Some recent cameras have such low levels of downstream read noise that the ISO-less setting is very low and the camera can be described as being _ISO invariant_ [35].
|
|
|
lonjil
|
2024-10-19 09:10:28
|
ooh, I should get a copy of that
|
|
|
spider-mario
|
2024-10-19 09:11:18
|
using the terminology in that excerpt, the people you mention might have meant that ISO 320 is the α7R V’s ISO-less setting
|
|
2024-10-19 09:12:00
|
(but ultimately, looking at the input-referred read noise curve gives you more information than any categorisation into “ISO-invariant” / “not ISO-invariant”)
|
|
|
lonjil
|
2024-10-19 09:13:09
|
both ranges are closeish to flat
|
|
2024-10-19 09:14:03
|
(d5000 for reference 😄)
|
|
|
spider-mario
using the terminology in that excerpt, the people you mention might have meant that ISO 320 is the α7R V’s ISO-less setting
|
|
2024-10-19 09:15:57
|
what they usually say is 100 is the start of one iso invariant range, and that 320 is the start of another iso invariant range. So presumably they mean that you should shoot at 100 unless it would've been too dark for 300, in which case go to 320 and stay there.
|
|
|
spider-mario
|
2024-10-19 09:16:16
|
yeah, given that curve, that’s probably how I would use it too
|
|
2024-10-19 09:16:29
|
100 or 320 and nothing else
|
|
|
lonjil
|
2024-10-19 09:17:18
|
I'll agree with your statement that this could probably be talked about it better ways than saying that things either are or aren't iso invariant.
|
|
2024-10-19 09:18:07
|
I don't think your rule of thumb regarding the shadow improvement chart works though
|
|
|
spider-mario
|
2024-10-19 09:19:33
|
I think this reflects that those cameras aren’t really “ISO-invariant” in the strict sense (the sense where the ISO-less setting is the base setting)
|
|
|
lonjil
|
|
spider-mario
|
|
lonjil
I'll agree with your statement that this could probably be talked about it better ways than saying that things either are or aren't iso invariant.
|
|
2024-10-19 09:25:49
|
someone I admired would call such binarisation “mutilating barbarism” and “Procrustean deviancy” 😁 https://x.com/JamesMaloneLee3/status/1317756706156400640 https://x.com/JamesMaloneLee3/status/1335629601456926725 https://x.com/JamesMaloneLee3/status/1409056750846844928
|
|
|
lonjil
|
2024-10-19 09:26:56
|
hooray
|
|
2024-10-19 09:29:05
|
ok I made a slight mistake
|
|
2024-10-19 09:29:30
|
I forgot to look up when the C/2024 A3 comet was going to set in my location...
|
|
2024-10-19 09:30:01
|
So if I'm gonna head out in the opposite direction of the airport with my camera, I'll have to aim for something else!
|
|
2024-10-19 09:31:51
|
reckon I can get a magnitude 13.1 comet with my camera? lol
|
|
2024-10-19 09:34:42
|
Guess I'll just have to try tomorrow
|
|
2024-10-19 09:40:18
|
the a7S III looks kinda funny in the input-referred chart
|
|
2024-10-19 09:51:39
|
the plastic bit on my tripod holding the mounting part to the legs just cracked as I picked it up. That's kind of annoying. But at least it didn't happen when the camera was on it.
|
|
|
RaveSteel
|
2024-10-19 09:52:48
|
sheesh
|
|
|
lonjil
|
2024-10-19 09:56:21
|
maybe I can glue it back together...
|
|
|
MSLP
|
|
spider-mario
the above was a stack of somewhat short exposures; here is a single 4-second exposure:
|
|
2024-10-19 10:52:31
|
Cool, what ISO sensitivity was this taken with?
|
|
|
spider-mario
|
2024-10-19 10:54:20
|
originally 12800 but brought back down 2-3 stops
|
|
|
lonjil
|
2024-10-20 06:31:23
|
I went and did some evening bird photography. The sparrows were beyond my ability to track, but I got some nice shots of magpies.
|
|
2024-10-20 06:31:36
|
|
|
2024-10-20 06:31:59
|
|
|
2024-10-20 06:32:38
|
|
|
2024-10-20 06:33:45
|
|
|
|
_wb_
|
2024-10-20 06:55:44
|
<:BlobYay:806132268186861619>
|
|
|
lonjil
|
2024-10-20 07:23:31
|
I think I should buy one of those 18% gray cards so I can better adjust the color balance
|
|
|
spider-mario
|
2024-10-20 08:29:15
|
I bought https://www.greywhitebalancecolourcard.co.uk/
|
|
|
lonjil
|
2024-10-20 08:31:52
|
ty for the suggestion
|
|
|
DZgas Ж
|
|
spider-mario
|
2024-10-21 09:10:46
|
finally pulled the trigger on Canon’s tilt-shift 24mm
|
|
2024-10-21 09:10:51
|
I’ve been eyeing it for close to a year
|
|
|
lonjil
|
|
spider-mario
|
2024-10-21 09:19:59
|
part of why I waited for so long was that I wasn’t 100% sure whether the 17mm, the 24mm or the 50mm would be the most suitable for me
|
|
2024-10-21 09:20:06
|
(I’m still not 100% sure, but somewhat closer)
|
|
|
lonjil
|
2024-10-21 01:41:31
|
Are there any reviewers or sites other than DxoMark that try to assign scores for sharpness?
|
|
|
RaveSteel
|
2024-10-21 01:42:28
|
Lens rentals sometimes has a look at lenses
|
|
2024-10-21 01:42:41
|
Mostly Blogposts
|
|
2024-10-21 01:43:04
|
Not a lens review but a nice article nonetheless
|
|
2024-10-21 01:43:04
|
https://www.lensrentals.com/blog/2017/07/experiments-for-ultra-high-resolution-camera-sensors/
|
|
2024-10-21 01:43:18
|
It is a bit older though
|
|
2024-10-21 01:44:11
|
Wait, they have a section dedicated to rewiews now https://wordpress.lensrentals.com/blog/category/reviews/
|
|
|
lonjil
|
2024-10-21 01:46:19
|
thanks
|
|
|
w
|
2024-10-21 01:47:27
|
i went down the lens sharpness hole and my conclusion was that everything is fine
|
|
|
lonjil
|
2024-10-21 01:47:32
|
I'm trying to figure out which lenses are actually sharp enough to make full use of a 61MP sensor, especially if cropping into a corner
|
|
|
w
i went down the lens sharpness hole and my conclusion was that everything is fine
|
|
2024-10-21 01:47:43
|
hm, aight
|
|
|
RaveSteel
|
2024-10-21 01:48:24
|
Lensrentals did some comparisons with older and newer lenses and concluded indeed that old lenses are perfectly fine
|
|
2024-10-21 01:49:03
|
Sony claims that their GM lenses are good with 100MP, but this is very possibly just marketing
|
|
|
w
|
2024-10-21 01:49:29
|
because even the sharpest lens is bottlenecked by everything else
|
|
|
spider-mario
|
|
lonjil
Are there any reviewers or sites other than DxoMark that try to assign scores for sharpness?
|
|
2024-10-21 01:49:59
|
one-dimensional scores, I’m not sure, but various sharpness numbers can be found on lenstip or OpticalLimits
|
|
|
lonjil
|
|
spider-mario
one-dimensional scores, I’m not sure, but various sharpness numbers can be found on lenstip or OpticalLimits
|
|
2024-10-21 01:50:51
|
more detail than just one number is fine, indeed better for me, thanks!
|
|
|
RaveSteel
|
|
w
because even the sharpest lens is bottlenecked by everything else
|
|
2024-10-21 01:50:51
|
True, also most camera still have that filter in front of the sensors that kind "smoothens" the ingoing light, what was its name again?
|
|
|
spider-mario
|
2024-10-21 01:51:23
|
incidentally, see what Roger Cicala thinks of DxO’s “perceptual megapixels” https://www.lensrentals.com/blog/2019/10/more-ultra-high-resolution-mtf-experiments/#:~:text=Appendix%3A%20Why%20Perceptual%20Megapixels%C2%A0are%20Stupid
|
|
|
w
|
2024-10-21 01:51:29
|
I tried the sony gm 2470 and photos ended up very similar to the 2070 G, ultrawide G and even the kit lens
|
|
|
RaveSteel
|
|
w
because even the sharpest lens is bottlenecked by everything else
|
|
2024-10-21 01:51:34
|
If you are looking for sharpness above all then macro lenses are among the greatest you will find
|
|
2024-10-21 01:51:41
|
otherwise fixed lenses
|
|
|
w
|
2024-10-21 01:51:52
|
yeah for landscape youre bottlenecked by the air
|
|
|
RaveSteel
|
2024-10-21 01:51:55
|
for zoom lenses the wider end is almost always the sharpest
|
|
|
w
yeah for landscape youre bottlenecked by the air
|
|
2024-10-21 01:52:17
|
100% true
|
|
|
w
|
2024-10-21 01:52:52
|
that's how i ended up on getting the lightest thing possible
|
|
2024-10-21 01:52:56
|
because everything else doesnt matter
|
|
|
RaveSteel
|
2024-10-21 01:53:17
|
Gotta get that Sigma 500m 2.8f
https://www.nikonpassion.com/wp-content/uploads/2012/10/sigma_200-500_01.jpg
|
|
|
lonjil
|
2024-10-21 01:53:33
|
I'm gonna put that $100 Viltrox 28mm pancake on a $3000 camera 😵💫
|
|
|
w
|
2024-10-21 01:53:35
|
lightest thing with the fastest AF
|
|
|
RaveSteel
|
|
lonjil
I'm gonna put that $100 Viltrox 28mm pancake on a $3000 camera 😵💫
|
|
2024-10-21 01:53:52
|
Which camera?
|
|
|
w
|
2024-10-21 01:54:03
|
and for sony E, only the latest sony lenses have the better AF
|
|
|
lonjil
|
|
RaveSteel
Which camera?
|
|
2024-10-21 01:54:10
|
a7CR
|
|
|
RaveSteel
|
|
w
and for sony E, only the latest sony lenses have the better AF
|
|
2024-10-21 01:54:31
|
The older lenses may be slower, but fast nonetheless
|
|
2024-10-21 01:54:41
|
except for the 50mm 1.8f smh
|
|
|
spider-mario
|
|
RaveSteel
Gotta get that Sigma 500m 2.8f
https://www.nikonpassion.com/wp-content/uploads/2012/10/sigma_200-500_01.jpg
|
|
2024-10-21 01:55:14
|
a.k.a. the “Bigma”
|
|
2024-10-21 01:56:00
|
Christopher Frost reviewed it: https://youtu.be/C9UnFxwww3Y
|
|
|
lonjil
|
2024-10-21 01:56:11
|
Yesterday was the first time I've managed to track a magpie at close enough distance to get a nice shot. I failed around 2/3rds of my attemtps. But when I succeeded, the autofocus failed to be fast enough around half the time.
|
|
|
RaveSteel
|
2024-10-21 01:56:31
|
I wielded that Sigma a few times, it is truly massive
|
|
|
lonjil
Yesterday was the first time I've managed to track a magpie at close enough distance to get a nice shot. I failed around 2/3rds of my attemtps. But when I succeeded, the autofocus failed to be fast enough around half the time.
|
|
2024-10-21 01:56:58
|
With the pancake lens you mentioned?
|
|
2024-10-21 01:57:01
|
Or a tele?
|
|
|
lonjil
|
2024-10-21 01:57:35
|
What I mentioned is what I want to buy in the future (though maybe I'll have different plans by the time I have the money)
|
|
2024-10-21 01:57:58
|
So with my Nikon D5000 with a 70 to 200mm tele
|
|
|
w
|
2024-10-21 01:58:06
|
some warning the big MP images are a pain to work with
|
|
2024-10-21 01:58:20
|
you can ONLY use sony's software or latest lightroom
|
|
|
lonjil
|
|
w
|
2024-10-21 01:58:30
|
the files are HUGE
|
|
2024-10-21 01:58:36
|
you need at least UHS-II sd card
|
|
|
lonjil
|
2024-10-21 01:58:40
|
Good thing I'll be able to afford a macbook at the same time
|
|
|
spider-mario
|
2024-10-21 01:58:40
|
you mean the pixel-shift images?
|
|
|
w
|
2024-10-21 01:58:50
|
the regular images
|
|
|
spider-mario
|
2024-10-21 01:58:52
|
native shots should be fine, right?
|
|
2024-10-21 01:58:56
|
ah
|
|
|
RaveSteel
|
2024-10-21 01:59:02
|
Darktable and RawTherapee don't work with them?
|
|
|
w
|
2024-10-21 01:59:09
|
they dont support ARW 4.0
|
|
|
RaveSteel
|
2024-10-21 01:59:12
|
Darn
|
|
2024-10-21 01:59:22
|
I hate proprietary formats
|
|
2024-10-21 01:59:53
|
And the sony software is crappy enough as is
|
|
|
w
|
2024-10-21 01:59:54
|
you will ONLY use JPEG and TIF
|
|
2024-10-21 01:59:59
|
bcause other formats are too laggy
|
|
|
spider-mario
|
2024-10-21 02:00:02
|
DxO PhotoLab says it supports α7C R files except “RAW M and S”
|
|
|
lonjil
|
2024-10-21 02:00:52
|
honestly I quite like the JPEGs I get out of my 15 year old Nikon and presumably recent cameras are even better at producing JPEGs
|
|
|
w
|
2024-10-21 02:01:08
|
yeah the jpegs are good
|
|
|
w
bcause other formats are too laggy
|
|
2024-10-21 02:01:33
|
for this I mean when you are processing on your computer
|
|
2024-10-21 02:02:23
|
lightroom takes AGES to load the images in the import dialog
|
|
|
lonjil
|
2024-10-21 02:02:31
|
Though I read that Sonys don't have any function to do raw->jpeg conversion on the camera, so presumably I won't be able to take a photo and then decide it needed to be stepped up or down a bit.
|
|
|
RaveSteel
|
2024-10-21 02:02:33
|
Lightroom is slow in general
|
|
|
w
|
2024-10-21 02:02:48
|
for shooting you do jpeg+raw
|
|
|
lonjil
|
|
RaveSteel
|
2024-10-21 02:03:21
|
Am I the only one who exclusively shoots RAW? xd
|
|
2024-10-21 02:03:31
|
Camera JPEGs are a waste of space imo
|
|
|
w
|
2024-10-21 02:03:54
|
made me think yeah i probably can not use jpeg
|
|
2024-10-21 02:04:02
|
since the raws have previews
|
|
2024-10-21 02:04:09
|
and load as fast as the jpeg
|
|
|
lonjil
|
2024-10-21 02:04:16
|
They should add a mode that does the same processing as the built in JPEG conversion, but stores it as a 16-bit JXL file so all the detail remains.
|
|
|
w
|
2024-10-21 02:04:34
|
if you put those images in jxl your computer will explode
|
|
|
RaveSteel
|
2024-10-21 02:05:07
|
JXL support in 5 years maybe, sad
|
|
|
lonjil
|
2024-10-21 02:05:09
|
with streaming decoding it will be fine
|
|
|
w
|
2024-10-21 02:06:44
|
so that's why I think getting the a7cii may have been a better experience
|
|
|
RaveSteel
|
2024-10-21 02:06:49
|
Ok, at least darktable was able to open an ARW for the 7CR
|
|
|
w
|
2024-10-21 02:07:44
|
maybe I would have had the possibility of editing on the go
|
|
|
lonjil
|
2024-10-21 02:08:03
|
Do you ever shoot in the downsampled modes?
|
|
|
w
|
|
RaveSteel
|
2024-10-21 02:09:20
|
Anything like downsampling can be done easily in post
|
|
2024-10-21 02:09:37
|
Greater control and better results
|
|
|
lonjil
|
2024-10-21 02:10:33
|
Sure, but if you want more manageable file sizes and don't care about losing the higher resolution, it works.
|
|
|
w
|
2024-10-21 02:11:42
|
i paid full price for this so I may aswell use it all
|
|
|
RaveSteel
|
2024-10-21 02:11:52
|
Agreed
|
|
|
w
|
2024-10-21 02:12:00
|
no blessing only curse
|
|
|
RaveSteel
|
2024-10-21 02:12:20
|
"Storage is cheap" I have almost a TB in my camera
|
|
|
w
|
2024-10-21 02:12:43
|
yeah i carry 2 512gb cards
|
|
|
RaveSteel
|
2024-10-21 02:12:55
|
heck yeah
|
|
|
w
|
2024-10-21 02:12:57
|
it's not expensive
|
|
|
RaveSteel
|
2024-10-21 02:13:16
|
I paid 25€ for one 512gb card
|
|
2024-10-21 02:13:32
|
my early bought 64gb uhs-ii was 120€ lol
|
|
2024-10-21 02:13:51
|
but well, early adopters always pay a premium
|
|
|
lonjil
|
|
spider-mario
incidentally, see what Roger Cicala thinks of DxO’s “perceptual megapixels” https://www.lensrentals.com/blog/2019/10/more-ultra-high-resolution-mtf-experiments/#:~:text=Appendix%3A%20Why%20Perceptual%20Megapixels%C2%A0are%20Stupid
|
|
2024-10-21 02:14:15
|
to be fair, DxO doesn't assign a perceptual megapixel score to just a lens, but to a lens and body together. For example, Sony FE 28mm F2 on an A7R II gets 35 P-Mpix, and on an A7R IV it gets 47 P-Mpix.
|
|
|
RaveSteel
|
2024-10-21 02:15:04
|
Lensrental uses machines that do not rely on cameras at all, ony the lens itself is tested
|
|
2024-10-21 02:15:17
|
I forgot the name, it's been a while
|
|
|
spider-mario
|
|
lonjil
Though I read that Sonys don't have any function to do raw->jpeg conversion on the camera, so presumably I won't be able to take a photo and then decide it needed to be stepped up or down a bit.
|
|
2024-10-21 02:24:59
|
using Sony’s software, you might
|
|
|
RaveSteel
I forgot the name, it's been a while
|
|
2024-10-21 02:25:04
|
bench?
|
|
2024-10-21 02:25:34
|
https://www.lensrentals.com/blog/2014/05/introducing-the-optical-bench/
|
|
2024-10-21 02:26:24
|
with all that said: https://www.dpreview.com/opinion/4042117089/roger-cicala-why-i-dont-use-an-mtf-bench-to-test-my-own-lenses
|
|
|
lonjil
|
|
spider-mario
using Sony’s software, you might
|
|
2024-10-21 02:26:34
|
Indeed, which sounds a lot more annoying than doing in on camera, considering how janky vendor software often is (and everyone seems to complain about Sony's camera related software).
Doubly annoying because I'm on Linux 😄
|
|
|
RaveSteel
|
2024-10-21 02:27:35
|
My own camera isn't even supported by sony's mobile apps anymore
|
|
2024-10-21 02:28:39
|
Very fun, i was on the road and wanted to remote control my camera, only to find out that the app had updated and quietly removed support for my camera
|
|
|
lonjil
|
2024-10-21 02:28:57
|
Oh and I doubly hate supposed features that require a vendor app to use. Like ok I can control the camera with the Sony camera whatever app, but what happens when the camera is 10, 15 years old? It'll still be very good, but oops now it's worse because of lack of app support.
|
|
|
RaveSteel
|
2024-10-21 02:29:29
|
Doesn't need to be 10 years, my camera is 6 years old and support was removed when it was 5 years old
|
|
2024-10-21 02:30:39
|
Sony is also not very good regarding firmware updates, my camera received its last one three years into its life
|
|
|
lonjil
|
|
RaveSteel
|
2024-10-21 02:31:28
|
Which in my case, with the a7III, means that I did not receive the update that removed the 29:59 limit for video recording for example
|
|
2024-10-21 02:32:08
|
Not a large issue, but annoying nonetheless
|
|
|
spider-mario
|
2024-10-21 02:36:31
|
my EOS R6 still receives firmware updates _but_ that still doesn’t include lifting the 29:59 restriction AFAIK
|
|
|
RaveSteel
|
2024-10-21 02:37:27
|
Man...
|
|
|
w
|
2024-10-21 03:04:09
|
my catalog here <https://tanbou.grass.moe/2024/05/mygo/> is all taken with the a7cR
|
|
|
lonjil
|
2024-10-21 03:07:40
|
nice photos 🙂
|
|
|
w
|
2024-10-21 03:13:19
|
thx, was most fun lining them up
|
|
2024-10-21 03:13:41
|
some more phone crashers
|
|
2024-10-21 03:13:49
|
from last week
|
|
|
RaveSteel
|
|
_wb_
|
2024-10-21 03:24:11
|
the New Yorker photo and the playground+tower photo might be nice to develop in HDR, they look like they would make interesting test images 🙂
|
|
|
RaveSteel
|
2024-10-21 03:28:01
|
Does developing HDR only work in Lightroom etc? What does the workflow look like? Or is it enough to export to rec2020?
|
|
|
w
|
2024-10-21 03:32:57
|
there ought to be a way for lightroom to use a phone as preview
|
|
2024-10-21 04:36:20
|
i can't get the hdr output in lightroom to work
|
|
|
spider-mario
|
2024-10-21 07:02:32
|
https://www.filmpixmedia.com/laowa-55mm-and-100mm-f-2-8-ffii-tilt-shift-macro-lenses-finally-announced/
|
|
2024-10-21 07:02:47
|
just today 😂
|
|
|
RaveSteel
|
2024-10-21 07:10:39
|
mfw no unlimited budget to satisfy GAS
|
|
|
Fox Wizard
|
2024-10-21 07:10:47
|
Gotta buy them all™️
|
|
|
spider-mario
|
2024-10-21 07:17:40
|
a secondary problem is having enough space to store it all
|
|
|
lonjil
|
2024-10-21 08:15:17
|
ooh
|
|
2024-10-21 09:43:04
|
here's a photo I took a few years ago on my phone at 3:30 in the morning
|
|
2024-10-21 09:45:42
|
|
|
2024-10-21 09:45:52
|
|
|
2024-10-21 09:46:08
|
|
|
|
AccessViolation_
|
2024-10-21 10:37:42
|
Those look incredible
|
|
2024-10-21 10:37:44
|
I love fog
|
|
|
lonjil
|
2024-10-21 11:03:19
|
^_^
|
|
2024-10-21 11:03:34
|
I love anti-crepuscular rays
|
|
2024-10-21 11:04:08
|
Here is a photo from last winter. Rare light pillars caused by ice crystals perfectly suspended in the air.
|
|
2024-10-21 11:04:56
|
When I went to the grocery store, there were miniature light pillars literally less than a meter from my face
|
|
|
AccessViolation_
|
|
lonjil
I love anti-crepuscular rays
|
|
2024-10-22 10:32:31
|
That's interesting! I never thought about it but it makes sense that the same light rays also appear to converge opposite of the sun
|
|
|
lonjil
|
2024-10-22 10:36:26
|
it's cool
|
|
2024-10-22 10:38:08
|
Anyway completely different topic. So the 48 MP sensor in the a7S III has a quad bayer pattern like this, and is downsampled during readout as shown in the picture. This allows for faster readout rates, useful for video.
|
|
2024-10-22 10:41:42
|
If you were making a sensor primary for still photography, but you wanted faster readout rates, would a downsample like this make sense? You get some funky overlap in the locations of the photosites of each combined readout pixel, which might lead to something weird? Probably fine though. And I'm sure you could find a better pattern for the green pixels.
|
|
2024-10-22 10:42:34
|
I think the effective resolution would be lower this way, but that's probably fine.
|
|
|
spider-mario
|
2024-10-22 11:06:54
|
in principle, I think it should be possible to simulate the kind of artifacts we would get
|
|
2024-10-22 11:08:01
|
high-resolution input (photographic or rendered) -> simulate sensor with that pattern -> downsample as you describe -> demosaicise -> output
|
|
|
lonjil
|
2024-10-22 11:59:34
|
oh, that'd be a fun little project
|
|
|
spider-mario
|
2024-10-22 12:17:46
|
from what I recall, one potential drawback of this approach is that with very small pixels, CFA cross-talk can be an issue
|
|
2024-10-22 12:18:16
|
(light goes through one type of filter but ends up captured by a pixel that’s supposed to have a different filter)
|
|
2024-10-22 12:19:13
|
ah: https://www.dpreview.com/forums/post/59967266
> Sony essentially eliminated the problem in the a7RII with the combination of BSI and low-profile microlenses, without losing the high fill factor.
|
|
|
AccessViolation_
|
2024-10-22 12:35:27
|
Is chromatic aberration not something you can correct for if you know the properties of the lens? I noticed chromatic aberration correction in Darktable isn't part of the lens correction module, and it's something I need to hand-tune, it doesn't calculate the parameters for my specific camera + lens it seems
|
|
2024-10-22 12:35:57
|
Oh also I updated Darktable and my lens is actually in the database now, which is awesome
|
|
|
spider-mario
|
2024-10-22 12:49:08
|
iirc, there’s both
|
|
2024-10-22 12:49:33
|
lensfun (used by the lens correction module) definitely has CA data (I’ve contributed some), and the module can apply them
|
|
2024-10-22 12:49:50
|
but there might be an _additional_ module that can also correct them from manually tuned parameters
|
|
2024-10-22 12:51:30
|
https://github.com/lensfun/lensfun/commit/5c78d634364abfe2b6d895a4ea3eb0be7367a294
|
|
2024-10-22 12:52:13
|
more generally: https://lensfun.github.io/lenslist/
|
|
|
AccessViolation_
|
2024-10-22 01:51:41
|
Oh, TCA is chromatic aberration correction? I tried the TCA option on its own in the Lens correction module and it didn't seem to change anything. Maybe my lens doesn't have TCA data associated with it
|
|
2024-10-22 02:01:03
|
I just checked, my lens (Canon RF-S 18-45mm F4.5-6.3 IS STM) only has distortion and vignetting information associated with it, so that explains it
|
|
|
w
|
2024-10-22 02:11:32
|
can darktable do hdr?
|
|
|
AccessViolation_
|
2024-10-22 02:16:45
|
It can export in HDR yeah. I don't know if it has HDR in the editing view. I don't have a HDR display so I can't test
|
|
|
spider-mario
|
|
AccessViolation_
Oh, TCA is chromatic aberration correction? I tried the TCA option on its own in the Lens correction module and it didn't seem to change anything. Maybe my lens doesn't have TCA data associated with it
|
|
2024-10-22 02:20:13
|
TCA is transverse (a.k.a. lateral) chromatic aberration which is the correctable kind (as opposed to axial/longitudinal chromatic aberration)
|
|
2024-10-22 02:20:40
|
(as Wikipedia points out, “LCA” could refer to either lateral or longitudinal CA so it’s ambiguous and should be avoided)
|
|
2024-10-22 02:22:11
|
https://commons.wikimedia.org/wiki/File:Comparison_axial_lateral_chromatic_aberration.svg
1: no CA
2: axial/longitudinal CA (different wavelengths focus at different distances)
3: transverse/lateral CA (different wavelengths focus on the same plane but at different locations on it; only occurs off-axis)
|
|
|
RaveSteel
|
|
w
can darktable do hdr?
|
|
2024-10-22 02:22:25
|
|
|
|
AccessViolation_
|
|
spider-mario
https://commons.wikimedia.org/wiki/File:Comparison_axial_lateral_chromatic_aberration.svg
1: no CA
2: axial/longitudinal CA (different wavelengths focus at different distances)
3: transverse/lateral CA (different wavelengths focus on the same plane but at different locations on it; only occurs off-axis)
|
|
2024-10-22 02:22:38
|
Ah, good to know
|
|
|
spider-mario
|
2024-10-22 02:22:58
|
it can technically export to HDR, but without being able to see what you output before you export it, it’s hardly usable in practice
|
|
|
AccessViolation_
I just checked, my lens (Canon RF-S 18-45mm F4.5-6.3 IS STM) only has distortion and vignetting information associated with it, so that explains it
|
|
2024-10-22 02:23:26
|
oh, that’s quite a rare combination
|
|
|
w
|
2024-10-22 02:23:32
|
does darktable have a auto color button light in lightroom
|
|
|
spider-mario
|
2024-10-22 02:23:37
|
usually, it’s distortion+CA but no vignetting
|
|
|
AccessViolation_
|
|
w
does darktable have a auto color button light in lightroom
|
|
2024-10-22 02:24:38
|
A bunch of modules have auto options. I think by default it goes derives the options it uses from the metadata in the raw file. It's free software and they have a flatpak, so it's pretty easy to try out if you wanna mess with it, but I'll answer that specific question in a bit
|
|
|
w
|
2024-10-22 02:28:06
|
waiting minutes for avif export...
|
|
2024-10-22 02:29:06
|
lightroom's avif is only seconds is this e0 or something
|
|
2024-10-22 02:30:53
|
phone fails to load this 🤦
|
|
|
AccessViolation_
|
|
spider-mario
usually, it’s distortion+CA but no vignetting
|
|
2024-10-22 02:31:35
|
Ah well I'm very glad it has vignetting correction as it's *very* visible at 18 mm. I'm more okay with not having CA correction, I didn't even notice it until someone zoomed in and pointed it out to me, and the defaults for the manual CA correction module take care of it well it seems. Although it does also remove some of the vibrancy and color on things exhibiting subsurface scattering which is a bit of a shame. I'll probably leave it off or learn to apply it selectively
|
|
2024-10-22 02:33:00
|
How do you go about collecting metrics like these for Lensfun? Do you have like a test pattern that you point your camera at and take many different pictures at different configurations, and the software using the data interpolates the rest?
|
|
|
w
|
2024-10-22 02:33:29
|
probably the checkerboard
|
|
|
AccessViolation_
|
2024-10-22 02:37:30
|
How does the camera do it? Does it have an internal dataset or is that data stored digitally in the lens?
|
|
|
w
|
2024-10-22 02:37:54
|
my photos have the lens data embedded
|
|
2024-10-22 02:38:04
|
the lens communicates the data to the camera
|
|
2024-10-22 02:38:24
|
the lens has a firmware
|
|
|
AccessViolation_
|
2024-10-22 02:39:40
|
Right, but how does the camera know which corrections to apply based on that data. I can also see data like aperture, focal distance, etc, but without the Lensfun database Darktable still doesn't know how to correct for it, so presumably either the lens communicates the rules for applying corrections to the camera or the camera has a dataset of these rules
|
|
|
w
|
2024-10-22 02:40:30
|
https://docs.opencv.org/4.x/dc/dbb/tutorial_py_calibration.html
|
|
2024-10-22 02:40:38
|
this is for distortion
|
|
2024-10-22 02:40:51
|
but it's a single formula and just 5 numbers
|
|
2024-10-22 02:41:22
|
but there's just... more data i guess
|
|
2024-10-22 02:42:59
|
yup there is just more data
|
|
2024-10-22 02:43:10
|
> Vignetting Corr Params : 16 0 64 256 576 1024 1568 2176 2880 3648 4416 5248 6048 7040 8288 9952 11488
> Chromatic Aberration Corr Params: 32 640 896 896 1024 1024 1024 896 896 896 896 896 768 640 512 384 128 -256 -384 -512 -640 -640 -640 -512 -512 -512 -384 -256 -128 -128 0 256 512
> Distortion Corr Params : 16 0 -10 -40 -89 -157 -243 -347 -465 -597 -741 -896 -1059 -1229 -1405 -1585 -1767
etc
|
|
|
spider-mario
|
|
AccessViolation_
How do you go about collecting metrics like these for Lensfun? Do you have like a test pattern that you point your camera at and take many different pictures at different configurations, and the software using the data interpolates the rest?
|
|
2024-10-22 02:51:36
|
I think I followed https://pixls.us/articles/create-lens-calibration-data-for-lensfun/
|
|
|
AccessViolation_
Right, but how does the camera know which corrections to apply based on that data. I can also see data like aperture, focal distance, etc, but without the Lensfun database Darktable still doesn't know how to correct for it, so presumably either the lens communicates the rules for applying corrections to the camera or the camera has a dataset of these rules
|
|
2024-10-22 02:52:32
|
the raw files should contain the data in question, but darktable currently doesn’t read it
|
|
2024-10-22 02:53:51
|
also, in proprietary raw formats, it might not be clear how to read it in the first place – but Adobe DNG Converter then makes it accessible as OpcodeList3 https://helpx.adobe.com/content/dam/help/en/photoshop/pdf/DNG_Spec_1_7_1_0.pdf#page=105
|
|
2024-10-22 02:54:49
|
> WarpRectilinear: This opcode applies a warp to an image and can be used to correct geometric distortion and lateral (transverse) chromatic aberration for rectilinear lenses. The warp function supports both radial and tangential distortion correction.
|
|
|
AccessViolation_
|
|
spider-mario
|
|
AccessViolation_
Ah well I'm very glad it has vignetting correction as it's *very* visible at 18 mm. I'm more okay with not having CA correction, I didn't even notice it until someone zoomed in and pointed it out to me, and the defaults for the manual CA correction module take care of it well it seems. Although it does also remove some of the vibrancy and color on things exhibiting subsurface scattering which is a bit of a shame. I'll probably leave it off or learn to apply it selectively
|
|
2024-10-22 02:56:27
|
ah, right, I remember that module now – iirc, it kind of “cheats” in that it “corrects” TCA by just desaturating edges
|
|
2024-10-22 02:56:49
|
instead of actually rescaling the colour channels so that they align again
|
|
|
AccessViolation_
|
2024-10-22 02:59:43
|
Yeah that checks out with what I've seen
|
|
|
lonjil
|
2024-10-22 07:39:49
|
I find it slightly funny that several a7R V and a7CR reviews rave about how good the noise performance becomes when they put it into downsample mode
|
|
2024-10-22 08:07:15
|
paraphrased representation of reviews:
*zooms both images to 100%*
"As you can see, the a7CR is noisier than the a7C II, but if we bring up the a7CR medium downsample, it looks really clean"
|
|
|
spider-mario
|
2024-10-22 08:45:17
|
_effectively zooms the α7CR image 1.35× as much_
“as you can see, it’s noisier”
`surprised_pikachu.png`
|
|
|
lonjil
|
2024-10-22 08:49:10
|
it's crazy too, they're open right next to each other, you can see how much bigger one is!
|
|
2024-10-23 12:42:07
|
In this video, the a7S III looks very good compared to the a7R V, even though he shows the images at the same proper scale https://www.youtube.com/watch?v=HdPAfAMPnls
very likely that there is some confounding factor I am missing that would explain it, though. The fact that the second gain stage kicks in at a much higher ISO is interesting, but I'm not sure how much it might explain.
|
|
|
w
|
2024-10-23 02:23:09
|
because megapixels aren't everything!!!
|
|
2024-10-23 02:24:06
|
I always remember when my artist friend from elementary school always says 2 megapixels is enough
|
|
|
lonjil
|
2024-10-23 07:42:56
|
a7S III has a 48 MP sensor tho!
|
|
|
spider-mario
|
2024-10-23 09:07:05
|
it’s a bit hard to tell because they don’t look developed with the same amount of contrast
|
|
2024-10-23 09:07:17
|
higher contrast would exaggerate noise
|
|
2024-10-23 09:08:00
|
if using e.g. unsharp masking, one would need to make sure to adjust the radius accordingly
|
|
2024-10-23 09:08:08
|
not use a radius of the same number of pixels
|
|
|
lonjil
|
2024-10-23 09:23:29
|
Ah, good point
|
|
|
AccessViolation_
|
2024-10-23 05:39:49
|
|
|
2024-10-23 05:39:58
|
|
|
2024-10-23 05:40:33
|
I've waited a couple of days for fog, today I was able to try out my camera in this weather for the first time 👀
|
|
2024-10-23 05:43:31
|
The previews mess up some of the details, so if you click "open in browser" you can make out some shapes in the fog
|
|
|
lonjil
|
2024-10-23 06:38:28
|
Niiice
|
|
|
spider-mario
|
2024-10-24 08:57:51
|
as I was hoping, it seems that I can use the shift feature of the 24mm not only to correct for the keystone effect, but also, on the contrary, to exaggerate it
|
|
2024-10-24 08:58:19
|
and thereby, get sort of an UWA effect without actually taking an UWA picture
|
|
|
lonjil
|
2024-10-24 09:12:26
|
hooray
|
|
|
AccessViolation_
|
2024-10-24 09:40:29
|
Do you guys usually shoot with noise reduction with high ISO?
|
|
2024-10-24 09:43:44
|
I have it on default, but a colleague said they always shoot with noise reduction off. I'm thinking they probably have a much better sensor since their camera is like three times more expensive
|
|
2024-10-24 09:46:35
|
I know there's no one right answer, I'm just curious what you guys do
|
|
|
spider-mario
|
2024-10-24 09:52:29
|
if you are referring to what Sony calls [“Long Exposure NR”](https://helpguide.sony.net/ilc/1720/v1/en/contents/TP0001629724.html), it refers to the camera automatically taking a dark frame of the same duration to use for subtraction
|
|
2024-10-24 09:53:12
|
“High ISO NR”, on the other hand, would not affect raws
|
|
2024-10-24 09:53:43
|
I shoot raw so I apply however much noise reduction I need for each image
|
|
2024-10-24 09:53:58
|
(and haven’t felt too much need to deal with dark frames so far)
|
|
2024-10-24 09:54:41
|
https://photographylife.com/long-exposure-noise-reduction#what-is-long-exposure-noise-reduction
|
|
|
AccessViolation_
|
2024-10-24 09:58:07
|
I'm using a Canon EOS R100. I just mean the noise reduction it does "by default" which they call high ISO noise reduction. Long exposure noise reduction is a separate option that happens for exposures longer than 1 s, and it's off by default
|
|
|
spider-mario
I shoot raw so I apply however much noise reduction I need for each image
|
|
2024-10-24 09:59:15
|
Yeah that's a good point, I shoot JPEG + RAW so I can always create one without noise reduction if I want I suppose
|
|
2024-10-24 10:04:18
|
I didn't know long exposure noise reduction worked like that, that's clever. I should have enabled it when trying to take pictures of the night sky. I assumed it would just do a normal denoise pass so I left it off
|
|
|
spider-mario
|
2024-10-24 10:40:09
|
you can also take the dark frames yourself, which gives you more control (although it also means you need to use software that’s capable of utilising them)
|
|
2024-10-24 10:40:41
|
it lets you _stack_ dark frames, for example
|
|
|
AccessViolation_
|
2024-10-24 10:49:19
|
I'm going to try long exposure NR with the lens cap on. It should take two identical dark pictures that are subtracted from each other and then I should be left with only the random noise and no static sensor artifacts. If you then compare that to the same picture without long exposure NR, I wonder if that gives you some idea of the quality of your sensor
|
|
2024-10-24 10:58:22
|
Interestingly the ones taken with long exposure NR seem overall brighter and more noisy compared to those without
|
|
2024-10-24 11:02:03
|
The corners seem brighter, I thought it might be light leaking in past the lens cap but it's also possible it's the vingetting correction
|
|
|
TheBigBadBoy - 𝙸𝚛
|
2024-10-25 08:37:38
|
First time I see the Atomium at night
Didn't know there were lights on it <:KekDog:805390049033191445>
|
|
|
lonjil
|
|
TheBigBadBoy - 𝙸𝚛
|
2024-10-25 10:31:12
|
but as expected from a phone camera, really high noise
|
|
|
CrushedAsian255
|
2024-10-25 10:55:39
|
What model of phone?
|
|
|
TheBigBadBoy - 𝙸𝚛
|
2024-10-25 02:19:35
|
Xiaomi Mi Note 10
|
|
2024-10-25 02:19:53
|
and that pic was taken with the 2X zoom camera
|
|
2024-10-25 02:21:05
|
never buying Xiaomi ever again
|
|
2024-10-25 02:21:11
|
too many SW problems
|
|
|
AccessViolation_
|
2024-10-25 03:47:02
|
Huh I was expecting a Google Pixel because the filename starts with PXL
|
|
2024-10-25 03:47:10
|
Did you use gcam?
|
|
|
TheBigBadBoy - 𝙸𝚛
|
2024-10-25 07:26:12
|
yeah (a custom one tho)
LineAgeOS, signed with Pixel keys <:KekDog:805390049033191445>
So I have unlimited Google Photo storage lol
|
|
|
RaveSteel
|
2024-10-25 08:00:34
|
I thought they scraped that
|
|
|
TheBigBadBoy - 𝙸𝚛
|
2024-10-25 08:13:17
|
mmmh, did not check for quite some time true
at least it was the case when I started using it
|
|
|
spider-mario
|
2024-10-26 09:25:30
|
first outing with the tilt-shift 24mm
|
|
2024-10-26 09:25:33
|
(just tilt here)
|
|
|
AccessViolation_
|
2024-10-26 09:30:22
|
I wonder if people would misclassify images taken with this lens as being AI generated because "the focus doesn't make sense"
|
|
|
lonjil
|
2024-10-26 10:37:32
|
very cool
|
|
|
DZgas Ж
|
2024-10-28 04:18:47
|
out city 🌌
|
|
|
jonnyawsom3
|
2024-10-29 04:13:24
|
If you ignore the slightly clickbait title, a neat little video of a DIY camera with a single photodiode and a color wheel https://youtu.be/Y-WEyZHIDFo
|
|
|
CrushedAsian255
|
|
If you ignore the slightly clickbait title, a neat little video of a DIY camera with a single photodiode and a color wheel https://youtu.be/Y-WEyZHIDFo
|
|
2024-11-02 10:18:56
|
theoretically you can replace the little camera with an actual camera and use it to get automatic panoramas?
|
|
|
lonjil
|
2024-11-03 10:43:28
|
I'm quite confused by something in this article, <https://clarkvision.com/articles/iso/>, specifically the section "Camera Dependent ISO Definitions":
> So let's say you have lenses that on each of the above 3 cameras that deliver the same photons per second to a pixel. Then if we set the exposure time the same on all three, each camera gets the same true exposure.
Since each of the three cameras have differently sized pixels, the amount of light per area is different, doesn't sound like the same exposure to me, nor does it seem like a reasonable comparison.
I guess if you want comparisons that make sense at 100% zoom, but why would you want that?
|
|
|
spider-mario
|
2024-11-03 10:58:47
|
I think his definition of “true exposure” departs from focal plane exposure
|
|
2024-11-03 10:58:54
|
we might be able to find his definition somewhere else on the site
|
|
2024-11-03 10:59:10
|
oh, yeah, here it is: https://clarkvision.com/articles/exposure/
|
|
2024-11-03 10:59:19
|
> _**True exposure**_: the actual amount of light recorded, e.g. expressed in photons (or photoelectrons) on the subject. Remember, the subject is what we are concerned about in our images, not pixels.
|
|
|
lonjil
|
2024-11-03 11:02:09
|
That sounds like light per solid angle or something, which also wouldn't result in the same amount of photons per pixel.
|
|
2024-11-03 11:03:19
|
Other than the case where a smaller sensor and a larger sensor have an equal number of pixels, and lenses chosen to capture the same angle of view, but that wasn't the case in the ISO article. (16, 18, and 21 MPix)
|
|
|
diskorduser
|
|
TheBigBadBoy - 𝙸𝚛
but as expected from a phone camera, really high noise
|
|
2024-11-07 05:54:50
|
High noise is there because he is using an incorrect noise model in gcam.
|
|
|
TheBigBadBoy - 𝙸𝚛
|
2024-11-07 06:34:36
|
same noise if I use the default camera app
|
|
|
spider-mario
|
2024-11-07 08:27:09
|
https://www.dpreview.com/news/2325465902/laowa-cf-12-24-f5p6-zoom-shift-lens-global-availability
a shift zoom??
|
|
|
lonjil
|
|
190n
|
|
spider-mario
https://www.dpreview.com/news/2325465902/laowa-cf-12-24-f5p6-zoom-shift-lens-global-availability
a shift zoom??
|
|
2024-11-09 02:16:21
|
whoaaaaaa
|
|
2024-11-09 02:16:28
|
didn't know what shift lenses were but this sounds super cool
|
|
2024-11-09 02:16:29
|
|
|
|
spider-mario
|
2024-11-09 10:21:23
|
“keystone effect” (https://en.wikipedia.org/wiki/Keystone_effect) is maybe a better term than “perspective distortion”, given that the perspective without shift is exactly as you would expect
|
|
|
AccessViolation_
|
2024-11-09 08:00:33
|
Dang it, Canon makes no ~18 mm, low light APS-C lenses...
|
|
2024-11-09 08:07:22
|
Anything faster than F3.0 is for full frame cameras, making them not very wide angle on my camera
|
|
|
lonjil
|
2024-11-09 08:11:58
|
really? huh
|
|
2024-11-09 08:13:10
|
Isn't F3 on APS-C equivalent to like F4.5 on full frame at equal angle's of view in terms of light? Kinda crazy that they don't have anything brighter than that.
|
|
|
AccessViolation_
|
2024-11-09 08:14:15
|
Hmm, I didn't think of that
|
|
2024-11-09 08:14:20
|
That just makes it worse
|
|
2024-11-09 08:16:50
|
The fastest my kit lens can go is 18 mm F4.5 which as it turns out really isn't that good for nighttime photography
|
|
|
spider-mario
|
|
AccessViolation_
Anything faster than F3.0 is for full frame cameras, making them not very wide angle on my camera
|
|
2024-11-09 08:17:47
|
I’m not sure I understand the issue – it should be just as wide as an APS-C lens of the same focal length?
|
|
2024-11-09 08:17:55
|
e.g. what’s wrong with https://www.dpreview.com/products/canon/lenses/canon_rf_16_2p8_stm ?
|
|
|
AccessViolation_
|
2024-11-09 08:20:31
|
On an APS-C camera that becomes a 26 mm F4.5 full-frame equivalent
|
|
|
spider-mario
|
2024-11-09 08:20:53
|
sure, as would any 16mm lens, whether it’s made for APS-C or not
|
|
|
lonjil
|
2024-11-09 08:21:39
|
Outside of very small cameras, like phones, all lenses are specified by their real physical focal length
|
|
2024-11-09 08:22:06
|
So an 18mm lens gives the same angle of view on APS-C regardless of whether the lens was designed for APS-C or for full frame.
|
|
|
spider-mario
|
2024-11-09 08:22:15
|
that it’s made for FF just means the image circle extends further than necessary beyond an APS-C sensor
|
|
2024-11-09 08:22:40
|
with content that an APS-C lens would just crop off
|
|
|
AccessViolation_
|
2024-11-09 08:25:34
|
Ah, gotcha. But on Canon's RF-S lenses (specifically for APS-C, unlike their RF lenses) don't they compensate those reported specs? Like, an RF18mm lens on a full frame camera would produce the same image as an RF-S18mm lens on an APS-C camera?
|
|
|
lonjil
|
2024-11-09 08:31:46
|
I'm 99% sure RF-S lenses have their real physical focal length as the reported focal length
|
|
|
AccessViolation_
|
2024-11-09 08:32:12
|
> This ultra-wide-angle 10-18mm (16-29mm equivalent)
Ah yeah, looks like it
|
|
2024-11-09 08:32:31
|
That's good to know, thanks
|
|
2024-11-09 08:36:41
|
So my F4.5 is effectively an F7.2 as well in terms of incoming light
|
|
|
spider-mario
|
|
AccessViolation_
Ah, gotcha. But on Canon's RF-S lenses (specifically for APS-C, unlike their RF lenses) don't they compensate those reported specs? Like, an RF18mm lens on a full frame camera would produce the same image as an RF-S18mm lens on an APS-C camera?
|
|
2024-11-09 10:31:23
|
in the Micro Four Thirds system, Olympus sometimes reports equivalent focal lengths, but they do it _only_ for the focal length and not the aperture, which is arguably somewhat dishonest (it leads many to think that they have a 600mm f/4 equivalent)
|
|
2024-11-09 10:31:49
|
but the convention is to report the actual focal length and let people calculate 35mm-equivalent values if they need them
|
|
2024-11-09 10:33:14
|
in some way, the “F4.0” notation kind of plays into the confusion
|
|
2024-11-09 10:33:54
|
the “correct” notation is “f/4”, reflecting the fact that then the entrance pupil diameter is equal to the focal length (“f”) divided by 4
|
|
2024-11-09 10:34:44
|
knowing this makes it more obvious that if the focal length is doubled, but the entrance pupil stays the same size, then the new correct expression for its diameter is “f/8”
|
|
|
AccessViolation_
|
|
spider-mario
knowing this makes it more obvious that if the focal length is doubled, but the entrance pupil stays the same size, then the new correct expression for its diameter is “f/8”
|
|
2024-11-09 11:15:14
|
Hmm... the total light hitting the sensor is smaller because the sensor is smaller, but light per sensor area remains the same. So with the same 300mm f/4.0 lens, a full-frame picture which is manually cropped to be 600 mm equivalent should look just as bright as an image taken on an APS-C sensor with otherwise equivalent specs (like pixel size, light sensitivity etc), no? So together with the 600 mm equivalent focal length, shouldn't f/4.0 be more representative than f/8.0?
|
|
|
spider-mario
|
2024-11-09 11:21:29
|
sure, cropping is the same whether it’s done by using a smaller sensor or later in processing, but if, instead of cropping, you use a correspondingly (2× in the case of Micro Four Thirds -> FF) longer lens (i.e. “equivalent” rather than equal focal length) to still fill the larger sensor, then f/8 (and a correspondingly higher ISO setting) is what gives you similar results because then the entrance pupil (virtual image of the aperture stop as seen from the front of the lens, i.e. virtual hole through which light enters the lens) is the same size, so the same amount of light is captured from a given solid angle
|
|
2024-11-09 11:22:26
|
so 300mm f/4 on MFT is like cropping a 300mm f/4 on FF, _or_ like using a 600mm f/8 on a full FF sensor
|
|
2024-11-09 11:22:45
|
(or any linear interpolation thereof)
|
|
2024-11-09 11:23:34
|
the same amount of light enters from the relevant angle of view, it’s just spread onto different surface areas, hence the different focal plane exposures
|
|
2024-11-09 11:23:51
|
but the former is more relevant to the final results than the latter
|
|
2024-11-09 11:24:05
|
the latter is arguably more of an implementation detail
|
|
|
AccessViolation_
|
2024-11-09 11:37:56
|
So the 600mm f/8 on FF would appear darker than non-cropped 300mm f/4 on FF, right?
|
|
2024-11-09 11:41:01
|
Because the physical iris size is the same, you're just sampling a smaller angle for light, making the image darker, and that's reflected by the higher f-number, as that's focal length over iris size
|
|
2024-11-09 11:41:06
|
I think I get it
|
|
2024-11-10 12:14:26
|
Honestly I might go for the RF24mm F1.8 MACRO IS STM. That extra wide aperture might be worth it for the superior low light performance. Since the RF16mm is also not *that much* wider than the 18mm my current lens does, and a proper low light lens is what I really want. And the image stabilization is going to allow for even better handheld light shots, compared to the 16mm F2.8 with no stabilization (I don't have IBIS)
|
|
|
quixoticelixer
|
|
spider-mario
in the Micro Four Thirds system, Olympus sometimes reports equivalent focal lengths, but they do it _only_ for the focal length and not the aperture, which is arguably somewhat dishonest (it leads many to think that they have a 600mm f/4 equivalent)
|
|
2024-11-10 09:30:21
|
I think its better to show the actual aperture instead of equivalent since its only equivalent for depth of field and not light right
|
|
|
spider-mario
|
2024-11-10 09:39:36
|
it is equivalent for light (the same amount of light comes in from the relevant angle of view), just not light density on the sensor
|
|
2024-11-10 09:40:05
|
(and ISO is defined in terms of light density, so indeed, despite the equal amount of light, you would use different ISO settings)
|
|
2024-11-10 09:41:26
|
https://www.dpreview.com/articles/2666934640/what-is-equivalence-and-why-should-i-care/2
|
|
|
quixoticelixer
|
2024-11-10 09:53:49
|
yeah but its light density thats the imporant thing
|
|
|
spider-mario
|
2024-11-10 10:00:10
|
hardly
|
|
2024-11-10 10:00:42
|
why would it be?
|
|
|
quixoticelixer
|
2024-11-10 10:41:09
|
???
|
|
2024-11-10 10:41:14
|
why would it not be?
|
|
2024-11-10 10:41:36
|
if you shoot a photo with f5.6 at a 300mm equivalent FOV and 1/100 shutter
|
|
2024-11-10 10:41:42
|
i can get a very similiar photo
|
|
|
spider-mario
|
2024-11-10 10:53:47
|
if we shoot on two different formats, it will be more similar if you follow equivalence than if you target the same focal plane exposure, as described here: https://doi.org/10.1117/1.OE.57.11.110801
|
|
2024-11-10 10:55:30
|
> In Sec. 1.1, it was pointed out that the same camera exposure used on different formats leads to images with different levels of noise and diffraction softening, the advantage belonging to the larger format. By contrast, equivalent photos have the following properties:
> - total image noise of the same order of magnitude and
> - same level of diffraction softening
> As proven in Sec. 2, these properties arise from the fact that equivalent photos are produced by using the same lens entrance pupil diameter on each format instead of the same camera exposure.
|
|
|
quixoticelixer
|
2024-11-10 10:57:13
|
yes but thats not relevant for the context olympus is using
|
|
|
spider-mario
|
2024-11-10 10:58:32
|
it’s arguably as relevant as “you would be using 600mm to achieve similar results on FF” 🤷
|
|
2024-11-10 10:58:59
|
they pick and choose the parts of equivalence that make them look better
|
|
|
quixoticelixer
|
2024-11-10 11:01:58
|
I mean it's not them picking it, it sort of is convention
|
|
|
spider-mario
|
2024-11-10 11:02:59
|
a misleading convention, although indeed they’re not the only ones doing it – here is Apple: https://www.dpreview.com/files/p/articles/6780391159/Apple_California_Streaming_00065.jpeg
|
|
|
quixoticelixer
|
2024-11-10 11:05:45
|
yes everyone else does it
|
|
|
lonjil
|
2024-11-10 12:23:35
|
I don't understand the M43 market
|
|
2024-11-10 12:24:36
|
Most of the cameras are just as big and heavy as typical FF cameras, while not being particularly cheaper than low end FF cameras.
|
|
2024-11-10 12:28:55
|
But everyone I've stumbled on online who uses M43, uses it because of compactness. On DPReview, I only see a single compact M43 camera released in the last 5 years (Olympus PEN E-P7, which doesn't have a viewfinder). And it's not a model I've seen people mention as the one they use, those are all 2018 or earlier, like Lumix DC-GX9.
|
|
|
spider-mario
|
2024-11-10 06:07:28
|
yeah, a lot of M43 users lament the direction the system has taken
|
|
2024-11-10 06:09:57
|
I used Olympus 2019-2020 for the excellent IBIS, relatively fast readout for a non-stacked sensor, decent weather sealing and lens selection, but then moved to Canon FF in late 2020
|
|
2024-11-10 06:10:31
|
technically, I still _have_ the Olympus gear, as I’ve procrastinated reselling it
|
|
2024-11-10 06:10:37
|
but I haven’t used it in a while
|
|
2024-11-10 06:10:57
|
(I really should get around to doing that)
|
|
|
lonjil
|
2024-11-10 06:12:11
|
Since it'll be a while before I can afford a modern fancy camera, I've contemplated buying something like a Sony NEX-5 and putting a pancake lens on it 😄
|
|
|
spider-mario
I used Olympus 2019-2020 for the excellent IBIS, relatively fast readout for a non-stacked sensor, decent weather sealing and lens selection, but then moved to Canon FF in late 2020
|
|
2024-11-10 06:13:53
|
my dad has an Olympus. I took a look at it last week, and I was surprised by how not much smaller it is than my old DSLR.
|
|
|
lonjil
Since it'll be a while before I can afford a modern fancy camera, I've contemplated buying something like a Sony NEX-5 and putting a pancake lens on it 😄
|
|
2024-11-10 06:20:04
|
heh, maybe if I find one of the older compact M43 cameras used at a good price, I could get one of those and borrow my dad's lenses 🙂
|
|
|
quixoticelixer
|
|
lonjil
Most of the cameras are just as big and heavy as typical FF cameras, while not being particularly cheaper than low end FF cameras.
|
|
2024-11-11 07:28:44
|
idk the OM systems cameras are for sure smaller than my z6 II which isnt big
|
|
2024-11-11 07:28:51
|
bit also the lenses are much smaller as well
|
|
2024-11-11 07:29:00
|
and for wildlife when you need big zooms that makes a difference
|
|
2024-11-11 07:29:05
|
also for wildlife you are going ot be cropping a lot anway
|
|
|
jonnyawsom3
|
2024-11-13 10:10:32
|
Thought I'd post this here and see what results other people have been getting, since 12%, 20% and 60% are quite different numbers... https://www.reddit.com/r/jpegxl/comments/1gqd03r/comment/lwzeycr/
|
|
|
spider-mario
|
|
jonnyawsom3
|
2024-11-13 11:33:31
|
Nearly
|
|
|
spider-mario
|
2024-11-13 11:39:09
|
I came across other red benches along the river that really reminded me of it 😁
|
|
|
jonnyawsom3
|
2024-11-13 11:42:32
|
I should really do a photoshoot around London sometime. I go there every month, get home, then realise I have a picture of a pint glass and that's it xD
|
|
|
DZgas Ж
|
|
spider-mario
|
|
I should really do a photoshoot around London sometime. I go there every month, get home, then realise I have a picture of a pint glass and that's it xD
|
|
2024-11-14 10:20:22
|
nice parks there https://sami.photo/2022-10-Londres.html https://sami.photo/2023-05-Londres.html
(the second album is mainly the Zoo but also a bit of Richmond Park)
|
|
|
jonnyawsom3
|
2024-11-14 12:52:07
|
I've actually never been to the zoo, but have been to the park briefly. Was giving a Canadian friend a tour around but we'd already been walking for hours in 32c heat at that point. Did go to Mudchute Farm, nice bit of green surrounded by all the glass of Canary Wharf
|
|
|
a goat
|
|
lonjil
Most of the cameras are just as big and heavy as typical FF cameras, while not being particularly cheaper than low end FF cameras.
|
|
2024-11-15 02:45:07
|
It's not about camera size, it's about lens size imo. An Oly 40-150 f2.8 is significantly smaller than an 80-300 f4 equivalent full frame lens
|
|
2024-11-15 02:47:20
|
It's both the lens sizes and the feature set that the main MFT cameras provide, though admittedly other camera manufacturers have caught up on the video and IBIS front
|
|
2024-11-15 02:48:23
|
My G9 is ironically gigantic, but my 40-150 is too useful and small to find any equivalent
|
|
|
spider-mario
|
2024-11-15 02:58:21
|
strictly speaking, though, f/5.6 is enough to be equivalent
|
|
2024-11-15 02:58:27
|
and then the size advantage is not so clear https://www.dpreview.com/products/compare/side-by-side?products=olympus_m_40-150_2p8_pro&products=sony_fe_70-300_4p5-5p6_g_oss&sortDir=ascending
|
|
2024-11-15 02:59:52
|
the thing is mainly that in some cases, they don’t make an equivalent at all
|
|
2024-11-15 03:00:37
|
e.g. there is no 70-200mm f/5.6 full-frame lens, as an equivalent for the 35-100mm f/2.8 for M43 (to say nothing of the 35-100mm f/4-5.6)
|
|
2024-11-15 03:41:28
|
left to right: 70-200mm f/2.8, 70-200mm f/4, 70-200mm f/5.6 equivalent, 70-200mm f/8-11 equivalent, shedding some size and weight with each step (and, in this specific case, a clean FF / M43 divide in the middle)
https://www.dpreview.com/products/compare/side-by-side?products=canon_rf_70-200_2p8l_is_usm&products=canon_rf_70-200_4l_is_usm&products=panasonic_35-100_2p8_iii&products=panasonic_35-100_4-5p6_ois&sortDir=ascending
|
|
2024-11-15 03:42:42
|
|
|
2024-11-15 03:43:29
|
(or in M43-equivalent terms: 35-100mm f/1.4, 35-100mm f/2, 35-100mm f/2.8, 35-100mm f/4-5.6)
|
|
2024-11-16 02:20:05
|
decided to try and see whether this photo benefits from HDR
|
|
2024-11-16 02:20:12
|
I think it does
|
|
2024-11-16 02:24:29
|
(HLG image compressed using jpegli, although I forgot to make it P3 instead of Rec. 2020)
|
|
2024-11-16 02:33:11
|
not too fond of how the SDR fallback looks, though
|
|
|
jonnyawsom3
|
2024-11-16 02:34:00
|
Not terrible, a little washed out but tapping it on mobile thankfully works
|
|
|
spider-mario
|
2024-11-16 02:35:01
|
my previous, SDR-only edit of this photo was:
|
|
2024-11-16 02:35:30
|
maybe I could brighten up the deer a bit
|
|
|
RaveSteel
|
2024-11-16 03:14:22
|
Both look pretty nice
|
|
|
jonnyawsom3
|
|
Thought I'd post this here and see what results other people have been getting, since 12%, 20% and 60% are quite different numbers... https://www.reddit.com/r/jpegxl/comments/1gqd03r/comment/lwzeycr/
|
|
2024-11-16 05:03:42
|
Touching on this again... I could've sworn I was only getting around 20% savings at most for lossless DNG, but every file I've tried now is 50% or more
|
|
|
spider-mario
|
2024-11-16 05:04:27
|
are they compressed at all in the first place?
|
|
2024-11-16 05:05:11
|
I ran through some of my old DNGs to try out TinyDNG and found a few that went from about 25MB to 8MB or so
|
|
2024-11-16 05:05:25
|
I think those were from my Galaxy S8, probably using Open Camera
|
|
|
jonnyawsom3
|
2024-11-16 05:07:06
|
My phone takes uncompressed 24MB files, usually gets to about 8MB when using the old JPEG compression, but TinyDNG is hitting 4MB now
|
|
|
Touching on this again... I could've sworn I was only getting around 20% savings at most for lossless DNG, but every file I've tried now is 50% or more
|
|
2024-11-16 05:08:27
|
Those numbers were compared to old lossless compression
|
|
2024-11-16 05:15:47
|
Hmm... Guess I'll have to run the tests again, this is all I can find https://discord.com/channels/794206087879852103/803574970180829194/1186903859415760986
|
|
|
diskorduser
|
|
spider-mario
decided to try and see whether this photo benefits from HDR
|
|
2024-11-17 01:49:59
|
HDR photo looks nice. SDR boring.
|
|
|
jonnyawsom3
|
2024-11-17 03:10:13
|
Huh... I didn't expect that when opening it in Chrome
|
|
|
spider-mario
|
2024-11-17 09:25:51
|
do you have one HDR and one SDR monitor?
|
|
|
jonnyawsom3
|
2024-11-17 09:39:35
|
Nope, only a single SDR
|
|
|
spider-mario
|
2024-11-17 10:09:29
|
seems Chrome might be a bit confused about it and forgetting to tone map
|
|
2024-11-24 03:36:33
|
|
|
2024-11-24 03:39:41
|
(oops, forgot to make the greyscale one 4:1:0)
|
|
|
yoochan
|
2024-11-24 06:43:41
|
you have been spotted by the bird, take care
|
|
|
lonjil
|
2024-11-24 09:51:13
|
nice photos!
|
|
|
Meow
|
2024-12-09 03:41:47
|
A road
|
|
2024-12-09 03:42:06
|
Free to use https://commons.wikimedia.org/wiki/File:TW_CHW105_Dec_2024.jpg
|
|
|
DZgas Ж
|
2024-12-24 04:34:19
|
|
|
2024-12-26 10:51:34
|
|
|
2024-12-26 10:53:33
|
full of garbare
|
|
|
jonnyawsom3
|
|
DZgas Ж
|
|
2024-12-26 11:11:26
|
Thanks Discord
|
|