Messages

If Chroma Keying with h.264, in my experience, the recording work has to be done almost perfectly in order to get good results.

First of all, I would like to mention that Cinestyle can be your downfall in this matter. If you are chroma keying with cinestyle, the scene might simply be too flat for your software to be able to exclude the green screen. Same goes for landscapes and cinestyle, if there is no contrast in a scene and you record with cinestyle, you risk ruining the footage as it will be hard to pull back all the details that differentiate in contrasts.

Do what kihlbahkt said, bump up the green channel and if possible in your software, start a new layer after for further adjustments.

2nd: Filming a green screen.

Its imperative that you keep some distance between your talent and the greenscreen to avoid green reflective spill on your talents hair, shoulders etc. Atleast 3-4 meters when the greenscreen is lit up by controlled light.


And with h264 its very important that your greenscreen is evenly lit as the codec is so compressed that small variations in lighting can easily make artifacts that can require masking to remove, which is a pain when it could have been avoided.


and last.. Try doing this in RAW and save your self a headache

Good luck! 

If the dial is on P or Av, does it do the same?

I am also sure you can adjust this somehow in canon menu for one of the custom dials.

I don't have my MKii at hand right now, so cant test this for myself, sorry.

Good speed-up! But magiclantern-Nightly.2014Sep01.5D3113 and raw_twk.mo  has a problem with 5x zoom ML Grayscale. White lines on the screen and  camera hangs sometimes.

I got same build, I'll see if I get same results with Crop mode and ml grayscale.

Edit:

Confirmed

So is there no chance for the waveform to be developed in to RAW?

And I was laughing at the fs700 waveform

Yes, makes sense that the idx is interferring as these mlv files have been played before on the earlier nightly that I was using.

Thank you, I will try this.

Installed on 1.1.3. on latest nightly. See significant improvement

Played a clip that took 64 seconds to play before raw_twk and after it was 35 secs.

But latest nightly wouldn't play .mlv files that were recorded before I updated to latest nightly. raw files played fine though.
Nothing to do with raw_twk though, it was not loaded when I started playing the files and noticed that the mlv files would not play, just mentioning.

Thanks a lot for this geggo! Really nice improvement. Haven't really done any recordings with the raw_twk loaded, but also just updated to latest nightly so will be hard for me to tell if I encounter problems, if it is the raw_twk module or latest nightly that causes issues.

Correct.  Only the spotmeter, histogram and zebras work with raw data.

I was under the impression that the waveform was RAW too.. Now looking at the menu again I see it doesn't mention anything about RAW.

This changes everything, I've been basing all my exposure on the Waveform

If playback is set to "fast", do you get realtime playback?

Anyways, really nice improvement, I will try this on 1.1.3 if thats not a problem? As above post states an issue?

Thought I'd share this.

Turns this cheapo lens in to a beast of a macro lens.

And shots from the same guy:

Now imagine using this lens with 3x Crop

Take a look at the Rokinon 35 T1.5 cine lens.

It's a beast!

What you need to do is make the composition to 1920x1080, add a solid black layer first, then add your 1920x817 footage, that will make the dnxhd footage render out perfectly.

You're welcome

25 fps will make max continues resolution smaller. I was talking about 23.976 earlier. Hihgher framerate requires higher write speed.

But you should definitely be able to record more than 4 secs. Try only activating raw_rec module, it gives best write speed.

It would also help a lot if you posted your exact settings under Raw tab.

Here is the 5D MK ii specific thread: http://magiclantern.fm/forum/index.php?topic=11205.0

Firet post pretty much contains everything you need to know.

Install all modules, you will have to activate them later in modules tab.

For video recording, i only use Mlv rec, mlv snd, mlv play and file manager.

Mlv_play also works with Raw rec.

Mk ii struggles when sound recording is activated, as the write speed is limited. Disabling audio recording will gain you more speed and that gives you higher resolution on continues or longer record times on non-continues resolutions.

Reddeercity, he's an avid ML Mk ii user and has managed to get continues 16:9 at max resolution, 1880x1058. I dont remember what his precise settings were though, but that was on raw_rec module, october 24th build.
Global Draw off and every other extra feature, think also Sraw was selected.

But mk ii records normally 16:9 1880:1058 for atleast 30-40 seconds without hazzling of disabling too many features.

This is ofcourse if you have a 1000x CF card.

ML Raw will seem quite confusing at start, but if you do some reading on the forum, especially the 5D mk ii thread in Camera Specific Section, you will learn a lot.

Good luck and prepare to be amazed.

I dont use lightroom, fcp or prores.. So I cant be of much help there.

But if it works for whom is in that video, then it should also for you. I'm sorry, but I have only a 5kbs connection, so i cant watch it.

If lightroom has ACR, then you can upscale there. Go via Bridge and select all DNG's.

I asked this to get a little clarification. Working with RAW In post, I sense that the DR is so much more than 11.8. I mean when I really get in to highlight recovery with Acr+cineon and what not , I manage to pull out detail from the Sun itself (not actually), but exposing for indoor without any ND filtration on windows and still being able to pull an incredible amount of information from the outside, is astonishing. With some good masking and cc the shots look surreal.

