Messages

[On Youtube: https://youtu.be/gg_eUU9SWCM]

If somewhere there is a paradise on earth, then no doubt that this is Maldives! White beach, turquoise ocean, romantic wedding - everything was as we dreamed 🙂  Our experience, a sense of peace and calm happiness that overtakes everyone here, we have tried to convey in our video.

Enjoy watching!

On Youtube: https://youtu.be/gg_eUU9SWCM

Gear used: 5Dmk3 ML RAW, Sigma 24mm f/1.4, Rokinon 14mm f/2.8, Canon 75-300mm, DJI Ronin-m, GoPro.

emrahcahit, your lilliput monitor is not 1080p. Are your lcd monitor is full hd and you were using 1.2.3 firmware with clear hdmi 1080p signal?

Do you have any chance to shoot the latency issue and the latency difference between internal and external monitor? It also will be very handy to connect 1080p computer monitor over hdmi and check if the latency still there.. I guess it will give you the answer who is guilty. Camera or the monitor.

Hello everyone!

Thank you for watching my video and I'm very glad you liked it!

It all was shot in 1920x1080p25 without any exclusion. For slow motion I used Twixtor. I used Osiris LUT with after effects color correction.

The 24-70L is very versatile and sharp lens. It is very useful for shots like this when you have about 1-5 minutes to shoot every location. But I'm not sure about it's artistic value. If I have ability to shoot "in stage" I'm surely wouldn't choose it.

PS My girlfriend just was on her vocation like I do) I didn't tell her what to do or were to go. It's like our home video or something

Gear: Canon 5d Mark III, Canon 24-70mm f2.8

Thanks for watching. Feel free to ask if you have some questions.

LiveView ISOs are a little lower than displayed. I've measured 82 on 5D3 LV, vs 104 in photo mode - that is, 0.34 stops difference.

You took the CR2 at F1.4 (from exif), and at this aperture, Canon applies 0.15 stops of digital gain (found by DxO and confirmed by my experiments - the exact value is log2(0x239/0x200) from the digital gain configuration).

So, you should expect the MLV to be 0.5 EV darker than the CR2, assuming identical metadata.

I've converted your CR2 into DNG with Adobe DNG converter, so ufraw renders it like any other DNG (that is, normalizing the raw data according to black and white levels from metadata, and not other black magic), and I still needed 0.45 stops of exposure compensation for the MLV.

   

Noise levels are obviously going to be different (see the first link). The 5D3 does hardware 3x3 binning on the sensor, and then it adds read noise from its electronics (after binning). The end result is worse than a CR2 downsized by 3x3 in software, both in sharpness and noise levels.

=> this is not a bug in MLV.

Yep. I think you are right.

I have a manual lens with chipped m42-eos adapter. This might be the problem? What aperture should I select so the canon apply no digital gain to the image? Taking the opportunity to ask you. How can I enable the 66 - 115 - 230 etc. iso on 5dmk3? I only have 100 - 160 - 200.. Thank you for your help!

[CR2]

Took mlv test shot to same exposure as CR2 by moving the exposure in ACR. And compered noise level.

Croped 250x250px and 200% resize.

CR2


MLV


Resized to 1080p. Croped 250x250px and 200% resize.

CR2


MLV


When MLV frame is formed in the camera the 5760x3840 resolution resized and croped to 1920x1080? So the noise level should be much less then in CR2. Didn't it?

[MLV]

Have some tests.

Same setting, same condition. MLV vs CR2.

MLV

https://www.dropbox.com/s/uc5g48qshid0twc/M31-2250.000000.dng

CR2

https://www.dropbox.com/s/w1s9pkxjmgre45r/2C1A0087.CR2

0,75 stop difference.

[a1ex]

Your ETTR hint indicates 1 stop of underexposure, and ETTR itself uses another stop as a safety margin (the algorithm needs it to know how much to go back, but you can reduce it to 0.5, or allow it to clip some more highlights, or ignore some color channels).

