1
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.
I know this is an old post and I was wondering if anyone figured out a way to do this? It looks like ML for some older cameras has a feature to allow for this, but I looked in the “Flash Tweaks” menu on my t5i and there is no option for thisCould be that that feat isn't enabled because not working, basically it's a workaround that change mode to not LV when taking the pic and then reverts back to LV. IIRC also on 6d it's not present.
Maybe I missed something ...
Thank you
Nice to see some progress, good finding for the fonts...![]()
![]()
![]()
![]()
![]()
Figured out how to use two patches from scrax to have a copy of his previous and post tracked what was the main problem.
Don't know why it showing only 2 menu tabs.
Assert related to mem.c was solved adding "_mem_init()" before malloc space for "bmp_vram_idle_ptr" and to make loads fonts is necessaries to "call_init_funcs(0)" before "_load_fonts()".
If I try to load all tasks, I get an error related to 5DC.sym I still need to figure out, probably related to module_task.
Unfortunately I'm still unable to make my previous patch to works, even with init.c and gui.c from scrax's work.
Here is the link to the patch (may have unnecessary changes because is a mix of an old patch found in the forum).
Any help is appreciated
a1ex, if I may..
I don't know you and you don't know me and I'm a nobody here or in general. But I feel you are going through something in you life possibly. Something that makes you doubt if this project is worth doing or maybe your time/effort is better applied somewhere else.. This is very normal and something I can relate to. Or maybe you are an artist at heart and nothing kills creativity and fun better than pressure and lack of respect and appreciation from others.
I know that behind that nick there's a living person, who feels and fights his own demons as we all do. I can't even imagine to what number of hours this number of messages below your nick translates to.. a lot. You have already done for us, for this project so much and you owe nothing to anyone. Do whatever you need to do to go through whatever you are going through and make it right for yourself. Maybe it even means stopping working on ML. We often forget that a person is more important than stuff..
No matter your decision, I will respect you the same. You have already done for me much more than I will ever do for you. Now take care of yourself and do the right thing that makes you feel better. I wish you all the best!
Now colors are gone so the debayer stuff seems washed away here when transcodeing to dng.
This is just a matter of adapting to other advancements in industry. For example, the issue you mentioned could be solved with better ASIC, using parallel programming, better/faster compression algorithms and better flash drives:
http://parallel.princeton.edu/openpiton/
http://fadu.io/
https://github.com/facebook/zstd
After downloading RAWs from the above mentioned linke, setting "all to 0", no sharpening, no denoising, white balance set on a gray card in the middle for each shot separately:
- sd Quattro H has an amazing sharpness and nearly no moire/aliasing artifacts. The text below the color checker is readable to the last line. Way better than D850 and 5DIV, despite much lower resolution of the final image (45 and 30 vs 25MPx).
- color checker looks virtually idenctical on D850 and 5DIV but sd Quattro H is very different. Blues, oranges, browns, violets are heavily affected. Despite I somehow "like it" (does it matter? or should the photo just match reality perfectly?), I don't know what is closer to real, as I can't compare it with the color checker itself.
- on sd Quattro H the blue channel is noisy already on well exposed parts (look at blues of the color checker!). I wonder how is it usable for landscape shots with a lot of blue sky...
- response curve is different; has to push shadows by +0,5EV to match exposure of D850 and 5DIV
- +1EV and the image from sd Quattro H already gets awful, large colored spots over the whole dark gray background. Mostly prominent close to image edges. Just with +1EV! For me, such a cam would be useless.
I can live with Bayer, for me it's a sweet spot. No wonder it's commonly adopted. No breath-holding what near future brings.
EDIT:
If someone argues about the choice of competitors: just checked the prices and ok, fine, comparing a 1,3k€ cam with a 3k€ might be unfair. Just take then 80D instead of 5DIV and D7500 instead of D850. The outcome stays same.
Just to be sure: You set ML to defaults before enabling autoexpo and haven't played around with Expo. Lock, ETTR ...?I've tryed it on my usual config so yes played a lot
Expo override is off and it doesn't work outside LV, too?
The changes aren't immediately visible in LV. Requires half-shutter to see the exposure changes in LV.
Things work more smoothly in LV with 'Same TV curve' set to ON. With Same TV curve set to OFF, I have to press half-shutter, release and press again fairly quickly, for the correct exposure settings to stick.
Your best bet for now would be Hasselblad... if you can afford it.
If noise is "ok only at 100 - 200 and 400" then the dynamic range is bad. Nikon, Sony and Pentax are also having so called ISO-less sensors, i.e. it doesn't matter if you dial in ISO 3200 or ISO 100 and push the file by +5EV in postprocess: the results will be the same.
If there is potential to recover highlights, then the photos are probably not ETTR-er. No surprise, as all DSLRs I know tend to underexposure.
Anything you can use tripod and is static (not moving) this can be a good camera. Would be nice to test together with HDRMerge...Yes Sigma bought Foveon and are the only one who can make it but both Sony and Canon are trying to find how to make it, and recently there is this that could be the evolution of the Foveon and maybe can be bought and developed by Canon
I think Foveon is a great technology and much better than Bayer. The noise issue could be solved if there was more people producing/researching it, but AFAIK, SIGMA patented the technology and now no one can use it, except them. Too bad.
You can simulate the Foveon, doing a technique called Drizzle. This software (supposedly) does that:
https://github.com/LucCoiffier/DSS/
Look at samples. The dynamic range (=> shadow noise) sucks. People like it due to its colors, not ISO performance.
There were another variations in the past from different manufacturers. Honeycomb instead of standard Bayer, additional fourth color and differently sized sensels to increase DR, to name just a few.
163: 8499.968 [MC] PROP_GUI_STATE 0
164: 8499.968 [PRP] ERROR TWICE ACK REQUEST L:846
165: 8499.968 [PRP] this->dwWaitAckID = 0x80020000(0x80040004)
166: 8499.968 [LV] [LVAE] EP_SetControlBv() >> EP_ControlBv:1
167: 8500.992 WARN [LVDS] First Get DTS_GetAllRandomData
168: 8501.248 [LV] [PATH] GetPathDriveInfo[0]
169: 8501.248 WARN [LVDS] First Get DTS_GetAllRandomData
170: 8501.760 WARN [LVDS] First Get DTS_GetAllRandomData
171: 8502.272 WARN [LVDS] First Get DTS_GetAllRandomData
172: 8502.272 WARN [LVDS] First Get DTS_GetAllRandomData
173: 8502.528 [MC] cam event guimode comp. 0
175: 8506.880 [GUI] ERROR ***** Lv GetMovieFrameRateIcon S (81)
176: 8507.136 [GUI] ERROR ***** Lv GetMovieZoomIcon S (88)
177: 8507.136 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
178: 8508.672 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
179: 8508.672 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
180: 8508.928 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
181: 8508.928 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
182: 8510.208 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
183: 8510.208 [DISP] UpdateReverseTFT(off) Current=1 Target=1
184: 8558.336 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
185: 8558.336 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
186: 8558.592 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
187: 8558.592 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
188: 8558.848 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
189: 8616.704 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
190: 8616.704 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
191: 8616.704 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
192: 8616.704 [GUI] ERROR ***** Lv IsMovieZoomSetting(88)
... this Lv IsMovieZoomSetting(88) continues till I get out of LV...