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

#1
Quote from: a1ex on August 24, 2012, 02:10:00 PM
Did you get any ERR70 or similar stuff?

Sounds like you have auto power off in Canon menu.

I disabled auto power off and re-ran the Stability test and it ran for about 15 minutes. I did not notice ERR70 or any error. It ended with ":)" in the upper left. Nice.
#2
It runs for a few minutes then the camera seems to shut off. Afterwards I see some photos and movies were written to the SD card, but I am not sure if it passed or failed. Any suggestions?
#3
Quote from: a1ex on August 24, 2012, 07:54:13 AM
Or enable the console module.

Or enable CONFIG_DEBUGMSG=1 only in debug.c.

Thank you Alex. I looked in console.c, but I'm not sure what to do in there. Then I looked in debug.c and found:
//~ CONFIG_DEBUGMSG 1
//~ CONFIG_HEXDUMP 1
I uncommented the first line only and it gives the following dumps on 600D/T3i:
08/24/2012  02:30 AM         9,437,184 ROM0.BIN /* I was expecting this one */
08/24/2012  02:30 AM            65,536 BOOT0.BIN /* not sure what to do with the other two yet */
08/24/2012  02:31 AM       268,435,456 RAM4.BIN /* wow the RAM dump is big */

So now it's time to look at some dumps as I attempt to follow in the footsteps of ML developers before me. My goal is to have Focus Peak in x10 as well as x5 zoom. It is working in x5 with is_zoom_mode_no_zebras() always returning 0, but in x10 the Focus Peak is from the x5 zoom. Maybe there is a simple change to get both. I am open to suggestions.
#4
I got this from the FAQ: "You can generate the ROM images from your own camera by compiling with CONFIG_DEBUGMSG=1 and then selecting Dump ROM from Debug menu." So I made the change in Makefile.inc and built ML as follows:

make clean; make;
// I get these build errors
zebra.o: In function `card_benchmark_wr':
zebra.c:(.text+0x354c): undefined reference to `console_printf'
zebra.c:(.text+0x365c): undefined reference to `console_printf'
zebra.c:(.text+0x366c): undefined reference to `console_printf'
zebra.o: In function `card_benchmark':
zebra.c:(.text+0x36c4): undefined reference to `console_printf'
zebra.c:(.text+0x36fc): undefined reference to `console_printf'
zebra.c:(.text+0x3704): undefined reference to `console_show'
vram.o: In function `vram_toggle':
vram.c:(.text+0xf0): undefined reference to `menu_show_only_selected'
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/vtrandal/magic-lantern/platform/60D.111'
make: *** [60D] Error 2

Having been away from firmware development for a while I could use some help getting this to build. Thanks.
#5
Quote from: 1% on August 21, 2012, 05:13:05 PM
Its not focus peaking but its something.

OK. I hope I can wrap things up with regard to testing "Increase SharpContrast" and "LV contrast" on my 600D/T3i.

In neither case do I see a substantial change in contrast around edges or anywhere. If Focus Peak is enabled in red, I see blinking red dots on and around focused subjects when in Magic Lantern LiveView. And in x10 zoom the red dots go away.

I understand that while in x10 zoom and adjusting manual focus, one can say a focused subject has high contrast. I cannot argue with this, but when I am out shooting landscapes in adverse lighting conditions I would like to have the visual aid that blinking colored dots provide as in the Focus Peak feature.
#6
Quote from: a1ex on August 21, 2012, 05:32:15 PM
Focus peaking is done in livev_hiprio_task - which does not run in 5x modes.

If you comment out the call to is_zoom_mode_so_no_zebras(), all overlay tools will work in zoom mode (but this makes little sense IMO).

To get only focus peaking, you will have to let the loop run in zoom mode, but only display focus peaking (and block the others, like histograms and top/bottom bars).

Alex, this is awesome. I can't thank you enough for pointing me in the right direction here. I understand you feel this makes little sense, and I may come to feel that way too. But I want to give this a try and see how it works. Thanks!

