DOWNLOADS:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
Code:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/src/master/
Is there any reason to have halfshutter button switch to framing when real-time preview is selected now when all presets are realtime? This is causing some overhead while recording. I´d suggest changing in mlv_lite.c:
if (PREVIEW_AUTO)
{
/* half-shutter overrides default choice */
if (preview_broken) return 1;
return prefer_framing_preview ^ long_halfshutter_press;
}
else if (PREVIEW_CANON)
{
return long_halfshutter_press = 0;
}
else if (PREVIEW_ML)
{
return !long_halfshutter_press;
}
else if (PREVIEW_HACKED)
{
if (preview_broken) return 1;
return (RAW_IS_RECORDING || prefer_framing_preview)
^ long_halfshutter_press;
}
return 0;
Also a suggestion if working with auto focus. By not enabling aewb_enableaewb in small_hacks and more hacks auto focus will still work with those hacks on. Maybe possible to detect if cam af is on and unselect:
/* disable auto exposure and auto white balance */
//call("aewb_enableaewb", unhack ? 1 : 0); /* for new cameras */
call("lv_ae", unhack ? 1 : 0); /* for old cameras */
call("lv_wb", unhack ? 1 : 0);
and here:
if (!video_mode_crop && !use_h264_proxy()) /* Exlude Movie Crop Mode and H.264 Proxy from these hacks */
{
if (!unhack) /* hack */
{
WillSuspendAeWbTask = 1; // we are going to suspend AeWb task (check code around shutter_blanking_idle in crop_rec.c)
wait_lv_frames(1);
if (small_hacks == 2)
{
lvfaceEnd();
//aewbSuspend();
}
if (small_hacks == 3 && CartridgeCancel_works) // CartridgeCancel_works: calling CartridgeCancel(); freezes LiveView in some models
{
lvfaceEnd();
//aewbSuspend();
CartridgeCancel();
wait_lv_frames(2); /* In some cases the first frame would be corrupted when calling CartridgeCancel */
}
}
Also curious. Is it not possible to get 16:9 in 1:1 crop modes?
A general black level question. A user noticed black level on eosm(and other digic V cameras I suppose) ends up with 2047. Isn´t it supposed to land at 2048? Correcting this in Mlv App gives a more balanced image.
How to handle this? In raw.c it could be hard coded around here:
/* black level looks alright, go ahead and use it */
/* log significant changes to console */
if (ABS(black_mean - raw_info.black_level) >= 10)
{
printf("Black level: %d\n", black_mean);
}
raw_info.black_level = black_mean;
It seems black level is calculated every time but shouldn´t this be more robust with hardcoded figures?
All digic V cams? 5DIII as well. Below is fixing eosm.
#ifdef CONFIG_EOSM
{
raw_info.black_level = 2048;
}
#else
{
raw_info.black_level = black_mean;
}
#endif
EDIT:
Or maybe simply:
/* black level looks alright, go ahead and use it */
/* log significant changes to console */
if (ABS(black_mean - raw_info.black_level) >= 10)
{
printf("Black level: %d\n", black_mean);
}
raw_info.black_level = black_mean;
//Correct black level for digic V cameras
if (black_mean == 2047)
{
raw_info.black_level = 2048;
}
EDIT2:
These changes will fix correcting black level but also letting us use auto focus while using small_hacks and more hacks.
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/30c34d6d66232a328f578900d7ed768cd4366324
That's a nice tip!
Fixing black level to 2048 makes a big difference in the shadows at 10-12bits.
At 10 bits, the red tint in the noise is reduced significantly. (This can be tested by pushing the shadow recovery to 100 in MLV App). Thanks!
Not wanting to crash into bilals thread here so I probably start another post soon if I keep this going.
Firstly. This build of his is a beast. It is stable, it is real time, it is like dream come true. Nevertheless. I miss a few things so would like to adress possible refinements and I will also keep a modified build here:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
First off. I really want to be able and use some sort of Focus aid while recording. This was achieved also by Bilal in former builds. Using magic zoom just isn´t working for me. I created some focus aid by using halfshutter. It isn´t perfect but it gets you closer to the subject.
(https://i.postimg.cc/ZRxLcT5N/VRAM0-PPM-300px.jpg)
I added fix for black level 2048. BAck to 2047 after some deeper testing.
Some tap display functionality. Tapping display opens up ml menu.
Oh, and auto focus is still ruinning with all hacks on. awsuspend is disabled when af is used but the other hacks are being used.
Happy new year!
Being able to focus while filming is the most important feature here to me :).
Quote from: Danne on December 31, 2023, 11:27:04 PM
Being able to focus while filming is the most important feature here to me :).
It is for a lot of folks I guess .. going to check it out later, but wanted to say thank you and a happy new year!!
Thanks. Yeah, I guess it's about problematic with the small screen :P.
Let me know if it works and also if my stuff is interfering with general recording times. I just recently started to film with this cam again so not really used to Bilal's build yet.
@Gabriielangel provided a 10bit testfile which demonstrates the problem with black level 2047 here. Exposure pushed for checking shadows.
2047
(https://i.postimg.cc/wM2bN0Lh/Screenshot-2024-01-01-at-15-30-03.png)
2048
(https://i.postimg.cc/gcH71kQn/Screenshot-2024-01-01-at-15-29-52.png)
EDIT:
After som more tests it seems 2047 is the correct value. Deepest black are not correct with 2048.
Posted another build. Better Focus aid, closer to subject. Still needs better centering but works pretty well while filming with 1x3 and 1x1 presets.
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/752c78080de8505f2943deb9dd9f7d2ca83dfc26
These registries zooms much like x10 zoom while filming.
EngDrvOutLV(0xc0f11B8C, 0x0);
EngDrvOutLV(0xc0f11BCC, 0x0);
EngDrvOutLV(0xc0f11BC8, 0x0);
EngDrvOutLV(0xc0f11A88, 0x1);
Download:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
Quote from: Danne on January 01, 2024, 11:28:30 PM
Posted another build. Better Focus aid, closer to subject. Still needs better centering but works pretty well while filming with 1x3 and 1x1 presets.
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/752c78080de8505f2943deb9dd9f7d2ca83dfc26
These registries zooms much like x10 zoom while filming.
EngDrvOutLV(0xc0f11B8C, 0x0);
EngDrvOutLV(0xc0f11BCC, 0x0);
EngDrvOutLV(0xc0f11BC8, 0x0);
EngDrvOutLV(0xc0f11A88, 0x1);
Download:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
Firstly a huge thank you once again to Danne and Bilal for all your extraordinary work!
Secondly a very safe, productive and prosperous 2024 to all the ML community.
All the best for the year ahead.
RE
what is the different between crop_mood.2023Aug19 and crop_mood.2023May09?
sometimes my camera won't turn on when use crop_mood.2023Aug19 build
Quote from: ML700D on January 02, 2024, 08:24:45 AM
what is the different between crop_mood.2023Aug19 and crop_mood.2023May09?
Some answers here: https://www.magiclantern.fm/forum/index.php?topic=26851.msg244733#msg244733
p.s. It would be nice to group all the releases under a single post near the top of the thread. Once the thread becomes as large as Danne's, it will be very tedious to refresh our memories!
Quote from: gabriielangel on January 02, 2024, 06:43:05 PM
Some answers here: https://www.magiclantern.fm/forum/index.php?topic=26851.msg244733#msg244733
p.s. It would be nice to group all the releases under a single post near the top of the thread. Once the thread becomes as large as Danne's, it will be very tedious to refresh our memories!
thanks a lot..
Quote from: Danne on January 01, 2024, 11:28:30 PM
Posted another build. Better Focus aid, closer to subject. Still needs better centering but works pretty well while filming with 1x3 and 1x1 presets.
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/752c78080de8505f2943deb9dd9f7d2ca83dfc26
Download:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
I tested magiclantern-crop_mood_Danne.2024Jan01.EOSM202.zip and magiclantern-crop_mood_Danne.2024Dec31.EOSM202.zip
Both builds tested with small hacks set to More, and kill global draw set to On
BrightenLVmethod set to AeWb, because it didn't change AF accuracy when set to EVF.
Resolutions at 2.39:1 ratios and 23.976 fps.
Dec31:
When assigned to half-shutter, Focus Aid works while Idle and While recording;
Focus aid needs (as you already pointed out) better centering as it is too far off center to check if AF was accurate. Even if using MF, the aim difference is significant enough to make a difference at wide apertures;
Got 1 clip out of 10 with a corrupted first frame.
Jan01:
When assigned to half-shutter, Focus Aid doesn't work while Idle (maybe that was intentional). While recording, it is distorted (stretched) at 1:1 crop modes, and showing as expected at 1x3 modes;
Focus aid needs centering;
No corrupted clips.
Both builds:
You need 12 bits minimum for AF to work correctly. I read that Bilal adressed the issue, but I don't know if the fixes were included in his last posted build, or if it only works when small hacks are off.
2.5K:
AF works
very well, rarely misses (even at f1.4) and doesn't affect recording times, even at 14 bits.
2.8K and 1x3 modes:
AF makes the recording status turn orange or red while the half shutter is pressed. If you hold it for too long, recording stops;
ef-m lenses are quick enough (tried ef-m 32 and ef-m 28mm), but I also tried an ef-s 15-85mm and AF lock often took long enough to halt recording;
You need an unobstructed line of sight to get accurate AF. It misses often, especially when several objects are close to one another or if some objects are close to the camera, while the background is far away. Works better at smaller apertures. None of those issues at 2.5K.
One has to be careful not to push the shutter button too far. If done while recording, the camera hangs on a "Busy" message and needs to be restarted (Battery Pull).
The scene needs to be properly exposed for AF to work well. So, resolution / bitrate combos where you need to underexpose should be avoided.
Also happens in Bilal's original build:
When in 2.8k, the aspect ratio in Crop mood always shows 2.35:1 (and always shows 2.33:1 when in 2.5k), regardless of the setting there, or in RAW video menu. One has to check the resolution displayed next to RAW video to make sure.
I also noticed that the Screenshot feature doesn't work anymore.
Changed 1x1 Focus aid so it looks a little better.
Centering not an easy task. Bilal knows how to wiggle his preview regs, I don´t really know how to combine the full set of regs.
Quote
Also happens in Bilal's original build:
When in 2.8k, the aspect ratio in Crop mood always shows 2.35:1 (and always shows 2.33:1 when in 2.5k), regardless of the setting there, or in RAW video menu. One has to check the resolution displayed next to RAW video to make sure.
Think this is expected. Hardcoded presets.
Quote from: gabriielangel on January 04, 2024, 12:45:57 AM
One has to be careful not to push the shutter button too far. If done while recording, the camera hangs on a "Busy" message and needs to be restarted (Battery Pull).
It's a pity this broke in crop_mood... previously it just captured a still. Would be great to be able to take production stills while shooting. Not a deal breaker but it sure was a handy reference tool that saved us having to dig through CDNG files
Interesting I changed from 64gb card to 128gb and getting more stable recordings. Even magic zoom is working real nice again 😎. Maybe not that bad after all.
Would it be easy to set a 1 or 2 pixels horizontal offset for the 1x3 and 3x3 modes? It would able avoiding dead pixels which would help old cameras. Thanks!
Just installed the crop mood ver 20230809 on Rebel SL1 with firmware updated version 1.01. Aamazing work. Two thumbs up.
I can do continuously recording (green) in 5.2k 1x3 mode, ar 2.67, 10 bit, 14 bit lossless, 24p, sd card overclocking 240 mhz, small hack more, global draw off on, sandisk extreme pro 256 gb. I tested at iso 100, 200, 400, 800, 1600. At ISO 800 and 1600, the recording time is about 30 seconds when global draw off is off, continuous when global draw off on. At ISO 100-400, it is truly continuous even when global draw off is off.
Two issues:
1. when stop the recording, there is error message "audio cannot stop recording".
2. when play back, the screen is black, and I have to take battery off and restart the camera, then I can play back the latest clip, but no other function buttons showing up.
Just wondering.. if it's easy simple for someone..any way to make the preview when using dual iso just normal preview? It's very distracting to shoot with the preview having the ulternating lines on iso. Honestly I'd rather have just some sort of preview be it over or under. Obviously we could have the exposure tools reflect the true exposure of that's possible. Just throwing it out there. Not demanding. Thanks for everything dudes!
Quote from: Teamsleepkid on January 07, 2024, 03:16:05 AM
if it's easy simple for someone..any way to make the preview when using dual iso just normal preview?
Likely possible, will not be easy. The preview is showing the lines, because the sensor is recording the lines. Fixing this in software is too slow. Fixing it in hardware is likely to be difficult.
Quote from: Teamsleepkid on January 07, 2024, 03:16:05 AM
Just wondering.. if it's easy simple for someone..any way to make the preview when using dual iso just normal preview? It's very distracting to shoot with the preview having the ulternating lines on iso. Honestly I'd rather have just some sort of preview be it over or under. Obviously we could have the exposure tools reflect the true exposure of that's possible. Just throwing it out there. Not demanding. Thanks for everything dudes!
you can use histogram for estimating imo.
I did some customization in Crop mood lately which I wanted to share. Tested on eos m. Should work for other supported digic v cameras. These are modifications done for my personal liking. If anyone else likes it, be my guest and use it. New to this build is also being able and use customize buttons in stills mode when shooting CR2 files. Do not turn Crop mood off, simply turn your knob to photo mode and keep movie mode settings on. This way cutom buttons will still apply.
My builds are to be seen as work in progress and in good gpl faith. I really like bilals work here so porting ideas from my older build seems logical to me at least :P.
Download here:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
How to use it. Easy. Install, start to film. All necessary modules are preloaded. Sd overclocking also activated on install. I use my own custom buttons so feel free to change this after installation.
1 - Rearranged some menu items to Movie menu. Custom modes also added
(https://i.postimg.cc/hjyLTvNM/01.jpg)
2 - Tap display with your finger and it goes straight to the preset screen
(https://i.postimg.cc/QCFpbs3D/02.jpg)
3 - All modules needed preinstalled(not showing) Left is a bunch of other modules. Use more if needed.
(https://i.postimg.cc/KcW7YKP8/03.jpg)
4 - Global draw items turned off
(https://i.postimg.cc/MHg1346Q/04.jpg)
5 - My custom buttons
(https://i.postimg.cc/4Nh6HJPb/05.jpg)
6 - Using high framerates I enable som reduced speed to get stability. Turn this off if you want fastest framerates
(https://i.postimg.cc/fRnxx6g4/06.jpg)
7 - Zoom on HalfShutter is turned on. I use it in photo mode with manual lenses
(https://i.postimg.cc/XYf9xQTr/07.jpg)
Photo mode
8 - New in this build is being able and use customize buttons in stills mode. For instance moving iso up and down is now also functioning with still CR2 photos. Aperture control increase and decrease with SET and INFO buttons.
(https://i.postimg.cc/VN4nP5s1/08.jpg%5B/b%5D)
9 - Use tap display to go straight to Expo tab when in photo mode
(https://i.postimg.cc/rpqxH5kQ/09.jpg)
hi danne,
can I install your build in 700d?
It needs compiling for 700D.
Danne you da man!
Ported rest of the buttons to work in stills mode as well as in movie mode:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
Quote from: Danne on January 08, 2024, 01:30:21 PM
It needs compiling for 700D.
how to compile it? thanks.
This is Nice! Having every most used menu under the Movie tab again makes making modifications faster.
Also, giving access to the ISO Expo page (And Others) is good news.
Here's why:
On the Eos m, by default, the Wheel is assigned to Shutter and when you hit Right Button, it is momentarily assigned to Aperture.
Because the U/D and L/R buttons are located under the Wheel, if you reach for it and press too hard while turning, you end up triggering one of the buttons. So for me, putting ISO there is a no no, as I often bumped it up to 200-400 inadvertently and only realized 4-5 clips later. So I had to switch to Photo mode to modify it, which was annoying.
Same thing with the touch screen, it is too easy to touch it when you grab the camera and change something. In this build the Presets keep the modifications you make (Changing the bits to 14 for example), so it's not as bad as your former build where you had to dial in everything again whenever you switched presets.
But still, I'd rather put something inconsequential on the touch screen, like false colors; and then use the INFO and SET buttons, which are a lot harder to trigger by mistake, to put ISO access and x10 zoom (Or Aperture + -, which will be a lot more convenient than the wheel when the cam is on the gimbal).
Therefore, if you eventually added false colors to the touch screen menu, it would be a welcome addition.
Also, if doable (I know it may involve pre-populating the SETTINGS folder, which may be an annoyance) Having all the enabled modules showing with the green light, so that the user can unload those if needed, could help with troubleshooting, when people ask questions on the forums.
I 've been benchmarking my cards for the past few days, so I retested my Sandisk Extreme Pro 128 with your custom.
There is a slight penalty of about 5 MB/s when writing to the card. This can be mitigated by switching to 12 bits. With the fast cards, there is enough headroom for this.
Thanks for checking in.
I want a workflow which excludes the scroll wheel. As you say, it works bad as it needs multiple functions to work. With expo shortcuts we can skip the scrolling fiunally.
Installing this build automates modules and enables the build. Having an option to turn off the "invisible" modules will complicate things and I like to keep this simple. There´s the main crop mood build to do tests with. My version is more my personal preference and built around simplicity and usability.
Added false colors to tap display and fixed a few bugs.
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
Quote from: Danne on January 09, 2024, 10:01:31 AM
Thanks for checking in.
I want a workflow which excludes the scroll wheel. As you say, it works bad as it needs multiple functions to work. With expo shortcuts we can skip the scrolling fiunally.
Installing this build automates modules and enables the build. Having an option to turn off the "invisible" modules will complicate things and I like to keep this simple. There´s the main crop mood build to do tests with. My version is more my personal preference and built around simplicity and usability.
Added false colors to tap display and fixed a few bugs.
Danne's on fire in 2024. This is awesome!
I'd just completed configuring my presets folders when I saw your update from yesterday. Combined with my presets this takes the little EOS M to a whole new level of functional.
Presets folder jpeg
https://drive.google.com/file/d/1Ew3EqcYAQOHQGj9SSY8Em6UznV11I7in/view?usp=share_link
(https://drive.google.com/file/d/1Ew3EqcYAQOHQGj9SSY8Em6UznV11I7in/view?usp=share_link)
Crop mood with the best of the polished Danne's builds, cannot get any better :D
So happy to have the Dual ISO shortcuts again, and the seamless photo switch is an awesome bonus. Thanks a lot Danne!!! <3
Thanks guys. I really am building my own personal version here and happy to share it with you.
@gabriielangel
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
Regarding speed penalty losing 5mb. I posted a new version. In this version if camera is set to manual focus and U/D Arrows is turned OFF or set to Aperture and if small hacks is set to More this should enable all hacks on the eos m and maximize sd card speed.
If cam is set to af or U/D Arrows set to ISO it will automatically turn off aewbSuspend(); which when enabled will ruin af and iso changes while filming.
Anyway. Thanks for noticing before.
Thanks. As long as we know what's going on, it's easy to make a decision / compromise based on our needs (Pre-Focus at x10 Zoom on my end).
The Half-Shutter AF while filming works best at 2.5K and 1080p, and these modes can do without the 5 MB/s on a good card :)
I added a new preset to th 1x3 family:
(https://i.postimg.cc/66ZW51vb/VRAM0-PPM-300px.jpg)
Full res LV and will film in 12 fps. Full sensor. Really nice. Preview should be set to framing. I talked to bilal and he might try and make a real time preview possible. Preview kind of works with 2:35.1 but shows only part of the image but this indicates bilal should probably be able and fix this. I cross my fingers ;).
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/
Commit:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/ec57380e8ef222843c36adfc9aa00e66bf21f715
Essential parts:
if (Anam_FLV)
{
cmos_new[5] = 0x20 + CMOS_5_Debug;
cmos_new[7] = 0xC00 + CMOS_7_Debug;
}
if (Anam_FLV)
{
RAW_H = 0x1D4; // from mv1080 mode
RAW_V = 0xDB0;
TimerB = 0x1407;
TimerA = 0x207;
//From AR_2_35_1
Preview_H = 1728; // from mv1080 mode
Preview_V = 2214;
Preview_R = 0x1D000E; // from mv1080 mode
YUV_HD_S_H = 0x10501B5;
YUV_HD_S_V = 0x1050341;
}
@Danne
Testing - magiclantern-crop_mood.2024Jan11_Custom.EOSM202
Adding custom mode presets folders removes the ability to capture CR2 in camera mode, works when custom mode presets is set to off and the camera restarted.
Works in various resolutions if CM is set to off and camera restarted.
Will sticky half shutter toggle be able to be fixed in Crop Mood? Would be nice to be able to have x10 Zoom stick on half shutter and the ability to toggle on and off, it currently freezes LV when activated. I know this is an old issue but thought it worth revisiting.
Otherwise working like a dream so far. Even on older slower cards.
Hi!
Noticed CM modes weren´t working a few builds so fixed now. Uploaded a new build again.
About your issue taking CR2 stills. I could not reproduce this. Maybe it was related to the bug I just fixed? Could you retest this again?
Tested sticky halfshutter. Once halfshutter pushed you cannot disable the halfshutter push. Is that the issue? What are you using this function for by the way?
Thanks Danne.
I just came back to post an update to my previous post to say I retested the new build on a different SD card and it solved the issues I was having with CR2.
All seems to be working fine now
Good to know.
Regarding sticky halfshutter. Curious what could be done here. If you are using it to keep x10 zoom with halfshutter it should be easier to create a function for this in crop rec code than using the external stick halfshutter.
I was using SET for x10 Zoom but now using for Aperture + so was hoping for an alternative for x10 Zoom that toggles on/off
I see. I will take look when I get some more time.
Meanwhile. Increased fps to the 1x3 fullres LV preset.
14bit(12fps)
12bit(14fps)
11bit(14fps)
10bit(16fps, silent movie fps) Turn off ISO buttons up/down for best performance. Small hacks set to More.
With realtime preview this will probably be more solid than now.
Push MENU button a few times when changing fps or it will not be taken into effect.
FIXED. No need to enter MENU and back.
Quote from: RhythmicEye on January 11, 2024, 11:59:42 AM
I was using SET for x10 Zoom but now using for Aperture + so was hoping for an alternative for x10 Zoom that toggles on/off
If you set your camera to Manual Focus (MF), in the canon menu, or on the lens if you are using an ef-s lens on an adapter.
You can go to the customize buttons menu and set it as:
Half-Shutter: Zoom x10
SET Button: Aperture +
INFO Button: Aperture -
Then, pressing the shutter halfway (Be careful not to push it too far!) will toggle x10 Zoom on off.
If you press it all the way in, it may take a photo, but sometimes it freezes the camera. So you need to pull the battery and restart it.
EDIT: I remember what I did to stop that annoyance:
Go to the Canon Menu
In the 5th tab
Set Video snapshot to: ENABLE
From now on, when in Video mode, the full Shutter Button won't work at all.
And it will work as usual in Photo Mode.
No Video Snapshot seems to be recorded on the card.
I haven't tested if it affects performance though. Let me know.
If your camera (Or ef-s lens) is set to AF
You can go to the customize buttons menu and set it as:
INFO Button: Zoom x10 (Preferred)
or
SET Button: Zoom x10 (If you do this, you won't be able to recenter the focus box automatically if you move it. You will have to use the arrows on screen to put it back in the center)
Then you use the wheel to change the Aperture.
If you use the wheel directly, it will change the shutter speed.
If you push right button, then turn the wheel, you will be able to adjust Aperture + -
Using the Tap screen fo x10Zoom would not work, as you wouldn't be able to turn it off once you're in, because of the Nav arrows on screen;
Using the U/D buttons seems to have a performance cost (I don't know if it's the buttons themselves, or what's currently assigned to them);
L/R buttons cannot be assigned in eos m ATM (From what I have read so far).
Up down buttons are only problematic with More hacks and ISO. Iso stops changing because of the hack. Therefore I disable the hack when ISO is enabled to up/down buttons. Other shortcuts are not affected.
Quote from: Danne on January 10, 2024, 09:51:37 PM
I talked to bilal and he might try and make a real time preview possible. Preview kind of works with 2:35.1 but shows only part of the image but this indicates bilal should probably be able and fix this. I cross my fingers ;).
Previewing 1736x3478 in LiveView works :D
(Code was sent, check it out!)
Damn! The preview wizard from Syria has done it again 8) :o. I will fix this later tonight. Many thanks!
New build uploaded in first post 8)
1736x3478 (Full res LV) 1x3 preset. Upscaled 5208x3478 that is!
With 10bit you get 16 fps. With a little imagination this is like shooting CR2 bursts but continuous packed in MLV format :P.
12bit runs at 14fps and 14 bit at 12 fps.
All thanks to the preview wizard theBilalFakhouri. Big thank you!
The preset is stashed in here:
https://www.magiclantern.fm/forum/index.php?topic=27084.msg245758#msg245758
Bilal + Danne is one hell of a team! Thanks, guys!
Great job guys!
Can't wait to have the time and test it.
New build:
- Sticky zoom added to halfshutter button
- Various fixes
(https://i.postimg.cc/tJXHRYpG/VRAM0-PPM-500px.jpg)
Danne!!! This is awesome man, thank you.
Yet another level up on functionality. Great job and thanks again.
RE
Quote from: gabriielangel on January 11, 2024, 05:19:28 PM
If you set your camera to Manual Focus (MF), in the canon menu, or on the lens if you are using an ef-s lens on an adapter.
You can go to the customize buttons menu and set it as:
Half-Shutter: Zoom x10
SET Button: Aperture +
INFO Button: Aperture -
@gabrielangel
Thanks for the suggestion man but you've probably already seen Danne has added a sticky half shutter fix to the code. Woohoo!
Allows for the best of all button presets.
Hard to believe the EOS M just keeps getting better in 2024.
RE
Nice.
Refined Focus aid some in last build. A compromise but better than centre way off like before.
New upload:
- Reworked Movie tab menu, added access to all important stuff
- Fixed screenshot bug
- Added fixed intervalometer and rec delay lua scrip(autoenabled, bottom in movie tab), fixed a console bug
Hi .
I tried focus aid at 3x3 HFR , so i switch lens to AF (sigma 30 f1.4 art for ef-s mount) => Liveview get freeze, switch back to MF , live view work normaly.
Can we fix this, please. Happen at 3x3 only.
With the last build I've noticed that the screen gets darker when pressing record and less than 14bit is selected, and darker with 10bit than with 12bit.
Anyone else noticed?
https://vimeo.com/903613854
I don't change to selected bitdepth until we hit record now. It stays 14bit before this. That is why 8).
Quote from: Danne on January 17, 2024, 11:36:32 AM
I don't change to selected bitdepth until we hit record now. It stays 14bit before this. That is why 8).
But why is it darker? Shouldn't the brightness stay the same regardless of the bit depth?
Quote from: Danne on January 16, 2024, 01:43:09 AM
New upload:
- Reworked Movie tab menu, added access to all important stuff
- Fixed screenshot bug
- Added fixed intervalometer and rec delay lua scrip(autoenabled, bottom in movie tab), fixed a console bug
Sharing my extended Config Presets folder for -
Crop Mood Danne custom tweaks 16th Jan 2024Make sure to read the Presets_READ_ME before installation and follow the specific instructions
Please feel free to share link https://drive.google.com/file/d/1OWKJGSERLr9bbWm9wjSy6AiPJSLju2ux/view?usp=sharing
NOTE: all resolutions are intentionally set to 23.976 @ 1/48 shutter
Enjoy!
Quote from: iaburn on January 17, 2024, 11:44:28 AM
But why is it darker? Shouldn't the brightness stay the same regardless of the bit depth?
Strange. Will fix it. Is it only happening with that preset?
Using latest build?
EDIT: Tested your preset but couldn´t reproduce your issue.
Quote from: Danne on January 17, 2024, 02:16:40 PM
Strange. Will fix it. Is it only happening with that preset?
Using latest build?
EDIT: Tested your preset but couldn´t reproduce your issue.
It seems to happen when I customize the buttons like this:
Half shutter : Focus aid
Set button: zoom 10x
Info button: dual iso
Tap: false color
U/D arrow: aperture
L/R arrows: off
Edit: its the U/D arrow: aperture
Thanks! Fixed. I commented out awbsuspend hack. It´s causing these liveview freezes and disturbs too much.
I also Reworked 2.8k to 2.39:1 instead of 2.35:1. Also added 2.39:1 in HFR section.
Quote from: Danne on January 17, 2024, 05:19:30 PM
Thanks! Fixed. I commented out awbsuspend hack. It´s causing these liveview freezes and disturbs too much.
I also Reworked 2.8k to 2.39:1 instead of 2.35:1. Also added 2.39:1 in HFR section.
Sounds good, thanks!
What is the impact of commenting out the awbsuspend hack? Does it mean that some performance is lost?
Yes, around 4mb.
I know many people value reliability more, but I personally prefer a bit more of performance and deal with the compromises. It doesn't sounds like a lot, but in Magic Lantern 4MB can be the difference between orange continuous recording and red stopped recording :-\
Could add it back but It will be disabled when affected functions are enabled so better remember it ;).
New build:
When up/down or SET or INFO buttons are assigned to ISO or Aperture More hacks is bypassed. If up/down button is disabled and other functions to SET and INFO are assigned than ISO and Aperture More hacks is active.
Quote from: Danne on January 18, 2024, 08:42:11 AM
New build:
When up/down or SET or INFO buttons are assigned to ISO or Aperture More hacks is bypassed. If up/down button is disabled and other functions to SET and INFO are assigned than ISO and Aperture More hacks is active.
I think it's a good solution :)
Am I right thinking that the problem is allowing to modify ISO and aperture while recording? Because another option could be to allow the shortcuts for ISO and aperture to work only when not recording.
Yes, liveview altering function is completely frozen regarding iso and aperture with the hack enabled no matter what buttons are used ;). WHy you noticed the brightness shift was due to a race condition because I know use 14bit until we start to record. Using engdrvout overrides regardless if the hack is on or not so this is used now with More hacks.
//Workaround when small_hacks is set to More in mlv_lite.c
if (!Arrows_U_D && INFO_button != 2 && INFO_button != 3 && SET_button != 2 && SET_button != 3)
{
if (OUTPUT_12BIT)
{
EngDrvOutLV(0xC0F42744, 0x2020202);
}
if (OUTPUT_11BIT)
{
EngDrvOutLV(0xC0F42744, 0x3030303);
}
if (OUTPUT_10BIT)
{
EngDrvOutLV(0xC0F42744, 0x4040404);
}
}
Hi Danne, do you know if this build would work on an EOS M2?
It works great on my M, but I have found an interesting offer for a top mint M2, and I was considering getting it...
Many thanks for your excellent work!!
I have no problems with not being able to change ISO or aperture while recording, so I didn't assign buttons for that.
I did a quick test with my main sd card and 5.2K at 1:2.35 and 12bit is red with ISO shortcut but orange without the shortcut, so I'm happy with the extra MB/s :D
Quote from: Promet73 on January 18, 2024, 12:25:52 PM
Hi Danne, do you know if this build would work on an EOS M2?
It works great on my M, but I have found an interesting offer for a top mint M2, and I was considering getting it...
EOS M2 is not well supported. So basically: You don't want to buy it if you want to do high res raw recordings.
Quote from: Danne on January 18, 2024, 08:42:11 AM
New build:
When up/down or SET or INFO buttons are assigned to ISO or Aperture More hacks is bypassed. If up/down button is disabled and other functions to SET and INFO are assigned than ISO and Aperture More hacks is active.
I also think this is a sound compromise. Those recording with higher resolution presets will be able to get longer recording times.
Making preview 14bit allows for more precise exposure monitoring, as false colors and Histogram are more representative. Those were always slightly off when recording below 14 bits before, so you had a greater chance of clipping footage. The pink clouds you see in iaburn's example are the result of the highlights being clipped. It's not always possible to get rid of those after.
Quote from: gabriielangel on January 18, 2024, 03:51:27 PM
Making preview 14bit allows for more precise exposure monitoring, as false colors and Histogram are more representative. Those were always slightly off when recording below 14 bits before, so you had a greater chance of clipping footage. The pink clouds you see in iaburn's example are the result of the highlights being clipped. It's not always possible to get rid of those after.
Interesting, I didn't know that.
I've been experimenting with a variable ND filter and using the RED, AMBER, GREEN recording icon as a kind of exposure metre. I ride the exposure with ND filter based on the icon. Similar to focus pulling, it's not perfect but it gives quite a good result. Definitely takes some practice though
Is what we see on screen during recording under 14 bit not a representation of what is recorded to SD card? Including the new build...
New build:
Added a 1080p regular preset which allows to use ratios also with 1080p mode. Caveat. Preview slightly laggy until pressing rec.
Regarding 14bit preview @RhythmicEye. Preview screen is 14bit and only when recording it will change to other selected bit depths. If selected. 14bit will always be 14bit.
OK got it!
Now that I've had a chance to do a bit more testing, I'm starting to understand where and why you've made the compromises/choices you have. Been swapping SD cards between Danne's Jan 19 2024 build and Bilal's Aug 19 2023 build to see the performance and functionality differences.
I really like the compromises you've made to give us something with the best of both builds and a bit more ML magic sprinkled on top.
Once again kudos and thank you Danne and Bilal!
It´s all polishing now :).
New upload:
- Support of cropmarks and enabling aspect ratios from crop rec instead of in RAW video when in 1080p:
(https://i.postimg.cc/MZ4vBtyr/VRAM1-PPM-300px.jpg)
Preview works normally in this one.
EDIT: Added a fix for resetting offsets.
Hey, Danne, i want to thank you and all the people that have made Magic Lantern happen! From my perspective it is amazing!
I was wondering is it possible in the future for this camera to shoot 3:2 video in some other mode rather than 3x3. I really like the modes that doesn't have aliasing and moire. Thank you 🙏
Danne I've noticed that on 2.8K your build records at 2880x1206, but the original crop mood was 2880x1226. Is that intentional?
I don't mind the 20 pixels, but there is currently no focus pixel map for MLVApp. Just wondering if you changed it to 1:2.39 instead of 1:2.35 for stability, or it was a mistake
Yes, changed. 2.35:1 is an older format. Want coherency.
Right now 16:9 and 2.39:1 will work for 1x1, 1x3 and 3x3. Also added offset crop marks for 3x3 in crop rec so even easier now to dial in preset.
I think mascwill add maps here but not sure when.
Also corrected a few red pixeled bottom lines lately.
(https://i.ibb.co/v1ZdRv0/FocusPix.png) (https://imgbb.com/)
Those are the focus maps I have in my app, and I can see it getting rid of the focus pixels on files I recorded Last Week at 2880x1206.
This was before @danne added the 2.39:1 preset, so I changed the ratio from the Raw Video submenu when recording. Don't know if that makes a difference.
Edit:It does make a difference.
Those are the rez where my focus pix don't work here:
1736x2178
1736x2322
1504x2538
1736x3478
2880x1206
Played with the new presets (so many, probably not all):
1736x2178 -> no problem
1736x2322 -> how to get that? I just get 1664x2268, which should be same AR. This one has a red line at the bottom.
1504x2538 -> new map uploaded
1736x3478 -> no problem
2880x1206 -> new map uploaded
1736x738: works fine
1736x726: works fine
Edit: 1736x2322 has 2.24:1 AR. Can't reproduce that. Is there a typo?
Quote from: masc on January 21, 2024, 10:31:44 AM
Played with the new presets (so many, probably not all):
Edit: 1736x2322 has 2.24:1 AR. Can't reproduce that. Is there a typo?
Sorry @masc, yes typo. It is 1376x2322
I re-checked:
1736x2178 , it doesn't work
1736x3478, it doesn't work
1736x738: works fine here also
1736x726: works fine here also
I recorded everything with the Jan 19 build, and I think Danne uploaded 2 versions on Jan 20.
As 1736x2178 works when I use bilal's original version, maybe check to make sure there won't be any interference?
My computer isn't internet connected (MLV App cannot auto-download), would you mind giving me the repo's address?
(https://i.ibb.co/NyNKvYG/Resolutions-Tested.png) (https://ibb.co/z42ZMft)
Ah okay.
Use these maps:
1376x2322 - 80000331_1448x2351.fpm
1736x2178 - 80000331_1808x2207.fpm
1736x3478 - 80000331_1808x3507.fpm
1736x2214 - 80000331_1808x2243.fpm
Note: some of Bilals original presets had a red line on the bottom. Danne fixed this for many modes. For each fix another map is needed now, even if you don't notice a change in resolution. If you can use (compile or download (with github account)) the latest commit version of MLVApp, the focus pixel map dialog shows which map is needed, if you did not install it.
Fixed red bottom just now on:
Medium 1x3 2:1 1360x2040
Medium 1x3 2:20.1 1424x1942
Medium 1x3 2:35.1 1472x1878
Medium 1x3 2:39.1 1472x1846
Higher 1x3 2:35.1 1600x2040
Higher 1x3 2:39.1 1600x2008
Highest 1x3 2:20.1 1664x2268
I have no time checking through these changes. If anyone could check these for bottom borders it would be nice. Would need new maps, sorry :P
Just checked myself. Seems fixed 8)
Thanks! I think I'll wait until we have focus pixels maps, I'm not using those modes very often :D
Maybe you could help creating them? It is simple. You check the old presets and what maps are being used on every old preset I changed and then simply alter height number by minus one 8).
Is it really that easy? I'll take a look :D
Yeah, and one can check width and height with mlv_dump -v drag/mlv/file/here and check exactly what is going on.
Quote from: iaburn on January 22, 2024, 03:23:12 PM
Is it really that easy? I'll take a look :D
Sorry. +1.
Quote from: Danne on January 22, 2024, 03:27:17 PM
Yeah, and one can check width and height with mlv_dump -v drag/mlv/file/here and check exactly what is going on.
You can also check with MLVApp:
(https://i.ibb.co/FbbBtM1/Bildschirmfoto-2024-01-22-um-20-21-16.png)
I'm missing something because I've modified the second column with +1, using the correct name so it's green on MLVApp(thanks masc), but still not working. For example this file for the new Medium 1x3 2:1 1360x2040:
https://filetransfer.io/data-package/h0ycmUY8#link (https://filetransfer.io/data-package/h0ycmUY8#link)
What is wrong with that file? I took the 80000331_1432x2068.fpm to make the 80000331_1432x2069.fpm by adding 1 to the second column. Is not that what has to be done? ::)
A couple of general MLV App questions.
Do Profile Presets and "Allow Creative Adjustments" make any changes to the RAW data file when exporting to any of the CDNG formats in MLV App?
When "Allow Creative Adjustments" is deselected are we looking at a clean RAW image (+RAW Corrections) or is something else happening to the image we see in MLV App video window?
I just want to understand if I'm bringing clean RAW data into DaVinci Resolve and that what I'm seeing in MLV App closely matches what I'm seeing in DVR.
@RhythmicEye: completely offtopic here - there is a MLVApp thread. But no, RAW stays RAW, no matter what processing you choose in MLVApp. RAW corrections can be exported into RAW.
@masc Completely offtopic!? You guys were talking about MLV App otherwise I wouldn't have asked the question. Anyway thanks for your answer :)
The thread us about a custom EOSM build. And the corresponding pixel maps.
Quote from: Danne on January 21, 2024, 05:30:30 PM
Medium 1x3 2:1 1360x2040
Medium 1x3 2:20.1 1424x1942
Medium 1x3 2:35.1 1472x1878
Medium 1x3 2:39.1 1472x1846
Higher 1x3 2:35.1 1600x2040
Higher 1x3 2:39.1 1600x2008
Highest 1x3 2:20.1 1664x2268
Here those settings look good. I uploaded a pixelmap for each of these settings.
However I also found a problem, probably not related to the new stuff, but who knows:
Settings 1x1 FullRes. After selecting I get for less than a second the liveview I expected. Then it zooms in and has a horizontal line in the middle of the frame. When I try to record, it stops immediately. The MLV is 26.9MB but corrupted. Happens the same for you?
1x1 fullres is a no go here. I never touched this preset or trying to fix it. Instead I focused in 1x3 fullres which works perfectly well as a substitute.
New build:
- Fixed 1x1 Full res LV preset.
Reduced to 2 FPS, seems to work now. Disable sound recording when recording in this mode. Preview is not too funny.
I can do 3k crop res and its more stable thats pretty neat.
Anyone knows how to do 1440p but square 4/3 ratio ? Or possibly even higher like 1600p square ratio like 4/3 ? I wanted to test the limits
is 1440 tallest in crop modes ?
No, you can use Full-Res LV 1x1. It's tallest.
Yes but no 24fps, i haev 2fps in fullsensor mode
Is there a specific address in 1440mode where i can up the height of the image ?
i have orange on 2500x1440 so i think in 1600x1600 il get green and i want 4/3 for 16mm look emulation, maybe even 1800x1800 would be recordable on this card
Don't think it is possible. Either use a ratio in RAW video to get 4:3 or use the 1x1 1920x1280p.
Cool Build! But is it just me or the Photo/Stills function does not work? (camera locks up and battery needs to be removed) I also tried turning it on by holding the SET button but still the same behavior.
Possible 8).
New build:
- Added 1620p (2160x1620 1x1 4:3)
After some feedback from @2blackbar it seems we get a new preset into the mix. It´s a decent 4:3 1x1. Nicely centered realtime preview. Almost full preview. Use framing if needed.
(https://i.postimg.cc/DwBbdjBd/VRAM0-PPM-300px.jpg)
This new mode is amazing, thank you!!!! (thank you 2blackbar for not being shy to ask xDD) Almost perfectly centered and it seems to have the full width in real time preview :D
It fits like a glove c-mount lenses, one of my favorite modes from now on :o
(https://i.ibb.co/8cWJJ53/IMG-0502.jpg) (https://ibb.co/8cWJJ53)
Cool!
Yeah this preset is a nice addon for c-mount lenses.
From what side vignette shows up ? I think from the bottom a bit evenly from left and right but only on really low light scenarios where i shouldnt even film.
And its a bit hard to predict all c mount lenses, some vignette earlier and arent super centered
I just like one of my c-mount lenses, the 25mm 1.4 from the picture before. It's perfectly centered with vignette visible on non-crop, but totally gone on 1x1 modes.
The new 1x1 4:3 mode has 0 vignette even wide open
Would be nice to see example of footage with these c-mount lenses.
We'll need a new map here too.
Pixel map added for 2160x1620 preset.
Quote from: Danne on January 30, 2024, 01:32:19 PM
Pixel map added for 2160x1620 preset.
<3 I'll post some samples when I find something nice to shoot :D
Danne, MLVApp is looking for 80000331_2232x1648.fpm instead of 80000331_2232x1649.fpm, if you want to change it, but works perfectly fine :D
Cool thing is that 14bits are possible in this mode with fast SD cards:
(https://i.ibb.co/qs3Xz7c/datarate.png) (https://ibb.co/0MR8km6)
A quick night test while taking out the rubbish on this 4:3 mode with the c-mount 25mm f1.4 wide open, showing light flares.
The lens is sharp from corner to corner, but it has this "spherical focus" shape, so the center and the edges are never in focus at the same time.
Same video with a more vintage look that fit the lens and the format better:
Yea, very nice 👌😍😍
Interesting indeed.
About the pixel map. Could you recheck against latest build in first post? I think I added 1 pixel height to get rid of pixelation at the bottom.
Quote from: Danne on January 31, 2024, 08:02:04 AM
Interesting indeed.
About the pixel map. Could you recheck against latest build in first post? I think I added 1 pixel height to get rid of pixelation at the bottom.
I was indeed on an older version, cannot keep up with so many updates! :D
A curiosity about this new mode: 16mm film format size is 10.26x7.49mm, and the 2160x1620 pixels are spread approximately on a 9.3x6.98mm area of the sensor, so quite close.
For reference, the original BMPCC sensor size is 12.48x7.02mm, almost the same height but wider, to imitate super 16 format
I had a nice setup today, so I took the opportunity to test the latest build while things were still in place: magiclantern-crop_mood.2024Jan29_Custom.EOSM202
The image quality is better than before.
I have tested all the resolutions below:
(https://i.ibb.co/TcC4nfb/Danne-Jan29-Test-1.png) (https://ibb.co/TcC4nfb) (https://i.ibb.co/wrrpSnB/Danne-Jan29-Test-2.png) (https://ibb.co/wrrpSnB)
And I haven't found a single one of these (bad scan lines):
(https://i.ibb.co/Ch16S3R/BadScan.png) (https://ibb.co/MM2fJxF)
Which would appear every now and then in the previous builds. This is quite nice.
No corrupted frames either.
The following resolutions still have remnants of scanlines at the bottom, but those do not export to prores:
(https://i.ibb.co/Zx7q7p3/Scanline.png) (https://ibb.co/5Lwbwgd)
1280x2160, 1472x2208, 1600x2400, 3072x1308, 2520x1080, 1920x1280, 1736x1160, HFR: 1736x976, 1736x868, 1736x790, 1736x738.
The 726p 3x3 HFR Preset will show a black preview if the camera is set to AF. It shows ok when set to MF.
The 1:1 full-res LV only shows a portion of the frame, and it's not possible to press the * button to switch to framing.
This preset only worked well on bilal's first release of crop mood, where you would see a cropped preview, but you could press * to see the framing. (the 3k also worked this way back then)
I Like the order of the new Movie menu: Everything you use most often is right there, and 1 push up, goes at the bottom, so you can get to the rest with less scrolling.
The new preset is nice, You can post on TikTok or other Vertical / Square delivery platforms without wasting the side pixels like before.
I have 2 suggestions:
1- It would be nice if the 3k preset got the 2.39:1 treatment. The little extra room would give it more recording time on a bright day.
2- It would also be nice if MLV App could have an option to map clipped pixels to white. Because of the pink highlights, it is very challenging to shoot a scene like I did today, without underexposing a lot (Because of the reflective stainless steel on the watch).
You can enable framing/realtime back. There is a setting for that in RAW video.
Will check the other stuff later 8).
Danne one small thing I've noticed on the new mode is that the "Focus aid" is centered when not recording, but way off centered when recording. Not sure if it's fixable, but would be great if there was a way to have the same focus point when recording than when standby ::)
I can´t get it centered @iaburn.
I added a new build which allows to adjust reg_height in the sub menu. This is how to fix the bottom border pixelation. Usually +1 should work but maybe it is -1, -2 or +2, I am not sure. I simply don´t have time to correct this myself atm. Once correct number is obtained write them down and I can put them into the build.
Quote from: Danne on February 01, 2024, 02:14:33 PM
I can´t get it centered @iaburn.
I thought that, not a big deal anyway :D
A day light example showing the incredibly creamy bokeh and how the bar gets sharp at the edges when the center is out of focus. This lens is super fun to use :)
https://vimeo.com/908661212
Nice! I like this new mode 1620p. Works really well.
Quote from: gabriielangel on February 01, 2024, 04:34:11 AM
The 1:1 full-res LV only shows a portion of the frame, and it's not possible to press the * button to switch to framing.
This preset only worked well on bilal's first release of crop mood, where you would see a cropped preview, but you could press * to see the framing. (the 3k also worked this way back then)
Try enabling "Preview toggle" on the RAW video menu, and also remove any action assigned to the Half-Shutter on "Customize buttons". If you do that, half shutter press and (*) will toggle between real-time and actual framing. Not sure why half shutter affects (*) though, maybe is not possible to assign an action just to (*).
Quote from: iaburn on February 01, 2024, 11:27:45 PM
Try enabling "Preview toggle" on the RAW video menu, and also remove any action assigned to the Half-Shutter on "Customize buttons". If you do that, half shutter press and (*) will toggle between real-time and actual framing. Not sure why half shutter affects (*) though, maybe is not possible to assign an action just to (*).
The * is assigned in the Canon Menu's Custom Functions(C.fn). In C.Fn IV menu 5, some settings transfer Auto-Focus to the * Button.
But Just enabling "Preview Toggle" Did the trick! You can then use the * Button to see the whole frame.
Quote from: gabriielangel on February 02, 2024, 02:35:57 AM
The * is assigned in the Canon Menu's Custom Functions(C.fn). In C.Fn IV menu 5, some settings transfer Auto-Focus to the * Button.
But Just enabling "Preview Toggle" Did the trick! You can then use the * Button to see the whole frame.
I couldn't find a way to remove the autofocus from the half shutter and leave it only on the (*), but it doesn't bother me much because I just realized that enabling "Kill global draw", the black info bars on top and bottom are removed and it's a perfect 4:3 real time preview :)
It would be even better if we could simply hide this info bars, but keeping global draw so the zebras are visible, but I can live with that ;)
It does 👀. Interesting.
Maybe also we should put in a short cut to enabling disabling autofocus?
New build uploaded:
- Fixed following presets, height tuning.
1280x2160, 1472x2208, 1600x2400, 3072x1308, 2520x1080, 1920x1280, 1736x1160, HFR: 1736x976, 1736x868, 1736x790, 1736x738.
- Added new pixel maps to Mlv App
- Reworked 3K 1x1 so that it is now 2.39:1 instead of 2.35:1.
Thanks @gabriielangel
If we find anymore pixelated presets please let me know which ones.
Quote from: Danne on February 02, 2024, 11:29:03 PM
New build uploaded:
- Fixed following presets, height tuning.
1280x2160, 1472x2208, 1600x2400, 3072x1308, 2520x1080, 1920x1280, 1736x1160, HFR: 1736x976, 1736x868, 1736x790, 1736x738.
- Added new pixel maps to Mlv App
- Reworked 3K 1x1 so that it is now 2.39:1 instead of 2.35:1.
Thanks @gabriielangel
If we find anymore pixelated presets please let me know which ones.
Since you asked so nicely 8)
I tested all the presets while I were at it. For some reason GitHub isn't cooperating, so I can't check the focus pixels. But only the following stilll have issues:
1736x976 HFR: Corrupted Frame (But this is the one showing the black preview. I found that HFR 16:9 and 2:1 show ok if you move the focus box Up by 4 units. Other ratios remain black);
1472x2208 Black line at bottom
5208x3478 Black or Red line at bottom, depending on exposure.
1920x1280 Needs Focus Pix
2560x1440 Black line at bottom
3072x1284 Needs Focus Pix
1552x2118 Needs Focus Pix
1600x2400 Needs Focus Pix
I filmed a white card this time to make sure I wouldn't miss anything, but I'll film a real scene on your next release to make sure the image didn't get hurt.
Thanks a lot!
New build:- Heights tuned according to @gabriielangel and also added new pixel maps
All new maps are downloaded over here @gabriielangel so not sure what is going on. Maybe works now?
regarding this:
Quote1736x976 HFR: Corrupted Frame (But this is the one showing the black preview. I found that HFR 16:9 and 2:1 show ok if you move the focus box Up by 4 units. Other ratios remain black);
I guess it is related to auto focus being on. Could you test to restart your camera after selecting HFR presets the first time? A while ago I added focus box automation so that it moves to correct position after restart.
This build is getting super polished, thanks Danne! :D
I was recording on the new format yesterday and got a couple of shoots "broken". One was green, I just deleted it, and another one got corrupted over time, I never saw that before (example below).
Any idea why did that happened?
https://mega.nz/file/owtlWZpa#v8lLceDaJdDigWqS-BHeN8WuQJt-hGFHgwG9MtZBcus (https://mega.nz/file/owtlWZpa#v8lLceDaJdDigWqS-BHeN8WuQJt-hGFHgwG9MtZBcus)
What preset was used? Not on my computer atm.
I fixed an issue in my older build long ago which is not included in Bilal's build. Might be the issue here too.
New build:
Could you test this build @iaburn?
- Adjusting powersavetiming registry probably causing random image tearing. To be tested.
commit
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/2e041f5e51fbcdbd931399b1e31109c1db45ca67
Quote from: Danne on February 04, 2024, 02:07:02 PM
New build:
Could you test this build @iaburn?
- Adjusting powersavetiming registry probably causing random image tearing. To be tested.
commit
https://bitbucket.org/Dannephoto/magiclantern_hg_02/commits/2e041f5e51fbcdbd931399b1e31109c1db45ca67
I just tested again, will post results tomorrow pm as it is still compressing as I am writing this, but the new 1620p preset gives corrupted frames right from the start (I can see it onscreen as it records).
I switched to 2.8k to see, no problem there.
Then back to 1620p and it did it again.
This seems to be recent, as when I recorded last time (Feb 2, Jan 29), it did not happen.
No issues here. Tried restart?
Quote from: Danne on February 04, 2024, 02:07:02 PM
Could you test this build @iaburn?
I tried a few clips and had no issues with the new build, but it will need more testing, as I only had this problem twice ::)
Thanks!
It's an old nasty bug and rarely occurs but I think this will fix it.
Tested magiclantern-crop_mood.2024Feb04_Custom.EOSM202.zip
Tested every resolution, no more black / red bars at the bottom of any preset.
No corrupted frames, except for the new preset. This one is strange, because out of 3 recordings, 2 showed glitches on screen while I were recording, but only 1 file had corrupted frames in it.
And 1736x868 48fps gave a corrupted frame even in manual mode.
The image is free of artifacts.
About the 3k preset:
After recording yesterday and last time with the watch scene, I realized that the 3k preset cannot work at 14 bits. The data rate is way too high,
and you need to underexpose 2 stops (Which is equivalent to switching to 12 bits) for it to work.
See the scene I recorded for the tests below. You can see that it is reasonably exposed and not overly bright. Plenty of shadow areas and it still needs 94 MB/s.
If you look at the screenshot, you'll see that 20, 21 and 22fps brings it within reach for the fastest cards.
So, it would be a good idea to take the same approach you took with the Full-Res 1x3 presets, whereas 14bit uses a lower frame rate.
This would make 14bit usable until faster cards are found.
(https://i.ibb.co/619t949/3k-data-rate.png) (https://ibb.co/LJjgjCj)
Thanks for your findings.
I consider 12bit as standard for all presets.
Corrupted frames in 1620p. Might be overhead histogram or similar. What was enabled? What SD card is used? Run 12bit and don't add global draw items, manual focus. Still corrupted frames?
Thanks for all your tests. Valuable too many.
I forgot to mention that I have "kill global draw" enabled, 12 bit and only zebras
We could play around with variable fps. It is possible to lower fps while recording which gets cpu on track again.
Quote from: Danne on February 05, 2024, 05:11:50 PM
Thanks for your findings.
I consider 12bit as standard for all presets.
Corrupted frames in 1620p. Might be overhead histogram or similar. What was enabled? What SD card is used? Run 12bit and don't add global draw items, manual focus. Still corrupted frames?
Thanks for all your tests. Valuable too many.
Sandisk Extreme Pro 128GB R170W/W90 (Freshly Low-Level formatted)
Kill Global Draw On (So Nothing Was On Screen)
Manual Focus (Feb02, Feb04 and Feb05. The tests I did before that were all on AF)
U/D Buttons Off
INFO Button x10 Zoom
SET Button False Colors
TAP Screen Off
(I always use the same setup)
Today, running the Feb05 Build,
Recording at 12bit, I got a corrupted frame using 1376x2322 (See Image)
Although anything is possible, I have gone through the preset thing at least 6 times since Jan 1, so that's 25+ Presets + the 3x3 Presets, times 6.
9 of those presets have a higher Megapixel Count. So I'd lean more towards a recent change.
I am unable to reproduce it on demand though. So a few more tests are required.
I will record some this evening and let you know.
(https://i.ibb.co/x7S2nj2/Corrupt.png) (https://ibb.co/qrMDHsD)
Hello, I will ask a lot of simple questions, because I have not shot with your builds for a long time. Also I don't speak English and I use a translator, so it's not easy for me to learn new settings. In the new build I can't find how to switch the video mode from automatic to manual. Previously it could be done with the info key.
I don´t understand what you mean. Please do a screen recording of your preferred workflow and use the build that works as described. Without this step I cannot provide any relevant answers.
The Info button is mapped from the start in this build. Go to customize buttons and set it to OFF, that might help
About the Feb05 build additional tests, I tried the following settings at 2160x1620, 10 seconds clips, 5 trials each:
Manual Focus, Kill Global Draw On, 12bit
Manual Focus, Kill Global Draw Off, No Overlays, 12bit
Manual Focus, Kill Global Draw Off, Histogram On Screen, 12bit
Manual Focus, Kill Global Draw On, Histogram On, 12bit
Auto Focus, Kill Global Draw Off, Histogram On Screen, 12bit
Auto Focus, Kill Global Draw Off, Histogram On Screen, 14bit
Auto Focus, Kill Global Draw On, Histogram On, 14bit
Alternating AF/MF, Kill Global Draw On, Histogram On, 14bit for 6 trials
I got 1 corrupted frame on 1 out of 5 trials with Auto Focus, Kill Global Draw Off, Histogram On Screen, 12bit
No corrupted frames in any of the other trials.
Same Sandisk Extreme Pro 128GB R170W/W90 (Freshly Low-Level formatted)
Same button assignments as previously reported.
Files recorded @ 76MB/s (The cand can handle 76.5 in the Green)
I did not change focus, switch presets or used any of the custom buttons.
It's surprising we are not getting more image corruption with that much height in 1x1.
I was playing around with Dual ISO on the newest version and it seems like focus peaking isn't working correctly, mainly just highlighting the horizontal lines in Dual ISO vs in the original crop mood where it works as intended.
I didn't do anything to dual iso. If you could do tests with exact same setup and test the same scene against both builds you'll see if something is different or not.
Thank you for the 1620p mode! Here are some notes from my experiments with a 4:3 mode, which could perhaps be useful:
- from what I see in the framed preview, setting cmos_new[7] to 0xAC8 gives a better vertical centering
- rolling shutter can be reduced (from 89% to 77%) by setting the timer A to 0x279, timer B to 0x838 (yielding FPS 23.977)
- one can squeeze more of the vertical real time preview with the correct aspect ratio by setting:
YUV_HD_S_H = 0x1050220;
YUV_HD_S_V = 0x1050240;
YUV_LV_Buf = 0x1B505A0;
YUV_LV_S_V = 0x10501B2;
YUV_LV_S_H = 0x1E0038; // register 0xC0F11A8C
although the preview appears a little messed up
Cool. I'll have a look at this soon. Seems a nice contribution.
Test build:
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/magiclantern-crop_mood.2024Feb11_Custom.EOSM202.zip
(https://i.postimg.cc/sgnhKwcG/VRAM0-PPM-300px.jpg)
Added @doktorkrek nice fixes for the 1620p preview. As stated preview will have a section to the right which doesn´t do anything. This is TEST1. I we skip YUV_LV_S_H = 0x1E0038; // register 0xC0F11A8C it will fill up the whole screen but have a stretched anamorphic look to it. I lean towards keeping the TEST2 version. Maybe @gabriielangel and @iaburn and others could test and share their opinions?
I Think Test 2 is better also, because we see the whole recorded frame (Some of the bottom was missing in the original preset). Test 1 is too small and could give the impression that something is broken.
In Test 2, there is a distortion at the bottom of the frame in the preview, but the image records cleanly.
I've tried both and agree that making the preview smaller is worse than slightly distorted.
I guess it's not easy, but on TEST 2 the image while recording extends till the top, using the space of the black info bar, but doesn't extend till the bottom. If it could take the entire height, like it does on the current version, the image will be less squished and the preview will take the entire screen with "kill global draw" enabled.
I'm sure this is one of the "easier said than done" things haha :D
In any case, it's already one of the best modes and super useful, it's giving the larger vertical resolution from all non-anamorphic settings :o
Thanks guys. I'll have a look soon.
What about recording times. Would it be an idea to reduce resolution a bit to get more stable 12bit recordings? Maybe have two presets. This one and one with less reolsution?
Quote from: Danne on February 12, 2024, 09:17:49 AM
Would it be an idea to reduce resolution a bit to get more stable 12bit recordings?
On a 512GB extreme pro 200MB/s I get green with 12bits, never got a forced stop even though I always ETTR. Many times I can use 14 bits :)
Note: I have live ISO and aperture not assigned to get the extra MB/s
New build added:
- Preview for 1620p shows more or less full realtime preview. A bit stretched but fully usable imo
- Added a More_hacks switch under Customize buttons. When selected it will always stay enabled if selected in RAW video. When recording user can´t change aperture or iso while filming. Turn it to OFF and the hack will be disabled while recording when using U/D and INFO button as before.
(https://i.postimg.cc/NGXQF7jc/VRAM1-PPM-300px.jpg)
Quote from: Danne on February 12, 2024, 02:52:11 PM
New build added:
- Preview for 1620p shows more or less full realtime preview. A bit stretched but fully usable imo
- Added a More_hacks switch under Customize buttons. When selected it will always stay enabled if selected in RAW video. When recording user can´t change aperture or iso while filming. Turn it to OFF and the hack will be disabled while recording when using U/D and INFO button as before.
Pure gold! Best solution to the "more hacks" dilemma :D
Let's see if all work as intended 8).
Quote from: Danne on January 18, 2024, 08:42:11 AM
New build:
When up/down or SET or INFO buttons are assigned to ISO or Aperture More hacks is bypassed. If up/down button is disabled and other functions to SET and INFO are assigned than ISO and Aperture More hacks is active.
Could you elaborate a bit on the intended effect of adding More_harck Allow? If what's in the quote above is still active, I'm not sure what it targets exactly.
Small hacks "More" is not running when up down and Info button is assigned. That is because we want to be able to modify iso and aperture while recording. With the switch now it will enable More hacks always and iso and aperture won't work when recording but we gain an extra 5mb overhead.
Tested feb 12 build, works well, but I always get a black screen when going from the ML menu to LV. To restore LV need to go into canon menu and back to LV.
Is this happening with all presets? Even if restarting cam?
Quote from: Danne on February 15, 2024, 12:44:35 PM
Is this happening with all presets? Even if restarting cam?
I only use 4.2k 1x3 @23.976 12bit 16:9 1280x2160 2.18x
Yes it happens also restarting the camera.
No big deal, just press the "menu" button twice in and out the canon menu and it works fine.
I´ll keep an eye on it.
Hello, The Histogram is broken at lower bit depths with the latest build magiclantern-crop_mood.2024Feb12_Custom.EOSM202.zip.
To reproduce the issue:
Load any 1:1 Preset (Because Histogram is steadier in this mode)
Set Histogram to RAW-based (RGB) / ETTR hint
Set the preset to 14bit
Aim the camera at something bright and steady (Lamp, LCD Screen)
Take a Histogram reading
Press Record
Take a Histogram Reading again, Everything is ok, the number is identical.
Set the preset to 12bit
Take a Histogram reading
Press Record
Take a Histogram Reading again, The Histogram number is now higher than it should.
The number will go progressively higher than normal as you select lower bit depths.
My guess is that the Histogram takes its reading after the Live View Brightening adjustment. Because you recently made it so everything stays 14bit until we hit record (...) fill in the blanks :)
Although it has always been off by about +-0.2 EV in the past when using 12,11 and 10bit, it was still close enough. Now the difference is such that it will display OVER, so we can't do the translation in our heads.
It was last seen working as before in Crop Mood 2024Jan08 Custom, and 2024Jan12 Custom releases (I don't have the others ATM).
BTW, the changes you've made in the Movie menu really make a positive difference, as everything is "Right There" (As opposed to the Jan08 and Jan12 versions I just tried).
Yeah, my roundtrip probably causes the issue here. Not sure if I can fix that in any near future. Thanks for reporting.
New build
- Fixed a bug around more_hacks "Allowed" function.
love the build, there is one thing i love about this build is sticky zoom feature, how ever i experience a weird behavior, my AE lock button now also sticky zoom
is this a bug? or intentional
video test in photo shooting mode
thank you Danne
AE button is also working as halfshutter button. You can change this button in cnaon menu C.fn section.
sweet thanks man!
Quote from: Danne on February 16, 2024, 03:23:00 AM
New build
- Fixed a bug around more_hacks "Allowed" function.
Thanks, Danne for your efforts to make eosm better. I only saw 2024-2-12 binary build at https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/magiclantern-crop_mood.2024Feb12_Custom.EOSM202.zip. Any update link?
Check commit in repo 8).
A bugfix.
Quote from: Danne on February 16, 2024, 09:47:03 AM
Check commit in repo 8).
A bugfix.
Yep I did see the change in commits, but that requires compilation, right?
Is there any document that explains how to compile your repo in Linux? The Makefile at https://bitbucket.org/Dannephoto/magiclantern_hg_02/src/master/Makefile does not specify about compiling for Canon EOS M. Or does 'make eosm` or `make EOSM` or make `eos-m` work?
Thanks!
Quote from: zenny on February 16, 2024, 12:39:09 PM
Yep I did see the change in commits, but that requires compilation, right?
Is there any document that explains how to compile your repo in Linux? The Makefile at https://bitbucket.org/Dannephoto/magiclantern_hg_02/src/master/Makefile does not specify about compiling for Canon EOS M. Or does 'make eosm` or `make EOSM` or make `eos-m` work?
Thanks!
You don't need to compile, I guess Danne forgot to upload the binaries ::)
build uploaded now :)
I'm wondering about the possibility of having a true preview for 1x1 1920x1080 crop video. Is it theoretically possible? I've never done any ml coding but I am able to compile using other people's repos, and maybe I could fiddle with it if I knew there was a chance.
Crop mood? All presets are real time preview. Or am I under hypnosis :o.
Yes, but I don't see a 1920x1080 one. The closest is 1920x1280 (or maybe I am under hypnosis, or just blind)
Quote from: Frank7D on February 16, 2024, 10:25:03 PM
Yes, but I don't see a 1920x1080 one. The closest is 1920x1280 (or maybe I am under hypnosis, or just blind)
In theory you can use the 1920x1280 and set a mask to hide the extra pixels on top and bottom. You can also try to set the aspect ratio to 16:9 on RAW menu
New build:
- Added 1920x1080p 1x1 preset(although it´s like a 1440p with less resolution)
(https://i.postimg.cc/4dmHZKR5/VRAM0-PPM-300px.jpg)
Wow, thanks! I'll see if I can get it working with my 650D (despite having done zero ml coding before. I am an optimist.)
@Frank7D
Could you test this module on your 650D?
https://bitbucket.org/Dannephoto/magiclantern_hg_02/downloads/crop_rec.mo
Didn´t test, no 650D.
Please report back if working or not.
It works! Thanks so much!
One thing I see is that the preview image fills the whole screen, so I assume it's stretched vertically. This doesn't bother me, as the main thing is accurate framing, but I thought I'd mention it.
New build
- When Histogram and RAW-based is enabled 14bit preview whie in other bits is turned off working as regular 12,11,10bit preview. Fixes the histogram issue mentioned by @gabriielangel
Needs some testing.
@Frank7D, Yes, stretched, but only a little right? Maybe could be done better but I don´t know how.
Quote from: Danne on February 18, 2024, 08:27:56 AM
New build
- When Histogram and RAW-based is enabled 14bit preview whie in other bits is turned off working as regular 12,11,10bit preview. Fixes the histogram issue mentioned by @gabriielangel
Needs some testing.
Will test later, thanks!!
Another 1620p sample, this time with a tiny Cosmicar/Pentax 16mm f1.4 lens (the one on this post (https://www.dpreview.com/forums/thread/3634499#forum-post-53238394))
Really nice footage man. Where to buy this lens and adapter?
Quote from: Danne on February 18, 2024, 10:07:19 AM
Really nice footage man. Where to buy this lens and adapter?
Thanks, I got it on eBay, but you have to be patient because there are really ridiculously high prices. A fair price in my opinion is 50/60€, I wouldn't pay more...
The adapter for c-mount lenses is easier to find and very cheap (look for "c-mount ef-m adapter")
I see. Meanwhile I will play with my bulky sigma 3.5 10-20mm. Quite sharp and well controlled ca.
Quote from: Danne on February 18, 2024, 08:27:56 AM
New build
- When Histogram and RAW-based is enabled 14bit preview whie in other bits is turned off working as regular 12,11,10bit preview. Fixes the histogram issue mentioned by @gabriielangel
Needs some testing.
@Frank7D, Yes, stretched, but only a little right? Maybe could be done better but I don´t know how.
The 1920x1080 preset needs a proper focus pixel map. The one I just downloaded makes my MLVApp freeze.
It records without corruption.
Preview is a little stretched, but as long as we know that it records fine (it does), we can at least see the full, uncropped preview.
It doesn't disturb me, as I use AF before recording, but someone who uses MF could chime in.
Note: Because we cannot skip the MLVApp Step no matter what, it would be wiser to record using the 1440P preset and export to 1920x1080 with MLVApp. This gives sharper images (Oversampling) and the crop isn't as brutal.
The real reason to use the 1920x1080 preset would be to record 14-12bit Uncompressed (Which has been removed in this version).
When recording on a ski slope for example, this would prevent the camera from stopping the recording because of sudden variations in image brightness, which is likely to happen when recording at 14bit lossless.
It would also allow you, for example, to clip the highlights a little to get more exposure for people's faces, as long as you know that if you clip too much, the pink highlights cannot be removed.
The histogram now works as before at all bit depths. I tried with both Kill Global Draw ON and OFF.
So, to make it clearer:
If you enable the Histogram, the Preview's Bit Depth is always the same as the recording Bit Depth selected (If you bump up ISO to 6400 and raise shutter to 1/1000 or more it is easy to verify.)
If Histogram is disabled, The Preview's bit Depth is always 14bit, regardless of the recording Bit Depth selected. The recording Bit Depth selected will kick in as soon as you hit record and will return to 14bit when you stop.
Especially when using 11-10bit, this gives an artifact-and-color-cast-free preview, which makes focus and evaluation a lot more enjoyable.
I will use it during the week and let you know if I find anything else.
The map causing Mlv App to freeze? Works over here 8).
Quote from: Danne on February 19, 2024, 01:23:32 AM
The map causing Mlv App to freeze? Works over here 8).
Yes. If I load a clip recorded at any other resolution, everything is fine.
If I load a clip I just recorded at 1080p, without the focus pixel map installed, the clip opens fine (With the focus dots showing).
If I shutdown MLV APP, Install the new 80000331_1992x1109.fpm; when I launch the app and open a 1080p clip, I get a beach ball and I need to force-quit (I'm on OSX).
If I launch the app again, but load a 2.8k clip this time, all is well. MLVApp 1.14, official build.
Try report this on Mlv App thread. Strange.
New build
- Removed histogram check. It was causing some serious overhead. Need to rethink. Maybe a manual switch back to regular preview when selected 12bit etc.
New build
- Fix for now regarding Histogram:
(https://i.postimg.cc/FszfttqJ/VRAM0-PPM-300px.jpg)
New build again.
- Seems I fixed histogram check automated and without speed penalty.
Quote from: Danne on February 19, 2024, 02:51:18 PM
New build again.
- Seems I fixed histogram check automated and without speed penalty.
The camera heats up faster with RAW histogram enabled, quite CPU demanding, but good to know it works now if I ever use it :D
Here's a test I made last week, checking overhead. Could be useful as a baseline.
The effects of different settings on Write Speeds / Recording times:
Because I didn't know what the parameters were ahead of time, I give the following figures in seconds of recording time instead of speed in MB/s.
This allowed me to set a fixed exposure level and only change Settings.
As the slightest change in exposure can make a difference of +- 30 seconds, this approach will make the test length more manageable, because there are too many variables to take into account to do several trials to check repeatability.
Card Tested: Samsung Evo Plus microSDXC UHS-I 512GB MB-MC512K (Fresh Low-Level Format)
Build Used:magiclantern-crop_mood.2024Feb11_Custom.EOSM202.zip
Resolution: 2880x1206 14 bit
More Hacks set to Always, unless specified.
Filming a test chart on LCD Screen, slightly off-focus to avoid moiré (Which would affect the Data Rate).
I set the exposure to be slightly under the Write Speed limit of the card, so I could get a max record time of about 30 seconds (Baseline).
1- MF (Manual Focus), No Custom Buttons Assignments, Kill GD ON = 31-35 Seconds (Baseline)
2- AF (Auto Focus), No Custom Buttons Assignments, Kill GD ON = 31-45 Seconds
3- MF, No Custom Buttons Assignments, Kill GD Off = 20-21 Seconds
4- AF, No Custom Buttons Assignments, Kill GD Off = 20-21 Seconds
5-MF, Custom Buttons INFO x10 Zoom , SET False Colors, Kill GD On = 31-33 seconds
6-AF, Custom Buttons INFO x10 Zoom , SET False Colors, Kill GD On = 31-33 seconds
7-AF, Custom Buttons INFO x10 Zoom, SET False Colors, U/D ISO, Kill GD On = 6 seconds (31-33 seconds if More Hacks = Always)
8- MF, Custom Buttons INFO x10 Zoom, SET False Colors, U/D ISO, Kill GD On = 6 seconds (31-33 seconds if More Hacks = Always)
9-MF, Custom INFO Aperture Expo, SET False Colors, U/D ISO, Kill GD On= 6 Seconds (31-33 seconds if More Hacks = Always)
10-AF, Custom INFO Aperture Expo, SET False Colors, U/D ISO, Kill GD On= 6 Seconds (31-33 seconds if More Hacks = Always)
11-AF, Custom INFO x10 Zoom, SET False Colors, Kill GD On, Histogram On= 31 Seconds
12-AF, Custom INFO x10 Zoom, SET False Colors, Kill GD Off, Histogram On= 16-18 Seconds
13-AF, Custom INFO x10 Zoom, SET False Colors, Kill GD Off, Histogram On= 11-16 Seconds; Kill GD On=30-31 Seconds
14-AF, Custom INFO x10 Zoom, SET False Colors, Kill GD On, =1:07 (I lowered the exposure to get a New, Longer Baseline)
14b-AF, Custom INFO x10 Zoom, SET False Colors, U/D ISO, Kill GD On, = 6 Seconds
14c-AF, Custom INFO x10 Zoom, SET False Colors, Kill GD Off, = 21-25 Seconds
Conclusion: For those who prefer using the higher resolution / high bit depth Presets, or just extend recording times, the following is recommended:
Kill Global Draw must be set to On;
and ISO / Aperture assignments to the custom buttons must be avoided while recording.
Quote from: Danne on February 18, 2024, 08:27:56 AM
@Frank7D, Yes, stretched, but only a little right?
Yes. I think the screen has a par like 1920x1280. Using 1920x1080p preview, a circle appears a bit taller than it is wide. But it's fine for framing, which was my main goal. Thanks again!
Quote from: iaburn on February 18, 2024, 09:58:07 AM
Will test later, thanks!!
Another 1620p sample, this time with a tiny Cosmicar/Pentax 16mm f1.4 lens (the one on this post (https://www.dpreview.com/forums/thread/3634499#forum-post-53238394))
Wow that is really nice. Thanks for posting. Does this 16mm lens causes vignetting? I have C-EOSM adapter, but mounting a C-lens does not show up anything. Maybe wrong adapter from Amazon! Which adapter did you use?
Quote from: zenny on February 20, 2024, 04:14:39 PM
Wow that is really nice. Thanks for posting. Does this 16mm lens causes vignetting? I have C-EOSM adapter, but mounting a C-lens does not show up anything. Maybe wrong adapter from Amazon! Which adapter did you use?
Hi, thanks. I think there is a setting on the EOS M to allow recording without lens, which is necessary to mount lenses without electronic contacts. Try that if you hadn't already.
At least you should see light, no matter which adapter you are using.
Most c-mount lenses will not cover the entire sensor, that's why the 1x1 modes are so useful, they only use a small part of the sensor, so the lens protection covers all the area in use.
With this 16mm you will get an image like looking through a tube on 3x3 1080p for example.
There are many different c-mount lenses and it's hard to tell how big the projection circle will be, so I just buy the cheapest ones so I don't feel bad if they don't perform too good :D
Manual page 283: C.Fn IV, 7: Release shutter w/o lens
Quote from: iaburn on February 20, 2024, 05:03:30 PM
Hi, thanks. I think there is a setting on the EOS M to allow recording without lens, which is necessary to mount lenses without electronic contacts. Try that if you hadn't already.
At least you should see light, no matter which adapter you are using.
Most c-mount lenses will not cover the entire sensor, that's why the 1x1 modes are so useful, they only use a small part of the sensor, so the lens protection covers all the area in use.
With this 16mm you will get an image like looking through a tube on 3x3 1080p for example.
There are many different c-mount lenses and it's hard to tell how big the projection circle will be, so I just buy the cheapest ones so I don't feel bad if they don't perform too good :D
Thanks for explanation. I have a 35mm f1.6 CCTV lens. When I used 1x1 crop, I get just blur blob like bokeh on the screen. Would you mind shariung your configs while using 16mm C-mount lens to film such a gorgeous 4:3 video? Thanks
Quote from: Walter Schulz on February 20, 2024, 05:21:43 PM
Manual page 283: C.Fn IV, 7: Release shutter w/o lens
Thanks for the pointer, your inputs are always as technically-precise as that of Danne and Bilal. Cheers and good night.
Quote from: zenny on February 21, 2024, 07:30:59 PM
Thanks for explanation. I have a 35mm f1.6 CCTV lens. When I used 1x1 crop, I get just blur blob like bokeh on the screen. Would you mind shariung your configs while using 16mm C-mount lens to film such a gorgeous 4:3 video? Thanks
I'm afraid this is not a settings problem. If your c-mount lens cannot focus, you can try adding a spacer. It's like a small ring that will move the lens further, hopefully improving focus...
Huge thanks for the Crop Mood updates! :D
Danne, and the whole forum community, you're all amazing!, thank you so much for your work on the Crop Mood features for the EOS M. So grateful for your dedication and hard work. These continuous updates are transforming the way I use my little camera
You guys rock! :P
I've noticed that the new 1620p mode doesn't show the image through the HDMI out, is it something fixable or is this mode too special?
Not directly related to this build, but another issue that I have is that the image through the HDMI port is blowing the highlights from a certain brightness, while they still look good on the camera display and the histogram is also not reporting any overexposed area.
I thought that it would be a setting on the monitor, but I cannot fix it.
Is it a known issue? Anyone else did also notice that?
Hdmi for this mode could be working. I did'nr look into it at all but there is a lot of nice code around HDMI from Bilal we could play with.