Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Milk and Coffee

#101
Quote from: andicgn on December 26, 2019, 11:52:15 AM
Is it possible to record straight in dng lossless?

Wondering this too
#102
Quote from: Levas on May 17, 2020, 11:17:31 AM
Yes, there's a module which improves the write speed of the SD card. (also works for other cams, not sure on which camera's it is used, but the eos-m builds from Danne use it too)
Here's a link to the topic of this module:
https://www.magiclantern.fm/forum/index.php?topic=12862.msg199224#msg199224

Without this sd_uhs module, the 6d has a write speed of about 39Mb/s and with the module it reaches about 57Mb/s write speed.
Doesn't work on all SD cards, you need one that is compatible with the settings. (Sandisk extreme pro 95Mb/s and 170Mb/s work)
So even with the module, write speed is still lower then 5d2. (Not sure what the write speed of 5d2 is exactly, but it's probably about 75Mb/s ? )

But besides 12 and 10 bit raw recording, there is also lossless 14 and 12 bit recording, only available on digic 5 cameras.
The amount of lossless compression you get depends on the scene, the brighter the scene, the less compression you get.
For normal, good exposed scenes you get probably around 25% / 35% compression.
So with this advantage of lossless compression, you can record about the same amount of raw data as the 5d2.

But to be able to do that, you need the sd_uhs module and a compatible card.

For plain, 3x3 mode, full-view, mode video recording I think you can get about the same results, resolution and recording time wise.
But with the 5d2, you're not depended on how good the lossless compression will be, which could be a lot less on very bright scenes.
Hard to choose, for raw video, probably very comparible camera's (5d2 and 6d)

The 5d3, has both, high compact flash recording speed (about 100Mb/s) and lossless raw compression.

So to summarize: the 5D2, CANNOT do lossless compression because of the DIGIC 4 processor, but can write up to 75mb/s with the CF card. And the 6D CAN do lossless compression because of the DIGIC 5 processor, but has limited write speed to the SD card (but can be sped up with the SD_UHS module, while still only reaching ~51mb/s?)

Is there any cautions using the SD_UHS module?
#103
Quote from: reddeercity on May 17, 2020, 02:52:52 AM
I did a quick test build with no image offset , in other words I recorded the whole sensor black border & all .

First 3x3 (FHD) 2040x1267 , this is the raw_image dump
(I didn't adjust the black level , sorry it 128 should be 112 for 10bit )


Here the 5D2-3x3-Raw_Dump_dng-ppm-png.zip
If you do a crop in IrfanView you get 1880x1250 ,
which the offset is correct in raw.c  160 pixels left & 18 pixel from the top
Though this would help people understand better how the sensor is configured  ;D

So including the black pixels, the sensor is actually larger than 36mmx24mm, yes?
#104
Thanks @Levas! I thought I read somewhere that there is a module that speeds up write speed on the 6D? Do you know what that is? I can't find it anywhere.

Also Andrew Ried states here (https://www.eoshd.com/raw-video/magic-lantern-raw-video-current-camera-capabilities-updated-2017/) " Note however, that older DIGIC IV (4) cameras like the 5D Mark II, 7D and 50D do not have 10bit-12bit capability, only uncompressed 14bit raw."

Can the 5D2 do 10bit now? (That EOSHD post was from 2017)
#106
@Levas thanks so much for all the great info! Very encouraging and relieving! As you can probably tell, I'm trying to figure out which camera to buy lol.

Out of further curiosity, you said "whole sensor used in photo mode." Are the black pixels suddenly not black anymore? Is the FOV wider in photo mode? Or do you mean something like "full resolution?" (The ability to capture all 5000ish pixels in photo mode)

So with all the caveats that you listed, the crop factor (3x3 full frame mode) could loosely be called the same between the 6D and 5D2. NOW I think the winner is the 5D2 because if it's faster write speed capabilities. We could pack in more vertical resolution on standard 24fps.

Would you agree?
#107
Quote from: Walter Schulz on May 14, 2020, 07:43:21 PM


And APS-C factor in Canon realm is 1.62.

Yes, I know. 1.5x was just an example. In other words I am referring to "Focal Length Multiplier" (AKA Crop Factor.)

And I think the ML RAW Calculator's calculations are correct. At least to my math, the Focal Length Multiplier (Crop Factor) is calculating correctly based on the selected resolution setting. 
#108
Technically speaking, ALL canon (or general CMOS sensor) cameras have black/covered pixels right? Are these black/covered pixels the ones referred to when listing the "Actual" and "Effective" pixels on camera store websites?
#109
Quote from: Walter Schulz on May 14, 2020, 03:24:55 PM
I think we are all wondering where the number 1.1 comes from. Please share the steps of your calculation.

Hey Walter. If you look on this site, https://rawcalculator.netlify.app/calculator_desktop listed at the bottom is "crop factor." The "1.Xx" factor i'm using is also listed in sensor specifications of common camera reseller websites. IE: APS-C= 1.5x crop. Does that help clear things up?

@Levas, thanks for helping clear that up for me!! So technically speaking in 3x3 mode, the 6D can achieve a wider field of view than the 5D2 (since the 5D2 has this "black pixel" phenomenon?)
#110
Quote from: ZEEK on May 12, 2020, 12:23:02 PM

Whatever you touch in MLV App will not affect the DNG Files as these come straight from the sensor, so no point editing in MLV App if exporting as DNG.


@ZEEK does the "RAW Correction" panel affect exported DNG's? No panels affect the DNGS at all?
#111
So looks like the 5D2 technically records about a 1.1x crop (3x3) in mlv. Is 1.1x correct? Is it smaller than that? If you could physically measure 36mm x 24mm of the 5D2 sensor, the active pixels used for capturing MLV 3x3, would be slightly smaller? Is this a negligible crop? Even if we could add the extra pixels, would there be much of a difference?
#112
Does the 5D3 and 6D have this "black bar" issue? Is it just the 5D2?
#113
Quote from: reddeercity on May 12, 2020, 08:37:41 AM

Canon also crop's the full sensor a little bit , the real size of the sensor is 5632x3750 wide! magic lantern unlocks the extra pixels .
So with the real size 5632/3=1877 ML report this as 1880x1250


So ML "reports" as 1880, but it's actually 1877? Does that not cause an error with the file?

So it seems that the 5DMKIII and 6D, utilize the full width of their sensors because of the sensor's native resolution is divisible by 32? And the 5DMKII has to "crop" out 16 pixels because of the black pixels and it's imperfect division of 32?
#114
Quote from: Levas on May 11, 2020, 10:24:28 PM
In normal default raw MLV recording, there is no crop on the 6d, crop is 1.00.
You can select 1824 x 1026 as highest resolution in 16:9 aspect ratio.
The 1824 horizontal pixels come each from 3 pixels binned together (so the origin is from 3 x 1824 = 5472 pixels, the full width of the sensor of the 6d).
The 1026 vertical are from every third line on the sensor, (skipping 2 lines every time), so every 3th line is read, 3 x 1026 = 3078 pixels. (This is for 16:9 aspect ratio, sensor is 3:2 aspect ratio)

Thank you! Very very useful!
#115
Quote from: Kharak on May 11, 2020, 09:37:56 PM
The Magic Lantern terminology can be hard for a newcomer, but when you are trying to ask questions. It helps a lot if you use more familiar terminology. 1.0 x crop, do you mean a 1:1 ratio of the sensor? or entire sensor the full frame, width and height?

By "1.0x Crop" I mean entire width of the sensor.

I am just curious if the 5DMKII is capable of 1880px width resolution, as the OP mentioned they can only get 1856px wide as a maximum resolution. (1856px wide on the 5DMKII is a 1.01x crop of the full width of the sensor. TECHNICALLY not full width. 1880px wide [1.0x,] would be full width.)

Sorry for the confusion!

@Walter Schulz , I am inquiring about the 5DMKII, because I am looking to buy one. I currently only have a 5DMKIII on loan. I am trying to keep up as best I can :)
#116
Quote from: Walter Schulz on July 08, 2015, 06:11:32 PM
Crop mode is not using line skipping but every line in selected frame. You cannot get anything in between. It's either full sensor size with skipping or a subframe with every line used. No option for every second or 1,5 or else. It's just not there (or not discovered by devs yet which means pretty much the same for us).
The only thing coming close is "full resolution silent pics" (FRSP) which is using every pixel but is just too slow for anything else than timelapse.

To confirm, can the 5DMKII get 1880px wide/1.0x crop?
#117
Is there a crop to the full frame sensor shooting MLV on the 6D? (IE: does it say 1.0x/1.06x/1.09x after selecting the highest resolution?)
#118
Raw Video / Re: Current raw recording modules
May 11, 2020, 04:01:07 PM
Thanks Walter! Are u using a nightly build?
#119
Sorry, yes. I am referring to using the full sensor width. So 1.0x crop would be full frame/no crop.
#120
Is the 5DmkIII the only camera capable of capturing 1.00x crop RAW because of the sensor pixel dimensions?

Can we get perfect 1.00x crop on the 6D? 5DmkII? Since their sensor pixel dimensions don't perfectly divide by 3 (for 3x3 pixel binning?)

According to this (https://rawcalculator.netlify.app/calculator_desktop) the 6D and 5DmkII sensors aren't perfectly divisible by 3 resulting in 1.06x and 1.09x crops.
#121
Thanks! But I still think I'm not articulating my question well enough! Anyway, I tested, and I'm getting a good 24.00fps sync with audio!
#122
Raw Video / Re: Current raw recording modules
May 11, 2020, 05:27:28 AM
Does MLV Lite support 10 and 12bit recording?
#123
Raw Video / Re: Current raw recording modules
May 10, 2020, 09:49:19 PM
Quote from: Levas on September 18, 2018, 07:57:29 PM
Good one, new topic for raw video.

To new users I would say:
Magic Lantern (RAW) Video format v2.0 (mlv_rec.mo)                            = The old and not in development anymore module needed for raw recording.
MLV Lite                                                                                              = The current and in development module needed for raw recording.
Crop mode recording (crop_rec.mo) (1:1, RAW/H.264, 25/30/50/60 fps)  = This is more like an add-on module for MLV_Lite(or old MLV_rec.module), to give more options. But can also be used without MLV_Lite or MLV_rec module for standard Canon h.264 compression.
crop_rec on steroids: 3K, 4K, 1080p48, full-resolution LiveView               = This is an add-on module for MLV_Lite(or old MLV_rec.module), to give more options. Can't be run without MLV_Lite or MLV_rec module. This one is more experimental then the above add-on.
Can be run without MLV_Lite or MLV_rec module, but with limitations (see post below from Bouncyball)

I'm confused. I thought MLV_Rec is the module in current development, and MLV Lite has been superseded by MLV_Rec?
#124
Thanks for the reply! I think you may have misunderstood me. What I meant was --- Does Magic Lantern record REAL/Exact FPS from "FPS Override?" Or is magic lantern achieving custom frame rates by dropping frames from canon's standard/default frame rates? Does that make sense? (It's just a general question about how magic lantern achieves FPS Override frame rates.)
#125
Quote from: Walter Schulz on May 10, 2020, 08:51:44 PM
You can come very close. And remember that 24p is 23.976 fps.

When I refer to "24.00fps," im setting FPS override at exactly at "24.00fps." I DONT want 23.976. I want an even 24.

Also, generally, when using FPS override: Is FPS override a 'true' frames per second? If I set it to "24.00fps, Exact FPS" is the camera actually recording a proper 24.00 even frames in a second? Or is it interpolated/faked? IE: If I set FPS Override to "24.00," is the camera really recording a 29.976fps and dropping frames from 29.976fps resulting in 24.00fps?