Messages

1

crop_rec and derived builds / Re: Crop mood - WYSIWYG Edition

« on: April 07, 2023, 05:17:02 PM »

About the crowdfunding, maybe someone will not agree, but why not impose an upper limit on the money offered by each individual person, perhaps around 15/20 dollars?

I don't want to be misunderstood, I certainly don't intend to devalue the work done by Bilal, which I consider extraordinary and incredibly superior to what he asks in return.
I only believe that crowdfunding is good when there is broad participation, in which many people can and are in some way encouraged (if not "forced") to contribute.

By the way, last time, when I saw the subscription, it was already closed thanks to a few generous users. This time I really want to contribute. 

2

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: February 06, 2023, 08:56:06 PM »

I haven't done extensive testing, but I've discovered a very small problem: when you set the ISO value from the Expo menu to AUTO, you can't even get into the ML menu anymore. You have to avoid loading ML and set it again to a different value from the Canon menu.
It's a really small bug, probably no one is using auto iso in ML (I don't use it myself, I set it by mistake), so it may be a lowest priority problem to fix.

3

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: February 03, 2023, 05:22:46 PM »

Nice to know I am not alone!

The shutter button behaves a lot better than last year, where it were a lot more sensitive, but I also press it too far every now and then.

Yes, it definitely behaves alot better. I will try your suggestions this weekend, thank you very much!

@Danne
As soon as I get some free time I'll starting looking too, but I don't have big hopes since you know the code so much better than anyone else!

4

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: February 03, 2023, 03:31:47 PM »

The latest changes appear to be a big improvement over the version from just a month ago!
The shot preview is pretty much usable in my opinion, so even with the highest resolutions I don't have to be blind frame anymore!
Danne, you did a great job once again! 

I have other cameras, but I honestly find using Magic Lantern easier and more rewarding than other companies' native shooting functions. 

Only one detail bothers me, and that's the shutter button. Isn't there a way to block the photo taking functionality?
Personally I only use the camera for video and sometimes it happens that I press the button too much while focusing, ruining the shot.
Does this happen to anyone else or am I the only wimp? 

5

Raw Video Postprocessing / Re: MLV App 1.14 - All in one MLV Video Post Processing App [Windows, Mac and Linux]

« on: January 27, 2023, 11:01:59 AM »

Yes, the idea of comparing points between images and taking the one from the low iso image if the difference exceeds a threshold might be naive... but in my opinion it's also quite wise. 

The choice of the threshold value can be critical and, as you said, it can be different depending on many things (especially the selected ISO values).
However, I still have the impression that the root of the problem may be exposure for video: ETTR should be applied for the high iso, not the low one.

Technically speaking, with dual ISO we gain more detail in the shadows, not in the highlights (I said technically because in post we can change exposure as we prefer).
That's why a1ex reduces the exposure of the high iso image before merging, instead of increasing the exposure of the low iso.

By the way, his blending algorithm is much more complex and sophisticated, but I suspect it's also too slow to be usable for video. That's why it has been simplified in the implementation.

6

Raw Video Postprocessing / Re: MLV App 1.14 - All in one MLV Video Post Processing App [Windows, Mac and Linux]

« on: January 26, 2023, 10:59:30 AM »

Activating "Fullres reconstruction" improves the resolution on the shadows but can break highlights, so I will try to add an option to do fullres reconstruction only on the shadows for these cases

From the documentation of the a1ex dual-iso algorithm, full frame reconstruction should only be possible for midtone and impossible for both highlights and shadows.
This is because only the midtones fall into the "sensitive" part of both the low and high ISO lines.

7

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: September 21, 2022, 10:32:56 AM »

Being a 5.2k, this new setting has so much vertical resolution that dual-iso is no more so much penalizing in terms of loss of detail.
Danne and Bilal did a wonderful job!

8

Raw Video Postprocessing / Re: MLV App 1.14 - All in one MLV Video Post Processing App [Windows, Mac and Linux]

« on: July 06, 2022, 02:00:50 PM »

My goal is to create digital image processing that handles bright colours smoothly. It's possible. Film does it. It's what I've been working towards for the past two years.

That's a great goal.
Color science (including color smoothness and highlight rolloff) can make more difference in the beauty of an image than the dynamic range and much-much-more difference than the resolution (personally I don't care too much of resolution unless it's less than 720p).

About this, are colors in MlvApp treated like in the color science of Arri Alexa (or Amira), with color saturation limited to a certain value like in watercolors?

9

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: May 04, 2022, 02:14:54 AM »

The latest releases are really great, thanks to Danne!

I don't have suggestions about shortcuts for the buttons INFO and SET, but about the gain button, there's a limitation that perhaps can be avoided.
When dual iso is enabled the gain buttons gets always disabled.
That's perfectly understandable if the gain buttons are set to control iso value, but maybe if set to "aperture only" they don't need to be disabled.
I could be missing the whole point, anyway...

10

Raw Video / Re: AI algorithms for debinning

« on: July 20, 2021, 02:45:23 AM »