EDIT #13: I made a quick change to is_zoom_mode_so_no_zebras() to always return 0, and I'm having fun playing with Focus Peak in x5 zoom. But in x10 zoom I'm noticing focus peaking for x5 zoom on the x10 zoom. I suppose that is somehow related to the fact that "Focus peaking is done in livev_hiprio_task - which does not run in 5x modes" as you stated above? Or am I confused? Also, in both x5/x10 zoom there's a lot of random blue and yellow dots that disappear when focus is achieved and blinking red dots appear. Any idea why?
#7
General Development / Re: OT: Sony NEX & Alpha hack
August 21, 2012, 10:16:55 PM
This is very exciting. I had the chance to use an NEX-5N this summer here in the US. I intend to keep up with your work on the a55. I hope it leads to firmware mods, add-ons, or replacements to Alpha and NEX firmware in general.

Specifically, the NEX-5N and NEX-7 are stuck with a lousy bracketing mode. Sony has said they will *never* fix this. I don't think Sony did a good marketing study. Here in the US most HDR enthusiasts find the 0.3/0.7 EV steps in Sony's "Bracket Continuous" mode too small.

I will follow the nex-hack.com link given by Malcom above to see in what fashion I might be able to help.
#8
Quote from: nanomad on August 21, 2012, 07:24:48 PM
HG pulls and update tend to revert any changes made to Makefile.inc ;)

The pull followed by the update results in opening my default editor (gvim) and showing me a visual diff summarized as follows:
-VERSION:=v2.3.RC5... /* what is was when I cloned magic-lantern on Sunday */
-VERSION:=v2.3.RC6... /* what I changed it to on Monday */
+VERSION:=v2.3.NEXT... /* what I got from doing the pull and the update last night */

This seems like a fairly standard approach for resolving potential merge conflicts. In all, 10 of 11 files were updated without conflict. And yet, my build gets broken by the pull and update.

So I think there's a problem here and I don't know what the work around is yet. Any suggestions? How do I update my magic-lantern source code when change sets become available?

In the meantime I have rolled my Ubuntu installation back prior to the point where I damaged it by doing an hg pull followed by an update.

I think I can safely say developers are not doing an hg pull followed by an hg update if that is going to mess up their magic-lantern development environment. So then, what are they doing to keep their source code in sync with the magic-lantern repository?
#9
Quote from: vtrandal on August 20, 2012, 10:34:10 AM
Thanks Francis. Next time I get my hands on a T3i I will be sure to try that.

Any additional replies should be made to this thread:
http://www.magiclantern.fm/forum/index.php?topic=2197.0
#10
Quote from: a1ex on August 21, 2012, 04:29:41 PM
Do you see the image becoming less contrasty when you hold the shutter halfway in 10x mode?

Maybe it's not working on 600D?!

Alex, I will test it on my 600D/T3i as how you describe above. But don't you mean the image becoming more contrasty when you hold the shutter halfway in x10 zoom? To me that is what "Increase SharpContrast" and "Zoom on HalfShutter" in the Prefs menu means.

1%, do you also have a 600D/T3i to test it on? Maybe we could compare results.
#11
Quote from: 1% on August 21, 2012, 07:11:15 AM
ML mostly calls functions and sets things in the firmware so that is the place to look. Not all of the camera is figured out, especially on new cameras like 600D (which has audio now).

Yes, I understand analyzing a dump is fundamental to ML development. But I am mainly interested in extending Focus Peak to work in x5/x10 zoom. To that end I have found some interesting reading here http://magiclantern.wikia.com/wiki/Focus_Assist

I haven't yet found how to get a dump and the tools for analyzing it yet. But I will keep looking.
#12
Quote from: nanomad on August 21, 2012, 09:22:31 AM
You didn't set up your compiler properly. Edit Makefile.inc

I followed the instructions here http://magiclantern.wikia.com/wiki/Build_instructions/Unified

My compiler setup was working fine until I did the pull and the update. What am I missing?
#13
Quote from: a1ex on August 21, 2012, 09:36:19 AM
On 5d2 I'm using it daily, and worked without any glitch (took thousands of pictures with it).

When you trigger 5x/10x zoom with the Zoom In button, press shutter halfway to restore normal settings (and release it to go back to high sharpness).

When you trigger the 5x/10x zoom with half-shutter, it will use high sharpness mode.

If your lens is very soft, you will probably not notice sharpening artifacts (noticed this with my 135mm lens at f/22).

I have a new 600D/T3i with the 18-55mm kit lens. I don't know if that's a soft lens or not.

