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

Pages: 1 [2] 3 4 5
26
Hello folks,
here is my newbie question.
I use Ml only for photography.  When I start a Hdr sequence with the HD bracketing function of Ml,  sometimes I need a exposure from more than 30 seconds for the first shot. But the exposure measurement seems limited to 30 seconds for the first shot of the sequence even with Ml. I thought that ML can make an override on my 5D Mark III with Firmware 1.2.3. so that I can use exposure metering over 30 seconds.
I am using the ML nightly build from 01.07.2014. The camera is set to M mode.
Maybe I am just missing something or doing it wrong?
I haven't tried it, but I think bulb mode should work (use ML bulb timer along with it)

27
Share Your Photos / Re: Thread photos dual iso
« on: July 04, 2014, 01:11:46 AM »
I spent a lot of time removing hot pixels from these...and they were only 10s exposures. I've tried 30s, and there are just tons of hot pixels, but if you have the time to remove them, you can get some great stuff.







(Yes, that's me, I'm a small guy)

28
Share Your Photos / Re: Thread photos dual iso
« on: May 20, 2014, 03:46:31 PM »
Not sure if this is a good candidate for Dual ISO, but I went for it anyway


29
General Help Q&A / Re: Playback Dual ISO Images
« on: January 23, 2014, 04:00:30 PM »
I'll just wait till it gets fixed in the official nightlies; I'm a bit lazy to go and compile myself now. Unless dual_iso.c is supposed to be found on my camera, in which case I don't have it.

I'm more interested in keeping up with the developments with the current investigation on ISO, even though I don't understand most of the technical parts of it.

30
General Help Q&A / Re: Playback Dual ISO Images
« on: January 23, 2014, 12:18:53 PM »
My picture style sharpness is already 0 though.

As I said before, the issue is not there when I zoom in (or out, for that matter). But at the default image preview/playback size (fullscreen image), the image will display perfectly for about half a second before becoming blurry. That happens when the box at the top left corner of the screen pops out, showing either "dark" or "bright"

31
General Help Q&A / Playback Dual ISO Images
« on: January 23, 2014, 11:59:46 AM »
Hi,

I'm not sure if this is a bug or if it's caused by a certain setting, but whenever I view a dual ISO image in playback mode, the image is just a blurry mess. It goes back to normal if I zoom in, but at the normal playback size, the image will first appear normal for about half a second (apart from the bars of alternate ISOs), then become a blurry mess (a small black box with containing either "dark" or "bright" shows up as well, and I assume it's showing which parts would be used from the dark and bright areas respectively - or something like that). Sometimes I am able to see the dual ISO images normally (without the blurring effect), but I cannot reproduce that outcome.

How do I view the dual ISO images "normally"? I don't mind having the bars of alternate ISOs, but having the blurry images makes previewing the images almost useless. Since I do see the non-blurry preview for half a second + the image isn't blurry if I zoom in, there has to be a way that the preview can stay non-blurry, right?

32
Duplicate Questions / Re: Double Exposure?
« on: January 08, 2014, 02:02:51 AM »
You can preview it in the camera (SET+MainDial: Exposure Fusion).
Exposure fusion preview uses enfuse right? Does enfuse combine long exposures well? I personally haven't tried it and I haven't seen many people recommending enfuse for stacking (for long exposure purposes - I have only seen people use it for focus stacking). The tutorials I've seen suggested using GIMP/Photoshop to stack through layers or using Photoshop's image stacking features, or using ImageMagick as described here: http://blog.patdavid.net/2013/09/faking-nd-filter-for-long-exposure.html

If enfuse does it, then the preview would be useful; otherwise it will produce a preview that is different, which is not very useful.

33
Duplicate Questions / Re: Double Exposure?
« on: January 02, 2014, 03:03:59 AM »
There is another purpose for this: long exposures with little noise. Or extend a long exposure to an ultra long one (can use just a 10 stop ND to achieve a ~4 or 5 min exposure in bright daylight rather than stacking NDs)

Basically shoot multiple long (or long enough) exposures (each image will be the correct exposure, unlike in astrophotography) and combine them into a single long exposure image. Combining the images/averaging them takes away the noise and also adds the motion from each long exposure.

In post, you would open all the images up as layers, then each layer would be (100/x)% opacity, so bottom layer will be 100%, second from bottom would be 50%, third from bottom would be 33% and so on. Tedious in post without some form of automation. With Photoshop I think there are image stacking tools, but in GIMP, you probably have to write your own script which I don't know how to.

Either way, the advantage of having this in-camera is that you can preview the final result, rather than waiting for you to get home to combine in post. If the results are not satisfactory, you can at least shoot another set of pictures, but if you do it in post, it's guesswork as to what the final image would look like.

34
Feature Requests / Re: Extension of the Expo Presets Function
« on: December 31, 2013, 02:16:01 AM »
In this situation, I would use Auto ETTR in Auto Snap mode. For 10 stops it will require most likely 2 test pictures, but I'm experimenting with a theory that would allow much better accuracy for metering in complete darkness.

Exposure offset is not well defined, because you have 3 exposure variables. Look in the bracketing menu.
Interesting idea, though it would still be slow, especially considering metering in almost complete darkness coupled with very long exposure times.

I was also thinking of baking this 10 stop adjustment into the "Arrow/SET shortcuts" function. Shutter speed can already be adjusted in this way, but only in fine stops. If we could configure the number of stops to change, it could work.

But I quite like your idea of using bracketing as a workaround. I'll try it when I feel well enough (I'm still recovering from a surgery)

