Menu

Show posts

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.

Show posts Menu

Topics - Audionut

#51
Share Your Photos / A few from me
May 01, 2014, 08:01:13 PM
These are all using the ISO research tools, the top 2 using dual ISO, and of course, raw based exposure feedback.
The last one may be not suitable for work.









#52
Related discussion:  https://bitbucket.org/hudson/magic-lantern/commits/70f59636d89d1491aa66e17860f99bf6ebb7b4dc




Brief evaluative metering refresher.

http://media.digitalcameraworld.com/files/2012/06/Metering_mode_photography_cheat_sheet.jpg

Canon metering attempts to consider every photon in the scene, combine all of the values obtained, find the average, and meter that average for a midtone (13% in the case of Canon).  From this midtone point, there are defined points where saturation (over exposure) occurs, and the point where noise becomes greater then the signal.  Dynamic range.

Evaluative metering places some priority at the focus point.  So if we place the focus point over an area of the scene that is predominantly darker then the average, the Camera will attempt to meter this area closer to a midtone. And the same occurs when we place the focus point over an area of the scene that is predominantly brighter then the average.  This is useful if we decide we want to place priority on the shadows or the highlights.  In other words, let's place (some exposure) priority in these areas, so they don't get crushed to black, or over exposed.




Consider this scene.



The red dots indicate the focus points used to evaluate this scene (5D3).  Note:  The indicated focus points may not be 100% accurate, use your best judgement.
With aperture and ISO locked, the camera recommended these shutter settings for exposure.

Quote1/400
1/250
1/640
1/800
1/500
1/200
1/320

We can see a spread pattern of 2 EV for this scene.  Remember, the indicated exposure settings are for a midtone. 
In this case, the darkest exposure recommendation 1/800 (middle top focus point), still wasn't enough to capture the highlights without any saturation.  It was close, only slightly saturating the green channel in the brightest parts.  Note:  Most recent Canon cameras will saturate around 3.5 EV from the midtone.

Also, in this case, the brightest exposure recommendation was 1/200 (far right bottom focus point).  Here, the exposure feedback has exposed the shadow point, as a midtone.  So here, the point where SNR=1 is some 7 EV below this midtone exposure.

So, we have 1/800 with a saturation point around 3.5 EV above this, and 1/200 with a bottom limit around 7 EV below this point.  If we add all of this together, we have 3.5 EV (above the darkest midtone metering ), 7 EV (below the brightest midtone metering), and the 2 EV between the metered spread pattern, for a total of 12.5 EV of required dynamic range.

Recommended exposure settings.  1/800 with a 3 EV recovery ISO.  In this case, we still had some slight over exposure in the highlights.  However, on scenes where a focus point only covers the highlights, I would expect that we should see sufficient headroom.

Now, I don't pretend for a second that this will provide the user with 100% accurate exposure.  However, if I wanted 100% accurate exposure, I would use existing functions (AETTR, bracketing). 

Unfortunately, these existing solutions are somewhat slow.  Currently, the only way to sufficiently meter for large dynamic range scenes, fast, is to meter for the highlights, using the newly developed Auto dual ISO.  Or previously, metering for the highlights with some pre-set dual ISO setting. 

Both of these metering practices, require the user to be able to meter for the highlights.  By implementing exposure decisions based on automatic calculations of evaluative metering, from various focus points, we make another successful attempt at turning our expensive DSLR's into Point and Shoots   :P

All of this, in the vain hope, that ML can control the focus point.

Another option, would be to spot meter the highlights and the shadows.  However, I expect this to be rather difficult and complicated to code, and the speed slows somewhat, where you probably should just use AETTR.
#53
The black level fix has been merged with unified.  If you're still having issues make sure you're using an updated build.



Quote from: Original PostSince this is a kludge fix that requires extra post processing for all recorded video, you may want to help the developers fix it properly.





There are some issues in the raw backend, that may cause some issues with the black level in recorded video.
The black level is a function of the camera, and needs to be set correctly, otherwise issues such as pink casts on the footage may result.

