-
going crazy with large files from varicam 35 in ppro cc 2014
I’m at my wit’s end here trying to edit some varicam 35 footage I have to turn in soon.
If anybody can help me figure out what’s going on here I would greatly appreciate it.
The footage is in avc-intra4k422 format, 50 fps, UHD.
Some of the files are large, for example 280GB.
From what I’ve read this codec runs about 800mbps, so approx 100MB/sI was worried that my raid was too slow, so I”ve upgraded it, and now atto windows disk benchmark is reporting speeds around 1100MB/s for read (writes are quite slow though). I’ve uploaded atto disk benchmark results for the array below. It’s a sonnet DX800 raid expansion enclosure (the newer ones with 6g), but only an R380 raid controller. Still, the read speed seem ok, especially as I’m only trying to play back one stream at a time.
For some reason blackmagic speed test gives me nonsense results.Starting playback, or navigating to different parts of clips lags for over a minute before I can play.
Then playback is smooth for a few seconds, then gets choppy.
Looking at perfmon, it really seems like the the delays and choppiness are related to disk activity, because the disk activity on the raid array completely maxes out whenever I’m having problems.PC specs are as follows:
MB : asus z87 deluxe
haswell core i7 4770K 3.5 ghz
ram 32gB
system disk : samsung ssd 840 series
graphics gtx 960Can anybody point me in the right direction for troubleshooting ?
Here’s what I’m thinking about:
– there could be something about varicam 35 files in premiere that’s buggy. Or something about very large files. I know from adobe support that there’s a bug in media encoder that affects varicam files, so maybe it also affects premiere ?
– maybe I’m reading the situation wrong, and I need a card like blackmagic 4k extreme ? and it’s not a disk performance issue ?
– maybe playback needs better write speeds for some reason ?
– maybe atto is giving me fake rosy read speeds, and my actual speeds are lower ? Or premiere is trying to read the data in a size/way that doesn’t let the raid gives its best performance ?Any ideas would be very welcome !
Thanks,
sam

