Uncompressed 14-bit RAW video testing - 5D Mark III

Started by bumkicho, May 17, 2013, 04:59:17 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

jonathan.grevsen

@deafeyejedi I will test it again, since 1920x960 is what I prefer to shoot I never really got into finding out where the issue was with 1080

Nerodanger

First of all I just wanted to thank ML for amazing software.

I've installed  Nightly Build 2015Dec20 5D3123

Using Sandisk Extreme pro 160MB/s 64GB card.

Frustingly I'm getting the pink frame/corrupted frame issue. But it's intermittent. Sometimes not at all in a 3 min MLV RAW video and sometimes twice in a 2 min video. As I have an ATOMOS Ninja, I'm torn between downgrading to 1.1.3 for the stability or using the clean HDMI out as a back up to corrupted frames.

Is it possible to get stable MLV RAW output on 1.23. or should I just accept I'm going to get corrupted frames?
Also the time remaining indicator doesn't work so I have to guess how much space is left on the card.

You help would be gratefully appreciated. Thank you.

Danne


Nerodanger

I've set it to focus peaking only as I was hoping the card is fast enough to cope with this minimal setting. But I will test with GD off and report back. Are there any other settings worth trying before turning this off? Thank you.

Nerodanger

I've just run a test of 8mins MLV RAW 1920x1080p with sound and Global Draw turned off and I'm very pleased to report that there were no bad frames! Does this mean I need a faster card  (Like a CFast as opposed to the x1066 SanDisk I'm using) to get any extra features like focus peaking or is there anything else I can change like the card buffers? I'm really not sure what they do and can't seem to find any info on them in the forum.

Having a remaining record time or size of disc space left would also be very helpful - neither seems to work.

Thank you once again.

5DIII 1.2.3 Dec15 ML build

Walter Schulz

CFast not supported by Canon DSLRs. If you manage to insert one it will bend most pins in cam's CF-slot.

Nerodanger


Nerodanger

Does anyone know how to get the remaining record time or space left on the card whilst recording RAW on 5Diii build Dec15?

Frank7D

What works on the 7D is:

Turn camera off
Turn camera on
In Canon menu, go to format (but don't actually say ok to format) and you will see how much space is used.

Nerodanger


strikermed

Running the latest build of ML on 5d3 1.2.3.  Is anyone having issue with random Red Frames?  I get them on just about every clip.   Buidl: Nightly.2015Dec 20.5d3123

Is anyone else have thing issue?  Does anyone know how to fix this?  I use an Atomos Ninja Blade, so I need the uncompressed HDMI, so I can't go down to 1.3.3.

Any help would be great!

Nerodanger

I'm new to this too, but from testing I've discovered that enabling the HDMI mirroring does slow the write speed down so it could cause errors potentially. 

It would depend on your card speed and the frame size you've chosen to record. Turning off global draw and recording in RAW (not MLV RAW) without sound might help. If you've tried that and it still doesn't work someone more experienced would need to help. When you select RAW you should see in the menu at the bottom if ML thinks the card is fast enough. If the writing isn't in green your card or setting might need to change.

jarabmx

Any more tips how to solve pink DNGs? Turning off global draw is not great as you lose a lot of important information. It makes me nervous that the good take might be ruined by it..

Also, with the latest ML nightly build, when shooting MLV, only few resolution options are available, only 1600x900 and then 1920x1080 - any reason why that is? I love tweaking the resolution and find the one that you can just keep running fine.

Thanks

itsDPmikey

When I first got my 5DM3 early last year.. or a little more than a year ago, I was using the 123 version and I would record 1920x1080 24fps all the time with no bad frames at all. When I started to update to newer versions of ml I started noticing bad frames, mostly when I changed to 113 version.

I wish I had never changed anything.
I love this &^*$ MAN!

beauchampy

Quote from: itsDPmikey on February 22, 2016, 11:40:02 PM
When I first got my 5DM3 early last year.. or a little more than a year ago, I was using the 123 version and I would record 1920x1080 24fps all the time with no bad frames at all. When I started to update to newer versions of ml I started noticing bad frames, mostly when I changed to 113 version.

I wish I had never changed anything.

I have a build from August 2014 I've been using for years with no issues.. I've just gone back to it (testing right this minute) all being well I can send it to you. PM me.

EDIT: just tested and it has that issue where it stops after 8 mins with the 'Failed to open file. Card full?' error..

I'm at a bit of a loss on how to get my 5d3 recording past 8 mins without pink frames now.. Help?!




Walter Schulz

Quote from: beauchampy on February 23, 2016, 12:23:26 PM
EDIT: just tested and it has that issue where it stops after 8 mins with the 'Failed to open file. Card full?' error..

I'm at a bit of a loss on how to get my 5d3 recording past 8 mins without pink frames now.. Help?!

If you are using a build made before late January/early February 2015 and are using MLV you will run into that error because MLV shots were restricted to about 40 GByte.

beauchampy

So.. MLV 123

Build #37 (Aug 7, 2014 12:01:30 AM) - Doesn't cause pink frames but has a limit of 40gb (around 8mins at 24p)
Build #38 (Mar 16, 2015 2:12:37 AM) - Pink frames present but no 40gb limit. Also bad vertical banding @ ISO 800?
Build #43 (Dec 20, 2015 7:57:55 PM) - Pink frames present but no 40gb limit.

I'm now going to test the in-between builds.. (Updating this post as I test)

a1ex

You could try to test 1.1.3 builds between Aug 7 and Mar 16 - that way you have more chances of narrowing down the exact change that is causing the issue.

beauchampy

Quote from: a1ex on February 23, 2016, 03:12:27 PM
You could try to test 1.1.3 builds between Aug 7 and Mar 16 - that way you have more chances of narrowing down the exact change that is causing the issue.

These builds?

3​53 Mar 16, 2015 1:10 AM
3​52 Mar 15, 2015 1:10 AM
3​51 Mar 14, 2015 1:10 AM
3​50 Mar 13, 2015 1:10 AM
3​49 Mar 12, 2015 1:10 AM
3​48 Mar 11, 2015 12:08 AM
3​47 Mar 10, 2015 11:55 PM
3​46 Mar 2, 2015 1:10 AM
3​45 Feb 20, 2015 1:10 AM
3​44 Feb 18, 2015 1:10 AM
3​43 Jan 29, 2015 1:10 AM
3​42 Jan 28, 2015 1:10 AM
3​41 Jan 24, 2015 1:10 AM
3​40 Jan 15, 2015 1:10 AM
3​39 Jan 14, 2015 1:10 AM
3​38 Jan 3, 2015 1:10 AM
3​37 Oct 7, 2014 1:10 AM
3​36 Sep 27, 2014 1:10 AM
3​35 Sep 12, 2014 1:11 AM
3​34 Sep 1, 2014 1:10 AM
3​33 Aug 20, 2014 1:11 AM
3​32 Aug 8, 2014 1:41 PM
3​31 Aug 7, 2014 1:11 AM

At the moment my testing is to record around 10-15 clips at 50p with GD On, Audio on.
I also record a long 20min 24p file.

The trend so far is that if there is corruption in the 50p footage - there will be corruption present in the 24p stuff as well. I propose (since there are 23 builds to get through) just to run the 50p clip tests.

Not sure I'll be able to get round to it this week, but this is my plan...

Walter Schulz

40 GByte limit was fixed in build 346 (02.March.2015). Sorry, thought it happened 1 month before.
Test build 345 and 346 first.

DeafEyeJedi

Geez guys this better be worth the efforts and thanks to @itsDPmikey for starting this party. It is actually a great thing that we are digging through this in order to narrow down those issues.

Will report back my findings w 50p tests as soon as I can.
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

itsDPmikey

Quote from: DeafEyeJedi on February 23, 2016, 06:33:18 PM
Geez guys this better be worth the efforts and thanks to @itsDPmikey for starting this party. It is actually a great thing that we are digging through this in order to narrow down those issues.

Will report back my findings w 50p tests as soon as I can.

Appreciate it thanks Jedi. I am now using 1.1.3 from 03/27/2014, installed it yesterday and used it for a couple of hours. Works BEAUTIFULLY! But I am curious to what the trade off was between that and the newest build.
I love this &^*$ MAN!