Messages

fixed, thanks.

Thank you for all your effort!

I just tried the latest nightly build and sometimes during recording (MLV_rec enabled), the console pops up (on a 5D3). Found no way to disable it unless I restart the camera...

this is the assert:

ML ASSERT:
hdr->blockSize > 0
at mlv_rec.c:1969 (mlv_prepend_block), task raw_rec_task
lv:1 mode:3


Magic Lantern version : Nightly.2014Apr16.5D3113
Mercurial changeset   : 9058cbc13fa4 (unified) tip
Built on 2014-04-15 23:11:59 UTC by [email protected].
Free Memory  : 151K + 3815K

I have been using the 1066x 128 GB Komputerbay CFs (I think I had three or four different ones) but the raw recording performance was even more inconsistent than with the 1000x I own. Quite disappointing, but you get what you pay for. I am working with SanDisk Extreme Pro 160 MB/s since two months and they're the first CFs that work reliably for 1080 25p acquisition. Interestingly, there is a performance difference between ExFAT and FAT, which is way more reliable.

No problem here with recording raw with an external monitor (SmallHD DP4) attached via hdmi. Sometimes I'm even running 2 monitors (one larger for the director) in tandem, still no problems. The one thing you won't be able to do is properly display the 3x sensor crop on an external monitor. Also, use the fastest CF cards that fit your budget for trouble-free recording, especially on 128 GB + cards. I had no luck going 1080p on Komputerbay 128 GB... and eventually, Midphase is right, the safest thing is to test it out for yourself!

Updated to the latest version of ML for 5D3 1.1.3. yesterday, getting the same type of errors "Faild queued 139 /*or other number*/    faild 1 (Reqeued)" as mentioned by other users. I'm on SanDisk Extreme Pro 160 MB/S. By any chance, is there an explanation of the error msg available or a solution on the way? Thanks a lot for the effort.

Just to add my 2 cents, I tested various 128 GB CF-cards recently, among them Komputerbay 1050x, SanDisk Extreme 120MB/s, Lexar Professional 1000x and Hama 150MB/s, but the only ones that I found reliable are the SanDisk Extreme Pro 160MB/s. 64GB cards seem to perform a whole lot better (understandable), the 128 GB models work much faster as FAT and rather unreliable formatted in ExFAT.

Thanks for the quick reply, but might there be any chance to add such a feature in-camera?

Apparently I am not the only one who has stuck / hot pixels at higher ISO settings (on 5D3). This might be the result of higher noise clusters from the sensor that are interpreted as *fixed bright pixels* due to the original-sensor-resolution-to-1080p binning (or similar) process inside the camera.

Especially noticeable and annoying when filming in a dark environment (bright pixels spots on otherwise near-to-black background), it would be highly beneficial if the developers could provide a similar feature to Black Shading Calibration http://www.red.com/learn/red-101/black-shading-calibration.

As I am not a coder, I have no idea whether that is possible to implenet on a technical level, but it would make post work so much easier, especially when the footage is behind handed to someone else for further processing / editing / post.

Thank you and have a beautiful day!

Thank you for your answer! Fun thing is, on my camera they seem to appear randomly and not always at the exact spot. I have been trying out a plugin for FCPX and once replicated on a different clip the stuck pixels moved (by one pixel left / right / up / down). Might have something to do with the binning of the full sensor resolution down to 1080p... Would sending the camera to Canon be a solution for the problem? I understand that the raw recorded by ML is direct sensor information, is the re-mapping process before the raw extraction or after? I don't have any issues with the standard h264-recording, but high compression might as well blur the faulty pixels out.

To be a bit more specific, here is a link to some examples. The pixel dots stay where they are and move with the camera.
Running the manual cleaning option on the 5D3 does not solve the problem.

https://www.wuala.com/superhypernatural/Clients/ML/?key=J8U7ZlBe3jVU

I would be very thankful about suggestions.

The Magic Lantern raw recording workflow has openend a whole new world for me and it is spectacular to be able to work at such a high level of image quality for filming.

I have spent quite some time and money to find the right cards and workflow to record 1080p without dropouts and more or less process the clips in a reasonable amount of time.

Last week, I went to a bar to shoot a concert of a friend of mine and was faced with a rather dark environment, which forced me to shoot at rather high ISO settings on my 5D3 (ISO1600 - ISO 2000). That was the first time that I realized a number of light grey pixels that appear in dark areas, and I have been testing the camera for this annoyance ever since. It seems that those grey pixels appear at ISOs above 800, taking the long way (ACR) to process the DNGs sometimes takes care of some of them, but not of all and not every time.

Do other users also experience these issues? Any suggestions to get rid of them?

Thank you very much,

Martin