Messages

Thank you for your swift reply, Bilal.

I didn't know somebody else asked for this function, but at the same time I'm not surprised.
Maybe someday you'll manage a solution, who knows? In the mean time, thank you for everything, and I hope everything's going well with you.

Hi again Bilal Fakhouri!

Is it somehow possible to shoot at 30 fps in the UHD 1x3, 4K 1x3 or 4.3K 1x3 modes?
Or if I set some values manually, can the 700D with all the speed hacks actually achieve this?

Hi Bilal!

Thanks for the fixed interference between ML menu and Canon overlays in LiveView. At times it could be very annoying.
Keep up the good work!

Hi there!

I can buy a Canon 6D with 190.000 actuations for €180. I know the MTBF is 150.000. Is this a good deal?
Right now I have a Canon 700D with the kit lens, the 10-18 IS STM and a EF 35mm F/2 (the non stabilized version). I was planning to use the 35 with the 6D; I am a father of a small child, and low light performance is critical Besides, I believe a 35mm lens on a full frame body would allow my shots to breathe.

All opinions are welcome!

[Thank you!]

Looks like it fixed the issue. I was able to record this ~1 minute example at 5496/3x1944 @ 24 FPS : https://www.youtube.com/watch?v=ePmpH5QNuGU
Thank you! I'm very happy, going to post more tests with steadicam soon.
By the way, do you have a repository at GitHub or other Git hosting where it's possible to see the edits you made to the source code?

UPD: Another quick test, now with steadicam: https://youtu.be/Lrc_npKrWaQ

Is the steadycam a real steadycam or a stabilized lens? Looks amazing, by the way!

P.S.: I can buy a 6D with 190.000 actuations for €180 euros. I know the MTBF is 150.000. What do you think about this? Should I go for it? Right now I have the EF 35mm f/2 (the non stabilized version).

What do you mean by "real"?  1280*2160 should have all the light from 3840*2160 because it's binned, and at least as good resolution for detail as 1280*2160 (probably, slightly better angular resolution?  Binning loses you some but you don't need as good a lens etc to have the resolution available over the 3 pixels as you would over 1?).  If you downsample to below 2160 height, you are throwing away resolution.  The *vertical* resolution really is 2x 1080.

So, it should definitely be better than 1920x1080 resolution overall.  That's 2.1MP.  1280*2160 is 2.7MP.  But they're a little odd to compare.  The horizontal and vertical angular resolution aren't the same in 1x3 binned, but the native 1920x1080 is binned anyway and compressed so what are you comparing against?  1920x1080 raw from some different camera?

Yes, that's it, I'm trying to compare it against 1920x1080 raw from a different camera. If the vertical resolution is really 2x1080, what happens to the horizontal resolution? Are the 1280 pixels "stretched", i.e. interpolated, if we want to maintain the 2160 vertical dimension and 16:9 ratio? Sorry if my question is dumb, I understand this involves a lot of math.

Hi Bilal!

Yes, I can believe it's hard, if not impossible to reach to a number.
However, in your opinion, do you believe it's equivalent to 1920x1080, or a lower resolution?

This is beyond awesome! Definitely Black Magic Lantern
I fully trust in your builds, and I've never had any problem. I assume that's also the case with this one

Thanks ML700D!

Indeed IDA_ML, it's amazing the quality the developers achieved with the 1x3 high-resolution modes with so ancient cameras...

