Messages

It works now. Hope it stays that way ;-)  Sorry for the hassle...

Tried that, but I didn't get a Create button.

Just to be clear: wiki means https://wiki.magiclantern.fm/ not the one on wikia. Correct?

Wiki login works with the same credentials as for the forum. However, apparently I don't have permissions to create a page, not even in the playground. And I didn't find any hint on who is admin or moderator of the wiki or otherwise responsible.

I like this proposal. I guess it would be the best possibility to have up to date help files once. I'd like to do some work to make this happen. Unfortunately I'm not familiar with the ML development ecosystem at all.

I read through the forum a bit and I think the text from the User Guide thread is the best we have currently. I wouldn't like to wait until they are up to date, since this probably won't happen. Could this be copied automatically to the source files or to an intermediate place like the structure proposed by kitchetof and already implemented in https://bitbucket.org/kichetof/magic-lantern/src/2208edf04a73b86a839fefd799329521cea9b6f0/help/en/?at=help_files ?

I understand the argument by jplxpto about the difficulty to have different language texts  in the source files. However, the english version could be considered as master with other languages held in indexed files, such that they are used if present. It would be relatively easy for users to provide such files.

My guess about what needs to be done:

• The developers should agree on a syntax and format, be it comments or conditional defines.
• Current text from the User Guide thread should be copied to either the source files or an intermediate place for peer review and update.
• A mechanism should be established to provide the help in-camera (if not the old bitmap format is used)

And all that, without increasing the workload for the developers too much.

