5D2 RAW video Builds 14-Bit

Started by a.d., May 20, 2013, 05:27:13 PM

Previous topic - Next topic

0 Members and 4 Guests are viewing this topic.

dariSSight#1

Quote from: Redrocks on June 22, 2013, 02:38:05 PM
I just installed a.d's latest build (cf56893d7be4) and it appears to have variable buffering. Also he has removed his 1880 hack to bring his resolutions inline with A1ex's builds.

Hope your have a Cinematic day Redrocks and Magic Lantern Community,
I put the June 22 a.d's latest build (cf56893d7be4) in and it took my measure back to 1872 instead of 1880 what going on? So to keep thing somewhat accurate I put the 2013/06/21 0c3188c5134f Build back in at least the measurements right. What's the changes from 2013/06/21 0c3188c5134f Build and a.d's latest build (cf56893d7be4)?

morflexxx

Quote from: dariSSight#1 on June 22, 2013, 02:22:36 PM
Using a Laxar 1000x 32GB & 2013/06/21 0c3188c5134f Build on the 5d2, Ratio 4:3, 3:2, 16:9, 1.85:1 and 2:1 of Redrocks reading are the same but the 2.20:1, 2.35:1 and 2.39:1 are different on my readings:

2.20:1=1880x854
2.35:1=1880x800
2.39:1=1880x786

@ Redrocks & dariSSight#1
THANX!
This kind of summary-update-info about progress of improvements of the latest release are really useful to all ML users (instead to search and dig into 20+ pages of the thread with old infos).
From your tests experience, do you think raw recording without VAF filter is acceptable or there is to much aliasing and color aliasing?

Thanx again

Redrocks

cf56893d7be4, Komputerbay 64GB, GD off, exact 24 fps, resolution 1872:

1250 / just over 3:2 =

187
226
202
224
219

1054 / 16:9 =

575
510
511
561
543

1012 / 1.85:1 =

783
875
803
937
919

936 / 2:1 = one take only 7572 I'd say this ratio is good for 5 mins

850 / 2.20:1 = continuous

796 / 2.35:1 = continuous

Redrocks

Quote from: dariSSight#1 on June 22, 2013, 03:04:43 PM
Hope your have a Cinematic day Redrocks and Magic Lantern Community,
I put the June 22 a.d's latest build (cf56893d7be4) in and it took my measure back to 1872 instead of 1880 what going on? So to keep thing somewhat accurate I put the 2013/06/21 0c3188c5134f Build back in at least the measurements right. What's the changes from 2013/06/21 0c3188c5134f Build and a.d's latest build (cf56893d7be4)?

You too, dariSSight. A1ex has this to say about 1880 vs 1872:

"the builds from a.d. contain a number of extra changes, e.g. allows non-mod16 resolutions (which I prefer to stay away from, for DMA alignment reasons)"

"Bigger is not always better, mod16 resolutions are more important IMO, and the EDMAC is very sensitive to alignment."

Which is over my head, but I realised that 1872 is an exact 1/3 rd of the sensor and probably an easier number to work with.

Redrocks

From your tests experience, do you think raw recording without VAF filter is acceptable or there is to much aliasing and color aliasing?

Thanx again

______________

I intend to get one in the next week or so, but it's certainly acceptable without one.

dariSSight#1

Quote from: Redrocks on June 22, 2013, 03:29:44 PM
You too, dariSSight. A1ex has this to say about 1880 vs 1872:

"the builds from a.d. contain a number of extra changes, e.g. allows non-mod16 resolutions (which I prefer to stay away from, for DMA alignment reasons)"

"Bigger is not always better, mod16 resolutions are more important IMO, and the EDMAC is very sensitive to alignment."

Which is over my head, but I realised that 1872 is an exact 1/3 rd of the sensor and probably an easier number to work with.


I'm a little stomp but does that mean its an exact RAW video conversion from the sensor measurement, I think it's because Canon non-compromise for low-level access to the sensor that Magic Lantern cannot push the 1880 up.

Does lowering it to 1872 RAW measurements takes from conversions like 1080p?

Forgive my ignorance but I believe asking make you a little least ignorant.

dariSSight#1

Quote from: Redrocks on June 22, 2013, 03:36:54 PM
From your tests experience, do you think raw recording without VAF filter is acceptable or there is to much aliasing and color aliasing?