That's nice that it works for you Alex, but I don't seem to have the trained eye that you or anyone else might have to see this. I need it red like in Focus Peak(ing).
#14
Quote from: adijiwa on August 21, 2012, 05:02:21 AM
Try "hg pull" first before "hg update"

Thanks. But there's some problem with the toolchain after the pull and update:
vtrandal@ubuntu:~/magic-lantern$ make clean
vtrandal@ubuntu:~/magic-lantern$ make
make -C /home/vtrandal/magic-lantern/platform/60D.111
make[1]: Entering directory `/home/vtrandal/magic-lantern/platform/60D.111'
[ CPP      ]   magiclantern.lds
/bin/sh: /home/vtrandal/arm-toolchain462/bin/arm-none-eabi-gcc-4.6.2: not found
make[1]: *** [magiclantern.lds] Error 1
make[1]: Leaving directory `/home/vtrandal/magic-lantern/platform/60D.111'
make: *** [60D] Error 2

Prior to that the "hg pull" seemed to work OK as follows:
vtrandal@ubuntu:~/magic-lantern$ hg pull
pulling from https://bitbucket.org/hudson/magic-lantern
searching for changes
adding changesets
adding manifests
adding file changes
added 246 changesets with 600 changes to 83 files (+7 heads)

And the "hg update" seemed to work OK as follows:
vtrandal@ubuntu:~/magic-lantern$ hg update
11 files updated, 0 files merged, 0 files removed, 0 files unresolved

So, I'm not at all clear on how to properly use hg and what branch, tag, or revision I should be working with.
#15
Quote from: Francis on August 21, 2012, 02:44:46 AM
Not sure how to do it with hg tools but you can go to the bitbucket page. Under downloads, scroll past all the binaries to where it lists source revisions. The 2nd or 3rd revision listed will be marked v2.3.

Thanks Francis. I might do that. But first I will try a few things with "hg" to "diff" and "update" the "unified" branch I got yesterday.

I followed http://www.magiclantern.fm/develop and used "hg clone -r unified https://bitbucket.org/hudson/magic-lantern" to get the unified branch.

So far "hg diff" works nicely. I can see my small change to Makefile.inc to tweak the VERSION from RC5 to RC6.

But "hg update" does not result in any file updates, merges, or removals. So I'm not sure which branch current work is being done on.

Would anyone happen to know the name of the branch that ML 2.3 was released under? Or a tag or something?
#16
Quote from: 1% on August 21, 2012, 02:38:30 AM
Unset the flag in 5x/10x mode? Don't know what will happen. I haven't looked at the LV stuff yet but in 3x mode all of the overlays work.

How good are you at assembly and C?

First step would be reading the wikia/getting FW dump/dissasembling.

I should add a couple things to my original post with which I started this thread:
1. My simple test photo of a street sign a block away is done with a 50mm lens on a 600D/T3i which has a 1.6 crop factor. Thus the effective focal length is 80mm. So it's still relatively small at x10 zoom and would greatly benefit from Focus Peak.
2. The street sign down the block sits atop a stop sign which exhibits considerable sharp contrast and focus artifacts at x10 zoom. This is the first time I have seen this happen and it was nice. But not all subjects I would like to focus on are going to behave this way. Thus, I still want Focus Peak in x5/x10 zoom.

As for my technical skills I think I'm still pretty good with C and assembly. I made my living for 25 years as a firmware developer. But I have not programmed much in the last few years.

Since ML is already working on the 600D/T3i (except for audio, no?) what is the purpose of getting a firmware dump and disassembling it? Would I be the first one to try to do anything in x5/x10 zoom?
#17
I'm mostly interested in landscape photography at the moment. I believe focus peaking at x5 and x10 magnification will result in better manual focus results for me. As a simple test, reading a street sign a block away is not easily done without this.

In a previous thread in the support area for early downloads Alex explained there's a global flag that blocks all LiveView overlays in x5 (and I also assume x10) modes.

So then showing peaking in x5 modes can be done? But there's a global flag that blocks all LiveView overlays in such modes. Hmmm ... Focus Peak is in the overlay menu. So then I don't understand how it can be done.

