Roberto Lequeux
Well-known member
1 bit does not equal 1 stop. Your bit depth is a range of values available, which fall where they may given the DR of your sensor.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: this_feature_currently_requires_accessing_site_using_safari
Oh come on...
You haven't worked with an Alexa yet. Maybe it's overpriced. Maybe it's not. You can't know. And by the tone of your posts you've already made up your mind about how MX and Alexa compare.
1 bit does not equal 1 stop. Your bit depth is a range of values available, which fall where they may given the DR of your sensor.
The exchange rate might tip our decision once our Epic is ready, since we are in Europe. Plus, Arri offers service right around the corner, while I need to go through horrible customs protocols to have a RED sent back and forth…
Thank you Michael. Actually, thank you very much for your nice
and clear comments.
I am hoping that the Alexa is designed so that even if the current
firmware does bake in the WB, that later firmware builds will not.
Its' all about "100 years of history" and "a name you can trust" and so on. Nothing meaningful (except the Prores module) as an advantage over Red+MX, let alone Epic.
The more someone talks about their laurels, the more I feel (and I'm sure I'm not alone in this) that they plan to rest on them. Not good.
1 bit does not equal 1 stop. Your bit depth is a range of values available, which fall where they may given the DR of your sensor.
Since Michael Bravin is the Arri rep posting here, could you point me to the his posts that led you to write the above?
All he says is that they'll give more details at a later stage. Nothing wrong with that. It would be a bad thing to release the camera without giving details. But the camera is not released yet.
Before anything I'll judge a camera by the pictures it produces. Then the workflow and pricepoint. Have a little patience, and you'll be able to do a meaningful comparison.
Grading is another story - here the more recorded bit-depth you have, the more you can pull things around in post without getting banding.
No. Not at all. The tone of my posts expresses frustration at the quality of information coming out of Arri, which I find very poor. Its' all about "100 years of history" and "a name you can trust" and so on. Nothing meaningful (except the Prores module) as an advantage over Red+MX, let alone Epic.
The more someone talks about their laurels, the more I feel (and I'm sure I'm not alone in this) that they plan to rest on them. Not good.
Personally RED's philosophy on paper sounds better to me. It requires less storage.
Fair enough. I'm just trying to express my vote as to what would constitute a point in the right direction, or at least a direction that would have positive impact on my age group. To my credit, its' not like they've been trying to keep their cam under wraps, and they have been releasing lots of information, albeit not very useful information (in my opinion).
Hi Gavin. How are you? Are you still the "only one guy"?
I don't know if your above comment is true. Linear data is not the best candidate for compression. That is why JPEG-like stuff have inherently assumed a non-linear mapping to increase data correlation.
Joofa
Having WB completely changeable in post is clearly great, but, even as a dedicated Redite, I have to admit it's only necessary if you really get it wrong while shooting. If Alexa workflow requires a selected white balance that's baked, most shooters who know their light source and how the camera reacts are going to get it close enough to be happily fine tuned in post. And it sounds as if Arri has designed a suite of tools to make that work.
Me too. The more that is baked in, the more that can become a mistake, due to fatigue or stress on set, that cannot be fixed later, and the more time it must take before confidently pressing the record button.
This baking and un-baking deal makes no sense, especially when you consider the resolution of Alexa is the delivery resolution so there is no room to throw away rounding errors.