Відео

If you're using shutter angles, there's nothing to adjust. Leave the camera at 180° and as a product of what a shutter angle is, the exposure time will be adjusted automatically. If you've set the camera to use shutter speeds instead of angles, then you do have to adjust the speed manually.

If you select something that's grayed out and press the set button, the camera will tell you what function is interfering with it.

The table you're looking for is on pages 242 and 243 in the manual. According to the manual released with 1.0.9.1. According to the tables, the CN-E 18-80mm T4.4 L IS KAS S it's fully compatible with camera iris control, camera zoom control and autofocus.

@@PointsInFocus Much obliged!

We're talking about the R5, not the mark 2. And on the R5 there's no point in testing with the electronic shutter since that's not frame rate limited by battery power level.

@@PointsInFocus Whoops my bad.

No worries.

@@PointsInFocus So I assume you are confirming that in ES mode the regular battery powers the camera at maximum burst just fine. That is interesting to see the choice of shutter mechanism is enough to overwhelm the battery.

Keep in mind, in ES mode the camera is basically shooting video but saving the frames as stills. The ADCs are in 12-bit output mode, and the aperture stays stopped down (except in some rare circumstances), and metering and focus are measured at the stopped down aperture setting. So there's not a lot going on power wise other than the sensor read and AF drive. In FEC mode, the camera is cycling everything like a traditional camera. Stop down the lens, reset the sensor (this is the electronic first curtain), make the exposure, close the second curtain, read and reset the sensor again, open aperture, open the first curtain, measure focus and exposure, drive the lens, remeasure focus and repeat.

Good catch. Thanks!

Thanks. Not sure what was up with that, but it should be fixed now.

Battery intern is LP-E6NH and extern smallrig 99. Maybe I need the new Batterie LP-E6P?

PD shouldn't (and doesn't at least on my camera) block changing the sensor mode or media size. My suspension is that you've actually got a setting somewhere that's preventing that (something that got reset in the firmware update) but I'm at a loss at the moment as to what setting that could be. About the only thing I can think of off the top fo my head is that you could backup your camera's settings and reset it to factory defaults and see if it's still happening. If it is, then you may have to get in touch with Canon support about that. Though if I think of something else that could also be the problem, I'll post back.

Hi you right. I reset the Factory defaults and it works. When I load the old settings from the SD Card I have the same problem again. Thanks

If you close the terminal, the commands you ran should be saved in the history (you can press up to step back through your history), but the history will lost after enough commands are issued. If you want to save them permanently you should copy and paste them into a file and save that.

I haven't even tried it yet. It's on my to do list to dig into, but Canon dropped this so close to Christmas and my end of the year break that aside from getting the video out I really haven't dug into anything yet.

Does it happen with different lenses and in different lighting? That's a hard problem to diagnose without seeing anything. Though honestly, if it happens with multiple lenses and in different lighting conditions, I would suggest just getting in touch with Canon support.

Re. 1: I don't see any difference in quality between 40K60 and 4K30, and both are down sampled as far as I can tell. So I'm not sure what difference you're seeing that's making "4k60 really disappointing..." Re. 2: The camera already is DPAF II (and always has been). That tech was inherited from the R5. Not sure why it's taken so long for the other cinema cameras to get it though. Re. 3: That would be nice. But Canon doesn't read the comments on random UA-cam channels, and I'm nether a Canon employee, brand ambassador or explorer of light. In other words, I have precisely 0 influence on anything they do. So if you want gyrodata, I would recommend bringing it up with every Canon rep and employee you talk to. d.) WiFi….. To start with, the built in WiFi is not very good. I wouldn’t trust it in a professional environment, given it’s performance with direct line of site to enterprise grade APs with nothing else going on. I've tested this, and have a series of videos on it. The grips themselves aren’t great for Canon either, I don't know why everyone assumes they're such a money maker or something. They’re expensive because they’re a very low volume part that’s comparatively expensive to build (machined Mg). They likely exist only because of the limitations of the internal chip/setup in high performance applications. My guess is that Canon barely breaks even on the WiFi grips when you factor in the engineering, certification and tooling costs. That said, while I’m sure it could be enabled, my guess is that Canon’s professional conservatism is stopping that. Canon has always been more conservative when it comes to disabling features that don’t fully function than most other companies. If they can’t deliver a low latency full HD feed over WiFi that can actually be used for monitoring in a professional environment, they’re likely not going to enable WiFi at all. FWIW, it seems to me that the cinema team continues to maintain that philosophy even though it’s clearly relaxed in some respects on the consumer camera side. So no, I don’t see the internal WiFi getting enabled ever on the R5C. It will take a new camera with a better WiFi implementation that can support professional users before that happens.

@@PointsInFocus R5C 4K60 is better than R5 4k60, worse than R5C S35 4k, much worse than SONY 6700 4k60. It's pixel binning with some heavy handed sharpness enhancement, looks bad. The only way to get a good 4K60 out of R5C is 8K60 or s35 4K60.

Yes, it works anywhere you have either an AF frame or the manual focus guide.

Thanks so much, and I hope you have a great holiday season as well!

Thanks so much, and I hope you have a great holiday season as well!

I don't think we'll see that in the R5C, and I'm dubious that it would make the cut on an R5C mark 2 (assuming there is one), at least not as long as the cinema camera team is behind the software and overall design or until there's a big change in the post production software environment that can handle aliasing artifacts properly.

Thank you very much, and a Happy Holidays to you as well!

Thank you, and a happy holidays to you too!

Yeah, because other brands have exactly the same camera and wifi + gyrodata :)

Unfortunately, it sounds like you're going to have to get in touch with Canon to get that fixed. If it was a failed flash, then you'll likely have to send it in to have it fixed.

Much appreciated and Happy holidays!

I hope so. But then again the current R5C does everything I need.

Yes, just except for clog2

Based on the math that I've done, as best as I can figure it's because the R5C's sensor cannot capture enough dynamic range to warrant the decreased precision that comes from the format's log curve (nor can it write 12-bit compressed files either). Remember, all log formats are just lossy compression. They all are designed to cram more dynamic range into fewer bits than a equivalent linear file. The more dynamic range they're designed to compress, the greater the losses in precision in any given stop. Clog2 is designed to encode 18+ stops of DR. The R5C's sensor, due to the 12-bit ADCs in video mode, is hard limited to 12-stops (and lossy files, which are the only ones to use the log curves, are limited to 10-bits). Both clog (15+ stops) and clog3 (16+stops) are more than capable of supporting that, and their increased precision in the mid tones compared to clog2 is better for 10-bit files. So far as I can tell, Clog2 only makes sense on cameras that can actually capture >15 or 16 stops (like the C300-3 or C70) or cameras that can write 12-bit compressed files. Neither of which the R5C can do.

​@@PointsInFocus Thank you so much for the explanation.

this is not the worst,the worst is photo mode can use bluetooth but video mode can not using bluetooth, very anoying while in video mode and can not link with dji 3 pro,f

R5C will never get clog2 just accept it

@@jaylee2656I also can’t believe this hasn’t been corrected in 2024. Not enough people talking about this! I also have RS3 and only way still is to use the HDMI splitter, N3 cable or £1000 WiFi grip.