|
|
Presumably you mean the part about denying two separate exposures. My apologies. I've edited my original post so no one gets the wrong idea if they stumble across it in search or something.
I looked at some past posts, and I think I must have been extrapolating from posts like these:
(I know, I know, you hate when people read into things! I'm really trying to quit!)
I dont think its our job to figure out how it works.. thats RED's
all we should care about is that it does work and how to make best use of it
I mean why do you care ? are you guys building cameras or are you creating images??
Jim I cant wait to purchase an Epic...!!
Whether the use of HDRx™™ is deliberate or not, and given that it is intended to be a tool in post, is there an argument why it wouldn't be enabled on every frame shot? In every situation?
I think we got crossed wires here or something. I was trying to apologize, and concede the point, but you seem to have taken it in some other way. Again, I'm sorry for any offense.
Funny enough, but the longer explanation you've since posted in a separate thread more or less exactly matches my prior understanding. "Motion-conjoined," as opposed to any gap in time between exposures, is what I was trying to describe. Apparently I didn't do a very good job.
But essentially we're frame interleaving here, right? There's no surplus bandwidth to write the frames at "the same time". And the X track exposure correction is a function of time between read-reset cycles. This would account for the unique motion blur that be achieved. Also the efficiency of making this part of a single R3D stream so the media can handle it. But in theory, the X track could be the "first" frame in the sequence giving the motion streak of the A track as a trailing, comet-tail effect, right?
| « Previous Thread | Next Thread » |