Thanks for the screen shots , but something when wrong I was looking for just the capture size reg's
You should see the same list of reg's I posted not just cmos reg's , that tells me either
didn't enabled the "
ENGIO Reg's" in the advanced tab of adtg_gui.mo or you didn't
refresh liveviewe.g.
load a h264 of review a photo , this a must or nothing will work and you will not get access to the hidden reg's .
There over 900 reg's you can see when it right but if not there only around 16 or 18 reg's visible
The other think that help's with development is the dump_image_buffer
This help to analyze the raw image for true raw size before cropping with exiftool
There was 3 reg's that I saw that where useful
c0f06088
c0f06008
c0f06014First let understand what going on here
let look at reg c0f06088 =>0x4520452
What does this tell us ?
Will for starter , this is the raw resolution and we read this in decimal , so let spilt the number up .
452=>1106 that the vertical res & the back half is horizontal 452=> 1106x2 =>2212 -160 (crop off boarders) =>2052
that should close to the Image dump .
Next Timer A =>c0f06008 & Timer B =>c0f06014
So timer A =>0x27b27b , we only use the last 3 (27b) ,
Let do some math , 27b hex = 635 decimal x4 => 2540
So this tell us that the max horizontal resolution that Timer"A" can do , including black boarder crop off area offset etc. ...
On the 5d2 raw image dump exiftool tell me the crop off area or offset e.g. 52 /160 (52=vertical & 160=horizontal) in crop_mode
Timer B =>c0f06014=>0x5e5 =1509 , max vertical resolution
So a Image dump in crop_mode would be very useful right now to see the offset , not sure if it's the same as 5d2
So if I was you , I would start with a small horizontal increase , from 1920 -- theoretically you shouldn't have to mess with timers
unless you exceed 2540 H , thou the very first thing I would do is slow timers A & B to get 23.976fps of very close to that (24).
This what I do on 5D2 , start @ 29.97fps -- reduce timer A by only a few units (0x2270227=>0x227027b) Increase timer B (0x4ff=>0x59f)=>23.976fps
then increase vertical to 1200 (my case) then increase horizontal in very small increments to 2400 H stopping between changes to check liveview .
The best way to approach this in my opinion , is to understand what each reg does in relation to raw size & preview size.
Also Liveview will messed up or freeze something pink , that canon liveview everything has to done with ML B/W (Gray) Preview.
A half shutter button press should give clean preview plus that how I refresh liveview between resolution changes .
Sorry for the long post and If this seem too simplistic , I'm writing this not only for you @aprofiti but for everyone else , so it can be understood by all
and get more people to develop .
I saw you modified also other regs (ADTG12[100c], c0f07XXX...) from the one you listed a couple of post above.
How did you find they were necessary?
That was found or discovered by a1ex from what I understand
ADTG12[100c] squeezes the image vertically , that's the 720p 50/60p mode on other cams ,
yes that right 5d2 can do 720p 50/60 all the way up to 72fps (that's where I stop don't push it any more but there was still room to go)
The how I got 1888x704 @ 48fps -- unsqueezed (1.66) I get 1888x1174 @48fps .
c0f0713c & c0f007150 open up the vertical window , it a must .
Explained here , I do belive I posted this before for you to read -- It's a1ex explaining every thing you what to know .
