Menu

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.

Show posts Menu

Messages - NunoCaldeira

#1
Main Builds / Re: EOS M Update
January 02, 2018, 11:31:19 PM
Quote from: hkden on January 02, 2018, 06:07:15 AM
Hi guys,
I just updated my EOS M firmware to the latest, 2.0.3.

I went to download the appropriate ML firmware.

The ML release says it's only for 2.0.2.

Before I downgrade my firmware - 

quick questions, has anyone used the ML Firmware on Canon Firmware 2.0.3?

Is it be stable?

Thank you

Den
you answered your own question. unless you want to try something that might brick your camera.
#4
Camera-specific Development / Re: Canon 6D
October 16, 2017, 02:07:23 AM
will try it tomorrow
#5
Quote from: Lars Steenhoff on October 15, 2017, 05:49:59 PM
and did you get it to work with any version you downloaded at all?
perhaps the lua fixes one as thats more recent
didnt manage it to work,only with the April one
#6
Quote from: Lars Steenhoff on October 09, 2017, 01:30:51 AM
Ok I just tried building for the 6D but I got some errors.
no worries Lars. was just trying to get it working with the latest nightly. cheers
#7
Raw Video / Re: Raw Slow Motion 5D Mark III
October 12, 2017, 04:11:40 AM
you can find the answers for your questions, by using "Search" on your upper left.
#8
Quote from: Lars Steenhoff on October 09, 2017, 12:37:44 AM
https://www.dropbox.com/s/jwuambvb6it1xmz/magiclantern-Nightly.manual_lens_info.2017Oct09.5D3123.zip?dl=0

@NunoCaldeira you can try this build from today where I merged the manual lens info branch on to the 4kcrop.

Please report if it works well for you, or if you have any issues.
thanks, but have a 6D. not 5D MKIII :)
#9
Quote from: Lars Steenhoff on October 07, 2017, 06:24:04 PM
I think you copied the script to a build from 4k crop without the capabilty of manual lens scripts?

Quote from: dfort on October 07, 2017, 05:51:05 PM
@NunoCaldeira

What exactly are you doing? Updating a lua script shouldn't be that hard.

6D Latest Build: 2017-10-03
copy the lua script to script folder
#10
Quote from: dfort on October 04, 2017, 07:22:14 AM
I've got a pull request open for additional lenses but other than the branch hasn't changed much. You could comment on the pull request or just take the script from bitbucket and replace the one in your ML/scripts directory.

By the way, there's another pull request for merging manual_lens_info into lua_fix. That would be a very good thing for this project because at some point lua_fix will be merged into unified and it will be available on the nightly builds.

tired that, with no success. the script isnt shown on the SCRIPTS menu. when i get to DEBUG menu theres the Memory Error in red.
#11
any idea when will we have a build with this? last one was in April
#12
User Introduction / Re: Not a hacker
September 28, 2017, 02:01:50 AM
you should read FAQ and ML User Guide http://wiki.magiclantern.fm/userguide#bulb_timer
#13
update with two new lenses:

{ name = "Lensbaby Sweet 80", focal_length = 80, manual_aperture =  2.8 },
{ name = "Lensbaby Creative Bokeh", focal_length = 50, manual_aperture =  2.5 },
#15
cool.

heres the values:

--  Lensbaby lenses

--  { name = "Lensbaby Sweet 35", focal_length = 35, manual_aperture =  2.5 },
--  { name = "Lensbaby Sweet 50", focal_length = 50, manual_aperture =  2.5 },
--  { name = "Lensbaby Twist 60", focal_length = 60, manual_aperture =  2.5 },
--  { name = "Lensbaby Edge 50", focal_length = 50, manual_aperture = 3.2 },
--  { name = "Lensbaby Edge 80", focal_length = 80, manual_aperture =  2.8 },
--  { name = "Lensbaby Circular Fisheye", focal_length = 5.8, manual_aperture =  3.5 },
--  { name = "Lensbaby Soft Focus Optic", focal_length = 50, manual_aperture =  2 },
--  { name = "Lensbaby Double Glass Optic", focal_length = 50, manual_aperture =  2 },
--  { name = "Lensbaby Single Glass Optic", focal_length = 50, manual_aperture =  2 },
--  { name = "Lensbaby Plastic Optic", focal_length = 50, manual_aperture =  2 },
--  { name = "Lensbaby Pinhole Optic", focal_length = 50, manual_aperture =  19 },
--  { name = "Lensbaby Fisheye Optic", focal_length = 12, manual_aperture =  4 },
--  { name = "Lensbaby Velvet 56", focal_length = 56, manual_aperture =  1.6 },
--  { name = "Lensbaby Velvet 85", focal_length = 85, manual_aperture =  1.8 },
--  { name = "Lensbaby Creative Aperture", focal_length = 50, manual_aperture =  2 },
#16
hi a1ex.