35
Feature Requests / Extension of the Expo Presets Function
« on: December 29, 2013, 05:14:46 AM »
Hi, I like to do a lot of long exposures with an ND filter, specifically a 10 stop one. The expo preset function is pretty useful, but I think its functionality can be extended by providing an option to use it to offset exposure rather than storing two exposure presets. The reason is that when shooting with a 10 stop ND filter, you spend a lot of time just spinning the dial to get the exposure to change by 10 stops. If you stack ND filters, it's even worse, and you spend a lot of time just changing exposure between shots.

So a simple function could be added to the expo presets to make it just offset the exposure by a fixed number of stops. Press it once and it increases exposure time by a fixed number of stops, press again and it decreases it back to the original exposure time. Or something similar.

36
General Help Q&A / Re: Memory Error - Anything to worry about?
« on: September 23, 2013, 03:18:44 PM »
Solved, at least on 60D. Nightly builds are being recompiled right now.
Thanks, I just installed the latest one and the error is gone

37
General Help Q&A / Memory Error - Anything to worry about?
« on: September 23, 2013, 10:45:24 AM »
Recently after installing the nightly build (the 22 Sep one) for my 60D, I saw a "Memory error" under my debug menu. It says Last error: 4 at libtcc.c:222, task module_task

Should I be worrying?

38
Share Your Photos / Re: Thread photos dual iso
« on: September 20, 2013, 03:57:44 PM »
Here's mine. It's my first time doing a night shot, though I've done sunsets before.

F6.3, 8s, ISO 100/1600 on the 60D


Untitled by |Panzer|, on Flickr

39
General Development / Re: Quick Guide and Solutions for VirtualBox
« on: September 20, 2013, 03:42:50 PM »
What gcc version?
I'm using 4.7.3