On 5D3, 7D and others, the black level should be 2048.
On 5D2, the black level may be 1024, or around 1750.

If you notice issues with your footage from MLV, there are 2 options to fixing the footage.

With mlv_dump, you would use the --black-fix command option.

mlv_dump --black-fix=2048 -o out.mlv in.mlv

Here, you would adjust the value for --black-fix, suitable for your camera, until the footage looks correct.  From my quick testing, if you have the black level to low, there will be pink casts, and if you have the black level to high, there will be green casts.

If you have already outputted DNGs, then you can use exiftool to fix the issue.

exiftool -BlackLevel=2048 input.dng
Adjusting the -BlackLevel value.
You can substitute the input name for a wildcard (*), to batch process large amounts of DNG files.


User ultimatemale has created a tutorial with Mac.  Most of the things can be followed even if you're a Windows/Linux user.

Quote from: ultimatemale on June 06, 2014, 01:20:30 AM
This is a video tutorial to show you how i fixed the corrupt ML files that comes out looking black and green
Shot a music video on ML-RAW (not MLV)
Canon 5D3 1.2.3
ML build March 17th
Converted with RAWmagic lite
I use an apple Imac


#55
A new user guide has been started, updated with the changes from the latest nightly builds.
It is currently a work in progress.  Feel free to catch up on the latest features, and any help you can provide, would be greatly appreciated by all members.

User guide.
#56
A new user guide has been started, updated with the changes from the latest nightly builds.
It is currently a work in progress.  Feel free to catch up on the latest features, and any help you can provide, would be greatly appreciated by all members.

User guide.
#57
Main Builds / User Guide for latest Nightly Builds
April 24, 2014, 01:09:34 PM
A new user guide has been started, updated with the changes from the latest nightly builds.
It is currently a work in progress.  Feel free to catch up on the latest features, and any help you can provide, would be greatly appreciated by all members.

Camera Help.

Let's restore ML help together!
#60
http://www.space.com/25401-nasa-computer-codes-released-public.html

QuoteThe code catalog covers project management systems, design tools, data handling, image processing, life support functions, aeronautics, structural analysis and robotic and autonomous systems, NASA officials said.
#69
F.A.Q
The F.A.Q, is a list of frequently asked questions.  As such, if you are new to Magic Lantern and have a question, you should read this short document first.
http://www.magiclantern.fm/faq.html

Also check the next post in this thread.




Installation / Uninstallation
For questions relating to the installation, or the uninstallation of Magic Lantern version 2.3 on your camera, please see the Install Guide.


For the installation of nightly builds of Magic Lantern, the process has become extremely easy.

  • Ensure your camera is running the Canon firmware that is supported by Magic Lantern*
  • Download the nightly build for your camera
  • Format the card in camera
  • Extract the contents of the downloaded nightly zip
  • Copy the contents to the card
  • Run the firmware update from the Canon menu

For the uninstallation of Magic Lantern.

  • Run the firmware update
  • Follow the instructions




Modules

For installation and loading modules, see this post:  http://www.magiclantern.fm/forum/index.php?topic=12713.0




Features of Magic Lantern

A summary of the features available in Magic Lantern can be found here: http://www.magiclantern.fm/features.html

For a complete list of features available for all models of supported cameras, please see this feature list:  http://builds.magiclantern.fm/#/features




Using Magic Lantern


The userguide for Magic Lantern version 2.3 can be found here: http://wiki.magiclantern.fm/userguide

This userguide covers most features available in the nightly builds of Magic Lantern.  For features only available in the nightly builds, links for these features can be found in the feature list:  http://builds.magiclantern.fm/#/features

Let's restore ML help together!.  <-- Work in progress.
You can find links to tutorials in this post.

A list of Best Practices for Magic Lantern can be found here: http://www.magiclantern.fm/forum/index.php?topic=8286.0




How to ask smart questions, and provide useful bug reports

The quality of your questions, and the quality of your bug reports, are directly proportional to the speed at which your questions are answered, and your bug reports are fixed.

