Even that is not up to date anymore.......
Re: Export video file from Premiere with a transparent background?
↧
↧
Premiere Pro vs. Final Cut Pro X - multicam video playback performance
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.
2019-01-08-Adobe-vs-Apple-multicam-performance-test.pdf
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.
↧
Re: Déplacer mes sous-titres
Set them all to the bottom of the caption frame (as you have).
Then select the caption stream in the timeline, and in the Effects panel, move the whole stream down as you wish.
If you are burning the captions in to the video on export and don't have a lot of captions/subtitles to do, use titles. The quality of caption text is not as good.
↧
Re: Input LUT don't show all the LUTs sets
Appreciate the explanation. I like the Lumetri Presets organization in Effects. Thank you!
↧
Re: After updating old project to cc19, Dynamic Link doesn't work anymore
Unfortunately, this doesn't sound that surprising. There's a difference between saving a project and overwriting it with a different one. I wonder if the link will work again if you clear your media cache with Premiere closed. Force it to reload all the media, and hopefully the Dynamically Linked project.
As for the Live Text Templates, going forward you should look at making Motion Graphics Templates (MOGRTs) because play much quicker, as they don't use Dynamic Link, and actually load chunks of After Effects inside of Premiere.
↧
↧
.srt import and editing not working in Premiere CC 2019
Hello,
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 !
↧
Is CC 2019 ready for a full time post pro to commit to using it?
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.
↧
Re: CC 2017: An unknown error occurred while opening the project.
Thank you so much! You are a life saver! I can't believe how quickly you were able to save my project! Thanks again!!
↧
Re: Problem with privacy settings when exporting videos to YouTube
I am using the CC version and I have updated recently to the latest version. I did not seem to have this problem before.
↧
↧
Re: CC 2017: An unknown error occurred while opening the project.
Your welcome dear. It is my pleasure to help you. Best wishes with your great project.
↧
Re: Adjustment layer, transform effect, and scaling individual images
I could not replicate the Issue, It is working fine with me.
Can you please share a screenshot or a screen-recording of the Issue? Also what version of Premiere are you using?
Meanwhile, as a workaround:
1- select all clips/stills, Right click --> Scale to frame size or Set to Frame size.
2- Apply a transform effect directly on one of them, set the desired scale, save it as a preset and apply it to the rest, OR Copy/paste attributes
↧
Re: Premiere Pro 2018 can't open projects created in previous versions
Saved my life for real Neil. Thank you so much.
↧
Danger Stripes And Media Link Issues After Updating Premiere
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.
↧
↧
GoPro N00b needs Export Settings
I'm recording mountain bike videos using a GoPro Hero 5 Session recording at 2.7K 30 FPS.
I looked up a lot of videos in my "research" for best exporting settings in Premiere Pro. I went with what was most common between a bunch of different videos. Most of them were saying the same stuff. The Main thing (I think) I'm hung up on is CBR vs. VBR 2 Pass. (Everyone says VBR 1 Pass is pointless.)
I was using CBR first, and that exported a lot faster. (Uploading to Youtube is a whole other thing. That took 12 hours for this 25 minute video.) Once I stumbled upon the VBR 2 Pass option, I tried that. I exported in both CBR and VBR 2P to see if I could spot the difference. I couldn't tell it apart but 90% of people say VBR 2 Pass is the best quality. (However they're also filming with LEGIT cameras and not Go Pros?) I thought, Ok.... maybe the difference will be when I upload it to YouTube. Maybe that's where I'll see the difference. But in that case, I'd have to upload two videos and play them side to side... I originally said no to that. Too much work and time Uploading. I then deleted one of the files. I wish I didn't. So today's video I'm exporting in VBR 2P, it is only 10 minutes long and incredibly simple with very few files although it has a highlight effect on the wole video. It took 8 hours and that's with it being rendered previously to Exporting. So I started researching again. Trying to find faster ways to Export.
One thing is "smart rendering" but that's not an option because it isn't yet formatted for encoding MP4.
The other hot tip was to Queue stuff instead of Export it. Queuing stuff sends it to Media Encoder to do. However, mine isn't functional.
I also realised that my copy of PP is installed on the Solid State Drive but I've been saving things to the Hard Drive. So I thought maybe that was slowing things down? So then I cancelled this Export and Saved it to the Solid State thinking I can just move it later and it made no difference.
I guess the last thing is... My Target Bit Rate. That was a big discrepancy with most people. The Max Bit Rate hovered between 32 and 40 for most so I put mine at 35. But some people had their Target at 8, or 16, or 32. I decided to go with 16, that's the YouTube suggested one. I don't know if that's what's making a difference. One guy just had them both set to 32...
I want the best quality, first and foremost, but I also need to find the fastest way to export without sacrificing quality. I'm afraid i'm going overkill right now and wasting a lot of unnecessary HOURS exporting for a 10 minute video. I have 2 hour videos planned... This isn't going to cut it.
↧
Re: Premiere blew my macbook pro speakers
I had the same thing happen to me.
MacBook Pro, 2018, Radeon Pro Vega 20 4080 MB, RIDICULOUSLY expensive...
I simply clicked on the "Enhance Speech" check box while the clip was playing and the loudest sound possible blasted out of the speakers. Now the right speaker is damaged. Great.
Unacceptable for a pro machine this expensive and a piece of pro software that I pay monthly for.
↧
Re: Canon XF705 H.265 HEVC Files
That grainy-ness is going to be there in that low of light. The codec and resolution of the vid have no effect on that.
Anytime the ISO jumps up past around 800 I start seeing grain no matter what camera I'm working with.
↧
Scale effect with keyframes doesn't work in Premiere Pro CC 2019
I want to make scaling effect with keyframes on a photo. But it doesnt work. Has anyone same problem and solution? please.
Thx
↧
↧
Re: Color Management in Premiere doesn't match the export
@ marq5.1
Does it look the same when imported back into premiere? the export file may be interpreted differently.
↧
Re: GoPro N00b needs Export Settings
Its either quality or fast encoding: cant have both.
Post screenshot export settings: 12 hours upload for 25 minutes is way too long.
↧
Re: Scale effect with keyframes doesn't work in Premiere Pro CC 2019
Resave the photo in Ps to psd.
See how that goes.
↧
More Pages to Explore .....
