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

#104
Hopefully this thread will turn into a knowledge base of how us mere mortals can help the development team in ways other then providing code.

Quote from: dmilligan on December 11, 2013, 04:16:32 PM
Test, as in really test. As if you were QC working for a software company. Don't just use ML in normal situations and submit problems when things go wrong (and don't just do another ML RAW vs. H264 test, there are more than plenty of those out there). Try to break a feature. Think of as many possible scenarios as you can. Throw everything you can think of at a feature to break it. Try every value of every setting. Try it in extremely unusual scenes or lighting. Write down your results like a scientist doing an expirement. Then share your results, even if nothing went wrong. It's also helpful for devs to know when something actually works. Test for the sake of testing, with specific intention, not for the sake of making your 'budget short film'.

If you notice a problem, figure out how to repeat it and try to isolate it to a specific build (or if you can compile, isolate it to a specific changeset). Looking at the change log on bitbucket is very helpful in doing this (look for commits related to the feature and check those builds first). This requires no coding ability at all, and can save devs a lot of time, b/c they will know exactly where in the code the problem lies. Even I can figure out bugs that would normally be way above my skill level if you tell me exactly the changeset that is causing it, in fact most of the very few patches I've submitted, I've found like this.

This has been reiterated by a1ex time after time, I'm sure he's tired of saying it. It's clear that very few people actually end up reading the 'how to report bugs' links he posts.

A good example of the lack of this being done is the 600D 'overheating' issue. Countless people have reported this issue. Not one has done anything to help resolve it. Simple scientific-like experimentation can easily help resolve the exact source of the problem without any coding skill at all (e.g. monitor the temp of the camera overtime, both the display temp and with an actual thermometer, try different builds, use the stable build as a control group, etc.). The nightly builds are for testing, nobody actually seems to be doing this, or their idea of 'testing' is: 'use in a production enviroment and complain when something goes wrong'


http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

QuoteAnybody who has written software for public use will probably have received at least one bad bug report. Reports that say nothing ("It doesn't work!"); reports that make no sense; reports that don't give enough information; reports that give wrong information. Reports of problems that turn out to be user error; reports of problems that turn out to be the fault of somebody else's program; reports of problems that turn out to be network failures.

There's a reason why technical support is seen as a horrible job to be in, and that reason is bad bug reports. However, not all bug reports are unpleasant: I maintain free software, when I'm not earning my living, and sometimes I receive wonderfully clear, helpful, informative bug reports.

In this essay I'll try to state clearly what makes a good bug report. Ideally I would like everybody in the world to read this essay before reporting any bugs to anybody. Certainly I would like everybody who reports bugs to me to have read it..................



Answering a developers questions directly.

When a developer asks you to check if your problem happens when shooting at shutter speeds faster then 1/200th (for example), the developer doesn't care if your neighbours dog had 13 kittens and they photograph better at 1/10th!  Be specific with your answers that relate to the questions asked by the developer.  If you don't understand the request, ask questions.  Questions imply learning!  Discussing the current political climate on pluto or any other manner of irrelevant discussion, simply wastes a developers time and slows the bug finding process.  ie:  Your problem will remain.
#105
General Chat / New 1DX firmware adds a few ML features
October 23, 2013, 04:18:28 AM
Would love to see all of this filter down to the 5D3, but that's probably wishful thinking.  Just as well we have ML :)

http://www.canonrumors.com/2013/10/new-canon-eos-1d-x-eos-1d-c-firmware-coming/

Here are a couple of the updates that are already available with ML.

Expanded Minimum Shutter Speed in Auto ISO – In response to user feedback, this improved functionality in Auto ISO enables photographers to select a minimum shutter speed as high as 1/8000th of a second to freeze moving subjects.

Exposure Compensation in Auto ISO with Manual Mode Set – This new function enables photographers to manually set a desired shutter speed and aperture, use Auto ISO to control the exposure, and use Exposure Compensation to adjust the exposure for challenging lighting conditions (e.g., a very dark or very bright background). This new function can be activated through the Quick Control Dial or by using the Main Dial while pressing the SET button.

