Messages

You wouldn't happen to have a copy of that build would you? The furthest back I can go on the nightly builds is January of 2014

I have a copy of one from December and one from October. I'm having a whole new issue now though, and it applies to those as well as the latest, all the same - namely, none of the exposure settings are working. I can't control shutter, and I can change the numbers for aperture and ISO but they have no effect, at least not in LV.

Can someone help me understand the shutter speed values displayed on Live View? After upgrading to the most recent nightly build, (after using V2.3 with this RAW build - http://www.magiclantern.fm/forum/index.php?topic=5586.0) my shutter speed values are now confusing me.

My camera's setting, (based on the top of my camera) is on 1/50, since I shoot 23.976 and the fewer frames offer greater resolution shooting.

BUT in Live View it reads a completely different shutter speed and the Live View picture is whitewashed when shooting outdoors, (even though photographs I take with the same settings are exposed correctly). For example, the camera is set to 1/50, but in live view it will read as 1/92 (or any number it would like to). In fact, even when I adjust my aperture I've found that this number changes. I'm not certain of how my frames are being exposed. I also get confusing readings within the ML menu, like "1/92, 94°." When this value is changed within Magic Lantern, my photo settings change on the top of my camera as well. It also appears to loop around through settings when I rotate my click wheel far enough.

All in all, I would like some help in setting an accurate solid shutter speed for 23.976 fps raw video recording, and an understanding of what these units represent. Do I follow what's on my camera's top display or what ML tells me?

Regards and much thanks, ImagineFlight

This is the closest to the problem I've been having that I could find. The last build I could use on my 50d was back in December. Ever since then I've had next to no control over the shutter speed, and I get a flashing screen as if it's hopping from ISO to ISO. In the past this would happen only when I tried to change the ISO, but with the latest build it starts doing it a few seconds after I turn the camera on. If I switch off LV I can set any shutter speed, but as soon as LV is back on it goes haywire again. For me the builds just keep getting worse and worse!

Whoops, figured it out - 'disable all modules' was engaged.

Thanks, Gerardo, got it.

Now a new problem - loaded the latest build into my 5d3, clicked the modules I wanted, rebooted the camera (I assume that just means turn it off) - but the modules didn't load. They're there, with the green lights lit, saying they'll load, but they don't.

Well that's weird - I tried a different computer and the links came up.

I click http://builds.magiclantern.fm/#/ and all I get is a blank screen. Anyone else?

Oops, my bad, you're right. But dual iso is greyed out on my camera. I can manipulate the settings, but I'm not getting anything.

I see now that this has been dealt with before - but I have the latest version of cr2hdr.

Thanks, seem to have it going now. But now what's happening is I drag the dngs, and they're processed - and nothing's changed. In Adobe bridge I can still see the alternating frames at different iso's. When it's processing there's a little note for each frame as it flashes by, something like "doesn't look like interlaced iso's." So I guess it's not recognizing that the frames are different. I lowered the difference between the two iso levels, could that be doing it?

Just shot some dual iso on my 5dii, and can't get the thing to work - always get a "filename or extension too long" error signal when I drag the dngs. I have cr2hdr with the dcraw and exiftool in the same folder with the dngs.

Thanks for the tip about vision log, I'm going to try that. But I'm not sure why you'd exit AE in a compressed format. The big-ass files don't give me any issues in Premiere, so it seems to make sense to leave compression for the last step.

Thanks, that really worked. Weirdly enough the 300 mb file that results looks a bit better than the original monstrosity. What's up with that?

I've been using workflow #3, and have a question about the final step, exporting from PP. I've been going the highest quality route (avi uncompressed), and ending up with a ridiculously large file - 15 gb for 2 minutes - that won't even play back properly on my computer. Any thoughts?

I've had 2 issues with my 50d since installing the latest build. When changing the iso the lvf goes to a kind of flashing white, and as far as I can see all I can do is turn the camera off. Also, while I can record much longer clips than before at top resolution, if they're too long (over 3 gigs, I think) I get a file that won't open in raw2dng. I have to stop it at about 50 seconds. And at about 60 seconds the lvf just shuts off and that's it.

I guess that's more than two issues. But god knows I'm not complaining about getting 50-second raw clips!

No, I was not clear.  Your file naming format is wrong!

Try this:

copy/b file1.raw+file2.raw+.... filenew.raw

I changed the file names as you suggested, but I'm getting the same thing - a new file much smaller than the originals, and that won't open. (The original r00 will open, but the dngs are completely garbled.)

Update: figured it out with FSJ, thanks for your help!

Read:
RAW Video: PostProcessing -- Beginners Guide --
http://www.magiclantern.fm/forum/index.php?topic=5654.0

Your format is wrong

Thanks! I changed the formatting to exfat, but the 5d mkii doesn't seem to recognize it.

I'll change back and try the file-renaming.

Could the opening post include also commandline howto (taken from http://www.magiclantern.fm/forum/index.php?topic=5533.msg37819#msg37819 ):

Joining files
WIN
    Start dialog: cmd
    1. cd C:\Users\my_destination_folder
    2. copy /B xyz.RAW+xyz.R00+xyz.R01 xyz.RAW

OSX/LINUX
    Start Terminal
    1. cd /Volumes/my_destination_folder
    2. cat xyz.RAW xyz.R00 xyz.R01 > xyz.RAW

    Tips: cmd and Terminal support drag & drop => Don't need to type!

I do this (in Windows) on one raw and one r00 file, hence copy /B xyz.RAW+xyz.R00 xyz.RAW - that's right, isn't it? And I get one RAW file, a lot smaller than the originals, and it won't open in raw2dng. Any ideas?