40
General Development / Re: Quick Guide and Solutions for VirtualBox
« on: September 20, 2013, 11:38:49 AM »
And where's the error?!
afaik it used to show CC instead of RM? I'm not sure. Either way, if I just ignore and continue, I still get this when I do "make 60D"
Code: [Select]
magiclantern@magiclantern-VirtualBox:~/magic-lantern$ make 60D
make -C  /home/magiclantern/magic-lantern/platform/60D.111
make[1]: Entering directory `/home/magiclantern/magic-lantern/platform/60D.111'
[ VERSION  ]   ../../platform/60D.111/version.bin
~/arm-toolchain/bin/arm-none-eabi-gcc-4.7.3    -c -o ../../src/entry.o ../../src/entry.S
[ AS       ]   ../../platform/60D.111/stubs.o
[ VERSION  ]   ../../platform/60D.111/version.c
[ CC       ]   version.o
[ CC       ]   boot-hack.o
../../src/boot-hack.c:51:16: warning: '_reloc' defined but not used [-Wunused-variable]
[ CC       ]   mem.o
[ CC       ]   ico.o
[ CC       ]   edmac.o
[ CC       ]   menu.o
[ CC       ]   debug.o
[ CC       ]   cfn.o
[ CC       ]   gui.o
[ CC       ]   picstyle-noauto.o
[ CC       ]   exmem.o
[ CC       ]   bmp.o
[ CC       ]   rbf_font.o
[ CC       ]   config.o
[ CC       ]   stdio.o
[ CC       ]   bitrate.o
../../src/bitrate.c: In function 'time_indicator_show':
../../src/bitrate.c:376:61: warning: signed and unsigned type in conditional expression [-Wsign-compare]
[ CC       ]   lcdsensor.o
[ CC       ]   tweaks.o
../../src/tweaks.c:3643:21: warning: initialization discards 'volatile' qualifier from pointer target type [enabled by default]
[ CC       ]   lens.o
[ CC       ]   property.o
[ CC       ]   propvalues.o
[ CC       ]   gui-common.o
[ CC       ]   chdk-gui_draw.o
[ CC       ]   movtweaks.o
[ CC       ]   menuhelp.o
[ MENU IDX ]   ../../src/menuindexentries.h

No menuindex.txt! The "Complete user guide" menu is empty!
Run make docq to update menuindex.txt.

[ CC       ]   menuindex.o
[ CC       ]   af_patterns.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   bootflags.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
../../src/vram.c: In function 'vram_redirect_lv_buffer':
../../src/vram.c:581:35: warning: assignment makes integer from pointer without a cast [enabled by default]
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   shoot.o
../../src/shoot.c:464:60: warning: initialization makes pointer from integer without a cast [enabled by default]
../../src/shoot.c:464:1: error: initializer element is not constant
../../src/shoot.c:466:53: warning: initialization makes pointer from integer without a cast [enabled by default]
../../src/shoot.c:466:1: error: initializer element is not constant
make[1]: *** [shoot.o] Error 1
make[1]: Leaving directory `/home/magiclantern/magic-lantern/platform/60D.111'
make: *** [60D] Error 2

After which if I try to "make clean" and "make" any module, it gives me
Code: [Select]
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/autoexpo$ make clean
[ RM ]  autoexpo.o autoexpo.mo autoexpo.sym autoexpo.dep module_strings.h *.o *.d *.bmp *.dep *.sym hgstamp
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/autoexpo$ make
[ README   ]   module_strings.h
[ CC       ]   autoexpo.o
[ MODULE   ]   autoexpo.mo
[ STRIP    ]   autoexpo.mo
[ EXPORTS  ]   autoexpo.sym
[ DEPENDS  ]   autoexpo.dep
Not checked (compile ML for these cameras first):
    100D, 1100D, 40D, 500D, 50D, 550D, 5D2, 5D3, 5DC, 600D, 60D, 650D, 6D, 700D, 7D, EOSM
make: *** [autoexpo.dep] Error 1

41
General Development / Re: Quick Guide and Solutions for VirtualBox
« on: September 20, 2013, 11:22:12 AM »
When I do a "make clean" (after hg update), I get this garbage

