Hi - about two years ago I was working with some Phantom camera files. Everything worked great. I had to revisit the project today all of the .cine source files look really pixilated in the blacks
Same issue here. I thought it was some sort of clipping indicator for crushed blacks – but it appears in the exports too! Does anyone know whats the latest version of Premiere you can use without getting this error?
Same issue here in Premiere Pro 25.1 - MacOs Sequoia 15.3 - Apple M1 Max - I've also detected that even though the .cine clips were recorded at 25fps, Premiere Pro imports them at 24fps.
Having likely the same issues here. Seeing it across numerous phantom clips - some recent, some older. These clips played back fine for me in previous versions of Premiere on Intel processors; current issues are in the latest version of Premiere and have been seen on M2 MacStudio and M1 MBP - issue appears to be on M chip machines. Confirming that clips do indeep play back and debayer correctly in DaVinci Resolve. Have a library of hundreds of phantom clips would prefer not to have to bake a bunch of transcodes.
Just a followup on this: I have looked through older footage from our Phantom Camera an the dead pixels are consistent, meaning they are in the same place throughout, so it seems to be actual dead pixels on the sensor and not some kind of render error.
on page 35 the camera does not compensate for dead pixels. It is entirelly up to the decoding software. So it seems that Resolve has this in place but not Premiere Pro.
Hi - Thanks for your repsonse - I'm running OS Venture 13.4.1 & Premiere 23.60. I attached an screen shot of how the phantom footage looks when loaded in premiere. Thanks for your help
AdChoices