Horizontal Glitch w ML

Started by Meca, January 06, 2017, 12:09:55 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Meca

What's the name for this kind of horizontal glitching? Is there any solution or discussion?

I think it's due to quick movement of a 5d2 while shooting ML. It affects a small number of frames but can make a shot unusable. Perhaps the information stream from the sensor is disrupted. Sometimes it happens a second or two after moving. I've looked around but I can't figure it out.

Is it a sensor problem w my camera alone or does it affect other 5d2 & 5d3's running ML?

All footage shot 23.976, 1856 x 844, converted w MlRawViewer to PR422 HQ, the glitches are all visible on the orig raw footage. It's a version of ML from late 2015 so am updating all my cards now to the latest ML builds.   

Thanks




Meca

Bump. No one recognises this fault :( ?

reddeercity

Yes it shearing - tearing , Did you have a external HDMI monitor connected ? look here . Have you tried a different extractor ?
MlRawViewer is obsolete MLVFS Cross platform (Win/MAC) MLVProducer (Wins but runs on MAC with Wine ) , Raw2Cdng (Wins) and mlv_dump
are the only one I know that are up to date and maintain regular .

Meca

Thank you for your reply David, it is much appreciated.

I am using a Viltrox DC-50 monitor, so I will test using "force-VGA" and other possibilities. It's a pity also that the monitor image won't display optimally, (it's slightly smaller that the full screen size) but I understand that it's an inherent problem with Canon not solved by ML.   

Regarding MLVFS, unfortunately I don't use Premiere CC and Resolve is too slow on my 2009 Macbook Pro. MLV Producer via Wine hasn't "compiled" or created an app that can launch - Probably an error somewhere on my part, I tried to follow the wineskin process but it seemed to have many variables in the creation process. MLRawviewer is an expedient enough workflow solution to create Prores 422 HQ (using the the small code mod I found in this forum).

Thank you again. I'll test and report back any findings.