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.
Here's some footage I edited together from last weekend in Central Oregon:
https://vimeo.com/66866250
All but the last three shots are with the Magic Lantern firmware....it's a bit tedious in post but WORTH IT!
They have fixed the Mac GUI version of raw2dng, no more 2GB recording limit! That was very fast and very un-Canon!
That's because it's not Canon, it's the MagicLantern team
Exactly! A rag-tag band of part-time, just-for-fun programmers can fix their software in a couple of days...meanwhile Canon announces a firmware update and then takes over 6 months to actually roll it out...
Well, they have some advantages. If things break and your camera no longer works, they aren't legally liable. Granted if it happens to too many people they'll just stop using it. But Canon needs to make sure things are as bullet proof as possible, otherwise they face potential massive liabilities. Also, ML runs on top/alongside the Canon firmware, they don't have to do everything top to bottom like the firmware does.
That said...I definitely agree Canon should move faster with some of their firmware updates.
Theory!
Flipping the switch triggers metering. Since evaluative metering invokes code that looks at multiple metering points and tries to intelligently guess what to do, it's somewhat reasonable to assume that it might a different decision on what to do each time it's invoked if the light entering the lens in non-uniform across the image.
A way to test if this is happening is to point the camera so the image is completely uniform in brightness across the image — at the sky, or a flatly coloured wall, etc.
Please bear in mind that I don't own this lens or camera, but I do have experience in programming. In algorithms like this, it's often the case that there's some guesswork involved — hell, I once implemented an algorithm that would just randomly choose one of tho values if it couldn't determine one value over another with any degree of certainty, and it worked just fine.
Since I doubt the camera saves the reasoning behind its metering decisions between each metering, I can easily see this sort of thing happening in something that's supposed to be "smart" like evaluative metering. If you require absolutely consistent metering, I guess evaluative isn't the right mode to choose.
LetTheRightLensIn, cayenne, Drizzt321, thanks. Yes that has been what I have been thinking too. Unfortunately I "want" the f8 focus and the faster AF for flash so I don't want to downgrade to 1.1.3...
I guess I will sit on the sidelines for an alpha on 1.2.1 and look at the game being played and drool...
Has anyone used the latest ML release (alpha 3 or nightly build) with the 1.2.1 firmware? Also how do I get the nightly build? Do I need to build it?
Thanks in advance.
I don't have it up in front of me, but I've been following in the forums....
1. THey are currently only working on the older firmware, I think it was 1.1.3? The threads are like 50 deep, but in those they have links to get the older firmware so you can 'downgrade' to the version that works with current builds.
2. There are no 'guides' with everything you need to know about running the nightlies so you can play with the RAW video. YOu basically have to read through the long forum threads and take notes. ON some of those threads I saw links to outside sites where people have tried to put it all together into one guide, but if you're not familiar with a bit of coding, or more intricate computing methods, you might just want to wait till they have a more stable candidate.
That being said, the info is on a couple of ML forum threads.....I"m currently just watching the threads from the sidelines for now, but I may jump in at some point and try nightlies....
HTH,
cayenne
Yea, I'd recommend waiting until there's at least a pre-built alpha/beta that's officially released. A lot easier to install and use. Also it'll be a lot more stable and less experimental. But, if you do want to participate, please do so and help them out with any bug reports or suggestions!
Has anyone used the latest ML release (alpha 3 or nightly build) with the 1.2.1 firmware? Also how do I get the nightly build? Do I need to build it?
Thanks in advance.
You will need a new type of monitor to really use it the way it could possibly be made. Imagine no pixels, no 'resolution', just a standard size that everything is scaled to. It might be vector-based with infinite resolution if the picture is digitally made. Or if it captured with this type of Foveon sensor, it will have to use some math processing to figure out what color to put where.
whyThere is no perceptible difference between the two encodings that I can detect. Not on moving or still or simple or complex images. The only difference I can find is ALL-I wastes a lot of card space.
What you want to do for broadcast use is get an Atomos Ninja 2 and the new Canon 1.2.1 Clean HDMI firmware for the 5D3. The Ninja 2 will record the HDMI output direct to ProRes in either 1080i or 1080p formats, up to 60i or 30p frame rates. You will have the best quality that way and the files will come out of the Ninja ready to submit and be cut.
http://www.atomos.com
Key question (albeit probably deserving of a separate thread) - SmugMug or Zenfolio?
Magic Lantern RAW video for the Canon EOS 5D Mark III comes to the Mac & OSX
http://blog.planet5d.com/2013/05/magic-lantern-raw-video-for-the-canon-eos-5d-mark-iii-comes-to-the-mac-osx/?utm_source=feedburner&utm_medium=email&utm_campaign=Feed%3A+Planet5dBlog+%28Planet5D+Blog%29
This was very helpful. It looks like the RAW workflow is starting to take shape!
I want to preface my next question by saying that I'm a video n00b. Should I do most of my tonal/color adjustments in ACR, or should I wait until I have the footage in AE/Premiere and do most of it in Davinci Resolve, MB Looks, etc.? Does it matter where I do it? My instincts tell me that there are two competing issues:
1. Which program is better at a specific task (e.g., recovering blown out clouds).
2. Flexibility of not having to go upstream to make changes to footage and then re-import downstream. For example, if I do my tonal/color work in ACR, won't that mean I have to go back-and-forth, rather than being able to quickly make adjustments via plugin without the extra step of re-importing?
Again... I'm just a n00b here. :-)
ML RAW gives MUCH better quality, have to blind AND not trying to not instantly see the difference. The Ninja 2 1.2.1 external recording stuff is a minor little difference that most times you have to reallllly look to notice and well a basic static shot and you'd be hard pressed to see much difference but with ML the difference leaps out at you.
Of course the Ninja 2 does record gobs of footage at once and is tres easy to handle and you don't need to do slow pr-processing step for every little minute clip (OTOH that slow pre-process also is done with full power of ACR and even ACR and PS so you can get things so good that you don't even need to process anything in PP or use any slow tools there which does greatly speed up final compression time in PP so you gain some time back there, it's just it is a bit nicer to have the slow stage later rather than earlier, but whatever).
But most people have been kinda hmm eh I mean I guess a little about the HDMI+Ninja 2 and like OMG!!!!!!!!!!! about the ML RAW.
Once ML works with 1.2.1 the Ninja would make a nice zebra/focus peaking monitor though over HDMI since, at least for now, the ML RAW hack tends to crap out earlier at times if you try to force it's focus peaking and zebras and fancy stuff to run full force at the same time as the ML RAW is going.
If you do run 1.2.1 over HDMI I think the Atmos Ninja 2 type stuff is the way to go over the Black Magic for various reasons.
But man that ML RAW is just wow!
I wonder if they will find a way to feed the HDMI out with a less mangled signal. It would have to be 10bits at most and probably 8bits since I bet Canon didn't use HDMI 1.3 although who knows 1.3 is ubiquitous these days. It seems criminal that it took Canon six months to get the same crappy singnal out of HDMI and ML gives us this RAW stuff in three weeks. Perhaps the digic chip just utterly sucks at debayer and processing (in cam jpgs were never nearly as crips as RAW, but then again they do seem much better than the video stuff so....) and maybe that is why they say they do not use digic in C300 but use older video cam chips for processing?? (but still the in cam jpgs are better than the video they get out of it so....)
That said they did slightly tweak the video for 1.2.1 so whether hmdi or internal it does produce a bit better signal than it does with the older firmware. (which also reminds me DO NOT compare 1.2.1 HDMI Ninja 2 footage to pre-1.2.1 internally recorded footage since that footage is worse than the new internal footage quality).
I gotta think the Ninja and other external HDMI recorders out there, expecting the 5D3 market to open up to them are just hating life right now, with the new ML Raw stuff coming out...that is so far, exclusively CF based.
There goes a market for them unless the ML people can somehow put this stuff out of HDMI, which by the numbers, doesn't look hopeful.
C
