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

Pages: [1] 2 3
1
Magic Lantern Forum and Site Discussion / Re: Non-bitcoin donations?
« on: July 25, 2019, 04:44:46 AM »
Great, thank you for replying a1ex.

I'll send the money to g3gg0's PayPal.

Thank you so much for your hard work!

2
Magic Lantern Forum and Site Discussion / Re: Non-bitcoin donations?
« on: July 20, 2019, 05:47:12 PM »
I really want to give you guys some money.

3
Magic Lantern Forum and Site Discussion / Non-bitcoin donations?
« on: July 08, 2019, 06:51:28 PM »
Hi,

I want to donate some money but I noticed there's only a bitcoin option in the donation page.

Is there a way to donate using PayPal?

4
I tested a few builds and went back to the first build that supports the 6D (magiclantern-crop_rec_4k.2018Mar10.6D116.zip) and even that one doesn't work properly.

I also reseted the camera to factory settings before testing.

5
Did this work any better in previous builds? If yes, can you find the last good build?

https://builds.magiclantern.fm/jenkins/view/Experiments/job/crop_rec_4k/

This is the first time I'm using it. I'll test previous builds and see how that goes. Will report back after testing.

6
Best guess: some sort of misconfiguration for ADTG powersaving registers.

Please define "latest crop module", mention the settings used for crop_rec (including resolution and frame rate in Canon menu) and the number of affected lines (the low-resolution screenshot doesn't help much).

I'm using magiclantern-crop_rec_4k.2018Jul22.6D116.
  • Settings for crop_rec: default, I touched nothing
  • Canon menu settings: 1280x720 @ 50fps, Low comp (ALL-I)
  • Number of affected lines: 540px
Here's the full-res image: https://i.imgur.com/ZbvYcPq.png

7
I tested the latest crop module last night on my 6D and I'm getting 2/3 of the image with a magenta color:



I used mlv_lite and mlv_rec both with default settings. Both give the same results.

Any idea what could be happening?

8
I tested the latest crop module last night on my 6D and I'm getting 2/3 of the image with a magenta color:



I used mlv_lite and mlv_rec both with default settings. Both give the same results.

Any idea what could be happening?

9
That's great information, thank you!

10
"MlRawViewer is a cross-platform viewer for raw video files produced by Magic Lantern." and outdated, not supported anymore. Nobody will fix your issue.
Move on to supported applications.

I didn't know it was outdated. What application is people using now?
This one maybe? https://www.magiclantern.fm/forum/index.php?topic=20025.0

11
I'm having issues viewing MLV files.
The program shows I have two files inside a folder:



But when I access the folder, I don't see any files:



Yet they are there in the file explorer:



I'm using v1.4.3 on Windows 10.

12
Right now I can only use the Wifi feature to monitor or download pictures using the Canon Camera Connect app, but that isn't quite useful. Would it be possible to bypass this



and record while monitoring?



13
Both in Safari




and Chrome


14
Exposure target
But if I change that setting to let's say -2 EV (what I would need for night time), during daylight I'll get an underexposed shot.

15
I noticed AutoETTR tends to "overexpose" my shots when the sun goes down and there's moonlight. It's not actually overexposed because the histogram is far from the edge, so I could bring down the exposure and get a nice exposed image, but I was wondering, is there a way to make the module underexpose a bit the images during night? Less steps in post are always welcome.

I was shooting on a 6D and my settings were:
Exposure target: -0.5 EV
Highlight ignore: 0.1%
Midtone SNR limit: 6 EV
Shadow SNR limit: 2 EV
Trigger mode: Always ON
Slowest shutter: 8"
Interval: 15"

16
Modules Development / Re: Intervalometer Ramping Module (adv_int.mo)
« on: July 30, 2015, 06:27:00 AM »
Yes, that's what I meant. So even though this is a separate module you can't change that behavior? Is that because it depends on the core intervalometer?

17
Modules Development / Re: Intervalometer Ramping Module (adv_int.mo)
« on: July 29, 2015, 04:03:37 PM »
Lately I've been reading about this module and after experimenting a bit I noticed the interval ramping only works with integers. Would it be possible to change that behavior to have it ramp using decimal intervals? That way it would be more accurate and more similar to a bulb ramping when used along with Auto ETTR.

18
General Help Q&A / Canon 60D: broken shutter logs (Err 20)
« on: July 27, 2015, 04:11:48 AM »
Today I broke my shutter and while downloading my images I saw some logs on the card. I was thinking maybe those are useful for developers? Let me know if you want then, I can upload the logs for you.

PS: Not sure where to post this, sorry if it's in the wrong subforum.

19
Camera-specific discussion / Re: Canon 6D / Firmware 1.1.6
« on: June 26, 2015, 05:13:25 AM »
No problems here with the third party batteries I was using with 1.1.3.

20
Anybody know where I can download Canon firmware 1.1.3?

Page 1 of this thread.

22
Archived porting threads / Re: Magic Lantern for 6D | Dev kit released
« on: April 02, 2014, 04:16:00 AM »
Nope, I'm running 1.1.3 and my only 3rd party battery is chipped and works fine. I've only heard of the new error message and delay on CR and decided it's not worth finding out for myself. The same thing is present on latest 5d3 though.

What delay exactly?

I'm on 1.1.3 and two of my batteries show this error message when turning the camera on, not sure if its the same as 1.1.4


23
Archived porting threads / Re: Magic Lantern for 6D | Dev kit released
« on: March 31, 2014, 04:52:10 PM »
Nope, not supported yet, simply downgrade to 1.1.3 as the (nearly) only thing 1.1.4 does is screw 3rd party batteries.
I'm sure someone already asked this but I couldn't find a proper answer. Would it be possible to bypass that with Magic Lantern so third party batteries show up as an original?

24
Feature Requests / Re: Force fixed aperture for non chipped lenses
« on: March 05, 2014, 11:51:16 PM »
Whoa whoa... this feature is for live view. So silent pics, raw, etc... I've never seen it keep the settings in photo mode. It appears to do the same thing on other cams I tried as it does on 6D... so how exactly isn't working?

I only tried on live view, not other modes.

This is what I do:

Put the camera in M mode. Let's say it's incredible dark, a moonless night with no light pollution so I set the shutter speed to 4s so I don't have to wait a lot of time, I just need to frame my shot. f/2.8 (which doesn't matter since the camera can't read that information because the lens is not chipped) and ISO 25600.

Instead of seeing at least some detail in the screen, I just get a dark image and no visible noise moving around.

On the 60D, which has max ISO 12800, I see much more detail (and noise, of course) than on the 6D. I also use the same settings here, 4s and f/2.8.

This is another thing I could try my hands on since I have a 6D. Expo override doesn't let me change ISO anymore after enabling it but it displays the correct exposure in LV. Is it the same for you leandroprz?

I am able to change the ISO after enabling exposure override. I tried from ML and Canon menu. Also with the top button near the LCD orange screen.

Edit: after doing a few more tests, it seems I got the features mixed up. What I described above seems to be exposure simulation, right? Now I feel like an idiot -.-
Still, that feature is not working for me.

25
Feature Requests / Re: Force fixed aperture for non chipped lenses
« on: March 05, 2014, 05:16:59 PM »
I thought since it came back to the nighly builds there was a developer with the camera behind it.

Will test it again tonight under low light conditions and report back in bitbucket.

Pages: [1] 2 3