Messages

Roberto Mena, the camera profile you shoot with will not affect the DNGs in any way, at least not directly. If it causes you to shoot differently, however, (say, by exposing differently) because of how the image appears on the camera display, then that could indirectly affect the DNGs you get.

Yes, you need them:
http://www.magiclantern.fm/forum/index.php?topic=11454.msg145501#msg145501

Not sure if this will help but here is some info: Once you install ml on a camera, the camera's "boot flag" is enabled. This means that if you put a bootable card in the camera without ml on it (like if you deleted ml from the card) then the camera will not be able to boot up. Have you tried a card that is not "bootable?"

"How exactly would a silent picture cause mechanical vibrations?"

It wouldn't; hence its advantage in astrophotography and the desire for longer possible exposures in FRSP.



Topic split from here.

Nice! Looks like you used two cameras?

Brought back fond memories. Thanks!

@visiono,

Only nightlies have raw. It is recommended to use the latest to get all recent improvements. As frequently indicated, no ml is 100% "safe" but you won't find many (or any?) stories of actual damage done to date. Whichever version you decide to use, always thoroughly test it before using for anything important.

@ _OLLE_

So, in AE under edit preferences, under import, you can set the default sequence frame rate. Set that to whatever is your most common frame rate (or change it as needed).

In Smart Import 2, there is a field for the comp frame rate. If you leave it blank, the comp frame rates will be set at the default value you set in AE as mentioned above. If you put a value in there, it should override the default AE value.

Using these two settings, you should be able to deal with different frame rates. However, you might need to run Smart Import 2 script separately for each frame rate.

MLVFS

@ Welles, looks like aliasing. No perfect solution, but there have been a lot of suggestions for reducing or preventing it if you look around. Crop mode nearly eliminates it (but has its own drawbacks).

If you're using AE with MLVFS, you'll want to use the Smart Import 2 script.
Also, the post here includes an explanation of how to use the script with AE (steps 3-6; the rest of it won't apply to you since you're on a mac.)

@ Exo,

Why, do video restorers like to waste their time? RAW is cool because of all the information it contains. If you "convert" H264 to RAW you are not adding information, you are just adding useless bit weight.

I wonder if there's any legacy converter to turn h264 into 14bits RAW/MLV?

IMO that would be a pointless waste of space (and time).

Q2: You don't need to know code to use raw. You need:
1 - a fast CF card
2 - a lot of hard drive space
3 - a decent computer
4 - time and motivation to learn a new post-process (one of several described on this site)

Thanks for the update. Did you use magic lantern?

I like the look. Technical details?

Are you talking about some kind of compressed format?
The stock video is H.264 which is 4:2:0. AFAIK, that color sampling can't be changed.
RAW (available through magic lantern) has no color sampling. It's just all the sensor data.

[EDIT:]

Ottoga,

Here are the formulas I am using. Note that they do not show all the math since I am using some Excel functions ("DEVSQ" etc.).

Code Select Expand

Sum of the Squared Deviations
x=DEVSQ(Data Set A)+DEVSQ(Data Set B)

Pooled Sample Variance
y=x/([Count of A]-1+[Count of B]-1)

Standard Error of Difference in Means
z=SQRT(y*(1/[Count of A]+1/[Count of B]))

Our T -Stat
=([Mean of A]-[Mean of B])/z

U (used in DF calculation)
U=[Mean of B]^2/[Mean of A]^2

Degrees of Freedom
V=(1/[Count of A]+U/[Count of B])^2/(1/([Count of A]^2*([Count of A]-1))+U^2/([Count of B]^2*([Count of B]-1)))

Critical T Value @ 0.95 (95% confidence)
=TINV(0.05*2,V)


If the T -Stat is larger than the Critical T Value, then the difference in the means of the two data sets is significant.

If someone wants the spreadsheet, I can upload it.

As far as the data format, it doesn't matter much to me except that it would be nice if it were consistent.

EDIT: I should probably give the site where I got these formulas:
http://policeanalyst.com/performing-a-statistical-t-test-in-excel/

[B beat C, D and E]

For Reply #67

Code Select Expand

GDraw ON

A: raw_rec.mo
Count = 15
Mean frames = 1061

B: raw_lite.mo
Count = 10
Mean frames = 1118

C: 30bb06a.mo
Count = 20
Mean frames = 939

D: e78c7b8.mo
Count = 5
Mean frames = 926

E: Don't know
Count = 5
Mean frames = 920

A vs. B
T -Stat: 0.88
Critical T: 1.73

