Messages

I hadn't even considered that. Just checked, though, and nothing was recorded to the SD card.

I'm fairly certain there will be no recovery of this footage, but my other question remains: Isn't there a way to prevent this from happening in the future? I had "Reserve card space" turned on, which is supposed to prevent data loss on a full card. Obviously it didn't help here...

It was a couple of minutes into the clip, which is why this surprises me. I would have expected to see some indication of data, but there is nothing.

Yes, all of the files, including the .MLV.

I've seen solutions to fix this problem when recording .RAW files, but not .MLV. I thought maybe the same technique would work (editing the footer in a hex editor), but no luck figuring out how to do so thus far.

My issue is this: I was recording several clips to a 64GB card. During the last clip, the card ran out of space and (obviously) stopped recording. That last clip was split into 10 files (M18-1239.MLV, M18-1239.M00 - M08). When I copied all of the files from the card to my computer, I noticed that they all had file sizes of zero bytes. It seems to me that there is nothing to recover, but I'm holding out hope that they file size is simply reading incorrectly due to whatever is causing the corruption.

So my question has two parts:

1) Is there anything for me to recover and, if so, how can I do so?
2) How can I prevent this from happening again? I thought there was some sort of buffer built in to ML that would stop recording and close a file before running out of space on the card. Is that not the case?

I'm using ML Nightly.2015Apr28.5D3123
5D Mk III
Lexar 1066x 64GB CF cards

Thanks in advance for any enlightenment.

Thank you for the quick reply. Your answer to #1 makes perfect sense. I agree that the complaint is sort of silly given your explanation. As for #2, I don't even know what to make of that or how I can alter the tm_mon field. I'm on a Mac. Is this something I would have to do in Xcode? Terminal?

One final question: I shot this footage at 29.97, but I want it to play back at 23.98. In the MLVFS window, I see an option to override the framerate. When I change it to 23.98 (or 23.976), PPro interprets the footage to be 23.000fps. If I use 24 in MLVFS, PPro interprets it at 24. That could work, but I'd still rather have it be 23.98. Am I better off leaving it at 0 and doing Interpret Footage in PPro? Will that cause issues in Resolve?

Thanks so much, and again I apologize if these are basic questions.

**Correction to above: Resolve sees the footage as 23.98. When I render proxies, PPro also sees them as 23.98. Looks like we're OK here; just a glitch with the way PPro sees the original DNGs.**

I just found this a few days ago, and I've been using it re-process some MLVs that were full of bad pixels. The "bad pixel fix" feature alone is going to save me hours of post on this music video, so thank you!! I have two questions that I haven't been able to find in the forums:

• First, when I use MLVFS, the resulting DNGs are noticeably darker than the DNGs I get out of RAWMagic. I didn't even know that was possible, because I thought a DNG was a DNG (I'm new to shooting RAW, so forgive my ignorance if I'm way off base here). Is there something that either MLVFS or RAWMagic is doing to process these that could affect their levels?
• Second, the DNGs seem to have the wrong date. The year, day, and time are all correct, but the month is one less than it should be. For example, footage that I shot yesterday (7/29/15) is showing up as 2015-06-29. I double-checked the date setting in my camera, and it is correct.

Neither of these is a big deal; I'm obviously color-correcting anyway, and the dates aren't critical. I'm just curious.

Thanks again!