Thanx again

______________

I intend to get one in the next week or so, but it's certainly acceptable without one.

I will puchase a VAF filter soon because it seems to be something you might not want to be without, I do believe its always better to watch your ISO for Color Alasing and Moire and watch for pattern in your shots. What's the option for VAF filters I've only heard of the Mosaic VAF Filter?

Redrocks

As far as I know it is to do with line skipping which involves discarding 2/3rds of the data. In crop mode you have a true cutout of the sensor with no line skipping, but also a crop factor of 5.

EDIT:

http://www.magiclantern.fm/forum/index.php?topic=6242.0

more info here.

Redrocks

Current ad vs A1ex, Komputerbay 64GB, GD off, exact 24 fps, resolution 1872:

ad 1248 / 3:2 =

217
223
217
226
218

A1ex 1248 / 3:2 =

222
228
223
229
216

ad 1054 / 16:9 =

587
561
586
553
579

A1ex 1054 / 16:9 =

558
564
598
553
541

ad 1012 / 1.85:1 =

833
888
950
893
933

A1ex 1012 / 1.85:1 =

835
963
861
921
871

ad 936 / 2:1

4992

A1ex 936 / 2:1

3954


Yes it's better to do everything you can before relying on a filter, I haven't heard of any similar products to the Mosaic line.

Redrocks

Current ad vs A1ex, Sandisk Ultra 8GB, GD off, exact 24 fps, resolution 1872:

ad 1248 / 3:2 =

86
87
87
83
85

A1ex 1248 / 3:2 =

85
86
84
86
85

ad 1054 / 16:9 =

108
109
109
109
109

A1ex 1054 / 16:9 =

108
104
108
106
104

ad 1012 / 1.85:1 =

124
125
123
124
124

A1ex 1012 / 1.85:1 =

124
124
124
125
124

ad 936 / 2:1

132
128
133
131
117

A1ex 936 / 2:1

131
132
132
125
131

dariSSight#1

Quote from: Redrocks on June 22, 2013, 04:39:19 PM
Current ad vs A1ex, Komputerbay 64GB, GD off, exact 24 fps, resolution 1872:

ad 1248 / 3:2 =

217
223
217
226
218

A1ex 1248 / 3:2 =

222
228
223
229
216

ad 1054 / 16:9 =

587
561
586
553
579

A1ex 1054 / 16:9 =

558
564
598
553
541

ad 1012 / 1.85:1 =

833
888
950
893
933

A1ex 1012 / 1.85:1 =

835
963
861
921
871

ad 936 / 2:1

4992

A1ex 936 / 2:1

3954


Yes it's better to do everything you can before relying on a filter, I haven't heard of any similar products to the Mosaic line.

I seen that forum thread before but I don't think I soak it in. Reddeercity Post is very vital for the point of Aliasing and Moire fear, I took a closer look at his video after reading the thread and you can see he was correct Aliasing can be seen in the small low Res window but if you open it to full screen and even more pick the 1080p or Original format option it clears up greatly for presentation (beautiful), that's scratching the surface of filming in RAW and Upscaling. Thanks again for the revisit to the thread because it help drill the option of line skipping, Moire and Aliasing problem solving into my head.

siebenmorgen

 The cf56893d7be4 build locks really great! Sorry to say, it crashes with an external monitor.

eatstoomuchjam

Quote from: dariSSight#1 on June 22, 2013, 03:56:14 PM

I'm a little stomp but does that mean its an exact RAW video conversion from the sensor measurement, I think it's because Canon non-compromise for low-level access to the sensor that Magic Lantern cannot push the 1880 up.

Does lowering it to 1872 RAW measurements takes from conversions like 1080p?

Forgive my ignorance but I believe asking make you a little least ignorant.

When a1ex says 1872 is a mod16 resolution, it means that 1872 is evenly-divisible by 16 (1872 / 16 = 117).  In terms of upscaling 1872 x 1053 vs 1880 x 1057.5 to 1920x1080, you could say you see a difference, but you'd probably be lying or fooling yourself.  It's dropping a total of 0.85% of the resolution for much better performance.

dariSSight#1

