Messages

Interesting, is there any calculation doc about registers settings for cmos5 and cmos7 ?
I started with values taken from the code (0x20 & 0xB87) but it's not clear how it works.

Awesome, tested with wide lens (and speed booster), it's amazing. Using Resolve AI upscaler add even more sharpness to the image.
Great job dudes 
I'm wondering what we can expect more from that little beast

Here -> https://drive.google.com/file/d/1MWE1chTVrV3EWb3rUA5ZkCKZpdkN37By/view?usp=sharing

Working here too I had to compile it by myself cause the binaries are for 5D3
Doing some tests right now

Can't wait to try it !! 5K is my preferred mode because of its "almost-no-crop" nature

Yep, just tested it, lot of pink frames.... Too bad, cause it improves image quality on non pink frames

In play mode the 128Gb Extreme pro 170MB/s reports a fabulous 95Mb/s

Same with the microSD 64Gb/90MBs, 62MB/s now (that was the worst case before the hack with 42MBs)
Super happy

Quick test with the 32Gb/90MBs and it looks like perfs are better. I have been able to record 2520x1070@12bits continously. (Benchmark says 62MB/s, got 48MB/s before the 240MHz hack)

Not yet, was too excited to test it at such a speed 
I wil for sure do that

Ok, I made a write benchmark and I accidentally pushed the set button,what deactivated the live view... Indeed I get 69MBs now 
Thanks for that hack

I used the 128gb in the picture I attached earlier.
I did reboot after the setting change...

Good news here, the card benchmark reports 40MBs but recording go higher with last build... I've been able to record 2.5K at around 78MBs continuously.
I will do more test this afternoon

I know, just a test, weird thing though, the speed does not fall to 20MBs with the non pro card

I have not kept the blister, unfortunately....

I tested with :
32Gb 90MB/s -> 50GB/s @ 192 & 240MHz
64Gb V30 U3 microSD (no speed indicated) -> 40GB/s @ 192 & 240MHz
No real gain here...
Frustrating.. 

No luck for me  SanDisk ExtremePro 170MBs 128Gb "made in China" card here... I hope we can find a fix for those
@192Mhz -> 60.5MB/s
@240Mhz -> 20MB/s

I use those maps successfully (5K anamorphic, 2.5K, 1080...): https://github.com/ilia3101/MLV-App/tree/master/pixel_maps

I use C-mount lenses in 2.5K mode on EOS-M, I really love that mode. I currently use the canon-gui arrrows to shift the crop area and center the lens, it's OK, but I was wondering if those X-Y shift values could be read from the camera registers, dumped in the crop_rec config file then restored at startup ?
It's something I can do if someone tell me how to do.

Good idea, but the battery pack is larger than the camera 

Hi,
Here's how I made my (poor man) external battery for my EOS-M :


The dummy battery is 3D printed and I use 2 3.7V batteries (18650) from a salvaged notebook power pack (contains 6x18650).
I found the batteries holder on eBay for 4$.

Tough ! Thank you for the reply. I'll do manual correction.

[sensor_res_x / (sampling_x * raw_res_x) * sensor_crop]

Here's what I found so far, but seems wrong (or miss parameter(s)) :
sensor_res_x / (sampling_x * raw_res_x) * sensor_crop
where sampling_x = binning_x + skipping_x

example : on EOS-M raw video 1800x754 with 3x3 sampling (3x1 binning) gives a crop factor of 1.56 (!!)

Oh, yes, there is a lot of information, but I don't exactly know how to do the calculus with pixel binning/skipping values...

Yes, I get the sensor crop factor (1.62 on EOS-M) via (mlv_oject*)->RAWC.sensor_crop, what I'd like to get is the crop factor when the captured image data doesn't fill the entire sensor (in crop mode)