Code: [Select]
magiclantern@magiclantern-VirtualBox:~/magic-lantern$ make clean
make -C platform clean
make[1]: Entering directory `/home/magiclantern/magic-lantern/platform'
make -C all clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/all'
[ RM ]  autoexec-all autoexec-all.bin
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/all'
make -C  ../platform/40D.111 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/40D.111'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/40D.111'
make -C  ../platform/50D.109 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/50D.109'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/50D.109'
make -C  ../platform/5D2.212 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/5D2.212'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/5D2.212'
make -C  ../platform/5DC.111 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/5DC.111'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/5DC.111'
make -C  ../platform/60D.111 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/60D.111'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/60D.111'
make -C  ../platform/7D.203 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/7D.203'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/7D.203'
make -C  ../platform/1100D.105 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/1100D.105'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/1100D.105'
make -C  ../platform/500D.111 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/500D.111'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/500D.111'
make -C  ../platform/550D.109 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/550D.109'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/550D.109'
make -C  ../platform/5D3.113 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/5D3.113'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/5D3.113'
make -C  ../platform/600D.102 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/600D.102'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/600D.102'
make -C  ../platform/650D.104 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/650D.104'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/650D.104'
make -C  ../platform/6D.113 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/6D.113'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/6D.113'
make -C  ../platform/7D_MASTER.203 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/7D_MASTER.203'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/7D_MASTER.203'
make -C  ../platform/EOSM.106 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/EOSM.106'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/EOSM.106'
make -C  ../platform/700D.111 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/700D.111'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/700D.111'
make -C  ../platform/100D.100 clean
make[2]: Entering directory `/home/magiclantern/magic-lantern/platform/100D.100'
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
make[2]: Leaving directory `/home/magiclantern/magic-lantern/platform/100D.100'
make[1]: Leaving directory `/home/magiclantern/magic-lantern/platform'
[ RM dir ]  doxygen-doc
[ RM ]  magiclantern.lds /home/magiclantern/magic-lantern/lua/*.o /home/magiclantern/magic-lantern/lua/.*.d /home/magiclantern/magic-lantern/lua/liblua.a doc/Cropmarks550D.png doc/credits.tex doc/install-body.tex doc/install.wiki doc/menuindex.txt src/menuindexentries.h doc/userguide.rst doc/INSTALL.aux doc/INSTALL.log doc/INSTALL.out doc/INSTALL.pdf doc/INSTALL.rst doc/INSTALL.tex doc/INSTALL.toc doc/UserGuide-cam.aux doc/UserGuide-cam.log doc/UserGuide-cam.out doc/UserGuide-cam.pdf doc/UserGuide-cam.tex doc/UserGuide.aux doc/UserGuide.log doc/UserGuide.out doc/UserGuide.pdf doc/UserGuide.tex doc/UserGuide.toc *.pdf platform/*/qemu-helper.bin
[ RM dir ]  doc/cam
[ RM dir ]  binaries

I've also tried "make all clean", but I get another bunch of errors
Code: [Select]
magiclantern@magiclantern-VirtualBox:~/magic-lantern$ make all clean
make -C  /home/magiclantern/magic-lantern/platform/60D.111
make[1]: Entering directory `/home/magiclantern/magic-lantern/platform/60D.111'
[ VERSION  ]   ../../platform/60D.111/version.bin
[ CPP      ]   magiclantern.lds
[ AS       ]   ../../platform/60D.111/stubs.o
[ VERSION  ]   ../../platform/60D.111/version.c
[ CC       ]   version.o
[ CC       ]   boot-hack.o
../../src/boot-hack.c:51:16: warning: '_reloc' defined but not used [-Wunused-variable]
[ CC       ]   mem.o
[ CC       ]   ico.o
[ CC       ]   edmac.o
[ CC       ]   menu.o
[ CC       ]   debug.o
[ CC       ]   cfn.o
[ CC       ]   gui.o
[ CC       ]   picstyle-noauto.o
[ CC       ]   exmem.o
[ CC       ]   bmp.o
[ CC       ]   rbf_font.o
[ CC       ]   config.o
[ CC       ]   stdio.o
[ CC       ]   bitrate.o
../../src/bitrate.c: In function 'time_indicator_show':
../../src/bitrate.c:376:61: warning: signed and unsigned type in conditional expression [-Wsign-compare]
[ CC       ]   lcdsensor.o
[ CC       ]   tweaks.o
../../src/tweaks.c:3643:21: warning: initialization discards 'volatile' qualifier from pointer target type [enabled by default]
[ CC       ]   lens.o
[ CC       ]   property.o
[ CC       ]   propvalues.o
[ CC       ]   gui-common.o
[ CC       ]   chdk-gui_draw.o
[ CC       ]   movtweaks.o
[ CC       ]   menuhelp.o
[ MENU IDX ]   ../../src/menuindexentries.h

No menuindex.txt! The "Complete user guide" menu is empty!
Run make docq to update menuindex.txt.

[ CC       ]   menuindex.o
[ CC       ]   af_patterns.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   bootflags.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
../../src/vram.c: In function 'vram_redirect_lv_buffer':
../../src/vram.c:581:35: warning: assignment makes integer from pointer without a cast [enabled by default]
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   shoot.o
../../src/shoot.c:464:60: warning: initialization makes pointer from integer without a cast [enabled by default]
../../src/shoot.c:464:1: error: initializer element is not constant
../../src/shoot.c:466:53: warning: initialization makes pointer from integer without a cast [enabled by default]
../../src/shoot.c:466:1: error: initializer element is not constant
make[1]: *** [shoot.o] Error 1
make[1]: Leaving directory `/home/magiclantern/magic-lantern/platform/60D.111'
make: *** [60D] Error 2