Quote from: eatstoomuchjam on June 22, 2013, 10:19:51 PM
When a1ex says 1872 is a mod16 resolution, it means that 1872 is evenly-divisible by 16 (1872 / 16 = 117).  In terms of upscaling 1872 x 1053 vs 1880 x 1057.5 to 1920x1080, you could say you see a difference, but you'd probably be lying or fooling yourself.  It's dropping a total of 0.85% of the resolution for much better performance.


So Redrocks and EatTooMuchJam, I should reinstall the latest build?

Doyle4

Everything nice again on latest build! Managed to solve the X5 and X10 how too shoot, took awhile as only just found the page to set up the framing box and things! all good stuff :)

One thing i have noticed on this build is the text at the bottom that lets you know if you can record continuous (green) and yellow if it needs to buffer, it'll go green when i first setup but after shooting a raw video for say even a few seconds the text goes yellow, even after rebooting?

Once again, great work :)

UPDATE: All showing yellow now, checked through all settings and all are fine, checked CF read and write speed and no change.

eatstoomuchjam

Quote from: dariSSight#1 on June 22, 2013, 10:36:56 PM

So Redrocks and EatTooMuchJam, I should reinstall the latest build?

I have no opinion on what you should or shouldn't install.  :)

With that said, development is moving fast.  It's usually worth staying up-to-date.

Redrocks

"When a1ex says 1872 is a mod16 resolution..."

Thanks for the explanation. I agree there is no noticeable difference and if it lends itself to performance, I'm sold.

Unless you have a specific reason, always be running the latest builds dariSSight. Even though RAW is pretty stable, it's far from ready for general release and the developers need to hear from people who encounter bugs.

neopixel

Quote from: Doyle4 on June 23, 2013, 01:55:26 AM
Managed to solve the X5 and X10 how too shoot, took awhile as only just found the page to set up the framing box and things! all good stuff :)



I keep having pink images in crop mode with the lastest build (june 22nd); what settings did you use to get rid of that?
Any particular reslution or else?

Thanks for your help!

dima510

hi -  just wanted to say: GREAT JOB GUYS!! keep up your good work ...

d.

Doyle4

Quote from: neopixel on June 23, 2013, 10:03:32 AM
I keep having pink images in crop mode with the lastest build (june 22nd); what settings did you use to get rid of that?
Any particular reslution or else?

Thanks for your help!

Is this when you are Auto focusing? If so.. thats normal :)

dariSSight#1

Quote from: Redrocks on June 23, 2013, 08:22:01 AM
"When a1ex says 1872 is a mod16 resolution..."

Thanks for the explanation. I agree there is no noticeable difference and if it lends itself to performance, I'm sold.

Unless you have a specific reason, always be running the latest builds dariSSight. Even though RAW is pretty stable, it's far from ready for general release and the developers need to hear from people who encounter bugs.


Thanks All for the feedback and I'm running the latest build, You had me at Mod16 Resolution.

neopixel

Quote from: Doyle4 on June 23, 2013, 11:51:07 AM
Is this when you are Auto focusing? If so.. thats normal :)

Actually no! I only use the AF in photo mode... Are your dng files alright with the latest build?

thanks again!

Doyle4

Quote from: neopixel on June 23, 2013, 01:24:43 PM
Actually no! I only use the AF in photo mode... Are your dng files alright with the latest build?

thanks again!

When shooting RAW video are making sure ur LV is movie mode?

my DNG's seem to be fine mate.

neopixel

Quote from: Doyle4 on June 23, 2013, 03:07:54 PM
When shooting RAW video are making sure ur LV is movie mode?

my DNG's seem to be fine mate.

Yep! LV is movie mode!
But now I'd noticed something very stange:I own a 24-105mm; in crop mode (x5):
when shooting at 24mm: image is perfect
when shooting at 105mm: pink image

Fps overide is set on 24fps exact...

I didn't had this problem with the previous build that I used (14th june)

UPDATE: just to be specific it's working perfectly with resolution 1920 but not higher (used to work just fine before)

UPDATE 2: pink image with aspect ratio at 2:1 in crop mode; perfect image at 2:35

moet_chandon

I think it´s absolutely random.

Just made 12 movies in crop mode (tested 1920x960 (first 7) and 1920x818 (rest)):

- good
- pink
- pink
- pink
- good
- pink
- pink
- pink
- good
- good
- pink
- pink