Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Straight_Shooter

Pages: [1]
1
Camera-specific Development / Re: Canon 80D
« on: May 19, 2021, 03:14:16 PM »
I really don't know why my realism is perceived as sarcasm. I offered an easy calculation for this assumption. Nobody challenged the numbers, yet.
https://www.magiclantern.fm/forum/index.php?topic=19737.msg225763#msg225763

Well, may I challenge them? ;-)

Learning to program is one thing. But even if you have mastered C or C++ or whatever language, you are still a far cry away from being able to make any meaningful change in MagicLantern. We're talking about a complex piece of software here. To the best of my knowledge, there is no real requirement specification or design specification - if you want to get into it, you have to do so by jumping through dozens of threads on this here forum, and by reading thousands of lines of code. That is cumbersome work, to be quite honest. It's as if you wanted to climb a medium-sized hill, but then they tell you "No, you need to do the Seven Summits for starters. Then we're talking." ;-)

2
It would be great if one could donate to this project via PayPal. I know I would give a couple bucks to it for sure.

3
General Development / Re: Easy Coding tasks
« on: May 19, 2021, 02:46:20 PM »
Would there be a way to breathe some new life into this thread? That is, to set up some new easy coding tasks for people to work on? I think that having these is a great idea, and it can help to bring in some new people into ML development. Can't hurt to try :)

4
Camera-specific Development / Re: Canon 1100D / T3
« on: March 05, 2017, 05:18:01 PM »
Looks OK, so the 1100D build was re-enabled a while ago.

Ah, that is great news! I hadn't noticed that yet. Thanks for your good work a1ex.

5
Camera-specific Development / Re: Canon 1100D / T3
« on: March 05, 2017, 05:08:05 PM »
1280x720 @ 25 fps selected:
ML displays a steady fps rate of 25.000

1280x720 @ 30 fps selected:
ML displays one of two different values. The fps value changes between 29.976 and 29.922.
This behavior is reproducible, but the time after which this happens seems to be random? I have seen it happen like after half a minute, or sometimes earlier (after ten seconds or so). It seems that the value 29.976 is shown for noticeably longer periods of time than the other value.

Desired FPS: 35 (from 25)
Actual FPS: 34.949

Desired FPS: 35 (from 30)
Actual FPS: 34.949

Okay, so... does anybody know what to do with these values?

I tried looking at the code, but I can't really make heads or tails of it.

6
Camera-specific Development / Re: Canon 80D
« on: March 05, 2017, 05:01:32 PM »
I am now the owner of an 80D, in addition to my old 1100D.  :)

As soon as we have some binary that we can test I will be happy to help with testing.

7
Feature Requests / Re: [ALREADY DONE] Auto Preview for long exposure.
« on: January 15, 2017, 11:27:12 PM »
Nope, this one doesn't exist yet.

I see. Could you please remove the [ALREADY DONE] tag then, it seems to be kind of a misnomer.

Also, I am wondering: Would this be possible to do at all? Do you perhaps have a rough estimate how difficult it would be to do (if at all possible)?

You can preview the brightness of a long exposure, in LiveView, with:
- ExpSim on
- Expo Override on
- FPS override in Low Light mode, as needed

More details here or here.

On DIGIC 4 models, FPS override goes to very low values (close to one frame every 5 seconds), so you can preview motion blur in some cases as well (but not on the actual exposure).

Here's a script that gets somewhat close to your request (though it doesn't add the frames in camera).

Thanks a lot, I will look into those.

8
Feature Requests / Re: [ALREADY DONE] Auto Preview for long exposure.
« on: January 15, 2017, 04:29:58 PM »
Hi,

I am not sure if I understood everything in this thread correctly. Could somebody please tell me: Does this feature exist in Magic Lantern?

Description of the feature:
1.) You set up a long-exposure in your Canon camera
2.) You start the exposure
3.) While the camera is busy taking the picture, the Live View monitor shows the picture as it is being generated. (perhaps updated e.g. once per second)

The purpose of this would be to stop the exposure when the "preview image" on the monitor looks just right.
This would be extremely useful for night photography and light painting.

9
Feature Requests / Re: Live Composite Mode / Live Time Mode
« on: January 15, 2017, 04:12:21 PM »
The end result will have higher absolute noise (not as good in very low light), but also higher dynamic range.

How so? I thought that when you combine many pictures into one, then you get less noise in the end result? Since the noise is randomly distributed in every picture, and you have as many data points for every single pixel as you have pictures, I thought that this would even out then.

Maybe I am mistaken here - quite possible. I am by no means a professional photographer. Rather an advanced amateur.

Also, I would totally kill to have these features from Olympus being available on Canon cameras! ;)
Or rather, I would pay 100 (one hundred) dollars to the person who implements Live Composite Mode and Live Time Mode in Magic Lantern. Any takers?

10
Camera-specific Development / Re: Canon 1100D / T3
« on: January 14, 2017, 09:38:35 PM »
With this build, please check whether the FPS values displayed by ML match the value selected from Canon menu, in all video modes.

1280x720 @ 25 fps selected:
ML displays a steady fps rate of 25.000

1280x720 @ 30 fps selected:
ML displays one of two different values. The fps value changes between 29.976 and 29.922.
This behavior is reproducible, but the time after which this happens seems to be random? I have seen it happen like after half a minute, or sometimes earlier (after ten seconds or so). It seems that the value 29.976 is shown for noticeably longer periods of time than the other value.

Also check whether selecting 35 fps in ML menu gives valid image in all video modes.

Desired FPS: 35 (from 25)
Actual FPS: 34.949

Desired FPS: 35 (from 30)
Actual FPS: 34.949

11
Camera-specific Development / Re: Canon 1100D / T3
« on: January 13, 2017, 01:17:40 AM »
From what little I know about this issue, I seem to understand that the value for TG_FREQ_BASE is not correct. To solve this, somehow a better value needs to be obtained. But I have zero idea what exactly needs to be done to achieve that, hence my question.

What kind of computation is needed here? Is this explained at some point in the code, maybe in a comment?
I guess I'll try having a look at the file: fps-engio.c

12
Camera-specific Development / Re: Canon 1100D / T3
« on: January 12, 2017, 04:29:15 PM »
The 1100D nightly build was intentionally disabled because a1ex noticed some incorrect values for FPS override timers. I've never cared enough to try and fix it (the Maths involved hurt my head :P ), I just compile it with the old incorrect values.

Hi dmilligan,

being both a software developer and an owner of the 1100D, I would be willing to help here. However I have no idea what exactly needs to be done with the values found by Floont in Reply #1410. You mention something about complicated maths. Is there some formula that we need to compute certain values with? Could you please point me in the right direction about what needs to be done? Then maybe I can figure out a way how to do it.

Pages: [1]