What am I doing wrong? I didn't have this problem previously (like a 1 or 2 months back), but now whenever I try to compile, it doesn't work.

42
How could you use it? You compiled it yourself? I just don't understand why the author can't compile the thing and give a download link.
Yes I compiled it after he fixed the code. He said there was a typo which caused the errors we were facing while compiling. It depends on a few changes so I just cloned his entire source to build rather than trying to clone the main ML source and patching in his stuff. I don't pretend to know how to do that, so I just do it the easy way  :)

43
Have you used it before?
yes I've used it, and it works pretty well. However I have not had a chance to use it in a real world situation, I only did a short test at home

44
Im struggling to understand what brapodam is meaning to be honest (not in a nasty way at all) to me it sounds like you are wanting to work like either Tv or AV mode which i would recommend using for the quickness you are after and shoot in RAW, Auto exposure to me is a advanced Auto feature with manual adjustments. But like i say, i may not be understanding your post correctly so im sorry in advance if i am reading it wrong  :)
What I was suggesting is to have a quick way to adjust the maximum aperture to suit one's DOF needs. DOF requirements can change from shot to shot (for instance when shooting events where you may want shallow DOF to isolate subjects, but a larger DOF for group shots), and right now it's not easy to do that quickly - you have to dive into menus.

However, I do recognise that this may not be the point of this module - the Auto ISO module by Marsu42, used in Aperture Priority mode may better achieve this requirement.

45
What you are saying is what you ca do.. if for instance you want to do a group shot and you dont want 2.8 set the AV to from 5.6 to 16 for instance? This is quite a complex module.
Yes, but there's no fast way of doing it. If you can, say, control that setting with the rear dial, it would be significantly faster

46
General Development / Re: Need help merging code, etc.
« on: July 28, 2013, 07:14:29 AM »
1) Does my source need to match my camera's source version of ML?
2) I got one module to make but for its counterpart, it gave me an error. This is what happened:

Code: [Select]
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/m42_aiso$ make
[ CC       ]   m42_aiso.o
m42_aiso.c: In function 'm42_aiso_shoot_task_cbr':
m42_aiso.c:64:30: error: 'shooting_mode_c' undeclared (first use in this function)
m42_aiso.c:64:30: note: each undeclared identifier is reported only once for each function it appears in
m42_aiso.c: At top level:
m42_aiso.c:162:17: warning: initialized field overwritten [-Woverride-init]
m42_aiso.c:162:17: warning: (near initialization for '(anonymous)[2].help2') [-Woverride-init]
m42_aiso.c:217:1: error: expected identifier or '(' before '{' token
m42_aiso.c:217:1: error: expected identifier or '(' before '}' token
m42_aiso.c: In function 'm42_aiso_shoot_task_cbr':
m42_aiso.c:125:1: warning: control reaches end of non-void function [-Wreturn-type]
make: *** [m42_aiso.o] Error 1
magiclantern@magiclantern-VirtualBox:~/magic-lantern/modules/m42_aiso$
Got the same error. I've got the other modules to make but m42_aiso always has a problem.

EDIT: Oh actually the errors I get are slightly different.

