Messages

50D24fps?

Can not seem to reply to your PM.

I'm afraid I don't do video, although I do timelapse.

I proved to myself that ML does allow me to record video on the 50D, but that was it: one test video.

Sorry I can't help.

Cheers

Garry

Hi Garry23!  I was wondering if you had been successful in using the latest v2.3 of Magic Lantern to record 1080 24P video with your 50D.  If you don't do video, no worries.  But if you have experience with this particular combination of camera and frame rate (23.97 fps in progressive), please do share.

Thanks

Weldr

I can assure you that not only does ML work on the 50D, but that you will be able to things you couldn't before. My main/only use of ML is to give me full bracketing control for subsequent HDR processing. I also use the WB setting in ML.

I also have a Promote Remote to extend my bracketing. But ML allows me to leave this at home and travel light.

The bracketing in ML is also different to the Promote as ML has a killer feature: the auto bracket mode.

If you need any 50D specific help please don't hesitate to contact me.

Cheers

Garry

A1ex

I have read all the requests and I personally don't relate to them. Saving time taking brackets is important if you are handholding, ie faster the better. On my 50D I use the 3-bracket canon bracketing when handholding as I can shoot at 6fps.

As I said, I use the LV 'trick' when on a tripod and most of my shots are not moving, eg churches..

Thanks for your usual quick comments and over and out on this one, as I ave ML and LV.

cheers

Garry

A1ex.

You are right, but most of us that bracket on a tripod are not that worried about 'saving' a second or so in capture. The main thing is to get tack sharp image capture.

I am more than happy to push the LV button before and after accessing ML.

It was just an idea.

Cheers

Garry

I have been using the latest nightly build on my 50D to try out the new aperture bracketing: and I like it.

