Messages

I use "Magic Lantern RAW Video Converter 1.9.1" (I'm on Windows). It doesn't export cdng but simple dng files. I've never tried raw2cdng, but what should be different? I think every Windows tool uses mlv_dump.exe, or am I wrong?

What I noticed this evening: Regardless of whether HTP is on or off or which ML digital gain value is set, the footage looks exactly the same in Resolve. Same DR, same noise levels, a 100 percent match. I still can't believe it, but I've tested it six or seven times.

HTP & ML digital gain off (ISO 100)
HTP on, ML digital gain off (ISO 200)
HTP on, ML digital gain +1.0 EV (ISO 400)
HTP on, ML digital gain +2.0 EV (ISO 800)
HTP on, ML digital gain -0.3 EV (ISO 160)

During recording, the differences were clearly visible.


Edit: Apparently it's a known fact that HTP doesn't affect raw video. So that can't be the reason for my issue.

Hey, thanks for your answer!

So, here's a warmer version. And that's the waveform (damn, I revealed his face :-))
Of course the overall image got even noisier as it has more red in it. Here's another obvious example



EDIT:

A few moments ago, I tried to grade it without any LUT applied (just normal BMDFilm colors), and it looks much better! At these noise levels, Neat Video will work very well. Red is obviously way less saturated than with the LUT getting applied.
I did it via TeamViewer though, I'll check the exact result tomorrow. Thanks so far! Stay tuned.

Hi,

I've been recording RAW video with my 50D since December 2013. It took me 1.5 years to find out that the image noise level in the red channel is extremely high.
Take a look at this screenshot.

The t-shirt is plain red, no structure at all. But in my footage it's covered by a ton of low frequency noise.
For testing purposes, I separated chrominance from luminance in Resolve and took a look at the noise levels of both of them. Result: The luminance channel is almost noise-free, so are the blues and greens, but the reds look like this.

• I'm using BMD Film to VisionLOG LUT.
• I have highlight tone priority enabled and configured a ML digital ISO gain of +1.0 EV. In my tests, this has led to the best dynamic range. Dark areas are quite noisy, which is why I denoise my footage with Neat Video (just a tiny bit, there is no visible loss of detail)
• I can't get rid of this noise with Neat Video, it's frequency is too low and the irregularity too high.
• It doesn't matter wheter I denoise before the LUT is getting applied or afterwards.
  
• I tested a second 50D on this behaviour. Same result.
• When using the Linear to BMDFilm 4K LUT, the issue is almost invisible, but the more I try to grade it towards the gorgeous colors of the VisionLOG lut, the more appearant the noise gets.

Is this a known issue? Do you have any advice in terms of settings or post processing? Please keep in mind that I would like to get the best dynamic range and if the solution would noticeable reduce the DR, I ain't even averse to switch to another camera.

Best regards,

eightcore

I'm still highly amazed by the organic and beatiful image this camera is delivering. VAF is a must of course.

I still hope that I will find a worthy successor one day.



Just a frame grab out of Resolve. Dang, JPEG made it look blocky. PNG.

Huere guet! Das geile Video zeigt wider mau, wie wichtig der Schnitt isch.

Yes, double-posting. Please delete!

I'm not able to export 2.35:1 footage as DNxHD Full HD with letterboxes. Resolve always streches the 2.35:1 frames vertically to match 16:9 ratio, I can't change this behaviour.

Any hints?

Back to 10.1.5 then.

I've discovered a problem with my 50D and every nightly build since 2014-03-10. When I want to change shutter or aperture over the scroll wheels, nothing happens on the main display. The hole image on the screen is not changing at all, including the displayed shutter and aperture values. On the b/w display on the top of the camera, the values are changing correctly.

When I switch to the gallery and go back to LiveView the exposure is getting applied correctly.

In summary, it seems that rotating the scroll wheels doesn't trigger a refresh of exposure anymore.

Example:

I power on the camera and launch LiveView.

Main Display: f/2.2, 1/660
Top Display: f/2.2, 1/640

I use the scroll whell to increase the aperture value

Main Display: f/2.2, 1/660
Top Display: f/9.0, 1/640

I open the gallery and switch back to LiveView

Main Display: f/9.1, 1/660 (the new aperture is now getting applied physically, too)
Top Display: f/9.0, 1/640

