Messages

Shooting on a 5DmkIII, why are the DNG's converting as 128x96 resolution?  They are almost 4MB each and the .raw file hasn't dropped a frame..I have access to 1000x cards from Delkin, Lexar, and SanDisk, and would like to test them all for members' information, but cannot get useable video from the process..will anyone help me?

-Colemar Nichols

I think they are recognised only by LR and ACR. Davinci Resolve also sees them as 128x96 (most likely a preview incorporated in the headers).

I uploaded my test to Vimeo. Play in HD

My setup:

- 5D Mark III
- Lexar Professional 600x 16Gb UDMA card (Manufacture Part Numer 508-60729 Rev A)
- firmware posted by lourenco on post nr. 385
- resolution set to 1280 x 720, only one that does not drop frames on this card

There are two problems I find:

a. tearing on some frames and I think it's always on the same line the tearing happens (may be wrong)
b. stuttering on pans, more evident for example from sec 42 to 52.

Questions:

A. Does the fix posted by Alex solve both? I don't know even if the're connected.
Maybe the raw video feed which the developers are trying to "redirect" to the CF it's not capable of genlocked 24 fps, hence the stuttering.
To me it doesn't seem that this raw feed is used to make the video recordings on the genuine firmware. The quality difference it's too much. Just an opinion 

B. It's the clip shot in RAW mode 24,000 fps or 23,976fps ??




PS. I solved the flickering on the wall, going through the AfterEffects - ACR route.

Regards,
Cristian

Ok, little recap, today I used:

- 5D Mark III
- Lexar Professional 600x 16Gb UDMA card (Manufacture Part Numer 508-60729 Rev A)
- firmware posted by lourenco on post nr. 385

I benchmarked the card using the built-in menu command  "Card R/W benchmark (5min)" under "Debug" menu. I have no ideea what is the correct procedure (if have to set something specific before running the bench). The bench just remains on the end screen when finishing. I have no ideea if this is correct, but anyway I found out there is a BMP file saved in the root of the CF.



Now the results:

A. 1920 x 1080 will drop frames . Probably because of the lower write speed of Lexar 600x (?)
B. 1920 x 1720 will drop frames . Probably because of the lower write speed of Lexar 600x (?)
C. 1280 x 720 will record with no dropped frames. I made some pans to look for tearing and unfortunately there is some from time to time. See below





Anyway to share some of the of the content:

Example of file with tearing (but there are more in the sequence):
https://docs.google.com/file/d/0B3ncQl4hSqlncER2VzdZVWk1dWc/edit?usp=sharing

H.264 movie from the first 1300 DNG files of the recording. DNG files were extracted with raw2dng.exe. I did some highlight recovery in Lightroom and there is some flickering on the wall behind. Probably because LR treats recovery on a per file basis. Have to check if this occurs in Davinci Resolve/Speedgrade or similar. 72 MB download, don't bother with the youtube preview, it's nowhere near the mp4 file.
https://docs.google.com/file/d/0B3ncQl4hSqlnUmhWQ2NhaXRNN0E/edit?usp=sharing

First 1300 files of the recording. 1,66 Gb download. If somebody wants to play.
https://docs.google.com/file/d/0B3ncQl4hSqlnRE1BNmdPalp6dms/edit?usp=sharing

Regards,
Cristian

Try new build. Card too slow maybe? It only happens sometimes... I posted examples. Also try different modes like 640 (shrinks yuv buffer on this camera)

Hi,

I tried only on lourenco posted firmware on post 385. I don't know if it's the very latest but I don't know how to compile the very last build.

Last time I compiled something it was like 20 years ago

It could be cool to save a log with how many frames are dropped.
Also I didn't find a way to stop the recording. For now it seems to just finish the 4gb file. If I press any buttons while recording I get Err 70 and I get very nervous 

Tested with the lourenco firmware posted on reply 385 on a Lexar 600x CF Professional 16gb & 5D Mk3

It drops frames on both 1920x1080 and 1920x720. Significantly more on the higher resolution but don't know exactly how much because there is no log saved. But there  were many frames dropped.

This should be the latest one from last night that reports frame skipping. It should work better too. let me know.
  https://docs.google.com/file/d/0B7QlH_BH2m32dWpOOEpkWktXMXM/edit?usp=sharing

Just to be sure:

raw2dng, 5D3-113-bootflag.fir, UserGuide.pdf don't need to be on the CF card. Is this correct?
5D3-113-bootflag.fir has to be used only once to set the bootflag then it can be deleted?

Mkay, so now I can make it begin recording but didn't figure out how to make it stop. Anyway, everytime I record after a awhile I end up with an Err 70 and camera it's blocked. I have to take out the battery to make it work again. A little bit nerve wracking.

Anyway I observed with lourenco firmware that when loading it says something about "scripts dir missing". Maybe it has to do with benchmark never finishing?

Hi,

Thank to the replies from previous posters I managed to make the lourenco posted firmware to load.
I loaded the raw module.
When I got to the movie raw screen it didn't let me set width/height and there was a message about "write speed needed".


So I went into the write benchmark but I have the following problem: the benhmark doesn't seem to end, it stays forever on this screen:



If I press some keys it will revert back to ml menus, but it doesn't seem to retain the becnhamrk speeds.

Thank you,
Cristian

Hi,

I'm new to this stuff, never used ML firmware before. But I have an MK3 and want to test/help on this.

I  have the 1.1.3 firmware on the mk3 and i've downloaded the mk3 zip files posted by lourenco and extracted them to an empty lexar cf card.
Then I followed the installation wiki documentation (although I see it was not written for the mk3).
When initiating the firmware update process I see a message superimposed on the menu saying something like "enable bootflag " and nothing happens. On restart I have the original 1.1.3 firmware.

I know it's probable trivial but can somebody help?

Thank you,
Cristian