Why are Phantom camera .cine files all of a sudden pixelated?

[jackb71338586]

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

[joeydoyle]

I'm running into the same issue. Phantom .cine files have bright "dead" pixels in Premiere despite showing up without any issue in Resolve.

[jackb71338586]

Yes, I noticed it looks fine in Resolve. Not sure how to get a answer on this. Maybe I have to load up an old version of Premiere?

[Brian Mulligan]

Same issue here.  lookslike I'll have to go to Resolve.

[Morten Corfit22608037wubj]

Yes - same issue here - looks good in Resolve but at least 5-6 dead pixels in Premiere Pro and AME

[Morten Corfit22608037wubj]

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.

According to this document https://phantomhighspeed.my.salesforce-sites.com/servlet/fileField?id=0BE1N000000kD2i 

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.

[Kartika Rawat]

Hi there! Sorry about the issue. Which OS are you using? Also, let us know the exact version of Premiere Pro.

Thanks,

KR

Moving to discussions from bugs for troubleshooting.

[jackb71338586]

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

[Kartika Rawat]

Thanks for the details. Can you share some sample files with us to test and share the download link with us: https://helpx.adobe.com/in/creative-cloud/help/share.html

^KR

[jackb71338586]

Hi - Here is a link to one of the clips

https://shared-assets.adobe.com/link/0c5f927b-8f77-475d-5a20-133b48856558

[commonpoet]

Any update on this? I am experiecning the exact same thing.

[jackb71338586]

I found another project with the same problem. It appears to be in the blacks only. There has to be more people experience this issue?

[태호33358071xn5m]

I'm experiencing the same problem.
We desperately need a solution

[roberth92950775]

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.

[andreasj35521332]

We're having the same problem as well. Up until now we've been able to bypass the problem by opening the intel version of premiere via the creative cloud app (found when klicking the three dots next to the open-button by the premiere pro app in creative cloud.) BUT!! This workaround seems to have dissapeared with the latest versions of Premiere Pro. D'oh!!

[Quenton5CB2]

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?

[JLSM]

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.