Hi there,
I had a colleague accidentally set a DPX sequence copying between two storage devices, landing directly into an automated RAWcook transcode path this week. While it was copying across the sequence was RAWcooked encoded taking about 90 mins. The RAWcooked encoding didn't fail in this instance, even though there would have been additional images dropped in. Not sure if this check would have existed and is faulty, or if this is the first time it's cropped up.
Might be a useful addition in the encoding --check feature though for odd cases such as this.
We're encoding on version 24.11 and most part it's working like a charm! Thank you team.
Hi there,
I had a colleague accidentally set a DPX sequence copying between two storage devices, landing directly into an automated RAWcook transcode path this week. While it was copying across the sequence was RAWcooked encoded taking about 90 mins. The RAWcooked encoding didn't fail in this instance, even though there would have been additional images dropped in. Not sure if this check would have existed and is faulty, or if this is the first time it's cropped up.
Might be a useful addition in the encoding --check feature though for odd cases such as this.
We're encoding on version 24.11 and most part it's working like a charm! Thank you team.