Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Raw Video / Re: AI algorithms for debinning
« Last post by mlrocks on July 21, 2021, 10:25:27 PM »
I just did a test on 5D3 in the following modes: 1x1 UHD, and 1x3 anamorphic UHD. All in 10-bit color depth, 14-bit lossless compression. Aspect ratio was set to 3 to make 1x1 UHD continuous. The scene was composed of side trees with dense green leaves, an apartment gate, a parking lot with cars. The focus length of the lens was about 28mm. I used MLV App to process the raw into prores 4444. The footage was viewed in Potplayer on my computer screen of 27 inch 1920x1080 in full screen mode. I can see that the details of leaves are noticeably better in 1x1 UHD mode than in 1x3 anamorphic UHD mode. For the apartment gate and the park lot and the cars, the difference is not noticeable.
I have a little concern here with this experiment. The 1x3 anamorphic UHD is not an independent mode on 5D3. It is in the anamorphic mode, but can choose the horizontal resolution of 1280. Not sure if this UHD submode is optimized enough. I tested on 650D anamorphic UHD which is an independent mode and the results for the same scene (different dates, maybe different time of the day) showed that tree leaves were pretty sharp. I will do more controlled tests on this aspect.
Right now, probably IDA_ML's experiment is more convincing. Hopefully others can do more tests on 1x1 versus 1x3 modes using different approaches, such as similar experiments on an Apple 5K Retina monitor, etc, so that the conclusion will be more solid.
72
Raw Video / Re: AI algorithms for debinning
« Last post by mlrocks on July 21, 2021, 10:12:30 PM »
I'll try to answer all the MLVApp questions...Don't use the MLVApp sharpen sliders for anamorphic footage. Stretching is done after sharpening, so you'll get bad lines. Better sharpen after the export in your NLE. By default, MLVApp doesn't sharpen at all.
You can't undo binning. You can just use better and worse algorithms for unsqueezing: most applications use bilinear or bicubic for this job. MLVApp uses AVIR, which brings better stretching results.
The results should be the same between photo and video mode. And if you use the same applications for processing, you'll notice that. MLVApp brings very similar results to Adobe ACR - just ACR has a denoiser enabled by default (switch it off and it looks mostly identical). When using defaults, processing video in MLVApp and photo in ACR, you'll thing photo is better - but it isn't.