I also own the mk ii and would like to help with your tests, but I am out sailing and my mk ii is at home. I will most likely return home in a week or two... Hope for one.

What is the goal of the test you are conducting?

So I've doing some thinking and reading.

5D mk iii has a dynamic range of 11.8. (This is h264 i believe).
I know Alex is working on some sub 200 iso's where the dynamic range on the mk ii and iii is increased with some decimals. I believe I read that the mk ii has more dynamic range than the mk iii at these 90 iso's or something. Think the mk ii hit 12.4 and mk iii, 12.1. Dont quote me on these numbers, read it somewhere deep in a developers thread.

This aint the pooint about this thread either, just mentioning them.

When I record Raw on my mk iii and ettr and I pull down the highlights, add cineon convert and all the tricks of the trade to pull as much information out of the highlights as possible and raise detail in shadows. Am I still only within those 11.8 of dynamic range?

Is post work on raw files included in these DR tests?

My experience with raw rec is that its 100% reliable. Only way raw rec messes up is if the user does something stupid.

Mlv works like 98% of the time.. Very rare, but sometimes, some shots are just messed up for no apparent reason

Adobe Ae cc has some kind of biliniar upscaling technique. Not sure how that fits your workflow.

I would also suggest that all upscaling be done with the original DNG's.

I've had pleassurable results with upscaling from DNG's to Tiffs in ACR, if you can get your hands on them.

Sounds like colour space mismatch.

Try rendering to rec.709

Thanks for further clarification on the Videolan binary.

@Audionut

I will try your simplified command, but I'll increase the bitrate for my quality (whore) needs

But I don't think I will be using x264 as a renderer in the future. After comparing the DNxHD footage with the h264 from PP (VBR 2 Pass 100 mb), I can't tell any difference. This is an upload for the internet anyways and the slight increase of quality in the h264 will be so minimal when watched on Vimeo that I don't think its worth the hassle.

Besides, if one really wants max quality on a video on Vimeo, isn't it best to upload a DNxHD or Prores file via Dropbox?

I'll just rework my workflow now and re-render all non-16:9 footage from AE with a Solid Black Layer.

Thanks again! I really appreciate your insight.

Just want to let you all know that I've solved the problem.

I added a solid black layer as a letterbox for all my 2:20.1 footage in AE and that rendered out perfectly with DNxHD, so no more stretch.

Premiere Pro also exports perfectly now without any aliasing or cropping of the image.

I want to thank you all for all the trouble you went through, trying to help me with this. It really shows what great community the Magic Lantern forum has.

How much money do you think RAWmagic guy and Baldand send to Planet5D to advertise their product?

@Film Dude

Yes I noticed that preview tick later and it was not ticked in. Never had it ticked in.

Maximum Render quality and Bit depth has also been ticked in always (I am a quality whore)

@Luiz Roberto.

I've been trying to get your command to work. First of all it stopped with the --fgo 15 said it was unrecognized. So I changed it to --fo 15 and it worked, but I couldn't find in --help what --fo does. Well maybe not worked, but atleast it didn't report it as an error.

But I seem to be unable to output my file. This is what I put in.

F:\>F:\x264-10b-r2431-ac76440.exe --crf 18 --profile high444 --preset placebo --
tune film --fps 23.976 --level 5.2 --sar 2:20.1 -t 2 --aq-mode 2 --me tesa --sub
me 9 --psy-rd 2 --fo 15 --no-fast-pskip --thread-input 8 --opencl -o [F:\Testfil
e] [F:\Næraberg\05.07.2014 160 Tons\Render\Sólar Rísing.mov]

x264 [error]: could not open output file `[F:\Testfile]'   <-- received message

I am not really sure if this is the correct way?

I drag and drop the binary file I downloaded in to cmd and then put in the command.

Do you see any error? I am not sure if I should write the aspect ratio as I wrote it: 2:20.1 ? Not sure how it interprets it.

I tried --profile high444 just for the hell of it, but it was the same with --high10

PS. I just noticed something else. PP crops the image. I noticed it when I was looking at the screenshots I posted and noticed that the framing was not similar on both screenshots. Especially the latter screenshots I posted, that shot was filmed on a tripod and I knew I didn't zoom in or out during the recording. So PP really has an issue with the 2:20.1.

Thank you Luiz!

Very detailed, I'll get at it right away!

the compositions settings are 1920x1080 with the black border, but when it is rendered out of AE it is still stretched. The codec doesn't do black borders. There probably is a workaround with adding a layer or something for the black border, I might try that.

To your second part, I am not sure if it is using preview files or Rendered files, I was assuming it was using the DNxHD files. How can I tell?

But the aliasing most definitely must have something to do with Squeeze - Unsqueeze.

@Luiz roberto

I tried your binary, I put it in to cmd. I am not very good at these command things. Could you point me in the right direction on how to use this tool? Like an example.

I typed in --help and got some info but I am not sure how to tell the program which file I want.

--fullhelp seems to exceed the number of lines allowed. I tried increasing max Buffer Lines (I think it was called) to 500 but it seems to be the same.

All your help is much appreciated.