Same Exposure for New Aperture in Manual Mode – This new firmware feature provides users with the ability to maintain consistent exposure levels in Manual mode when the aperture changes, for example when a photographer shoots at maximum aperture with a variable-aperture lens (such as the Canon EF 70-300mm f/4-5.6L IS USM telephoto zoom) or when using a lens equipped with built-in extender (such as the EF 200-400mm f/4L IS USM Extender 1.4X). The feature gives users the option to have the camera adjust the shutter speed or the ISO to compensate for the aperture change.
#116
General Chat / Capture priority vs Exposure priority
September 15, 2013, 08:40:13 PM
Topic split from http://www.magiclantern.fm/forum/index.php?topic=8309.0



I honestly don't understand why you would need to check for overexposure well after a shot has been taken.

My brother in law and I were doing some shots of fireworks at the local show last night.
I was trying to explain to him that we would take some test exposures first to ensure that we had our focus and exposure nailed.  He had the mentality of just setting the camera up with basic adjustments for fear of missing a single firework.

After convincing him to check the first exposure, he soon realised that missing the first few fireworks was far more preferable then capturing all fireworks with borked settings.

And the same applies here.  Why are you not checking your exposure decisions on the first captures.  What's the point of being able to capture a scene quickly when important highlight detail is being pushed to white?
#119
General Development / Help compiling cr2hdr
September 09, 2013, 04:54:56 PM
Using the ML VM, I've downloaded mingw development environment and pretty sure I have the paths setup right.

Do I need to change anything in the makefile?

edit:  Got it.  Needed .exe added to CR2HDR_BIN=cr2hdr.exe
#120
Pretty easy job this one. 

For small changes to code anyway :P

From the main repo, create a fork.

https://bitbucket.org/hudson/magic-lantern/overview



Give it a name and fork it.


Voila, your own repository.


From there you can browse the source code and edit it.


When you've finished editing the source, it's time to commit it.


You should give it a name that suits the changes you have made.


Once the changes have been committed to your own repo, it's time to create a pull request for merge into the main repo.


Note:  You can edit more files at this stage before creating the pull request.

You can change the title, add a description, and then create the pull request.


Note:  You can edit more files (or the same file) at this stage and update the pull request.  Just hit the pull request button again and follow the procedure above.  A new pull request will not be created, the original pull request will be updated.

And it ends up in the main repo as a pull request :)


Where hopefully it gets merged into the main source tree.
#121
Forum and Website / New site layout
August 20, 2013, 07:28:32 AM
The new homepage looks beautiful.  Well done.
#122
Feature Requests / Dual-ISO only use with low base ISO
August 15, 2013, 08:03:17 AM
Can an option be added to only use dual-ISO with low base ISOs, say 100-200.
When ISO goes above limit, dual-ISO becomes disabled.
#123
NIGHTLY BUILDS FOR 5D3 are now available at
Nightly Builds - try the very latest stuff here
http://www.magiclantern.fm/forum/index.php?topic=3072.0

If you use Nightly Builds please delete all old files and replace with the new including ML directory.

Nightly builds for all supported cameras are also being maintained here : http://www.magiclantern.fm/forum/index.php?topic=3072.0

Some cameras are being developed separately from the main Unified build.  Some of those builds will have certain features available which may not be available through the nightly build.  You can explore the individual RAW development threads for additional builds; of course AT YOUR OWN RISK.


----------------------------------------



All general discussion regarding Raw recording.

The builds can be found in this thread

Please read through the many sticky posts here if you need information and help about installing these builds.
RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST

Current raw video capabilities - All ML cameras

PostProcessing -- Beginners Guide

(Auto) ETTR (Exposure to the Right): -- History & Beginners Guide
#124
Feature Requests / Shutter/ISO limits in expo lock
June 08, 2013, 09:53:37 PM
Never really noticed how useful expo lock was before.

First thing I thought was that I can ETTR, and then adjust DOF while maintaining exposure.  That's pretty cool.

Can you add minimum shutter and possibly maximum ISO limits please.  I'm not sure what's the best way to handle hitting both limits simultaneously.
#125
Raw Video / Automatic exposure Raw recording
June 05, 2013, 04:54:51 AM
Has anyone else been using AutoETTR in Raw recording.  I just tried it and it seemed to work pretty damn good.

It only seemed to hunt a little to much on large changes of exposure.
#126
The bootflag cannot currently be removed from the Canon 5D3.  You should consider this before using the custom firmware to enable the bootflag.



