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

#1
Raw Video / Re: Abnormal sparkling pixels in Canon 6D
December 23, 2023, 10:28:27 AM
I call them hot/cold pixels, but they aren't indeed the type that are stuck forever. So it's not the same as a permanent hot/cold pixel which would show up at the same spot in all of your photos.
These hot/cold pixels are dancing around the frame and show up when using high iso on a low light scenery.
I took a closer look at your files, and the sparkling pixels show that either one of the green channels has a value of zero (so at the moment of recording, in that particular frame it was temporarily a cold pixel in the green channel).
It also happens in the dark area's but there the other pixels have values near zero, so it won't show up as a weird color.

For as far as I know, this is very common for all canon DSLR's with magic lantern raw video. Mostly it can be fixed by using hot/cold pixel fix in your raw editor (for example MLVapp with bad pixel fix)
What really helped reduce these for me is the dead pixel remapping (automated by your Canon DSLR, less then 5 minutes of work)
https://www.youtube.com/watch?v=9Nrn2N_syBA

Take the lens of your camera and put the body cap on the camera.
And perform a manual sensor cleaning in the canon menu and wait for a while(probably one minute) to turn your camera off.







#2
Raw Video / Re: Abnormal sparkling pixels in Canon 6D
December 22, 2023, 05:32:01 PM
Those are hot/cold pixels, very normal when using high iso. (iso 3200 and higher probably).
Can be fixed in most raw photo/video software, search for hot/cold pixel fix.

MLVapp also has an option to fix this, it's called: Fix bad pixels.
It's Off by default, but the options auto or force fix most of dancing colorfull pixels in your samples.
For further cleaning in MLVapp, you may want to use chroma smoothing, 2x2 or more aggresive 5x5 setting.

Furthermore, you can reduce those in camera also quitte a bit for future recordings by doing a hot/dead pixel mapping one your camera.
Google for:hot/dead pixel remap canon dslr
Helped a lot with my 6d. Before doing the sensor cleaning without a lens attached and a body cap on, I warmed up the sensor by using iso 6400 in video mode for a few minutes.
#3
Quote from: HugoMouteira on August 21, 2023, 01:52:14 PM
one think I noticed is that 6D lacks a 5k mode, unlike eos M or even 5dIII. Could you explain me why? It has even more 2MP than eos M, why it lacks that?

The reason for this is, the sensor readout speeds is too slow on the 6d.
The APS-C camera's have faster readout speed (smaller physical size gives them probably faster readout speed with the same design)

The 6D is the cheap full-frame from Canon, readout speed is rather slow compared to the APS-C Canon's.
Sensor of the 5dIII is a different design, readout speed is almost 2x as fast compared to the 6D. 
That's why the 5DIII has all the cool high resolution options like 3.5K crop mode and such.
The 2880x1200 crop mode is the highest resolution possible in 24/25 FPS in 1x1 mode, resolutions beyond this gives corrupted frames or camera lockups, because the sensor can't keep up.
Same goes for the 1x3 mode 1640x2156@24fps, giving 4920x2156 after stretching.
Readout speed is about 85 megapixel per second on the 6d.
2880x1200x25fps = 86400000 pixels per second (86MP).
1640x2156x24fps = 84860160 pixels per second.(85MP).

So it's a limitation of the hardware.


#4
Not sure, but my guess is that fps override doesn't work wel when crop_rec module is activated.
Probably it works good with crop_rec module set to off.
The crop_rec module in 6D uses fixed A&B timers for sensor readout. FPS override works by modifying A&B timers, but is overruled by crop_rec module if crop_rec module is enabled.
#5
The build is based on the same branch as the ML build on the download page on magiclantern.fm -> experiments -> 4K raw video recording; lossless compression

https://builds.magiclantern.fm/jenkins/job/crop_rec_4k/80/artifact/platform/6D.116/magiclantern-crop_rec_4k.2018Jul22.6D116.zip

