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

#1
Feature Requests / Re: Panorama module?
September 17, 2014, 06:50:54 PM
Yes, maybe. But think about Gigapixel-Panorama. I don't want to make much more pictures than I need... a 10x10 pic panorama is much faster than a 20x20 pic panorama, because I tilted only 1/4 of the width and not 3/4...
#2
Feature Requests / Re: Panorama module?
September 16, 2014, 06:42:33 PM
No no, not all picture parts at all, I want only the current "neighbours" (left/top neighbour) while shooting - just to make sure, I don't move to far to get in trouble while stitching.

Hmm,, Brenizer correct - maybe we need a mode for this order of the pictures too. I never did that, but I think you shoot the middle picture with the subject first, and then go around. Correct?
#3
Feature Requests / Panorama module?
September 15, 2014, 08:02:12 PM
Hi there,

I use ML for years now, and don't want to miss the incredible features, which make the life better and easier. Intervalometer, Dual-Iso, RawVideo and Focus Peaking in Liveview... they are huge enhancements for the main camera.

I am now interested in panorama photography, and I am wondering, if "we" can use two features together, to get Panoramas done more easily. I am thinking (and I can't find a similar request, which gives me some doubts... If it was already posted, sorry) about ghost image function.

The Module has to define some parameters:
- panorama mode (line, multi-row)
- Suboption: line - left to right, right to left
- Suboption multi-row: L->R | R->L,  Up->Down | Down -> Up, Zig zag
- Overlap: 1/4, 1/3, 1/2

I start the panorama, shoot the first frame, and the camera load and display the last image as ghost image with overlap. The easiest example is single-line-panorama left to right, i select 1/3 overlap and I got the right 1/3 part of the last image on the left part of the live view screen as ghost, so I can move the new image selection to the right and take the next shot. And again the last shot is the new ghost.
On multi-row we have to have a new switch for "line feed" also, I notice now. After line-feed the function need to paint 2 ghosts, the first pic after line-feed only the lower (or upper, see option) 1/3 of the first pic, after this pic, it should show the second pic of the first line and the right part of the second line first pic. Hmm, maybe a little bit weird - but it only should help to keep the track of the height and width to get all pics done without thinking to much. ;)
This would help a lot to keep track of the current part of a really huge panorama. I often move a little bit to fast, so the overlap is to tiny for automatic stitch programs, i have to fiddle a bit to make that work.
Hmm, if I select multiple exposure (for HDR), this maybe should track only the first pic of every series.

Is this possible to paint only a part of the whole picture as ghost?

Best regards,
  David.
#4
Thank you very much!
#5
@ayshih: Thanks for your reply.
The 60D hast no AF configuration, that is one missing feature to the 50D, propably to make a bigger difference to the 7D at this time.

I use the 70-200 IS II.

I tried it again, the values in the original Canon menu are the same as in the DotTune module menu, vice versa - so this works.
I tried with -20 to 20 manual and with the option "all lenses" instead of "this lens" - this seems to be the problem. "all lens"es works fine. There might be a problem, that its a zoom lens? In the Canon menu I got two values W and T (Wide and Tele it seems), but the one value in the DotTune module seems to stores to both settings (propably ok), but I again get these problems, that I even get at -100 and +100 a focus indication.
Anyway, no matter... I can use the "all lens" option and remember the values at 70mm and 200mm (and other lenses) and can store these manually with the original Canon menu. It is a big hit.... but "unfortunately" my 70-200 after the test want to set a "0" value - and this seems ok - because this lens IS very sharp - i never had problems with it. ;-)
#6
Yesterday I updated ML to magiclantern-v2.3.NEXT.2014Jan15.5D3113 on 5D3 - earlier i used an September20-build with dualiso and rawvideo - and it works perfectly for me.
Then I want to test the DotTune-module - I never tried this (except with the old September and now this version).

I use a tripod, a tele lens (small DOF) on 3m distance to a picture frame on the wall, use Liveview for focus, set the lense to MF and go into the menu.
The iteration works, but it seems that ML can't set the calibration value into the register - he try between -100 and +100, and its always in focus (dot/red light in VF). If I manually set different values into the original canon menu - it works, and I get at -12 and 15 or so no focus indication - so my lens is ok, and this kind of test works - but not with the ML iteration automatic. It searchs and later there is an error message, that I should double check, if it is in focus. I event tried several lenses.
Am I too stupid, is something broken (and I don't find it), or ..?

Thanks again.
#7
DualIso works well on 5D3, thank you for this feature! With the first tests the detail loss of structures was a little bit to much, but with newer converters it is much better. But the shadow recovery works very very good.

But I have a little "other" request. I install the ML-version from the dropbox onto the CF-Card (not SD), and it's working good. Yesterday I want to format the CF, because of 300+ pics, and the format menu cleans the whole card, with ML. Grrr, I had to copy it again with the card reader.

With the ML-version of my 60D I know the "feature", which reads the whole ML-directory (and autoexec) into the RAM, formats the card, and rewrite ML back to the card. Is this feature broken or is it deactivated on purpose?
#8
Raw Video / Re: 60D RAW video - it's working !!!
June 16, 2013, 03:37:58 PM
I like the Image from June/8th very much, I am very busy doing several tests, so I didn't switch the image to a newer one yet.
I do in the last days "only" timelapse with fps override (1fps) - and I love it! So I don't have any problems regarding writing speed.
But sometimes the capture breaks, and the camera didnt responde until I get out the battery. So there are some minor issues with stability I think.
In the next days we expect here thunderstorms and I will try the "new" bolt rec feature, If it is possible to do something great.
My best shot of last year doing the good ol' way of 15-30sek shutter time gave me this result:
http://www.flickr.com/photos/davidcl0nel/8543588975/
Maybe there is something more possible. ;-)


Now I got a 2000 frame sequence (30min), and got over the 4GB "barrier", so it seems to be no problem. But it seems to don't react to time changes (in manual mode) from 1/1600 to 1/2000 after start.
On "normal" video with fps override I can raise the exposing time without a problem.


Anyway, well done, and I will see, what the good ol'd 60D is capable of in the next weeks. ;-)


Edit: Nope, it runs out yet, I got a 4.194.304kb size RAW file and a 3.151.146kb r00 file. The size on the display while recording seems to be the added size (7G), while it ends after 4GB and didn't restart automatically regardless of the restart option, which was set. Never mind, I will check now the results. ;-)
#9
Raw Video / Re: 60D RAW video - it's working !!!
May 29, 2013, 10:06:27 PM
My compile chain also finally working now and I got also the full image (as in nightly build) without module support. (which is ~3mb for all cameras)
If I try to activate module support (and dependencies), I got a 3.5mb autoexec, but it crashs on start with null pointer. Is this image to big, oder is something else broken then?
Your image has the module support, but nothing else. Do you deactivate all features in features.h? Some lower features as silent pictures or such things - some features are really not very important.

Is there a way of combination both ways in one image?
#10
Raw Video / Re: 60D RAW video - it's working !!!
May 27, 2013, 11:35:42 PM
I'm stuck with my own ARM cross compiler toolchain yet (EABI version mismatch with own arm-toolchain, and with precompiled arm he couldn't find, even the path is absolutely correct - tomorrow....)...
So I've tried your build a few minutes ago! My main goal is only timelapse (1fps or less), so I don't care about writing speed. My first attempt with 1720x1146 @ 0.5fps worked fine. Thanks!
Other interesting feature would be silent picture (for timelapse), but it isn't included in your build, am I correct?