Etiquette, expectations, entitlement...@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
Started by Audionut, July 15, 2014, 04:24:16 PM
0 Members and 1 Guest are viewing this topic.
Quote from: dmilligan on December 11, 2013, 04:16:32 PMTest, 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'.
QuoteCameras tested up to now1100D by dmilligan5D3 by RenatoPhoto, alex50D by ayshih60D by dmilligan600D by escho650D by Walter Schulz7D by Walter Schulz, RenatoPhoto
QuoteThese stubs are functions from Canon firmware, that can be called from ML code. To use them, one needs to know:- the function address in Canon code (that's the stub you need to find). The exact address is unique for each camera.- the function declaration (what parameters it accepts?) - declared in some header file, and usually common for all cameras.- what does it do (if it's not obvious from its name and usage context, a comment is welcome)
Page created in 0.114 seconds with 16 queries.