That build contains a ettr module, see folder 'ML/modules/ettr.mo', you can copy the ettr.mo file to the build on your card in the same folder as the other modules, should work.

Haven't used the ettr module myself, so not sure how good it works, I'm using raw histogram and adjust exposure to that.
#6
Hi, tested on the 6d.
JPG only is 151MB + 3 x 35MB in photo mode, RAW only is 255MB + 4 x 35MB in photo mode.
But with RAW only, as soon as I activate live view either in photo or video mode, it's going to 151MB + 3 x 35MB.





Must say that I always had the camera in RAW photo mode only, didn't needed the jpg's.
#7
Camera-specific Development / Re: Canon EOS R5 / R6
June 13, 2022, 02:03:42 PM
@C_joerg
Interesting, so black level changes happen on more canon cameras.
Not sure if I understand the stuff discussed in the links you send.
So am I right that one theory is that the camera actually uses a lower iso then it actually reports ?
So in case of the Canon R5, which only has black levels of 512 in iso 100 and 200, you think it actually uses a lower iso/gain, like 25 or 12.5 ?
Iso/gain is the only thing they can use,  a faster shutter speed or smaller aperture would both be noticed by people I guess.

The 10 bit and 12 bit raw recording is possible on the 6d with raw video recording in magic lantern raw.
This was done by using a register that act as digital gain, it pushes the values recorded 2 or 4 stops lower.
Now I think about it, that makes sense that in this case the black level becomes lower in value.
Digital negative gain also lowers the noise signal, so this means lower black level  ???

What I also see discussed in the links you send, is that the image data is rescaled in the raw files in camera.
This is also the case with the R5, max white value is always at 16383 - black level.
This makes it difficult to see what is going on...

The whole iso magic is also happening with clog1, clog3, highlight tone priority etc.
Minimum iso that is possible in 8k raw:
No log -> iso 100
Highlight tone priority enabled -> iso 200
Log1  -> iso 400
Log3 -> iso 800

When actually using the above settings and iso, and load the files in raw digger, you can see in the noise level that it's all the same, it's all recorded in iso 100 :P


#8
For those interested:
Posted some comparison shots 6D to R5 and posted them in the R5 topic.

https://www.magiclantern.fm/forum/index.php?topic=24827.msg239189#msg239189
#9
Camera-specific Development / Re: Canon EOS R5 / R6
June 10, 2022, 08:34:09 PM
For those interested, some comparison of raw video against the 6d.
Was hard to do, not easy shooting the same scene and layering the footage and matching colors etc.  :P

8k raw of the R5 scaled to ultraHD matched to aspect ratio of the 3x1 mode of the 6d.
It starts with R5 footage and wipes to 6d footage (3x1 mode, 1832 x 1856 -> 5496 x 1856 resolution scaled to ultraHD)
The footage is very comparible, but R5 wins on detail, far more detail in the leaves.
And the R5 can shoot more usable aspect ratios of course  :P (R5 footage aspect ratio is matched to 6d 3x1 mode.).
https://drive.google.com/file/d/1c059wQoWCMJmlSClCrJ7aq2N7DgEv2r8/view?usp=sharing

Another comparison, here the 6d is used in crop mode 2880 x 1200.
The 6d footage is placed on the R5 footage which uses the whole frame.
So the frame somewhere in the middle is the 6d footage.
https://drive.google.com/file/d/1ktI5tKHdYd80gjpT6c5AdFYYRvTDsdVq/view?usp=sharing
#10
Camera-specific Development / Re: Canon EOS R5 / R6
June 10, 2022, 07:54:11 PM
What is also interesting, when shooting raw video in the raw lite codec, which has a compression ratio of 6:1instead of normal raw which has 4:1 compression ratio.
The max white value of both green channels become about 10780, not 15359. (16383(max 14 bit value) - 1024(black level) = 15359)
Both the red and blue channels still have 15359 as maximum white level.
So the extra compression is achieved with using lower values for green channels, which according to the measurements done with dark frames doesn't impact dynamic range.
Weird enough, there seems to be a slight advance in dynamic range when shooting raw lite instead of normal raw  ???.
Although this probably comes with a penalty of less fine detail, since the green channels seems to contain more noise reduction done already in camera, or the standard noise reduction kicks in more because of the lower values.
#11
Camera-specific Development / Re: Canon EOS R5 / R6
June 10, 2022, 07:44:37 PM
Wanted to know some more how the camera(Canon R5) behaves under different modes and different iso settings.
Shot some dark frames in different photo and video modes and loaded the into raw digger to calculate dynamic range based on noise.