Many thanks to Charlie Loc (correct spelling?) for creating it.
#127
Feature Requests / [DONE] RAW zebras in liveview
June 02, 2013, 03:07:00 PM
As per title.  If not, is it possible to have JPG zebras off in liveview (they aren't accurate enough imo, and we have RAW histogram/spotmeter), with RAW zebras on after taking a picture?
#129
A general banter thread for discussing this wonderful feature.

Development discussion should be made in this thread

There are plenty of tutorials and how-to's in the Tutorials and Creative Uses section, including plenty of pinned threads.

Specific bug reports should be made in the Bug Reports section to make it easier to keep track of, and for other users performing searches.

Feature requests should be made in the Feature Requests section for the same reasons.

Also, you should consider posting your videos in the Share Your Videos section.

The old large discussion thread can be found here

If you're looking for compiled builds to try, have a look in the Newest compiled builds for RAW recording thread
#130
The last thread was getting quite large and was becoming more of a general banter thread.

Please keep this thread to development discussion only.

General discussion/banter should be in this thread

Video showing problems/issues with this feature are welcome in this thread.
Video showing how great this feature is, should be shared in the Share Your Videos section

There are plenty of tutorials and how-to's in the Tutorials and Creative Uses section, including plenty of pinned threads.

Specific bug reports should be made in the Bug Reports section to make it easier to keep track of, and for other users performing searches.

Feature requests should be made in the Feature Requests section for the same reasons.

If you're looking for compiled builds to try, have a look in the Newest compiled builds for RAW recording thread

All other RAW video based discussion should go in this section
#131
I'm not sure what factors determine what resolutions are available for RAW video, but can I request that if possible, they become mod 16 resolutions.

http://mewiki.project357.com/wiki/Computer_movie_files/Video/Mod16

http://doom10.org/index.php?topic=2160.0
#146
Share Your Photos / A full moon
May 26, 2013, 12:32:36 AM
Canon 5D3 - 1/80 - f/5.9 ISO 100
Saxon DOB 8 telescope with EOS adaptor.
Reduced 3 stops in post with a heap of clarity and contrast.

#147
Feature Requests / Sound recording location
May 19, 2013, 03:36:48 AM
Is it possible to choose which card to use for the sound recorder?  Save a little trickery in having to adjust it through the Canon menu.
Also can it be set to trigger on RAW record?
#148
General Help Q&A / ML overlays on image review 5D3
April 23, 2013, 02:27:10 AM
On the 550D, when reviewing images you can press the Q button to bring up the ML overlays.

Is this possible on 5D3?
#149
The devs seem keen to get a new stable release out that includes all current models.  They can't do that without knowing what's working, and more importantly, what doesn't.

This is a thread for you to list what camera you are using, what features are working, and which ones aren't.
Options that aren't listed haven't yet been confirmed by users to be working.

Please do not make feature requests in this thread.

Canon 5D Mark III

Audio
Working

Not Working


Expo
Working
All white balance options
ML digital ISO

Not Working


Overlay
Working
Zebras
Spotmeter
Histogram
Waveform
Vectorscope

Not Working

Movie
Working
All image finetuning options


Not Working
Load H264.ini  -  See the bottom of this page http://www.magiclantern.fm/forum/index.php?topic=4124.25

Shoot
Working
Advanced bracket
Mirror lockup

Not Working

Focus
Working
DotTune AFMA

Not Working

Display
Working
Advanced settings - Screenlayout, UpsideDown mode, UniWB correct

Not Working

Prefs
Working

Not Working

Scripts
Working
Tried a couple of scripts and they're working fine

Not Working

Debug
Working
Screenshot


Not Working


Didn't realize there were so many options until I had to start typing them out :)  I dare say the formatting of this post will change as more results are added.

Please feel free to list your camera and the options you have tried.
#150
General Chat / Official EOS firmware updates
January 30, 2013, 05:52:41 AM
I thought I would start a thread where we can all list, find and discuss firmware updates.

Canon 5D Mark III

http://www.usa.canon.com/cusa/about_canon/newsroom?pageKeyCode=pressreldetail&docId=0901e024806daf9c

QuoteCanon U.S.A., Inc., a leader in digital imaging solutions, today announced a new firmware update for the EOS 5D Mark III Digital SLR camera that significantly improves the camera's performance and usability. In response to requests from professionals working in the fields of cinema and television production, the firmware update enables the use of uncompressed HDMI Output support, making possible more efficient video editing and monitoring procedures. Additionally, the upgrade supports the advanced needs of photographers through improved AF performance when capturing still images...................The new firmware update will be available, at no charge, in April 2013 from the Canon U.S.A. website and can be downloaded by end users or through Canon Factory Service Centers.