Andrew Reid

Finally!! Let's hope the AF is as good as the Fringer EF adapter is.

What's your YouTube channel? Can we have a look?

I seem to remember the amount of data coming off the sensor per second is similar in 8K/30p and 5.5K 60p. However, the individual frame scan time in milliseconds for 8K resolution is not necessarily going to be the same as for a 5.5K frame. So the rolling shutter might be even worse on the R5 in 8K. We'll have to wait and see. We can work out the worst case scenario. All frames have to come off in 999ms or under (under 1 second per frame). Divide by 30 = 33.3ms So it can't be any worse than 33.3ms in 30p. 24p can't be any worse than 41ms (shudder). So I would expect 32ms on the EOS R5 for sure in 8K. Probably less in 4K as it will pixel bin / line skip.

Indeed it's very bad compared to Fuji X-T4 120fps.... And Sony A7R IV, and A99 II, and Sigma Fp, and Leica SL, and the SL2, and Fuji X-T3, Samsung NX1, and about 5 more that I have not remembered in the 5 seconds that took No bias, only facts. When you pay this much you expect better 120fps 1080p quality. They are identically poor. See the Slashcam test. It's not the scaling down, otherwise 5.5K 60p would have AF. It's not the processing power otherwise 4K 60p crop would not have AF. It must be something else, most likely a power consumption limitation. It would be nice to be able to ask them. There is no reason I can see, for Canon not to use the 16ms frame readout time for 24p. It strikes me as extremely odd crippling again.

I am not asking you to refrain from praising the Pocket cameras! Just asking you to edit yourself a bit for the benefit of our topics and threads. And less YouTube clips as well It really is not a personal thing. I am trying to moderate the best I can and this is a major issue.

Yes it would have to be a second hand one as the SL is out of production since mid-2019 now, so I would have thought a new CL for 4K Super 35mm LOG 24p would be idea! It's a lovely form factor for it as well. A bit like a Sony A6400 that actually looks and handles like a camera rather than a Playstation2 controller

From Slashcam's test: [Google translation] At first we thought that this paragraph could be ticked off with three sentences, but surprisingly you have to take a closer look at the Canon EOS-1D X Mark III. First we were amazed by the result of 16ms for the complete 5.5K sensor readout. This is very good value for a 35mm full frame camera. However, this value is also necessary in order to be able to read the sensor fully 60 times per second. (16ms x 60 = 960ms). Unfortunately, this value is not fixed, but is only so low as long as the sensor works in 4K or 5.5K at 50 or 60 fps. If, on the other hand, you put the camera in a mode with 24, 25 or 30 fps, the sensor allows itself a very moderate 32 ms for a complete readout. This is incomprehensible, especially since many interesting video functions of the Canon EOS-1D X Mark III only work with 24-30fps (including the dual-pixel autofocus). A thermal reason for this seems unlikely, since the sensor does not miss any rows or columns at 60 fps and generates exactly the same debayering as with 24-30fps. In the 4K crop 1: 1 sensor readout, on the other hand, the camera has a 15ms readout across all frame rates and in this mode it can also use the auto focus at 50 fps. It is therefore also unlikely that the processing behind the sensor readout requires a slower 4K readout. It is also interesting in this context that a similar behavior can be seen in FullHD: The full sensor readout is 11 ms between 24 and 60 fps. However, if the camera has to deliver 100fps or more, the sensor can suddenly be read out with 7 ms without any visible change in the image detail or debayering quality. *** So yes, 15ms is better for 4K/24p in the 1.33x crop mode. But again, this is not why you spend the extra for a full frame camera. And why is the 1D X III processor fast enough to enable dual pixel AF at 4K/60p in 1.33x crop mode, but not in 4K/60p from the full 5.5K sensor readout?

It's why we buy a full frame camera in the first place, to shoot in 1.33x crop!

When I began shooting with my own Leica SL2 earlier this year, I found a lot to like about the high-spec mirrorless camera for filmmaking - and it is superb for photography. However, the battery power management has prevented shooting in 4K and 5K reliably, varying depending on the type of lenses used. After making Leica aware of this issue, Leica's Head of Product Management, Professional Photo System and co-designer of the SL2 Stephan Schulz has been on my case and I have been on his! The good news is that Leica are investigating the possibility of a firmware update to alleviate the problem and I will be carrying out testing duties for Leica on the video side going forward. The Leica SL2 battery grip is on the way from Wetzlar and could offer an instant solution, but this needs to be tested. Here we hear directly from Stephan at Leica Camera AG in an exclusive interview on EOSHD... https://www.eoshd.com/news/interview-with-stephan-schulz-leica-camera-on-the-sl2-and-filmmaking