If I pull the main ML source and download the Makefile and m42_aiso.c files, I get the following when trying to make the auto iso module:
Quote
[ CC       ]   m42_aiso.o
m42_aiso.c: In function 'm42_aiso_shoot_task_cbr':
m42_aiso.c:60:30: error: 'shooting_mode_c' undeclared (first use in this function)
m42_aiso.c:60:30: note: each undeclared identifier is reported only once for each function it appears in
m42_aiso.c:84:26: error: expected ',' or ';' before numeric constant
m42_aiso.c:88:19: error: 'e4' undeclared (first use in this function)
m42_aiso.c:90:23: error: expected ')' before 'er'
m42_aiso.c:90:23: error: expected ')' before 'er'
m42_aiso.c:90:23: error: expected ')' before 'er'
m42_aiso.c:91:42: error: 'ref_tv4' undeclared (first use in this function)
m42_aiso.c:87:13: warning: unused variable 'e' [-Wunused-variable]
m42_aiso.c:99:47: error: expected ',' or ';' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:102:22: error: expected ')' before numeric constant
m42_aiso.c:108:23: error: expected ')' before 'er'
m42_aiso.c:108:23: error: expected ')' before 'er'
m42_aiso.c:108:23: error: expected ')' before 'er'
m42_aiso.c:109:43: error: 'ref_av4' undeclared (first use in this function)
m42_aiso.c:104:13: warning: unused variable 'e' [-Wunused-variable]
m42_aiso.c:117:1: warning: control reaches end of non-void function [-Wreturn-type]
make: *** [m42_aiso.o] Error 1

If I pull the whole source from Marsu42's branch, I get the following instead:
Quote
[ CC       ]   m42_aiso.o
m42_aiso.c:162:17: warning: initialized field overwritten [-Woverride-init]
m42_aiso.c:162:17: warning: (near initialization for '(anonymous)[2].help2') [-Woverride-init]
m42_aiso.c:217:1: error: expected identifier or '(' before '{' token
m42_aiso.c:217:1: error: expected identifier or '(' before '}' token
m42_aiso.c: In function 'm42_aiso_shoot_task_cbr':
m42_aiso.c:125:1: warning: control reaches end of non-void function [-Wreturn-type]
make: *** [m42_aiso.o] Error 1

47
Set ISO to a manual number say 100 as you would normal, also see if auto ISO is on, if so do the first part this post, i know what your meaning as i had this problem, i think i had auto iso on, if auto iso dosnt make a difference then im not sure,
I don't have ML auto ISO module though, and I didn't set ISO to auto from Canon menu.

Anyway, is there any way to use this as an aperture priority with auto ISO? There are many times where setting the aperture you want is more important than using the lowest ISO possible. For instance, in an indoor event where, say, you use a 24-70 f2.8 or 17-50 f2.8. You want to set the max aperture to 2.8 (or leave it at the default 1.4) to shoot normal shots, but for group shots, you don't want to use f2.8, and instead something like f5.6. If you dial in f5.6, the module just meters and sets it back to f2.8

Maybe a "link to canon shutter" like the auto ettr min. shutter speed setting can be implemented (except in this case, link the Canon aperture setting to max aperture)?

48
General Help Q&A / Re: SD card wiped, camera won't work :(
« on: July 28, 2013, 03:12:44 AM »
I don't know how to fix your problem, but I recommend that in future, use a SD card reader instead of connecting the camera to the computer

49
please please, read the whole help guide in the first post
this hack has configurable ISO curve, you can exatly set how the ISO will be increased
spend some time by reading some help
and default values fits to 5D2, which is fullframe
As I said, the problem is with me not fully understanding how the thing works, and not your code. I've already read the first post already but I still do not fully understand how this should work, though I have a better idea after playing around with it for a while.

50
I think it works really nice on 60D.
Ditto on that. However I still need to spend some time with it first to understand how it works. I initially thought that you could just leave the minimum ISO at 100 and forget about it and just tweak the aperture range, max ISO and minimum shutter speed. I found that it was not the case, and that I had to increase the minimum ISO in low light situations before it would select a higher ISO for proper exposure, regardless of my max ISO setting. (Or am I doing it wrong?)

Pages: 1 [2] 3 4 5