To gain an understanding on how best to ask your questions, you should reference this article: http://www.catb.org/~esr/faqs/smart-questions.html

And for bug reports, you should reference this article: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Reading and understanding both of those articles, will go a long way into increasing your experience here at Magic Lantern.




Searching the forums

The forum search function is available here: http://www.magiclantern.fm/forum/index.php?action=search

This is a general search function.  For an advanced search function that allows you to specify extra options in your search, see here: http://www.magiclantern.fm/forum/index.php?action=search;advanced;search=

How to use the forum search feature




Forum Rules

http://www.magiclantern.fm/forum/index.php?topic=934.0




About Magic Lantern

http://www.magiclantern.fm/about.html




Donating to Magic Lantern

http://www.magiclantern.fm/donate.html




Some threads you may find useful

HOW ML START (or why it doesn't boot topic) & Restore Camera Settings
Audio Recording - which settings to choose with external Mic ?
Formatted CF Card - Recovery options?


Ideas/Suggestions/Questions about this topic can be made in this thread: http://www.magiclantern.fm/forum/index.php?topic=9654.0


Thanks for reading, and enjoy.
#79
Being a dumb windows user, I like GUI's.  Turns out there is a frontend already installed in the pre-built VM.

Note:  Windows and Mac users, may be interested in the free GUI from Atlassian, the owners of bitbucket.

You will find it in the ubuntu menu under development.

TortoiseHG


There are a couple of things to setup beforehand that will increase the usability.
TortoiseHG needs a visualdiff tool which is used to compare 2 file revisions, and easily patch between them.  The first one I found was Meld.  This can be installed in the VM by using the Ubuntu Software Center, found in the Ubuntu menu.

So lets create a new repository in TortoiseHG and clone the ML repository.
Select the file menu and create new repository.



In the options panel that appears, select a location on the local drive to create the repository and click create.



This creates a blank repository on the local drive like so.


From here, it's best to set a couple of settings in TortoiseHG.  Select the file menu and settings.


This will allow us to perform some functions at a later date.  The text in the visual editor option.
emacs [+$LINENUM $FILE] [--eval '(highlight-regexp "$SEARCH")']

I use emacs for this tutorial.  And this can be installed via the ubuntu software manager also.  If you are more proficient with linux, you can use any editor you wish.

Now, we need to clone the ML repository to the local drive.



  • Select the synchronise panel
  • Change the location from local to https
  • Enter the web address for the ML repo
  • Hit the pull button

The ML source and all the changesets will now be on the local drive.  However, you need update the unified branch to HEAD, which will also push the files to your local repository.




  • Scroll through the commit log and find the first entry for the Unified branch
  • Right click on the commit and select Update...

Now you can browse the files in your local repository, and start building the source.  Right click on the repository and choose the option.

#80
Feature Requests / Delete folders in file_man
March 03, 2014, 06:23:45 AM
Unless I'm missing something simple, there does not appear to be a way to delete folders.

This would be a handy addition.
#82
General Chat / Onboard F1 video with 360 degree view
February 23, 2014, 06:28:42 PM
Board waiting for stuff to upload for a1ex.

http://www.mercedesamgf1.com/en/car/f1-w05-360-video/

edit:  Does video footage count as being related to Cameras!
#83
As per this announcement, all users are kindly asked to discuss all features and fixes from Tragic Lantern, in this thread.

Please state clearly, the camera model, and feature or fix.  It would be helpful, if you are aware of the specific commit, to note that here also.
The quality of the (your) bug report, is directly proportional to the speed of the resolution process.  Please reference this article:  http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Where it is possible, and within the limits of time constraints of the developers, these features and fixes will be backported to Magic Lantern.  It is hoped that an equilibrium can be found, whereby all features and fixes developed by 1% can be smoothly transitioned to Magic Lantern in the shortest time frame possible.

Please be aware that the developers are actively monitoring this thread, and if you receive no response to your enquiry, please do not immediately consider that your enquiry has been ignored.  Responding to forum posts is time away from coding  ;)