I tried the following:

- changed several settings in terms of exposure (Exp. Lock and so on)
- formatted the card and completely reinstalled ML
- tried over 15 builds (problem doesn't occur < 2014-03-10 < problem occurs)

What's the cause?

Amazing tool by the way! I already integrated it in my workflow. A question: Could you implement the specific feature which allows to see the progress in the taskbar?

Example:

It seems that the conversion library or whatever already supports splitted video files (*.m00), but the "GUI" doesn't know this. As a result, the percentage exceeds 100 percent (because e.g. 3600 of 2200 frames are exported), which throws a .Net error.


Edit: I tested it and it really works except the percentage error.

Can at least the last 6D ML version be made available?

Maybe alex had given a link in the past. I do not know. I will search but a link would be welcome...

And 50D, please.

In the thread "RAW video & ML -- Beginners Guide, FAQ & Useful Links -- READ FIRST" they refer to builds.magiclantern.fm/#/ as the download source for RAW video firmware, which isn't correct anymore in the case of the 50D.

What's the point of having development builds if nobody is developing?

The point is that users without knowledge of compiling code can easily use ML for RAW recording.

You (developers) think: "Nobody is developing, so it makes no sense when we keep it in there"
I (user) think: "Why we have to compile it by ourselves just because nobody is developing?"

There isn't any Information about Dual ISO capability, neither in the linked thread nor in the Google Doc spreadsheet.

Which cameras support dual ISO for video recording?

Hi,

DualISO is only working in photo mode for me. For testing purposes, I imported the DNGs in Lightroom right after extracting them out of the RAW file (via raw2dng) and they aren't interleaced. Of course cr2hdr says the same as me: "Doesn't look like interlaced ISO".

And no, I haven't forgotten to enable DualISO.
I'm using build 2013-11-12.

Does anybody use the 50D for RAW recording with DualISO? If yes, successfully? If yes, which build?


Best regards,

eightcore

a1ex, I just noticed that you've removed the 50D nightly builds.

So new ML users with a 50D have lost the possibility to record RAW video with their camera (due to missing repositories for downloading builds which supports this)?!
Seriously?

The card was in the camera when the problem occured, and I don't think that the camera is an 'un-compatible card reader'.

Hi,

I recorded a music video yesterday using the ML nightly build of the october 26th. Towards the end, the camera stopped working. Changed ML settings were not saved and at every boot the message "Camera was not shut down cleanly. Skipping module loading." appeared.

Later I've noticed that writing to the CF card (SanDisk Extreme UDMA 7) respectively mutating data is no longer possible. I can't neither format it on my PC nor directly in the camera. When I delete a picture, it's there again after the next boot (same issue on PC). It is completely read-only!

Can anyone help me?

Edit 1: CHKDSK stucks at 0 (zero) percent.

Yes, you're right.
But at the end, I can't export it with this framerate. Or at least I haven't yet found any way to do this.

I switched to Adobe Premiere Pro now.

New Problem:
In the sequence settings, I can't set the fps rate manually, but only 24.000 and 23.976 (and several others, but these drop off for me)
If I set the fps rate in ML to 24.000 or 23.976, the image is too bright, so I can't use my 50mm at f1.4 anymore during daylight.
The brightness is okay at 24.008, but I can't choose these frame rates in Premiere.

How can I solve this?

Hi there,

I record videos with 24 fps. Nevertheless, the fps number is set to 30 in the video file, so I wrote a batch which converts the videos with the correct framerate. I use Avidemux for that.
And here's the problem: If i set the destination framerate to 24 fps, the video file is being converted with 23.999 fps.
That's why the videos are stuttering.

Does anybody know a solution for my problem (e.g. another software)?

Thank you for your help, Got it.

Yes, it is. Bad idea?

With exposures like 1/50 or 1/100 the difference is pretty small. But here's an example:

Preview:


Final photo with the same settings:


Other settings doesn't change anything (tried it with enabled and disabled ExpSim)

Another example:

Hello!

I've got a problem with my 50D: A specific subject looks overexposed in LiveView but when i shoot a picture with the same settings, the final picture is exposed correctly. Can I solve this problem?


Sincerely, eightcore

Thank you!

I have a 50D