Made a spreadsheet in google drive with some more info about the Canon R5:
https://docs.google.com/spreadsheets/d/1D3lpiMQniUzPiaVqDzAs5Gmc2hR9mIjDXpDe5IBTP9E/edit?usp=sharing

What suprises me are the different black levels.
In photo mode in iso 100 and iso 200 it's about 512.
While in all other iso modes it becomes 2048 (which is normal for most Canon camera's with digic 5 with ML support).
In raw video mode black level is 1024, all iso's also iso 100 and 200.

The Canon 6d always has black level in the 2048 range, unless when shooting 12 bit or 10 bit raw, then it becomes 512 and 256)
Does this mean that the Canon R5 is using 13 bit a/d conversion for video modes ? (would explain the black level shift from 2048 to 1024)
And what is going on with iso 100 and 200 in photo mode, the only modes where black level is 512, can't be because 12 bit a/d conversion I guess, dynamic range is highest at iso 100  ???

Furthermore, it seems that iso 200 can be best avoid(dynamic range wise), if 100 is not enough, you can go directly to iso 400  :P
Also, after iso 3200, every more stop of iso is a direct stop loss in dynamic range, so there is probably not much reason to shoot higher then iso 3200, since digital exposure push in post should give similar results.

So anyone has any idea what's going on with the different black levels, especially the black level of 512 with iso 100 and 200 in photo mode?
#12
In this case the after is worse.
The after has the vertical lines which have that Magic lantern high iso raw fingerprint  :P
Dark frame subtraction should solve the vertical line issues.

So if you haven't mistaken before and after...then it looks like your dark frame is not made with the same settings as the shot you extracted it from.

All settings must be equal, resolution settings in ML, iso setting and shutter time setting. Aperture shouldn't make a difference, I always close it as much as I can for dark frame creation.
It looks like your dark frame are recorded in different resolution or other iso setting.
#13
Grain noise looks very clean, almost like added film grain effect.

Just like Skinny told, upload one of the noisy MLV files (google drive or something else), or just one frame off them, then we can take a look at the original.
Can't tell much about a processed file.

Doesn't look like normal noise to me but something added in post in software  ???
#14
Glad you figured it out too  ;D
#15
No realtime correct framing liveview.
There is realtime liveview, but it is squeezed and zoomed in.
So to check framing, you need ML preview (the preview with slow refresh rate)
#16
Low light performance of the 6D is very good.
Although in this case I would worry if those 190000 are indeed real.
According to this site:
https://shuttercheck.app/data/canon/eos-6d/

There aren't that many that go beyond 190000 ??? But not sure how much data that is coming from.

180€ for a 6d is not much, but it can probably fail anytime if it really had 190000 shutter actuations, are you sure that number is real ?
#17
Camera-specific Development / Re: Canon EOS R5 / R6
April 14, 2022, 10:21:05 PM
Interesting, so most of the knowledge is based around hobby and not that much career/work related.

Grew up with the commodore 64 and amiga 500. But all we did back then was playing games   :P
No programming. Although later on I did a lot in microsoft quickbasic as a hobby. Even made a working tetris game in quickbasic.

With photography as a hobby( and Canon shooter) I found out about the Magic Lantern site in the 5d2 area. Read a lot on the forum. Later on when crop recording was introduced by alex I could help by changing the values in the already written crop_rec module.
Just changing numbers in the code and test it on camera, that's about as far as my programming knowledge goes  :P

