Mlv files ok on camera playback, pink frames on MLVApp

Started by biolimbo, April 15, 2019, 09:36:56 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

biolimbo

Hi,
I am running magiclantern-crop_rec_4k.2018Jul22.5D3123. I use KB 64GB 1066x, and didnt have any problems for the first 2 weeks using MLV Lite 14 bit lossless, however i started getting pink frames and odd glitches within the same workflow i used before. I dont know much about hex editing and stuff, and even tried to use mlv dump via MLV batch, and this is what i get:





here is a 2 seconds small "corrupted" mlv file along with the dngs and a video prooving the video plays ok in camera:

https://drive.google.com/drive/folders/1P17-3dHpTKCjVz67RWUqHABklSwI8j04?usp=sharing

I have 70 gb+ of "corrupted mlv files" i would love to know if they can be fixed, and also what i am doing wrong. I read all the threads i could read and was thinking to downgrade to 1.1.3 but the fact that i can have an hdmi monitor along with the on screen camera is very important for me.

What are your thoughts, what should i do? did i just lost all of that material?

Thanks Guys!

2blackbar

Get some faster card, that solves pink frames in most cases, its not worth to struggle like this with barely good card .As for the footage , just conver to raw and look them up in photoshop or gimp to see if frames are really corrupted.14bit lossless does not have big advantage over 12 bit, i couldnt find any in shadows and highlights and colours were equally good, and 12bits footage  takes up less space so camera should produce less pink frames.

masc

I don't think the card is the problem. KB 64GB 1066x is very fast, I have the same and it works fine. You wrote you use a external monitor. This should be the problem. Have you tested without monitor? If a file is corrupted, you won't get it fixed in most cases.
5D3.113 | EOSM.202

MartijnR

Hi there,

I am having the same issue, similar glitches ones in a few seconds. Using several fast cards, all containing these errors. Would be great to know if there is a solution for this.

I have been using the 113 built, and because of the errors also tried it with the same built as you describe (magiclantern-crop_rec_4k.2018Jul22.5D3123). Similar results unfortunately. I am not using an external monitor.

Thanks a lot,

Martijn