1
General Help Q&A / Re: Microadjustment Canon eos 550d
« on: March 24, 2022, 10:39:08 PM »
Spt.info, but that will cost you more than the camera is worth
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
function test()
camera.iso.value = 100
camera.shoot()
camera.iso.value = 200
camera.shoot()
camera.iso.value = 400
camera.shoot()
camera.iso.value = 800
camera.shoot()
camera.iso.value = 1600
camera.shoot()
camera.iso.value = 3200
camera.shoot()
camera.iso.value = 6400
camera.shoot()
camera.iso.value = 12800
camera.shoot()
camera.iso.value = 25600
camera.shoot()
camera.iso.value = 51200
camera.shoot()
camera.iso.value = 124000
camera.shoot()
end
keymenu = menu.new
{
name = "ISO photo bracket",
select = function(this) task.create(test) end,
}
Nothing we can do from here.As you can see, people have figured out before how it works with other serial numbers from Canon.
Only thing I can imagine is trying to contact stolencamerafinder admin and asking him to address this issue in some way. Maybe asking Canon users to look for len's funny number via EXIF and not trying to use a number unable to track.
Sorry! No correlation found.The problem may be when a lens gets stolen and the only lens serial number is the one in Exif.
Do you have any problem affected by this? Repo, legal, incurance claim, ... ?
Hi, In the middle or was in the middle of moving back to the UK but with the problems we are facing that has been put on hold, I normally use the Lightroom plugin to convert my dual iso files but that computer has been packed away but I have a small lap top running Windows 10 so where please can I download the stand alone version of the converting software for a Windows 10 computer. Thankyou.I have been using Barracuda GUI for Windows https://www.magiclantern.fm/forum/index.php?topic=9102.0
I had some success with the .cr2 file. After dropping it into Adobe DNG converter, I've recieved a 16bit uncompressed .dng file.Almost gone when using VNG4 in RawTherapee.
After many tries, I've managed to open the data. Stangely the inner data width is 5360 opposed with 5202 that is reported by RawTherapee. The additional data is not black, but very dark rectangle on the left. RawTherapee somehow just crops it. Height is 3465.
I've overwritten the values with vertical neighbour averages, and stuffed the data back into the dng. Black lines are gone, but there are visible artefacts, like above the eye.
https://drive.google.com/file/d/1Wf6caNNeuPfo5uhd0Aak-s_PRiPGsAs5/view?usp=sharing
I tried Switch for the 1st time without problem on a ubuntu studio 18.10. It installed Yad , as planned. With a serie of pictures, dualiso, from the same Eos5DmkII, it doesn't work at all. I look at the log file & there, i don't understand the problem... The Switch files are in my Home directory. I followed the instructions. Can you help me?Got the same yesterday. Worked last time I tried. Ubuntu 18.04.
The log file:
DR analysis based on a lossy compressed CR3 file is not a good idea - https://www.canonrumors.com/initial-testing-shows-canons-new-32-5mp-aps-c-sensor-improves-dynamic-range-over-predecessor/I got the same results when I with Hraw checked normal raw files from 90D.
Hardware issue - one of the 8 readout channels is no longer working.Do you have more details how Canon's own bad pixel correction works? The only thing I know is the "lens cover on, manual sensor cleaning etc thingy", but nothing that explains how it works and why it doesn't always work.
What we can do, at software level, is to interpolate these dead columns as bad pixels (easiest to do in post-processing, but also doable in the camera, to some extent). Unsure whether Canon's own bad pixel correction feature would work here (didn't try).
In any case, this workaround will introduce some aliasing (somewhat similar to Dual ISO), but at least you will be able to keep using the camera for a while. Whether that's going to be a matter of days, months, or years until it fails completely, I have no idea.
This info was published before those firmware were even mentioned elsewhere, so I assumed it was an error.CVE-2019-6001 published 6 August, firmware 1.3.0 published 7 August. 1.3.0 was already ready.
But yes, that makes sense.
R firmware 1.3: https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos-r.html?type=firmwareNot fixed. https://www.magiclantern.fm/forum/index.php?topic=24385.msg219582#msg219582
RP firmware 1.2: https://www.canon.co.uk/support/consumer_products/products/cameras/digital_slr/eos-rp.html?type=firmware
No mentions about fixes for recent vulnerabilities.
I doubt this is a concern, the vulnerabilities found aren't related to the firmware encryption. I also wonder if it's even possible for Canon to update the AES key with a firmware update.They are vulnerable according to CVE. 7D together with WFT-E5 isn't on the other hand mentioned.
"Even though our camera model doesn’t support Bluetooth, some Bluetooth-related commands were apparently left behind, and are still accessible to attackers. In this case, we found a classic Stack-Based Buffer Overflow" - maybe those cameras don't have the Bluetooth code in their firmware, or different versions of it that aren't vulnerable?
Ok, I see why nobody did it then... Thanks!https://www.spt.info/sptstore.php/canon-eos-700d_t5i_kiss-x7i/software-canon-eos-700d-advanced
As I understand, Canon does perform focus calibration on this bodies in some way, if you send the lens and the body to them, does someone here know how they do it, if it's possible to do it without shipping all the kit to them?
Is there a reason why my camera createssRGB and AdobeRGB.
_MG_2846.JPG
and
IMG_2767.JPG
EOS R (before/after)Is that EOS R with the latest firmware 1.2.0? I saw samples of before/after with big difference. But yes, your script is impressive.
I don't know if I should publish this script, maybe I should sell it to Canon?
Banding correction 200D (M50 also has this problem) before/after :Any tutorial how to remove that kind of banding? Or just dark frame substraction?
dpreview
The EOS R too, just compared it.Didn't the latest firmware for EOS R solve that?