Regarding the Lensbaby:
- I will organize the aperture field. i already done it for most of the optics at my website http://www.lensbabylovers.info/2013/03/compatability-chart.html Just to confirm, you want each unique f value possible with each optic or just the min and max f? I have them all, can confirm, just let me know if you want the min-max or all the possible f values.
- Yes you can replace LB with Lensbaby (i was just lazy);
- The lens names dont have typos. You can verify lensbaby lens names here https://lensbaby.com/optic-compatibility/

Technically, lensbaby lenses (besides Circular Fisheye, Velvet 56 and Velvet 85) are called optics, because they can be used with one of these optic bodies (Composer, Composer Pro, Composer Pro II, Spark, Muse). But in my point of view, theres not really a point of having to list the lens body, when what matters is the optic.

#17
thanks for your quick reply.
Are we sorting some sort of list of lenses for the future to act like a "db"? Guess it would be easier to delete than to add manually.
Anyway heres my listing regarding Lensbaby lenses:

{
        { name = "LB Sweet 35", focal_length = 35 },
{ name = "LB Sweet 50", focal_length = 50 },
{ name = "LB Twist 60", focal_length = 60 },
{ name = "LB Edge 50", focal_length = 50 },
{ name = "LB Edge 80", focal_length = 80 },
{ name = "LB Circular Fisheye", focal_length = 5.8 },
{ name = "LB Soft Focus Optic", focal_length = 50 },
{ name = "LB Double Glass Optic", focal_length = 50 },
{ name = "LB Single Glass Optic", focal_length = 50 },
{ name = "LB Plastic Optic", focal_length = 50 },
{ name = "LB Pinhole Optic", focal_length = 50 },
{ name = "LB Fisheye Optic", focal_length = 12 },
{ name = "LB Velvet 56", focal_length = 56 },
        { name = "LB Velvet 85", focal_length = 85 },
{ name = "LB Creative Aperture", focal_length = 50 },
}
#18
hi guys. thanks for this. how do i add my manual lens to the list? any tips would be welcome.
Also had 3 crashes on my camera when using this. where should i upload the logs, if it matters. thanks in advance
#19
Camera-specific Development / Re: Canon 6D
July 15, 2017, 04:18:42 PM
Quote from: Oleg_K on July 12, 2017, 04:17:08 AM
This I read, the camera canon 6d does not work.
unless you made a custom ML for yourself it does (yes i do have a 6D).
https://www.magiclantern.fm/forum/index.php?topic=3498.0

go to PREFS/POWERSAVE IN LIVEVIEW/ then enable the power saving on recording or whatever u want, pick a button to activate or turn off auto after certain seconds.
#20
Camera-specific Development / Re: Canon 6D
July 11, 2017, 08:17:22 PM
Quote from: Oleg_K on July 11, 2017, 07:17:16 AM
How to turn off the display during the timelapse and is it possible for Canon 6D?
Button "info" I do not turn the screen, and sorts out different information.
http://wiki.magiclantern.fm/userguide#powersave_in_liveview

Powersave in LiveView...

Options for maximizing battery life when using LiveView.
Quote
    Enable power saving: on Standby, during Recording, or always.
    Use LCD sensor: you can use it to wake up from powersave (wave your hand near it), or to force powersave mode (cover the sensor for a few seconds).
    Dim display: In LiveView, if the camera is idle, Magic Lantern will reduce the LCD backlight level to minimum in order to save power.
    Turn off LCD and LV: this will turn off the display and the sensor activity in LiveView. Mirror will not be moved. If the camera is recording or motion detection is enabled, only the display will be turned off (so recording will not stop).
    Turn off GlobalDraw: if the camera is idle, ML overlay graphics will be disabled to reduce CPU usage.

#21
Yes, that happens to me too, it turns into green and magenta.. Even disabling the fps override it continues to show up on the live view and only restarting the camera it goes normal. Can anyone besides me and this user confirm? Think it's a bug on the latest nightly build. As I mentioned I used to fps override a lot on the 550D and I have the exact same settings on the 6d and this error is persistent.
#22
hi, is the FPS OVERRIDE feature available on the 6D (i have checked this and looks like https://builds.magiclantern.fm/#/features )? i use to use it a lot on my 550D, but cant seem to get it to work properly on the 6D. i only get, for instance, 3fps on the liveview not on the recorded. also the images doesnt blow up (i use ND filters ) when i turn the feature and return to liveview. any tips? Do i have any other option on the official firmware or on ML that i have to disable?
#23
Archived porting threads / Re: Canon 6D
March 22, 2015, 10:43:10 PM
sorry...my bad...just realized i had to press the top LCD light button to trigger that function to be displayed on playback mode :(. Sorry guys for making you waste time. Thanks for the support and for working on ML.
#24
Archived porting threads / Re: Canon 6D
March 22, 2015, 10:33:33 PM
yes i am in playback. it does work on liveview, not just in playback
#25
Archived porting threads / Re: Canon 6D
March 22, 2015, 10:05:25 PM
heres the video, activating and deactivating the functions that work and the ones that doesnt.