Quote from: andicgn on December 26, 2019, 11:52:15 AM
Is it possible to record straight in dng lossless?
Wondering this too
Etiquette, expectations, entitlement...
@autoexec_bin | #magiclantern | Discord | Reddit | Server issues
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 MenuQuote from: andicgn on December 26, 2019, 11:52:15 AM
Is it possible to record straight in dng lossless?
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.
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
Quote from: Walter Schulz on May 14, 2020, 07:43:21 PM
And APS-C factor in Canon realm is 1.62.
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.
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.
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
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)
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?
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.
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)
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.
Page created in 0.108 seconds with 13 queries.