This post is about a refinement that I think is missing in ML, but could make the 'bracketeers' life a lot easier (unless I'm missing something).

When bracketing, on a tripod, the usual 'best practice' is mirror lockup, however, when I try this through the normal ML menu, with the canon MLU on or off, the MLU function seems to only work for each image. In other words the MLU is operating individually for every bracket.

The way round this is to put the camera in LV and then take the ML-enabled brackets. BTW I mostly use the auto feature now as I don't need to 'worry' about the EV range.

With the camera in LV mode, ML only operates the shutter, ie the mirror does not move, ie remaining up until LV is turned off.

So, the thought is: would it be possible to put in a feature that enables LV mode before ML takes the requested series of brackets and then takes the camera out of LV mode at the end of the sequence capture. In other words the bracketeer gets the possibility of capturing the most vibration free images.

Cheers

Garry

Dear wtspc

I have a 50D and a Promote Remote. Like you I bought the Promote to extend the camera control, especially as I am an HDR biased photographer. 

I have a very simple view of the benefit of ML vs the Promote. If you have the Promote get ML, if you have ML think carefully about getting the Promote.

The Promote will give you greater and smoother control when doing timelapses, and of course Promote is not a video controller.

I have no hesitation in saying that ML scores on bracketing for subsequent HDR processing. Why? Because you need no additional cables or hardware than your camera. You can travel light.

Additionally, ML bracketing has what I think is a killer feature: auto HDR mode. That is ML decides how many brackets to ensure the full dynamic range is captured. I usually use the auto HDR mode these days. I do not need to do any metering to decide how many brackets I need.

Bottom line: get ML in your 5D, as you are an HDR bracketeer!

Cheers

Garry

Although I don't have a 60D I can assure you that the 50D and ML works fine. I would be surprised if mirror lockup is a cause of your problems. I have been out shooting today and tend to use the auto HDR mode these days as I don't need to think about the dynamic range foe scene. I have proved the auto moe up to 17 captured images in a bracket.

Bottom line: if you are in manual mode (exposure and focus) and on a tripod you should have no issues.

 I hope it is ok to ask how are 50D users getting on with 2.3, especially bramping?

Cheers

Garry

As another 50d owner I also hae been experimenting with bramping in 2.3 and like others have come across the 'setting the right parameters' problem.

I hope someone in the know can provide some advice regarding bramp speeds. I have read elsewhere that at sunset the ev will change about 2ev per 10 min. Maybe this gives a guidance figure for speed bramp?

Bottom line looking forward to some guidance.

Ps have any of te 50d owners worked out how to move the cursor up and down the calibration curve. When I use te small wheel it does not move very far, ie I can not get it to move fully up and down te curve.

Cheers

Garry

Tried my first bulb ramping yesterday with some success. However I have a couple of questions I hope the experts can help me with.

In post I noticed that, in addition to a few iOS jumps, as expected, parts of the exposure curve show very erratic changed in exposure, ie jumps between frames. Is this an ml algorithm feature or my settings?

Also when I did the calibration step I got a nice s curve but I had difficulty moving the 'cursor' up and down the curve. I have a 50d and could only use the small wheel and then it only moved over part of the curve.  Once again does anyone have any ideas if this 'just' reflects ml or is it me!

Cheers

Garry

For Edwarda and others, here is my humble take on HDR and ML.

First let me say I have a CHDKed G11 and a S95 and, of course, a MLed D50. I can honestly say the latest ML (RC2.3) is an incredible addition to the 50D (and the other cameras ML works on). My interests are HDR and hence the addition of CHDK and ML, which allows extended bracketing, which is the cornerstone of the HDR process, takes me to a great place, where I can focus (pun) on composition and not worry about bracketing.

I would also say that ML2.3 takes bracketing to where it is now nearly a perfect in-camera process. Why do I say this, because without the ML AutoHDR feature you need to first work out the number of brackets to cover the scene. I could go with the 50D default brackets (three) and hope I capture the range. I could also measure the range (with a spot meter, say) and calculate the number of brackets and manually adjust the camera to capture additional AEB triplets. Or I could use some technology, like, Promote Remote (which I do with a spot meter, but this cost money!).

With AutoHDR in ML you can travel light (with your light travel carbon-fibre tripod) and know you will be able to capture the required number if images for the dynamics of the scene. It simply is the best thing that has happened to still photographers who can access ML.
Second, I would suggest you not 'waste time' and try to Enfuse in camera. You could, but why? It is like having a Ferrari and using it to tow a caravan. That is use ML for what it is really good at, ie to help you capture the brackets that you will later post process on your computer. With a camera in your hand (on a tripod) focus (that pun again) on capturing images, not processing images.

I do use Enfuse, also Photomatix and HDR Efex Pro. I access all these through Ligthroom 4.1. I would suggest to anyone wishing to explore HDR, first get LR4.1 running on their computer. I say this recognising the Apple folk could go the Aperture route. However, LR works better for me, as an HDR biased photographer, as it not only allows you to have a fully-in-LR  Enfuse plugin , not only does it seamlessly interface with HDR Efex Pro and Photomatix, but, and this is the clincher, it allows you to process 32-bit TIFFs. So, with Photomatix you have the ability to 'merge' your brackets into a 32-bit TIFF and post process this 32-bit TIFF in LR with all the LR capability.

Bottom line: everyone needs to find their own workflow. Mine is to use ML to capture my brackets (most of the time now using AutoHDR setting), then ingest them into LR, then carry out base corrections (eg WB, although the ML scene-based WB capability is a great help), export these brackets to Photomatix (say), create a 32-bit TIFF (that automatically gets imported into LR through a watched folder), process the HDR in Photomatix (if I want to), reimport (auto process) back into LR as a 16-bit (sic) TIFF for further post processing. In other words, using this workflow, I end up with a 16 and 32 bit TIFF file to further post process in LR.

Cheers

Garry

Alex

Thanks for the confirmation: I thought the 50D was the 'problem'.

BTW I can confirm (so far) that RC2.3 seems to have eliminated the 'hanging battery' problem on my 50D.

I also religiously follow the 'wait before taking the card out' advice.

Cheers

Garry

Using rc2.3 with great success on my 50D but I can not find how to enable or show any focus help, eg green bars or spilt screen.

Could someone point me in te right direction?

Cheers

Garry

Alex

I thought that might be the case regarding the fast access screen, however, it is still accessible in still mode: which I like. I wonder if it would be worth considering a tweak that allows access to faster shutter speeds if the user is in still mode, ie if movie mode is dsiabled. I must say I find the fast access screen useful in LV mode.

The fast access screen seems to fully work in LV still mode, even if movie mode disabled. The only 'limitation' appears to be the 1/24 shutter limitation.

In the Xmas release I was never able to see hyperfocal read out in the ML menu: now I can. Although now it does show it, I think it does not respond when the focal length of a lens is changed. This was what I saw, although in LV I saw the lens focal length. That is it appears to be a process lag.

Finally, I wonder if it's worth considering a user option to (re) position certain LV sub-screens, eg the histogram. In CHDK I can do this and I find this customisation very useful. Also, is the size of the ML histogram fixed or could there be a small, med, lartge option. Many still photograhers use the histogram a lot, especially for expose to right maximisation.

Cheers

Garry

Continue to test out the latest rc on my 50D and still looking great, eg stable and responsive.

One matter continue to 'confuse' me is the fact I can not lower the shutter speed below 1/24 from the fast access buttons, however, the shutter speed can be taken faster via the standard cannon 'wheels' even when the ml fast access screen is active.

Also what are the algorithms behind the shutter and aperture feedback color changes..

Finally, ml says can not calculate hyperfocal (I'm using a sigma lens) but the focus distance is shown by ml and clearly tracks my manual focusing changes.

Cheers

Garry

Francis

Thanks for confirming my understanding.

Garry

'zhujunsan'

Not sure I understand what you are saying. The min intervalometer increment is 100, thus I am interpreting this to mean ML will stop after 100 images and not one less. Thus, if I play it back at, say, 30 fps, I will have just over 3 secs of 'video'.

Bottom line: I think ML is telling me I can stop after 100, 200, 300 etc images.

Just uploaded my 50D firmware, downloaded RC2.3 and all looks good. Battery drain problems from previous versions of ML seems to have gone away: fingers crossed!

One thing I have noticed, although I may be missing something, is that the intervalometer shoots number can only be changed in increments of 100. Of course I may be missing a trick.

I will carry on testing on the 50D and post anything I find.

Cheers

Garry

PS I PMed Alex on this as well