DV Info Net

DV Info Net (https://www.dvinfo.net/forum/)
-   Canon XL H Series HDV Camcorders (https://www.dvinfo.net/forum/canon-xl-h-series-hdv-camcorders/)
-   -   So Chris, how does 24f actually look? (https://www.dvinfo.net/forum/canon-xl-h-series-hdv-camcorders/51066-so-chris-how-does-24f-actually-look.html)

Thomas Smet September 15th, 2005 02:07 PM

Even "if" it was frame mode (which I doubt it is) that might still be better than 720p.

Somebody mentioned that frame mode on the XL1 had about 360 lines compared to 480 instead of only 240 from one field. Based on that ratio "if" the XLH! used frame mode we should get about 810 lines instead of only 540 from the Z1 and 720 from the HD100. The only other camera that might beat that is the HVX200 but we do not yet know how they will get 1080p. It may be interpolated from 720p chips so it may not be any better than 810 lines from frame movie mode.

Again this is a what if it is situation.

Heath McKnight September 15th, 2005 02:18 PM

I don't think it's like Frame Mode. Also, check this out:

http://www.dvinfo.net/conf/showthrea...hlight=28+days

heath

Charles Wood September 15th, 2005 11:52 PM

24f
 
A little confusion seems to be being introduced to this question of 24P. Lets set aside the naming of names point initially: The key issue is that if the data on the CCD is clocked at the same moment AT 24 FPS but then read out off the block as two interlaced fields, we really don't care about how it is read do we? The key issue is that the image capture is at one moment in time and at 24Hz

The important issue then becomes do they then recombine the two fileds to form a FRAME at 24 Hz BEFORE any image processing. They would be crazy not to, but maybe there are processing limitations on this (like no actual full frame store anywhere). What happens to get the data into the HDV transport stream seems irrelavant then, provided the field sequence is marked, and recoverable.

Then back to the naming of names: 24P implies the data can be read off the block progressively. 24F implies the data can be CAPTURED at 24Hz but is read as FIELDS. So there is a difference, and maybe it would affect noise patterns or something, but it probably is simply a technical difference, not one that affects the actual image we finally get to use.

Or is this too logical?

Someone say yes Charles...this is what we do....

Michael Wisniewski September 16th, 2005 12:28 AM

Thank you Mr. Spock, that is very logical.

Charles Papert September 16th, 2005 01:36 AM

Quote:

Originally Posted by Heath McKnight
I heard a rumor someone owned the trademark to 24p and was to receive money for that right. But I think that's been debunked.

http://www.filmlook.com/

Barry Green September 16th, 2005 06:33 AM

Quote:

Originally Posted by Charles Wood
The key issue is that the image capture is at one moment in time and at 24Hz

I'd say the key issue is how the final product looks, not how it does it. If it delivers full 1080p resolution, and the motion is sampled once every 24hz, and it looks like a high-def version of the DVX's 24p, then I don't think it matters how they do it or what they call it.

CineFrame24 is hated because it is neither full-resolution, nor 24hz motion. If 24F is full-res and 24hz motion, it will be embraced regardless of what they name it or how they accomplish it.

Heath McKnight September 16th, 2005 06:58 AM

Thanks, Charles! BTW, saw your HD100 footage at an HDV show with Ken Freed. Nice stuff.

heath

Obin Olson September 18th, 2005 12:24 PM

Under this light then they ARE indeed getting a WHOLE frame from each ccd at 1/24th of a sec? then the readout is interlaced? I don't care a rip about the "readout" if the CCD is getting a WHOLE frame every 1/24 of a sec....is this the deal with 24f??


Quote:

Originally Posted by Charles Wood
A little confusion seems to be being introduced to this question of 24P. Lets set aside the naming of names point initially: The key issue is that if the data on the CCD is clocked at the same moment AT 24 FPS but then read out off the block as two interlaced fields, we really don't care about how it is read do we? The key issue is that the image capture is at one moment in time and at 24Hz

The important issue then becomes do they then recombine the two fileds to form a FRAME at 24 Hz BEFORE any image processing. They would be crazy not to, but maybe there are processing limitations on this (like no actual full frame store anywhere). What happens to get the data into the HDV transport stream seems irrelavant then, provided the field sequence is marked, and recoverable.

Then back to the naming of names: 24P implies the data can be read off the block progressively. 24F implies the data can be CAPTURED at 24Hz but is read as FIELDS. So there is a difference, and maybe it would affect noise patterns or something, but it probably is simply a technical difference, not one that affects the actual image we finally get to use.

Or is this too logical?




Someone say yes Charles...this is what we do....


Charles Papert September 18th, 2005 12:39 PM

Doesn't happen often, but when it does; we've got two Charles in the same thread. Heath, thanks for the nod for the JVC footage. How were they showing it? on a monitor loop or as part of a presentation? just curious.

Charles Wood, welcome to DVInfo.net...and, mind if we call you Bruce?!


All times are GMT -6. The time now is 04:41 AM.

DV Info Net -- Real Names, Real People, Real Info!
1998-2025 The Digital Video Information Network