Thank you very much for the instructions on MLV App, masc. It is very nice to know these tips.
73
Raw Video / Re: AI algorithms for debinning
« Last post by masc on July 21, 2021, 09:44:13 PM »
I'll try to answer all the MLVApp questions...
In MLV App latest version, if a low contrast lens is used and sky is overcast, I use 81 contrast, 81 clarity (microcontrast), 81 chroma separation- sharpening.
I wonder if it has something do do with the order of operations, such that MLV App is sharpening before stretching, but if ILA_ML is getting good results (and given that ilia knows what he's doing), that seems unlikely.
Do you happen to know what MLV App uses by default?
Don't use the MLVApp sharpen sliders for anamorphic footage. Stretching is done after sharpening, so you'll get bad lines. Better sharpen after the export in your NLE. By default, MLVApp doesn't sharpen at all.

If MLV App has a transformation/debinning algorithm to reverse engineer the Canon binning process, or has an AI algorithm to guess right the original 3 pixels from this fat pixel, then the anamorphic UHD will be very close to the native UHD.
You can't undo binning. You can just use better and worse algorithms for unsqueezing: most applications use bilinear or bicubic for this job. MLVApp uses AVIR, which brings better stretching results.

I once accidentally underexposed my footage, after elevated the exposure in MLV App for about 3 stops, the noise made the footage not usable. Yet 5D3's low light performance is pretty good in photo mode.
The results should be the same between photo and video mode. And if you use the same applications for processing, you'll notice that. MLVApp brings very similar results to Adobe ACR - just ACR has a denoiser enabled by default (switch it off and it looks mostly identical). When using defaults, processing video in MLVApp and photo in ACR, you'll thing photo is better - but it isn't.
74
Hi @Icaab

You can already do time-lapses with crop_new (Crop mode V2) which works greatly, do you have any issue with it?


Let's fix the shutter issue on your camera, assuming you have my crop_rec_4k build on your SD card:

1- Download adtg_gui module from here
2- Put it in ML/modules folder in SD card
3- Load "adtg_gui.mo" from "Modules" tab in ML settings, restart the camera
4- From "Debug" tab in ML settings, turn ON "ADTG Registers"
5- Highlight "ADTG Registers" then Press Q button

Now you should see bunch of ADTG2[XXXX] registers, you need to find two registers which are:

1-ADTG2[805F] N
2-ADTG2[8061] N

Highlight the first register and give me these numbers in the yellow box (write them down, or take a picture with your smartphone)


Do the same thing for the second register, and give me the numbers
75
As far as I know mlv_lite has basic metadata which explains why there is no real-time focal length info . . I think it could be implemented into mlv_lite (updating focal length info per frame), personally I don't have an experience with metadata so can't help much here . .

BTW you can use uncompressed 10/12 bit-depth using mlv_rec which requires lower write speed than uncompressed 14-bit, you can find a build here:
https://builds.magiclantern.fm/experiments.html

Under:
"10/12-bit RAW video" or "4K raw video recording; lossless compression"
76
Share Your Videos / Re: 5D Mark 3 Magic Lantern Official Music Video
« Last post by huyct666 on July 21, 2021, 07:48:05 PM »
hi i use the experimental 10bit 12bit use for 5d3 113

lenses used:

canon ef 35 1.4L
canon ef 24 1.4L II
canon ef 50 1.2L
canon ef 85 1.2L

soviet mir1v 37 2.8
soviet helios 44-2 f2
soviet mir 47 20mm f2.5

thánks for watching
77
Raw Video / Re: AI algorithms for debinning
« Last post by Jonneh on July 21, 2021, 05:06:37 PM »
We use PLAY mode for running cards benchmarks since in this mode there is no overhead happening by anything, so this mode gives us the highest CF/SD card controller speed.

Gotcha---good to know!
78
Raw Video / Re: AI algorithms for debinning
« Last post by theBilalFakhouri on July 21, 2021, 04:17:40 PM »
..
Btw, the maximum writespeed on the 5D Mark III is not 135mb/s. The edge is somewhere else.
In my Tests I got 138mb/s and I wrote this in the Forum here.
..

But later I reached 139mb/s, but never more.
...

Yeah, never said it's exactly 135 MB/s . . I always added the approx sign before the numbers "~135 MB/s" . . at some point I also got ~138 MB/s write speed, let's say it's around these numbers ~135 MB/s to ~139 MB/s write speed using card spanning (23.976 FPS)


I'm sure I'm missing something obvious here, but what is PLAY mode? As I know it, it's just for playback, and no writing occurs there.

We use PLAY mode for running cards benchmarks since in this mode there is no overhead happening by anything, so this mode gives us the highest CF/SD card controller speed.
79
Raw Video / Re: AI algorithms for debinning
« Last post by Jonneh on July 21, 2021, 01:47:00 PM »
In order to increase vertical resolution you need to increase FPS Timer B (increasing FPS Timer B decreases FPS) , I could do 1920x3072 1x3 @ ~20 FPS, but not in 24 FPS, in this case we need to lower FPS Timer B to get 24 FPS in 1920x3072 in 1x3 mode, but doing that broke the image and might freeze the camera . . it's weird because we didn't hit read out speed limit yet . . there are other *head* timers are related to FPS Timers, tweaking it are not enough . . maybe there are other registers needed to tweak . .


Fascinating how byzantine the gears and levers are that need to be moved to get a desired result. Proper detective work!

In LiveView the camera uses more memory cycles resulting in lower write speeds, lowering framerate from "FPS override" helps .

In my previous tests, maximum write speed with card spanning in PLAY mode is ~155 MB/s (5D3.123) using 160 MHz, 192 MHz and 240 MHz overclock presets, in LiveView the write speed decreases a bit due to more memory cycles are used which became ~135 MB/s write speed when the framerate @ 24 FPS . .

~155 MB/s write speed limit in PLAY mode is coming from the memory (RAM), so I think it's a memory speed limit here . . bypassing this memory speed limit somehow may increase card-spanning write speed in theory . .

I see---that makes things clearer. So the 155MB/s is a RAM bottleneck and the 135MB/s (or 139, per Bender's current record) is the same minus the LiveView overhead. I'm sure I'm missing something obvious here, but what is PLAY mode? As I know it, it's just for playback, and no writing occurs there.
80
Bilal, hey.
Tell me: Is there such a opportunity that in the future in the firmware 650d/700d it will be possible to shoot timelapse with video so that all settings are flexibly adjusted ( shutter speed, for example) as on EOS M?
Pages: 1 ... 6 7 [8] 9 10