Messages

Beautiful, thanks!

For the first time in years I shot some dual iso pics again just to find out that I don't have cr2hdr on my machine any more. Tried to grab it from Bitbucket but - surprise - Bitbucket seems to have been bought out and the ML repo doesn't seem to be accessible any more... Does anybody happen to have some recent source files of cr2hdr anywhere?

Actually, it was a question - I just forgot the question mark, but thanks for the explanation and the link

I noticed a very odd thing with my shutter speeds in LV mode. While the top LCD shows 1/50, ML actually shows 1/48 on the monitor. I have filmed in a location with very bad CFL tubes and I did get vertical moving artifacts, suggesting that I really was shooting with 1/48. Next lower would be 1/41 and next higher would be 1/62 according to ML. Video mode was set to 1080p25.
Is this a quirk in the 7D Canon fw or is that an ML quirk

Standard YouTube license

7D, EF 135mm f/2 L, MLV normal and crop mode

Maybe posting a request in the "volunteer work" subforum at blenderartists.org could lead to something. After all, Blender and ML are both open source and there's quite a few open source- / CC-minded people in that forum.

I noticed that DaVinci Resolve doesn't recognize the sound file belonging to the sequence when exporting to cDNG which results in sound having to be linked manually. When using MLVFS, that works. It's probably just a matter of correct naming of the sound file. I also noticed that the sound is exported twice, once in the sequence subfolder and once in the parent folder.

@Andy600:
Jep, that's what I'm doing mostly - rendering to AVI and then using ffmpeg and libx264 for compressing. I'm mostly delivering for YouTube at the moment.

I tried forcing data levels and the render looks more like the GUI viewer bit then with more clipped highlights.

[different]

I think, you are missing the point . A calibrated monitor through a dedicated output guarantees a consistent result on different viewing systems (minus user settings) but as I said, I was talking about viewing the render result on the same monitor on the same system that I used the GUI monitor on. In that case, the render result should look identical to what you see in the GUI viewer - minus compression loss, of course.

I did a ton of tests and I found that when I render to any Quicktime format, I see a Gamma shift in the render, even when I render to uncompressed YUV with Quicktime. However, when I render to uncompressed YUV AVI, I do NOT see any Gama shift. In that case, the render looks exactly like the preview in the GUI viewer.
According to what was written by others in the BMD forum and what I found myself through Google, this problem in Quicktime is known since 2010! There's even well known workarounds on MAC using Apple Compressor.

Here's a post of William Aleman in the BMD forums about that: https://forum.blackmagicdesign.com/viewtopic.php?f=21&t=6557&p=281742#p281622
3 posts above is my test results.

There is a known problem with QuickTime messing up the colors when rendering. Some software has found a way around it. Resolve hasn't. I had the same issue as ddelreal and found the only way around it was to render to AVI uncompressed YUV and then compress to h264 with libx264.
@andy600:
To my understanding, the GUI vs. dedicated (calibrated) monitor only applies when viewing the render on a different system. When I use the GUI viewer for grading and then view the render on the same system and the same monitor that ran the GUI viewer, the render should look identical to the GUI viewer.

Thanks @Andy600 !

Yes, I do have a fair amount of storage and a reasonably fast machine (Core I7-4770K / 32GB RAM / GTX770). Hence I decided to use MLVP to convert MLV to cDNG and work in Resolve from cDNG without intermediate codec. Besides, subjectively I find Resolve performs faster with cDNG than with ProRes or DNxHD material, especially when moving on higher speed through the material or backwards. At the moment, I'm doing the rough cut for my project, also deciding which of the material I use. After that I'll go into color correction and then into grading.

I understand the advantages of debayering to log space with regards to creative choices. Does it also have advantages as to dynamic range? I'm trying to wrap my head around the whole colorspace-stuff and it's not easy if you never dealt with the underlying technologies before . I was assuming that if I edit straight from cDNG, all raw information will be available, regardless of which colorspace I choose for debayering, i.e. I don't lose any dynamic range. Is that assumption correct?

@markodarko:
No Adobe here... Just for principal - long story...
@reddeercity:
Actually, I got myself a Windows 7 license just for Resolve . I'm on 12.5b1 at the moment, waiting for more feedback on b3 in the BMD forums before I install it.
I'll try your method.

I am editing in Resolve .

So, I finally dared to use ML in real production - not on my 6D, though, but on my 7D, and I'm quite happy with the image quality! Thanks to MLV Producer, converting MLV to CDNG was done very easily.

Now, the correction and grading... At the moment I use REC709 as input color space in the project/camera raw settings. Would there be any advantage to using another setting, e.g. BMD Film?

When exporting to CDNG, the chosen export color space on MLVP doesn't really seem to make a big difference.

Is it already possible to apply an export/conversion profile to all clips in a queue? Yesterday I had to go through 28 clips to set the profile . Some "apply this preset to all clips in queue"-button would be awesome .

@sgofferj
I did some windows scaling support, but it was a long time ago. i need to rework it.
Can you make screenshot how it looks?

Here's the screenshot: http://home.gofferje.net/stuff/mlvp4k.png

I meant the start-stop button .
That's odd that it happens to you with any file size... For me it works perfectly fine for short recordings.

Had a quick look and test... Awesome program! Just a little issue... I have a 4k display and increased the Windows font scaling a bit and MLVP doesn't seem to cope with that too well. The top bar is halved...

You have to hit the button a second time. The problem occurs when your record a big file, because the camera pops up that message about the file being split because it's too big. That message triggers the restart of the recording. If you push the button again right after that restart, the recording will stop.

Will do. I also noticed something funny... When I connect an external monitor, I have dropped frames after a few secs. Without external monitor I don't. I can consistently reproduce that.
Edit: Is there an interface speed limit on the 7D like on the 6D? Or does it make sense to buy the fastest card I can find?

ML Nightly.2016Jan14.70203.ca5315a3b586

Card
SanDisk Extreme 60MB/s UDMA 8GB

Benchmark
Global draw on
16384: W41.1/R43.4MB/s
            W41.4/R43.5MB/s
15625: W41.4/R42.4MB/s
4096:   W39.3/R41.0MB/s
3906:   W37.5/R40.5MB/s
2048:   W39.8/R38.8MB/s
1953:   W34.6/R36.7MB/s
128:     W14.9/R16.5MB/s

Global draw off
16384: W43.1/R46.1MB/s
            W48.0/R45.1MB/s
15625: W45.4/R45.5MB/s
4096:   W41.3/R44.2MB/s
3906:   W40.1/R42.5MB/s
2048:   W39.6/R43.0MB/s
1953:   W37.0/R39.4MB/s
128:     W15.9/R17.8MB/s

Settings
1600x680, FPS override 23.976, optimize for exact FPS

Just started with MLV on the 7D (6D works, no problems) and I see exactly the same as in the OP's video. What information is needed to find the source of this problem?

Morning!

I recently got a 7D and I'm planning to use it with ML for video and photography, mainly wildlife. I have a handful of old 8, 4 and 2 GB cards and already successfully upgraded the camera FW and installed ML on a card. So far so good.
Now, what's the biggest size card the 7D can handle? Any recommendations for cards for MLV?
Any caveats for shooting video with the 7D? On a quick research I read something about overheating?
And then a less ML-related question: I already did some photography with the 7D and compared to my 6D, the raw pics look a bit washed out and less sharp out of camera. I'm using darktable on Linux for developing my raw pics and for the pics from my 6D I rarely need to apply any big expo or contrast correction, especially when using ML AETTR. The 7D pics I shot all required pretty strong modifications of black point, expo and cranking up the sharpening a lot.