Messages

I confirm, with the newest version the glitches are less (not completely gone btw).
Another thing i've noticed (not related to the version i think) is that if i change the whitebalance from say "auto" to something else, there is'nt no more the voice "auto" in the ML menu. The only way to return in auto whitebalance is to do it in canon standard menu.
not shure if this happens in all the versions of ML or only with the 6d version, tomorrow i will try a comparison of features with 60d and 6d. btw thank you for your great development

Hi developers,
the subject already is quite self explanatory. Sometimes, when you shoot consecutive frame, for example in a stop motion animation or in an hyperlapse (timelapse with camera movements too), could be useful to see in overlay the last frame shooted, to alignment purposes. i don't know if it's already imagined before or not, or if it's possible to do it or not, i can imagine that could be difficult/impossible for ML to know the last image taken. but if it's possible should be very interesting some times

what i wrote before is not completely true. Looking better, i have that rendering problem also when i'm not in a submenu, but when i'm simply over every voice of the main menu (the blu bg on the active line). But the glitches are very rare, only sometimes i see a little black line breaking the pure blu bg of the line selected. When i open the submenu the rendering issue is more evident, and seems that when i close the busmenu the problems stay more strong for a while and then calm down (but never disappear completely)
it's difficult to explain better the problem, don't know if is only on mine 6d or not...

Hi,
i'm trying the new bin, and seems to have some "graphical glitches" in the interface. All is ok when normal navigating the menu, but when i open up a submenu (with q or with set or with other buttons) there are some strange graphical glitches, changing in time. Here is a screenshot of what i mean, can you see that lines? they are not still, but moving at a framerate something like 2 fps. All the other older versions of bin is ok here, so this glitches are related to pickbox version. And just for information, the lines are always inside the submenu box, and always of the same color of the bg of that box



hope it helps

Agree with all the people thank you for give us the chance to test ML on 6d, i'm amazed to have ML again. hope to do another donation soon guys, you really deserve all our gatitude and help )

great work

Hi Vlad,
The quick answare is this example: it's like for the stills images. In the images you can have a .jpg (compressed) or you can have a .bmp (uncompressed) or you can have a .cr2 (raw).
For the video is the same.
compressed, uncompressed and raw, where raw is not only the video uncompressed, but a lot of other datas directly from the sensor. I mean, for shure more bit depth, and a lot of other information. Actually (if i remember well) in the canon lineup only the c500 can shoot raw: http://cinemaeos.usa.canon.com/products.php?type=Camera-c500

Hey 1%,
i'm absolutely amazed by your fast progress, and i'm following with a lot of interest all your posts about 6d developing, keep the good work, i'm your fan ))

canon 60d, andjust buyed my first full frame, 6d. but without ML it's "just a camera" )

wowowow, i'm superhappy.. i was planning to buy it... now i have another reason to do it
great work!!

 

wow, looks very promising

hi, yes, the feature you are searching for is bulb ramping. and about the f22, for timelapses (especially with night timelapses) the best approach is to shot wide open, and there's 2 main reasons for that. the first is that the final video is in a much lower resolution of the original shots, so the gain in details closing the lens is irrilevant. the second is that wider apertures means no sensor dust spots (more evident in timelapses than in photos because they stay still when the rest is moving). but of course it depends on what is the lens you are using

Yes, here is much longer than 5 sec too, if i remember well was 12seconds. Do you think it's too much? do you suggest to use less time between shots?

Hi all,
just s short timelapse, part of a huge amount of timelapses i'm doing in dolomites these days. i have only one week to shot, so i have a lot of raw material to process when i will be back in rome. This is only a little preview.
The timelapse was done using magic lantern of course, and the postpro was done in lightroom, with the help of LRTimelapse for keyframing and for deflickering.
enjoy

Inspired by how the computer keyboard works, or how the tv interfaces or the volume keys of mp3 players, would be great to have a keystroke repeater after say 2 seconds it's pressed.
an example is when you have to set a value that can go from 0 to 100 in 1 steps (like focus ramping one). If you want to go to 100 now you must press the set key 100 times. but with this feature you should press only once and then stay pressed for 2 seconds. After that the values should start increasing. the best for usability should be a progressive speed boost. so it starts slow, and end up very fast

what do you think?

agree with Alex,
9 exposures handheld make not so much sense

the basic workflow written by Schloime is perfect. And should give you nice and natural results. And using automatic hdr in magic lantern correctly assures you that you have all the dynamic range you will need.
anyway should help us to see your results, and what you don't like of it

this reminds me a thing that i thought some days ago. that when you hide a feature, it should automatically deactivate himself.
logically speaking is strange to have a function working when it's hidden, anyway not a big deal, just a matter of "user friendly" approach. and could be interesting to have an icon, or a sign, something that says that in that page you have something hidden (so if you forgot it you can see visually that there's something hidden in that place). Of course should be something very small and non invasive

+1

Hi Hugo,
and welcome in the forum of magic lantern. And as already said in private, great work here, explains well the power of the combination of magic lantern and LRTimelapse, well done

Luca

Hi StevenKucharski, and welcome.
I think you are speaking about the original firmware 1.0.1, and the version of magic lantern should be the 2.2, right?
if so, first i suggest to make a donation for downloading the 2.3 wich is a great improvement.
Anyway the 2.2 has the time-lapse functions, and it's called intervalometer.
Here you can find more info (related to the 2.3 of magic lantern): http://wiki.magiclantern.fm/userguide#intervalometer

This is really interesting!! unfortunately i'm a windows user without developing skills :\ whould be fantastic to have a windows compiled version!!
hope that Alia5 will have success and will want to share the compiled win version
anyway the results are pretty impressive

beautiful

Agree with gingertronMk1,
i'm hoping that canon will deliver soon another eosm, with more pro features (like some more dials, things like this)

hey sd, pretty interesting video
you remade the autovelox