How can I deal with Pixel 7 Pro footage on Premiere Pro? Currently, my version is 23.0
When I import my footage video like is not supported by Adobe. I mean, is it serious? Adobe doesn't support HDR 10 Bit? If not, Media Encoder 2023 can help by converting this to a support file for Premiere so I can work with it. Handbrake, so far, got my footage washed out. I feel powerless in this situation! Looks like there is nothing that I can do. How does Adobe not support it? HDR 10 Bits has been around for a while now.
That phone footage is HLG, and also VFR ... variable frame rate. Pr is not great at working with VFR footage, as that means the number of frames per second constantly changes yet the audio stays constant. Pr is built as any NLE for constant number of frames per second.
So yes, converting that to CFR would probably be wise before importing to Pr. You might try ShutterEncoder, also free, also based on ffmpeg ... but with a more 'modern' UI than Handbrake.
Next, make sure you are using the latest video drivers for your card. And if Nvidia, that you are using Studio drivers and not 'game-ready' drivers. I've seen a couple posts where people had the same view as you post which gee, was fixed as soon as they changed to studio drivers.
And in most apps, if you are going to work with HDR footage, you need to do some manual color management work.
Thanks a lot for your reply. It's kinda frustrating in those situations!
from the screenshots, it looks like it can't decode correctly. try free shutter encoder convert prores and see if that fixes the issue.
To be honest, everything is sad with Adobe codec support. Now, more and more people are using third-party applications to record from screens to confirm their actions (regardless of the game or sites with programs) and Premiere does not support.MKV is a more modern codec than .MP4. Engineers have removed its support. The same trend has been with HEVC lately. Some files open, some don't. Files with the extension .I don't remember MTS with the index, it's also a problem, but not with everyone. The video opens, but with the music question. Users should not experience problems with codec support in the professional installation program provided. Than then this program benefits from simpler and undemanding programs for video cropping. There are no codecs there either. And what is the strength? Very weak support for more modern readable extensions.
Premiere's codec support seems to be rather broader than the other two major NLEs ... Resolve and Avid. Resolve doesn't do ProRes RAW at all ... and Avid doesn't do a fair number of codecs well or at all.
Yes, Pr doesn't support Matroska, which isn't normally used in any b-cast/streaming or even any web-bound work. Would it be nice if they did? Yea. Would it be nice if Resolve could work with ProRes RAW? Oh Hades, yes.
.MKV (Matroska) was supported up to version 15 of Pr, if I'm not mistaken. And there was also more extensive support for audio files. But then they refused. It seems that people only work with not very good in quality and performance .H264
MKV was apparently mostly "accidentally" supported in one version, a couple cycles back. Not by intent, but just due to how the coding for other things 'splayed over onto Matroska' as an engineer told me. But not because they made it workable.
And when the next series code did some natural changes, it no longer 'supported' Matroska. Not because they removed it, but because ... that it had worked for that series ... was entirely accidental.
As far as I know, the only audio removed, was after Dolby Labs demanded to have full-time access to the full Adobe accounting process to make sure that the licensing of Dolby AC3 audio was up to their approval. At that point, they told Dolby to pound sand and removed Dolby audio support. Except for what the OS supports, of course.
For what it's worth, with 40+ years running our own business, if anyone demanded full-time, live access to our entire accounting data, to use their product, we'd tell them to take a LONG hike from a steep cliff.
And the engineers are really kinda hacked at the camera makers, who keep coming up with new & exotic ways to encode H.264/5 in higher bit depths, bitrates, and doing so using all sorts of unique applications & stretches of long-GOP standards. It's probably good for the camera users. But makes the engineers have to continually update the internal code for working with H.264/5 media.
The engineers would like something a bit more ... well, standard ... lol