Would be cool to dive some more into this, but not sure what knowledge would be most helpfull.
Maybe setup a working qemu build or better understanding about the Magic lantern source code  ???
#18
Camera-specific Development / Re: Canon EOS R5 / R6
April 14, 2022, 04:25:15 PM
Quote from: kitor on April 14, 2022, 08:59:19 AM
will be nice to have anyone of the "old guild" with deeper hardware understanding to have a look at D6/7/8 models (even if this means poking around ROMs and not real hardware). Unfortunately Alex is gone for almost a year now.

Always amazed me how far magic lantern has come with digic 5.
With the whole raw video development.
This whole thing about A timer, B timer, shutterblanking, capturing the raw stream and write it to sd.

I wonder how somebody can figure such things out, with reversed engineering. Alex must have broad knowledge about digital image capture.

What kind of people become good at reversed engineering, must be some work related thing. Or are there people out there who figure this out as hobby?
There must be some basic knowledge about firmware and product development I guess.

@Kitor, how did you learn how to get 'hello world' on various cameras?
Has the knowledge you need for that overlap with your work ?
#19
Good to hear it's working without corrupted frames  :)
I don't have the source online.
But I could upload it to my google drive.
It's mostly the crop_rec module where changes are made.

The steadycam footage looks good on youtube in 4k  8)

#20
Camera-specific Development / Re: Canon EOS R5 / R6
April 13, 2022, 08:32:00 PM
Quote from: kitor on April 12, 2022, 10:22:29 PM


Great, can't wait to have raw video on this camera  ;D

(Sorry for the stupid joke, had to make it  :P)

Curious if the R5/R6 still have the CMOS registers used for controlling iso.
Want to know which is the highest CMOS iso and from which point it's only amplified gain.
From tests I guess it's either iso 1600 or 3200 which is highest sensor iso.

And ofcourse if dual iso still exist, two separate iso settings.

#21
The numbered files belong to the MLV with the same name.
Your video file is recorded in chunks of 4GB size.
So it starts recording, and around 4GB it creates a new file with M00 extension, if that becomes 4GB in size, another file is created M01 etc.

MLV app automatically connects those numbered files to the MLV file.
#22
Quote from: Danne on April 08, 2022, 03:19:37 PM
"one more hack" caused freeze. Will investigate further.

The same with 6d, but it's not just a freeze. Trashcan button to enter ML menu is responsive.
In ML menu you can see that it's starting raw video, but it never starts  :P
Switching off the camera gives clean shutdown, so no ordinary freeze.
#23
Uncompressed DNG will always be bigger.
MLV's are recorded in 14 bit and the conversion to DNG goes in 16 bit (for compatibility reasons I guess :-\ )

So conversion from 14 bit MLV to 16 bit uncompressed DNG always comes with increase in filesize.

MLV to lossless DNG should become the same filesize or smaller.
It depends on the settings used with recording. (14 bit normal or 14 bit lossless option) the lossless MLV optiom became available in later magic lantern builds.

So my guess is that most of your MLV's are not lossless compression recorded.
This means you should end up with smaller filesizes if you choose lossless DNG option.
If your MLV's are lossless compressed, you end up with roughly same filesize, since the compression technique is the same.
#24
It also works for 6d, Bilal made and update of MLV_lite module, thanks Bilal :)

For those that wants to test on 6d, here's the link to the MLV_lite module file, replace it with the one on your card:
https://drive.google.com/file/d/1trrpR00vqtJh2SC-HpTfG43rS8tUCAZc/view?usp=sharing

The "more hacks" function works, use lvface + aewb setting for best results.
The "One more hack" function doesn't work on 6d for now, recording doesn't start with this enabled  ???

Improvement ~6MB/s
Without I get about ~86MB/s write speed
With more hacks enabled I get ~92MB/s write speeds  8)
#25
When you think there is nothing more to gain...amazing  8)
Although I miss a particular camera in that list  :P
Would love to try this on the 6d.

Are you able to add the 6d in too, or do you need some info ?