I wanted some way to inspect and modify the ADTG registers directly from menu, not via log files (so I could play with it in the train, for example) => I wrote a modified version of adtg_log: it's
adtg_gui. Now that's it seems to work pretty smoothly, I thought you may find it useful.
Warning: this is not a toy; it can destroy your sensor.What's different from adtg_log:
- it appears in Debug menu
- no log files, it's all in the menu
- all intercepted registers are displayed after Canon code touches them
=> [photo mode] first enable logging - simply open the ADTG registers menu - then take a picture, for example, then look in menu again
=> [LiveView] some registers are updated continuously, but there are a lot more that are updated when changing video modes or when going in and out of LiveView (so, to see everything, first open ADTG menu to enable logging, then go to LiveView, then look in menu again)
- for registers that we have some idea about what they do, it displays a short description
=> you can add help lines if you understand some more registers
- you can display diffs (e.g. enable logging, take a pic, select "show modified registers", change ISO, take another pic, then look in the menu)
- you can override any register
=> if you don't have dual ISO yet on your camera, just change CMOS[0] manually, then take pics
=> you can find some funky crop modes (e.g. if you change the line skipping factor)
=>
now it's easier than ever to kill your sensor for science- camera is autodetected (I've added the stubs from this thread and 1% repo for 5D3, 5D2, 60D, 500D, 550D, 50D, 6D, EOSM and tried on the first 3; 7D will not work by design).
- if in doubt,
take the battery out. Quickly! (well, that's what I do)
Tip: some registers use NRZI values (they are displayed with a N), others use normal values. If the value doesn't make sense (e.g. something affects brightness, but it seems kinda random, not gradual changes), try flipping the is_nrzi flag from known_regs. You can't do it from the menu yet.