You are downscaling instead of upscaling, this result in less details and resolution, this way you are getting oversampled 1280x720. Instead of dividing 2160 by 3, multiply 1280 by 3 which result in 3840x2160 1x3 image which has more details compared to 1280x720 (of course it's not true 3840x2160, also it's not 1280x720, it's actually in-between these resolutions. I call it myself Hybrid-1080p).

MLVApp upscale 1x3 footage by default by multiplying horizontal resolution by 3. Transformation tab set to "0.33" when importing 1x3 footage.

Thanks, I didn't know that! I filmed a bottle of water with very fine details in the mode UHD 1x3 - 1280x2160. Then, in MLV App I extracted a frame at 1280x720 and another at 3840x2160. Afterwards, I downscaled the 3840x2160 to 1920x1080 and upscaled the 1280x720 one to 1920x1080, as you can see:



I did the same process again, only this time downscaling the 3840x2160 to 2560x1440:



To my eyes, there's definitely an improvement in the first case. The fine details in the paper, especially the green stripes, are visible when downscaling to 1920x1080, being invisible when the image is exported at 1280x720. You said the 1280x720 would have less detail but would be cleaner, as it can be seen. However, I think is worth it to uspcale and denoise it; the software that I use (RG Magic Bullet) can clean the noise and maintain the vast majority of the detail.

When downscaling to 2560x1440 I don't think there's extra information in relation to 1920x1080. What do you think is the "real" resolution when exporting the footage at 3840x2160?


Relative to the second question, your step-by-step guide helped me get rid of the corrupted stripe, thanks!

Thanks Bilal, for your very thourough answer!

You're right, the 1x3 presets have ~2.7 Megapixel; however, since the vertical resolution must be squezzed to a third, the final resolution results in 1 Megapixel. 1280x2160 (using your example) gives us a final result of 1280x720 = 921600 pixels, since 2160 must be divided by 3, correct?

I tried the 1600x2040 2.35:1 AR 1.74 crop factor @ 23.976 FPS in 1x3 and used the EDMACs hack. When I was recording I had live preview, but it was distorted (stretched vertically). Is this what I should expect?

This results in a very good quality footage; however, in the MLV App a horizontal stripe artifact showed at the bottom of the image. Do you have any idea why did this happen?

Bottom artifact:

Hi Bilal!

I've been watching some videos from Zeek, and I found this one quite interesting: https://www.youtube.com/watch?v=D3QbsVYgCrc&t=927s&ab_channel=Zeek.
In minute 2:16, it says that the EOS M 2.5K RAW mode is ~3.2x Crop. This poses some questions:

- Does this mean that it has double the magnification of the normal 1.6 crop from Canon, i.e., does it use half the sensor area? If that's so, maybe it's not the preferred method when filming in low light, as it gathers less light, am I right?

- Is 2.5K Expanded Preview similar to EOS M 2.5K RAW mode?

- What's the setting that allows to record with the most resolution possible, with no moiré, small crop factor and real-time preview? 4.5K 1x3, 4.3K 1x3, 4K 1x3 and UHD 1.3 all offer about 1 megapixel of resolution. Is there something I can do to increase it to 1,5 or even 2 megapixel resolution? I am already using the SD hack at 240Mhz.

@theBilalFakhouri

Thanks for your fast and thorough explanation!

@theBilalFakjouri

Hi there!

I noticed in your last post that you mentioned:" Results:

1-2560x1440 @ 23.976 FPS in 10-bit lossless, 240 MHz, same scene, mlv_snd on, global draw off, real-time preview, required write speed reported by mlv_lite 70.8 MB/s:
-Without EDMACs hack: 14-15 seconds recorded, write speed reported while recording ~69 MB/s
-With EDMACs hack: 38-45 seconds recorded, write speed reported while recording ~72.4 MB/s"

Does this mean I can record real 2560x1440 resolution in 1x3 mode (no aliasing) with real-time preview with my Canon 700D with a Sandisk Extreme 64GB 170MB/s overclocked to 240MHz? That's great news!
If that's so, what are the modules I have to activate/change?

Does the real-time preview show the scene as it is or cropped?

Hello @lightwriter

Sorry for the delay:

Your 700D have different shutter blanking addresses, resulting in wrong shutter speeds when using my build, the problem isn't from the build itself, on my 700D it works just fine because the addresses used in my build matches the addresses which my 700D generate, let's say for now some 700D models are different from other 700D models, and your 700D need other shutter blanking addresses.

a1ex did explain this case earlier and I did mention it before, current temporary solution is to release two builds which include the two addresses, or find a way to add them in one build.
I may do it in near future.

During my tests, SD overclocking isn't related to corrupted frames in any way.

Please provide a frame or short MLV clip which have corrupted frames your are experiencing, probably you are using "Crop mode V2" which is a bit buggy right now, and always make sure you are refreshing LiveView manually by pressing Menu button twice (I have explained this before).

You may want to stick with "Crop mode" (crop_rec) for now which works better.

Hi @theBilalFakhouri!

Sorry for only now replying to your answer.

Thanks for the explanation of the first point; I was going a little nuts, trying to figure out what I was doing wrong.

Regarding the corrupted frames, I exposed this situation to a guy in youtube: https://www.youtube.com/channel/UCA1OBB0Z2EERvT5hHiXLTmw, and he told me to disable Global Draw. That did work flawlessly; however, has it was to be expected, disabling Global Draw stops me from seeing important information like zebras and the histogram...

Oh, and congratulations for the soon to be released build. Seems you added some very welcome additions!

@lightwriter

Hi again!

1- This corruption due to un-refreshed LiveView, to prevent this:
Also when you startup the camera and if crop_new was already ON you need to refresh LiveView manually!

2- In mlv_lite submenu --> Preview --> Framing

3- Yeah, that's what I am using

4- ?

MLVApp corrects aspect ratio automatically for you, you don't need to change anything regarding resolution. The output would be correct.

5- EOS M has some problems with 240 MHz overclock it doesn't work fine on this camera even with 170 MB/s Sandisk Extreme PRO cards (except one card: Sandisk Extreme PRO 170MB/s with 512 GB Capacity) , doing a "Low Level Format" would fix the speed drop issue e.g: from 66.7 MB/s to 51.8 MB/s -- these things have been discussed before in this topic.

6- This issue has been discussed here

Hi @theBilalFajhouri!

Thanks for your answer. Regarding number four you're right, the MLVapp corrects the aspect ratio; I only have to insert the resolution values for exporting.

I have read the answers related to number 6, but there you said "shutter speeds are working fine in all presets, and both from ML and Canon menu shutter speed is showing correctly " My build is crop_rec_4k.2020Sep30.700D115. Is this problem related to this specific build or am I doing something wrong?

I bought the Sandisk Extreme PRO 170MB/s card, and it indeed allows me to record indefinitely (almost always), but I'm having corrupted frames (random frames with the bottom half being pink). Is there some setting I can alter to prevent this from happening?

Hello again @theBilalFakhouri!

Thank you so much for your detailed and easy to follow answer.

I ran the benchmark in play mode and you were right; I'm getting read speeds of 85.6MB/s and write speeds of 79.6MB/s.

Most of my clips over around 10-14 seconds; however, I managed to record one clip with approximately 1 minute of duration. I don't know how this happened, but it was the exception.

1 - I recorded 5 clips - two of the shorter ones don't have any problem; the other two short ones have a lower horizontal stripe corrupted (around 80-100 pixels height, perhaps?), and the longer clip was fine. What can I do to prevent the horizontal corrupted band? Here is one example of a corrupted frame: https://imgur.com/BLhAOr3 - all these clips were recorded at 192MHz overclock.

2 - You talked about using ML Framing to check framing. I've searched the options but I can't find it...could you point me to the right direction?

3 - The Sandisk Extreme PRO 170MB/s card you talked about is this one, right?: https://www.amazon.es/SanDisk-Extreme-Pro-Tarjeta-Memoria/dp/B07H9J1YXN/ref=sr_1_1?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=Sandisk+Extreme+PRO+170+MB%2Fs+64&qid=1607862081&quartzVehicle=74-902&replacementKeywords=sandisk+extreme+pro+mb%2Fs+64&sr=8-1

4 - In MLVapp, in order to export with the correct aspect ratio, I inserted the values of 2400 by 1020 - this method works, but is it the best one?

5 -  Several users posted images of benchmarks with the 170MB/s card, 240Mhz. One user showed the first write speed being high - 66.7MB/s, but the second one reaching only 51.8MB/s. This happened with a EOS M, in movie mode. Are those values normal? https://www.magiclantern.fm/forum/index.php?topic=12862.625 - bottom of the page.
In this video: https://www.youtube.com/watch?v=tm1pFNRIlcI&feature=emb_logo&ab_channel=Zeek., by the 2.14 minutes mark, with an EOS M, using a 64GB 170MB/s card the results were as follow: write speed: 20.4MB/s

6 - In normal situations, the shutter speed appears as N/A (I can change the shutter speed but I can't see the value), even if in Crop mode V2 I activate Full range in Shutter range. If, in the Movie tab, I select FPS override, then it shows a value of 0,4'', but I can't change it. What's the solution?

Thanks again for your help!

Hello @theBilalFakhouri

Thank you very much for your detailed answer!
Unfortunately, I followed all your steps but it stops recording the instant I begin, and the frames are corrupted.

In RAW video I selected 1600, but when I go to Crop mode V2, I didn't change X resolution, but it says 1736. What bit depth should I select in Crop Mode V2? Or should it be off? And in RAW video, I chose 12 bit lossless; is this the way to go?

At the bottom, it says in yellow that it will record at 64MB/s, 0x5.4MB, 23.982 (49%). Expect around 0 frames at 56.3MB/s.

Pressing Menu button twice, the resolution of Crop mode V2 shows 1736x2040 1x3, RAW video shows 1600x2040 1.74x and SD Overclock is at 192MHz

I did low level format in the original canon menu when formatting.

What am I doing wrong? Sorry for the trouble.

P.S.: Would the Sandisk Extreme Pro 170MB/s V30 be a better choice by allowing 240MHz?

P.P.S.: In Benchmark, with SD Overclock at 192MHz I'm getting write speeds of about 54 MB/s...it's on the low side, no?

@theBilalFakhouri

Hi there!

I have a Canon 700D and a SanDisk Extreme Pro 95MB/s SDHC V30 speed class U3 32GB. Is SD Overclock at 192Mhz stable with this card?

You referred the 1x3 Mode which can be used with this configuration: 1600x2040 @ 23.976 FPS 2.35:1 AR. How can it have a 2.35 aspect ratio with  a resolution of 1600x2040? Does it have to edited in MLV app to get the correct aspect ratio?

Does the 1x3 Mode get rid of the aliasing?

Hi there!

I have a 700D, and installed the 4K raw video recording; lossless compression experiment. I have some questions:

- If I choose Movie crop mode (600D movie crop-mode), my maximum resolution is 1800x1012 with 4.66 crop; choosing centered 5x zoom mode I am able to get 2000x852 2.35:1 for about 20 seconds. Both modes avoid aliasing, correct?

-I have the 10-18mm STM, so this means I have the equivalent of 10x4,66=46,6mm in the first case, is this right?

- When I choose either of the crop modes do I lose light gathering capability? i.e., since I'm recording from a smaller portion of the sensor, does this mean I'll have more noise?

- When I choose the 5x zoom mode and I override the slow correct framing with the half-shutter, and I try to change my shutter speed the Canon menu appears and show 1/80 of a second, for example, while the ML menu shows at the same time 1/49 of the second. Is this normal? It's the ML reading I should trust, right?

Thank you for your attention!

[How to use 1x3 Binning:]

New build for 700D:
https://drive.google.com/open?id=1qnhTArl_DsfyHaLLfQJDPbLD85OBtMxB

-White Level is correct for Analog gain (thanks Danne)
-Now once you load sd_uhs it will patch during start up, no need for script and enabling it manually (thanks Danne)
-There is no 11-bit lossless , it will start from 10-bit lossless to 8-bit lossless depending on ISO (I removed 11-bit lossless to enhance recording time in ISOs 100-800)
-Included Dual ISO fix for ISOless 8 & 15
-Shutter flickering has been fixed (Thanks a1ex)
-Removed Crosshair in crop_rec
Note: Once you enable crop_rec and change Y or X resolution the actual bit-depth Will be 10-bit lossless , there is no 14-bit lossless (You should always select 14-bit lossless from mlv_lite if you want to use crop_rec in this build , and the final bit-depth will be 10-bit lossless , I did this to enhance recording times and I couldn't figure out how to chose between 14-bit to 12-bit lossless when using crop_rec) and once you disable crop_rec you can use the bit-depths from mlv_lite normally .

How to use 1x3 Binning:
Load crop_rec and restart the camera, activate crop_rec , go to crop_rec submenu by pressing Q button , chose 1x3 Binning , press Menu button to refresh LiveView , That's it! --> To increase the Vertical resolution Just change Y resolution to 2214 (Sweet Spot) and refresh LiveView by pressing Menu button and getting back to LiveView.

Note 2: When you do any change in crop_rec you Must/Should/Have to refresh the LiveView manually ! How? by pressing Menu Button and going back to LiveView otherwise your settings will not be applied , if the settings were saved and crop_rec was activated and you turn on the camera You should also make a refresh .

Hi there!

I'm a newbie regarding Magic Lantern...I have installed the Canon build for the Canon 700D around the 13th of August from the official page. How can I install the build you shared?