Messages

The printed time *is* the saving time, not the capture time, which is why there is variation.  I don't offhand know whether anyone has measured the rolling shutter time for the 650D (such as 5D2/5D3/6D/500D, 60D, and 50D), but it's probably ~0.3 ms.  The rolling shutter means that, not matter how fast a shutter speed you select, there will be a gradient of exposure from top to bottom, and the bottom of your frame will always be exposed at least ~0.3 ms.

[mlv_play]

This module just got a bunch of improvements, and they're in tonight's nightly builds.  See the text of the now-merged pull request for details.  Enjoy!

For fans of "exact" playback, there's a performance boost when playing back long MLV videos.  However, to achieve this boost, the index files (*.IDX) that are generated by mlv_play now have additional information embedded in them.  The consequence is that IDX files created prior to tonight's update will actually inhibit "exact" playback from working properly because the module isn't told which frames are okay to drop.  The remedy: simply delete any existing IDX files and let the module re-create them.

It sounds like a promising approach!

I'm interested in helping, but it'd be nice if there was a way for it to work on Windows.  Unfortunately, it looks like the only actively developed implementation may be DokanX (https://github.com/BenjaminKim/dokanx/), and I don't think it uses the FUSE API.  (See the list of relevant projects on this Wikipedia page.)  But, I do have an OS X machine and Linux VMs, so it's not an non-starter.

I've only started reading up on this stuff, but I'll point out that OSXFUSE says that it provides an API that is a superset of the FUSE API, so you may want to make sure you're using just the FUSE API to ensure Linux portability.  Of course, at such an early stage, that's a very low-priority concern.

@ItsMeLenny
It sounds like he doesn't see this behavior with the a non-ML card, so it's not likely to be a Canon setting.

@Rick W
The behavior you describe doesn't ring a bell for me, but you can see what you have enabled/configured in ML by going to the delta (or "Modified") tab, the rightmost one in the ML menu.  "HS" undoubtedly refers to half-shutter.  Maybe you have a module enabled that is doing exposure control?

I still notice I can't change the lens aperture while recording is taking place either in RAW or H264. What's the latest on this? Is some more info/testing still required?

I'm not familiar with this issue.  Are you using exposure override?

Just wanted to ask fellow Canon 50D users or anyone who knows whether you can turn on Liveview through the menu in the camera instead of by pressing the Liveview button on the upper left corner?

It'd be possible to make a menu option in ML to turn on LV, but I imagine that it'd be too niche of a use to be included in ML itself.  A simple module would probably be the way to go (or script, once that's possible).

Anyone knows if full-res silent pics is now part of the nightly build for 50D? I'll be shooting a time-lapse this weekend . . . . Please, please, please . . . .

I guess the "weekend" is already long gone, but no, full-resolution silent pictures are not in the nightly builds yet.  You can always compile a build yourself or request one.

Er, that sounds pretty weird.  My inclination is to suspect the card reader; I don't see how ML could be at fault here.  Which card reader, camera, and filesystem?

[mlv_play]

The loop function could be automatically set to loop at the end of one clip or perhaps a loop button to restart the clip each time you press it?

I've wanted this too!  I've just implemented this functionality – replay a video by selecting "|>" after it finishes – on my mlv_play pull request, which is up for review.

[exiftool]

The existing "Fix black level" option does not work properly on the 50D because the wrong target value is in the code (1024, when it should be 1792), so don't enable it.  It's usually immediately apparent if the black level is wrong on your videos (strong green or magenta casts), and you can correct any black-level issues after recording by using exiftool.

Once this pull request is fully tested and merged, black-level detection should be much more reliable.

Still doesn't change the fact that the 50d can't do dual iso video, its a dead horse point.

I dont own a 50D.  But from what I read it was one of the first to offer dual ISO.

To clarify this particular point, the 50D can do dual ISO *photos*, but cannot (yet) do dual ISO *video*.

[exiftool]

The safety I am talking about here is
- killing something (sensor, killing some pixels for good, something else in camera..)
- shortening life of something (shortening life of sensor, some other part?)

As a general rule, electronics don't like being exceptionally warm, especially if they weren't actually designed for it, so there's probably some risk, but we certainly can't quantify it.

Thanks for other answer, all clear now .. this nightly looks very very interesting .. any manual that's following the nightly builds?

There's a work in progress in this thread, and of course, you can always search the forums.

and how to get this pink stuff out of the dng's ?!!? any converter I try I get same pink images?

I can't view DNGs on this computer, but my guess based on your words is that the automatically set black level is incorrect in the DNG.  The black level on a 50D DNG should be 1792, so you'll need to use exiftool to set it to the correct value.  It could also sometimes be a problem with the white level, depending on which parts of your image have a color cast.

Full-resolution silent pictures should not be available yet in any nightly build (there's not even an open pull request yet).  You'll have to look for or ask for builds in either its specific thread or the general build-request thread.

[mlv_rec]

I installed ML on my 50D but I don't see RAW video anywhere? Do I need to get the latest nightly or?

You need to load either the mlv_rec or raw_rec module, and then enable one (not both) under the Movie tab.

Any ideas if the RAW feature for 50D will go to stable release any time soon? How stable are the nightly's? I don't mind if camera crash from time to time but I'd hate to brick it (it's the only decent camera I have)

There currently isn't a timeline for the next stable release.  The nightly builds are pretty stable, but there will occasionally be broken builds (hopefully fixed soon after).  I don't believe there's been an actual instance of ML bricking a camera in a permanent sense, but rarely a camera may end up in an odd state and need to be coaxed back to normal, which could mean days/weeks of downtime.

I remember in the 50D manual there was talk about "you cannot leave LV on for long because sensor will overheat" - I see temp during RAW recording (nightly) goes to 50C fast how safe is that?

I don't know if it's possible to quantify the safety.  At the warmer temperatures, you may see some variation or artifacts in the sensor output, and the 50D has a quirk where the FPS may lock to 22 fps.

what is the difference between modules that record MLC and RAW wrt 50D, I see that MLC adds some meta data and RAW is just raw but anything related to 50D I should know of? some use more ram then the other? some need more io then th eother?

Since the 50D can't do audio, the primary benefit of MLV is the useful metadata.  I recommend using MLV unless you find that it's not performing well enough for your needs.  If that's the case, then see if RAW makes a difference.

and final question, can't find the "crop" option anywhere

Press the 5x zoom button in LV mode.

Let's not start this confusion again.  itsDPmikey is converting from DNGs to DNGs, because the dual ISO video frames are extracted in DNG format, before they are even processed.  itsDPmikey, please just try the Lightroom plugin before asking more questions.

If H.264 playback is part of the 50D firmware, we don't know how to access it.  If it's not, a software solution would need to be developed, but the performance would likely be poor.

i gave it a shot and these are the issues i recognized(canon 7d)
1-occassional is not possible to stop recording..hit the stop button and it has no effect or stopd for a second and goes back to recording

Known issue and being looked into.

2-screen turns black and white when i 5x zoom(only in the raw mode)

If you're talking about during actual recording, that's not a bug.  What you are seeing is ML's preview rather than Canon's preview, because Canon's preview shows only part of what is being recorded when in crop mode.  (There is some ongoing investigation into improving the crop preview, but it needs much more testing.)  You can change which preview is used in the options; "Auto" means that the Canon preview is used when not in crop and the ML preview is used when in crop.

3-missing the audio features

Under discussion

[movie_was_stopped_by_set]

Hmm, curious.  It looks like the 7D was lumped in with the 50D and the 5D2 because movie restart wasn't working the other way (see this commit from Jan 2013).  For the 7D, movie_was_stopped_by_set was set by BGMT_LV rather than BGMT_PRESS_SET, despite the name.

Then, it looks like movie restart broke recently because the 7D-specific gui.c was considered obsolete and removed (see this commit from two months ago).  It's possible that a1ex simply didn't notice that there was a custom button handler in there.

This "noise" can happen with fine bright points and specular highlights.  As with most cameras, the 50D skips rows in non-crop mode, which for example means that the blue pixels next to a red pixel in the image are actually from three rows away on the sensor.  As a consequence, a white feature on the size scale of only a few pixels can gain a color tint due to the poor color sampling of that feature.

It makes sense this noise is not present with motion because motion blur will smear out any small features, and thus mitigates the spaced-out color sampling from row skipping.  If these were hot pixels, motion shouldn't make a difference.

It also makes sense that this noise is minimized in crop mode because every sensor pixel is being read out.  You can still get color effects depending on the presence of very fine features and the effectiveness of the demosaic algorithm.

[playback]

ML histogram in playback on first shot showed plenty of headroom to increase exposure, histogram in second pic showed that I had almost clipped highlights.

However, in quick review, the histograms seemed to be the same (both shots had plenty of headroom to push highlights)

That's correct: in playback mode, ML only has access to the processed data, so it's not possible to produce a raw histogram, unlike in quick review mode, where the raw buffer is accessible.

There is no ML histogram in Playback, so I don't know what you are taking about.

He's talking about bringing up the image analysis in playback mode (pressing FUNC or the equivalent button on the camera).

[cr2hdr]

First, don't use a cr2hdr built in 2013(!)

Second, don't refer to "2.0" and 1.4" when referring to the version of cr2hdr, because it's not versioned like that.  I presume you are referring to the version of the Lightroom plugin, but that doesn't immediately reveal what version of cr2hdr is actually being used.

Third, please do what kichetof suggested: in your two cases with different behavior, run the respective cr2hdr executables from Terminal, without giving it any input files.  The first few lines should look like:

Code Select Expand


cr2hdr: a post processing tool for Dual ISO images

Last update: f381b87 on 2014-07-06 09:46:41 UTC by phil:
Fix output (-o) filename value passed to Adobe DNG Converter wh...

No input files.


I presume, perhaps incorrectly, that there is some way in BarracudaGUI to save the location of exiftool.exe as a preference so that it doesn't prompt you on every frame.  If you have saved the location as a preference, and it's still prompting you, then that sounds like a bug you should report to the author.

Since you have Lightroom, definitely see if the Lightroom plugin works for you.

[adtg_gui]

adtg_gui is slow because it intercepts everything.  it's more appropriate to look at iso_regs for guidance, although you'll need the camera-specific addresses found in adtg_gui.

[mlv_play]

Well I have the same problem no sound at all

"Same problem"?  There's no sound with RAW recording (as opposed to MLV recording).

and the second problem always I record in Raw but when I playback the video on camera is always in slow motion

Playback in the camera (using the mlv_play module) can only go at a few FPS, so it can't keep up with a normal frame rate.  You can switch the playback mode from "all" to "exact", and then the module will drop frames as necessary so that the playback simulates the actual speed.

This doesn't clarify anything... If both modules are loaded RAW/MLV recording will break after a few frames.

What he's trying to say is that he has the two modules loaded in the Module tab, but he hasn't enabled both types of raw recording in the Movie tab (so no green dots in that tab).  It hasn't caused me any problems to have both modules loaded, as long as you don't actually enable both types of recording at the same time.

It's definitely safer to not load both modules to avoid accidentally enabling both types of recording.

[raw2dng]

I did notice some other errors/warnings, if someone has time, can you please confirm that the following is acceptable?

It looks like the errors you're still having are with building the local executables (raw2dng and cr2hdr), which is why you aren't having any problems with what you are loading on the camera.

Like a clapperboard?