No that's not what I'm saying. The image quality of RAW is not too much for me. The file sizes are ridiculous. Canon don't have a proper RAW codec. RED do. So on the 1D X III you may as well not use it and stick to the 10bit. The shadows are very grainy and noisy anyway when you try to extract the extra dynamic range in the RAW files. The noise has a compressed look to it too. 230Mbit in 4K/60p 10bit? Don't think so. In 24p maybe, but then you have the rolling shutter to contend with.

The Canon apologists are out in force! 470Mbit vs 500Mbit. Still huge. And the Long GOP data rate is almost as big if you want to avoid 32ms rolling shitter.

By cropping slightly more and upscaling slightly to 4K.

So the 4K crop modes are 1.33 not 1.5? I thought this time it was using the S35 standard in 4K crop mode - like every other camera. But no, they kept the weird 1.33x crop? Even though it has a full frame mode? I have more than one machine. The other one is a Windows machine with RTX 2080 Ti. I'll try it on that. I don't have much appetite for 2400Mbit/s file sizes in RAW though to be honest. 500Mbit/s on the 1D C was bad enough with MJPEG. So mainly a 10bit H.265 camera for me. I think in that respect, GFX 100 is much better.

If this shot is still then the Hasselblad lenses use a leaf shutter inside the lens. It could be a problem with that, or it could be a problem with the timing of the shutter in relation to the capture by the sensor. Has not happened yet with my HC lenses on the GFX 100

It isn't about me. Every thread has at least 5 pages of your opinion in it. Reams and reams of postulating from an armchair. People are not looking to read what you had for breakfast People are looking for actually useful camera information in each topic. ???? Yeah life is too precious to be wasted. YOU GOT IT

I think the bullshit in this topic is putting me in a very difficult position. The original story is about DPReview locking a protest photographer's thread on their forums. And now this one has died with such ugly bullshit remarks I may have to lock it. And then people are going to cry hypocrisy. All I can say is, there is no free speech for racists.

Chit chat, in every thread makes it hard for readers to research topics and find info. so please my appeal to you is find a more useful way of posting in general... like the guy with the lenses above because for every Single interesting post on this damn forum there is your gobbledegook sat right next to it

What is this adding to the topic?

If we're going to make assumptions about my character, how about I make some assumptions about yours! You just had a very high profile murder of a black man in your country and not once have you condemned it. So why don't we start by you condemning that, just so we can get the racist stuff out the way so we can carry on talking cameras?? Or is your love of Trump making you tongue tied?

The 1D X III has a single processor which is much faster than the dual processors in the prior models. Canon explains this in their white paper. They don't however explain what core count the CPU has. Probably a lot more than two.

It's really odd that you think my motivation for starting this topic is because I feel "left out" of the Zoom conference between DPReview's chief salesman and Cinema5D's chief salesman. Nothing would fill me with more dread being stuck in a video with that pair. I can assure you of that.

Rather than the rather heavy expander and loss of brightness, I'm waiting to see if Fuji bring a 35mm crop mode to 4K on the GFX 100.

Ever thought of actually contributing?

I still don't see the link with this topic. Easiest thing for me would be to kiss these camera industry writer's asses and reap the reciprocal links and quid-pro-quos. This video is one twat interviewing another in a circle jerk. I am not interested in that. I am infamous for not being interested in it. So what's Blackmagic got to do with it. You're saying I was butt hurt not being invited to try the new Pocket 4K when it came out? Damn right I was fucking pissed off. They deprived me of the chance to cover the new camera, because they knew I'd be honest about it. That's how PR works my friend. And they deprived all of you, the review too. And then I had to spend £1300 buying the potato just to see that it was in fact all I feared. And 6K situation was even worse. It didn't work properly and Blackmagic, rather than listen and sort it out, decided to berate me *in person* instead at IBC. Do I feel happy that a company who doesn't value me as a customer, and *before any falling out* decides to actively snub EOSHD as a long-time blog resource for Blackmagic, with a thread of 1.2m views on just one camera? No I don't. So what are you suggesting I do next then? Kiss their ass? Play the game? FFS get a clue.

Thousands and thousands of incidents of racist police brutality and it all passed you by? You'll be denying the slave trade next.