Differences

This shows you the differences between two versions of the page.

--- glossary [2021/03/20 01:39] – [CHDK] Walter Schulz
+++ glossary [2024/12/19 19:59] (current) – [Aperture flicker] names_are_hard
@@ Line 6: / Line 6: @@
 Feel free to add your input!
-> To do: All around binning, skipping, crop, aliasing
+> FIXME All around binning, skipping, crop, aliasing, FPN
-> + firmware stuff
+> FIXME [[#Build]] and other build varieties.
-> + Adding links
+> FIXME [[#Bricking]] and related stuff
 Preferred link formats:
@@ Line 67: / Line 67: @@
 -> [[#Pixel Binning]]\\
 -> [[https://a1ex.magiclantern.fm/bleeding-edge/lv-binning/binning-modes.html|Simulation: 1x3 "column binning" vs 3x1 "line skipping" vs 3x3 binning/skipping]]\\
+==== Aperture flicker ====
+Unwanted effect in time-lapse recordings caused by small variations in aperture actuation from selected aperture number. \\
+Every time a pic is taken, aperture blades will move from "open" to selected aperture and back. Consumer lenses with electronically controlled aperture blades are generally not able to repeat aperture actuation with infinite precision. Thus small but noticeable variations in exposure may result in displeasing flicker.
+Workarounds to avoid aperture flicker:\\
+- Use manual lenses\\
+- Use electronic lenses wide open only. (No aperture blades moving -> no aperture variation)\\
+- Use electronic lenses but twist lens in mount while DOF preview is activated. Aperture blades will be locked in position -> no aperture variation. Take care to avoid lens getting completely unlocked and falling off the camera.
 ==== ARM (architecture) ====
 [[#Developer|Dev]] lingo.
@@ Line 131: / Line 141: @@
 There are some major diffences how PowerShot and EOS have to be programmed and that is why there are 2 different project teams.\\
-It may confuse some people that there are a few EOS M cameras not handled by ML but CHDK. And there are 4 PowerShot cameras not located in CHDK realm but ML. Those cameras run code contrary to their names!\\
+It may confuse some people that there are a few EOS M cameras not handled by ML but CHDK. And there are 6 PowerShot cameras not located in CHDK realm but ML. Those cameras run code contrary to their names!\\
 EOS M3, M5, M6, M10, M100 work with PowerShot firmware and are therefore handled by CHDK.\\
-PowerShot SX70, SX740, G5 X Mark II, G7 X Mark III work with EOS firmware and can be ported to ML.
+PowerShot SX70, SX740, G5 X Mark II, G7 X Mark III, V10, Zoom work with EOS firmware and can be ported to ML.
 Link to [[https://chdk.fandom.com/wiki/CHDK|CHDK project home page]]
+==== Clean HDMI ====
+In ML context "Clean HDMI" means: No visible overlays. No blinking red recording dot, no focus box.\\
+In does **not** guarantee you get: No black borders left and right, content in 16:9, seamless streaming for longer than 29:59, flawless AF, ...
+ML can enforce clean HDMI in all AF modes: Display tab/screen -> [[this>camera_help#clear_overlays|Clear overlays]]
 ==== Collaboration (software development) ====
 Despite popular Hollywood movie [[wp>Trope_(cinema)|trope]], a "normal" programmer doesn't work alone and saves the world by rewriting some green hieroglyphs in a live system twice a day.
@@ Line 229: / Line 246: @@
 ==== Dual-ISO ====
-Dual-ISO uses an alternating [[#line scanning]] technique to increase [[#dynamic range]]. Each alternating dual line is scanned at different [[#ISO|ISO's]] and later combined to produce an image (or video) with an increase in dynamic range similar to taking two images at the different ISO's.
+Dual-ISO uses an alternating [[#line scanning]] technique to increase [[#dynamic range]]. Each alternating dual line is scanned at different [[#ISO|ISO]] values and later combined to produce an image (or video) with an increase in dynamic range similar to taking two images at the different ISO values.
 As a single imaging technique there are no motion artifacts, however a loss of resolution in the highlights and shadows, and [[#aliasing]] are the drawbacks.
@@ Line 279: / Line 296: @@
 -> [[ml>forum/index.php?topic=18024.0|ML Forum: Auto ETTR - What all those settings mean and how to use them]]
+==== Event Procedure ====
+A function in the Canon firmware that can be called by string value. They can be executed with [[#canon_basic_scripting|Canon Basic scripts]], through [[#usb|PTP]], or through the //call// function in C. Internally, these are known as //evprocs//.
 ==== Experimental Builds ====
@@ Line 317: / Line 337: @@
 **5D Mark III**: Firmware version **1.3.x up to 1.3.5** can be downgraded by using EOS Utility. It is not possible to use firmware update menu in cam without tweaking. See [[ML>forum/index.php?topic=18941.0|How to do a Canon firmware downgrade]].\\
 Firmware version **1.3.6** can only be downgraded by a tricky procedure found by user Apollo7 and fine-tuned by a1ex: -> [[https://builds.magiclantern.fm/5D3-123.html#install|Install procedure for 5D3 1.2.3]] -> Method B\\
-"Method B" is valid for every EOS camera denying firmware downgrades!
+"Method B" is valid for any EOS camera denying firmware downgrades!
@@ Line 599: / Line 619: @@
 ==== Noise ====
+-> [[#Pattern Noise]]\\
-[[#Pattern Noise]]
+-> [[#Read Noise]]\\
+-> [[#Shot Noise]]
-[[#Read Noise]]
-[[#Shot Noise]]
 ===== O =====
@@ Line 614: / Line 631: @@
 A combination of [[#exposure]] and [[#ISO]] that results in parts of the image appearing white (reaching saturation).
-[[wp>Exposure_(photography)#Overexposure_and_underexposure|Overexposure]]
+-> [[wp>Exposure_(photography)#Overexposure_and_underexposure|Overexposure]]
 ===== P =====
@@ Line 847: / Line 864: @@
 Physically accessing UART in older cams required opening cam and maybe even soldering wires to camera's cirtuit board. Later cams have a UART connector on board for easier access. \\
 On some of Canon's Digic 7, 8 and X cameras this UART is accessible without opening the camera by just removing a reusable rubber cover.
+==== USB ====
+Generally used for debugging. Information is transmitted over the Picture Transfer Protocol. Canon
+has added several commands alongside the standard ones, such as the one that can be used to write the [[#bootflag]] (See https://github.com/petabyt/mlinstall)
 ==== Underexposure ====