Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
Name |
Domain |
Purpose |
Expiry |
Type |
wpl_user_preference |
www.xdcam-user.com |
WP GDPR Cookie Consent Preferences |
1 year |
HTTP |
YSC |
youtube.com |
YouTube session cookie. |
54 years |
HTTP |
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
Name |
Domain |
Purpose |
Expiry |
Type |
VISITOR_INFO1_LIVE |
youtube.com |
YouTube cookie. |
6 months |
HTTP |
Analytics cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
Name |
Domain |
Purpose |
Expiry |
Type |
__utma |
xdcam-user.com |
Google Analytics long-term user and session tracking identifier. |
2 years |
HTTP |
__utmc |
xdcam-user.com |
Legacy Google Analytics short-term technical cookie used along with __utmb to determine new users sessions. |
54 years |
HTTP |
__utmz |
xdcam-user.com |
Google Analytics campaign and traffic source tracking cookie. |
6 months |
HTTP |
__utmt |
xdcam-user.com |
Google Analytics technical cookie used to throttle request rate. |
Session |
HTTP |
__utmb |
xdcam-user.com |
Google Analytics short-term functional cookie used to determine new users and sessions. |
Session |
HTTP |
Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
Name |
Domain |
Purpose |
Expiry |
Type |
__cf_bm |
onesignal.com |
Generic CloudFlare functional cookie. |
Session |
HTTP |
NID |
translate-pa.googleapis.com |
Google unique id for preferences. |
6 months |
HTTP |
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
Name |
Domain |
Purpose |
Expiry |
Type |
_ir |
api.pinterest.com |
--- |
Session |
--- |
Surely, Alister, on the resolution question, we also have to take into account that the anamorphic image will almost universally be viewed on a 16 :9 screen, so we don’t actually need so many pixels to compare in quality to a standard 17:9 or 16:9 image as the final picture is occupying less of the screen?
Please correct me if I’m wrong!
(Of course there is an irony that anamorphic systems, originally designed to give a bigger image in the cinema result in a smaller image on our screens today)
Resolution is both horizontal and vertical. The horizontal resolution is no different. But also a crop isn’t lower resolution, it’s just using fewer pixels, the resolution within those pixels still needs to match that of the full frame height. If you were producing a master for anamorphic projection it would be the full height of the frame anyway.
Perhaps I’ve expressed myself badly (or I’m completely wrong). I’m talking about the resulting 2.35:1 image on a 16×9 screen where the full height of the original frame is being magnified less than in a regular 16:9 image. The original pixels are being used for what is, effectively, a smaller image on the screen.
I’m thinking of the way the BluRays from TV shows shot on 35mm 4:3 look particularly good because the full height of the 35mm frame is used with no cropping.
But the horizontal resolution is not different. You shoot 4K wide and the image is shown 4K wide on a 4K screen, it is 1:1. And because of the way 2x anamorphic works you need to shoot 4K wide and 3K tall. When the image is squashed vertically it will increase the vertical resolution but this has no effect on the horizontal resolution, it remains the same. This is part of the anamorphic look, an image that has greater vertical resolution than horizontal.
And because a 4K bayer sensor cannot deliver a 4K image anyway, if we want something that really does have 4K of horizontal resolution we need to start at 6K.
With respect, I think you’ve missed my point, which is a very simple one:
To match the picture quality on a 4K screen at home, the 2.35:1 image needs, in principle, less pixels than a 16:9 image because, effectively, we are dealing with a smaller (less tall) final picture.
This is not the case, obviously, when we are talking about projection.
I think you are confused about what resolution is, it is not simply the number of pixels used, but the information contained within those pixels.
If you take a full screen 4K image on a 4K TV screen and crop the top and bottom and replace that with black bars the resolution does not change, the remaining image does not become any less sharp or any less detailed. The fine details and textures remains exactly the same because the resolution does not change. It is simply a less tall 4K resolution image.
If you shot an imaginary 2K test chart with alternate black and white pixels and then show that filling a 4K screen each pixel becomes 2 pixels across. The resolution remains 2K even though you are viewing at 4K. Now squeeze that image 2x vertically and what you would see on the screen would still be 2 black then 2 white pixels horizontally (we have changed nothing horizontally, it will still be 2K resolution). But vertically we will see alternating single black/white pixels because the vertical resolution is double because we have squashed the image 2x vertically. BUT horizontally we are still 2K and diagonals will be approx 3k.
So if we really want a 4K image we MUST start at 4K because the width of the image does not change.
Dear Alister –
Yes, I get all of that, but you still don’t quite get my point.
But that’s OK, I really don’t want to waste any more of your time, I’m sure you have much more important things to think about. Thank you.
Let’s leave it there.