I have many quicktime files from GettyImages that are encoded in XDCam EX format 1440x1080 23.98fps. these no longer import and say that the format is unsupported on the latest versions of premiere/media encoder on either MacOS or Windows 10. it was suggested to me to encode using Handbrake but i am already transcoding to ProRes so don't want a third party making another file. These files all worked a number of versions back as i used them in another project but now they don't work or import! why has adobe drop the support for these files.
Here is an example https://shared-assets.adobe.com/link/c115358a-a20e-412f-5c71-23988a931168

I have many quicktime files from GettyImages that are encoded in XDCam EX format 1440x1080 23.98fps. these no longer import and say that the format is unsupported on the latest versions of premiere/media encoder on either MacOS or Windows 10. it was suggested to me to encode using Handbrake but i am already transcoding to ProRes so don't want a third party making another file. These files all worked a number of versions back as i used them in another project but now they don't work or import! why had adobe drop the support for these files.
Here is an example https://shared-assets.adobe.com/link/c115358a-a20e-412f-5c71-23988a931168

I have many quicktime files from GettyImages that are encoded in XDCam EX format 1440x1080 23.98fps. these no longer import and say that the format is unsupported on the latest versions of premiere/media encoder on either MacOS or Windows 10. it was suggested to me to encode using Handbrake but i am already transcoding to ProRes so don't want a third party making another file. These files all worked a number of versions back as i used them in another project but now they don't work or import! why had adobe drop the support for these files.
Here is an example https://shared-assets.adobe.com/link/c115358a-a20e-412f-5c71-23988a931168

I have seen countless posts of people requesting formats back. I would make a general inquiry to reinstate ALL previous file formats.

I get how the market works, I get how some formats might not be ideal or whatever. But as an editor, that should be OUR choice, why should Adobe decide what formats or codecs I am allowed to use? If you don't want to answer the questions in regards to older or less effective codecs and formats, just don't allow technical support for those specific items? Who thought it was a good idea to just remove them all together!? That must be the laziest and most closed-minded solution I have seen since in ages.

My temper is being tested to the max, every time I try to import a file format that in the past 5 to 10 years have always been supported. I don't care if it is not the perfect format for whatever medium YOU think I am going to make it for, I am the editor. I decide what I edit and I decide in which file format and with what codec.

I have tried installing the usual codec packs. Where they always used to work in previous versions of the Creative Suite, since this abomination called the Creative Cloud was released, none of these work anymore. I don't know what changed, but then again: I don't know what you were thinking either. Removing support for something that works perfectly fine has never been the pinnacle of intellect.

Now I got to get back to my project, as I now have a thousand files to convert through a program which isn't made by Adobe. I don't know which yet, I don't know how yet and I certainly don't want to think about the extra time this is about to cost me...

HEY, THANKS!

Having consistent problems with HEVC footage recorded with the Canon XF 705. This is not related to one individual computer and has been tested on many different systems to find the same issues consistently.

Bug description:

First of all the footage is incredibly laggy, it's impossible to edit from as it just freezes up after about 1 second of playback. We've tested this on even higher spec systems and the best we can get is some semi-smooth playback at 1/4 resolution with 1080p footage. If there is a way to improve playback of this footage that would solve the problem.

As a result, we have tried to implement a Proxy workflow. When attempting to create proxies we run into the same error every time on every machine which is as follows:

Frame substitution recursion attempt aborting after multiple attempts on file: FILENAME.MXF
Inserting black for frame number 0

This happens with ProRes, Cineform and DNxHR codecs. This causes media encoder to fail the export, on less powerful computers it actually causes media encoder to crash altogether. When trying to create proxies manually through media encoder rather than through premiere pro we run into the exact same issue.

We are able to create H.264 proxies, however, we then receive the error that the audio tracks do not match because our source footage Is often 4 track audio and we can only create 2 track H.264 files.

This makes it impossible to edit with the original footage and also impossible to create working proxies for the footage we are required to edit.

An example system that it has been tested on:

Processor: Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz (8 CPUs)
Memory: 32MB RAM
GPU: NVIDIA GeForce GTX 1080

All with the latest drivers and HEVC codecs from windows and Canon. We have been having these problems for the last few months and hoping it will be fixed with every Premiere Pro Update.

We have no issues working with HEVC/H.265 footage from other cameras but Canon says the issue lies in the NLE, not the codec. Please fix XF 705 HEVC footage in premiere pro.

Thank you.

So, we've finally had to move up to CC2020 (14.0.4), and proxy ingest names have been changed. You no longer have dimensions visible right there in the dialog box, but instead you're given options of Low, Medium, and High resolution.

Initially I thought that Adobe had finally implemented a change we've been asking for, where proxies are based off of the source media dimensions (say half res, third, quarter, etc), but no. It appears as though they're still sticking to specific dimensions (1280x720, 1024x540, etc), but they've just gotten rid of a quick and easy way to spot this by having the dimension in the preset.

Why? What is the point of making things less clear? Are we moving towards proxy sizes based off of source media, or...? If not, then can we just go back to the way it was before where it was clear what you were creating?