Thankyou.
#84
Feature Requests / Constrast detect microadjustment.
February 17, 2014, 08:06:58 PM
I have been speaking to Roger Clark (of Clarkvision) regarding permission to use his content in my upcoming article.

Roger proposed a request which I will forward here.

QuoteA big problem with phase detect
AF is 1) doing the calibration, and 2) the calibration changes
with temperature.  It should be possible to select an AF point,
focus on a target, raise the mirror, and for the same area on the sensor,
do a contrast detect AF and determine the difference and
add in the microadjustment calibration value.  More here:
http://www.clarkvision.com/articles/microadjustment/
Do you think this might be possible to do in Magic Lantern?
#85
a1ex has overhauled the screenshot function.

The pull request can be found here.

Advantages:

  • Does not rely on Canon's dispcheck (which suffers from memory errors, corrupted output, inconsistent paths, camera-specific quirks... all these are fixed)
  • Captures both BMP and YUV in a single screenshot (partial transparency support)
  • Handles ML palette tweaks
  • You can specify custom file names or patterns (e.g. "ML/TEST/myscr%02d.ppm")

Disadvantages:

  • Larger file sizes (1MB). Important?
  • PPM file format may not be very common in the Windows world. Important? I believe common image viewers (IrfanView?) can open them easily.
  • [SOLVED] you no longer get the full YUV buffer (you only get this data in transparent areas). Important?

API change: take_screenshot (now it also accepts a custom file name, which is optional). Any other modules calling this? From ML modules, only raw_rec and mlv_rec use this one, and only for debugging, so do we need to bump the API version because of this change? (I'd say no)

API addition: in the process I've added another API, get_numbered_file_name, to help with numbered sequences of files (here, VRAMnnnn.PPM) and refactored silent pictures with this one. Is this API sufficient to cover our use cases for these file sequences?

I make heavy use of screenshots in raw_diag (will update it after merging this one).

TODO:

  • [DONE] add PPM file support to pic_view (should be easy).
  • HDMI support (right now it will only save the central 720x480 crop). Important?
  • Better transparency support. Important? any examples where this code fails?
  • [DONE] full-res YUV screenshots (now it captures only 360x480). Important?
  • BT.601 support in rgb2yuv422 (without it, colors might be a little off on old cameras). Important?

Here is an idea of what the new screenshot function can capture.




Original post:
QuoteDoes anyone know who to make ML screenshots with transparent backgrounds?

For instance, you could have a screenshot of zebras overlayed on the resulting image.

edit:  I assume this is a post processing job.
#89
I'd like to ask all members to name their thread titles in the same manner as ML.

For instance, in ML the Canon EOS 5D Mark III is simply 5D3.  Currently if you want to search 5D3 specific, you need to check "5D mark 3", "5DIII", "5D3" and all other manner of options just to make sure you find every thread.

Modules should be labelled as they appear in ML, for instance, raw_rec, mlv_rec, mlv_play, dual_iso, etc.

Thanks.
#92
General Help Q&A / Links to Canon firmwares
January 15, 2014, 10:14:11 AM
Feel free to post links to Canon firmwares. 

http://pel.hu/down/
http://chdk.wikia.com/wiki/Official_Canon_firmware_updates  //probably outdated.

The above contains a bunch of links to pel.hu which hosts a bunch of firmware files, the eoscard utility and run by forum user Pelican.
#98
General Chat / Merry Christmas
December 24, 2013, 09:40:29 AM
Somewhere on the planet it must be getting close to midnight.

So Merry Christmas everyone, and I hope Santa brings you lots of camera bodies and lenses!
#99
Forum and Website / Forum ideas
December 24, 2013, 05:15:27 AM
As I'm sure most would agree, there is plenty of information to dissect regarding the usage of Magic Lantern.

I'd like to hear from users on any ideas/issues you have regarding the forum, it's layout etc, or any features that you think would help new users find the information they need.

I'd like to do something with the sticky threads.  Would it be best to leave the sticky threads as they are, or compile them into specific sticky threads to reduce the total number of sticky threads throughout the forum?

Thanks in advance.