Anyway, I want to do this and I would appreciate any help or pointers that I could get as I begin experimenting with a 600D/T3i. It appears that most or all the Focus Peak feature is implemented in zebra.c file, but I really have no idea where to begin at the moment.
#18
Quote from: nanomad on August 20, 2012, 08:26:54 PM
Fixed in the latest revision

OK. How do I update my magic-lantern folder to get this fix? I'm hoping it's not necessary to clone the whole thing all over again.

And if I wanted to work with the exact source code for the ML 2.3 stable release? It seems prior to this fix v2.3.RC5 was on the tip and I guess v2.3 was released on a branch, no?

I say this because ML 2.3 stable release has Firmware Ver 1.0.2-ml-v2.3 on the 600D, but I got v2.3.RC5 when I cloned magic-lantern yesterday.
#19
Quote from: a1ex on August 20, 2012, 12:57:15 PM
The sharpness increase looks very similar to the focus peaking used on SmallHD monitors. When the subject is in focus, you will see sharpening artifacts.

I've used this trick before ML, by shooting raw and having contrast and sharpness at maximum.

Thanks Alex.

Then does LiveView on, say, the 600D/T3i LCD qualify as a Small HD monitor? Because the camera is the only equipment I will have with me when shooting landscapes. And I'm not sure why shooting raw makes a difference. I'm not in a studio where I can compare things in the middle of a shoot if that's what you mean.
#20
To get started experimenting with Magic Lantern development I went to http://www.magiclantern.fm/develop and downloaded the source code as follows:

hg clone -r unified https://bitbucket.org/hudson/magic-lantern

Since I don't have a camera at the moment I am not able to test it, but I think the firmware version in the source code is still at 2.3.RC5 because of the following grep command and it's results:

cd magic-lantern
grep -r --include=*.[ch] "v2\.3" .

./platform/5D2.212/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.5D2212";
./platform/550D.109/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.550D109";
./platform/50D.109/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.50D109";
./platform/60D.111/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.60D111";
./platform/500D.111/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.500D111";
./platform/600D.102/version.c:const char build_version[] = "v2.3.RC5.2012Aug18.600D102";

When I had a camera I seem to recall it reporting the firmware version as 2.3 without RC5 appended, but now I am a little confused.
#21
The primary reason I want to use Magic Lantern is for features that assist with manual focus like Focus Peak and Increase SharpContrast. But neither one seems to do anything in x5/x10 zoom as far as I can tell. I don't find Magic Zoom at x3 zoom useful and here's why:

As a simple manual focus test I sometimes take a photo of a street sign a block a way. In the resulting photo I can read the street sign if taken with a Sony NEX that has Focus Peaking at x10 zoom. I cannot do this with a Canon with or without Magic Lantern.

Any suggestions? Please don't say buy a Sony NEX :)
#22
Quote from: Francis on August 20, 2012, 04:59:25 AM
It is under the Display menu, LV Contrast.

Thanks Francis. Next time I get my hands on a T3i I will be sure to try that.
#23
Thanks for the reply Francis. It raises a question though. How do you turn up the contrast in LiveView?
#24
First, Magic Lantern is great. I am grateful to everyone who has contributed to it's development. Thank you!

This post is about the "Increase SharpContrast" feature in the Prefs menu that Alex pointed to me in July. Maybe I am expecting too much from this feature in that I would like it to work a lot like Focus Peak but in x5/x10 zoom.

On page 42 of the ML User Guide "Increase SharpContrast" is listed as a feature for customizing Canon's x5/x10 zoom in LiveView i.e. sharpness and contrast are maximized when zoom is active. The User Guide also says increased sharpness works somewhat like focus peaking.

So then the User Guide says it "works somewhat like focus peaking" but not exactly like it. Then what should I see? I don't think I see anything. If anyone could try it on their camera and give a reply I would greatly appreciate that.

Thank you!
#25
kihlbahkt and others,

I'm eagerly awaiting anyone else generous enough to comment on Magic Lantern manual focusing issues that I am experiencing.

In the next day or so I think I am going to go ahead and split this up into two or three separate issues after I confirm these are indeed issues that also occur with my Canon 18-55mm kit lens. I want to rule out the possibility that the m42 screw mount lenses are causing problems with Magic Lantern manual focus features mentioned in the title.

Thanks all!