A vs. C
T -Stat: 1.55
Critical T: 1.70

A vs. D
T -Stat: 1.10
Critical T: 1.89

A vs. E
T -Stat: 1.21
Critical T: 1.89

B vs. C
T -Stat: 2.27
Critical T: 1.75

B vs. D
T -Stat: 1.90
Critical T: 1.83

B vs. E
T -Stat: 2.24
Critical T: 1.83

C vs. D
T -Stat: 0.10
Critical T: 1.94

C vs. E
T -Stat: 0.15
Critical T: 1.94

D vs. E
T -Stat: 0.03
Critical T: 1.89

B beat C, D and E

GDraw OFF

A: raw_rec.mo
Count = 15
Mean frames = 1826

B: raw_lite.mo
Count = 15
Mean frames = 1720

C: 30bb06a.mo
Count = 15
Mean frames = 1848

D: e78c7b8.mo
Count = 10
Mean frames = 1576

A vs. B
T -Stat: 0.68
Critical T: 1.70

A vs. C
T -Stat: 0.16
Critical T: 1.70

A vs. D
T -Stat: 1.14
Critical T: 1.72

B vs. C
T -Stat: 0.97
Critical T: 1.70

B vs. D
T -Stat: 0.68
Critical T: 1.72

C vs. D
T -Stat: 1.41
Critical T: 1.72

No winners

Bottom line:

Global Draw ON:
B beat C, D and E

Global Draw OFF:
No winners

If we're going to do much of this, would it be possible to get the data in a predictable format?
Perhaps something like a1ex provided in Reply #58, i.e.:

Code Select Expand

Raw_rec version : ML/MODULES/RAW_REC/32M-MLV.MO
Recorded frames : 671,1045,995,725,771,704,772,564
Raw_rec version : ML/MODULES/RAW_REC/HDR512G.MO
Recorded frames : 710,1253,1455,1326,1430,898,691,536
Raw_rec version : ML/MODULES/RAW_REC/32M-MLV.MO
Recorded frames : 451,1054,959,1045,1038,755,666,798
Raw_rec version : ML/MODULES/RAW_REC/UNIFIED.MO
Recorded frames : 832,1315,1316,1308,1178,1260,708,528

Btw: Is there an option to use not 14 BIT RAW, but something like 10 BIT or even 8 BIT? I know there is less data, but it might be still enough for the most of us and better than h264. Maybe some of the slower cameras could record in higher resolutions this way?

Nope.

AFAIK, when it says 5x, it's really 3x.

[B, C and D are tied (means are not significantly different).B, C and D beat A (32M-MLV.MO)]

For reply #58:

A: 32M-MLV.MO
Count = 104
Mean frames = 829

B: HDR512G.MO
Count = 56
Mean frames = 1050

C: UNIFIED.MO
Count = 80
Mean frames = 1012

D: 32M-RAW.MO
Count = 112
Mean frames = 1061

A vs. B
T -Stat: 5.63
Critical T: 1.66

A vs. C
T -Stat: 5.44
Critical T: 1.66

A vs. D
T -Stat: 6.92
Critical T: 1.65

B vs. C
T -Stat: 0.80
Critical T: 1.66

B vs. D
T -Stat: 0.24
Critical T: 1.66

C vs. D
T -Stat: 1.23
Critical T: 1.65

B, C and D are tied (means are not significantly different).
B, C and D beat A (32M-MLV.MO)

EDITED to correct some numbers (the spreadsheet is a work in progress) but it didn't change the bottom line.

[B beat A (HDR512.MO beat 32M-MLV.MO)]

For Reply #55:

A: 32M-MLV.MO
Count = 40
Mean frames = 742

B: HDR512.MO
Count = 24
Mean frames = 926

A vs. B
T -Stat: 5.54
Critical T: 1.68

B beat A (HDR512.MO beat 32M-MLV.MO)

[So A and B both beat C (32M-RAW.MO and UNIFIED.MO beat 32M-MLV.MO)]

A: 32M-RAW.MO
Count = 56
Mean frames = 992

B: UNIFIED.MO
Count = 70
Mean frames = 972

C: 32M-MLV.MO
Count = 16
Mean frames = 790

A vs. B
T -Stat: 0.70
Critical T: 1.66

A vs. C
T -Stat: 4.11
Critical T: 1.70

B vs. C
T -Stat: 5.80
Critical T: 1.71

So A and B both beat C (32M-RAW.MO and UNIFIED.MO beat 32M-MLV.MO)

If you're going to make the "Saving Private Ryan" sequel, you're all set.