So to catch up, ML is “unified” now? In layman’s terms, what does that mean exactly (for us non-coders?)
“unified” as the word mean "Join together"
so the best parts of different development branches (including source code from the old core)
merged into the "unified" Source code which the nightly builds are based on .
Exception are things like "Crop_Rec" , "Dual_ISO Video" , etc. .... there are developer own branches
which is based on the "unified" source code with developer own modifications to the code .
Once the developer's code is stable & proven to work correctly they can
submitted there code to the Admin (aka a1ex) to be joined with the "unified" source code (which the nightly are base on)
This the goal of all developer/coder in the end .
Reddeercity, is 1872px not available because the “unified” code requires 32px increments? Thus forcing us at a max 3x3 binned resolution of 1856?
Short answer , Yes
Any way to get 1872px in the 5D2 nightly build?
I do believe that the mlv_lite module has the work around to get 1880 but at a cost .
There no audio support on d4/5d2 , you can't kill the overlays(global draw) where recording
which reduces the record time by at least 30+% .
mlv_lite is mainly mean for compressed raw ( which has has reduce data rate) which the 5d2 does not (Yet)
thou it still work fine
But sometime down the road I could possibly add support for 1880(3x3) in my
"Crop_Rec" branch for mlv_rec module that has audio support
That would be more then likely way down on my priority list .
