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 - Levas

#26
Corrupted frames is not good   ???
Made a new crop_rec module where the max vertical resolution is lowered by 16 pixels. (So 16 lines less to read out by the sensor)

5496/3x1944 @ 24 fps
5496/3x1856 @ 25 fps

I expect this should prevent corrupted frames. Could be that it's still a little too much.
If you still experience corrupted frames, let me know, then I make a crop_rec build with the vertical resolution slightly more lower till no more frames are corrupted.

The crop_rec.mo file can be downloaded here from my google drive. you can replace this crop_rec.mo file with the crop_rec.mo file on you sd card (location on SD card:  ML/MODULES/ )
https://drive.google.com/file/d/14Rff7xmEOOVF9nxSFRYYVyKutGqhYS-D/view?usp=sharing

#27
Curious, can you see any difference in vertical line noise between raw type 0x10 and 0x12 on the 700d ?
#28
@Skinny

Tried to compile a same build for 5d2, but didn't succeed, error messages and no build.
Probably because the source is the "crop_rec_4k_mlv_snd" branch, where the 5d2 is not fully supported  ???

#29
@IDA_ML
Noticed that there is not much reaction to make a build with raw type enabled.
So compiled one for 5d3 - 113.
Not sure if it works, it's on your own risk, can't test it on a 5d3.
Also made a 6d build from the same source and tested it on my 6d, works and with raw_type selection in debug tab.
(sourcecode is "crop_rec_4k_mlv_snd_isogain_1x3_presets"

Couldn't figure out how to compile without crop_rec module and sd_uhs module.
So I unpacked the zip file, uploaded the complete folder to google drive and removed the sd_uhs module and crop_rec module manually.
(crop_rec and sd_uhs modules in this build are made for 6d, not sure if they work on 5d3, so removed them)
Since this build is based on the crop_rec_4k source, you can of course use crop_rec modules from other builds with this build, just copy the crop_rec.mo file from another build in the ML/module/ directory

As you know, if it breaks you get to keep both pieces  :P

https://drive.google.com/drive/folders/10a3g3M_b5n8DufDAaZMagcWsAXN8c_14?usp=sharing

For quick test to see If it makes any difference for vertical line noise.
Enable the following modules first time you start the camera with this build:
-mlv_lite
-mlv_play
-mlv_snd
Restart camera

Go to debug tab in ML menu and check LV raw type is 0x10
Now set iso to 25600 and shoot some ML raw video in low light.
After that, set LV raw type to value 0x12 and shoot another raw video in low light.

Curious, see any difference on 5d3 ?
#30
It's not difficult to test yourself, all you need is a build for your camera, where the option is enabled.

You can ask in the forum of your camera if someone can make a build where it is enabled.

The option is in the 'raw.c' file, located in the 'src' folder in the source files.

For example in the source on magic lantern page:
https://foss.heptapod.net/magic-lantern/magic-lantern/-/blob/branch/unified/src/raw.c

In this example, it's on code line 37

#undef RAW_DEBUG_TYPE   /* this lets you select the raw type (for PREFERRED_RAW_TYPE) from menu */


All someone has to do is change the 'undef' to 'define' and you will have an option in debug menu to alter the raw type value which will be used for raw video recording.

So the line has to be changed to:

#define RAW_DEBUG_TYPE   /* this lets you select the raw type (for PREFERRED_RAW_TYPE) from menu */


There are a lot of raw types value to choose from, some might freeze your camera, but in that case, pull out battery and try again  : ;D
There aren't that many clean raw type streams, most contain the purple pixels.
I think for Digic V an Digic VI the values are the same, so I expect default is 0x10 on other cams and first thing to try would be value 0x12.
Then do some comparison in low light high iso (6400 or higher) and see if there is any difference.

Edit: you can't see changes to raw type in canon liveview, but it will do show up in ML preview, the slow low resolution preview option available in raw video menu.
#31
No, different LV raw types exist on all cameras.
It's a debug options, so disabled in most ML builds.
In some 6d builds, I have the option enabled and available in Debug menu.

Lv raw types are data streams of the live view raw data. There are a lot of raw type data streams, some are more altered then the other.
There are raw types which contain purple pixels (dead/hot pixels), while on other the dead/hot pixels are fixed and not present.
So it seems that canon does some fixing on the raw data stream.

The difference between 0x10 and 0x12 on the 6d:

0x10 -> can be used with high resolution crop rec options and 0x10 has highest dynamic range.
In high iso and low light, vertical line noise becomes visible in image.

0x12 -> only works for normal available resolutions, doesn't work with the altered crop rec module resolutions.
Dynamic range is slightly lower ( 0.5 stop ). No vertical line noise in high iso low light situations.

The above difference means that canon is doing some dark frame correction in camera on raw type 0x12. Explains the lower dynamic range and missing vertical line noise.

Not sure if the above applies to other camera (lv raw type 0x10 vs 0x12).
#32
Bright saturated noise,  sounds like hot pixels ?
MLV app has option to fix bad pixels.
BUT, what helped me a lot to get rid of most of those hot pixels is to do a dead/hot pixel remap in camera.
you can google it, canon pixel remapping.
How it's done.

-Remove lens and put on body cap.
-Turn on camera and to get best results, enable liveview and set it to iso 6400 and leave it that way for a minute or more so the sensor becomes noisy.
-Now do a sensor cleaning in Canon menu (almost in the latest tab of canon menu, 'sensor cleaning' and choose 'clean now'.

After this, you should have much less hot pixels.


Darkframe subtraction is mostly helpful to remove vertical line noise in raw video.
But there is even a better way for 6d.
For low light, you should use LV raw type 0x12 (only works for normal raw recording, not working for high resolution crop module modes)

Not sure if you have a build where you can alter 'LV raw type', it should be available on top in the DEBUG tab of ML menu.

Debug tab -> LV raw type option
Default LV raw type = 0x10
For low light, set it to 0x12, highlight LV raw type option, click set button, use cursor keys to set cursor below the 0 from 10 value, and use scroll wheel on top of DSLR to set it to value 2, so you get 12.
Now use set button to exit and you should have LV raw type value of 0x12

Now shoot a scene in low light, in this mode, even iso 25600 looks great.
Every time the camera is turned off, the LV raw type is set to default 0x10 value.

If you don't have the LV raw type option in DEBUG tab,  try the build in this post:
https://www.magiclantern.fm/forum/index.php?topic=25782.msg228784#msg228784


#33
The preview is indeed very slow, unfortunately I don't have the knowledge to fiddle with the preview options in source code.
I made the custom resolutions for crop recording on the 6d, so learned a lot about the crop_rec module, but the rest of magic lantern source is like magic to me  :P

Canon liveview is broken in 4896x2160 crop rec option.
You could however use the 5496/3x1960 at 24 fps option in crop_rec menu.
5496/3x1960 has canon liveview working (although a bit squeezed and zoomed in)
Depending on your 'preview' setting in the submenu of raw recording, you could switch from Canon liveview to slow correct preview with half shutter (works while recording)

The way I would use it:
Use 5496/3x1960 at 24 fps in crop_rec menu.
Go to RAW video submenu (use Q button on RAW video in the MOVIE tab in ML menu.
Set resolution lower to get desired resolution/aspect ratio, you can use scroll wheel on top of your DSLR to set it (for example) from 1824x1960 to 1568x1960 to get 4704x1960 at 24 fps (2.4:1 aspect ratio).
Now go to preview option and set it to 'real-time'.
Now exit menu and you will see some distorted canon liveview which is as fast as Canon liveview, although not correctly framed, but if you do half press the shutter button, the correct framing preview shows up  :D
So use half shutter to get framing right, release half shutter to set focus right and keep track of your subject. While recording, you can check framing by using half shutter press.
So that's the most usable way I found, using real-time preview and occasionally using half shutter press to check framing.



#34
Not an expert with exiftool, but learned some useful commands on this forum  :P

The command line you're looking for is:
exiftool -IFD0:DefaultCropSize="1952 1112" *.dng

Use this command, while being located in the directory were the dng files are.

The above command keeps the originals, doesn't overwrite stuff.

If all works well, and you want to overwrite originals:
  exiftool -IFD0:DefaultCropSize="1952 1112" -overwrite_original *.dng

Not sure why the IFD0 part has to be used, but it is common, some standard layer naming in exifs or something  ???

#35
Camera-specific Development / Re: Canon EOS R5 / R6
February 04, 2022, 10:21:37 AM
Quote from: IDA_ML on February 01, 2022, 07:56:06 AM
I was wondering if you made any comparative experiments with your 6D vs. R5/R6.  No wonder if we get to see some interesting surprises here.

Not yet, want to do some tests outside, but the weather is not that inspiring last few weeks   :P (clouds/wind/rain)

I'm very curious about comparing the 6d in dual iso mode (for photos), the R5 has more dynamic range at iso 100, but 6d has dual iso.
And maybe some other things to compare, ML raw 14 bit video on 6d vs canon 12 bit video on R5.
#36
General Chat / Re: Canon EOS R5C
January 29, 2022, 05:18:25 PM
I should get back to discord, tried it for a while, didn't like the layout  :P
Seems like this forum is abandoned by most people in favor of discord.

Installed discord on my phone again, ah account still works  :D
#37
General Chat / Re: Canon EOS R5C
January 29, 2022, 04:45:03 PM
For photo mode this camera uses some sort of canon r5 firmware.
For video mode this camera uses some sort of cinema line C70 firmware.
Further the camera needs several seconds to switch between photo and video mode.
So wondering, is this camera actually using 2 different firmwares and switches between them when switching modes (or is it packed within one firmware ?) ?

Also wondering, is it running both firmwares on the same Digic X processor ?
Or did Canon put an extra DIGIC DV7 processor in there, not likely  :P
#38
Camera-specific Development / Re: Canon EOS R5 / R6
January 29, 2022, 03:56:35 PM
The above means, that in canon log 3, shadow data is pushed in post by three stops.
This is a lot and is the reason for shadow noise in log footage.

For non raw recording, and also for the R6:
If you're recording a low dynamic range scene (8 stops or lower), it could mean that you might be better of with exposing to the right and not use canon log 3.
This way, you could have cleaner shadows I guess (not sure, not tested it  :P)
#39
Camera-specific Development / Re: Canon EOS R5 / R6
January 29, 2022, 03:45:16 PM
Happen to have a R5 here and I noticed something which I haven't seen mentioned anywhere else around.

When recording in raw(internal 12 bit), selecting the Canon Log3 option does have influence on your raw data.
Side to side comparison in DaVinci Resolve, canon log 3 activated, and canon log settings to off, shows that activating Canon Log 3 means that the camera is actually recording at an ISO value of 3 stops lower.

Please test yourself.
Record something in 8K raw at iso 800 and with canon log 3 activated. (use fixed value for shutter time and aperture)
Now record the same in 8K raw at iso 100 without canon log 3 activated. (with same aperture and shutter speed ofcourse )

Now load both files in DaVinci resolve, go to the raw tab in color mode, and set both to:
Decode quality -> Full res - Canon
Decode using -> clip
Colorspace -> canon cinema gamut
Gamma -> canon log2
iso -> 800 (both files to 800 to match iso 100 recording to iso 800 recording)

Now look at the parade waveform, it's identical, max highlight data, noise in the shadows etc.

Now when recording in raw, and having canon log 3 activated, the lowest iso you can choose is iso 800, which makes senses, because in the background, it actually records 3 stops lower in iso 100, to save the highlights.
Also, when comparing footage recorded in iso 12800 with log 3, it's the same as normal non log raw at iso 1600. Same highlights, same shadows, same noise.

So when recording in raw, maybe better to not have canon log settings activated  :P
All of the above applies for internal raw recording.
#40
Quote from: gonzzalo_b on November 13, 2021, 12:58:52 AM
I can't playback the videos with 12 bit uncompressed and 10 bit uncompressed, only black frames are played, but when I transfer to the computer I can see it and edit. I will not use it because for me it is important to preview the video and be sure it is ok.

This has probably to do with mlv_play module.
The 12 and 10 uncompressed are seen as obsolete, because 14 bit lossless compressed is about the same size as 10 bit uncompressed.
So... if you can choose to record 14 bit lossless compressed at the same data rate as 10 bit uncompressed, why bother using 10 bit uncompressed.
Needless to say 12 and 11-8 bit lossless compressed are even smaller in file size then 10 bit uncompressed.
If you really want playback to work with 12/10 bit uncompressed, you can try swapping the MLV_play module file on your card with some MLV_play modules from other builds, like the one on the download page of magiclantern site. This will probably work, but big chance you can't play back lossless compressed video files.

Quote from: gonzzalo_b on November 13, 2021, 12:58:52 AM
Notes:
-In the SETTING A (240Mhz) after playback, when I record and automatically stops recording the flushing buffer remains a longer time. (Maybe the problem is after the playback can't reset the memory and for that reason can only record a few frames.)

Did notice that recording times are different sometimes, not sure what it triggers, but as you point out, it probably has to do with playback.
I can imagine that the UHS-hack settings won't work after you did some reading on the sd card (which happens in playback).
absolutely no idea how to fix this, but luckiliy you know what not do, not use playback function, or restart camera after playback  :P

Quote from: gonzzalo_b on November 13, 2021, 12:58:52 AM
-In playback mode, when I select the videos with compression (14 ,12, 11-8) appear the same info. It shows "14 bpp LJ92" in each video with different bit rate.
-When I change the SD OVERCLOCK and restart the camera, do not update the frames that it can capture until start the first recording, after that it showns the real frames can be recorded. (Maybe this module have problems updating)

Yeah this is normal behaviour and makes sense, only if you know how it works.
The compression you choose, only alters the image to be recorded, it sort of cuts out some stops of highlight data (which can be seen in raw histogram).
When 12 bit is selected, it cuts of 2 stops of highlight data (one bit of info is one stop if image info), but the resulting data is still recorded in 14bpp LJ92 data format.
But since this format uses LJ92 lossless compression, it can compress the image a lot more because of the 2 stops of highlight data missing.
So your raw data stream is about 12 bit, but you camera file format records it in 14 bits, lossless compression sees that it's only 12 bit data, so lossless  compression factor is much higher/ more efficient).

#41
Quote from: fred_76 on December 16, 2021, 04:17:20 PM
By the way, is it a big work to modify the ML intervalometer so that it could allow shooting at 1/10s step, instead of 1s step ?

Not possible, hardware limitation, sensor readout and write speed not fast enough.
1/10s means 10 photos per second.
Canon 6d has a burst rate of 4.5 fps. One second divided by the burst rate ( 1s / 4.5fps ) is 1/22th second.
But even that is limited to the buffer, since the write speed (without UHS-speed hack module) is about 40MB/s.
Full resolution CR2 raw file from 6d are about ~25Mb, which means you can't write them quick enough to your SD card. It's limited to slightly less than 2 photos per second.

Other options to consider for 1/10s intervalmeter is raw video.
With magic lantern raw video and crop_rec module you can choose some high resolution crop options.
In the latest 6d build posted in this topic, there is a 4096x2304 at 10fps preset (so you're recording the 4096x2304 pixels in the middle(could be little of, not sure) of you're 5472x3648 sensor, so you have an crop factor of 1.33x)
Within the crop_rec submenu you can even choose to set shutter range from original to full range, which gives you the option to record in 10fps with a shutter time of 1/10th of a second.
#42
Yes, for continuous recording I guess these setting should work very well with most cards. And it's the most stable and convenient way.

1824x776@25fps is about 37MB/s in data. (Standard max write speed of the 6d tops around 40MB/s)
Lossless compression varies depending on the scene, bright scenes get less compression. So if you really get continuous recording times also depens om the brightness of the scene.

For magic lantern beginners the above build is the most convenient to get used to working with raw recording.

There is a build with a module that gives the 6d more write speed, but you do need a sd card that works with it. With a compatible card and that build you can shoot continuous in 16:9 aspect ratio ( 1824x1026)
But it's all a little bit more fidely.
My advice, first get used to magic lantern and raw recording.
And once you feel the need for more you can read this topic, which contains more experimental builds for 6d.
You might experience some lockups with these more experimental builds, in that case, take out the battery and re insert and start camera again ;D
https://www.magiclantern.fm/forum/index.php?topic=25782.0
#43
There is a preview option in the submenu of raw video.
It's probably set to preview or auto, if you set it to liveview, you should see normal liveview as you're used to.

And with 720p, do you mean you have your camera set to 720p 50/60 fps in Canon menu ?
If so, you will get a raw recording that has to be vertical stretched by about 1.67 factor. (Canon is skipping some vertical lines to get to 50/60fps)

If you don't mind having 25/30fps, you're better of with normal 1080p mode in Canon menu. In this setting you don't need to stretch the footage by a factor of 1.67
#44
I see you're using the nightly build, you might want to check out the croprec4kbuild for 6d, it's on the dowloadpage -> experiments.
https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip
(Spoiler, there is no 4k on the 6d, there is only 4k on the 5d3  ;D )
But This build has the lossless raw recording option and even lower bit depth lossless raw recording. I think lossless options are missing in the build you're using ?
Lossless improves recprding times a lot.
The experimental build has a module mlv_lite (you don't need mlv_rec module)
This mlv_lite module has lossless raw recording in 14 and 12 bit depth, or even lower.
Lossless recording in 12 bit is on most normal sd cards continuous on 6d.
#45
For video you're way better of with the 5d3
5d3 has faster write speed to storage card and sensor read out is faster (which gives you higher resolutions at the same frame rate compared to 6d).

For photo's probably not much of a difference.

Concerning Magic lantern, 5d3 has bigger userbase / more developers and is therefore more updated compared to 6d.

#46
The original Canon firmware updater file for Canon 6D to version 1.1.6
Uploaded it to my google drive(long time ago). Contains the original .FIR file and some instructions PDF files in different languages:
http://drive.google.com/drive/folders/1_WpYbRMOm_XrjWJxnns1FMiEN0tzZBWV?usp=sharing

#47
Reverse Engineering / Re: UHS-I / SD cards investigation
September 23, 2021, 05:21:37 PM
Tested the build Bilal posted on the 6d.

Quickly benchmarked the 240+ preset in both play and video mode...but both my sandisk cards (95mb/s and 170mb/s) drop to ~20mb/s read/write speed  :-\

Will look into the source and test a little further but I think these 240+ settings won't work for 6d  :-\
#48
Yes, there is a preset in crop module for 1824x904 at 48 fps (which can be used to record 1824x776 resolution, which can be set in raw video menu)

It's under the 720p presets and must be used with the camera set in 720p video mode in Canon menu. These high fps modes won't work in normal 1080p mode, camera freezes and you need to do a battery pull ;)

Edit:
Not sure if this works, but to prevent switching between canon 720/1080 p modes, you could try to use 1824x904@48fps preset in 720p mode (with aspect ratio set to desired 2:35 in raw video menu to get 1824x776)
Once you want 24fps, try using fps override to see if you can get 24 fps instead of 48 fps.
Fps override is easy to switch on an off to get 24 or 48 fps.
#49
Raw Video / Re: AI algorithms for debinning
July 20, 2021, 01:41:59 PM
Quote from: Kharak on July 20, 2021, 12:36:51 PM
The R5 raw is not raw, I graded and shot a lot of R5 footage and the lossy compression is evident in the shadow detail. The noise floor is really bad, barely any information can be harvested from the shadows.

Curious, which raw format are you talking about, looking at the 5R specs and it seems to have 3 options for raw.
Where the 2600Mbps option is called raw and not raw light  ???

8k Raw (29.97p/25.00p/24.00p/23.98p): Approx. 2600 Mbps
8k Raw (Light) (29.97p/25.00p): Approx. 1700 Mbps
8k Raw (Light) (24.00p/23.98p): Approx. 1350 Mbps

Recording is in 12-bit, so if I calculate correct non compressed should be about 10000 Mbps. (12-bit at 24fps)
So the highest options has a compression ratio of 4:1.
#50
Raw Video / Re: AI algorithms for debinning
July 20, 2021, 01:30:34 PM
Ah yes it's called LJ92 compression and not J92 compression and 5dr is ofcourse R5 (fixed it in my post  :P )

What you say about the R5 raw footage confirms my expectations.
The Canon cinema raw lite file format could be considered more like a new codec type recording option then a raw format recording option.

probably all those high ratio raw formats like 6:1 and 5:1 could be considered as new codec types to choose from (instead of H.264 or H.265).

Since there is no way to get a raw image sequence from the R5 CRM files, I wouldn't even be surprised if it isn't even intraframe compression (All-i) but some IPB compression on raw data.
Could be the case, since it's one big file, nobody knows what data is really in there  :P