Hi everyone,
I tried shooting RAW with my recently acquired 5D Mark 2, the problem is that some frames from my DNGs have strange pink bands going across them.
Shooting 14-bit RAW 2.35:1 at 1872x796, Komputerbay 64GB 1050x Card, November 1st Nightly Build I believe. Unpacked through a few methods, including raw2dng.exe
Here is a sample of a DNG and what it's supposed to look like:
(http://i.imgur.com/V1mhfrP.jpg)
If anyone knows the solution to this, I'd greatly appreciate it. Thank you!
.
Have a 5d2 and never seen that.
I think you should try reinstalling ml and see if that takes care of it.
I saw the same stripes on some of my footage the other day. Have a 5dmrk3 on a late october build. Have used ML raw on four different small docus lately, and this one shooting day is the only one that has the stripes. Anyone know how to avoid it?
How do you "reinstall" ML? Just put a new version on the SD card, or do a new bootflag or something?
EDIT: This was on a new batch of KB64 cards. They otherwise perform great (no indication that anything is off). Could this be CF cards related?
How about trying a more recent Nightly build.... you guys are running builds that are almost or over a month old. Things move fast around here.
Quote from: Stedda on November 24, 2013, 02:24:15 PM
How about trying a more recent Nightly build.... you guys are running builds that are almost or over a month old. Things move fast around here.
Sure, will do. But do people using this for work actually use the very latest nightly build at any given time? I would think you stick to the ones that works safely..?
That would be fine but I don't think the DEVs look at bugs from month old builds.... you could also go back to your old build anytime.
Ok, thanks. But is it possible this is a "bad sector" on a cf card? I would think the entire recording would stop if that was the case..right? Always nice to narrow down the causes..
Could be.. I've never seen anything like it on my 5D III but I stay up to date every couple of days...
Quote from: hkarlsen on November 24, 2013, 02:31:13 PM
Sure, will do. But do people using this for work actually use the very latest nightly build at any given time? I would think you stick to the ones that works safely..?
People shouldn't use a hack for work and the developers are very clear about this fine point. However I can see how ML's stability can tempt people to feel overly confident about it.
Here's the thing...nowadays the nightly builds are being updated, but not at the same frantic pace as a few months ago. Most of the new improvements concern optimization for .mlv files.
Some people are still using builds from July, and that's plain stupid. However if you're using a build from November 1st, it shouldn't be too different than one from today.
I don't think it's a build issue (although if you're going to re-install, you might as well update to the latest). The way to re-install (at least the way I do it) is this:
1. Format the card in camera
2. Run the Boot script to prepare the card for in-camera booting
3. Drag manually onto the card the ML folders and the auto exec.bin
You'll need to re-configure your ML settings and modules, but it's the safest way I know to make sure that the ML install is clean.
The only time I've seen this type of problem on my 5D3 has been when I was shooting in Crop mode....I suspect the errors are results of data not being written quite fast enough on the card and becoming corrupted here and there.
Quote from: Midphase on November 24, 2013, 06:42:04 PM
The only time I've seen this type of problem on my 5D3 has been when I was shooting in Crop mode....I suspect the errors are results of data not being written quite fast enough on the card and becoming corrupted here and there.
Thanks, I see, so basically there's no hope in salvaging these?
Quote from: Kharak on November 24, 2013, 02:15:24 PM
Have a 5d2 and never seen that.
I think you should try reinstalling ml and see if that takes care of it.
What build are you on? Are you recording the same specifications as me? Also what card are you using? I think if I could narrow it down it would help! Thanks
Quote from: Tai.Fighter on November 24, 2013, 10:12:07 AM
Hi everyone,
I tried shooting RAW with my recently acquired 5D Mark 2, the problem is that some frames from my DNGs have strange pink bands going across them.
Shooting 14-bit RAW 2.35:1 at 1872x796, Komputerbay 64GB 1050x Card, November 1st Nightly Build I believe. Unpacked through a few methods, including raw2dng.exe
Here is a sample of a DNG and what it's supposed to look like
If anyone knows the solution to this, I'd greatly appreciate it. Thank you!
I had this problem once on my 5D mark ii, back in July
I recommend that you use the Oct 24 built from A.D. Hack built for the 5D2
https://bitbucket.org/a_d_/laboratory/downloads/af9a60fe144d.zip
This one is the Best built to date and completely Stable for Paid Work.
Plus I always Format my card in Camera before I shot raw, every time.
and use raw2cdng to extract.
Use Lexar 1000x 32,64 GB Max. size 1872x1250 23.976p for about 800 to 1000 frames
also Sandisk 90MB/s at lower frame size(1872x936 @23.976p ;)
Edit: I noticed that in ACR, the dng is set to 8bit, change that to 16bit in advance pulldown menu.
Quote from: reddeercity on November 25, 2013, 02:34:28 AM
I had this problem once on my 5D mark ii, back in July
I recommend that you use the Oct 24 built from A.D. Hack built for the 5D2
https://bitbucket.org/a_d_/laboratory/downloads/af9a60fe144d.zip
This one is the Best built to date and completely Stable for Paid Work.
Plus I always Format my card in Camera before I shot raw, every time.
and use raw2cdng to extract.
Use Lexar 1000x 32,64 GB Max. size 1872x1250 23.976p for about 800 to 1000 frames
also Sandisk 90MB/s at lower frame size(1872x936 @23.976p ;)
Edit: I noticed that in ACR, the dng is set to 8bit, change that to 16bit in advance pulldown menu.
Thank you so much! Hopefully this works out for me. You are a good man, sir.
Quote from: reddeercity on November 25, 2013, 02:34:28 AM
I had this problem once on my 5D mark ii, back in July
I recommend that you use the Oct 24 built from A.D. Hack built for the 5D2
https://bitbucket.org/a_d_/laboratory/downloads/af9a60fe144d.zip
This one is the Best built to date and completely Stable for Paid Work.
Plus I always Format my card in Camera before I shot raw, every time.
and use raw2cdng to extract.
Use Lexar 1000x 32,64 GB Max. size 1872x1250 23.976p for about 800 to 1000 frames
also Sandisk 90MB/s at lower frame size(1872x936 @23.976p ;)
Edit: I noticed that in ACR, the dng is set to 8bit, change that to 16bit in advance pulldown menu.
So youre not using exFAT formatting on the card? The camera formatting will make it FAT, right? Its a big one for me to have non-split files. If the problem is related to write speed as someone mentioned, Im still thinking its a card issue. What is peoples go to method for card testing outside of the benchmark function? Just shoot a card full, and speed through it in Resolve etc?
5D Mark II is Fat32 system, it can not work with exfat!
That why the file are in 4GB spanning.
I never test my cards with benchmark test,
Start at smaller frame size full card then
Keep moving up on frame size until you the
Size you want.
Some times you need to brake in the card.
I had to do this on my 64GB Lexar 1000x .
There is no other way to record raw on
5d2. If you do not want spanning file
Then stop before the 4GB mark :)
Quote from: reddeercity on November 25, 2013, 06:19:32 PM
5D Mark II is Fat32 system, it can not work with exfat!
That why the file are in 4GB spanning.
I never test my cards with benchmark test,
Start at smaller frame size full card then
Keep moving up on frame size until you the
Size you want.
Some times you need to brake in the card.
I had to do this on my 64GB Lexar 1000x .
There is no other way to record raw on
5d2. If you do not want spanning file
Then stop before the 4GB mark :)
Forgot to mention I am on 5dmrk3 where exFAT works beautifully. But will keep your tip in mind :)
I have seen this type of thing several times when I get a full memory card during recording. Other than that I have not seen anything like this since the very beginning of raw. I am tempted to say it is a faulty card that is corrupting some of the data.
Quote from: Midphase on November 24, 2013, 06:42:04 PM
Some people are still using builds from July, and that's plain stupid.
Cannot agree with this statement. If an old build works perfectly fine for someones purposes then there is no urgent need to upgrade, since new iterations can also introduce new issues.
However since the topic starter posted this issue I recommend changing ML version and try different CF card.
I've been using the latest nightly builds for the 5D3 and had this happen to me a couple times. Have not isolated why yet...
Quote from: spnsir on November 27, 2013, 10:09:30 AM
I've been using the latest nightly builds for the 5D3 and had this happen to me a couple times. Have not isolated why yet...
Interesting. What type of cards are you on?
Number all of your cards, then when copying your files to the HD include the card number somewhere - folder name / text file. I suspect this is due to a faulty card, if you can keep track of which files came from which card you may notice a pattern.
Quote from: pascal on November 26, 2013, 09:36:02 PM
Cannot agree with this statement. If an old build works perfectly fine for someones purposes then there is no urgent need to upgrade, since new iterations can also introduce new issues.
I can agree that if you're using Nov. 26 build, maybe you don't really need to update to Nov 27, but since July there have been such substantial improvements which have made the code much more solid and less error prone. If an bug is accidentally introduced, it's usually taken care of fairly quickly.
Since July, ML has improved the was the buffers are handled resulting in better data writing even with less than great cards, it has improved playback substantially adding not only near-real time playback but also color high res playback. ETTR has been added and improved, peaking has been optimized, support for the new .mlv format has been perfected, the interface has been substantially refined resulting in an easier to read and access GUI. The list goes on and anyone sticking with a build from over 3 months ago really should consider updating to a newer build.
Quote from: hkarlsen on November 27, 2013, 03:03:13 PM
Interesting. What type of cards are you on?
Komputerbay 64GB 1000x.. Using two cards.. Haven't isolated the problem to either one yet
I believe it's caused by our incomplete understanding on how EDMAC works. I don't think it has anything to do with the card.
Lowering CPU usage might help (for example, turn off GlobalDraw).
besides cpu, I think AE might touch the edmac too. turning it off helps a bunch with write speed on this generation of body. WB didn't have as much of an effect. of course the side effect of killing AE is you lose all exposure control while recording.
I got the cut up/pink frames from CPU more or less or canon drawing refreshing... i.e. turning on color preview full time.
Quote from: a1ex on November 29, 2013, 02:39:32 AM
I believe it's caused by our incomplete understanding on how EDMAC works. I don't think it has anything to do with the card.
Lowering CPU usage might help (for example, turn off GlobalDraw).
Is there a way to let Globaldraw kill itself upon pushing rec? I really need it before, but not really during recording.
On mine there is. MLV_REC has it too I think.
Quote from: 1% on November 29, 2013, 04:27:35 PM
On mine there is. MLV_REC has it too I think.
Hmm. You mean there's a module for this function? Could you please share how you make globaldraw hide on rec?
There is no module for that, what he means is that it also works with .mlv recording.
I think you press Q under your Global Draw settings and you can access the various settings which should allow you to set it as enabled only during preview mode and not under recording.
Quote from: Midphase on November 29, 2013, 09:14:21 PM
There is no module for that, what he means is that it also works with .mlv recording.
I think you press Q under your Global Draw settings and you can access the various settings which should allow you to set it as enabled only during preview mode and not under recording.
I cant really get this to work the way I want. Quickreview is only displaying the rec indicator upon recording, nothing else. Liveview mode is not different from "ON.all modes" as I see it. Any tips? I found somewhere to clear overlays upon recording, but that just gives me a clean 3:2 frame when recording.
Thanks
Hello All,
I have a new 5D Mark III and am experience similar looking glitches but much worse (pictured below). They are vertical pink glitches affecting SOME rare frames of SOME clips. I am using a very recent build of ML (Feb 28th-ish).
Interestingly MLV Dump (from Feb 28th) run from a terminal STOPS the process when it reaches the first frame that has pink glitches this and reads: "[ERROR] File ends in middle of a block". MLV Mystic just seems to power through and spit out the problematic frames. A1ex responded earlier in this thread with. "I believe it's caused by our incomplete understanding on how EDMAC works." Can someone help me understand a way to fix?
I am using:
Komputerbay 64GB 1050X (shot two other projects in stock h264 with no corruptions or problems)
Regular Canon Battery
Already tried sRAW image quality setting trick.
Been reading lots of success stories of "terabytes" of Raw footage from 5DM3 with no problems, so, scratching my head. Thanks!
(http://abstractmall.com/blakekimmel/images/magic-lantern-pink1.jpg)
(http://abstractmall.com/blakekimmel/images/magic-lantern-pink2.jpg)
Quote from: blakekimmel on March 04, 2014, 05:58:35 AM
I am using:
Komputerbay 64GB 1050X (shot two other projects in stock h264 with no corruptions or problems)
Regular Canon Battery
Already tried sRAW image quality setting trick.
Been reading lots of success stories of "terabytes" of Raw footage from 5DM3 with no problems, so, scratching my head. Thanks!
In my tests, I am beginning to find .mlv to be more prone to these types of issues than .raw. I don't know why that is, but what I can tell you is that while .raw has been a very stable format almost since the very beginning (and I have indeed shot terabytes of video with it), .mlv is causing some strange corrupted frames with more frequency than I'd like.
I would advise you to try using .raw and see if the issues go away. Maybe I'm wrong and maybe this has absolutely nothing to do with .mlv, but all I can say is that before .mlv I never ran into the very type of corruption that your post shows, and after switching to .mlv it has happened a couple of times.
Today I participated in a massive camera shootout, and I used .raw. No issues and no corrupted frames whatsoever.
I read it here and in the other thread. I really like to see the difference shoots in the really interesting cameras to compare the result, if you can of course provide a link or demo!
The guys that ran the shootout will publish it on Vimeo when the time comes, we were shooting all day and I'm sure it'll take them some time to sort through all of the takes.
As much of a fanboy as I am of ML raw, I don't expect it to have as much of a fighting chance against the likes of the Alexa or the RED Epic with the Dragon sensor. Without having seen all of the footage, I can tell you that dynamic range-wise and low-light sensitivity-wise the 5D3 raw will likely outperform the Blackmagic 4K (particularly considering that the Blackmagic wasn't recording in raw but in ProRes).
Quote from: Midphase on March 07, 2014, 08:54:41 AM
The guys that ran the shootout will publish it on Vimeo when the time comes, we were shooting all day and I'm sure it'll take them some time to sort through all of the takes.
As much of a fanboy as I am of ML raw, I don't expect it to have as much of a fighting chance against the likes of the Alexa or the RED Epic with the Dragon sensor. Without having seen all of the footage, I can tell you that dynamic range-wise and low-light sensitivity-wise the 5D3 raw will likely outperform the Blackmagic 4K (particularly considering that the Blackmagic wasn't recording in raw but in ProRes).
I read about BMC 4 K and the limitations in low light. Even the sensor size it's a big problem for the lens - 20% less than APS-C size.
Alexa it's really fantastic. Amaizing even for me than Red epic. I used for tv commercials, rented.
But, well, 5D .RAW it's a big deal for the moment.
Talking to the cinematographer of the shoot, the general feeling is that different cameras are suited for different things. They are just tools, and in the hands of the right individual, they are all more than capable to get formidable results.
I noticed these weird frames after updating the build. I'm using Feb08 and it works fine, no colored frames. When I try to update I get at least one or two, after one minute of mlv video. (it doesn't happen with .raw). I have to test more the latest builds trying to disable some feature and find out which one is causing the problem
The problem with nightly builds is that some seemingly innocent change or bug fix could open up some issues with other parts of the code. It usually takes a few days to weeks before people start noticing the incorrect behavior.
I would like to propose a system not dissimilar to what Tragic Lantern has done here:
http://www.magiclantern.fm/forum/index.php?topic=7987.0
They point to certain builds that are stable or semi-stable, as well as the nightlies for those who are more adventurous.
As of right now, there is no system in place (at least not that I know of) for members to determine which of the more recent nightlies has been deemed fairly stable. It's a bit like playing the lottery, and going backwards to an older build isn't necessarily any safer where for instance the Nov.12 might be great, but the Nov.13 might have introduced an issue that wasn't picked up and addressed until Dec.2.
You guys understand what I'm trying to say?
Thoughts?
Quote from: Pierluca72 on March 08, 2014, 11:48:33 AM
I'm using Feb08 and it works fine
Sorry I didn't specify that goes for the 5d3
Quote from: Pierluca72 on March 08, 2014, 11:48:33 AM
I noticed these weird frames after updating the build. I'm using Feb08 and it works fine, no colored frames. When I try to update I get at least one or two, after one minute of mlv video. (it doesn't happen with .raw). I have to test more the latest builds trying to disable some feature and find out which one is causing the problem
Thank you for the response! I feel better now that I have read this since those problems were my first 5D3 raw experience. I posted similar post in MLV Mystic thread and read someone who just recently started using a build from very late February and was getting similar color frames but previously had no problems. Thank you for specifying Feb 8th as well, I will be going back to that build and doing many tests before a huge trip to Haiti where I want to shoot some RAW video.
Would LOVE anyone elses input into this, if anyone has these frames and finds a new nightly build this month that fixes the problem, I would love to upgrade but until then I must use a better build with no problems. I only shot 20 minutes of video with my late Feb build and had many instances of problematic frames.
QuoteYou guys understand what I'm trying to say?
Thoughts?
Yes please, list the most stable builds and then list if something broke. I can't test everything myself, same goes for ML main. Also something may work great on one camera but have strange issues on another.
Just shot about 10 clips with a FEB 8th build that Pierluca72 sent me. Processed straight to DNG with MLV Mystic. Got NO glitch pink color frames or problems. My late FEB. build had many problems when this much footage was recorded. Looks like build to build these type of glitch frames come and go. I am wary of double posting the problem elsewhere, so I am only writing it here.
Excuse the excitement! Just got a 5DM3 two weeks ago and happy to start taking RAW to my real projects now.
Installed ML on a 5D 3 a couple of days ago... I have two 128 1050X cards with a custom Komputerbay firmware to operate / install ML on a Canon 50D. I get better write speeds in FAT than EXFAT. One of these cards appears to be about 5MB/s slower than the other. Anyway, I consistently get pink frame noise when shooting with Global Draw Turned on... When Global Draw is turned off, I will eventually get corrupt frames... It doesn't take long... I believe it to be related to the card not writing properly with the build I am using.
Truly honing in on workable solution... Currently processing about 15 minutes worth of vid in DaVinci. First time I've seen the 5D 3 in good lighting shooting MLV... Really makes you want to make it work. :-) Hope this helps.
Thanks for all the help and effort. It really comes through in the image.
I just installed nightly from march the 15th, and shot through 6x 64 GB Komputerbay 64 GB (two different batches) and 2x Lexar 64GB
Firmware 113
HDMi monitor connected
raw_rec module, not mlv_rec
Global Draw off when recording
I put the DNG through Resolve and outputted Proreses that I watched. Did not see any colou-strips frames. I really believe this to be connected to Global Draw. I might also have been corrected in the nightlies, since my latest install was from November I think.
Since Global Draw doesnt overlay correctly on HDMI out (it "enters" the actual frame, making it difficult to frame correctly) I want it gone on recording anyway. But there is still (?) no way of making GD kill itself upon recording. I saw this feature beeing enabled in mlv_rec, but I am staying on raw_rec for this next shoot at least. Or have I missed something?