I've been using a PIX240 with my Epic on a feature, and we've been getting a lot of recording errors (green and magenta partial/intermittent corrupt frames)...
I've tried to figure out where the problem is coming from...originally thought it might be bad BNC, but I've tried multiple cables, different batteries, two different SSD drives and two PIX caddys...there never seems to be a consistent reason.
Some points of consideration:
we've used right angle connectors for SDI coming out of the Epic, as well as going directly from camera to PIX (no connectors)
powered from Sony L batteries, also d-tap to hirose connector
mostly held by the director or an assistant...have built a handle so that nobody is holding the pix directly or handling the caddy portion (I was hoping maybe it was due to an intermittent connection from caddy to pix, but alas, the problem persists). can it be bad drives? bad caddy's? RFI? handling? almost everything seems to have been ruled out from corruptions occurring under so many different variables (different cables, different drives, different pix caddy's, being handled or sitting untouched).
Our camera/PIX settings:
5K 2:1, 23.98, clean SDI feed, build 1.6.46
Pix recording same resolution as camera feed (1080p, 23.98), recording off SDI flag, using red filename structure, prores 422, firmware 1.03
recording to samsung 470 series 256gb drives
Has everybody who's been using this with Epic (flawlessly) been genlocking to camera? are there any other settings i'm overlooking? This problem is really killing our workflow, as we don't have a redrocket or the man/machine power to handle transcoding/syncing for post (very small film), and we thought the PIX would be our way to handle the edit efficiently...now it seems as though it's just adding to our work, as we now have to go through and double check what takes are corrupt and then organize/transcode certain clips.
Any insight is very welcome...very unhappy to have a device that should be an integral part of workflow that is not performing as needed or expected. It's disappointing, as it seems to otherwise be a very well-engineered device...I really can't wait until these problems are solved once and for all.
clintlitton AT gmail DOT com