Is this somehow correct or am I totally wrong? What would it be I can do immediately? I have some experience in wiki editing (I'm the maintainer and one of the main writers of wiki.panotools.org, I dabble in PHP, HTML, CSS and javascript, I can read C and python a bit).

The point is not how up-to-date anything is. The point is to have a structure that can easily be updated. At the moment we have quite a bit of information in the forums, so a user can find almost anything if he invests some time to search. There are two issues: There is no central point to start and there is no in-camera help. Of those two I consider the in-camera help the more important, since if you are out in the wild with no internet and need a particular function you get no information at all (actually I've printed part of the User Guide thread to have something with me in those cases, but that's tedious and I won't repeat it for new features).

As far as I investigated the User Guide thread is the best we currently have. It's a good starting point anyway and if there would be something that can easily be updated by the community and reviewed by the developers I have no fears the it will be an up-to-date manual soon. I like the idea to keep the sources for this manual together with the ML sources, which allows for a manual that fits any build version.

Well, my main concern is in camera help. We have the User Guide thread by Redrock which has very good content IMHO. I'd be happy to help copying over this content to the structure kichetof provided. I still have some questions, though: Is there a mechanism to transform the bitbucket structure into ML compatible .bmh files? The help system in ML seems to be working still. I copied the doc folder from a 2.3 stable to a recent installation and most of the pages show correctly. So I guess there is something which links the menu pages to .bmh files. How does that work and how is it maintained? 

If I understand correctly the current content in the bitbucket structure are the extracted help strings from .c files in /src/ and /modules/. It would be interesting to know whether it's possible to extract the content from the User Guide thread by Redrock in a similar way. In https://www.magiclantern.fm/forum/index.php?topic=11269.msg109944#msg109944 a1ex wrote he could do that if the formatting is consistent. Would this be a good point in time to do that?

So is the structure at bitbucket  ready to be filled or is this still a draft? Would be the next step to copy the content from the user guide thread to that structure or is the current content considered ok? I'd like to help if possible...

Hello,

Is anyone working on rebuilding the in-camera help files? I'd like to estimate whether it would be possible for me to help. What would it take to do something here?

Erik

Why isn't astro.mo in the /modules folder on https://bitbucket.org/hudson/magic-lantern/src ?

Babel more please! How is the creature done?

About two weeks ago greg wrote:

Someone compared FRSP vs LV raw crop frame?

If the hybrid AF is like a dual pixel, one photodiode is composed of two :
http://www.imaging-resource.com/ee_uploads/news/4486/hybrid-cmos-af-iii.jpg

There is a possibility that in the photo mode, data of halves focus pixel are averaged. What is the result, focus pixel works as normal pixel.

So maybe just change the ADTG/CMOS registry to get a image without focus pixels.

Has someone investigated in this direction?

I guess RAWtherapee inherits this behavior from dcraw, which does it intentionally.

Ok, I see. Should have found this idea myself. If I have a number of images I can use (f.e.) their average or median exposure and for each image add the difference. ML is so marvelous, one thinks it could solve all problems ;-) Sorry for the hassle...

Many thanks!

Many thanks! Do I  understand correctly these tools do exposure normalization in post? This would depend on more or less similar content, wouldn't it? I just want to shoot different images of a given scene, loose no highlights with best SNR (hence AETTR) and have uniform exposure for common details (just as a starting point for further editing).

Hello,

is there a way to use AETTR and record the deviation of a preset exposure in XMP?

If I f.e. set exposure to f/8, 1/100, 100ISO and AETTR changes exposure to f/8, 1/200, 100ISO for one image and f/8, 1/100, 100ISO for the next could ML then write a XMP that causes the images to look equally exposed in ACR / Lightroom, even if image content is totally different? I know the deflicker module can do it, if the image content doesn't change much (exposure normalization), but that's not the point.

Further tests show that apparently my understanding was wrong. Sorry for the hassle.

This leads to a question: Is there a way to use AETTR and record the deviation of a preset exposure in XMP? If I f.e. Set exposure to f/8, 1/100, 100ISO and AETTR changes exposure to f/8, 1/200, 100ISO could ML then write a XMP that causes the images to look equally exposed in ACR / Lightroom?

Could well be it works as intended and I have wrong expectations. My thought was that aettr shoots such, that little highlights are clipped and SNR is high. This works very well. My hope was, deflicker.mo writes XMP files, that adjust images in ACR such, that the brightness of same details matches. For a timelaps that would mean that bright lights that show for a short time don't cause the respective image to have different over-all brightness. Same if I f.e. change zoom or move the frame just a bit. I know very well that I simply can shoot with a fixed exposure, but this way I might clip the highlights.

After first tests I was disappointed that images shot as described above show very different over-all brightness, even further apart than without XMP exposure compensation. I tried to compensate the exposure manually and landed at (roughly) the inverse values. In fact the exposure was perfectly normalized when I simply changed the sign. Hopefully I find some time tomorrow to do some further tests, especially in comparison to UFRaw...

I created issue #2402 on bitbucket. I'd like to know whether this can be confirmed or refuted by anyone. It seems unlikely that I'm the first to discover it since I originally found it with a nightly from May 2015.

Hello,

I tried aettr with deflicker module for exposure normalization. aettr works a treat! But if I use the XMP with Adobe Camera Raw the exposure correction value has the wrong sign. If I understood correctly the XMP data should cause all images shot with the same ettr settings to be of visually equal brightness. However, they came out very different. But if I change the sign of the correction, they look the same.

F.e. for one image ACR showed +0.04 EV and +1.31 EV for the other. The second image was much brighter than the first. When I change the values to -0.04 and -1.31 both images appear to have the same brightness.

Do I use the XMP files the wrong way (loading the corresponding CR2 files into ACR loads the XMP files automatically) or is this a bug?

magiclantern-Nightly.2015Nov07.5D2212, photoshop CS6 with ACR 9.1

best regards
Erik

The 5D2 doesn't record 60fps either. The 5D3 and the 6D does: http://www.magiclantern.fm/forum/index.php?topic=6215.0

On https://builds.magiclantern.fm/#/ after choosing the correct camera click on "Show Older Builds" and choose the next one.

I wouldn't ask if I'd be able to fix it myself :-)  Unfortunately my coding skills are near zero. But I found this a very useful feature and I'd be grateful if I knew someone worked on it...

I've read that sound recorder was disabled for safety reasons: https://bitbucket.org/hudson/magic-lantern/commits/4ba0f1c0909dcdf505765e6d326e09ebd229064f
Is there a chance it will be back soon?

Would be very nice!
Erik

Two examples with crops in extreme dual iso, 100-6400.

Very impressive! Could you provide the 100-6400 iso dng for download. I'd like to try for myself. I need to decide whether I buy a 5D3...