Glad you've found the video useful. As for the short battery life, I'd suggest powering the camera off USB-C. If you've got a reasonably modern laptop that uses USB-C for power an charging, you almost certainly have a suitably powerful charger to power the camera.

thank you for this tip, yes i am using MacBook M1 1TB 16GB i totally forgot about it good idea @@PointsInFocus

It's hard to say. MP4 uses the more efficient HEVC (h265) algorithm (at least in 4:2:2 mode) and is interframe/long GOP only. HEVC saves about 2x the bit rate compared to AVC (what XF-AVC uses), and being long GOP instead of intra compressed saves even more. Given that the bit rate is about 1/3 of the bit rate for XF-AVC, the image quality should be pretty close in most cases. However, in some situations the intra-frame compression of XF-AVC may do a better job than the longGOP compression of MP4. This is one of those situations where you'd probably have to shoot some test footage in the kinds of situations you're going to be shooting, and evaluate those to get an useful answer for your specific situation.

Log gammas and color spaces are already on the to do list. It's just a matter of getting to them and getting them done. Hopefully it'll be coming along sooner rather than later.

I don't have enough experience with XF-AVC to be able to really comment on it comparatively. I basically shoot everything in MP4, because the quality is good enough for my needs and I have to be mindful of file sizes. This is something I've wanted to really dig into objectively, but I haven't figure out a good way to do this without trying to spot differences between video clips and then decipher what's a difference due to compression versus just something being slightly different in the scene.

I agreed that not being able to see the file as a thumbnail is annoying 😂

Someone told me about Apple’s Mac Pro Video Codecs install - I installed it and all is good. 👍🏻

what about for window pc?@@BrianSellers

@BrianSellers what about Windows pc ?

It doesn't matter. When shooting in raw, the CLOG setting is only saved as metadata for post process conversion.

No, the R5 doesn't support XF-AVC. AVC on the R5 is limited to 8-bit 4:2:0 in an MP4 container. The differences between the two is the container format (XF-AVX uses an MXF file, while AVC on the R5 is in an MP4 file), bit depth (XF-AVC is recorded in 10-bit color, while AVC on the R5 is only 8-bit), and chroma subsampling (XF-AVC supporst 4:2:2 while AVC on the R5 only is 4:2:0). Ultimately which is better depends. XF-AVC can deliver a better quality image, but it can be harder to work because it can't be decoded by most GPUs and the high bit-rate makes it slow for CPU/software decoding.

You can convert raw into whatever lossly log curve you want. Doesn't even have to be Canon's. But it's not going to give you any more control, dynamic range, or information than was in the raw files to start with.

@@PointsInFocus but its confusing when Netflix officially rejects R5c for this one reason that it's missing Clog-2. It was in their blog post or some official account elsewhere. Shoot RAW and have Clog-2.

Netflix has approved the R5C as a primary camera on a Netflix production, so... That said, if your goal is to use Netflix's standards then you can't shoot in raw anyway, as they didn't approve that. So the idea of shooting in raw, and then converting to something else with clog2 encoding doesn't work if your goal is to stay within their approved constraints. That said, if your NLE supports Canon's Cinema raw files, there's precisely 0 reason to incur a generation quality loss and convert them to anything else just to pointlessly have something encoded in what's quite possibly the worst Canon log curve you could use for R5C's files anyway.

I don't know if this will work or not... This is the link to download what I think is the latest FCP Raw plugin for Canon. pdisp01.c-wss.com/gdl/WWUFORedirectTarget.do?id=MDIwMDAwNjU4NjAx&cmp=ABR&lang=EN Unfortunately, they don't have an easy way to link to the specific entry on the support page, so if that doesn't work, you'll have to search through the downloads on www.usa.canon.com/support/p/eos-r5-c#idReference%3Dsoftware-drivers. I had to go back to mac os Monterey to find it in the list.

wow, thank you it works. @@PointsInFocus

Hi, @TheAgora123, it seems that you're disappointed that you didn't receive as timely of an answer to your question you would have liked. To start with, that's definitely on me. However, please understand, I work on this channel alone. As such I'm responsible for carrying out every step of the process from generating the ideas to editing the final video. All of this takes a considerable amount of time and mental energy, sometimes leaving little left to respond to questions and comments as soon as they come in. As for your question. Again, you'll have to forgive me as I'm having a hard time trying to parse out what exactly you're asking. In reviewing your previous comment on this video, it seems that you're asking about the quality differences between MP4 and raw lite at 8K. Unfortunately, I don't have a satisfactory answer to that for several reasons. To start with, and this is actually the topic of my next video, it's virtually impossible to produce objective measurements on in camera recorded video on the R5C, as there's no way to simultaneously record MP4 and raw file. Shooting in raw compounds the problems, as the final image quality depends on the post processing software used to render it. You can get significantly different results if you're working in Premiere Pro while I'm working in Da Vinci Resolve. Ultimately, the best way to asses quality in situations like this is to shoot some test files; process them in the software you intend to use for your project; and evaluate them yourself on a screen that matches your intended viewing conditions. _There's no better judge for what looks best to you, than you._

@@PointsInFocus Thanks