Magic Lantern Forum

**Download links in the End of the post**
    This new OP created in 24-5-2021

My custom builds are splitted now from the official 650D/700D threads, now we can focus the discussion on my builds, I will share future updates and tutorials frequently in this thread.


Once upon a time, Trammell Hudson (https://trmm.net/Magic_Lantern_firmware/) said:
"if it breaks your camera, you get to keep both pieces". Nothing changed, same applies here and in every build you are using :D

Q&A:
-Why would you use my builds?
It's included features might be useful or interesting to you, read below.

-Why wouldn't you use my builds?
These builds include bleeding-edge developments, it might break your camera, Don't use it if you are afraid!. However, to some point I know what I am doing, I only use my builds on my camera, never bricked it, some users used my builds too without resulting in a broken camera, the stats look good, Relax.

Features:
-SD Overclocking module with selectable presets 160MHz, 192MHz and 240MHz.
-High resolutions pre-made presets (crop_rec) 1920x1280p/1440p/3K 1:1, 4.5K/4.3K/4K/UHD 1x3 and more (Including preview fixes (https://www.magiclantern.fm/forum/index.php?topic=19300.msg229705#msg229705), correct (https://www.magiclantern.fm/forum/index.php?topic=25323.msg230688#msg230688) framing (https://www.magiclantern.fm/forum/index.php?topic=25323.msg230933#msg230933) real-time (https://www.magiclantern.fm/forum/index.php?topic=25323.msg231048#msg231048) previews in 1x3 modes)
-Magic Zoom V2 (LiveView zoom in to check focus while recording!) for some (crop_rec) presets.
-Changeable resolutions, framerates and binning modes module via (crop_new), you can get Full-Resolution LiveView 5208x3472 continuous in 10-bit lossless @ 5 FPS!
-ISOless 8 & 15 Dual ISO fix (https://www.magiclantern.fm/forum/index.php?topic=7139.msg197139#msg197139) for some 700D users.
-You can use lower bit-depths in lossless compression when shooting in high resolutions.
-Shutter speed is correct when using any preset, or FPS override.

-Enhanced experience for 1x3 Binning modes (Disabled Canon GUI, ML top bar would go to bottom automatically for better preview)
-Bit-depth is showing in ML bottom bar when using Crop mode.

[gifv]https://i.imgur.com/qbuxkiG.mp4[/gifv]





General notes:
-You can load both crop_rec and crop_new modules, but don't activate them at the same time (use "Crop mode" or "Crop mode V2").
-Use maximum aspect ratio and and resolution from mlv_lite when using crop_rec presets with real-time correct preview, otherwise mlv_lite won't crop the RAW data correctly.

-Loading the modules
After installing the build, some modules should be loaded manually for once to be able to record RAW video, use crop modes, view recorded RAW clips . .
I recommend to load the following modules to get the best out of my builds:

(https://i.ibb.co/sgjYCQn/Modules.png)

crop_new: Second version of crop mode (read below).
crop_rec: First version of crop mode (read below).
dual_iso: Dynamic range improvement (read about it here (https://www.magiclantern.fm/forum/index.php?topic=7139.0)).
mlv_lite:  Records RAW video.
mlv_play: RAW video (MLV) player.
mlv_snd: Adds sound recording to RAW video.
sd_uhs: Does SD overlocking which increase write speed (continue reading).

-Load these modules from "Modules" tab from ML settings, highlight a module and press SET button for each module, then restart the camera.
-Loading other modules is fine if you need them.

-SD Overclocking
We can bypass SD Controllers write/read speed limits using sd_uhs module:

-Select a preset (160, 192 or 240 MHz) then restart the camera.
-The highest preset 240 MHz gives ~ 68 MB/s write speed (https://www.magiclantern.fm/forum/index.php?topic=12862.msg228673#msg228673) in video mode, and 240 MHz preset is stable when using Sandisk Extreme Pro 170MB/s Card (https://www.magiclantern.fm/forum/index.php?topic=12862.msg228673#msg228673).

(https://i.ibb.co/WWPYcJL/Menu1.png) (https://i.ibb.co/HGbT2FD/Menu2.png)

-Best compatible SD card is Sandisk Extreme PRO UHS-I U3 170 MB/s (works in all presets, stable at 240 MHz).
Second-best is Sandisk Extreme PRO UHS-I U3 95 MB/s (works well in 160 MHz and 192 MHz presets)

-Perform "Low level format" in camera to get stable write speeds (at least for once), image on the left before low level format, image on the right after performing low level format; stable as hell:

(https://i.imgur.com/V1t8kKE.jpg) (https://i.imgur.com/H4KeIhc.jpg)


-Crop mode (crop_rec) with Pre-Made Presets
(https://i.ibb.co/n15HFWH/Presets.png) (https://i.ibb.co/h1L61ZW/crop-rec-submenu.png)

1- 2.5K Expanded Preview: Experimental Real-Time Correct Framing Preview in default x5 Mode.
2- 1440p 1:1: 2560x1440 16:9 @ 23.976 or 25 FPS with Fixed Cropped Preview.
3- 3K 1:1: 3072x1308 2.35:1 @ 23.976 FPS with Fixed Cropped Preview.
4- 4.5K 1x3: 1x3 Binning 1504x1782 with 1.86 Crop factor ~2.50:1 @ 23.976 or 25 FPS with Correct (Un-Stretched) Preview.
5- 4.3K 1x3: 1x3 Binning 1440x1836 with 1.94 Crop factor 2.35:1 AR with Correct (Un-Stretched) Preview.
6- 4K 1x3: 1x3 Binning 1360x1976 with 2.05 Crop factor ~2:1 @ 23.976 FPS or 25 with Correct (Un-Stretched) Preview.
7- UHD 1x3: 1x3 Binning 1280x2160 with 2.18 Crop factor 16:9 @ 23.976 or 25 FPS with Correct (Un-Stretched) Preview.
8- 1920x1280p 1:1: 1:1 1920x1280p @ 23.976 or 25 FPS with Correct Preview.
9- Full-Res LV 1:1: 1:1 Full-Resolution LiveView 5208x3478 @ 2 FPS.
10- 720p50 3x3: 3x3 Binning in 720p (square pixels in RAW) 1736x698 @ 50 FPS with Correct (Un-Stretched) Preview.

-You can easily check focus by pressing Half-Shutter in LiveView while not recording (works in all 1x3 presets and 1920x1280p 1:1 preset) to get into x10 mode, unpress Half-Shutter to get back to normal LiveView.

[gifv]https://i.imgur.com/augUIo8.mp4[/gifv]


Crop mode submenu settings:
-Shutter range: Full range allows you to get the lowest shutter speed and highest shutter speed possible with camera Hardware, e.g: down to 1/24 shutter speed, up to 1/36K shutter speed @ 23.976 FPS.
-Bit-Depth: This allows you to get 10/12 Bit-Depths with higher resolutions presets:
Always select 14-bit lossless from mlv_lite, select 10-bit or 12-bit from crop_rec submenu.

-Set FPS: Change the framerate for some presets to 25 FPS instead of 23.976 FPS (works in all 1x3 presets, 1920x1280p 1:1 and 1440p 1:1).

-Magic Zoom V2
-3K and 1440p presets aren't supported, you can use regular x10 mode.
-I had corrupted frames when using Magic Zoom V2 with *HDMI monitor, don't use Magic Zoom V2 with HDMI monitor attached while recording.
*However attaching HDMI monitors isn't recommended in general for these small cameras; it cause problems even with official builds.

-4K and UHD 1x3 Presets do have Magic Zoom V2, but with not perfectly centered preview or stretched zoomed preview, but it's valid for focusing.

Features:
-Nail your focus While recording!
-Works with All presets with real-time correct framing preview.
-You can trigger it by Zoom button or SET button.
-No overhead or slowness, didn't have corrupted frames during my tests (on camera LCD screen).
-Real-Time as Canon Preview, it's a Canon preview actually, but zoomed.
-Works with Global Draw OFF.

[gifv]https://i.imgur.com/H81QemC.mp4[/gifv]


-Crop mode V2 module (crop_new) with Arbitrary Resolutions:
Instead of pre-made presets, this is the new version of crop_rec from a1ex (https://www.magiclantern.fm/forum/index.php?topic=19300.msg205546#msg205546), which allow you to select any preferred resolution, framerate and binning mode.

-How to use it?

Select "Pixel binning" mode, set your X resolution and Y resolution, set your desired Framerate option, Press SET button in LiveView to apply the settings.

(https://i.ibb.co/bgMffL4/crop-new-submenu.png) (https://i.ibb.co/6sMbXmm/Pixel-binning.png) (https://i.ibb.co/tcKPGvB/Frame-rate.png)

-Using 10/12 Bit-Depths in crop_new:
Always select 14-bit lossless from mlv_lite, and use 10/12 Bit-Depths option from crop_new submenu.

-Refresh LiveView manually after changing the settings by pressing SET Button in LiveView.

-Shutter range: Full range allows you to get the lowest shutter speed and highest shutter speed possible with camera Hardware (360° to 1°), e.g: down to 1/24 shutter speed, up to 1/36K shutter speed @ 23.976 FPS, or
in low framerate presets e.g @ 2 FPS loweset shutter speed would be 0.5", 360° and highest shutter speed 1/12K, 0°

-Fix Preview: Fix pinkish preview in x5 Mode, max X resolution should be 3112.

-x10 Mode will be valid for focusing, and won't be patched.
-This module doesn't include any recent preview fixes.

-Using HDMI:
-Connecting HDMI works, in general there is an overhead when using HDMI with 1080i output you may have corrupted frames especially in high resolutions like x5 mode/1440p/3K 1:1, but using HDMI in 720x480 output doesn't seem to make an overhead (it just act like camera LCD)

-The following crop_rec presets will only work with 1080i output! and with Full Canon preview (toggle between Small and Full preview by pressing Info button in LiveView):
  • All 1x3 presets which has real-time correct preview which are 4.5K/4.3K/4K/UHD in addition to "2.5K Expanded Preview"
  • "720p50 3x3" preset may not work with HDMI, didn't test it.

-I didn't have corrupted frames with 1x3 (real-time correct preview) presets and HDMI 1080i output, don't use Magic Zoom V2 while recording it will produce corrupted frames between the switch (Normal/ZOOM preview).

-Write speed improvement:
-You can get ~13 MB/s write speed increase when using the new hacks, total write speed in LiveView is 82.8 MB/s!, more info in this thread: LiveView hacks (write speed improvement) (https://www.magiclantern.fm/forum/index.php?topic=26443.msg238349#msg238349).
(https://i.ibb.co/gPPNVgJ/April-1st.jpg)


-Looking for more recording times?

-Check Image quality and its effect on memory (more RAM 4 free) (https://www.magiclantern.fm/forum/index.php?topic=26521.msg239231#msg239231).

Quote from: theBilalFakhouri on June 15, 2022, 06:37:18 PM
-Results on 700D:

-1736x2214 @ 11 bit-lossless at 23.976 FPS, 240 MHz overclock, no GD (~78MB/s required write speed):

JPG:  first clip: 1 Minutes and 54 Seconds, second clip: 1 Minutes and 13 Seconds.
RAW: I have to stop it manually after 6 Minutes of recording :D

Downloads:

700D:
-Download the New build: crop_rec_4k.2022May25.700D115.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.700D115.zip)
-Download the New build with re-solved Dual ISO ISOless 8 & 15 for some 700D users: crop_rec_4k.2022May25.700D115_ISOless_8_15.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.700D115_ISOless_8_15.zip)
-Some users have stuck shutter value issue in ML menu, please try this build: crop_rec_4k.2022May25.700D115_Shutter_Blanking.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.700D115_Shutter_Blanking.zip)
-Some users may have both stuck shutter value issue in ML menu and ISOless Dual ISO errors, try the following build which contain both fixes: crop_rec_4k.2022May25.700D115_Shutter_Blanking_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.700D115_Shutter_Blanking_ISOless.zip)

650D:
-Download the New build: crop_rec_4k.2022May25.650D104.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104.zip)
-Download the New build with re-solved Dual ISO ISOless errors for some 650D users: crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip)

Source-code:
magic-lantern-bilal (25-5-2022).7z (https://drive.google.com/file/d/1ZhlTQwCPHHb0QNqrpGHqfV8-NVqv30P7/view?usp=sharing) (crop_rec_4k branch)

-Original post has been moved to Reply #2 (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231134#msg231134).

---

Upcoming tutorial: Shooting in Full-Resolution LiveView 5208x3472 continuously in 10-bit lossless @ 5 FPS (or in 12-bit lossless @ 4 FPS).

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM

Really Really cool

Some questions regarding the regular Crop Mode (Because I would like to use the fixed Live-View):

1. All presets are 23.976 fps. Can I change it to 25 via the menu option?

2. Can the 4.5k anamorphic mode resolution be changed? (I prefer going 2.35 ratio)

In the other Danne's build, I could use the 5k Anamorphic and change resolution from the mlv_lite, and also have 25 fps.

Thanks!

Original OP started:
**Download links in the End of the post**

New Build for 700D
(https://i.ibb.co/0cH8jPq/New-Build.png) (https://imgbb.com/)
(https://i.ibb.co/DK5GB4g/Build-modules.png) (https://imgbb.com/)

Included:
-SD Overclock with selectable presets 160, 192, 240 MHz.
-crop_rec with the higher resolutions with fixed LiveView (https://www.magiclantern.fm/forum/index.php?topic=19300.msg229664#msg229664) and the latest real-time (https://www.magiclantern.fm/forum/index.php?topic=25323.0) correct  (https://www.magiclantern.fm/forum/index.php?topic=25323.msg230933#msg230933)preview  (https://www.magiclantern.fm/forum/index.php?topic=25323.msg231048#msg231048)presets.
-The new crop_rec from a1ex with arbitrary resolutions (https://www.magiclantern.fm/forum/index.php?topic=19300.msg205546#msg205546) under the name "crop_new" or Crop mode V2.
-ISOless 8 & 15 Dual ISO fix (https://www.magiclantern.fm/forum/index.php?topic=7139.msg197139#msg197139).
-You can use Lower bit-depths when shooting in high resolutions in both crop_rec and crop_new.
-Shutter speed is correct when using any preset, or FPS override.

Using SD Overclock (sd_uhs.mo):
-Select a preset (160, 192 or 240 MHz) and restart the camera.
-The highest preset 240 MHz gives ~ 68 MB/s write speed (https://www.magiclantern.fm/forum/index.php?topic=12862.msg228673#msg228673) in video mode, and 240 MHz preset is stable when using Sandisk Extreme Pro 170MB/s Card (https://www.magiclantern.fm/forum/index.php?topic=12862.msg228673#msg228673).
(https://i.ibb.co/jgXqzCZ/SD-Overclock.png) (https://imgbb.com/)
(https://i.ibb.co/zGT499N/SD-Overclock-Presets.png) (https://imgbb.com/)

Default Crop mode (crop_rec) with Pre-Made Presets
You have these presets:
(https://i.ibb.co/SwSx6pv/Crop-rec-with-Presets.png) (https://imgbb.com/)

1- 2.5K Expanded Preview: Experimental Real-Time Correct Framing Preview in x5 Mode, To be used in x5 Mode.
2- 2.5K Expanded Preview HDMI: Experimental Real-Time Correct Framing Preview in x5 Mode, To be used in x5 Mode when HDMI monitor is attached @ 1080i in FULL size Canon preview.
3- 1440p 1:1: 2560x1440 16:9 @ 23.976 FPS with Fixed Preview, To be used in x5 Mode.
4- 3K 1:1: 3072x1308 2.35:1 @ 23.976 FPS with Fixed Preview, To be used in x5 Mode.
5- 4.5K Anamorphic 1x3: 1x3 Binning 1504x1782 with 1.86 Crop factor ~2.50:1 @ 23.976 FPS with Correct (Un-Stretched) Preview, *To be used in x5 Mode.
6- 4K Anamorphic 1x3: 1x3 Binning 1360x1976 with 2.05 Crop factor ~2:1 @ 23.976 FPS with Correct (Un-Stretched) Preview, *To be used in x5 Mode.
7- UHD Anamorphic 1x3: 1x3 Binning 1280x2160 with 2.18 Crop factor 16:9 @ 23.976 FPS with Correct (Un-Stretched) Preview, *To be used in x5 Mode.
8- 1920x1280p 1:1 Preview: 1:1 1920x1280p @ 23.976 FPS with Correct Preview, To be used in x5 Mode.
*We are patching back x5 Mode to 1x3 Binning (Anamorphic Mode) to achieve the correct preview.

-Using 10/12 Bit-Depths in higher resolutions with crop_rec:
1-Always select 14-bit lossless from mlv_lite.
2-Go to crop_rec submenu by pressing Q button, Now you can see "Bit-Depth" option, Select 10 or 12, that's it.
(https://i.ibb.co/5YMhyQp/Crop-rec-Shutter-Range.png) (https://imgbb.com/)

(https://i.ibb.co/dQhb0xT/Bit-Depths.png) (https://imgbb.com/)

-Full Shutter range allows you to get the lowest shutter speed and highest shutter speed possible with camera Hardware, down to 1/24 shutter speed, up to 1/36K shutter speed both @ 23.976 FPS.

New Crop mode module (crop_new) with Arbitrary Resolutions:
Instead of pre-made presets, this is the new version of crop_rec from a1ex (https://www.magiclantern.fm/forum/index.php?topic=19300.msg205546#msg205546), which allow you to select any preferred resolution, framerate and binning mode you want.

-How to use it?
Select "Pixel binning" mode, set your X resolution and Y resolution, set your desired Framerate option, press Menu button twice to apply the preset.
(https://i.ibb.co/V97Mcdt/New-crop-rec.png) (https://imgbb.com/)

(https://i.ibb.co/pQhhPPs/Showing-Pixel-binning.png) (https://imgbb.com/)

-Using 10/12 Bit-Depths in crop_new: I think you saw it already, remember you should always select 14-bit lossless from mlv_lite when using 10/12 Bit-Depths from here.
-You should always press Menu button twice for refreshing LiveView to apply the new settings, after changing them in crop_new "Crop mode V2", even when you turn off the module, you should press Menu button twice.
-You can create your Time-Lapses from this module in high resolutions, you can use FPS override too.
-x10 Mode will be valid for focusing, and won't be patched.
-This module doesn't include any recent preview fixes.

New Focus pixel maps for the previous presets:
Download it from 700D Focus Pixels Maps.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/700D%20Focus%20Pixels%20Maps.zip), drag and drop them in MLVApp interface directly.

More info about:
-The Advantages of 1x3 Binning (https://www.magiclantern.fm/forum/index.php?topic=22818.0).

Download the New build: crop_rec_4k.2020Sep30.700D115.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/crop_rec_4k.2020Sep30.700D115.zip)
Download the New build with re-solved Dual ISO ISOless 8 & 15 for some 700D users: crop_rec_4k.2020Sep30.700D115_ISOless_8_15.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/crop_rec_4k.2020Sep30.700D115_ISOless_8_15.zip)
-Links are being updated for the Latest build and focus maps.

Great time for 700D users, Have fun :D
Original OP ended.

---

Then this Reply#1 (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231067#msg231067) comes

---

Original Reply #2 started:

Quote from: SubZeroz on September 19, 2020, 10:16:51 AM
1. All presets are 23.976 fps. Can I change it to 25 via the menu option?
2. Can the 4.5k anamorphic mode resolution be changed? (I prefer going 2.35 ratio)

1 -Done
2- Done

New Build for 700D:
(https://i.ibb.co/tQvfjMf/New-Preset.png) (https://imgbb.com/)

1- Added New 4.3K Anamorphic 1x3 Preset 1440x1836 1.94 Crop factor 2.35:1 AR with Correct Preview
2- Added option for 25 FPS in crop_rec
3- Added 9/8 Bit-Depths for both crop_rec and crop_new
4- In crop_new Now there is an Option for fixing Preview in x5 Mode Max X resolution should be 3112
5- Fixed Black Level in preview when using lower bit-depths 10/9/8 in crop_rec


(https://i.ibb.co/HXjSFYq/9-and-8-Bit-Depths-options.png) (https://imgbb.com/)

(https://i.ibb.co/XbgpFY3/25-FPS-option.png) (https://imgbb.com/)

(https://i.ibb.co/znTBhrX/Preview-FIX-crop-new.png) (https://imgbb.com/)

How to use this Build and more details about it:
https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049

Download the New build: crop_rec_4k.2020Sep30.700D115.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/crop_rec_4k.2020Sep30.700D115.zip)
Download the New build with re-solved Dual ISO ISOless 8 & 15 for some 700D users: crop_rec_4k.2020Sep30.700D115_ISOless_8_15.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/crop_rec_4k.2020Sep30.700D115_ISOless_8_15.zip)

New Focus Maps:
https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/700D%20Focus%20Pixels%20Maps.zip
-Added 4.3K Anamorphic 1x3 Preset 1440x1836 map.
Original Reply #2 ended:

Where do you publish crop rec code changes? Nice with 2.35:1.

Thanks,
I didn't create another online repository after Bitbucket did what it did :P, Planning to use Heptapod and import the repository, not sure if this would work easily, I am doing it locally for now . .

Quote from: Ballinger on September 23, 2020, 03:51:43 AM
I'm experiencing weird LCD screen artifacting with your latest build whilst utilizing the 2.5K expanded fixed preview crop mode preset.  Both the regular 2.5K and the HDMI 2.5K modes only fill up part of the LCD display while at the same time a pink color bar covers the bottom 1/3 or the LCD screen.   Framing seems correct in the actual footage shot, but the LCD display is just weird looking except for a skewed display of the actual correct framing preview that is offset to the upper left part of the LCD display.   Additionally, the pink color bar is sometimes replaced by an out of focus, pixelated portion of the subject in the frame.    Other times, the entire display seems to just go completely crazy with no discernible image at all, requiring a camera power down to reset it.   

This is normal, the bottom half of preview should be black, these artifacts are showing because there is no RAW data to show on the bottom of the preview, this can be controlled from Canon registers to cut this part and make it black, still working on it, Danne made Crop Marks for now to hide these artifacts, you can find it here:
https://bitbucket.org/Dannephoto/magic-lantern_jip_hop_git/downloads/crpmks_frtp.zip

Also I am working to add black bar baked in each preset directly, and without enabling Global Draw instead of changing it each time from Cropmarks.

Removed off-topic quoted from deleted posts //Audionut

Please read through the following article, which I mentioned many times earlier, also included in how use this build (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) some people are too lazy to read or understand, don't be like them, the article containing:
https://www.magiclantern.fm/forum/index.php?topic=25323.0

Quote from: theBilalFakhouri on September 10, 2020, 03:02:55 PM
Introducing the New Expanded Real-Time preview in x5 Mode
(https://i.ibb.co/3FdsrpY/New-Expanded-Preview.gif)

Quote from: theBilalFakhouri on September 10, 2020, 03:02:55 PM
Known Limitations:
-Black Bar in the right instead of the right part of actual RAW data.

Notes:
-The Preview is in the Top Part of the screen, not centered on screen.
-You may compare ML Framing vs The New Preview to trust it.
-Turn OFF Global Draw for better Preview.
-Feel the responsive.
-Instead Normal of x5 Mode Preview? Wow!
-Still working on Black Bar limit.

Quote from: theBilalFakhouri on September 10, 2020, 03:02:55 PM
Known Limitations:
-Black Bar in the right instead of the right part of actual RAW data.

Quote from: theBilalFakhouri on September 10, 2020, 03:02:55 PM
Notes:
-The Preview is in the Top Part of the screen, not centered on screen.
-You may compare ML Framing vs The New Preview to trust it.

Quote from: theBilalFakhouri on September 10, 2020, 03:02:55 PM
-Still working on Black Bar limit.

The artifacts are totally okay, Do you remember when we had the broken-pinkish preview in the initial crop_rec from a1ex:

Quote from: a1ex on April 01, 2017, 11:15:41 AM
* Canon preview is broken in most modes; you need to use the grayscale preview in the raw recording module.

It's the same thing here regarding Safety but in a different look, this preview still in Experimental Stage, don't use it if you are afraid, however many 700D, EOS M users have tried it, they pretty happy because they knew how to use it and they read this article before they used it:
https://www.magiclantern.fm/forum/index.php?topic=25323.0


-New build is coming soon containing:
1-All presets will support HDMI output with real-time correct preview.
2-You can ZOOM while recording to check focus instead of stopping recording, checking focus, starting over.
3- Black Bars instead of artifacts.
4-When you enable a preset, you will be automatically get into x5 Mode, to avoid crashes when you are enabling the presets on other modes.

Tidied this post up a little //Audionut

**Download links in the End of the post**

New Build for 700D

What's New:
-crop_rec:
1- When you enable any preset you will get into the right mode automatically, No more frozen LiveView or Camera crashes again (Stability :) ).
2- Autodetect HDMI support for the Real-Time presets, which means all presets works with HDMI now, no further selections needed.
3- Magic Zoom V2: Now you can use Magnification button or SET button to get zoomed preview to check focus, and this works while you are recording!
4- Better Centering for 3K preview.

-mlv_lite
1- Black Bar instead of preview artifacts.
2- Prevent using lower bit-depths for 3K and 1920x1280p presets, to avoid corrupted frames, use lower bit-depths in crop_rec submenu.

Autodetect HDMI
-The presets will only work with 1080i output! 720x480 or other outputs won't work.

Magic Zoom V2
-3K and 1440p presets aren't supported, you can use regular x10 mode.
-I had corrupted frames when using Magic Zoom V2 with HDMI monitor, don't use Magic Zoom V2 with HDMI monitor attached while recording.
-4K and UHD 1x3 Presets do have Magic Zoom V2, but with not perfectly centered preview or stretched zoomed preview, but it works for focusing.

Features:
-Nail your focus While recording!
-Works with All preset with real-time correct framing preview.
-You can trigger it by Zoom button or SET button on 700D and 650D.
-No overhead or slowness, didn't have corrupted frames during my tests (on camera LCD screen).
-Real-Time as Canon Preview, it's a Canon preview actually, but zoomed.
-Works with Global Draw OFF.
-It may work also with normal mv1080 Mode in theory, but didn't make a preset yet for this mode.

First Video showing Magic Zoom V2:
https://www.youtube.com/watch?v=1wFeCccCsLo

-To achieve better preview in real-time correct preview presets use this setting:
Go to ML Settings --> "Display" Tab --> Advanced settings --> Screen Layout --> "Bottom,under 3:2", Here is how it should look like:
https://www.magiclantern.fm/forum/index.php?topic=25323.msg231271#msg231271

How use this build and more Info about it: (Read all of them)
https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049
https://www.magiclantern.fm/forum/index.php?topic=25784.msg231134#msg231134
https://www.magiclantern.fm/forum/index.php?topic=25323.0

Download the New build: crop_rec_4k.2020Sep30.700D115.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/crop_rec_4k.2020Sep30.700D115.zip)
Download the New build with re-solved Dual ISO ISOless 8 & 15 for some 700D users: crop_rec_4k.2020Sep30.700D115_ISOless_8_15.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/crop_rec_4k.2020Sep30.700D115_ISOless_8_15.zip)

Download Focus Maps for All Presets: 700D Focus Pixels Maps.zip (https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/700D%20Focus%20Pixels%20Maps.zip)

Source Code with All commits: magic-lantern_zoom_function.7z (https://drive.google.com/file/d/1ruoGs_mz3BLijqmxD2QI_DV_iqSicFkT/view?usp=sharing)

Amazing to see all the developments on this camera.

I have a few questions does the Eos m offer a lot more features than the 700d for magic lantern raw recording or quite similar now a days? I like the form factor of the 700d more and my EF-S collection fits directly on it.

Beside the 1,6 crop factor of the 700d. Are there any high quality raw recording modes with no additional crop on top of the 1,6? For example would I been able to use my canon 10-18 @ 10mm and get a 16mm equivalent look in any raw video modes? If it's possible at all, is the footage usable as I read that ultra wide angle lenses can suffer from aliasing.

Are there any higher frame rates than 25 for example 50 possible for raw video recording?

Is single autofocus by touch possible to grab focus?

@Nigel95

Thanks,

EOS M and 700D are identical, same capability here and there regarding RAW recording yes, but I would prefer EOS M for Speed Booster support, and 700D for Flip Screen, if the size doesn't matter.

You can't have both 1.61 Crop Factor without aliasing. There are 1x3 Modes which solve aliasing problem but it has crop factors more than 1.61, or 1:1 modes which has a lot of cropping compared to 1x3 modes, also without aliasing.

There is 1x3 Mode which use full width sensor (1.61 Crop) which is 1736x2214 @ 23.976 FPS 2.35:1 AR you can achieve it by crop_new on 700D, however this mode isn't continuous even with the 240 MHz overclock and 10-bit lossless, you may lower the resolution to 1600x2040 @ 23.976 FPS 2.35:1 AR with 1.74 Crop to get continuous recording or You can stuck with 1736x2214 but lower framerate to @ 21 FPS to get continuous recording, However these two modes have stretched (not-correct) previews.

You can get 1736x868 3x3 2:1 AR @ 50 FPS, not continuous, (or 1736x738 2.35:1 @ 48 FPS this would be continuous @10-bit lossless) and with stretched preview. Or you can use the regular 5x3 Mode from Canon which have a lot of aliasing and Moire 1736x522 (1736x868 After stretching) 2:1 AR @ 50 FPS, this one is continuous with correct preview.

Autofocus by touch screen is possible, but the autofocus system is not that good on both EOS M and 700D. Autofocus won't work with the real-time correct preview 1x3 presets or x5 Mode.

Thanks for the new features. Very interesting.

I'm using my 700d for streaming (using the HDMI output). I do not record to the SD card. Do settings like high resolution or dual-iso now have any benefits for HDMI output, or only for the video recorded to SD?

Hi to everyone , thanks for you hard work. About 48fps record I have some dudes. Please can someone post the steps for a right configuration. Should I change the resolution in canon menu? Thanks for your attention

Very Cool!

I'm using an Android phone as a screen and found some issues when using this version with HDMI:
(I'm using the 4.3k preset)
1.  In order to get HDMI to work, I need to press the 'info' once, otherwise no image is being updated
2. Sometimes there's a strange and wierd flickering on the sides
3. Focus Peaking doesn't work, just shows lots of noise at the bottom
4. Probably not related to HDMI - I can't set the shutter speed. It's stuck at 1/26 and ignores my cannon shutter speed. I've tried going into the ML menu and change it but I can only change the 'TV' which doesn't seem to affect the shutter?


Because of '2' and '3' I Decided to also check this in Danne's Build listed above.

I've built (Based on source code online with some changes) a small Android app that gets HDMI input and stretches it. The result is actually pretty cool:

Camera:

(https://i.imgur.com/PKYZLz1.png)

Vs Phone (6.1 inch):

(https://i.imgur.com/YKTK8n8.png)


It seems like Danne's build also has issues with the HDMI:
1. Focus Peaking doesn't work here aswell
2. After recording, I've checked the videos in my computer. it seems like every few seconds there a PINK corrupted frame. This doesn't happen If i record without HDMI.


Any idea how to fix the Focus Peaking & Shutter?

Are you using what code for what cam? Will you share your android app source and application? Would be nice to test it out.
I tested hdmi with eos m and seems to work fine. Try 24 fps and see if that clears corrupted frames.

Using this build: https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr02.700D115.zip
for 700d.

I've tried changing to 24 fps but with no luck :\ Perhaps the HDMI to USB recorder i'm using is causing some issues, But thats a bit strange...


Is there any place I can access the source of that build?

____


The app is based on:
https://github.com/jiangdongguo/AndroidUSBCamera
which is based on some other repo...
I've mostly deleted lots of stuff and added the stretch code.

Currently It only stretches to support 2.35 ratio, and there's some code-mess.
If you'll still wish to get the source before I make some order & clean up I'll create a repo and upload it.

Here is a link to the APK:
https://drive.google.com/file/d/1MOXTtCjS4b0XovfBStPua7nu2Q3pLccD/

1. I've looked at the other git repos, and from a quick look - it seems O.K, but that code was not written by me, so use this app at your own risk :-)
2. Tested it on my phone screen ratio, I have no idea how it would look on your screen (Would appericiate a screenshot though).
3. My phone is running Android 9
4. If people need this I can add other stuff such as choosing the desired ratio etc'


How to install:
allow install apk from unknown sources

Run:
Simply run the app. It would show a blank black screen. Once you plug in the otg cable it would tell you it has recognized the camera.
The best camera liveview mode is the last one (by clicking 'info'), but any should work.
In Bilal's build only the second preview works. The first doesn't show any image.

Cool. I think I'll wait for a cleaned up build though  :P.
Regarding shutter speed it's probably related to shutter blanking. theBilalFakhouri is aware about that so hopefully he will take a look.

Quote from: Danne on October 09, 2020, 07:02:58 PM
Cool. I think I'll wait for a cleaned up build though  :P.
Regarding shutter speed it's probably related to shutter blanking. theBilalFakhouri is aware about that so hopefully he will take a look.

Uploaded it here:
https://www.magiclantern.fm/forum/index.php?topic=25406.0

Quote from: SubZeroz on October 09, 2020, 04:13:42 PM
Very Cool!

I'm using an Android phone as a screen and found some issues when using this version with HDMI:
(I'm using the 4.3k preset)
1.  In order to get HDMI to work, I need to press the 'info' once, otherwise no image is being updated
2. Sometimes there's a strange and wierd flickering on the sides
3. Focus Peaking doesn't work, just shows lots of noise at the bottom
4. Probably not related to HDMI - I can't set the shutter speed. It's stuck at 1/26 and ignores my cannon shutter speed. I've tried going into the ML menu and change it but I can only change the 'TV' which doesn't seem to affect the shutter?

1- Yes, you should be in Full Canon preview when you are using HDMI with Real-Time Correct Preview presets, you can toggle between full canon preview and small preview by pressing INFO button.
2- I had flickering on sides problem in the official builds too, this problem not related to this build exclusively, it's related to mlv_lite, also to crop_rec with the new presets, nothing to do, you can get rid of it by pressing Menu button twice or refresh LiveView.
3- Yeah, Focus peaking isn't working fine when using HDMI, this problem are there in the official builds too, not related to this build, no idea how to fix it.
4- I don't have this problem, any steps to reproduce the problem? can you explain more what settings are using and mode etc.. ?

Quote from: theBilalFakhouri on October 10, 2020, 01:55:38 PM
1- Yes, you should be in Full Canon preview when you are using HDMI with Real-Time Correct Preview presets, you can toggle between full canon preview and small preview by pressing INFO button.
2- I had flickering on sides problem in the official builds too, this problem not related to this build exclusively, it's related to mlv_lite, also to crop_rec with the new presets, nothing to do, you can get rid of it by pressing Menu button twice or refresh LiveView.
3- Yeah, Focus peaking isn't working fine when using HDMI, this problem are there in the official builds too, not related to this build, no idea how to fix it.
4- I don't have this problem, any steps to reproduce the problem? can you explain more what settings are using and mode etc.. ?

Hi!
I've also replied at the other thread.

1. O.K, just wanted to let you know
3. Yes, as I wrote in that post - It didnt work on Danne's build aswell :-(, I Hoped that mybe you have any clue about this.
4. Do you simply change the shutter speed from the main screen while in Manual mode? its number has red color, and when I go to the Magic Lantern menu it is stuck at 1/26.
Perhaps I should just ignore what's written in the ML menu?
Is there any way to check in-camera the REAL shutter speed?

3- I don't use focus peaking personally, I will let you know if I get any clue about how to solve it and I will try too . .

4- Tried your steps, shutter speeds are working fine in all presets, and both from ML and Canon menu shutter speed is showing correctly . .
You don't need to ignore what's written in ML menu, this problem is fixable I had something like that in the past . . Let's debug the problem first:

I think your camera are using different addresses for shutter blanking, Does Danne's build have the same shutter speed issue?

3. Thanks!
4. In Danne's build its working perfectly. How can the addresses be different? Aren't we running the same 1.1.5 Firmware?

My theory is correct, in my build, I am using these addresses:
#define FRAME_SHUTTER_BLANKING_ZOOM   (*(uint16_t*)0x40452d18) // ADTG register 805f
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x40452d1c) // ADTG register 8061
#define FRAME_SHUTTER_BLANKING_READ   (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM) /* when reading, use the other mode, as it contains the original value (not overriden) */
#define FRAME_SHUTTER_BLANKING_WRITE  (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)

in Danne build he is using these addresses:
#define FRAME_SHUTTER_BLANKING_ZOOM   (*(uint16_t*)0x40452918) // ADTG register 805f
#define FRAME_SHUTTER_BLANKING_NOZOOM (*(uint16_t*)0x4045291c) // ADTG register 8061
#define FRAME_SHUTTER_BLANKING_READ   (lv_dispsize > 1 ? FRAME_SHUTTER_BLANKING_NOZOOM : FRAME_SHUTTER_BLANKING_ZOOM) /* when reading, use the other mode, as it contains the original value (not overriden) */
#define FRAME_SHUTTER_BLANKING_WRITE  (lv_dispsize > 1 ? &FRAME_SHUTTER_BLANKING_ZOOM : &FRAME_SHUTTER_BLANKING_NOZOOM)

Try this build, added Danne addresses:
https://drive.google.com/file/d/11v53g04TANxRxDOS9HfI_aNqPa7HfVpA/view?usp=sharing

Quote from: SubZeroz on October 10, 2020, 03:05:05 PM
4. In Danne's build its working perfectly. How can the addresses be different? Aren't we running the same 1.1.5 Firmware?

This something related when Canon firmware copies something from ROM to RAM, explained by a1ex here:
https://www.magiclantern.fm/forum/index.php?topic=25976.msg231177#msg231177 (a1ex was talking about Dual ISO problem, same thing applies here regarding why we are having shutter blanking issue and different addresses)

Tried it now - WORKS GREAT!!!! Thanks!

Also, You are correct, the preview colors look better.

Couple of questions:
1. Are you going to change the position of the liveview? (Like - putting it in the center?), I need to know because I plan to change the Android-App to stretch the image to the entire screen, removing the black edges (Bigger image, No flickering or black!).

2. Out of 60 seconds 3 seconds with pink flickering. Its not only in ur build, it also happened in Danne's build. Does this happen because the camera CPU is under heavy usage? (This doesnt happen in NON-HDMI), Lowering the resolution should fix it?

Are you still running 25fps regarding pink frames? On Eosm I only tested 24fps but no pink frames. Also had reports from another user hdmi working with no pink frames.
Moving the full live view content to centre is not trivial.

Yes, still going 25fps because 24fps didnt fix it  :'(

Anyways, no need to move the liveview now, I did the following in the Android-APP:

1. Stretch HDMI-INPUT to the bottom & to the sides
2. move the entire INPUT down

Result (Screenshot from my phone):
(https://i.imgur.com/K4Ob3tr.png)

Only problem is that u cant see current shooting configuration. Perhaps I'll slice the bottom (Which isn't on the screen) and paste it.
Not sure how much work this is 

Cool.

What preset? 16:9? Are the other ones working better?

Quote from: Danne on October 10, 2020, 08:29:32 PM
Cool.

What preset? 16:9? Are the other ones working better?

2.35:1

I didn't push it to the git yet, a local repo (So what I've published earlier should work anyway).

All Presets are working great, I just wanted to see it on my entire phone-screen.

The problem was that in that build, the fixed liveview contains a rect at the top of the screen with the real image, so I've pulled it down to the center, and then scaled it to fit my entire screen.
I need to slice the configuration (shutter etc') from the bottom, because its out of the screen, thanks to the changes above :-)

I see. So corrupted frames occur with 2.35:1.

I checked 700D sources. in crop_rec.c there´s this for 2.35:1 preset:
        case 0xC0F06804: return 0x748018A;

        case 0xC0F06010: return 0x1C9;
        case 0xC0F06008: return 0x1C901C9;
        case 0xC0F0600C: return 0x1C901C9;

        case 0xC0F0713c: return 0x755;

You could try changing C0F0713c to the same as beginning of 0x748. So change it to:
        case 0xC0F0713c: return 0x748;
If still getting pink frames you could increase timer regs:
        case 0xC0F06010: return 0x1C9;
        case 0xC0F06008: return 0x1C901C9;
        case 0xC0F0600C: return 0x1C901C9;
This means you´ll gonna have to decrease reg 6014 to compensate back to 24 or 25 fps.


My preset in eosm code look like this as comparison example:
        case 0xC0F06804: return 0x748018A + reg_6804_width + (reg_6804_height << 16);
        case 0xC0F06014: return 0x8ec + reg_6014;
        case 0xC0F0600c: return set_25fps ? 0x2470247 - 24 + reg_6008 + (reg_6008 << 16): 0x2470247 + reg_6008 + (reg_6008 << 16);
        case 0xC0F06008: return set_25fps ? 0x2470247 - 24 + reg_6008 + (reg_6008 << 16): 0x2470247 + reg_6008 + (reg_6008 << 16);
        case 0xC0F06010: return set_25fps ? 0x247 - 24 + reg_6008: 0x247 + reg_6008;
        case 0xC0F0713c: return 0x755 + reg_713c;

I think increasing timer registry around the same as on eosm should do the trick:
        case 0xC0F0600c: return 0x2470247;
        case 0xC0F06008: return 0x2470247;
        case 0xC0F06010: return 0x247;
        case 0xC0F06014: return 0x8ec;
        case 0xC0F0713c: return 0x755;

Quote from: SubZeroz on October 10, 2020, 07:58:23 PM
Couple of questions:
1. Are you going to change the position of the liveview? (Like - putting it in the center?), I need to know because I plan to change the Android-App to stretch the image to the entire screen, removing the black edges (Bigger image, No flickering or black!).

2. Out of 60 seconds 3 seconds with pink flickering. Its not only in ur build, it also happened in Danne's build. Does this happen because the camera CPU is under heavy usage? (This doesnt happen in NON-HDMI), Lowering the resolution should fix it?

1- Unfortunately it's not a simple task, LiveView is very complex, we can't control this part yet, it may take weeks or months to achieve this, it won't be any time soon.

2- During my previous tests I didn't get corrupted frames in 1x3 Modes with the correct previews, I will make more tests in future, in other normal modes like 1080p or 2.5K I got some corrupted frames, it's an overhead yes when the output is 1080i which affects all builds, changing HDMI output to 720x480 probably would solve this problem, not sure how 720p output would perform.

It seems I missed two replies here.

Quote from: AllWashedOut on October 06, 2020, 10:18:16 PM
Thanks for the new features. Very interesting.

I'm using my 700d for streaming (using the HDMI output). I do not record to the SD card. Do settings like high resolution or dual-iso now have any benefits for HDMI output, or only for the video recorded to SD?

You're welcome

HDMI output won't be benefited from these modes regarding quality also Dual ISO (which needs to be processed in post, otherwise if you used it in streaming you will get lines in the image), as you said you will get the benefits from these modes only when recording RAW data to SD card, the best Mode for streaming using HDMI is the normal 1080p.

Quote from: Morfeus77 on October 08, 2020, 02:53:04 PM
Hi to everyone , thanks for you hard work. About 48fps record I have some dudes. Please can someone post the steps for a right configuration. Should I change the resolution in canon menu? Thanks for your attention

Hello, thanks

Set video mode to 720p @ 60 FPS (NTSC) from Canon Menu, then enable "Crop mode V2" and do the following:
https://i.ibb.co/NSGfybb/3x3-48-FPS.png (https://i.ibb.co/NSGfybb/3x3-48-FPS.png)

(http://i.ibb.co/NSGfybb/3x3-48-FPS.png)

Then press Menu button twice to apply the new settings, this will give 1736x868 2:1 AR @ 48 FPS in 3x3 Binning mode, the preview would be stretched!
- You can increase Y resolution more, but you may get corrupted frames.

Quote from: theBilalFakhouri on October 11, 2020, 12:15:53 PM
2- During my previous tests I didn't get corrupted frames in 1x3 Modes with the correct previews,

Do try my last suggestion. Also match 713c with 6804. Typically what will solve pink frame issues.

Thanks Danne.

Bilal is there any chance you'll test this?

I'll get an environment ready to compile but it would take me some time.

_______________________________________

I Have a special version of the Android App which should suites the last build.
In this one when you open the App you'll see the same screen as the Camera LiveView, but when you'll single-press the screen it would enlarge only portion of the screen - where the real image is (And not black edges etc')

I Currently use this with HDMI-INPUT 1920x1080, and 4.3k preset. I'm not sure how this will look with the other modes.

But it's really cool that you can see a big preview :-)

https://drive.google.com/file/d/1lGLnwsvirNw-rz3AAu5oJS0ZvhWwNOlY

Hi Bilal, is it possible to add a preset for "full resolution liveview 1:1) in your custom crop_rec module for 700D?

I tried to use crop_rec new but the preview in 5x is not usable and it stop working immediately after the start also if I reduce fps to 4.

I would try to take a video of the full moon at 1600 mm of FL to obtain a "mineral moon" picture.

Thanks for your great work

Fabio

Quote from: theBilalFakhouri on October 11, 2020, 12:51:04 PM
It seems I missed two replies here.

You're welcome

HDMI output won't be benefited from these modes regarding quality also Dual ISO (which needs to be processed in post, otherwise if you used it in streaming you will get lines in the image), as you said you will get the benefits from these modes only when recording RAW data to SD card, the best Mode for streaming using HDMI is the normal 1080p.

Hello, thanks

Set video mode to 720p @ 60 FPS (NTSC) from Canon Menu, then enable "Crop mode V2" and do the following:
https://i.ibb.co/NSGfybb/3x3-48-FPS.png (https://i.ibb.co/NSGfybb/3x3-48-FPS.png)

(http://i.ibb.co/NSGfybb/3x3-48-FPS.png)

Then press Menu button twice to apply the new settings, this will give 1736x868 2:1 AR @ 48 FPS in 3x3 Binning mode, the preview would be stretched!
- You can increase Y resolution more, but you may get corrupted frames.

Thanks a lot for the explanation, I'll will try now.
Good job

deleted.

Quote from: theBilalFakhouri on September 21, 2020, 08:39:23 AM

New Focus Maps:
https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/700D%20Focus%20Pixels%20Maps.zip
-Added 4.3K Anamorphic 1x3 Preset 1440x1836 map.

Sorry, but I don't see 1440x1836 map in this archive. The latest map here is from 2018 year.
(http://supervid.ru/700d_focus_maps.jpg)

In focus pixel maps we are calculating the black areas too, so:

Naming of focus pixel map  ≠ RAW resolution
Naming of focus pixel map  > RAW resolution

In your case the map you are looking for is "80000326_1512x1864.fpm", extract all the focus pixel maps in MLVApp folder, you should be fine in all crop_rec presets automatically.

-You can also use the latest MLVApp which can download all the required focus maps automatically too, or you can drag and drop the focus maps from the archive into MLVApp interface, and this will install the focus maps in MLVApp.

Original focus map created in 2018 which covers all focus pixels on the sensor, and we are using the same map for all 1x3 Binning modes (I am duplicating it), remaining thing is to identify which RAW resolution we are using now and calculate the offsets for current resolution (to match the focus pixel map with MLV file), and we can achieve this by just changing the naming of the focus pixel map to include RAW resolution + black areas, in this case the focus pixel map date will stay 2018 (renaming won't affect the date).

New Focus Maps:
https://raw.githubusercontent.com/bilalfakhouri/magic-lantern/master/700D%20Focus%20Pixels%20Maps.zip
-Added 4.3K Anamorphic 1x3 Preset 1440x1836 map.
[/quote]

Unfortunately, with 650D after extracting files into MLVAPP folder when I record 1440x1836 I have focus dots
(http://supervid.ru/focus_dots_1440.jpg)

Ah, I thought you are using 700D (Why not to post on 650D thread?)

Mostly all 700D focus pixels maps are identical to 650D too, in this case you need only to change the ID in focus pixel map files from 700D ID to 650D ID; from "80000326" to "80000301":

Just did it for all focus pixel maps, try these focus maps for 650D (It should work with all crop_rec presets using my 650D build):
650D Focus Pixels Maps.zip (https://github.com/bilalfakhouri/magic-lantern/raw/master/650D%20Focus%20Pixels%20Maps.zip)

Please let me know if these work for 650D in all presets.

Thank you very much theBilalFakhouri. All presets work fine now. Except these presets I use also not registered " 1736*696 1x1  48fps" from new Crop_Rec V2 menu and it has focus dots. Is it simple to create focus map for this preset?
 

You're welcome

Please provide short MLV sample for the mode you are using, you can cut it in MLVApp, two frames are enough, export it as MLV (fast pass)

I can make a simple tutorial about how to generte focus pixel map for any resolution (using Crop rec V2) for both 1x3 and 1x1 modes.

Quote from: IBIRRU on October 14, 2020, 03:16:00 PM
Hi Bilal, is it possible to add a preset for "full resolution liveview 1:1) in your custom crop_rec module for 700D?

I tried to use crop_rec new but the preview in 5x is not usable and it stop working immediately after the start also if I reduce fps to 4.

I would try to take a video of the full moon at 1600 mm of FL to obtain a "mineral moon" picture.

Thanks for your great work

Fabio

Sorry for the delay, I didn't use full resolution LiveView much in the past, so I spent some weeks playing with it.

I am preparing for a new build which solve ML Framing in x5 mode, and also added custom FPS in crop_new, this will allow using the full shutter speed in any framerate, from 360° to 1° angles.

Adding full resolution LiveView preset in crop_rec won't perform any better from crop_new, Canon preview would be broken in both modules, in this case you should use ML Framing (which has a problem currently in my latest build, fortunately I fixed it now, will realease a new build soon)

Guess what: Full resolution LiveView = 5208x3478 @ 5 FPS is continous in 12-bit lossless  :) , of course when using 240 MHz overclock. More info coming soon.

Great news !!

Many thanks Bilal!! :D

I will wait the next relaease.

Hey guys, could you point me to the latest mostly stable build that included the sd_uhs mod please. Also what can you achieve on the 700D? Is 240MHz stable? It's been working on on my 6D, need a B-roll camera and I've got a 700D lying around.

Wondering if someone can help me.

I studied and was into filmmaking about a decade ago, and am looking to get back into it. First off, though, I want to get better at photography, so I'm in the market for a very cheap but capable DSLR, and I'm looking at used Rebels and I might be able to get a pretty good deal on a 700D.

I'm also quite interested in using this camera as a low budget cinema camera down the line with ML, though I know it takes a bit of learning and tweaking. I'm fine with that. I've seen some great images come out of both the EOS M and the Canon 700D using ML RAW. The RAW excites me because more than 4k, what I want is something with no compression and higher dynamic range and bit depth. But I'm not completely sure of the 700D's capabilities with ML, so let me just ask some quick questions.

1. Since the EOSM and 700D have the same sensor and processor, can the 700D create the same quality of video I see on EOS M videos like from Zeek's channel?

2. I know ML won't work miracles. I don't care about true 4k or slow mo. But I'd like something stable, RAW, and around 1080p true resolution (I want to shoot 4:3 too, so 1440 x 1080 would be great).

tl;dr- I'm looking for a very cheap camera that I can practice photography on as well as shoot decent video with ML. RAW 1080p with a minimum crop to avoid aliasing (2x would be fine) is essentially what I am aiming for, and was just wondering if the 700D could do all this. If not, I might just go for a cheaper option like a used t2i.

Thanks

Could you add the option to disable 30-minute live view timeout? It's present in the 700D "Lua Fix" builds. Or perhaps it's just been renamed in this build?

Original name: Prefs tab -> "Powersave in Liveview" -> "30-minutes timer"

Add to which build? What is "this build"?

@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?

Hello @lightwriter

Yes, 192MHz overclock is stable for Sandisk Extreme PRO 95MB/S  cards, you need to do low level format in the camera at least for once, this prevent speed drops if it were there.

You can get 1x3 1600x2040 in crop_new (Crop mode V2):

Set Binning mode to 1x3, Y resolution to 2040, FPS to 23.976, keep X resolution as default (zero)

Press Menu button twice for refreshing LiveView to apply our new settings, from mlv_lite set the resolution to 1600, Aspect ratio to 2.35:1, now you should be okay, check the resolution from mlv_lite (RAW video)

MLVApp would read the file as 1x3 Binning, and would stretch the footage automatically --> So the stretched resolution from 1600x2040 file would be after stretching 4800x2040, now it's 2.35:1 AR

The Preview would be stretched in LiveView, there is no real-time correct preview in this mode, you want to use ML Framing to check framing.

Yes there is no aliasing in 1x3 Binning, this is the huge advantage for this mode! also 1x3 Binning reduces moire patterns a lot.

Is it possible to get a full 16:9 ratio over the HDMI output without the black vertical sidebars at any resolution?  I mean straight out of the camera without processing.  I know the T5i can't do a full-screen 1080i, but stretching or cropping with OBS software introduces some lag that is awkward on Zoom calls.

Note: I tried Canon's EOS WebCam software that uses USB instead of HDMI but the frame rate was way too low for reasonable Zoom calls.

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?

Hi guys, thank you for this wonderful forum. I am a new ML user. I apologize in advanced if this question is given already. I did search the forum but am having a hard time finding the answer. Is the Eos 700D able to shoot in 50fps in 1080p? I really need to know this. Thank you so much in advance. :)

Quote from: AlexPace on December 12, 2020, 08:58:53 AM
Is it possible to get a full 16:9 ratio over the HDMI output without the black vertical sidebars at any resolution?  I mean straight out of the camera without processing.  I know the T5i can't do a full-screen 1080i, but stretching or cropping with OBS software introduces some lag that is awkward on Zoom calls.

Note: I tried Canon's EOS WebCam software that uses USB instead of HDMI but the frame rate was way too low for reasonable Zoom calls.

Unfortunately clean HDMI output (without the black bars on both sides) from 700D/T5i isn't possible, I was doing some experiments regarding these black bars, I got promising results, you can see here (first post, the HDMI experiment):
https://www.magiclantern.fm/forum/index.php?topic=25287.0

So I think implementing clean HDMI output on T5i is possible and we know where to start, but currently I am unable to continue experimenting, lack of time, sorry.

---

@lightwriter

You're welcome!

When I mentioned 1600x2040 preset, I think here:

Quote from: theBilalFakhouri on October 01, 2020, 05:08:47 AM
There is 1x3 Mode which use full width sensor (1.61 Crop) which is 1736x2214 @ 23.976 FPS 2.35:1 AR you can achieve it by crop_new on 700D, however this mode isn't continuous even with the 240 MHz overclock and 10-bit lossless, you may lower the resolution to 1600x2040 @ 23.976 FPS 2.35:1 AR with 1.74 Crop to get continuous recording ..

To achieve continuous recording you need to use 10-bit lossless, and you need the 240 MHz overclock (with Sandisk Extreme PRO 170 MB/s card)

Quote from: lightwriter on December 12, 2020, 12:53:09 PM
In RAW video I selected 1600, but when I go to Crop mode V2, I didn't change X resolution, but it says 1736.

Yes, This seems correct, keeping X value to zero will give the default X resolution which is 1736 in grey color.

Quote from: lightwriter on December 12, 2020, 12:53:09 PM
What bit depth should I select in Crop Mode V2? Or should it be off?

For continuous recording, you need to select 10-bit from "Crop mode V2" , and keep it 14-bit lossless from "RAW video".

Quote from: lightwriter on December 12, 2020, 12:53:09 PM
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.

You will need to use 10-bit from "Crop mode V2" to lower the data rate, also you will need 240 MHz overclock which gives up to 68 MB/s write speed in video mode, 192 MHz is limited to ~55 MB/s maybe a little more which won't give continuous recording in this mode . .

Quote from: lightwriter on December 12, 2020, 12:53:09 PM
Pressing Menu button twice, the resolution of Crop mode V2 shows 1736x2040 1x3, RAW video shows 1600x2040 1.74x

Yes, this seems correct too, recording at this stage (after pressing Menu button twice) would allow you to record some seconds without corrupted frames, right?

Quote from: lightwriter on December 12, 2020, 12:53:09 PM
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?

Everything you are doing is correct actually, but you will need the 240 MHz overclock with 170 MB/s Sandisk Extreme Pro and 10-bit depth from "Crop mode V2" for continuous recording, the 192 MHz benchmarks looks okay too if you did the benchmark in video mode, try running benchmark in PLAY mode, run benchmark and press PLAY button; this should give you ~80 MB/s write and read speeds.

Have you managed to get some clips without corrupted frames in this mode?

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 (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 (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 (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. (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!

@lightwriter

Hi again!

1- This corruption due to un-refreshed LiveView, to prevent this:

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM
-You should always press Menu button twice for refreshing LiveView to apply the new settings, after changing them in crop_new "Crop mode V2", even when you turn off the module, you should press Menu button twice.

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 (https://www.magiclantern.fm/forum/index.php?topic=12862.0).

6- This issue has been discussed here  (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231838#msg231838)

Quote from: aserranojr on December 12, 2020, 03:57:17 PM
Hi guys, thank you for this wonderful forum. I am a new ML user. I apologize in advanced if this question is given already. I did search the forum but am having a hard time finding the answer. Is the Eos 700D able to shoot in 50fps in 1080p? I really need to know this. Thank you so much in advance. :)

Hello!

If you mean 1080p50 in H.264, no you can't (reason: hardware limitations), however:
700D doesn't record native 1920x1080 resolution in H.264, it's actually upscale 1736x976 to 1920x1080 in H.264, so now if your question was " Can we record 1736x976 @ 50 FPS in RAW? "

Kind of, with limitations, the sensor support up to 1736x970 @ 50 FPS:

-You have to record in uncompressed RAW to avoid corrupted frames, @ 10-bit uncompressed the write speed would be 100 MB/s
-You will have stretched LiveView

This can be achieved in crop_new

You're welcome

Quote from: theBilalFakhouri on January 04, 2021, 11:49:15 PM
@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 (https://www.magiclantern.fm/forum/index.php?topic=12862.0).

6- This issue has been discussed here  (https://www.magiclantern.fm/forum/index.php?topic=5951.msg231838#msg231838)

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?

Hi. Is H264 cropped recording available on 700D or 650D? 1:1 or 1:3 with binning?

Supported cams: https://builds.magiclantern.fm/features.html -> Movie -> CROP_MODE_HACK

Thanks. 1x3 binning works for H264 too, right? What about live preview while recording? How good is it? Does hdmi preview work in this mode?

Looks like 1:1 to me.

Quote from: far.in.out on March 28, 2021, 12:49:05 AM1x3 binning works for H264 too, right?

Looks like 1:1 to me.

Quote from: far.in.out on March 28, 2021, 12:49:05 AMWhat about live preview while recording? How good is it?

Unsure what you want to know. I get a 3x electronically zoomed frame in 16:9 which fills display horizontal. Both in idle and during recording.

Quote from: far.in.out on March 28, 2021, 12:49:05 AM
Does hdmi preview work in this mode?

If you want to ask what I get via HDMI: Looks like 1620x912 embedded in 1920x1080 and it is the same content (apart from overlays) shown by display when HDMI is not connected.

Quote from: far.in.out on March 28, 2021, 12:49:05 AM
Thanks. 1x3 binning works for H264 too, right? What about live preview while recording? How good is it?

No. 1x3 recording can work in RAW only. Liveview is realtime.

Thanks guys. One last question - when recording in H264 1:1 crop mode, what resolution is it reading from the sensor? Is it 1920x1080 or is it something less than that and it gets upscaled?

I was initially thinking of getting the 600D for it's aliasing free 3x zoom mode for H264. But then I saw the latest progress on RAW and the fact that you can now shoot aliasing free RAW with a crop factor of 2 on several cams. So I'm willing to give RAW another shot while having cropped H264 as a fall back. So that makes 700D a good choice I guess. No point in getting 600D any more.

Quote from: far.in.out on March 28, 2021, 11:36:18 PM
Is it 1920x1080 or is it something less than that and it gets upscaled?

https://wiki.magiclantern.fm/glossary#native_resolution

Thanks Walter. It looks like the wiki is about the full sensor mode. Is it the same case with cropped H264?

Quote from: far.in.out on March 29, 2021, 12:06:26 AM
Is it the same case with cropped H264?

Do the math on your own, please!
(https://abload.de/thumb/mvi_0024-1nujke.png) (https://abload.de/image.php?img=mvi_0024-1nujke.png)
(https://abload.de/thumb/mvi_0025-1bgjdg.png) (https://abload.de/image.php?img=mvi_0025-1bgjdg.png)
Pics taken with 650D.

OK, millimeters from your pics (425/141) have a ratio of 3.014184397.
While full horizontal sensor res divided by 1920 (5184/1920) is 2.7.
But I don't think this is a reliable way of checking if there's upscaling going on.  :D

Hm, after looking at it for some time I don't see how cropped horiz res can be more than 1/3 of full sensor res, which is 1728.

hi,
thanks for the bilal's crop_rec_4k, I installed it few days ago. This is my first camera I bought.
I still confuse actually for the setting when switching between photo and video.. :P
for instance if I set on crop rec new in video mode with 1x3 binning then switch to photo mode the preview zoomed a bit like in video mode, is it normal?
and if I set the crop mode ON the preview always zoomed. How to get actual preview like normal recording? Thanks.

sorry for my bad english  :)

hi again,
after I tried several times now I understand a bit.  :D
when I choose preset the preview looks perfect, I tried UHD 1x3 Anamorphic 1280x2160
as described here https://www.magiclantern.fm/forum/index.php?topic=25323.25

I think this is more than enough for me to take some footage.. @theBilalFakhouri you're great!

btw.. the black bar is not always black sometimes it turn like pink zebra flickering and sometimes the preview doesn't change between normal and zoom.

thanks.

Hi again..  :D
I have a problem when the crop_rec is ON then switch to Photo mode and take a photo, the camera got busy quiet long until I turn off and open the battery lid.. I don't know if it's right or not.. but I tried several times it turned out to be the same.

Hello @ML700D :D!

Sorry for the delay, glad you liked the build ;D

Quote from: ML700D on March 31, 2021, 01:28:17 PM
..
for instance if I set on crop rec new in video mode with 1x3 binning then switch to photo mode the preview zoomed a bit like in video mode, is it normal?
and if I set the crop mode ON the preview always zoomed. How to get actual preview like normal recording? Thanks.
..

Quote from: ML700D on April 17, 2021, 02:25:19 PM
..
I have a problem when the crop_rec is ON then switch to Photo mode and take a photo, the camera got busy quiet long until I turn off and open the battery lid.. I don't know if it's right or not.. but I tried several times it turned out to be the same.

Thanks for reporting, Crop mode module should be disabled in Photo mode to avoid Zoomed preview and "Busy" state when capturing photos, currently you can do it manually, just set "Crop mode" to "OFF", I will prevent "Crop mode" from being ON when we in Photo mode, and will release a new build.

Quote from: ML700D on April 06, 2021, 07:30:45 AM
..
btw.. the black bar is not always black sometimes it turn like pink zebra flickering ..
..

The bottom part of preview would have some flickering and weird patterns in presets which have correct real-time previews, this is normal, current solution is to make sure Global Draw is ON, and use mlv_lite module, this will draw black box on this flickering area.

Quote from: ML700D on April 06, 2021, 07:30:45 AM
..
.. and sometimes the preview doesn't change between normal and zoom.
..

I need to know your camera settings to reproduce the issue, which preset have you used? are you in Video mode? which modules are enabled?

You may want to share a video including what are you doing, this make things easier to reproduce the issue.

Hello @lightwriter

Sorry for the delay:

Quote from: lightwriter on January 10, 2021, 09:25:26 PM
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?

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.

Quote from: lightwriter on January 10, 2021, 09:25:26 PM
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?

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.

Quote from: theBilalFakhouri on April 17, 2021, 09:39:32 PM
Hello @ML700D :D!

Sorry for the delay, glad you liked the build ;D

Thanks for reporting, Crop mode module should be disabled in Photo mode to avoid Zoomed preview and "Busy" state when capturing photos, currently you can do it manually, just set "Crop mode" to "OFF", I will prevent "Crop mode" from being ON when we in Photo mode, and will release a new build.

Ohh.. Ok. thanks  :D

Quote
The bottom part of preview would have some flickering and weird patterns in presets which have correct real-time previews, this is normal, current solution is to make sure Global Draw is ON, and use mlv_lite module, this will draw black box on this flickering area.

If Global Draw is ON the preview looks jittery
I use mlv_lite module.

Quote
I need to know your camera settings to reproduce the issue, which preset have you used? are you in Video mode? which modules are enabled?

I use crop mode UHD Anamorphic 1x3 preset and some setting that you recommended in video mode
the module are mlv_lite, crop_rec, crop_new, dual_iso, ettr and sd_uhs

for first time use without changing the setting is fine then when changing the setting the issue usually comes as I mentioned before, especially change the crop mode setting, even though I've pressed the menu 2x.

Quote
You may want to share a video including what are you doing, this make things easier to reproduce the issue.

https://drive.google.com/file/d/1NRyvbrVhebr3zKLdayeebNtajPmEM4hS/view?usp=sharing

aahh...I just realized the problem is when the global draw is ON.

Quote from: ML700D on April 19, 2021, 09:15:27 AM
If Global Draw is ON the preview looks jittery
I use mlv_lite module.
..
I use crop mode UHD Anamorphic 1x3 preset and some setting that you recommended in video mode
the module are mlv_lite, crop_rec, crop_new, dual_iso, ettr and sd_uhs
..
https://drive.google.com/file/d/1NRyvbrVhebr3zKLdayeebNtajPmEM4hS/view?usp=sharing

aahh...I just realized the problem is when the global draw is ON.

To solve these problems, you need to use Canon preview, highlight "Raw video" --> Press Q button --> Preview --> set it to "real-time"

Now, everything would work as expected ;D

Quote from: theBilalFakhouri on April 19, 2021, 10:35:15 AM
To solve these problems, you need to use Canon preview, highlight "Raw video" --> Press Q button --> Preview --> set it to "real-time"

Now, everything would work as expected ;D

Nice! thank you..  :D

Quote from: theBilalFakhouri on April 17, 2021, 09:57:38 PM
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.

is it like mine? When I use shutter 1/50 on canon setting but on ml preview is wrote 1/26.

Yes, shutter speeds shows as stuck value or incorrect value in ML menu.

ooh.. I see, thanks.

Hello theBilalFakhouri,

I've got crash this day, I don't know why.
here I attach the crash log file: https://drive.google.com/file/d/140IBe4k-8p4F-TeIAxazwtAEE5fr25EV/view?usp=sharing (https://drive.google.com/file/d/140IBe4k-8p4F-TeIAxazwtAEE5fr25EV/view?usp=sharing)

but the camera run normal again after I turn off and open the battery.

hello again,

@theBilalFakhouri sorry to ask..
can the crop mode be integrated into the raw video menu?
because I had experience when I turn off the raw video but forget turn off the crop mode, to get normal video shoot, the camera freeze..

Hi @ML700D

Two requested changes you asked for are done, I will try to release as soon as possible:

1- crop_rec won't be patched in Photo mode.
2- crop_rec only would has effect when RAW video is ON, turning OFF RAW video would disable "Crop mode", and you can record H.264 safely, not of my crop_rec presets works in H.264 anyway.

Other changes for the coming build:

1- mlv_lite: Fixed ML Framing preview when not using real-time correct preview presets.

2- crop_rec: Canon overlays are disabled when using crop modes with real-time correct preview (Enhanced experience).
    crop_rec: ML global draw top bar would go to the bottom automatically when using crop modes with real-time correct preview and vice-versa (Enhanced experience).
    crop_rec: Pressing Half-Shutter in Idle would switch preview to Canon x10; to quickly check focus.
    crop_rec: Added Full-Resolution LiveView preset (5208x3478 @ 2 FPS).

3- crop_new: Enhanced LiveView automatic refreshing after applying new settings or when enabling/disabling the module.
    crop_new: Press SET button in LiveView to refresh LiveView manually.
    crop_new: Added selectable FPS option.

wow.. nice, thanks a lot..  :D

Nice news Bilal!

Thanks!

Quote from: theBilalFakhouri on April 17, 2021, 09:57:38 PM
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!

Hello!

New Build uploaded for 650D/700D, you can find it in first post:
https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049

Changes posted here:
https://www.magiclantern.fm/forum/index.php?topic=25784.msg235480#msg235480

I have just re-uploaded the 650D build, missed something, re-download it again.

Again, sorry! I have just re-uploaded the "crop_rec_4k.2021May24.700D115_Shutter_Blanking" build, missed something, please re-download it again from the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049)!

If you curios: I am using crop_rec_4k branch, when compiling an old version of mlv_snd gets included in the build, I have to replace it manually each time, not a huge thing, will try to update mlv_snd code in crop_rec_4k branch, currently you have the latest mlv_snd in my builds, so don't worry about it and have fun!

Quote from: theBilalFakhouri on May 24, 2021, 01:19:43 AM
Hello!

New Build uploaded for 650D/700D, you can find it in first post:
https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049

Changes posted here:
https://www.magiclantern.fm/forum/index.php?topic=25784.msg235480#msg235480

wow.. thanks. I will try it soon  :D

Hi,
I'm using the last 700d's build for "shutter blanking issue" and audio is not recorded.
Maybe i'm doing something wrong.
Audio module is loaded and on.
I did a test with the "regular" build and audio works fine.

Thanks.

Quote from: zandette974 on May 29, 2021, 08:43:26 AM
Hi,
I'm using the last 700d's build for "shutter blanking issue" and audio is not recorded.
Maybe i'm doing something wrong.
Audio module is loaded and on.
I did a test with the "regular" build and audio works fine.

Thanks.

Hello!

I don't have this issue, the sound gets recorded fine here with shutter blanking build.

More details are needed:

What modules are loaded, camera settings, which preset are you using?
Could share a picture for ML menu?

Note: I have re-uploaded that build (https://www.magiclantern.fm/forum/index.php?topic=25784.msg235561#msg235561) after few hours of the original upload, the new upload fix the sound recording compatibility issue, if you missed that, please re-download the build from the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) and test again.

Hi Bilal
I re-downloaded and everything is fine now.

Thank you

New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.0) for 650D/700D

Changes:

crop_rec:
-The preview in mlv_lite will change automatically to "real-time" when selecting presets with real-time correct preview. (some users are missing this step, now it's automatic)

-Added new "720p50 3x3" preset 1736x698 3x3 @ 50 FPS with correct un-stretched preview, this preset is included originally in the official crop_rec_4k builds (https://builds.magiclantern.fm/experiments.html) but without the preview fix, I didn't include 60 FPS option because of overhead and corrupted frames, at 50 FPS it works fine. The preview looks choppy but the recorded RAW data isn't affected.

-crop_rec won't be enabled when autofocus is ON

-Added warning messages to make everything clear in crop_rec

---

These from first post are no longer needed and have been removed:
...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  .
General notes:
-You need to disable autofocus when using crop_rec module (Important).
-Use "real-time" preview in mlv_lite submenu if you want to use crop_rec presets which support real-time correct preview for better experience.
...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  ...  .

Hello Bilal,
I have the latest build of yours installed on my 700D but I have a question. I am kind of confused from the different resolutions, formats and crops that are available. My question is what is the highest resolution I can shoot at without crop aka the highest quality the camera can offer without crop and with minimal alliasing

Dear Bilal!
Installed your firmware, installed SD card overclocking,
works well, thanks! Filmed without a crop, compressed at 14bit. On some shots, there is a sky, but it was pink. and there are frame drops, 1 or 2 for 30-40 seconds. 190 Mhz card. It may be my imagination, but the colors and dynamic range are better. Thank you! On the crop, of course, 18-55 is not very good quality. At 24 STM, the picture looks better both on crop and without it.

Уважаемый Билал!
Поставил вашу прошивку, установил разгон SDкарты,
работает хорошо, спасибо! Снимал без кропа, на 14bit сжатый. На некоторых шотах, есть небо, но оно было розовым. и есть пропуски кадров, 1 или 2 на 30-40 секунд. Карта на 190 Mhz.  Может это мое воображение, но цвета и динамический диапазон стали лучше. Спасибо! На кропе конечно 18-55 не очень качество. На 24 STM картинка выглядит лучше и на кропе и без него.

Hello Saint!

If you want me to check why the sky was pink, please provide short MLV sample for that clip, you can cut the MLV file inside MLVApp using "Cut In & Cut Out" tab, two frames are enough, then export it into MLV file, set the "Codec" inside "Export Settings" window to "MLV" "Fast Pass", and upload the sample and give me the link.

I don't have the pink sky issue, a common workarounds for this issue: don't use auto iso, try "Highlights Reconstruction" in "Processing" tab inside MLVApp, try lowering "RAW White Level" in "RAW Correction" tab also inside MLVApp with small steps.

---

To get continuous RAW recording in normal 1080p mode 3x3 (with no crop), depending on resolution, framerate and what aspect ratio you are using, you may want to use lower bit-depths like 12-bit lossless or 10-bit lossless, the overclock helps too, 192 MHz with Sandisk Extreme PRO UHS-I U3 95 MB/s is pretty good for most modes (~58 to ~61 MB/s Write Speed), Sandisk Extreme PRO UHS-I U3 170 MB/s with 240 MHz is the best (~68 MB/s Write Speed), as described in the first post.

Highlight "RAW video" in "Movie" tab inside ML Settings, you can see the a calculated required write speed in current mode in ML bottom bar, perform benchmarks test for your card in camera in current mode, load "bench.mo" module --> restart the camera --> "Debug" tab --> "Benchmarks" --> "Card Benchmarks" --> Quick R/W benchmark (1 min), you can see how your SD card performs.

---

If you want to get the best sharp images with 18-55 STM kit lens, you need to use f/5.6 at 18mm, and up to f/8 at 55mm (depending on my own tests), prime lenses are always better, I only have the 50mm 1.8 prime lens, so no much experience with wider focal length prime lenses, you may want to watch YT and see some reviews/advices . . etc.

Sorry for the long answer, glad you liked the build :D

Yes, I'll post a short piece. I am translating from MLV to DNG for Davinchi Resolve. Therefore, I do not do anything in MLV, because as I understand it, DNG is pure RAW. I tend to shoot at 24mm STM, from f / 5 to f / 16. M mode, ISO 100-400, rarely up to 800.
25 frames / sec. 1/50 s. 18-55 used only for crop, but soap is visible. Only now I realized that I removed all MLVs from the filming, only DNG remained. I'll try to catch it next time.
I'm afraid to run a speed test, because you sent a link about a person whose card is broken. And something tells me in my head that I also did the speed test then and it stopped working :-) So I'm AFRAID to do the test. :-)

Да, я выложу короткий кусочек. Я перевожу из MLV в DNG для Davinchi Resolve. Поэтому я ничего не делаю в MLV, потому что как я понял DNG это чистый RAW. Я стараюсь снимать на 24 мм STM, от f / 5 до f / 16. Режим М, ISO 100-400, редко до 800.
25 кадров / с. 1/50 с. 18-55 использовал только для кропа, но видно мыло. Только сейчас понял что я удалил все MLV со сьемки, остались только DNG. Попробую поймать в следующий раз.
Боюсь запускать тест скорости, так как вы прислали ссылку про человека у которого карта сломалась. И мне что то подсказывает в голове что я тоже делал тогда тест скорости и она перестала работать :-) Так что тест БОЮСЬ делать. Жалко карту :-)

Okay, you might prefer DNG for Davinci Resolve, no worries about the MLV clip with pink sky.

I see, if you are afraid to run SD benchmarks, don't do it, that's always up to you, doing anything related to ML is at your own risk.

Hello, everybody. I'm delighted that we've updated the firmware and made some positive changes. However, I'm concerned about the following:
In my last experimental firmware, I had the ability to configure the screen resolution so that in the editor of MLV App I had a picture like 2:35:1
https://pasteboard.co/K7e6M7f.png

In the current firmware, no matter how many times I've gone through the rabbi and crop settings - the height of the video cannot increase and in the application it is not 2214 pixels as before.
https://pasteboard.co/K7e7qv5.png

I like the firmware, but this is a problem for me. I have long wanted to use this very regime, because it creates the ideal balance of sides for my ideas.
I want a ratio 5208 by 2214 :)

(I used to change the following parameters:
Crop mode v2 and RAW video
https://pasteboard.co/K7e9vdG.jpg
But now the line of RAW video stays the same height)

Hello @Icaab

1736x2214 does work here, I didn't change anything regarding this, could you share a photo showing your camera settings? or a video showing what are you doing?

I found crop_rec may conflict with crop_new sometimes if both loaded in some cases resulting in crop_new (Crop mode V2) won't apply the selected settings, in this case try turning off "Crop mode V2", press menu button twice in LiveView, or toggle between 1080p and x5 modes by pressing magnification button several times, turn on "Crop mode V2" again, does it work?

Make sure you are getting 1736x2214 resolution from mlv_lite (RAW video) before recording . .

Ok, I think I found what is happening, will release a new builds soon might fix this problem (currently unload crop_rec module if you want to use crop_new).

New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.0) for 650D/700D

Changes:

crop_rec:
-Switching between presets now is faster
-Fixed a conflict with crop_new which made "Crop mode V2" in most cases has no effect
-Some code optimizations

RAW video with HDMI:

-Fixed a regression introduced back in "11 Dec, 2016" by this pull request (https://foss.heptapod.net/magic-lantern/magic-lantern/-/merge_requests/778/commits), regression symptoms:
(These symptoms happen when the camera is connected to HDMI monitor, no matter what's the output):

-LiveView freezes after recording some RAW video clips, or when toggling between mv1080 and x5 modes when RAW video is enabled
-Weird flickering/glitches in LiveView when the camera startups up with RAW video enabled

This issue is still presented in official Nightly builds, and probably all of DIGIC 5 cameras are affected, maybe except 5D3, (this issue isn't related to HDMI overhead things).

Some details:
ML use EDMAC write channel #18 for RAW data stream (something related to RAW video recording), back then a1ex asked the developers to find a none-used channel by Canon firmware for each model, channel #18 was available (and worked across all models except for 5D3 1.2.3 (https://www.magiclantern.fm/forum/index.php?topic=10443.msg100979#msg100979)), so we have used it for years . . without a problem, until some days ago I found out this channel is being used by Canon when connecting the camera (my 700D) to HDMI monitor and causes the issues above . .

Well, I started looking for another available EDMAC write channel, I found channel #3 being the best, not used by Canon in anything? (Not used in HDMI, capturing still images, recording H.264, and so) beside channel #3 didn't introduce corrupted frames, same performance as #18 channel in addition to no issues with HDMI connection :).

Cool. You've been busy lately :). Would be nice adding some of this to eos m. How would I change edmac channel and hdmi fixes?

Quote from: theBilalFakhouri on June 19, 2021, 03:57:47 AM
New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.0) for 650D/700D

Changes:

crop_rec:
-Switching between presets now is faster
-Fixed a conflict with crop_new which made "Crop mode V2" in most cases has no effect
-Some code optimizations

RAW video with HDMI:

-Fixed a regression introduced back in "11 Dec, 2016" by this pull request (https://foss.heptapod.net/magic-lantern/magic-lantern/-/merge_requests/778/commits), regression symptoms:
(These symptoms happen when the camera is connected to HDMI monitor, no matter what's the output):

-LiveView freezes after recording some RAW video clips, or when toggling between mv1080 and x5 modes when RAW video is enabled
-Weird flickering/glitches in LiveView when the camera startups up with RAW video enabled

This issue is still presented in official Nightly builds, and probably all of DIGIC 5 cameras are affected, maybe except 5D3, (this issue isn't related to HDMI overhead things).

Some details:
ML use EDMAC write channel #18 for RAW data stream (something related to RAW video recording), back then a1ex asked the developers to find a none-used channel by Canon firmware for each model, channel #18 was available (and worked across all models except for 5D3 1.2.3 (https://www.magiclantern.fm/forum/index.php?topic=10443.msg100979#msg100979)), so we have used it for years . . without a problem, until some days ago I found out this channel is being used by Canon when connecting the camera (my 700D) to HDMI monitor and causes the issues above . .

Well, I started looking for another available EDMAC write channel, I found channel #3 being the best, not used by Canon in anything? (Not used in HDMI, capturing still images, recording H.264, and so) beside channel #3 didn't introduce corrupted frames, same performance as #18 channel in addition to no issues with HDMI connection :).

Thank you very much for such a fast feedback. I downloaded the firmware and tried it. Yes, the switching problem has gone away, but the main problem I've always had to worry about with the cropping regime has not been solved:
There is no convenient height in the frame when you preview. This can be eliminated by turning on another preview mode, but for the filming of important work, this is not all and will only cause total discomfort.
For convenience, I flooded the phone footage of the camera settings. There's a preview comparison between the first crop of fashion and the second one, and you can also see the problem of the shutter value, which when changed on the screen remains in terms of its numerical value the same
https://mega.nz/file/F9AzmAwK#2Lx44NfjflSKbrUJMFdB4bjzfavNFw2OQ9KrxCOMvWM

Hello @Danne

I have updated the source code, you will find it in the first post if you want to take a look there, it's really easy,

To change EDMAC write channel for RAW stream from edmac-memcpy.c file:

#if defined(CONFIG_5D3)
uint32_t raw_write_chan = 0x4;  /* 0x12 gives corrupted frames on 1.2.3, http://www.magiclantern.fm/forum/index.php?topic=10443 */
#elif defined(EVF_STATE)
uint32_t raw_write_chan = 0x12; /* 60D and newer, including all DIGIC V */
#endif

Change it from:
uint32_t raw_write_chan = 0x12; /* 0x12 = channel #18 */ to uint32_t raw_write_chan = 0x3; /* 0x3 = channel #3 */

Not sure if channel 0x3 would work fine on EOS M you need to make tests, check channel activity with edmac.mo module, unload all modules, load edmac.mo, if channel #3 stays like this "0:     <w!>" what ever you do (Capture still photo, record H.264 video, connect HDMI monitor) then this channel isn't being used by Canon at these cases (that's what we need), now compile a build with 0x3 channel if you didn't, try recording RAW video in high frame rates like 1736x586 @ 60 FPS in lossless, try other crop modes, and look if there a corrupted frames or not compared to when using channel #18

Some channels appear to produce more corrupted frames than others, luckily channel #3 have same performance as channel #18 and without HDMI and RAW video issues :) .

Quote from: Icaab on June 19, 2021, 11:01:23 AM
..but the main problem I've always had to worry about with the cropping regime has not been solved:
There is no convenient height in the frame when you preview. This can be eliminated by turning on another preview mode.

From the first post:

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM
-Crop mode V2 module (crop_new) with Arbitrary Resolutions:
...
...
-This module doesn't include any recent preview fixes.

Currently if you want to use 1x3 modes with real-time correct preview you need to use crop_rec "Crop mode", and unfortunately there is no 5K option (*5208x2214), there is 4.3K (*4320x1836) 2.35:1 AR.

*After stretching.

Implementing real-time correct preview in crop_new "Crop mode V2" requires further research and time, processing 1736x2214 in LiveView might not be possible, even if it was possible we may have another problems like corrupted frames due to hardware limitations and limited memory or limited memory bandwidth.

Quote from: Icaab on June 19, 2021, 11:01:23 AM
..and you can also see the problem of the shutter value, which when changed on the screen remains in terms of its numerical value the same..

Okay, I will release two builds for 650D like 700D, this issue affects some 650D users , will try to release a second new build for 650D ASAP solves shutter issue.

Quote from: theBilalFakhouri on June 19, 2021, 04:31:45 PM
From the first post:

Currently if you want to use 1x3 modes with real-time correct preview you need to use crop_rec "Crop mode", and unfortunately there is no 5K option (*5208x2214), there is 4.3K (*4320x1836) 2.35:1 AR.

*After stretching.

Implementing real-time correct preview in crop_new "Crop mode V2" requires further research and time, processing 1736x2214 in LiveView might not be possible, even if it was possible we may have another problems like corrupted frames due to hardware limitations and limited memory or limited memory bandwidth.

Thank you. Sorry to bother you with the same question. I wanted to finally wait for the correction of this moment to finally start shooting what I wanted). But I guess I'll have to work with 4.3k in crop mode 1. And I fully believe that crop mode 2 is more likely to have a good source than the first )

Alex and you all are magicians, making 10-year old consumer level still cameras competing with the latest crop of professional video cameras, disrupting the whole Hollywood business. Kudos to you.
I want to not only compete with the big brothers like Red Weapon and Alexa LF, but also to beat them. I am using Alex's crop2 to get 1x3 5200x1160, i.e., 1736x1160, so it has an aspect ratio of 5:1. The 650D can do this at 10-bit raw 23.975 fps continuously, about 57 MB/s. The preview is good, I can use either raw video module to get the wide and narrow correct frame view or use raw video mlv module to get the full screen anamorphic preview which I think is better in this case because it uses the whole screen space. I like the aspect ratio 5 footage. The problem is the color taint. There is severely color taint in footage. Hopefully the color taint can be removed somehow to make this mode practical. Thanks a lot.

I did some concept testing. Using Alex's crop2 new module, set full width 1x3, 1736x1947, i.e., 5200x1947, aspect ratio: 2.67. Bit rate: 10. Using raw video module, 14 bit lossless. It is about 64 MB/s. If ISO is set to 100 to 200, this mode can be continuous. If 400-800, can be over 1 minute. It seems that even going up to 6400, the digital noise does not increase drastically. This is different from 5d3, which has a flat low digital noise at <ISO 3200, but increases rapidly at 6400, and drastically so at 12800 and 25600, rendering the ISO >6400 practically not usable.
Hopefully, color taint can be removed in this mode. Also, using Alex's crop2 new module, the AF does not need to be disabled. However, the crop module requires the lens to turn off the AF.

I tested in Alex's crop new module full width 1:3 1736x1736 aspect ratio 3. I can do 10 bit 14-bit lossless 24 p continuously. The data is about 56 MB/s. There is color taint, sometimes red in darkness sometimes green in darkness.

@mlrocks

There is only color tint/taint in LiveView when using lower bit-depths from crop_rec/crop_new submenu, this in normal and doesn't affect RAW footage

Let me check what you are having by providing a sample MLV file which has the taint issue, 5 seconds are enough, you can shorten MLV clip in MLVApp (export as MLV fast pass) then upload it somewhere and share the link

---

ISOs which are above 3200 are digital on 650D/700D and won't improve shadows it will just make noise more visible, there is a tiny (not noticeable) improvement between ISO 1600 and 3200 ISO, it better to keep ISO lower than 1600 for the best results in general on these cameras

@Icaab

It seems only your 650D has shutter value issue (first reported 650D), so we need to check shutter blanking addresses from your camera, but before doing that I want you to check if Danne crop_rec_4k build for 650D have the same issue on your 650D, try this build from Danne (outdated build, no longer maintained), but it would be useful for our test:
crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr29.650D104.zip (https://web.archive.org/web/20200812191122/https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr29.650D104.zip)

Test it and feedback, does it have shutter issue?

Also, does Dual ISO work on your 650D? or it give ISOless errors?

I have the shutter problem as well on the Canon 700D and Iso here in the UK, but with the right build it works really well, thanks Bilal

I use autofocus and I have no ability use the crop_mode in the last version with autofocus, but I could use it in the previous one (crop_rec_4k.2021May24.650D104.zip )
Bilal, would you please add the trigger anywhere in submenu to enable crop_mode menu with autofocus, maybe unchecked by default.

Quote from: theBilalFakhouri on June 24, 2021, 04:09:24 AM
@Icaab

It seems only your 650D has shutter value issue (first reported 650D), so we need to check shutter blanking addresses from your camera, but before doing that I want you to check if Danne crop_rec_4k build for 650D have the same issue on your 650D, try this build from Danne (outdated build, no longer maintained), but it would be useful for our test:
crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr29.650D104.zip (https://web.archive.org/web/20200812191122/https://bitbucket.org/Dannephoto/magic-lantern/downloads/crop_rec_4k_mlv_snd_isogain_1x3_presets_2019Apr29.650D104.zip)

Test it and feedback, does it have shutter issue?

Also, does Dual ISO work on your 650D? or it give ISOless errors?

Yes, I have problems with double ISO, therefore I do not use it (isoless error)

I put the firmware you suggested. The Dual ISO started to work, and the problem with shutter value - did not disappear (this manifested when included modules for shooting in RAW ).

Quote from: theBilalFakhouri on June 24, 2021, 04:09:24 AM
@Icaab
Also, does Dual ISO work on your 650D? or it give ISOless errors?

I have the ISOless PH err(2) error with Dual ISO on my 650d, but it seems there is the solution

Quote from: Roger2004 on September 16, 2014, 01:02:27 PM
-The ISOless PH err(2) is still there when i activate Dual ISO in M Mode. Starting in P mode and then moving to M mode works.

Quote from: alt1 on June 25, 2021, 11:29:45 AM
I have the ISOless PH err(2) error with Dual ISO on my 650d, but it seems there is the solution

Thank you for your decision. I hope they will correct this error in the new update.

Hello. I have a question: I understand perfectly well how to use the modules for shooting in Crop mode and RAW, but again, I would like to clarify the profile for the camera:
When shooting with such modules - the profiles do not work and we get the image in RAW as you see when the standard style is turned on ,but there is a certain sharpness there.
I take it I have to put it down at the very least, so the video can be even better for post-production? Or does it not make any sense and in RAW format still comes a certain sharpness?
https://ibb.co/NTDHPs3

And one more question:
In my artistic design, it is necessary to shoot in the scene a computer monitor turned on.
When you look at the footage, you see a little aliasing on the monitor.
(I shoot and in 1x3 and procedure in MLVApp, as is required, so that in other cases the muar and aliasing do not manifest)
Can do anything other than buy optical low pass filter?

Quote from: bern047 on June 24, 2021, 03:19:58 PM
I have the shutter problem as well on the Canon 700D and Iso here in the UK, but with the right build it works really well, thanks Bilal

Welcome :)

Quote from: alt1 on June 24, 2021, 08:17:04 PM
I use autofocus and I have no ability use the crop_mode in the last version with autofocus, but I could use it in the previous one (crop_rec_4k.2021May24.650D104.zip )
Bilal, would you please add the trigger anywhere in submenu to enable crop_mode menu with autofocus, maybe unchecked by default.

Yeah, I disabled the ability to use autofocus when crop_rec "Crop mode" is ON due to stability reasons, which modes you want to use autofocus with?

Autofocus might be stable only with 1440p 1:1 and 3K 1:1 modes, so I may re-enable autofocus with these modes.

---

Quote from: Icaab on June 25, 2021, 10:31:31 AM

Yes, I have problems with double ISO, therefore I do not use it (isoless error)

I put the firmware you suggested. The Dual ISO started to work, and the problem with shutter value - did not disappear (this manifested when included modules for shooting in RAW ).

Okay, we need to check your camera shutter registers addresses, I will write another post regarding this and how to it.

Quote from: Icaab on June 28, 2021, 11:28:38 PM
Hello. I have a question: I understand perfectly well how to use the modules for shooting in Crop mode and RAW, but again, I would like to clarify the profile for the camera:
When shooting with such modules - the profiles do not work and we get the image in RAW as you see when the standard style is turned on ,but there is a certain sharpness there.
I take it I have to put it down at the very least, so the video can be even better for post-production? Or does it not make any sense and in RAW format still comes a certain sharpness?
https://ibb.co/NTDHPs3

Picture style doesn't affect RAW data, only H.264 video and LiveView

Quote from: Icaab on June 29, 2021, 09:58:02 AM
And one more question:
In my artistic design, it is necessary to shoot in the scene a computer monitor turned on.
When you look at the footage, you see a little aliasing on the monitor.
(I shoot and in 1x3 and procedure in MLVApp, as is required, so that in other cases the muar and aliasing do not manifest)
Can do anything other than buy optical low pass filter?

Shooting a monitor is a nightmare for cameras, popular solution is to make the monitor out of focus (using camera lens) a bit, but in your case there are many subjects in the frame, so you probably need to change monitor position, or use a wider aperture . .

1:1 modes (have higher crop) might help to reduce aliasing/moire on monitor . . I have no idea if optical low pass filter can deal with monitor aliasing/moire . .

Quote from: theBilalFakhouri on June 29, 2021, 01:44:21 PM
Welcome :)

Yeah, I disabled the ability to use autofocus when crop_rec "Crop mode" is ON due to stability reasons, which modes you want to use autofocus with?

Autofocus might be stable only with 1440p 1:1 and 3K 1:1 modes, so I may re-enable autofocus with these modes.

---

Okay, we need to check your camera shutter registers addresses, I will write another post regarding this and how to it.

Picture style doesn't affect RAW data, only H.264 video and LiveView

Shooting a monitor is a nightmare for cameras, popular solution is to make the monitor out of focus (using camera lens) a bit, but in your case there are many subjects in the frame, so you probably need to change monitor position, or use a wider aperture . .

1:1 modes (have higher crop) might help to reduce aliasing/moire on monitor . . I have no idea if optical low pass filter can deal with monitor aliasing/moire . .

Thank you.
I'm going to do a different composition, and I'm going to use focus advice to shoot the monitor.

Hello. I have a problem: if you try to record a video with a microphone (boya by-m1) connected, the recording of the sound is disabled during the recording. Without a microphone, the sound is recorded and included in the raw settings.
(It's probably not a firmware problem, but I don't have any way to test it with another device right now. That's why I'm interested, just in case.)

The problem was easily resolved. You can delete this unnecessary message :).

Bilal, sorry to ping you in the wrong thread, but did you get any luck obtaining ArcziPL's source code? I would really love to see your work combined for a better 70D experience.

@Icaab

Okay, cool :) , well, I can't really delete replies or posts for other users, that's a moderator role, no problem with keeping your reply.

---

Quote from: elenhil on July 12, 2021, 06:43:57 PM
Bilal, sorry to ping you in the wrong thread, but did you get any luck obtaining ArcziPL's source code? I would really love to see your work combined for a better 70D experience.

Hello @elenhil, feel free to ask anytime . .

I got the source code from ArcziPL yes, but I can't really do much for 70D without having the hardware, at some point I was going to borrow 70D for some time, but plans changed, I don't mind working on 70D if I got the body.

I think higher resolutions in 1:1 and 1x3 are possible on 70D, but I have no idea if we can get real-time correct preview for 1x3 modes, I need to take a closer look, e.g 5D3 is different from 700D which means 5D3 need a new understanding about how preview works, 70D might be similar to 700D (easy) or 5D3 (currently difficult).

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?

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 (https://builds.magiclantern.fm/jenkins/job/iso-research/14/artifact/modules/adtg_gui/adtg_gui.mo)
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)
(https://i.ibb.co/SvfRwBm/Shutter-Blanking-Add.png)

Do the same thing for the second register, and give me the numbers

Quote from: theBilalFakhouri on July 21, 2021, 08:31:50 PM
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 (https://builds.magiclantern.fm/jenkins/job/iso-research/14/artifact/modules/adtg_gui/adtg_gui.mo)
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)
(https://i.ibb.co/SvfRwBm/Shutter-Blanking-Add.png)

Do the same thing for the second register, and give me the numbers

Yes, there is a little problem with it: I stopped using it because the real-time preview is transmitted distorted, flattened. (pixel binning 1x3)

Posting photos of registers:
(https://i.ibb.co/H449R19/1627151288002.jpg) (https://ibb.co/wgg2832)
(https://i.ibb.co/hV8ZFdN/1627151288010.jpg) (https://ibb.co/jD4WkwY)

Quote from: Icaab on July 24, 2021, 08:32:52 PM
Yes, there is a little problem with it: I stopped using it because the real-time preview is transmitted distorted, flattened. (pixel binning 1x3)

You asked for time-lapses, "Crop mode V2" is the perfect module for that, for preview you must use "Framing" preview from "RAW video" submenu.

Which resolution are you looking for to do time-lapses?

As far as I know, EOS M has 4080x3000 preset for time-lapses with real-time cropped preview (x5 preview), this preview would be valid for focusing but not for framing, in "Crop mode V2" x10 preview isn't patched you can use it for focusing before recording, then get back to x1 or x5 mode with "Framing" preview and start recording your time-lapse, I tried it and it works fine . .

Are you looking for something else maybe I am missing? please describe it with details or give me a link showing it so I can improve my future builds . .

---

Thanks for the pictures, weird, the addresses from your camera is exactly what we are using in our 650D custom builds (Me and Danne), the two builds had issue with shutter value in ML settings on your 650D.

Not sure why the stuck shutter problem is only presented on your 650D, doesn't make sense . . I will try to see if I can do something about it.

Edit: Do you have the shutter problem both in none-crop and crop modes? e.g. unload all modules, restart the camera, select 1080p24 from Canon menu, do you have shutter issue? now get into x5 mode by pressing zoom button, do you have shutter problem in this mode?

Use FPS override to 12 FPS in both 1080p and x5 mode, same problem?

New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) for 650D/700D

Changes:

crop_rec:
-Fixed a regression with "720p50 3x3" preset, now it works fine.

Hi everyone I'm new to posting.

On my T4i/650d with your crop_rec_4k latest build I get the shutter issue and ISOless LV err(2)

While having the shutter issue, these were the photos of my ADTG registers:

ADTG2[805f] N -> 4049fa18
(http://ibb.co/b2Cby16)

ADTG2[8061] N -> 4049fa1c
(http://ibb.co/ynQK3DZ)

Hi @NykkyC, thanks for the values, try this build:

crop_rec_4k.2021Jul27.650D104_Shutter_Blanking.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Jul27.650D104_Shutter_Blanking.zip)

Does the shutter issue solved?

@Icaab
Does this build works on your 650D without the shutter issue?

---

@NykkyC

Let's try to solve ISOless LV err(2) on your 650D:

1- Download adtg_gui module from here (https://builds.magiclantern.fm/jenkins/job/iso-research/14/artifact/modules/adtg_gui/adtg_gui.mo)
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 CMOS[X] registers, you need to find one register which is:

-CMOS[0]

(https://i.ibb.co/cbbts6p/VRAM0.png)

We need to check CMOS[0] address multiple times, in video mode at 100 ISO and 200 ISO, also in photo mode at 100 ISO and 200 ISO . .

1- Let's start with Video mode:

Set the camera to video mode, set the ISO to 100, check CMOS[0] address in white box (write it down), now change the ISO to 200, check CMOS[0] address again and write it down.

2- Set the camera to none still Photo mode:

Set the ISO to 100, take a picture (important), check CMOS[0] address and write it down, now change the ISO to 200, take a picture (important), check CMOS[0] address again and write it down.

Now share the values you got here for each mode and ISO, and let me check them . .

Quote from: theBilalFakhouri on July 27, 2021, 04:27:36 PM
Hi @NykkyC, thanks for the values, try this build:

I have tested the crop_rec_4k.2021Jul27.650D104_Shutter_Blanking build and It did not solve the issue.

The ADTG registers for CMOS[0]:

1 - ISO 100: 404a048e or 404a038e / ISO 200: 404a04b0 or 404a03b0

2-  ISO 100: 404a048e or 404a038e / ISO 200: 404a04b0 or 404a03b0 (Not sure if I did this correctly, what do you mean by "Set the camera to none still Photo mode"?)

Quote from: theBilalFakhouri on July 27, 2021, 04:27:36 PM
Hi @NykkyC, thanks for the values, try this build:

crop_rec_4k.2021Jul27.650D104_Shutter_Blanking.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Jul27.650D104_Shutter_Blanking.zip)

Does the shutter issue solved?

@Icaab
Does this build works on your 650D without the shutter issue?

---

I tried your first tips. Shutter speed with some modules does not work, as I noticed when they were turned off. (looks like most of it)

Installed your new firmware. Without modules included, everything works, and how it turned them on is the same problem.

But there is a way around it: go into photo mode. Shutter speed is displayed correctly.

I added a piece of text in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) which is "-Loading the modules" to make things clearer for users.

I will try to respond for new replies soon, sorry for the delay.

Quote from: Icaab on August 03, 2021, 10:15:24 PM
I tried your first tips. Shutter speed with some modules does not work, as I noticed when they were turned off. (looks like most of it)

Installed your new firmware. Without modules included, everything works, and how it turned them on is the same problem.

But there is a way around it: go into photo mode. Shutter speed is displayed correctly.

Another way is to push the info button, go to the second layout, then you can see the actual shutter speed.

On 650D, I loaded the following modules,
bench
ettr
file_man
mlv_lite
mlv_play
mlv_snd
pic_view
sd_uhs
slient

I then:
1. activated the "movie crop mode" to "ON",
2. chose "Raw video" to "ON, 1800x1008", 10-bit, AR 16:9,
3. pushed the record button to record a raw video clip,
4. pushed the playback button,
5. the recorded video clip showed dark frames from the begin to the end.

In playback mode, I can see the video clips if they are recorded in 14-bit lossless compression.

I also tested mlv_rec.mo (raw video v2.0) on 650D for 1792x1008, 10-bit, AR 16:9. When I pushed the record button, it started to record. However, when I pushed the record button again to stop the recording, the stopping process did not go through. I had to turn off the camera to start another recording.

Quote from: mlrocks on August 17, 2021, 02:22:15 AM
..
2. chose "Raw video" to "ON, 1800x1008", 10-bit, AR 16:9,
3. pushed the record button to record a raw video clip,
4. pushed the playback button,
5. the recorded video clip showed dark frames from the begin to the end.

In playback mode, I can see the video clips if they are recorded in 14-bit lossless compression.
...

Currently mlv_play doesn't support uncompressed 10/12 bit RAW video playback in camera natively in all builds, it would give black screen, on PC the footage would be fine.
You need to activate raw_twk.mo module which add 10/12 bit playback support to mlv_play . . currently there is no raw_twk.mo in my builds, I will include it in the next release, but you can get it from here and put it and in "ML/modules" folder:
https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/raw_twk.mo

During my tests I found raw_twk.mo appears to produce corrupted frames in 700D when recording RAW video in some modes/settings, probably the module is being active in LiveView somehow and affect RAW stream, will make more tests in future and try to disable raw_twk.mo in LiveView, and make it only work in Play Mode, also there is some quirks when raw_twk is activated like you can't navigate mlv_play settings (toggling between clips, pausing playback and switching between color and fast preview . . etc).

Quote from: mlrocks on August 17, 2021, 02:22:15 AM
I also tested mlv_rec.mo (raw video v2.0) on 650D for 1792x1008, 10-bit, AR 16:9. When I pushed the record button, it started to record. However, when I pushed the record button again to stop the recording, the stopping process did not go through. I had to turn off the camera to start another recording.

I am having the same problem when using mlv_rec, it keeps saying "Stopping" but nothing happens, you have to pull the battery out/turn the camera off after that, there is no point to use mlv_rec (maybe only for the metadata?), currently just use mlv_lite and it has all what you might need.

Edit: it seems I don't have the latest mlv_rec.mo in my builds, will update it in the next release and this might solve the problem.

Quote from: theBilalFakhouri on August 17, 2021, 03:22:50 AM
Currently mlv_play doesn't support uncompressed 10/12 bit RAW video playback in camera natively in all builds, it would give black screen, on PC the footage would be fine.
You need to activate raw_twk.mo module which add 10/12 bit playback support to mlv_play . . currently there is no raw_twk.mo in my builds, I will include it in the next release, but you can get it from here and put it and in "ML/modules" folder:
https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/raw_twk.mo

During my tests I found raw_twk.mo appears to produce corrupted frames in 700D when recording RAW video in some modes/settings, probably the module is being active in LiveView somehow and affect RAW stream, will make more tests in future and try to disable raw_twk.mo in LiveView, and make it only work in Play Mode, also there is some quirks when raw_twk is activated like you can't navigate mlv_play settings (toggling between clips, pausing playback and switching between color and fast preview . . etc).

I am having the same problem when using mlv_rec, it keeps saying "Stopping" but nothing happens, you have to pull the battery out/turn the camera off after that, there is no point to use mlv_rec (maybe only for the metadata?), currently just use mlv_lite and it has all what you might need.

Edit: it seems I don't have the latest mlv_rec.mo in my builds, will update it in the next release and this might solve the problem.

Thanks for the explanation, theBilalFakhouri. I now use mlv record v1.1 10-bit and it is good enough. I unloaded the preview and playback and mlv record v2.0 modules. As long as the footage is fine on computer, it is fine for me.

Quote from: theBilalFakhouri on August 17, 2021, 03:22:50 AM

During my tests I found raw_twk.mo appears to produce corrupted frames in 700D when recording RAW video in some modes/settings, probably the module is being active in LiveView somehow and affect RAW stream, will make more tests in future and try to disable raw_twk.mo in LiveView, and make it only work in Play Mode, also there is some quirks when raw_twk is activated like you can't navigate mlv_play settings (toggling between clips, pausing playback and switching between color and fast preview . . etc).

You are right. I benchmarked before and after unloading the preview and playback modules. The write speed was about 58 MB/s with the modules loaded, and about 60 MB/s without the modules. I think that playback modules are secondary requests, the highest priority is to record high quality mlv raw footage. Thanks a lot for your codes.

@mlrocks

It seems "Stopping" issue when using mlv_rec is related to mlv_snd module, unload mlv_snd and mlv_rec would work fine, this problem probably introduced after adding mlv_snd support to mlv_lite (3 years ago) and hasn't been fixed, currently it's a low priority for me . . just use mlv_lite.

---

@Icaab @NykkyC

Shutter blanking / ISOless issues won't be fixed by hardcoding addresses on some 650D cameras, it seems that the addresses are changing back and fourth among two values (probably more?), we need to follow a1ex suggestion by looking into RAM dumps, currently I can't help much with these problems, sorry.

---

New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.0) for 650D/700D (22-8-2021)

Changes:

crop_rec:
-Reset movie crop marks at every refresh.
-CBR fixes (sometimes the preview would get into x5 mode while you are in x10 mode when the module is off)

mlv_play:
-Playback for 1x3 footage has correct AR now (thanks to Danne)

General:
-Included raw_twk module
-Used old routine to brighten up LiveView in 10/12 bit-depths (which decrease overhead in high FPS)

---

-Write speed improvement:
It's a minor increase which is about ~2-3 MB/s write speed increase in LiveView in all modes:

Last week I was looking for ways to gain extra write speed while RAW recording, e.g by disabling Canon tasks in background or something like that . . I thought about disabling some EDMACs channels which might be not necessary while recording RAW video, I played with all channels then found these two:

EDMAC #12 and EDMAC #24
AbortEDmac(12);
AbortEDmac(24);

Disabling them doesn't affect LiveView preview and RAW data (doesn't produce corrupted frames) which what we need, but noticed some side effects:

-Switching between modes or x5/x10 previews would have 0.5 second of stutter/lag
-In some cases after capturing still photo the camera would take more time than usual to save one image on card and the camera will display "Busy" state
-Doing a camera restart solves previous symptoms

-This option is turned OFF by default, you can turn it ON from mlv_lite (RAW video) advanced submenu.

(https://i.ibb.co/w4skJhX/EDMACs-hack.png)

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

2-3072x1228 @ 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.9 MB/s:
-Without EDMACs hack: 11-15 seconds recorded, write speed reported while recording ~67.5 MB/s
-With EDMACs hack: 41-47 seconds recorded, write speed reported while recording ~72.0 MB/s

(I recorded three clips for each setting, so I triple checked the results ;))

-Use it at your own risk.

-This might work for all small cameras like 650D/700D/EOS M/100D, feel free to test on these cameras, however on 5D3 aborting EDMAC #24 causes LiveView freeze, aborting EDMAC #12 can only gain 1 MB/s write speed improvement (during my tests).

@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?

@lightwriter

Hello!

Well, from the first post, 2560x1440 preset is in 1:1 sampling (true 2560x1440 resolution, not stretch needed, no aliasing in this preset) which has 3.28 crop factor, also has real-time cropped preview. It's doesn't have continuous recording (well, that's depending on scene).

Quote from: lightwriter on August 25, 2021, 03:55:43 PM
If that's so, what are the modules I have to activate/change?

Just read the first post, all info are included there . .

@theBilalFakhouri

Thanks for your fast and thorough explanation!

@theBilalFakhouri thanks for the update..

Just tested the 8/22/2021 version on a relative complex scene containing trees full with leaves, kind of stressing test on details.

650D, 1X3, 1736X1954, AR 2.67, 10 bit, 14-bit lossless, 240 mhz, global draw on, mlv-snd on, EDMACs hack on, ISO 100, mlv raw reading 60 MB/s, can record more than 1 minutes, considering continuous.
The same set up with ISO 1600, mlv raw reading 65-70 MB/s, can record more than 180 frames, about 7-8 seconds, long enough for most video shooting.

Great Job, Bilal.

Quote from: mlrocks on September 08, 2021, 05:11:17 PM
Just tested the 8/22/2021 version on a relative complex scene containing trees full with leaves, kind of stressing test on details.

650D, 1X3, 1736X1954, AR 2.67, 10 bit, 14-bit lossless, 240 mhz, global draw on, mlv-snd on, EDMACs hack on, ISO 100, mlv raw reading 60 MB/s, can record more than 1 minutes, considering continuous.
The same set up with ISO 1600, mlv raw reading 65-70 MB/s, can record more than 180 frames, about 7-8 seconds, long enough for most video shooting.

Great Job, Bilal.

More tests on the same scene

650D, 1X3, 1736X1954, AR 2.67, 10 bit, 14-bit lossless, 240 mhz, global draw off, mlv-snd on, EDMACs hack on, ISO 1600, benchmark went 67 MB/s (from 45 MB/s nominal when global draw is on) with a SanDisk Pro 170 MB/s card. Recorded 360 frames, about doubled compared with that when global draw was on.

The same setup and the same scene, a Zacuto EVF is attached to the 650D using a HDMI to mini-HDMI cable. Recorded about 100 frames, about half with global draw on, about 1/4 with global draw off without an external monitor. There were a lot of pink frames. The HDMI output was real time live view, the framing seemed not correct.

Hello. I haven't been following the branch update recently and I have a question: will the 650d support the Viltrox monitor DC-90HD 4k ? Will everything be qualitatively displayed with firmware magic lantern on this monitor?

You can test it for yourself. Connect cam to TV set/monitor via HDMI.
650D output is limited to 1080i60. Active area is 1620x1080 in photo mode, 1620x912 in movie mode.

Added the following section to the first post:

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM
-Using HDMI:
-Connecting HDMI works, in general there is an overhead when using HDMI with 1080i output you may have corrupted frames especially in high resolutions like x5 mode/1440p/3K 1:1, but using HDMI in 720x480 output doesn't seem to make an overhead (it just act like camera LCD)

-The following crop_rec presets will only work with 1080i output! and with Full Canon preview (toggle between Small and Full preview by pressing Info button in LiveView):
  • All 1x3 presets which has real-time correct preview which are 4.5K/4.3K/4K/UHD in addition to "2.5K Expanded Preview"
  • "720p50 3x3" preset may not work with HDMI, didn't test it.

-I didn't have corrupted frames with 1x3 (real-time correct preview) presets and HDMI 1080i output, don't use Magic Zoom V2 while recording it will produce corrupted frames between the switch (Normal/ZOOM preview).

May clarify HDMI things.

I don't use HDMI much, please report for any issue.

New card. Definitely more tests needed ...
(https://abload.de/img/bench2mhjo4.png)

Quote from: theBilalFakhouri on July 12, 2021, 11:28:43 PM
I got the source code from ArcziPL yes, but I can't really do much for 70D without having the hardware, at some point I was going to borrow 70D for some time, but plans changed, I don't mind working on 70D if I got the body.

Since we're probably living on different continents altogether, I just hope you will one day cross paths with a friendly owner of an extra 70D. Will post a note to that effect in the relevant threads.

BTW, isn't it crazy that 70D, being the only ML-enabled camera with Dual AF, gets so little attention?!

Quote from: elenhil on October 05, 2021, 04:06:17 PM
BTW, isn't it crazy that 70D, being the only ML-enabled camera with Dual AF, gets so little attention?!

No, it is not. Nikfreak ported 70D, managing 3 different firmware versions (all going by the same version number) at once and some day had to shift his priorities. As it frequently happened and will happen in the future.
Such remarks "gets so little attention" are not helpful at all and some devs made it quite clear such things make them less interested in working on ML code at all. More like killing the motivation left.

Quote from: Walter Schulz on October 05, 2021, 05:24:16 PM
No, it is not. Nikfreak ported 70D, managing 3 different firmware versions (all going by the same version number) at once and some day had to shift his priorities. As it frequently happened and will happen in the future.
Such remarks "gets so little attention" are not helpful at all and some devs made it quite clear such things make them less interested in working on ML code at all. More like killing the motivation left.

So sorry. Killing the motivation was the last thing on my mind, really.

Hello, i'm using this build, great build, everything works, but i have a little problem, when using lossless dng, it shows the console every time i take a pic, a bit annoying

I'm using crop rec v2 (10 bit, 1:1, 4.000 x 2500) and silent pics (burst/simple, DNG lossless)

I can't test with the crop rec v1 (when half shutter it zooms and crashes the camera)


Also, i'm not being able to use ETTR (crop rec also zooms on button SET)

Thank you and i'm loving this build, the only reason i bought this camera

Hi all,

I'm having problems with Bilal's build when I output over HDMI in my 700D:

(https://i.ibb.co/MNrTtdc/photo-2021-10-10-18-12-00.jpg)

The red artifacts dissapear if I turn off Global Draw or disabling Focus Peaking.

If I use the standard Nightly Build no image problems, without artifacts, so it seems the problem is related with something in Bilal's build.

I love this Build, I'm gratefull and appreciate so much its development.

I hope you could help me. Just ask me for the info you need.

Kind Regards from Spain,
Marcos

Quote from: elenhil on October 05, 2021, 04:06:17 PM
BTW, isn't it crazy that 70D, being the only ML-enabled camera with Dual AF, gets so little attention?!

Back in 2016 I was going to buy 70D over 700D because of the awesome Dual Pixel AF, so yeah 70D is awesome, when X camera receive X ML developments/features that mean someone has:

Time + Inspiration + Hardware + Skills = new ML update

Time mean: a free time such as holidays, a part of day.. when a contributor/developer feels comfortable to spend some time on this project.
Inspiration: when a contributor/developer feels making X thing would be awesome or when that contributor/developer who is actually a user needs a feature for his camera (that's how ML project started in first place).
Hardware: lacking of hardware could be a problem for progress, in some cases a contributor/developer may be able to work on X camera remotely without the hardware (depending).
Skills: coding, reverse engineering, assembly lang or at least you are familiar how software and hardware works in general, basic understanding helps

How unique/cool is the camera isn't a factor for a progress but that helps to boost Inspiration I guess :)

Quote from: ShittyWebsite on October 05, 2021, 11:56:36 PM
Hello, i'm using this build, great build, everything works, but i have a little problem, when using lossless dng, it shows the console every time i take a pic, a bit annoying

I'm using crop rec v2 (10 bit, 1:1, 4.000 x 2500) and silent pics (burst/simple, DNG lossless)

Thanks, sorry for the delay,

Which camera are you using?

Taking "Simple" silent is broken by default on my 700D (even in official builds, it stuck on "Preparing...") burst silent works, does taking "Simple" silent picture works on your camera?
Currently I don't recommend to use silent picture with crop mode v2, in crop mode v2 sometime black level goes wrong when capturing silent pic (no idea why).

Which FPS are using in 4000x2500 ?

Be aware: Lower bit-depths in Crop mode/V2 are meant for RAW video recording only, silent picture does only support 14-bit uncompressed or 14-bit lossless otherwise using lower bit-depths from crop rec/v2 submenu can lead to wrong white/black levels and to unrecoverable image (currently if you want to use silent pic make sure lower bit-depths are off from crop mode/v2 submenus).

Quote from: ShittyWebsite on October 05, 2021, 11:56:36 PM
I can't test with the crop rec v1 (when half shutter it zooms and crashes the camera)

Actually the crash is caused because of RAW video is on and you are maybe using burst mode, burst mode crashes the camera when RAW video is on (I think RAW video should be off when using silent picture, same crash happens on 5D3), why would use crop mode v1 for silent picture? I see crop mode v2 is better option for silent pic.

Quote from: ShittyWebsite on October 05, 2021, 11:56:36 PM
Also, i'm not being able to use ETTR (crop rec also zooms on button SET)

Hmmm, I need to find a workaround for assigned buttons, SET button is being used by crop mode to trigger zoomed preview (in this case I will just disable SET button for crop mode while ETTR is on, you can still use magnification button to trigger zoomed preview), also I need to take care of crop rec v2 because it using SET button for manual LiveView refresh.

Quote from: theBilalFakhouri on October 10, 2021, 09:17:50 PM
Thanks, sorry for the delay,

Which camera are you using?

Taking "Simple" silent is broken by default on my 700D (even in official builds, it stuck on "Preparing...") burst silent works, does taking "Simple" silent picture works on your camera?
Currently I don't recommend to use silent picture with crop mode v2, in crop mode v2 sometime black level goes wrong when capturing silent pic (no idea why).

Which FPS are using in 4000x2500 ?

Be aware: Lower bit-depths in Crop mode/V2 are meant for RAW video recording only, silent picture does only support 14-bit uncompressed or 14-bit lossless otherwise using lower bit-depths from crop rec/v2 submenu can lead to wrong white/black levels and to unrecoverable image (currently if you want to use silent pic make sure lower bit-depths are off from crop mode/v2 submenus).

Actually the crash is caused because of RAW video is on and you are maybe using burst mode, burst mode crashes the camera when RAW video is on (I think RAW video should be off when using silent picture, same crash happens on 5D3), why would use crop mode v1 for silent picture? I see crop mode v2 is better option for silent pic.

Hmmm, I need to find a workaround for assigned buttons, SET button is being used by crop mode to trigger zoomed preview (in this case I will just disable SET button for crop mode while ETTR is on, you can still use magnification button to trigger zoomed preview), also I need to take care of crop rec v2 because it using SET button for manual LiveView refresh.

I'm using a 700D, Thank you, its very helpful

At 4500 x 2500 i was getting 10fps (8 photos buffer) now i'm using 5000x3200 (7fps, 2 photos buffer) sometimes i use 1x3 1668x2040 10bit (continuous, about 5k 24fps)

I've been testing with 3x1 too, (5300x1160, 10bit that gives me 16fps continuous, works greatly for some bird photography and horse jumping obstacles)

For ETTR i can use the photo mode, press Set, then switch to video mode and it works fine

I've been using silent pics with both crop rec and crop rec v2, works perfectly ("Simple" dosent work so i just "Burst" and click once, it works greatly)
sometimes i guess some purple highlights on the crop rec v1, i just refresh the liveview and its back to normal

Right now, i'm gonna test the isoless build (my camera was showing the isoless message when dual iso but I dont even care, i'll test the build just for fun)

I've just finished testing with the isoless build, everything works perfectly,
Dual Iso + Crop rec (1x3 uhd) + Raw v1: great for video
Dual Iso + Crop rec V2 (1:1 5000x3500) + Silent pics (burst) + Raw MLV: great for pics

It's amazing what you did with a entry level camera,

5K, 10bit, 2:35, 23,976 Continuous raw with dual iso, it's amazing, Thank you

I need your help for lens recommendations.

Im going to buy a 700D, and i want to use it in crop mode.

What are the best cheap fast lenses for 3.24x crop which can reach infinity focus with the EF mount, without camera modification?

@Deadcode

700D is a cool camera ;)

Unfortunately I am not fast-lens expert guy, no much experience there. You better ask your question in a new topic in the forum (https://www.magiclantern.fm/forum/index.php?board=40.0) or in reddit (https://reddit.com/r/MagicLantern/), maybe Discord  (https://discord.gg/uaY8akC)too.

For what purpose do you want to use crop mode? I mean if you are looking for wide field of view with 3.24 sensor crop (fast wide lens), it might be better to consider *EOS M + Speed booster.

*keep in mind there are some differences among EOS M and 700D, like the articulated screen, lens mount (you can use speed booster or adapter to get EF mount on EOS M), 240 MHz overclock for longer recording times on 700D.

I already bought the 700D yesterday, and i choose this becasuse of your 1x3 dual ISO video on youtube :D
I know the strong points of the Eos M, tried it several month ago, but i had to stick with dSLR form factor due to family requirements (My wife shoots with 600D which has very limited raw video capabilities and i wanted to upgrade "her" camera, and she didnt want much change)

As i can see the 2,5K 1:1 with corrected preview, the ana 4,5K and the regular raw mode are the most usable.

im still catching up about the correct settings for most of the modes, like
- is there a 2.8K mode with 10 bit? the 3K with 14 bit compressed limitation only shoots for about 60 frames
- with crop rec new it seem like i can shoot with 8-11 bit in high rez crop mode, but if i turn on fix preview it switches back to 14 bit. 1440p 1:1
- how can i shoot full widt anamorph 1x3
- are there any reason to shoot 3x1?

These are my first experiances about 2 hours of playing with the camera, you dont have to answere these questions :)

BTW: Im using a Canon 10-18 IS STM, and my goal is to shoot as beautiful images as Zeek does who shoot mostly 2.5K with his EosM

Deadcode,

Nobody can mimic your own experience with Magic Lantern.  You have your new camera in your hands now.  Instead of asking all these questions, why don't you just go ahead, test all available modes and check and see which one works best for you?  You have a large variety of mode choices and will very soon realize what increadible video features your camera offers to you.  Just pick one that you like most, test it out, learn how to use, practise a lot and you will soon start shooting these stunning quality videos that Zeek makes ! 

Personally, I like very much the 1x3 anamorphic mode on my EOS-M.  When set at 1280x2160 resolution at 10 bits lossless I get continuous recording at 24 fps and nearly aliasing free video with excellent rendering finest detail.   The crop factor is just as much as to avoid the softness and imperfections at the edges of my lenses. 

Here is a video that I shot this summer on the EOS-M using the above mode and settings:

https://cloud.mail.ru/public/x92j/VVXXaZdmV

To watch it in its highest quality, you have to download it from this link using the blue download button right above the video.  If you notice some softness on some of the clips, this is due to poor manual focusing on my part.   With manual vintage lenses focusing could be quite chalenging, especially at bright sun light.  Don't blame ocasional softness on the mode quality or the camera.

Good luck!

@Deadcode

You can use 10/12 bit-depths in lossless compression in all modes (for high resolution such as 1440p 1:1 and 3K 1:1 read the first post).
To get 2.8K resolution, choose 3K 1:1 preset from "Crop mode" (crop_rec) then reduce the resolution to 2.8K from RAW video submenu (mlv_lite).

To shoot in full-width in 1x3 mode, you need crop_new module (Crop mode V2), simply go in "Crop mode V2" submenu --> Choose preset --> 2.35:1 1x3 --> exit ML menu and press SET button to apply the changes if it didn't apply --> now you get 1736x2214 in 2.35:1 AR @ 23.976 FPS in 1x3 mode, if you want more height you have to reduce FPS through "Crop mode V2" submenu then increase Y resolution as you want and don't forget to press SET button in LiveView to apply the new settings.

-"FIX preview" option doesn't affect bit-depths.

-For 700D I can't see benefits for using 3x1 binning mode, this mode produce aliasing and moire as normal 3x3 mode, the option is there since the crop_new meant to control sensor parameters such as binning modes and other settings.

Quote from: theBilalFakhouri on October 23, 2021, 06:28:56 PM
exit ML menu and press SET button to apply the changes

That was the missing part for me! Thank you! I was hitting the info button, and rebooting constantly...

Hey everyone I have the latest version of bilals build but i have the shutter blanking issue. it just shows N/A. If there isnt a fix available I would like to have the is build https://builds.magiclantern.fm/jenkins/job/raw_video_10bit_12bit/53/artifact/platform/700D.115/magiclantern-raw_video_10bit_12bit.2019Mar24.700D115.zip but with the sd_uhs module. Is that possible? I tried adding it to the modules folder then reflashing but that didnt work and gave me an error loading the module. I would like this option as I don't like shooting in crop and the normal RAW video is great for me. What can I do?

Hello. Installed the latest version of the firmware on 650d. Decided to use a Dual ISO. Original ISO 100, Recovery 1600.
I open in mlvapp. Normal exposure. When I start correcting, the video is so dark, it's like I only shot 100.
Where can I go wrong?
(https://i.ibb.co/x3yvRwH/Screenshot-1149.png) (https://ibb.co/cxP57RL)

@barton_senger44

Quote from: barton_senger44 on October 26, 2021, 07:47:13 PM
Hey everyone I have the latest version of bilals build but i have the shutter blanking issue. it just shows N/A. If there isnt a fix available I would like to have the is build https://builds.magiclantern.fm/jenkins/job/raw_video_10bit_12bit/53/artifact/platform/700D.115/magiclantern-raw_video_10bit_12bit.2019Mar24.700D115.zip but with the sd_uhs module. Is that possible? I tried adding it to the modules folder then reflashing but that didnt work and gave me an error loading the module. I would like this option as I don't like shooting in crop and the normal RAW video is great for me. What can I do?

For 700D you have two different builds, one of them might work for you, from the first post:

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM
700D:
Download the New build: crop_rec_4k.2021Aug22.700D115.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115.zip)
.....
Some users have stuck shutter value issue in ML menu, please try this build: crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip)

Have you tried both? does the two build have the shutter issue on your 700D?

---

Quote from: Icaab on November 05, 2021, 07:34:10 PM
Hello. Installed the latest version of the firmware on 650d. Decided to use a Dual ISO. Original ISO 100, Recovery 1600.
I open in mlvapp. Normal exposure. When I start correcting, the video is so dark, it's like I only shot 100.
Where can I go wrong?
(https://i.ibb.co/x3yvRwH/Screenshot-1149.png) (https://ibb.co/cxP57RL)

Mind share a short MLV sample (maximum of 5 seconds) which has the problem? You can cut the affected MLV file in MLVApp, export it as MLV "Fast pass".

I did indeed try it and the problem still persists

Quote from: barton_senger44 on November 05, 2021, 08:07:03 PM
I did indeed try it and the problem still persists

Have you double checked both builds and replaced all files in SD card?

If so, does this build work for you without the shutter issue?
https://builds.magiclantern.fm/jenkins/job/raw_video_10bit_12bit/53/artifact/platform/700D.115/magiclantern-raw_video_10bit_12bit.2019Mar24.700D115.zip

Yes this march build works flawlessly but as I said it doesnt have the sd_uhs module. Is there a way to trace the shutter blanking bug in your latest builds tho? I think crop rec might come in handy or even 1X3 binning.

Okay, that's because march build (from 10/12 bit branch) doesn't support shutter blanking, in crop_rec_4k builds shutter blanking are required and it seems your 700D have different addresses from the included addresses in my two builds.

Shutter blanking allows to get correct shutter speeds when overriding FPS.

So in this case please follow these steps here:
https://www.magiclantern.fm/forum/index.php?topic=25784.msg236184#msg236184

And provide shutter blanking addresses from your camera, also provide a RAM dump (zip it before uploading), you can get the RAM dump from "Debug" tab in ML menu --> press "Dump ROM and RAM" and wait until it finish, you will find RAM4.BIN in your SD card under ML/LOGS please upload it somewhere and PM me the RAM dump.

---

IIRC sd_uhs won't work directly in 10/12 bit branch, probably needs some modifications, I will try compiling it for you so you can test it, but I don't promise to make it work if it doesn't work.

Quote from: theBilalFakhouri on November 05, 2021, 09:30:03 PM
Okay, that's because march build (from 10/12 bit branch) doesn't support shutter blanking, in crop_rec_4k builds shutter blanking are required and it seems your 700D have different addresses from the included addresses in my two builds.

Shutter blanking allows to get correct shutter speeds when overriding FPS.

So in this case please follow these steps here:
https://www.magiclantern.fm/forum/index.php?topic=25784.msg236184#msg236184

And provide shutter blanking addresses from your camera, also provide a RAM dump (zip it before uploading), you can get the RAM dump from "Debug" tab in ML menu --> press "Dump ROM and RAM" and wait until it finish, you will find RAM4.BIN in your SD card under ML/LOGS please upload it somewhere and PM me the RAM dump.

---

IIRC sd_uhs won't work directly in 10/12 bit branch, probably needs some modifications, I will try compiling it for you so you can test it, but I don't promise to make it work if it doesn't work.

first register 40452918, second register 4045291c
ram dumb https://drive.google.com/file/d/1wVDc0bWr3IWyPKrGEHvxbQcIhqX61g2j/view?usp=sharing
where should I get the shutter blanking address from?

@barton_senger44
Thanks, you already got them (from the registers).

I am using the addresses you have provided in this build:
https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip

This build should work for you without the shutter issue, please try it and feedback, make clean install (format SD card in PC then format it in camera then install the build from firmware update after coping the files to SD card).

Quote from: theBilalFakhouri on November 05, 2021, 07:52:45 PM
@barton_senger44

For 700D you have two different builds, one of them might work for you, from the first post:
Have you tried both? does the two build have the shutter issue on your 700D?

---

Mind share a short MLV sample (maximum of 5 seconds) which has the problem? You can cut the affected MLV file in MLVApp, export it as MLV "Fast pass".

Okay, I've got a raw source attached
https://drive.google.com/file/d/1j6alz9SFRrqHjrB8x7-s6iPPPpCilaZl/view?usp=sharing (https://drive.google.com/file/d/1j6alz9SFRrqHjrB8x7-s6iPPPpCilaZl/view?usp=sharing)


By the way, is there any way to remove the stripes that appear when dual Iso is enabled?
Focus harder
(https://i.ibb.co/G7TNf3J/1636369645574.jpg) (https://ibb.co/JnQgWFd)

And here's a picture where I have 100 ISO without dual iso

(https://i.ibb.co/0C4ZY4N/1636369645559.jpg) (https://ibb.co/qNq9mqG)

@Icaab

The footage looks good, you aren't using Dual ISO correctly, procced files will always have the low ISO exposure (then in Post you can raise exposure and you will have clean shadows).

Why your footage looks dark? because it's underexposed in first place, and in your case (the MLV file you shared) you don't need to use Dual ISO (your scene is flat, no much required dynamic range), there is no reason to start with 100 ISO in this case, you can start with 400 or 800 ISO and you probably won't have blown highlights.

Simple way to use Dual ISO correctly: You probably want to use Dual ISO only in contrasty scenes when you have bright highlights and dark shadows, expose your shot correctly (e.g expose for highlights), let's say you used 100 ISO as base, now turn on Dual ISO and set second ISO to 800 to get clean shadows recovery in post.

For example, take a look in these photos:
https://www.magiclantern.fm/forum/index.php?topic=7402.msg62865#msg62865

Quote from: ShittyWebsite on October 11, 2021, 03:15:46 AM
I've just finished testing with the isoless build, everything works perfectly,
Dual Iso + Crop rec (1x3 uhd) + Raw v1: great for video
Dual Iso + Crop rec V2 (1:1 5000x3500) + Silent pics (burst) + Raw MLV: great for pics

It's amazing what you did with a entry level camera,

5K, 10bit, 2:35, 23,976 Continuous raw with dual iso, it's amazing, Thank you

Hello. How did you manage to take a photo with a crop that appears when you turn on the module Crop rec V2? (my camera 650d)

Quote from: theBilalFakhouri on November 08, 2021, 03:23:20 PM
@Icaab

The footage looks good, you aren't using Dual ISO correctly, procced files will always have the low ISO exposure (then in Post you can raise exposure and you will have clean shadows).

Why your footage looks dark? because it's underexposed in first place, and in your case (the MLV file you shared) you don't need to use Dual ISO (your scene is flat, no much required dynamic range), there is no reason to start with 100 ISO in this case, you can start with 400 or 800 ISO and you probably won't have blown highlights.

Simple way to use Dual ISO correctly: You probably want to use Dual ISO only in contrasty scenes when you have bright highlights and dark shadows, expose your shot correctly (e.g expose for highlights), let's say you used 100 ISO as base, now turn on Dual ISO and set second ISO to 800 to get clean shadows recovery in post.

For example, take a look in these photos:
https://www.magiclantern.fm/forum/index.php?topic=7402.msg62865#msg62865

Okay. I realized my mistake.
I'm sorry, but can you drop the link to some instruction that describes how to shoot a timelapse with a dual ISO and a silent picture? (intervalometer doesn't work with these modules)

Also for a silent picture : I choose ful-res and shutter speed on frames always 1/4, whichever I choose. Am I to understand that this can only be fixed with an nd-filter?

And if I get a dng photo, how do I remove vertical stripes in mlvapp?

wrong topic...

Is there a way to get non stretched liveview in uncropped 1738x1880 1x3 binning?

Quote from: Icaab on November 08, 2021, 06:53:26 PM
Okay. I realized my mistake.
I'm sorry, but can you drop the link to some instruction that describes how to shoot a timelapse with a dual ISO and a silent picture? (intervalometer doesn't work with these modules)

Silent picture isn't reliable (https://www.magiclantern.fm/forum/index.php?topic=25784.msg237005#msg237005) for 700D in crop_rec_4k branch, you need to use burst mode with RAW video off, IIRC intervalometer does work with that.

Quote from: Icaab on November 08, 2021, 06:53:26 PM
Also for a silent picture : I choose ful-res and shutter speed on frames always 1/4, whichever I choose. Am I to understand that this can only be fixed with an nd-filter?

Full-Res in Silent picture doesn't use LiveView (the RAW resolution from crop modes), it's same as capturing normal RAW photos but without using mechanical shutter, read about it here (https://www.magiclantern.fm/forum/index.php?topic=12523.0), if you want to use full-resolution with fast shutter speed, set Crop mode V2 to full resolution preset and set silent picture to Burst mode, also turn on Full shutter range from Crop mode V2 submenu (read the first post for more details).

Quote from: Icaab on November 08, 2021, 06:53:26 PM
And if I get a dng photo, how do I remove vertical stripes in mlvapp?

I think there is an option in MLVApp to transcode and import DNG/CR2 files to MLVApp, or just use MLV option from silent picture.

Quote from: barton_senger44 on November 10, 2021, 12:59:40 PM
Is there a way to get non stretched liveview in uncropped 1738x1880 1x3 binning?

There is "Framing" preview, it's not real-time preview but it's useful for framing, you can set it from RAW video submenu or toggle between real-time and framing preview by pressing half-shutter in LiveView.

---

Have you tried yet the following steps?

Quote from: theBilalFakhouri on November 07, 2021, 03:03:11 PM
@barton_senger44
Thanks, you already got them (from the registers).

I am using the addresses you have provided in this build:
https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip

This build should work for you without the shutter issue, please try it and feedback, make clean install (format SD card in PC then format it in camera then install the build from firmware update after coping the files to SD card).

Does the shutter issue still present?

Ill try it right now I was busy with some stuff lately

hi again bilal..  :D
just thinking.. can I use 50fps 1080p? or it is just 720p? with 1x3 binning mode?
I worried if something gone wrong as a noob lol..
so i ask you questions first.

thanks  :D

@ML700D

You can play with Crop mode V2 and see what max FPS you can get at what resolution and binning mode :), 1736x970 3x3 @ 50 FPS is possible but can produce corrupted frames in lossless compression, and requires high write speeds (not practical)

AFAIK 1736x864 3x3 @ 50 FPS (maybe 48 FPS) is usable with lossless compression, might not be continuous. Using 1x3 binning mode with High-FPS would lead to very wide aspect ratio.

Quote from: theBilalFakhouri on November 29, 2021, 08:15:08 AM
@ML700D

You can play with Crop mode V2 and see what max FPS you can get at what resolution and binning mode :), 1736x970 3x3 @ 50 FPS is possible but can produce corrupted frames in lossless compression, and requires high write speeds (not practical)

AFAIK 1736x864 3x3 @ 50 FPS (maybe 48 FPS) is usable with lossless compression, might not be continuous. Using 1x3 binning mode with High-FPS would lead to very wide aspect ratio.

I ever tried using crop mode V2 but still confusing with the setting and get pink zebra at live view sometimes, so how to calculate it properly? thanks.

hi bilal..
I found that if i record at a distance this is what usually happens and it didn't work using fixed bad pixel
(https://i.ibb.co/Jz0Zgph/Screenshot-2021-12-08-180630.png)

Try chroma smooth 3x3.

@ML700D

This problem is related to focus pixel interpolation algorithms inside MLVApp, it doesn't clean all focus pixels with Dual ISO clips, sometime it produces more focus pixels, best thing to do is as Danne suggested to use chroma smoothing. also trying different RAW debayer algorithms might help reducing these pixels.

Quote from: Danne on December 08, 2021, 03:53:33 PM
Try chroma smooth 3x3.

Quote from: theBilalFakhouri on December 10, 2021, 02:28:07 PM
@ML700D

This problem is related to focus pixel interpolation algorithms inside MLVApp, it doesn't clean all focus pixels with Dual ISO clips, sometime it produces more focus pixels, best thing to do is as Danne suggested to use chroma smoothing. also trying different RAW debayer algorithms might help reducing these pixels.

I've tried it but it doesn't work with chroma 3x3 but yes it's a bit reducing when using log profile.
it's a bit strange, sometimes it's there, sometimes it's not even though I use the same setting.

ok. thanks bros..

hi bilal and danne

I noticed the problem when using fix bad pixels to auto that happen then I change to map it's reduced if I turn off, it disappeared..
weird 🤣

it's usually happen when using dual iso, afaik.

bilal,
I've got an error message Isoless LV (err2) when using dualiso in crop_rec shutter blanking version.

hi bilal, sorry to bother again.. 😁

just comes in mind, I saw that color primaries etc. (in the image below) using BT.709 in standard recording.
is it possible to replace BT.709 with others in magic lantern? e.g. log-c or something else.

(https://i.ibb.co/V233jk2/Screenshot-2022-02-15-150221.png)

@ML700D: this is metadata. You can write there whatever you want... but that won't change much, because the video data itself doesn't change. As far as I know processing in camera is done in hardware (for speed reasons) - so probably impossible to do "real" changes.

I see.. thanks masc.

Quote from: ML700D on January 29, 2022, 10:59:38 AM
bilal,
I've got an error message Isoless LV (err2) when using dualiso in crop_rec shutter blanking version.

-There are three builds in the first post, one of them should have both Dual ISO and Shutter values working without a problem, try each build and see what works for your 700D.

-Well, a while ago IDA_ML reported that shutter values are working fine when using crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip), but he had a broken Dual ISO module (ISOless errors), I have just added a new fourth build combines both Shutter Blanking and Dual ISO fixes, these four builds should cover all reported cases:

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM
700D:
-Download the New build: crop_rec_4k.2021Aug22.700D115.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115.zip)
-Download the New build with re-solved Dual ISO ISOless 8 & 15 for some 700D users: crop_rec_4k.2021Aug22.700D115_ISOless_8_15.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115_ISOless_8_15.zip)
-Some users have stuck shutter value issue in ML menu, please try this build: crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115_Shutter_Blanking.zip)
-Some users may have both stuck shutter value issue in ML menu and ISOless Dual ISO errors, try the following build which contain both fixes: crop_rec_4k.2021Aug22.700D115_Shutter_Blanking_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2021Aug22.700D115_Shutter_Blanking_ISOless.zip)

Sorry for these many builds, at least we have something that works :).

Thanks a lot bilal..
I really appreciate it

No need to be sorry, Bilal.  Since I use Dual ISO a lot, this bug was really giving me a hard time.  I am glad to see that you have fixed it.  Thank you so much!

bilal,
I tried fps overrides 1 fps but the result was not as expected, looks laggy instead of time-lapse.
I set 25fps crop_rec 1x3 4K preset then change in menu to 1 fps overrides.
export to h264 for testing.

why? thanks b4.

Quote from: ML700D on March 21, 2022, 03:20:50 PM
bilal,
I tried fps overrides 1 fps but the result was not as expected, looks laggy instead of time-lapse.
I set 25fps crop_rec 1x3 4K preset then change in menu to 1 fps overrides.
export to h264 for testing.

why? thanks b4.

Your camera settings are fine. You need to change "Framerate override" in MLVApp export settings to your desired FPS (24 or 25... etc) then export the clip.

This happening because the framerate in MLV metadata was saved as 1 FPS based on your ML settings, so you are playing-back 1 frame every second = laggy result. Change FPS in post in this case.

thanks bilal, I just did and works fine.

Hi, i've been struggling with the shutter blanking isoless build, everytime i stop recording the timer freezes and ML menu shows "Stopping" but it doesn't stop.
Any idea of what can it be?
BTW, thanks bilal, amazing work, i love your builds <3

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.

Hello!

Quote from: lightwriter on March 29, 2022, 07:37:18 PM
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?

Yes it's doubled magnification compared to 1.6 crop, it uses ~1/4 of the sensor area:
(https://i.ibb.co/KwxFmtz/Sensor-Area.png)
(16:9 showcase)

Quote from: lightwriter on March 29, 2022, 07:37:18 PM
- Is 2.5K Expanded Preview similar to EOS M 2.5K RAW mode?

"2.5K Expanded Preview" is same as "2.5K 1:1 centered frtp", However *"1440p" on 700D is same as  "EOS M 2.5K RAW".
*"1440p" preset on 700D has 2560x1440 resolution which can be called 2.5K. while "EOS M 2.5K RAW" has 2520x1418 resolution (a little less than 700D).

To get 2.8K on 700D, you can use "3K 1:1" preset which has 3072x1308 resolution, reduce the resolution to 2880x1226 via RAW video submenu (mlv_lite), now it can be called 2.8K :P.

Quote from: lightwriter on March 29, 2022, 07:37:18 PM
- 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.

All of 1x3 presets with real-time preview has ~2.7 Megapixel (out of the sensor, of course in 1x3 readout), not 1 MP.
Use one of 1x3 presets depending on aspect ratio you need.

Downscaling e.g. 1280x2160 to 1280x720 will give cleaner image, upscaling 1280x2160 to 3840x2160 will give more details.

You can go above 2.7 MP using "Crop mode V2" (crop_new) on 700D, but you will lose real-time preview. The reason why all of 1x3 real-time presets are limited to ~2.7 MP because of preview, going above ~2.7 MP resolution will make Preview frozen or you will lose part of the horizontal /vertical preview (there is a limit here, more research is required).

Maximum resolution in 1x3 Binning mode @ 23.976 FPS with full width sensor is 1736x2214 2.35:1 AR which is 3.8 MP, this mode isn't continuous. But we can achieve 1600x2040 2.35:1 AR 1.74 crop factor @ 23.976 FPS in 1x3 and have continuous recording (10-bit lossless, 240 MHz SD overclock), that's about 3.2 MP, but without real-time preview (using "Crop mode V2", set resolution to 1736x2214 then reduce it with RAW video to 1600x2040).

btw bilal,
why when use 1fps overrides lv looks very choppy, lag and changing darker then brighter like that?

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:

(https://i.imgur.com/VrsJn0R.png)

Quote from: lightwriter on March 30, 2022, 11:35:51 AM
Thanks Bilal, for your very thourough answer!

.. 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?

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.

Quote from: lightwriter on March 30, 2022, 11:35:51 AM
I tried the 1600x2040 2.35:1 AR 1.74 crop factor @ 23.976 FPS in 1x3 and used the EMACs 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:

You need to refresh LiveView manually (after changing Crop mode V2 settings) by pressing SET button in LiveView (before recording).
Switch Preview under RAW video submenu to Framing (or press half-shutter in LiveView) to check if these artifacts gone after applying a manual refresh.

Quote from: theBilalFakhouri on March 30, 2022, 12:05:07 PM
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:

(https://i.imgur.com/TbDSdaZ.png)

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

(https://i.imgur.com/IZQX6Ag.png)

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!

nice result.. 👍
UHD 1x3 is my favorite..
but bilal's crop_rec_4k is the real favorite.. 🎥

Absolutely!

The UHD 1x3 1280x2160 mode at 12bit and 24 fps provides an absolutely gorgeous result.  Recording is continuous too.  I use it all the time.

For wide  angle landscape videography, there is another favorite mode of mine: the 5k 1x3 1736x2928 mode at 12bit and 16 fps.  This mode is also continuous and provides full-sensor readout.  Works great with Dual ISO too - perfect for sun sets or other high-contrast scenes.  If you set the shutter to 1/16-th of a sec. you also get an additional stop of light - perfect for street videography at night.  You get a nice motion blur but need to keep the camera very steady (tripod, gimbal), otherwise rolling shutter will kill your shots.

All in all I think that the 1x3 high-resolution modes are among the greatest achievements of our developers.

Thanks ML700D!

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

New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) for 650D/700D

Changes:

mlv_lite:
-Added new LiveView hacks
-Get up to ~13 MB/s write speed improvement! total write speed in LiveView is 82.8 MB/s! :

Guide: LiveView hacks (write speed improvement) (https://www.magiclantern.fm/forum/index.php?topic=26443.msg238349#msg238349)

Quote from: theBilalFakhouri on April 07, 2022, 06:20:22 AM
-Some results:
-2560x1440 1:1 16:9 Continuous! (@ 23.976, 10-bit lossless)
-1736x2214 1x3 2.35:1 Continuous!  (@ 23.976, 10-bit lossless)
-2880x1226 1:1 2.35:1  Continuous!  (@ 23.976, 10-bit lossless)
-You can definitely record longer in 3K 3072x1308 1:1 2.35:1 preset (@ 23.976, 10-bit lossless)
-High frame rate modes can be Continuous! or "You can definitely record longer".

-Old EDMACs hack (https://www.magiclantern.fm/forum/index.php?topic=25784.msg236507#msg236507) has been removed and replaced with the new hacks.

crop_rec:
-Re-enabled some ADTG registers.

nice.. thanks bilal 🥳

Quote from: ML700D on March 30, 2022, 11:12:19 AM
btw bilal,
why when use 1fps overrides lv looks very choppy, lag and changing darker then brighter like that?

Sorry for the delay,

LiveView should look choppy because it's low FPS.
Laggy/the camera become slower: overriding FPS to low frame rates changes FPS Timers (LiveView speed is based on FPS timers) which result in slower LiveView updates.

Changing darker then brighter: This is related to shutter blanking and how it work, it will takes more timer to restore and apply the correct shutter speed. adjusting FPS to lower framerate will result in limited and slow shutter speed --> bright LiveView --> Shutter blanking will take aware of this and will restore full shutter speed range and will apply previous shutter setting --> dark LiveView (actual brightness before changing FPS).

Quote from: lightwriter on March 30, 2022, 03:50:20 PM
What do you think is the "real" resolution when exporting the footage at 3840x2160?

I am not sure if there is answer for that . . however 1280x2160 is ~2.7 MP, and the upscaled footage is based on that number of pixels.
Also the 1280 width resolution is based on 3840 Binned pixels from the sensor.

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?

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?

Quote from: names_are_hard on April 12, 2022, 05:10:11 PM
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.

Why don't you take some shots with test charts? Newton rings, Siemens stars, ...

Right, so you're comparing two different cameras, two different optical paths.  Using only the resolution numbers isn't going to get you a good answer.  As Walter says, take some calibrated test shots.

Yes, the vertical resolution is real 2160.  Horizontally, it's binned pixels; the light from every 3 pixels is combined in hardware.  Light is captured from a 3840*2160 region, the data produced is 1280*2160, but the pixels are rectangular.  The "stretching" is to undo the assumption by image formats that pixels are square.  Stretched and interpolated are not the same thing.  I believe this is not interpolation, but I haven't checked the code.  There is very little maths involved here.

It is definitely higher resolution than 1920*1080 *in terms of pixels*.  This doesn't tell you if it looks better or worse.  If you want to know that, you must measure it.  There's enough of an MP difference that I'd expect the ML footage to look noticeably better, but that's my guess.

1920*1080 is also a fairly weird raw format.  What cam is it?

1920x1080 doesn't leave any margin for stabilization or cropping, 3840 even stretched from 1280 but with real 2160 vertical should be much better in this aspect.. at least I think so. Of course I can only compare it to ML 1920x1080 and not other cameras.

I was trying to use the silent picture function in video mode on 650d.
I noticed that when coupling a dumb adapter with a manual focus lens, push the shutter button will generate error like "communication issue with lens". Then I have to remove the battery to clear.
Today I try connecting Canon EFS 10-18 IS, then push the shutter button, the camera generates both CR and JPEG files, and I hear a shutter sound. I have the silent picture on with "simple dng". I am happy that I can take pictures in video mode, although silent picture function seems not working, which does not bother me much.
It seems to me that the lens connection plays an important role when trying to take photos in video mode. Hope this can solve so that manual focus lens with dumb adapter will take photos too.

Update:
I just found out that the error was caused by my using extender. If there is no extender, open and close the battery, restart the camera, mf lenses with dumb adapters can take photos, although silent picture seems still not work, but this is good enough for me. 

New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) for 650D/700D

Changes:

mlv_lite:
-Excluded "Movie crop mode" from the new hacks, it freezes LiveView.
-Added a little more delay after calling CartridgeCancel a.k.a "One more hack", might help reducing/fixing first frame corruption.

-Menus:
-fixed interference between ML menu and Canon overlays in LiveView, I took this fix from here (https://foss.heptapod.net/magic-lantern/magic-lantern/-/commit/692eb50142bfdfa52a86253bdc46c06cf52a38f9), solves this issue (https://www.magiclantern.fm/forum/index.php?topic=7473.msg198464#msg198464).

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

Quote from: lightwriter on May 09, 2022, 11:56:04 AM
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?

Hello!

This was requested (https://www.magiclantern.fm/forum/index.php?topic=25976.msg235179#msg235179) before, the sensor is capable  (https://www.magiclantern.fm/forum/index.php?topic=25976.msg235201#msg235201) but when attempting  (https://www.magiclantern.fm/forum/index.php?topic=25976.msg235466#msg235466)to record e.g. 1280x2160 @ 30 FPS with real-time correct preview an overhead would appear resulting in corrupted frames.

So real-time correct preview (in ~2.7 MP presets like 4.5K/4.3K/4K/UHD 1x3) with 30 FPS are no go right now.

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.

Hey (Selam Bilal) everyone, I am relatively new to Magic Lantern and I am honestly a little overwhelmed by all the options I have.
I wanted to ask if somebody could help me set the optimal settings for a movie look. I make short films, but usually on other peoples cameras.

I baught this SD Card "Angelbird SD Card AV PRO UHS-II 128GB V90".
I am using Bilals newest build for my 700d and would love to use the best possible resolution in 25fps, 1/50.
I also only need to record for 20-25s max. because thats how long a Take takes.
Thanks in advance!

download link for 650d is not working atm.

it seems @Moderators are taking a bit long time to approve new posts, see (https://foss.heptapod.net/magic-lantern/magic-lantern/-/issues/2955), I think I should claim a moderator role  :P or at least the ability to see pending posts.

@Sucuk
Already answered on reddit (https://www.reddit.com/r/MagicLantern/comments/utr8gu/best_movie_look_settings_on_700d/). Feel free to continue chatting here.

New builds are posted in the first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) for 650D/700D:

Changes:

crop_rec:

-Added "Fix Dual-ISO flicker" option in "Crop mode" submenu, this option will remove waterfall effect for Dual-ISO lines (https://www.magiclantern.fm/forum/index.php?topic=26497.msg238977#msg238977) by reducing FPS a tiny bit, this option will work in all "Crop mode" presets except for "Full-Res LiveView" preset.
This option is enabled by default and will only have effect when Dual-ISO is enabled.

(https://i.ibb.co/3FrBYnP/crop-rec-Fix-Dual-ISO-flicker.png)

-Adjusted analog gain for lower bit-depths, now it's accurate. LiveView brightness is identical among 12/11/10/9/8 bit-depths, it was a bit off, now it's accurate.
-Added 11-bit option, it can be a sweet spot for some resolutions.

mlv_lite:
-Added  LVICV_ReleaseResource hack (https://www.magiclantern.fm/forum/index.php?topic=26443.msg238980#msg238980):

(https://i.ibb.co/jw0785q/Two-more-hacks.png)

You can find it in RAW video submenu, under "Two more hacks":
"1" enables CartridgeCancel a.k.a "One more hack" before.
"1 + 2" enables both CartridgeCancel and LVICV_ReleaseResource.

Please note: that LVICV_ReleaseResource hack may result in worse write speed performance, please make your own tests and see if it's actually enhance write speed or not, if not, it's better to avoid it and use only "1" option.

dual_iso:
-Added DISO block, I took it from crop_rec_4k_mlv_snd branch, now you will have Dual ISO info inside MLV file and you can view it using MLVApp:

(https://i.ibb.co/VQbBvsN/DISO.png) (https://ibb.co/VQbBvsN)

-Dual ISO would be disabled in x10 mode automatically, to be used for focusing.

crop_new:
-Added 11-bitdepth option.
-Adjusted analog gain and LiveView brightness, now it's accurate.
-Detect binning mode change, LiveView will refresh automatically after you change binning mode.

---

Source code is also updated:

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM
Source-code:
magic-lantern-bilal (25-5-2022).7z (https://drive.google.com/file/d/1ZhlTQwCPHHb0QNqrpGHqfV8-NVqv30P7/view?usp=sharing) (crop_rec_4k branch)

Sorry I tried to convert it to git, but I encountered errors and the process failed, will try again later.

-Looking for more recording times?

Check Image quality and its effect on memory (more RAM 4 free) (https://www.magiclantern.fm/forum/index.php?topic=26521.msg239231#msg239231)

Quote from: theBilalFakhouri on June 15, 2022, 06:37:18 PM
-Results on 700D:

-1736x2214 @ 11 bit-lossless at 23.976 FPS, 240 MHz overclock, no GD (~78MB/s required write speed):

JPG:  first clip: 1 Minutes and 54 Seconds, second clip: 1 Minutes and 13 Seconds.
RAW: I have to stop it manually after 6 Minutes of recording :D

-By setting "Image quality" to RAW from Canon menu this fixes "Simple" silent picture on 700D, probably 650D too.

Hello. Installed new firmware on 650d. Dual iso "ISOless LV err(2)" error periodically appears.

Hi Icaab, I didn't mention that I fixed "ISOless LV err(2)" on 650D.

Well, if you are asking for a fix, try this build and report back please:

crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip)

Quote from: theBilalFakhouri on June 17, 2022, 01:13:39 PM
Hi Icaab, I didn't mention that I fixed "ISOless LV err(2)" on 650D.

Well, if you are asking for a fix, try this build and report back please:

crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip)

If you attached the firmware that was posted on May 25, I installed it. Problems with Dual ISO can only be solved this way:
Turn on P mode on camera
Camera turns off
Battery removed and inserted back
Video mode starts
Switches to manual mode (M) and everything works until the camera restarts

You can tell me how to take photos with the following combination of modules:
Dual ISO + Intervalometer + Silent Picture(Burst MLV) + Raw Video + Crop rec v1 or v2(Full-Res 1:1)

When I turn on "Raw Video", my camera hangs during the photographing, and with "Raw Video (MLV)" everything works, but in MLVApp is not recognized Dual ISO.

Thanks

Quote from: Icaab on June 17, 2022, 02:21:47 PM
If you attached the firmware that was posted on May 25, I installed it.

No, the attached build is a different version from what you have tested before. So, again, do a clean install with this build (format SD card on PC then install the build):

Quote from: theBilalFakhouri on June 17, 2022, 01:13:39 PM
Well, if you are asking for a fix, try this build and report back please:

crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip)

Report back, then let's chat.

Quote from: theBilalFakhouri on June 17, 2022, 02:27:17 PM
No, the attached build is a different version from what you have tested before. So, again, do a clean install with this build (format SD card on PC then install the build):

Report back, then let's chat.

Yes, already several times overloaded the camera and ISOless LV ERR(2)no longer. WONDERFUL! Thank you!
Also tested the included "Dual ISO" with "RAW video" and yes - they conflict with each other.

Cool, so no more ISOless errors on your 650D when using crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip), does Dual ISO work in both photo and in video mode?

Quote from: Icaab on June 17, 2022, 05:35:03 PM
Also tested the included "Dual ISO" with "RAW video" and yes - they conflict with each other.

What do you mean by "conflict"? shows errors? could you explain more what do you mean?

Quote from: theBilalFakhouri on June 17, 2022, 01:13:39 PM
Hi Icaab, I didn't mention that I fixed "ISOless LV err(2)" on 650D.

Well, if you are asking for a fix, try this build and report back please:

crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip)

I tested it in video mode around the city today and Dual ISO works overall.

Dual ISO works well except for this one time when I was trying to take a picture with Dual Iso and Crop mode 4.3k 1x3.
I got an overall ML error message and then I had to turn off the camera and remove and set the battery back in.
After turning it back on I got "ISOless LV err(2)".
When I restarted my camera, Dual ISO was working without error!

Thank you :D

Quote from: NykkyC on June 18, 2022, 04:00:38 AM
I tested it in video mode around the city today and Dual ISO works overall.

Dual ISO works well except for this one time when I was trying to take a picture with Dual Iso and Crop mode 4.3k 1x3.
I got an overall ML error message and then I had to turn off the camera and remove and set the battery back in.
After turning it back on I got "ISOless LV err(2)".
When I restarted my camera, Dual ISO was working without error!

Thank you :D

You have tried to take photos when the following modules are included:
Dual Iso,Crop mode v1 or v2, Raw video v1 or v2 and Silent picture (for example burst)
?

Quote from: theBilalFakhouri on June 17, 2022, 06:18:33 PM
Cool, so no more ISOless errors on your 650D when using crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip), does Dual ISO work in both photo and in video mode?

What do you mean by "conflict"? shows errors? could you explain more what do you mean?

I understood: in the video shooting mode when I turn on the modules Dual Iso, Raw video and Silent picture - the camera turns into a brick if I take a photo.

@Icaab

Quote from: Icaab on June 18, 2022, 09:04:08 PM
..Raw video and Silent picture - the camera turns into a brick if I take a photo.

Quote from: Icaab on June 17, 2022, 02:21:47 PM
You can tell me how to take photos with the following combination of modules:
Dual ISO + Intervalometer + Silent Picture(Burst MLV) + Raw Video + Crop rec v1 or v2(Full-Res 1:1)

Currently full resolution presets and silent picture combination doesn't work very well on 700D (needs some memory management). Dual ISO isn't related to problem you are having.

Turning on RAW video and Silent picture will produce memory conflicts, that's why it crashes, especially with "Burst" mode.
Also, Intervalometer seems broken when using Silent picture in some/all cases? e.g. when using Full-Res LiveView. the counter will be broken.

Quote from: Icaab on June 17, 2022, 02:21:47 PM
I turn on "Raw Video", my camera hangs during the photographing, and with "Raw Video (MLV)" everything works, but in MLVApp is not recognized Dual ISO.

I can take pictures when "Raw Video" or "Raw Video (MLV)" is on without problems, how to reproduce this issue?
If crop mode is on, yeah the camera will hang, you need to either turn off crop mode or switch camera to photo mode (I noticed that Crop mode V2 will stay on in photo mode, I will make it turn off automatically in the next release).

Quote from: Icaab on June 17, 2022, 02:21:47 PM
..but in MLVApp is not recognized Dual ISO.

Could you give more details?
I recorded a clip with "RAW video (MLV)" with Dual ISO on, and MLVApp recognizes both ISOs.

---

-I have plans to dig into these issues and make some tries to improve memory management on 700D between crop modes modules, silent picture and RAW video . . but not in near future.

Quote from: NykkyC on June 18, 2022, 04:00:38 AM
I tested it in video mode around the city today and Dual ISO works overall.

Cool, thanks for testing!

Quote from: NykkyC on June 18, 2022, 04:00:38 AM
I was trying to take a picture with Dual Iso and Crop mode 4.3k 1x3.

You shouldn't take pictures when crop mode is on, you need to either trun off crop mode first, or switch the camera to photo mode, "Crop mode" will turn off automatically in photo mode.

Quote from: NykkyC on June 18, 2022, 04:00:38 AM
I got an overall ML error message and then I had to turn off the camera and remove and set the battery back in.
After turning it back on I got "ISOless LV err(2)".
When I restarted my camera, Dual ISO was working without error!

Thanks for mentioning this, so this mean the current method of fixing (https://foss.heptapod.net/magic-lantern/magic-lantern/-/issues/1781) "ISOless LV err(2)" error on 650D isn't perfect, but it's a lot better than before (works in most times).

Well, have fun :)

Quote from: theBilalFakhouri on June 18, 2022, 09:52:36 PM
Turning on RAW video and Silent picture will produce memory conflicts, that's why it crashes, especially with "Burst" mode.
Also, Intervalometer seems broken when using Silent picture in some/all cases? e.g. when using Full-Res LiveView. the counter will be broken.

Intervalometer behaves stably when silent picture in burst.

Quote from: theBilalFakhouri on June 18, 2022, 09:52:36 PM
Could you give more details?
I recorded a clip with "RAW video (MLV)" with Dual ISO on, and MLVApp recognizes both ISOs.

It's working.
I used the following combination for photos with Dual ISO: video mode, Raw Video (MLV), Dual ISO and Intervalometer.
For photo manifestation program cr2hdr, after which everything is easily configured in Photoshop.
The photo gets dark after cr2hdr and when the exposure is raised - there is a noise, even if not
minor. In mlvapp is much MORE. (I think now I can take photos).
But this is not surprising, because expensive cameras like mark 3 are better at shooting at higher ISO values than 650 and 700 cameras.
Then out I do everything correctly. Correct if I made a mistake (but how to process video with dual iso
in mlvapp - I don't know when a lot of noise comes out, unlike the manifestation in cr2hdr)

I think my main mistake was that I looked at the results with the included modules: Dual ISO + Intervalometer + Silent Picture(Burst MLV) + Raw Video + Crop v1 or v2(Full-Res 1:1) on the Mark 3 model. Unfortunately 650-700d is not yet very stable.
I was concerned earlier:
Whether I can shoot with a 14-bit(silent picture) intervalometer and a Dual ISO (instead of a bracketing) to minimally wear the shutter at the camera.
That's why I was interested in using so many modules.

?
If you get Silent Pic mode working it doesn't matter to have Dual-ISO loaded or not in terms of mirror/shutter actuations.

Bilal this build is fantastic. Thank you, great job.

Some feed back for you from my testing so far.

When formatting the card in camera the following folders are being deleted from within ML; cropmks, data, doc, docs, README, scripts. Interestingly all the names of the remaining folders are being changed to all upper case.

This has happened on all my cards when formatting in camera even with low level formatting switched off.

I'm using build; crop_rec_4k_stuckshutter_700D115 (25May2022) on Sandisk 170mb/s all sizes 64, 128, 256, 512

Has anyone else experienced this issue? I wonder... Other than this it's been working flawlessly and I can just delete files from my laptop without needing to format in camera but that's not always practical. My current understanding is that formatting cards in camera is best practice.

I shoot mainly in the 3K preset but reduced to 2.8k 2800 x 1190 @23.976fps. This way I get a beautifully centered frame in real time preview unlike the EOS M which is off centre by some margin.

I just wanted to post this quickly so I apologise if this has been raised previously.

Hope it's useful feedback and thanks again to you and the team for all your hard work.

All the best

Hello. I was shooting the timelaps with dual iso. After the program CR2HDR saw that in the source in the last frames began to appear noises in the form of strips. It's not in the brighter pictures:
(cr2,dng and jpg)
https://mega.nz/folder/uhohlaib#j7AelOhk-7cq5PFQ1-coew (https://mega.nz/folder/uhohlaib#j7AelOhk-7cq5PFQ1-coew)
Currently, the only solution is to reduce noise during processing.
Is it possible to avoid this by changing the configuration of the modules?
(there were fully manual settings and nothing changed during shooting)

@RhythmicEye

Thanks, glad you liked the build.

Quote from: RhythmicEye on July 26, 2022, 04:22:22 PM
When formatting the card in camera the following folders are being deleted from within ML; cropmks, data, doc, docs, README, scripts. Interestingly all the names of the remaining folders are being changed to all upper case.

This has happened on all my cards when formatting in camera even with low level formatting switched off.

Make sure "Keep ML" option is turned on, that way after formatting, ML will restore all ML build files which include cropmarks, scripts.. etc.

Yeah, sometime ML folders/files become in upper case after formatting card in camera with "Keep ML" option turned on, that's happens on my 700D too. I don't see a real problem here, upper case won't affect how ML build works. I think this a small bug which could be fixable (restore ML files/folder in lower case).

Best wishes

Quote from: Icaab on August 17, 2022, 10:50:59 PM
Hello. I was shooting the timelaps with dual iso. After the program CR2HDR saw that in the source in the last frames began to appear noises in the form of strips. It's not in the brighter pictures:
..
Is it possible to avoid this by changing the configuration of the modules?

Seems like cr2hdr issue, nothing to do with ML builds.

In the past, a1ex was taking care for these kind of problems, he wrote cr2hdr code. Currently no one is taking care of cr2hdr.
I don't know if there are some exiting commands can be performed using Command line and cr2hdr which could help in these cases.

650/700d and M share the same performance and video capability?

Quote from: anto on September 17, 2022, 02:28:29 PM
650/700d and M share the same performance and video capability?

Yes

i'm a 650d ML user now

in benchmark only first write speed it's ok.
sometime raw rec works normally with 240hz hack, sometime its lock at 20MB.

93 write speed
20 read

20 write
20 read

micro sd card with adapter (samsung pro plus 128gb)

on the back of the card:

mbddgvgbfw-5
kpnh656ih229
made in philippines

(https://www.linkpicture.com/q/bench1-Medium.jpeg)

Try with the new sd_uhs module from here (https://www.magiclantern.fm/forum/index.php?topic=25841.msg234228#msg234228) , then report back.

Quote from: Walter Schulz on September 28, 2022, 06:37:47 PM
You omitted first line which holds *the* essential information about card version. String should look like
MB-MC128H

MB-MD128K

anyway seams ok with new sd module

(https://i.postimg.cc/0Q3Zkwt3/bench3-Medium.jpg)

Thanks for the test. Will update the builds with latest sd_uhs later.

Hello
The problem began to appear at my camera 650d: the speed of recording began to fall when you shoot several videos at the same time.
Both sandisk cards extreme pro r170/w90 with benchmark show the same results:
(https://i.ibb.co/sPWdBGw/bench1.png) (https://ibb.co/sPWdBGw)
Should I turn off some parameters?
Attach my settings profile at the same time
https://mega.nz/file/7ww1lApC#hb2t-nr0_h7Fh-p3dugcSXwgf0Yk49ZhbNzRkweELf8 (https://mega.nz/file/7ww1lApC#hb2t-nr0_h7Fh-p3dugcSXwgf0Yk49ZhbNzRkweELf8)

Edit:
Low-level formatting was done on both memory cards;sd_uhs latest version.

Edit2:
And also about the firmware: I shot with dual iso, fps override and crop mode v2, where I chose preset x5, and when the scene becomes darker - on the video there are pronounced noise vertical lines (sometimes helped to turn on the fix preview, but also does not always work)
(https://i.ibb.co/VmV1pQb/Screenshot-1432.png) (https://ibb.co/VmV1pQb)
Here is the source:
https://mega.nz/file/L95iwR6K#LzE82LuWTq9CZRShWvXlg9scq8x40C_DyWqov_gG-ao (https://mega.nz/file/L95iwR6K#LzE82LuWTq9CZRShWvXlg9scq8x40C_DyWqov_gG-ao)

Hello
Are you ever planning to upgrade the firmware 650-700d with the correction of noise stripes, falling speed, etc.?

@Icaab

I don't have "faliling speed" problem (SD card write speed drop?), could you record a video which shows what are you doing then upload it to Youtube?
For "vertical lines" or "noise stripes" problems, plz share a short MLV clip (1-2 seconds are enough), and upload it somewhere, I can't download big file sizes. It would be better to be 200 MB or lower.

The photos in reply #256 (https://www.magiclantern.fm/forum/index.php?topic=25784.msg240789#msg240789) are dead, could you re-upoad them?

Quote from: theBilalFakhouri on January 04, 2023, 08:09:17 PM
@Icaab

I don't have "faliling speed" problem (SD card write speed drop?), could you record a video which shows what are you doing then upload it to Youtube?
For "vertical lines" or "noise stripes" problems, plz share a short MLV clip (1-2 seconds are enough), and upload it somewhere, I can't download big file sizes. It would be better to be 200 MB or lower.

The photos in reply #256 (https://www.magiclantern.fm/forum/index.php?topic=25784.msg240789#msg240789) are dead, could you re-upoad them?

Noisy stripes
I didn't know what to show. I think you just wanted to configure the modules for shooting Video. Dual ISO I did not turn on here, and the stripes still came out
https://youtu.be/yPvp4PkfeZo (https://youtu.be/yPvp4PkfeZo)
Here was fog machine and lens sigma 18-35 with f2.0 (the character himself that will stand in the scene, bright and based on it exhibited exposure, not Christmas tree)
https://mega.nz/file/D4J1DRrS#llV30fYvxev6Y5hQP8gOrs2O051t27Kbzm9pFNV616A (https://mega.nz/file/D4J1DRrS#llV30fYvxev6Y5hQP8gOrs2O051t27Kbzm9pFNV616A)
Here changed the lens on the Canon 85mm f/1.8 USM EF and exhibited the same aperture 2, but the fog is small and the skin relief itself is quite white and it shows the stripes at the top of the video where there is no focus (however, they are different and not as significant as in the video above)
https://mega.nz/file/qk5z3a7C#NrcwCbYJXHhuOVB-ZWt2JsbxOXixbtvchGdyb0rX3aM (https://mega.nz/file/qk5z3a7C#NrcwCbYJXHhuOVB-ZWt2JsbxOXixbtvchGdyb0rX3aM)
Here with dual iso they are (on dark clouds visible stripes)
https://mega.nz/file/a15SWZhI#29lQ8l_MzLqr8WMHwLkkoQCx5iTn5N5Al2aAtK-ubLc (https://mega.nz/file/a15SWZhI#29lQ8l_MzLqr8WMHwLkkoQCx5iTn5N5Al2aAtK-ubLc)

Falling speed
It happens periodically when a lot of video is shooting in one hour. I went to shoot nature and turned on dual iso and there the fall of speed manifested strongly.
But when there was a lot of filming at my house, but not so often, the speed of recording dropped less.
The same benchmark shows the speed drop over time (I checked both my memory cards - sandisk extreme pro 128gb):
(https://i.ibb.co/34JGM5m/bench0.png) (http://<img%20src="https://i.ibb.co/34JGM5m/bench0.png">)

Please repeat benchmark in PLAY mode.
Benchmark number decrease with decreasing block/buffer size, not because of time passed.

(https://i.ibb.co/7yCvkZD/20230107-165656.jpg) (http://<img%20src="https://i.ibb.co/7yCvkZD/20230107-165656.jpg"%20alt="20230107-165656"%20border="0">)
Yes, with this benchmark speed does not fall
But how then to explain that when you try to continuously shoot a lot of videos - the maximum time that footage can be recorded is reduced. (shot more than a minute, and then no more than 30 seconds - for example)

Last tests I did was some weeks ago. I used 650D, too and observed no decline doing continuous recording for 6 minute takes until card was full. Speed was shy of 80 MByte/s.

Redo your test without lossless compression to avoid side effects. Esp. high exposure/overexposure will reduce compression efficiency (and worse).

@Icaab

"Falling speed"

Your SD card seems fine. as Walter said the first benchmark (https://www.magiclantern.fm/forum/index.php?topic=25784.msg241355#msg241355) isn't related to what you are facing.
More likely your scenes are complex and you probably always use 14-bit lossless which requires fast write speed in some scenes in UHD 1x3 mode (could be more than 80 MB/s; more than the camera can handle).

You can check how much does RAW video recording needs in specific scene by higlighting "RAW video" in "Movie" tab, and check ML bottom bar.
If the required write speed is too high, you either need to enable "aewb" hack (which could gain 5-7 MB/s write speed) or use lower bit-depth from "Crop mode" submenu, like 12-bit.

"Noisy stripes"

I could see some vertical stripes after pushing contrast and some other settings in "M30-0751.mlv" clip, and it's probably there in "M30-0803.mlv" clip too (barely visible).
I think you will need to use dark frame to get rid of these vertical stripes, have you ever used dark frame before?

You can do that in MLVApp.

for "3 v M15-1653.mlv" Dual-ISO clip, it seems to me these are other type of vertical stripes which can come from Timer A (or B?) at specific values. The main cause for this is by using FPS override in some "Crop mode" presets like UHD 1x3. I am assuming you have used FPS override with UHD 1x3 preset, right?

To make sure, record a clip (like a cloudy sky, the scene must show vertical stripes as in Dual ISO shot), fiirst time using the same settings (5 FPS, UHD 1x3) and another time without FPS override, then upload them somewhere.

Hi Bilal. Unfortunately, the link you gave for the 650d is unavailable. Can you repost?

Hi @drmrtdmr

Which link exactly?

 https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip) this link

Quote from: drmrtdmr on January 08, 2023, 10:45:00 PM
https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip (https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads/crop_rec_4k.2022May25.650D104_ISOless.zip) this link

Works like a charm. Problem is on your side.
Try to access https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads

Quote from: Walter Schulz on January 08, 2023, 10:50:58 PM
Works like a charm. Problem is on your side.
Try to access https://bitbucket.org/bilal_fakhouri/magic-lantern/downloads

It enters the site you gave, but when I click on the file, it gives an error. I tried it on all my devices.

Quote from: drmrtdmr on January 08, 2023, 11:02:28 PM
It enters the site you gave, but when I click on the file, it gives an error. I tried it on all my devices.

Sounds like some connected device (home router,internet provider) doesn't like github. Have you tried proxy/VPN?

The link works fine. For me I have to use VPN to access bitbucket.

Quote from: Walter Schulz on January 07, 2023, 03:08:27 PM
Last tests I did was some weeks ago. I used 650D, too and observed no decline doing continuous recording for 6 minute takes until card was full. Speed was shy of 80 MByte/s.

Redo your test without lossless compression to avoid side effects. Esp. high exposure/overexposure will reduce compression efficiency (and worse).

Did you mean in the Movie > Raw video > Data format switch 14-bit losless to 14 bit? In this case, the camera can not record one second of the video, no matter how I reduce the bit (and in "RAW video" it is written that the speed required is 110.6 mb/s)

Quote from: theBilalFakhouri on January 07, 2023, 04:48:33 PM
@Icaab

"Falling speed"

Your SD card seems fine. as Walter said the first benchmark (https://www.magiclantern.fm/forum/index.php?topic=25784.msg241355#msg241355) isn't related to what you are facing.
More likely your scenes are complex and you probably always use 14-bit lossless which requires fast write speed in some scenes in UHD 1x3 mode (could be more than 80 MB/s; more than the camera can handle).

You can check how much does RAW video recording needs in specific scene by higlighting "RAW video" in "Movie" tab, and check ML bottom bar.
If the required write speed is too high, you either need to enable "aewb" hack (which could gain 5-7 MB/s write speed) or use lower bit-depth from "Crop mode" submenu, like 12-bit.

"Noisy stripes"

I could see some vertical stripes after pushing contrast and some other settings in "M30-0751.mlv" clip, and it's probably there in "M30-0803.mlv" clip too (barely visible).
I think you will need to use dark frame to get rid of these vertical stripes, have you ever used dark frame before?

You can do that in MLVApp.

for "3 v M15-1653.mlv" Dual-ISO clip, it seems to me these are other type of vertical stripes which can come from Timer A (or B?) at specific values. The main cause for this is by using FPS override in some "Crop mode" presets like UHD 1x3. I am assuming you have used FPS override with UHD 1x3 preset, right?

To make sure, record a clip (like a cloudy sky, the scene must show vertical stripes as in Dual ISO shot), fiirst time using the same settings (5 FPS, UHD 1x3) and another time without FPS override, then upload them somewhere.

Yeah, I know what you wrote. Unfortunately, there are probably failures in the camera and at one point it can not properly shoot a few seconds, as if not changing the bit depth(in the scene only my room).And so the fruitless shooting goes for five minutes, and then the problem disappears by itself and  I can shoot continuously even in 14-bit depth.

Yes, I know about the darkframe, but what's the point when I have a bright picture, shooting was with 200 iso and the exposure settings were not properly changed in mlvapp? I'll try it next time, but I've never seen such a problem with vivid frames

Bilal, what Walter Schulz meant when he said

QuoteRedo your test without lossless compression to avoid side effects. Esp. high/overexposure will reduce compression efficiency (and worse).

How do I do that?

hi bilal,
just curious, is it possible to implement transfer function like in mlvapp to camera?
I think it would be great to have log recording in camera..

thanks..

Quote from: ML700D on January 19, 2023, 03:58:24 AM
is it possible to implement transfer function like in mlvapp to camera?
I think it would be great to have log recording in camera..

MLVApp uses the power of CPUs - and you know how fast it processes. The camera has a tiny MPU. Transfer function must be applied on all pixels in all frames. I doubt you'll get more than 1fps, probably less... ;)

Quote from: Icaab on January 18, 2023, 09:34:42 PM
Yes, I know about the darkframe, but what's the point when I have a bright picture, shooting was with 200 iso and the exposure settings were not properly changed in mlvapp? I'll try it next time, but I've never seen such a problem with vivid frames

Just to make sure, you are not talking about "flickering" because of artificial lighting?

I mean by "flickering" is like this (https://www.youtube.com/watch?v=FLQMvDfERrs).
Because two of your MLV samples have flickering, "M30-0803.mlv" and "M30-0751.mlv" clips.

Also, could you share a rendered "vivid frame" which shows the artifacts clearly?

I don't have such problem on my 700D, and if you was talking about something like fixed-pattern noise, there is no magic setting can remove it, so I can't fix something like this.
Beside, every sensor has its own fixed-pattern noise . . the simplest way I know to get rid of it is to use a darkframe.

Quote from: Icaab on January 18, 2023, 09:34:42 PM
Bilal, what Walter Schulz meant when he said 
How do I do that?

He means to use uncompressed MLV RAW format, like 14-bit uncompressed, you can find the setting in "RAW video" submenu which is "Data format".
If the required write speed was too high, reduce the resolution until you have ~80 MB/s required write speed, to be able to do the test.

Also, you need to use hacks and pic quality trick to maximize write speed, these were coverd in first post in this thread.

Quote from: ML700D on January 19, 2023, 03:58:24 AM
just curious, is it possible to implement transfer function like in mlvapp to camera?
I think it would be great to have log recording in camera..

For H.264 recording?

I don't know if that possible also I don't know how transfer function works (even in MLVApp), but in general someone needs to understand Canon pipeline for image processing, if we are lucky enough it could be there some kind of "transfer function", but again . . someone needs to find from where the parameters could be controlled (assuming if there is a "transfer function").

If there isn't, I think it would hard, for processing speed there are hardware accelerators used for image processing in our cameras, and good luck with figuring out how to use them for our purposes.

Quote from: theBilalFakhouri on January 20, 2023, 12:14:44 AM
For H.264 recording?

for mlv recording.. like other cam that use log to record video

Quote from: theBilalFakhouri on January 20, 2023, 12:14:44 AM
I don't know if that possible also I don't know how transfer function works (even in MLVApp), but in general someone needs to understand Canon pipeline for image processing, if we are lucky enough it could be there some kind of "transfer function", but again . . someone needs to find from where the parameters could be controlled (assuming if there is a "transfer function").

If there isn't, I think it would hard, for processing speed there are hardware accelerators used for image processing in our cameras, and good luck with figuring out how to use them for our purposes.

I see..

btw, I found this on Wikipedia Transfer Functions in Imaging (https://en.wikipedia.org/wiki/Transfer_functions_in_imaging)

.

Hi. I'm sorry if this topic has already been discussed, but I have a question... First of all, thank you Bilal and all other users for the work you have been doing with these experimental builds. My question is with regards to the raw video live-view and the displayed aspect ratio (AR) using the latest 700D build. I like to use "Crop mode" (the normal version, not V2) and "RAW video"; the camera does not display the correct AR I selected and this happens with any crop preset I use. The only solution is to choose my settings and then restart the camera. It then will show the correct AR setting once booted, but it defaults to an incorrect view right after recording and I have to keep restarting inbetween every shoot. Is this a common "issue"? I have tried changing the Preview option to "Framing" but it always defaults to "Real-time".

Hello @azki , thanks!
I never had such an issue. Could you record a video shows the problem, what are you doing and ML settings, then upload it on Youtube?

In presets which have real-time correct previews like 1x3 presets, the preview will be always set to real-time automatically, because "Framing" preview doesn't make sense if real-time preview is correct.
I will change this behavior later this year in a new build.

Quote from: ML700D on January 20, 2023, 05:30:50 AM
for mlv recording.. like other cam that use log to record video

AFAIK, Transfer Function or "LOG" is only applciable to compressed lossy formats (like ProRes, H.264, H.265 ..etc), but not to RAW data.

Quote from: theBilalFakhouri on January 23, 2023, 09:30:21 AM
AFAIK, Transfer Function or "LOG" is only applciable to compressed lossy formats (like ProRes, H.264, H.265 ..etc), but not to RAW data.

I see..
can ml build add more format beside RAW maybe prores or something else better than just 8 bit canon recording?
so the log can be applied, I think it will be more versatile..

I hope.. 😅

Thread "Features that are NOT possible -  please don't request them"

Quote from: a1ex on May 24, 2012, 02:02:23 PM
Custom codecs
Codecs are not implemented on the general-purpose ARM processor. We can only use what Canon has already included in hardware (H.264, JPEG, LJ92) and fine-tuned their parameters (such as the H.264 bit rate).

The lossless compression used for raw video is the same "codec" Canon uses for CR2. The same processing path (codenamed JPCORE) might be able to handle (M)JPEG. However, we cannot implement additional codecs (such as H.265, JPEG2000 or ProRes). Even if these might be able to run on Canon's image processing hardware, we simply don't know where to start.

ah.. I see..
thanks Walter for the explanation..

No more wild thoughts, I accept ML as it is..

📸

is it save just to copy from already installed ML and paste to new card?
or I have to fresh install again in new card?

thanks.

https://wiki.magiclantern.fm/faq
https://wiki.magiclantern.fm/install

Quote from: Walter Schulz on January 24, 2023, 04:24:52 PM
https://wiki.magiclantern.fm/faq
https://wiki.magiclantern.fm/install

thanks once again Walter.. 😁

Quote from: theBilalFakhouri on January 23, 2023, 09:22:40 AM
I never had such an issue. Could you record a video shows the problem, what are you doing and ML settings, then upload it on Youtube?

Hi Bilal, thank you for your response.

I am sorry, I was testing a little bit more and while I was recording a short video of my settings to show you, I just realised I might have misuderstood how these 1x3 crops were supposed to be used. I was using the 4.3K 1x3 setting in crop_rec and seems like this preset is meant to record 4.3K in 2.35:1 aspect ratio (AR) only, giving me a "final" un-stretched resolution of 4320x1836, right? I was incorrectly trying to use this preset to record in different "less wide" ARs, like 1.85:1 or 2.00:1 (and of course you can't get more vertical pixels in there, but I was expecting it would crop it somehow repesctively to the AR I selected in the RAW video option). Since it is not possible it then reverts the live-view to the correct 2.35:1 AR for use with that preset. When I said that if I reboot the camera the correct AR would then display (1.85:1 for example), it actually is displaying the resolution as it would with crop_rec turned off and using mlv_lite only (3x3 with max height resolution of 1736 px in any AR). I guess what I should do is use your 4K 1x3 preset for 2.00:1 videos and UHD 1x3 with a bit of cropping for 1.85:1. If I want to record with a custom AR (lets say 1.70:1), in a resolution higher than ~2K, is best to play around with crop_new and try out different settings, right?

Thank you once again, I don't know if this made any sense xD

Yes, maximum AR and resolution should be used in 1x3 presets in crop_rec, these how presets work currently. reducing resolution or changing AR from RAW video while using these presets will result in wrong cropped RAW data and wrong real-time preview.

That's why I wrote the following, in first post (https://www.magiclantern.fm/forum/index.php?topic=25784.msg231049#msg231049) in this thread :):

Quote from: theBilalFakhouri on September 18, 2020, 07:51:30 PM
General notes:
-Use maximum aspect ratio and and resolution from mlv_lite when using crop_rec presets with real-time correct preview, otherwise mlv_lite won't crop the RAW data correctly.

Unfortunately, tweaking or making new 1x3 presets with correct preview and with different aspect ratios isn't a simple task currently.

Quote from: azki on January 25, 2023, 02:57:58 AM
If I want to record with a custom AR (lets say 1.70:1), in a resolution higher than ~2K, is best to play around with crop_new and try out different settings, right?

Correct, but you will lose the real-time correct preview, LiveView will be stretched. However "Framing" preview will be still an option to use with crop_new.

Quote from: azki on January 25, 2023, 02:57:58 AM
Thank you once again, I don't know if this made any sense xD

Yes, everything you wrote made sense and seems correct, no problem :)

Quote from: theBilalFakhouri on January 19, 2023, 11:50:24 PM
Just to make sure, you are not talking about "flickering" because of artificial lighting?

I mean by "flickering" is like this (https://www.youtube.com/watch?v=FLQMvDfERrs).
Because two of your MLV samples have flickering, "M30-0803.mlv" and "M30-0751.mlv" clips.

Also, could you share a rendered "vivid frame" which shows the artifacts clearly?

I don't have such problem on my 700D, and if you was talking about something like fixed-pattern noise, there is no magic setting can remove it, so I can't fix something like this.
Beside, every sensor has its own fixed-pattern noise . . the simplest way I know to get rid of it is to use a darkframe.

He means to use uncompressed MLV RAW format, like 14-bit uncompressed, you can find the setting in "RAW video" submenu which is "Data format".
If the required write speed was too high, reduce the resolution until you have ~80 MB/s required write speed, to be able to do the test.

Also, you need to use hacks and pic quality trick to maximize write speed, these were coverd in first post in this thread.

Hello
Yes, I was wrong: my homemade LED light starts banding when I reduce its luminosity with a dimmer. I will redo it.
Vivid frame - this is the source of M30-_, where banding is visible

Bilal, tell me: I correctly understand that with firmware correctly shooting with minimal ISO? I always lack light and I for the video include ISO 200 because of the fear that there will be a lot of color noise if there is ISO higher.
However, MLVApp has a feature to remove color noise and then with 400 ISO footage looks not so bad. Although the same scene varies between 200 and 400 ISO...are they a little different in their sharpness...
https://mega.nz/folder/a1ojlbwK#ZFBsusu_4owrUakcbfvXUw (https://mega.nz/folder/a1ojlbwK#ZFBsusu_4owrUakcbfvXUw)

hi bilal,
I got dual ISO flicker issue using 1440p 1x1 100/800 pressed record in 10x view
and one with standard raw 3x3 recorded in 5x view

here: Sample Files (https://drive.google.com/drive/folders/1CELH6U_8smDTTReD8_ttx1C_gUkQ3alQ?usp=sharing)

btw, when using preset the shutter is changing now.. not 180° or 1/50?
(https://i.ibb.co/7xD1b86/Screenshot-2023-02-18-132904.png)

thanks.

Quote from: Icaab on February 01, 2023, 10:33:12 AM
Bilal, tell me: I correctly understand that with firmware correctly shooting with minimal ISO?

ISO 100 is the minimal on 650D/700D and probably the native ISO. You can already shoot at it.

Quote from: Icaab on February 01, 2023, 10:33:12 AM
I always lack light and I for the video include ISO 200 because of the fear that there will be a lot of color noise if there is ISO higher.

Add more light or use a video denoiser in post. Neat Video does a great job, also Davinci Resolve. If there is no much movement on your scene you will want to use temporal denoising.

Quote from: Icaab on February 01, 2023, 10:33:12 AM
However, MLVApp has a feature to remove color noise and then with 400 ISO footage looks not so bad. Although the same scene varies between 200 and 400 ISO...are they a little different in their sharpness...
https://mega.nz/folder/a1ojlbwK#ZFBsusu_4owrUakcbfvXUw (https://mega.nz/folder/a1ojlbwK#ZFBsusu_4owrUakcbfvXUw)

Higher noise = lower sharpness/details

In 650D/700D usable ISO range is 100-1600, I mean by "usable" that when switching to higher ISO . . the shadows become cleaner in cost of dynamic range (in highlights).
e.g. Going from 100 ISO to 200 ISO you get 0.9 stops cleaner in shadows, but you lose 1 stop in highlights (if there is clipping), other ISOs (this applies to video mode, in photo mode shadows might be better):

-Going from 100 ISO to 200     (+0.9 stop cleaner in shadows, -1 stop  in highlights)
-Going from 200 ISO to 400     (+0.8 stop cleaner in shadows, -2 stops in highlights)
-Going from 400 ISO to 800     (+0.3 stop cleaner in shadows, -3 stops in highlights)
-Going from 800 ISO to 1600   (+0.3 stop cleaner in shadows, -4 stops in highlights)
-Going from 1600 ISO to 3200 (+0.1 stop cleaner in shadows, -5 stops in highlights)

So:
-Going from 100 ISO to 400   (+1.7 stop cleaner in shadows, -2 stops in highlights)
-Going from 100 ISO to 800   (+2.0 stop cleaner in shadows, -3 stops in highlights)

So using higher ISO in low light and as long as there is no highlights clipping (because of higher ISO) you should use higest usable ISO from 100 to 1600.

If we matched exposure in MLVApp for your clips:

-M31-1541, 200 ISO, pushed +1 stop in MLVApp:
(https://i.ibb.co/WKddxwL/M31-1541-200-ISO.jpg)

-M31-1540, 400 ISO:
(https://i.ibb.co/fQCt1KB/M31-1540-400-ISO.jpg)

400 ISO clip is apparently cleaner (view images in full size), and you didn't lose highlights (you didn't reach clipping point).


Same frames +3 stops:

-M31-1541, 200 ISO:
(https://i.ibb.co/QnL4z00/M31-1541-200-3-stops.jpg)

-M31-1540, 400 ISO:
(https://i.ibb.co/fNjPLXz/M31-1540-400-3-stops.jpg)

-M31-1540, 400 ISO, with neat video:
(https://i.ibb.co/C6sRcH1/M31-1541-neat-video.jpg)

Results will be better if you used dark-frame too (e.g. before de-noising).

Quote from: ML700D on February 18, 2023, 05:36:23 AM
hi bilal,
I got dual ISO flicker issue using 1440p 1x1 100/800 pressed record in 10x view
and one with standard raw 3x3 recorded in 5x view

here: Sample Files (https://drive.google.com/drive/folders/1CELH6U_8smDTTReD8_ttx1C_gUkQ3alQ?usp=sharing)

Hello!

Good samples, unfortunately the issue is coming from Dual ISO processing algorithm, not from my builds. I only tested MLVApp and there is flickering. Didn't test cr2hdr, may work better.
More likely it's something related with black level in Dual ISO processing algorithm.

-But why you are uisng 12-bit uncompressed?

AFAIK, Dual ISO works better in 14-bit (either uncompressed or lossless), but for lower bit-depths and for Dual ISO, always use lossless, it works better than uncompressed lower bit-depths.
And that's probably because black level there is same as 14-bit lossless (maybe that's why Dual ISO works better at lower bit-depths in lossless).

Quote from: ML700D on February 18, 2023, 05:36:23 AM
btw, when using preset the shutter is changing now.. not 180° or 1/50?
(https://i.ibb.co/7xD1b86/Screenshot-2023-02-18-132904.png)

Correct, it seems you are using Full "Shutter range" in "Crop mode" submenu. This way you will need to read shutter speed from ML menu to get the correct shutter speed, and not from Canon overlay which would be incorrect.

Quote from: theBilalFakhouri on February 19, 2023, 07:32:50 AM
Hello!

Good samples, unfortunately the issue is coming from Dual ISO processing algorithm, not from my builds. I only tested MLVApp and there is flickering. Didn't test cr2hdr, may work better.
More likely it's something related with black level in Dual ISO processing algorithm.

Oh.. I see, thanks for explanation.

Quote from: theBilalFakhouri on February 19, 2023, 07:32:50 AM
-But why you are uisng 12-bit uncompressed?

AFAIK, Dual ISO works better in 14-bit (either uncompressed or lossless), but for lower bit-depths and for Dual ISO, always use lossless, it works better than uncompressed lower bit-depths.
And that's probably because black level there is same as 14-bit lossless (maybe that's why Dual ISO works better at lower bit-depths in lossless).

I use 12-bit just for experiment only, because I saw in ML note that 14-bit lossless recommended iso < 100 that's why I tried 12-bit uncompressed lol.
so, is it better to use just 14-bit lossless for all other recording too?

Quote from: theBilalFakhouri on February 19, 2023, 07:32:50 AM
Correct, it seems you are using Full "Shutter range" in "Crop mode" submenu. This way you will need to read shutter speed from ML menu to get the correct shutter speed, and not from Canon overlay which would be incorrect.

ah.. I see, thanks bilal.. problem solved

Quote from: ML700D on February 19, 2023, 03:22:04 PM
I use 12-bit just for experiment only, because I saw in ML note that 14-bit lossless recommended iso < 100 that's why I tried 12-bit uncompressed lol.

You get the best compression at 100 ISO yes (in term of file sizes), that's what that mean. But the quality is identical among uncompressed vs lossless, you don't loss any data.
Also, you always get small file sizes if you used lossless compared to uncompressed (50-60% compression in lossless). There is no real point to use uncompressed.

Quote from: ML700D on February 19, 2023, 03:22:04 PM
so, is it better to use just 14-bit lossless for all other recording too?

Yes, always select 14-bit lossess under RAW video submenu.
If you are using crop modes and you want to use lossless at lower bit-depths, there is another bit-depth in "Crop mode" submenu, you can select lower bit-depths from there.

I see.. many thanks bilal!

Quote from: ML700D on February 18, 2023, 05:36:23 AM
hi bilal,
I got dual ISO flicker issue using 1440p 1x1 100/800 pressed record in 10x view
and one with standard raw 3x3 recorded in 5x view

here: Sample Files (https://drive.google.com/drive/folders/1CELH6U_8smDTTReD8_ttx1C_gUkQ3alQ?usp=sharing)

btw, when using preset the shutter is changing now.. not 180° or 1/50?
(https://i.ibb.co/7xD1b86/Screenshot-2023-02-18-132904.png)

thanks.

Hi, if you are using windows, can you please try this build and see if there is less flickering?: https://mega.nz/file/A1tiTASK#OK46h1pPjzsJDILuHyoGQNbLWM6VVm0u7lUfm41CE1A (https://mega.nz/file/A1tiTASK#OK46h1pPjzsJDILuHyoGQNbLWM6VVm0u7lUfm41CE1A)
If you use mac, you can try compiling this fork: https://github.com/anibarro/MLV-App

Hi Bilal and everyone on this thread. Reading all your messages inspired me to get a 650d and try magic lantern for the first time.
Its amazing to see a great discussion and an amazing support from you Bilal. Thank you for that.

I haven't installed your ML version yet as I want to check with you and the members on the thread first about the SD card. I've read all the pages and I could find that you recommend the Sandisk Extreme PRO 64GB 170MB/s that works well in 240hz. Can I also get an even faster SD card that support higher writing speeds? Will it be also stable?
Maybe the camera wont be able to achieve higher writing speed but I am thinking that I will be able to use it in a newer model in the future.

Thank you again for your amazing firmware and the support on this channel.

Quote from: sriver_fx on March 04, 2023, 12:17:04 PM
Can I also get an even faster SD card that support higher writing speeds? Will it be also stable?

Here is a small list of recommended cards:
https://www.magiclantern.fm/forum/index.php?topic=25841.0

And there is no way to predict card type's reaction to overclocking. It is trial and error.

Thank you sriver_fx!

Quote from: sriver_fx on March 04, 2023, 12:17:04 PM
I could find that you recommend the Sandisk Extreme PRO 64GB 170MB/s that works well in 240hz.

Correct, back then Sandisk Extreme PRO 170MB/s was the only recommended SD card, but that's not mandatory anymore.
Now there are many SD cards works at 240 MHz, as Walter shared a link for the tested SD cards at 240 MHz.

Quote from: sriver_fx on March 04, 2023, 12:17:04 PM
Can I also get an even faster SD card that support higher writing speeds? Will it be also stable?

As Walter said, we don't know if other and faster SD cards (like UHS-II) would work, no way to predict except for doing actual tests.
However, one guy has tested UHS-II SD card on EOS M which is "Lexar UHS-II V90", which performs the best write speed at 240 MHz:

Quote from: theBilalFakhouri on September 16, 2022, 09:15:24 AM
Card used: LEXAR UHS-II  V90 @ 240 MHz on EOS M:

(https://i.ibb.co/yVC7cJL/307006505-10160083455853563-6688025535724854510-n.jpg) (https://ibb.co/d7vxwyn)

But UHS-II SD cards are really expensive compared to UHS-I, it's up to you anyway.

Have fun!

Has anyone heard of a crop mode and or overclocking for the 1100d ?
Also I can't push the resolution hihger than 1408p horizontal (It doesn't seem to be speed limited as it could do this resolution at 25 fps and when i lowered to 5 fps it would allow for a higher horizontal resolution)
Does someone know why ?

We are completely offtopic here. Your question may be properly placed in "General Help Q/A" or "Camera-specific development" -> "Canon 1100D" (sticky thread).

Most likely you are stuck with Canon's native resolution roughly computed "horizontal pixel count/3". You will find more info on this in https://wiki.magiclantern.fm/glossary -> Binning.
Solution is described in FAQ: https://wiki.magiclantern.fm/faq#raw_mlvcan_t_set_resolution_to_full-hd1920_is_not_possible_in_current_video_mode_max_1728

There is no overclocking feature for Digic 4 cameras. You are limited to around 21 MByte/s which allows - give or take - 540p25.

Consider using an experimental build as lua_fix or 10/12-bit. https://builds.magiclantern.fm/experiments.html

Please switch to forums mentioned above for 1100D-related issues.

Does 650D/700D ML have electronic level? I know 5d3 has it and I use it constantly. Thanks a lot, Bilal and all ML gurus.

No level.

Quote from: Walter Schulz on March 17, 2023, 11:11:07 PM
No level.

thanks a lot for the info, walter.

I would like to ask for your help because I'm new here. I've been trying to set up all the options in this version correctly for several days, but something is always wrong and I'm already quite confused. I am interested in the 4.3K option and everything seems to be okay - the recording is in green, but there is a problem with the shutter speed - even if I manage to set it to 1/50 (or I can't), there is still some other value later - for example, 1/26, 1/31 - why are these values different?

I just want to set 4.3K, 25 fps, and 1/50 shutter speed, and I can't change the last parameter. I also got confused with other settings. Which settings are superior (more important) - those from the general ML version or Bilal's crop_rec_4k?

I have the modules set as in the screen capture. Should I change any other modules or general parameters in ML before starting Crop mode (crop_rec)?

I'm sorry if I'm asking stupid questions, but I'm just going around in circles and can't find a solution.

My camera is 650D

Greetings from sunny but still cold Poland.

Tom

Quote from: Tomasz Szladowski on April 05, 2023, 03:04:58 PM
..but there is a problem with the shutter speed - even if I manage to set it to 1/50 (or I can't), there is still some other value later - for example, 1/26, 1/31 - why are these values different?

I just want to set 4.3K, 25 fps, and 1/50 shutter speed, and I can't change the last parameter. I also got confused with other settings. Which settings are superior (more important) - those from the general ML version or Bilal's crop_rec_4k?

Could you record a video shows ML settings and what are you doing, then upload the video to Youtube?
Are you able to change shutter speed from ML menu? Does the value change when you tweak shutter speed from ML menu?

On 650d, shutter speed maintains at 25 in this preset. but push the info button, you can see the real shutter value.

Quote from: mlrocks on April 06, 2023, 05:21:22 AM
On 650d, shutter speed maintains at 25 in this preset. but push the info button, you can see the real shutter value.

If the actual shutter speed value is displayed after pressing the "info" button, then everything is fine - thank you for your help :) I was just adjusting the shutter speed earlier and the image on the screen either was darkened or brightened, which would suggest a change in shutter speed, but the value on the screen did not reflect that.

Quote from: theBilalFakhouri on April 06, 2023, 04:51:33 AM
Could you record a video shows ML settings and what are you doing, then upload the video to Youtube?
Are you able to change shutter speed from ML menu? Does the value change when you tweak shutter speed from ML menu?

theBilalFakhouri, mlrocks explained to me that the correct shutter speed value for the Canon 650D appears after pressing the "info" button, so I think I this problem is solved.
By the way, I have another question for you.
I would like to lighten the load on my SD card (SanDisk Extreme Pro) (sometimes it turns orange when recording. I did test - it is usually 60-68 MB/s write speed) and change the resolution to approximately 4.1K (1:3, e.g. 1381x1763) at a ratio of 2.35.
I know I need to use Crop v2. Should I enter both resolution values or is one enough and the 1:3 option will automatically choose the other? I tried both ways but each time the values displayed in crop2 were different from the ones I entered.

Best regards,

Tom

p.s.

It's still cold today, but without the sun.