About a better way to manage debinning... I had an idea for a custom debayering (some months ago) that could give us a bit more horizontal resolution, at the expense of some vertical resolution.
It could work but... the problem is that it needs the green pixels to be binned in a "shifted" way between lines, as shown in the following post:
https://www.magiclantern.fm/forum/index.php?topic=16516.msg210484#msg210484
as you can see the middle green pixel of the binning group of one line falls right between two groups of the following one (just forget the line skipping of the picture, it's not our case for 5k anamorphic). Substantially, it's a three pixels shift.

But... after some checking and tests I can confirm that, at least on the EOS-M and the latest ML version of Danne, the green pixels are binned with a single pixel shift between the line and the following one. So my idea cannot work on the current recorded material.
In case someone knows how to change the shift in binning (I played with registers with no success)... there could be a chance to test it, otherwise I think there's no way to improve the current quality.

11

Reverse Engineering / Re: Pixel binning patterns in LiveView

« on: March 05, 2021, 03:02:08 AM »

Thanks Levas!
I already entered that page but I missed the module from the list. Now I got it!
I'm gonna install the module following your suggestions for doing the tests. 
As soon as I am ready, I'll share my results here and I would be pleased if you and the other experienced guys can comment on them. 

12

Reverse Engineering / Re: Pixel binning patterns in LiveView

« on: March 03, 2021, 01:46:09 AM »

I'm doing some tests and I think to have found something interesting about the binning...
To double check it, I would like to play a bit with some settings to the the cmos registers.

Since I'm using the latest eos-m Danne release and the Adtg module is not included, is there an alternative way to adjust those registers without recompiling ML?
I've seen similarly called registers inside the page: Movie -> presets -> advanced
Can anyone confirm if they are exactly the same?
Thanks!

13

Raw Video Postprocessing / Re: MLV App 1.11 - All in one MLV Video Post Processing App [Windows, Mac and Linux]

« on: January 05, 2021, 06:56:44 PM »

@theBilalFakhouri

Yes, I already read that post. It helped me to understand how the binning is done in these cameras. And I have seen other people had almost my same idea.

What you say is absolutely true, we cannot restore the information that is lost with the binning.
But still I think an unbinning process is needed before doing the demosaicing: the value for the unbinned pixels won't be the original one, just an estimation from the nearest ones.

My opinion is not that we can restore what is lost during binning, but that applying a demosaicing algorithm made for unbinned pixels won't give best results on a binned image. In other words, I think we are losing even more detail than what the binning process itself implies.
It's absolutely just an opinion and I could be wrong, but I would like to test it.

P.S.: I have seen your contribute on many parts of the project and I really consider it impressive!

14

Raw Video Postprocessing / Re: MLV App 1.11 - All in one MLV Video Post Processing App [Windows, Mac and Linux]

« on: January 05, 2021, 01:35:03 AM »

Lately, I am studying by myself the Bayer filter and some demosaicing algorithms.
I think those included in MlvApp are great and the results are generally stunning.
What I'm not sure about is the correctness of the common way to proceed with videos recorded using the 1x3 binning pattern.
In my opinion, demosaicing the video then doing a horizontal stretch (or a vertical shrink) is going to lose part of the information captured with the raw image.
Personally, I would first expand the raw image unbinning the pixels with an ad-hoc algorithm, then I would apply to the resulting raw one of the existing algorithms (e.g. Amaze).
I could be wrong, but if you look at the pixels that are binned... they are spatially in a slightly different position compared to a normal Bayer filter.
I have an idea about how to do the unbinning, but I would like to have some suggestions on where to make the changes to the code.
BTW, I am a software developer, so my problem is not in coding, but not all the project code is clear to me.
If someone can help proceed with the test, that would be great.

15

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: November 15, 2020, 12:28:02 PM »

Nevermind.
I just asked because it seemed to me that I tried that resolution (in frtp) with a previous build and so I thought I now was not able anymore to set it up correctly.

16

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: November 15, 2020, 12:56:24 AM »

Hello, I need some help! 
I'm unable to get the resolution 1504x1782 (1x3) starting from the 5K anamorphic frtp preset.
It should be possible since it has been described here: https://www.magiclantern.fm/forum/index.php?topic=25323.msg230933#msg230933 and I was able to get it with older releases.
I'm currently using Danne build of 27 October.

Another question: how to disable the function to take a picture/snapshot while in movie recording mode?
Thank you for any suggestion.

17

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: September 21, 2020, 07:57:30 PM »

Uhmmm... I'm getting some thin vertical stripes over the realtime preview in this newest anamorphic  2.35 AR, but only during recording.
Still a great job!

18

crop_rec and derived builds / Re: Danne's crop_rec_4k experiments for EOS M

« on: August 16, 2020, 10:41:47 PM »

Hello all!
Thank you for this wonderful project and all the amazing improvements that have been made lately!
I have a couple of questions about the different EOS-M video profiles/presets:
- Is it possible to disable the zoom in the live view in 2.5k/2.8k/3.0k modes? I know the picture is severy cropped, so I would get a small view with black borders all around, but that is absolutely ok for me. I just don't know if this is a known limitation or a design choice.
- Any chance to have in the future a 2x2 profile (with line/column skip mode) to get a 2.6k using the full width of the sensor?
Thank you in advance for any feedback!