Messages

I have watched your video on my mobile phone and from what I've seen those colored dots are typical color aliasing and moire issues due to line skipping (or just debayering artifacts?). Those dots are more visible on cameras like Canon 7D (I know that because mine has those dots all the time) on shots with fine details (especially on wide-shots with great depth of field where fine details cannot be properly rendered , where everything is in focus). I've also noticed a lot of moiré on the wooden floor. There's not much you can do unless you buy a VAF anti-alising filter which is expensive or try to blur the color channels keeping the Y unaltered (google alising blurring color channels UV in Davinci resolve). It Works sometimes. Or just be aware of the limitations of your camera when shooting trees, foliage, textures with very fine details... and try steady shots, perhaps with reduced depth of field (you know, just some important object in focus, not everything). Hope this helps.


Enviado desde mi iPhone utilizando Tapatalk

I agree with all what domo94 said. I've been using 7d with ML for 4 years and the image is amazing, very cinematic. I have shot an entire movie with 7D. I think the main downside is the aliasing more visible in shots with fine details (especially wide-shots). The upscale to 1920x1080 works just fine, no big deal. Noise can be a serious problem on ISOs above 800 and could be very annoying on underexposed shots (not always someone can avoid underexposed situations).


Enviado desde mi iPhone utilizando Tapatalk

how does shooting raw affect the shutter count? Is it like shooting video where one video is only one to the shutter count? Or does every frame affect the shutter count?

I apologize for my ignorance but why is shutter count important for you?


Enviado desde mi iPhone utilizando Tapatalk

https://en.wikipedia.org/wiki/Lossless_compression

Thank you for your reply.
So, there should be no difference between lossless and uncompressed. When to use uncompressed then?


Enviado desde mi iPhone utilizando Tapatalk

Hi everyone,

Sorry if this has been asked before, but I can't really find relevant information. Have you seen any visual difference between uncompressed raw and lossless raw? The difference in file size is huge, but visually, even after hard grading, I can't see any. Thank you.


Enviado desde mi iPhone utilizando Tapatalk

+1 and it's free and chews through DNG files like nothing, free version has no de-noise or sharpening but you can use
CinemaDNG for that and is currently free also, recent update enables loading of MLV files directly

Win win

You're saying that Resolve is now accepting mlv directly?


Enviado desde mi iPhone utilizando Tapatalk

I've just tried the MlvApp and "tiff_clean script" command activated on mac and something weird happened every time the file was created:

When I export to any Prores, the .mov is created on the hdd. Then, the script runs automatically and a .tiff sequence is created. After the process is completed, the folder automatically deletes itself. Why's that? Anyone know?

In Premiere Pro CC the .dng from MLVApp needs a while to play and it's slower however .dng from MLVRaw Viewer plays smoothly.

Has anyone experienced this?

If I offended @masc in any way, I apologies.
Perhaps I overreacted because there's seem to be a trend these days: some users get really upset because some newbie dare to ask the "silly" and "obvious" question  that somehow goes against the forum rules and Google is always the way to go.

Both apps use different approaches of finding and eliminating bad/hot pixels and correcting vertical stripes.

I'll try that.

Which MLRawviewer do you use original old version without lossless MLV support or newer modified?

I used the MLVRaw Viewer 1.4.3 which is the last version. In Resolve, both .dng play smoothly.

Thank you.

TEST:

Two .dng sequences 14bits lossless, same raw settings.
.dng from MLVRaw Viewer 1.4.3 and .dng from MLVApp Alpha



 
In order to see the difference, I mixed the two waveforms. The red one represents the .dng from MLVRawViewer.  There is a slight visual difference between both. Doesn't seem like a big deal, however the MLVApp .dng visually has more red and blue.

In Premiere Pro CC the .dng from MLVApp needs a while to play and it's slower however .dng from MLVRaw Viewer plays smoothly.

TEST:

Two .dng sequences 14bits lossless, same raw settings.
.dng from MLVRaw Viewer 1.4.3 and .dng from MLVApp Alpha



 
In order to see the difference, I mixed the two waveforms. The red one represents the .dng from MLVRawViewer.  There is a slight visual difference between both. Doesn't seem like a big deal, however the MLVApp .dng visually has more red and blue.

In Premiere Pro CC the .dng from MLVApp needs a while to play and it's slower however .dng from MLVRaw Viewer plays smoothly.

I guess you know why. Let's have a look at what you have replied on the MLVApp thread:

uncompressed is uncompressed and lossless is lossless (compressed).

Oh, thank you very much for your very elaborate answer. Thank you for mentioning that uncompressed is uncompressed because I thought that uncompressed was, guess what... compressed.

I can't tell what MLVRawViewer does

