Thank you. After doing this and importing the file again, the red triangle appeared. However, when clicking on it, an Events dialog box comes up with no reason provided for the error. However, when the triangle initially appeared, a pop up window said "Unable to load video ... because file contains more than one image descriptor." What does that mean?
Hello guys, as the above picture shows, my unedited colour in the preview looks different from the source video file. Why is it like that?
If you select the error in the Events panel, then you should see the Details button activate and clicking that will list the same error you saw with the pop-up. What this error means is that the file has been marked with more than one codec image descriptor, which can be confusing to Importers.
I believe that these type of files would open in earlier versions of Premiere Pro, such as 11.1.2 or 11.1.4, via the legacy QuickTime 7 era/QuickTime 32-bit. Recent versions of Premiere Pro dropped the legacy QuickTime support, so these file types are not currently supported with our native Importers. The error you see now is in place to inform that the Import failed and the reason why (which could be a bit more robust in the details).
A possible workaround is to open he ProRes files in Premiere Pro 11.1.4 and export them with the exact same Export Settings (choose Format: QuickTime and Preset: Match Source (Rewrap)), which should smart render. This exported file should then work in current versions of Premiere Pro.
Bit more information on smart render: Smart rendering in Premiere Pro
Thanks. If by selecting you mean double click on it. I did and do see the error I saw before. I guess I need to download that earlier version of Premiere (you are correct that the file opened fine in a prior version of Premiere). I'll figure out where to do that and try what you suggest. Thanks again.
I am experiencing the same issue. Just happened today, March 5th. The volume output wasnt working on my Mac, so I researched and it said to update. I updated and now I am getting a white screen whenever I try to open Premiere. I hope there is an answer - I have a video project for a client expecting next week
I am completely blown away by this issue...
Top line is a frame exported directly from the timeline. Bottom line is a still from what the actual video looks like after the export. The text almost looks as if it has a stroke applied to it which it does not as you can see from the top line.
I have tried every possible combination - ProRes, H.264 at 50Mbps, Checking "Render at Maximum Depth" & "Use Maximum Render Quality", imported the text as a PSD, used the title graphics in Premiere, upscaled the text to 4K and then downscaled back to 1080p, using Mercury Software only, using GPU acceleration (OpelCL).... I just don't know what else to do. I've tried it all. My pixel aspect ration is set to square pixels and fields is set to "no fields (progressive)".
Please help!! I need to deliver this video to my client ASAP and I cannot deliver garbage like this.
Hi everyone,
I've recently run into an issue on Premiere Pro CC 2019, I believe Version 13.1
I'm currently running GPU Acceleration (Metal) and I've also tried running OpenCL - however neither are helping in this scenario. Every time I apply an Immersive Video effect, I get the red banner telling me that GPU Acceleration is Required for the effect to render correctly. I've reserved as much RAM as possible for PP and all my settings are set so that this shouldn't happen.
I'm running a 2018 MacBook Pro 15" - i9 Processor, 32GB RAM, 4TB SSD so spec wise we shouldn't have a problem.
Does anyone know a way around this? I've attempted to downgrade PP to an older version but the issue is persisting.
This is frustrating. My 2009 Mac Pro was running Premiere great with an Nvidia graphics card. Then Mac stopped offering OS updates for 2009 Mac Pro so I'm stuck in El Capitan. Now Premiere not supporting El Capitan in updates so my fantastic old computer is now defunct for editing in Premiere.
So I get a new MacBookPro with eGPU. Mac won't support Nvidia cards in eGPU so had to get AMD. With eGPU connected Premiere won't show clips and crashes when exiting the program. Not ideal and many reports of this.
Resolve works fine with new setup and leverages the AMD card well. Have had to switch projects to Resolve until Apple/Adobe can (maybe) work this out. If not sorted soon, will be switching permanently and cancelling CC subscription.
Hi - I've installed 12.1.3 which ran better than the other iteration but still left a handful of clips unlinked and unlinkable. I tried the fix I mentioned above but with this version it didn't work. I'll try the other two fixes, deleting cache and changing media folder
How is this possible? Is this a common problem? I can't understand why linkability through successive updates is a minor matter for developers. I'm still opening old projects in Final Cut Pro 7/X for regular clients.
The unpredictability of the situation is also nerve wracking.
BTW I tried to import psd files made Photoshop CS5 and 12.1.3 rejected them. Is that normal?
My next step will be to set up a drive with a probably Mac OS High Sierra and instal PPro 13.0.3 and see how that works - ie if current Premiere projects will open on it. I'm not confident.
I am using a mac and my iPhone footage won't play, do I need handbrake too?
Since you are on a Mac, you should have Quicktime
Exactly what is INSIDE the video you are editing?
Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing - For Windows Internet Explorer press the PRINT SCREEN button on your keyboard, and then do CTRL-V to paste the screen print from the clipboard into a forum message
Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download
- when you analyze your file in MediaInfo and post a screen shot in the forum, do so in TREE view
Hello, I had the same problem. Now I've solved it partly. The problem is Nvidia Geforce 1060 randomly goes to sleep mode when load is small and transfer control (in my case) to built in UHD Graphics 630 and never come back.
The solution is to set up custom Program settings in Nvidia Control Panel for Premiere Pro.
I set up Power managment mode in Prefere maximum perfomance for premiere pro.
The downside of it is that coolers constantly when I use Premiere Pro CC 2019.
I found this solution here:
Driver Power State Failure problem Windows 10 FIX!!! - YouTube
Hello, have had this issue for a while with past versions and it persists on the most up to date version. Currently, my eye dropper when trying to pick a color on an existing element, won't allow selecting the color, but rather it's reverting to a gray instead. Is doing the same with color mattes as well. Does anyone have any ideas?
Current PP version: 13.0.2
MacOS High Sierra Version: 10.13.6
I think I might be over complicating this, but I am extremely confused on how to do it a faster way. Here is an image of how the video would look in Premiere: https://i.imgur.com/KOeo5ZB.png But I only want one display to show for the final video, either the first, second, or third display. So the resolution of the video is 4099x1080(I cannot do 4480x1080 because OBS would error out so 4099 is the maximum) As you can see, there are three displays one is 1920x1080 and the rest are 1280x1024. I combined all of the displays them because I use OBS's replay buffer(shadow play alternative) to record all of the displays at once. The only problem is the editing part, in Premiere, I would like to have a preset for display 1,2, and 3 to crop out the rest, but I am really confused on how the cropping works and scaling, I wish it was like photoshop where you can drag the corners and it would work easily.
OBS output: 4099x1080
Premiere output: 1920x1080(even if the display is 1280x1024, black borders is fine)
I've just recently built a new Windows 10 machine to replace my old 2010 Mac Pro. I've installed the newest web driver from Nvidia. CUDA acceleration appears as an option for the Mercury Playback Engine in both Premiere and Media Encoder. When I make an export, even with CUDA selected, the software encodes with my CPU instead.
I was under the impression that on Windows 10 I only need to install the driver, that I don't need a separate CUDA driver like on macOS. Is this the case or do I need to install the CUDA 9.2 or 10 Toolkit from Nvidia's site? If I dont need the toolkit, what could be causing this?
Relevant system specs:
Gigabyte Designare Z390
i7-9700k
RTX 2070
32gb ram
Thanks!
I kinda regard it as being invasive, in as far as I'll lose all my customised settings by doing that.
Be that as it may, however, I am actually posting here again to inform the community (perhaps I'm stating the obvious though) that I've since discovered that Premiere Pro's behaviour in this aspect appears dependent on the video frame rate being worked with.
My original post followed my discovery of this issue when editing mp4 files that came from screen recording software, captured at what was apparently 10fps. However, today when I was editing "proper" video footage shot on a DSLR at 25fps, the Step Forward 1 Frame / Step Back 1 Frame options worked perfectly - advancing / retiring the video by one frame per click as they should (without me having changed any settings between the two editing exercises).
My conclusion is therefore that working at too slow a frame rate probably doesn't offer Premiere Pro enough "granularity" to be able to work with individual frames, in the way that it can when there are more frames to use per second. Probably obvious now, in retrospect!
Hi,
Can anyone tell me why my shortcut changed after last update and I can't find at all one of my favorite options which was "render in to out"?
There is "render selection" but it's completely not working
Everything is weird after the las update of PP.
Cheers
Przemek
The only thing different between the two projects was a driver update for my graphics card. There was another update today for the card, seems weird, but the project before would still act flawlessly regardless of the driver update.
Both had the same footage from the same camera at the same frame rate, resolution, etc.
My card is a GTX 1080 if that makes a difference.
Does the footage have variable framerate: if so convert with HandBrake before importing into Pr.
You can check this by looking at the Properties within Pr: variable framerate detected.
Also you can up the bitrate: Match Source adaptive bitrate.