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

#1
General Help Q&A / Re: EOS Utility compatibility?
August 15, 2014, 11:05:38 AM
Hi duhast,

I had the the same problem some time ago and if I remeber correctly I had to update EOS Utility to the latest version from the Canon website.

regards
Michael
#2
Hi mk11174

The module does not work with the current nightly. (old API)

I watched your beginners guide video and was able to compile the FullRes-SilentPic module but had no luck with this one.


magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/foc_inf$ make
[ CC       ]   foc_inf.o
foc_inf.c: In function 'setinfinity':
foc_inf.c:51:5: error: implicit declaration of function 'lens_focus_start' [-Werror=implicit-function-declaration]
foc_inf.c:53:5: error: implicit declaration of function 'lens_focus_stop' [-Werror=implicit-function-declaration]
foc_inf.c:57:5: error: implicit declaration of function 'beep' [-Werror=implicit-function-declaration]
foc_inf.c: In function 'inf_focus_toggle':
foc_inf.c:62:5: error: implicit declaration of function 'is_manual_focus' [-Werror=implicit-function-declaration]
In file included from ../../src/module.h:344:0,
                 from foc_inf.c:3:
foc_inf.c: At top level:
./module_strings.h:1:13: warning: '__module_string_a_name' defined but not used [-Wunused-variable]
./module_strings.h:2:13: warning: '__module_string_a_value' defined but not used [-Wunused-variable]
./module_strings.h:3:13: warning: '__module_string_b_name' defined but not used [-Wunused-variable]
./module_strings.h:4:13: warning: '__module_string_b_value' defined but not used [-Wunused-variable]
./module_strings.h:5:13: warning: '__module_string_c_name' defined but not used [-Wunused-variable]
./module_strings.h:6:13: warning: '__module_string_c_value' defined but not used [-Wunused-variable]
./module_strings.h:7:13: warning: '__module_string_d_name' defined but not used [-Wunused-variable]
./module_strings.h:8:13: warning: '__module_string_d_value' defined but not used [-Wunused-variable]
cc1: some warnings being treated as errors
make: *** [foc_inf.o] Error 1


I am not sure if it is my setup or something has be changed in your module...
I hope you find the time to take a look at it because I find the module very useful

thnx


edit:
ok - It looks like some includes are missing ...
I added

#include <beep.h>
#include <focus.h>

and now it seems to work again.  8)

I took Pelican´s code and updated it to hopefully work with the latest nightly - not sure if this is the newest version of the module  ::)

https://www.dropbox.com/s/vhiu3zu1y9ifbki/foc_inf.mo?dl=1
#3
Quote from: Wartburg-Entertainment on July 30, 2014, 06:35:26 AM
since the last builds (28-30.07) formatting does not work in the camera.
It will delete all files except the settings-folder.

Hi,

same problem here with 60D - after formating, ML files are not written back to sdcard (only settings)

edit: looks like ML files are not copied before formating - sorry cant record a video

last working version is: 2014-07-25 00:15:34 +0200
#4
Quote from: a1ex on July 28, 2014, 08:00:40 AM
When used with Dual ISO, ETTR measures the darker sub-image only.

Yes, now it works - not sure what went wrong in my first test - thanks.
#5
Quote from: dmilligan on July 27, 2014, 09:29:04 PM
If ETTR doesn't "measure" the bright part of you picture, that part will just be blown highlights. If that's actually what you want, then set the highlight ignore to 50%.

Thats exactly what I want - I don´t need the full resolution in the bright clouds.
Right now I do this manually by not overexposing with 100 ISO and recording with 100/800

I thought about the 50% but that only works if the brighter image is 100% (all pixels) overexposed.
#6
Quote from: barepixels on July 27, 2014, 07:50:37 PM
Just curious did you do ETTR FullRes-SP silent in DNGs  or MLV

I havent used ETTR until now - cam is shooting with ETTR in .MLV right now. The dual ISOs where recorded as .MLV (200+ frames, splited .MLV files with up to 6GB = 4+2GB)

Quote from: barepixels on July 27, 2014, 07:50:37 PMWhen you did DUAL ISO FullRes-SP only, didn't your shutter speed change a lot through out the shoot? If you did in DNG then you would't have EXIF info.  But you may have notice/remember

With "DualISO only" you mean without ETTR? I dont know - I would asume not - but in one test I saw some flickering but havent looked into it any further till now.



edit:
a video of my tests is here: http://www.magiclantern.fm/forum/index.php?topic=12802.0

its the 3rd scene without clouds that flickers
#7
Hi,

I have been playing with dual-iso and FullRes-SilentPic for the last view days to shoot time-lapse.
Now I would like to add ETTR to the process but I have 2 problems.

#1 ETTR does not have a "fastest shutter" setting to prevent it from using values that make no sense with FullRes-SP (<1/10 or 1/30)

#2 It seems that ETTR looks always at the entire picture to set the ISO and Shutterspeed. It would be cool if ETTR could be set to only measure the darker half of the DualISO Pics to be able to shoot bright sky and very dark parts in one image with DualISO 100/1600.
#8
Hello,

I did some tests with the new FullRes SilentPic Mode (some with DualISO 100/800) ...  very nice !!!  :D