Your issue was about the difference between raw and mlv (read the title of your post if you don't believe me).

a1ex my apologize for naming the post wrongly and for some misunderstanding. I'm just trying to understand what is going on and why the canon exposure meter don't match the result on the computer. And how should I setup the camera to achieve ETTR advantage.

As I understand your advise is to first exposure according to ettr raw hint and then give it an extra 0.5 stop to compensate underexposure in post?

As I understand you said that the problem of underexposured image in mlv is the wrong interpretation of meta data by ACR and not the raw files themselves? So the files are exposured right and they have entire Dynamic Range according to histogram in the camera. They just underexposured in ACR and need to be corrected?

Sorry if I get you wrong as my English is not very good. And thank you for your help!

[a1ex]

a1ex, I'm not sure that the problem is with the tiny difference between mlv's and raw's exposure. But the problem is with the exposure at all. As I see you had to use a 2 extra stops to properly exposure my images that was already properly exposured in the camera according to the exposure meter. It's mean that every shot that was made on 5d mark III need to be corrected. The 50d didn't have such a problem and the output images looked exactly as they was shot, with the ETTR hint all you had to do is just slide the highlight recovery all the way to the left get it back to normal and get your dynamic range with no noise. Now its not that easy and I'm trying to figure out how to use a ETTR hint now.

It does differ; raw2dng does not output 16-bit files, like the one you attached.

I'm not going to download these huge files.

Well. It's really does differ. My mistake

MLV (mlv_dump):
https://www.dropbox.com/s/etr4fu3szb37vna/mlv_mlv_dump.dng

RAW (raw2dng):
https://www.dropbox.com/s/g2do4cmxglm9p4b/raw_raw2dng.dng

But It's even darker.. I'm not sure is this right because of the fact that histogram on the camera doesn't match the result histogram and I can say it's not match even visualy. How to set the right exposure then. I'm confused.

It does differ; raw2dng does not output 16-bit files, like the one you attached.

I'm not going to download these huge files.

ok I'll post it in a few minutes.

[a1ex]

Can you use the reference converters? (raw2dng and mlv_dump)

You have used closed source software, so I have no idea what processing was applied.

a1ex, I already tried raw2dng, result doesn't differ. Also I will post source here, so everyone can try their converting methods, but I'm think it wont help.

https://www.dropbox.com/s/vuf7qv47sxjigrr/M29-2115.MLV (639MB)

https://www.dropbox.com/s/y3pd4i2lspfyuuz/M29-2115.RAW (563MB)

H264


RAW


MLV

Here is some tests. All made with the same settings and the same light conditions.

H264:
https://www.dropbox.com/s/bhcu6nw8mcx61mz/2C1A0080.MOV

RAW (RAWMagic Light):
https://www.dropbox.com/s/7xc4lk28rki8mku/raw.dng

MLV (MLVMystic):
https://www.dropbox.com/s/h3x4br0pvorhly5/mlv.dng

Here is jpg snapshots:

H264
https://www.dropbox.com/s/qunvtxsmadwwe5c/h264.jpg

RAW
https://www.dropbox.com/s/y9khlg1vdixwsr4/raw.jpg

MLV
https://www.dropbox.com/s/qkkfa8yk3akn3cm/mlv.jpg

Didn't get a chance to post video examples. Problem is still there. I'll post it today.

I'll try to post some test examples later this evening.

For one year I owned Canon 50d and shooting a lot of cool videos using RAW module. Recently bought brand new 5d mk3 and installed a Magic Lantern.

Recording goes ok (MLV + Audio) but when I copied, converted and open files in ACR noticed that they are 1 stop darker then they should be. Especially considering that they must be overexposured a little beacouse I was using a Histogram ETTR RAW Hint. It just 1 stop darker compered to h264 and raw_rec with the same settings and static conditions.

Here are some details what I found out:
- I tried converting MLV to dng using MLV Mystic (both Win/Mac) and MLV Converter 1.9.2
- I tried 1.1.3 and 1.2.4 firmware (clearing the bootflag everytime)
- I tried Nightly.2014Jul25.5D3113 and Nightly.2014Jul16.5D3123
- Overall exposure on the camera monitor seems to be the same. Result are different only on computer.
- Raw rec & h264 have correct exposure as it should be.

So for now nothing helps and I shooting using the raw_rec. But the ability to record sound in the same files using mlv rec are very useful and I'm looking forward to find out what is the problem.

Have someone any ideas why is it  happening?

Camera: Canon 50d ML RAW, Fuji Finepix XP60
Lenses: 30mm f1.4, 55-250mm f4, 11-16mm f2.8
Gear: Konova K2 Slider, Velbone DV-7000 Tripod with fuid head, Variable ND filter

If you have any questions please ask.

Probably the same and different, at the same time.

You should spend more time reading in the forums, rather than posting. Everything you need to know is here, you just have to digest it.

The point is that it's capturing raw live feed as sequential images. If you capture smaller than the whole frame, where would you take it from? It's not resizing it, it's just capturing as many pixels as you tell it to.

I know that and that is what I'm trying to tell. You capturing a part of image you suppose to take from sensor. So if you have 30mm lens in FF it will be 50mm on 50d and it will 60mm or even more when you choose to shoot in lower resolution with RAW on 50d. I't will just crop your angle. And in result you will have more noticeable noise. It will just be bigger and softer just like you zoom Full HD on computer. You just began to notice more then with max resolution.

No it won't do that.

Shooting in a lower resolution will just give you a softer image when blown up to 1080P, if you only plan to put it on a DVD then this won't matter. (although, in my experience, shooting a higher res and downscaling does tend to give better results than shooting SD from the outset)

The angle of view, crop factor, DOF, f-stop etc will stay exactly the same regardless of whether you shoot at 1584x1058 or less. All these things will  only change if you enter 5x shooting mode, then the crop factor is around 4x I believe.

Ok, But when I change the resolution on my 50d in raw_rec module (for example to 1440x890) the shooting frame becomes smaller and don't cover the whole screen. And records only the image that stays within the frame. And it always been this way in every build I tried. Your experience is different?

could shoot in lower resolutions to get more recording time

As I understand lowering the resolution will result in smaller frame cover (crop factor). As I see from my experience It will increase the DOF distance, noise level and cut the wide angle lenses. If the shooting condition allows, you can use it. But you must notice it.

I spend some time testing the smoothness of RAW video with different setups. And achieved success result.

I tested a lot of different combination and experiment with FPS timer A & FPS timer B using the calculator I found on the internet. The result was quiet different. And here what I found.

The only mode that was really smooth in my case was 29,97 fps with default h264 FPS timer A & FPS timer B settings. You can find it if you turn off the raw video and fps override and just enter the fps override menu. There will be default values that you can't change. I just copy the numbers and the result was very smooth with no twitches. I tried the same fps with Exact FPS and in my test it was not smooth enough. Also I tried 30 fps and it was even worst.

The post processing is alright as I tested it DaVinchi, Premiere, After Effects, RawMagic, Raw2Dng, ProRes, h264 and the result is always the same. h264 1920x1080p30 (29,97) is extremely smooth by default.

Unfortunately I have no time to prove it with examples but I think this could give a clue to someone who experience the same problem and test it out to prove or refute it.

And please someone, Post a video example that will show some smooth panning using RAW module fps 23,97 to show that it is possible? I can't find any of these.

Something wrong with fps again. Project settings or interpretation mismatch.
Or even stabilizer is still on ))

There are no stabilizer on this lens)

This are the setting I using:
FPS Override: 24 exact FPS
Resolution: 1584x892
Global draw: On
Shutter speed: 1/48
Exp.Override: On
Exp.Sim: Movie

Canon settings all default except: quality - RAW

This are the workflow:
Then raw2dng > adobe camera raw 7.0 > WB correction > Export to TIFF > Export Sequense in AE > interpret to 24 fps > new 24 fps sequense > add to render > h264 24fps 1584x892 High 4.2 target 20 max 62,5

I don't understand what can I do wrong. Maybe it something in my camera settings?

UPD
I tried the same thing in DaVinchi Resolve 10 Lite Beta. Result is pretty much the same. So it has to be something before post production.

Sorry for late reply.

Here is another example I shoot today. I think its pretty much better but not perfect. Maybe I just used to shoot in 30 fps and 24 fps is just not smooth enough for me. What do you think?