Are you the publisher? Claim or contact us about this channel

Embed this content in your HTML


Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog

Channel Description:

Latest Forum Threads in Premiere Pro CC

older | 1 | .... | 4909 | 4910 | (Page 4911) | 4912 | 4913 | .... | 4938 | newer

    0 0

    Need help figuring out how to fix this problem! I can't get any videos to play in any of the Premiere Pro windows, even though a couple of days ago it was fine!


    In the screen recording you'll see that the only thing that turns up in the Source window is audio, though no audio actually plays. Then when I try to play the videos, the audio image still appears. I try playing in all the windows and get nothing. It's really stressing me out!


    I've tried the rendering thing that most forums suggest, but nothing changes. I started and restarted a dozen times... The only thing that has changed in the past few days is that I updated to MacOS Mojave (version 10.14), so if there's anything else I can do please let me know!

    0 0



    I have a short piece of footage )someone talking which i have filmed against a green screen and removed the background in Premiere.


    Can someone please let me know how I export this footage with a transparent background so I can import into Adobe Captivate and place on a different backdrop?


    Many thanks



    0 0

    I have done some recent tests, comparing multicam video playback performance in Adobe Premiere Pro to Apple Final Cut Pro X. I thought this could be of interest for more people, and I really wonder what Adobe has to say about this. This is not a scientific test by any means, but I have tried my best to visualize the differences to maybe help explain why there is such a big performance difference. Take it for what it's worth.


    As I say in my final notes, the inefficiencies in resource usage/management in Premiere Pro appears to be a problem in general for video playback performance, which becomes very noticeable when adding additional streams of video. The extremely aggressive/excessive pre-fetching is certainly not working in favour of Premiere Pro, especially when playing video via TCP/IP from a NAS. To make sure storage wasn't a bottleneck, i tested using internal 4TB flash storage for the media files, as you can see below.


    It seems like Adobe is asking for data faster than actually needed, which results in the video playback engine choking (dropping a lot of frames) unless you have insanely fast storage in addition to a lot of fast CPU cores and a lot of memory. It is also interesting (and strange) to see how the playback is a lot less resource intensive when playing from the beginning of the timeline, compared to hitting play right after moving the timeline indicator forward.


    Comparing Premiere Pro to Final Cut Pro X, the test results kind of indicate two very different approaches in terms of video playback:

    • Premiere Pro: Give me as much data as possible, as fast as possible, regardless of what I actually need to play the video, and let's hope for the best.
    • Final Cut Pro X: Give me as much data as needed to play the video in a predictable way.


    Apple's approach with Final Cut Pro X appears to be quite beneficial. The fact that even an old 2015 iMac 5K with a 4-core 4GHz Intel i7 CPU and 16 GB memory is able to play the same 10 streams of media in “High Quality” both from local storage and a NAS via 10 Gbit Ethernet and SMB3, while at the same time on the same machine doing a screen recording at full 5K resolution with Telestream ScreenFlow using 1 full CPU core of the 4 (8) available. Final Cut Pro X is using less 50% of the total CPU capacity on this old iMac, which is very impressive.




    See the full test with graphs and metrics in the PDF above. You can also see TCP stream analysis of single-stream video playback in the PDF.


    I have included the text from the test below.


    Multicam video playback performance test

    Adobe Premiere Pro vs. Apple Final Cut Pro X


    iMac Pro (2017)

    2.3 GHz 18-core Intel Xeon W CPU, with Turbo Boost up to 4.3 GHz

    128 GB 266 MHz DDR4 ECC memory

    Radeon Pro Vega 64 with 16 GB of HBM2 memory

    4 TB SSD


    Software versions

    macOS 10.14.2 (18C54)

    Adobe Premiere Pro 2019, Version 13.0.2 (Build 38)

    Apple Final Cut Pro X 10.4.4


    Media stored internally on the iMac Pro 4 TB SSD

    10 two hour long Apple ProRes 422 Standard 1920x1080 25i QuickTime MOV files, at 120 GB each.

    Files recorded/created by an EVS XS Production Server.


    Notes and observations


    Adobe Premiere Pro

    Playing around with 10 two hour long HD streams of Apple ProRes 422 in multicam mode in Adobe Premiere Pro on the fastest Mac currently available on the market (as of January 2019), with media stored on its blazing fast internal SSD storage, works pretty well in general. At certain points however, even the 18 Intel Xeon cores (36 with HyperThreading) is pushed beyond its limits by Premiere Pro. At one point it dropped over 600 frames in a row after moving the playhead and hitting play, because the CPU hit the limit.


    • CPU usage often goes beyond 80% when starting playback, and sometimes even caps out at 100%
    • Storage bandwidth usage often goes beyond 1000 MB/s
    • Memory usage always goes beyond 10 GB during playback


    Enabling “High Playback Quality” makes matters even worse.


    There is no noticeable performance difference between Metal and OpenCL.


    Observing the incredibly bursty and wildly unpredictable/inefficient resource usage in terms of CPU, storage bandwidth and memory in these local iMac Pro tests is quite revealing. It becomes pretty clear why a NAS that can deliver up to 700 MByte/s via SMB3 to a macOS 10 Gbit client can easily become an issue. It also explains why a 10-core iMac Pro (2017) or a 12-core Mac Pro (2013) hits a CPU limit during playback and suddenly starts dropping frames, regardless of how fast the storage is.


    The initial burst in CPU usage and storage bandwidth usage when hitting play after moving the playhead appears to be causing a lot of issues for Premiere Pro.


    I have been doing some tests in Premiere Pro 13.0.2 on Windows 10 as well. The only Windows PC I have access to that is able to play the same 10 media files in multicam mode in Premiere Pro is a Lenovo P900 with a Dual 14-core Intel Xeon (58 cores including HyperThreading), with 128 GB memory. The CPU is still hitting the limit, but just barely manages to make it without dropping too many frames. Interestingly, the network bandwidth usage when playing media via 10 Gbit Ethernet via SMB3 from a fast NAS never goes beyond 3 Gbit/s. It looks like Premiere Pro on macOS for some reason requires faster storage than Premiere Pro on a beefy Windows 10 PC, but it looks like bursty CPU usage is a problem for Premiere Pro regardless of platform.



    Apple Final Cut Pro X

    Playing around with the same 10 two hour long HD streams of Apple ProRes 422 in multicam mode in Apple Final Cut Pro X works incredibly well.


    • CPU usage never goes beyond 8% when starting playback
    • Storage bandwidth usage never goes beyond 400 MB/s
    • Memory usage never goes beyond 1 GB during playback


    Actually, even an old 2015 iMac 5K with a 4-core 4GHz Intel i7 CPU and 16 GB memory is able to play the same 10 streams of media in “High Quality” both from local storage and a NAS via 10 Gbit Ethernet and SMB3, while at the same time on the same machine doing a screen recording at full 5K resolution with Telestream ScreenFlow using 1 full CPU core of the 4 (8) available. Final Cut Pro X is using less 50% of the total CPU capacity on this old iMac.


    On the iMac Pro with macOS 10.14.2 and Final Cut Pro X 10.4.4 Apple do things even more efficiently than Final Cut Pro X 10.4.3 did in previous tests on macOS 10.14.0 on an iMac Pro 10-core.


    Apple is clearly doing things very differently and a lot more efficiently in terms of system resource usage/management, compared to Adobe.


    Final notes

    The inefficiencies in resource usage/management in Adobe Premiere Pro appears to be a problem in general for video playback performance, which becomes very noticeable when adding additional streams of video. The extremely aggressive/excessive pre-fetching is certainly not working in favour of Premiere Pro, especially when playing video via TCP/IP from a NAS.

    0 0

    Hello, my Input LUT (in Lumetri Color panel) only show eight LUT sets. If I open Adobe Premiere Pro>Show Package Content>Lumetri>LUTs I have three folders Creative with 65 LUTs, Legacy with 79 LUTs and Technical with 8 LUTs which is the only one I have access.

    How can I access to all the others LUTs? It is a bug? Thanks!

    0 0

    Are there any crippling bugs in either that are preventing you from completing projects?  Or, anything forcing you to resort to draconian workarounds?


    I'd love to hear from full-time post-production professionals, if possible.


    I'm eager to be able to use the new Lumetri hue features, and Mocha as an effect in Ae CC19, but don't want to be taking two steps back in stability and reliability.


    Thanks in advance for weighing in.

    0 0

    A couple days ago I spent all day editing a project. It's about 10 minutes long and consists of all iPhone videos - various frame rates and resolutions. It came out great and I closed the project for the night. The next day I came back and tried to open the project and after the loading bar completes, I get the error: An unknown error has occurred while opening the project. Other projects open normally. New projects open normally. But this one does not. I am so upset and frustrated about the lost work.


    I went to my recent auto saves and they give me the same error. If I go way back in the auto saves, they will open normally but that was before many hours of additional work on the edit.


    I made a new project and tried to import the old project and I get the error: The importer reported a generic error.


    I used Media Browser to view the project and the window where I should see everything is blank, even after the loading bar finishes.


    I used Project Repair from Digital Rebellion's Pro Maintenance Tools which thinks it has repaired the project, but I get the same error when trying to open it.


    I used CS Repair from Digital Rebellion's Pro Maintenance Tools to trash Premiere preferences. No help either.


    I googled the error message endlessly and although the same question has been asked, none of them got an answer.


    Please advise.


    Premiere 2017.0.1

    macOS Sierra 10.12

    2012 Mac Pro 12 core 2.4GHz

    Nvidia GTX 780 6GB

    32GB RAM

    0 0

    When I try to open a project created in previous versions I get the message that the project will be converted, then Premiere just locks completely - nothing shows on the screen, I can't even close it from the X at top right - have to stop the app from the task manager.

    0 0

    Hey all!


    Firstly, system info:

    • Mac Pro (Late 2013) running macOS Sierra 10.12.5
    • 3.5 GHz 6-Core Intel Xeon E5
    • 64 GB 1866 MHz DDR3 RAM
    • Premiere Pro CC v13.0.2 (upgraded from 13.0.1 a few days ago)
    • Working with media on Mac OS formatted external hard drives (Lacie Ruggeds and G-Drives connected both via USB 3.0 and Thunderbolt 2)


    Full-time editor here with lots of experience in Premiere. At work, I've been experiencing a recurring problem where projects opened in newer versions of Premiere than the version they were started on will have many clips that have danger stripes. I know this means there's a fault with the way the media was linked and/or could be a broken master clip reference, but none of the usual solutions work. Here are some things I've tried:

    • Making media offline and re-linking without changing the media name and/or location on the drive
    • Making media offline and re-linking after changing the media name and/or location on the drive
    • Using "Replace Footage" in the project window
    • Replacing effected clip in timeline with corresponding clip in bin (this gets rid of the danger stripes, but I then have to manually slip the clip back to where it was)
    • Clearing all caches, resetting Premiere preferences, re-installing Premiere, restarting computer, etc. before trying any of the above methods


    The only solution I've found that allows me to open the project and have everything be linked the way it was when it was being worked on in an older version of Premiere is by installing that older version of Premiere and continuing to work on the project there. This solution is not sustainable as only certain older versions of Premiere are available for installation (not necessarily the older version I need) and I can't efficiently do my job if it means having to keep track of 2+ versions of Premiere.


    If Premiere projects are supposedly upgradable to the current version of the software, that upgrade should not come with project-breaking issues. I have experienced this issue on multiple (20+) projects on multiple (5+) workstations at work


    Appreciative of any tips that anyone might have! Thank you so much.

    0 0

    I have a new 2 month old 15" MBP. I Was working on a project, macbook volume was about on half, when suddenly an audio bug occurred with really loud screatching noise and not letting me pause it. After it stopped, the speakers were really quiet, and after the next restart they're clearly blown. Initially I blamed the hardware, though the same thing happened a day later with my Sony 1000X-M3 headphones, luckily the headphones are ok, but that did give me a heart attack.


    The situation is not ok, I am not happy. Adobe customer care chat is ridiculous.


    MacBook Pro (15-inch, 2018)

    Processor: 2,6 GHz Intel Core i7

    Memory: 16 GB 2400 MHz DDR4

    Graphics: Radeon Pro 560X 4096 MB; Intel UHD Graphics 630 1536 MB

    0 0

    I want to make scaling effect with keyframes on a photo. But it doesnt work. Has anyone same problem and solution? please.



    0 0

    Hello! I have been working on a new project in Premiere Pro CC 2019 (I have not updated PP since I began the project)


    My Specs:

    I'm working on a brand new 2017 iMac Pro

    - 3.2 GHz Intel Xeon

    - 32 GB RAM and Radeon Pro Vega graphics

    - Mojave 10.14.2

    - my footage is on a 16TB G-Drive.


    My project is set to auto-save every 5 minutes, and saves up to 20 copies a day, and I save manually a lot as well. At the end of each day, I save my work, close premiere, copy the project file, paste it to my desktop for backup (the master file is saved on my external hard drive) and then update the date on the filename.


    Yesterday, after I did all of that I remembered I needed to check something so I tried to open the project back up but Adobe said "sorry, a serious error has occurred..."  I tried to open up the auto-saves and they all gave me the same error. After a lot of troubleshooting (including trying to open the file up on a different computer), I moved the project file (the corrupt one) to a portable external hard drive, created a new project in Premiere and imported the contents of the old project into the new one - all of the information was in tact, thank god. I worked on the new file for a couple hours today and did the same thing at the end of the day. I tried to open the project back up and the same thing happened! However, this time, i found that the auto-saves prior to a certain point were all working (see image below - green dots mean good and red means it will not open). All I did today was change label colors and clean up some multiclipping, i did not import any new footage. So what could have happened between 2:03 and 2:19 that made the file corrupt?


    I also tried chatting with someone at Adobe and they were extremely unhelpful...

    Screen Shot 2019-01-05 at 3.23.11 PM.png

    0 0
  • 01/08/19--09:23: Export dialog Issue
  • Hoping someone ca help me with this...

    All of a sudden my export dialog no longer auto-selects sequence In/Out when I'm trying to export a marked area of my timeline. It defaults to "work area" every time. Where do I reset this or change it back to automatically change with my selection on the timeline?

    0 0

    Anyone else experiencing Premiere 13.0 mismatching timecode? I had a project done in Premiere 12 that needed its media reconnected. I opened in 13, and when it reconnected, in and out points were all over the map. Went back to 12, it reconnected just fine. No big deal, I think, it's the whole "don't open old projects in new releases".


    Well, now I'm trying to send a different edit via XML to Davinci Resolve for color grading. All the in and out points are incredibly off in Resolve - have NEVER had an import issue before like this. Some clips are just flat out offline because, according to Resolve, the XML calls for selections outside of the clip runtimes.


    So, I think to myself, let's have 12 be the middle man between 13 and Resolve. Go to 12, import XML - it freezes up. Every time. Now, unfortunately, I must go back and redo my recut of the last edit, as there is no way to get it out of Premiere 13 reliably, even to last year's Premiere.


    13 was not ready for prime time, this is a HUGE problem.

    0 0



    Whenever I apply Warp Stabiliser to a video it makes all of the bold, sharp lines in the footage glitchy, giving a sort of heat distortion affect, but only on the sharp lines. The actual stabilisation of the footage isn't an issue so much as the horrible scanning effect.


    Could this be a fault with my camera? I've reinstalled premiere, tried every different setting in Warp Stabiliser, tried using Warp stabiliser on multiple machines, all having the same problem.

  - This link shows the same clip, first with the stabiliser and if you look at the edges of the text you can notice the scan line effect. The second clip is the unstabilised version (excuse my awful camerawork it was freezing cold and I hadn't got the ronin out ) But on the second clip you can see that whilst it is shaky the text is sharp. Also the actual stabilised movement in the first clip is pretty much fine, just the lines:(


    I've spent the last few hours trying to figure out what is causing this issue to no avail, any help at all would be very much appreciated! I feel like this has to be an issue with my camera settings? For reference I am shooting using a canon 1DX Mark II.



    0 0



    After updating to Premiere Pro 2019 yesterday, I now see that it is required to have updated graphics drivers in order to use GPU acceleration. I am currently on a driver for my GTX 1070 from November 2017. I cannot update it, as any driver I update it to causes terrible bugs and glitches in the games I play on this PC.


    Is there a work-around? Some way of using GPU acceleration in this update without having to update my graphics drivers? Let me know, thanks!

    0 0



    I have a big issue with .srt files. I used to import .srt and add them to a sequence, then I used to edit size etc.... It is ok in Premiere CC 2018 but, it seems that all edit settings are doing nothing to the text . To reproduce the issue you just have to open Premiere CC 2019, load a .srt file and place it on the timeline, and try to edit captions settings (font size, font etc...). In my case I can see modification in the preview thumbnail of each caption in the "Captions" tab but, nothing is visible on the monitor, the text remains the same (very small and... that's it ).


    Can you help me with this bug ? Thank you !

    0 0

    Every time I attempt to import an After Effects comp into Premiere Pro, I have to make 2 attempts.



         Find the AE project file

         Find the comp within the AE project file

         Highlight (or double-click, doesn't matter)

         Click - "OK"


         First time it just sits there. Same import screen, like something is very wrong.

         Then I have to dig into the AE project file, find the comp I want again, Highlight it  and click OK.


    This has been going on for a couple months.  I have done some internet searches.  Not sure what keywords might get this to be answered.  All to no avail.

    Is anyone having this issue?  Is this a dynamic link thing?

    Would love if Adobe would weigh in on this one.


    Oh, and previously, no issues importing.




    0 0

    For some reason, in ALL (across multiple project files and sequences within 1 project file) of my synced audio/video created in Premiere 2018 has now been shifted over for some reason as seen below. It's done this in mutlicam sequences and just synced files. I've attached images of both.


    Anyone have any clue what happened here?



    This is the multicam sequence and was rendered in 2018 with zero issues.      This is just 1 video file with 2 audio files.

    0 0

    I have one gigabyte rx 550 2gb in that machine:


    Fx 6300

    8gb ram 16000mhz

    Asus M5A78L-M PLUS


    When I start the premiere and select Open GL, the program stops and crash in few seconds. When I use software only it works well but slowly... I'm using win 10 pro last version, and I just wanted to undertand why this cards is not even on the list and why in the gigabyte's rx 550 page they said the card would be 15x fast on premiere. THAT IS NOT EVEN RECOGNIZED HOW CAN IT BE 15X FAST????


    I see many people on google complaining the same.

    0 0

    When I export media at a higher quality, after selecting preset Vimeo 1080 then selecting attributes like VBR,2 pass, render at maximum depth and use maximum render quality I get a few frames that have glitches, weird colour changes? SEE attached pics.


    So in the images below the good image on top is preset Vimeo 1080, the second mage below it is preset Vimeo 1080 plus all the other higher quality attributes mentioned above!


    It doesn't happen if i just select a preset by itself like Vimeo 1080 and none of the other attributes mentioned whats causing this?GLITCH1.jpgGLITCH2.jpg

older | 1 | .... | 4909 | 4910 | (Page 4911) | 4912 | 4913 | .... | 4938 | newer