If you can't tell, please don't answer. Do you a favor and don't waste your precious time.

Regarding my question:

Maybe MLVRawViewer just generates the .dng sequence way differently than MLVApp. Is there a visual difference? Guess what, I made a test and there is a subtle one on my waveform (Red and green channels are lifted 1 IRE). Why's that? I don't know, maybe is just my imagination. I'm not sure, that's why I asked the community. There's even a subtle difference between both compressed .dng sequences on the waveform and looks like the difference lays in the saturation (the .dng from MLVApp look more saturated). Or maybe both are the same quality, only they are interpreted differently.

Cheers.

Has anyone noticed any difference between .dng uncompressed and lossless? 

Hi everyone,

I've just tried the MLVApp Alpha and then compared two .dng sequences in Resolve,  one exported from MLVApp, the other one exported with  MLVRaw Viewer 1.4.3.
I can't  see any visual differences not even after en extreme grade was applied. The MLVApp dng sequence doubles the size of the MLVRaw Viewer on my disc drive. I guess it is because MLVApp claims to export uncompressed .dng?

Any thoughts?

Thank you. I'll try that.

I've just done some tests with interesting results:

Canon 7D, Nightly.2017Dec07.7D203
Connected to my HDMI Monitor
Res: 1728x972
16x9
23.976fps
MLV Lite
No sound

Now comes the interesting part:

TEST1
Global Draw - On, All modes
Only Histogram Activated
Force HDMI-VGA - OFF
Clear Overlays - OFF

RESULT: Recording fails all the time (EDMAC timeout error).

TEST 2
Global Draw - On, All modes
Only Histogram Activated
Force HDMI-VGA - OFF
Clear Overlays - Recording

RESULT: Recording fails sometimes. However, if it successfully starts, it records continuously. No bad/corrupt frames. However, more test has to be done. No tearing.

TEST 3
Global Draw - OFF, All modes
Force HDMI-VGA - OFF
Clear Overlays - Recording

RESULT: No fails. Records continuously. No bad/corrupt frames. However, more test has to be done. No tearing. However, when I accidentally pressed the "ISO" button, the Canon menu showed up and the recording stopped. Conclusion: Looks like every time some kind of overlays are activated, recording fails. As you said, seems like  "ML might overload the memory bus when recording starts" and recording fails.

Hope this was helpful. Thanks again for your support.

The code is open source, feel free to modify it as you see fit.

One more question: the error only shows up on the screen at the begging of the recording. Once the recording successfully starts, It never shows up after. Why's that? Thank you.


Enviado desde mi iPhone utilizando Tapatalk

The code is open source, feel free to modify it as you see fit.

I don't have that knowledge.


Enviado desde mi iPhone utilizando Tapatalk

That's because the regular mlv_rec does not attempt to detect this condition (so it doesn't print the error).

Bandwidth is the amount of data processed in some fixed amount of time. If you record at the same resolution, you get the same bandwidth (+/- some minor differences from slightly different file layout, unlikely to be relevant - on the image processing side, there are no differences in the amount of data processed).

Ok. Maybe it might sound like a stupid question, but I assume that there's no way to to "bypass" it?


Enviado desde mi iPhone utilizando Tapatalk

Most likely, the bandwidth required for all these tasks is more than DIGIC 4 can handle.

If that happens at 24 FPS, I'm afraid there's not much you/we can do about it.

Thank you for your reply. I'm using it at 24fps (no sound). Isn't Mlv lite supposed to use less bandwidth because there's no sound, less metadata and no overlays? I'm telling you that because normal MLV Raw works just fine (however I get tearing when no force VGA is set).


Enviado desde mi iPhone utilizando Tapatalk

Hi everyone,

I'm using MLV Lite with an external monitor (no Force VGA is set, with clear all overlays set when recording)  and when I hit record, it stops pretty often. I get EDMAC timeout error. Does anyone know why?

I use Canon 7D with the last built.

Thank you.


Enviado desde mi iPhone utilizando Tapatalk

How do you change the bit depth?


Enviado desde mi iPhone utilizando Tapatalk

Hi everyone,

In Davinci Resolve, on the camera RAW tab, you can set the BMD color space and gamma. However, the names are generic: Blackmagic Design Color Space and Blackmagic design Film Gamma.

Does anyone know which one the ML's .dng is based on? Because each one of the following cameras uses a slightly different BMD color spaces and gammas (correct me if I'm  wrong):

Black Magic Pocket
Black magic 2.5K
BMCC 4K
URSA Mini 4.6k

Sorry if this has been asked before.
Thank you.

Thank you for your answer. I have tried the Mlv lite for a couple of days and I can confirm that there's no tearing anymore on my 7D. Regarding sound, hope they implement it soon.

Thank you for your advice.