Merlin Vandenbossche
Forum Replies Created
-
You cannot change a named lumetri effect across an entire timeline. You can affect multiple clips across the timeline though.
The closest thing to what you are trying to do is then called a ‘master clip effect’. You apply the lumetri effect to clips in the project window (instead of the timeline). Each time you adjust the effect on one clip (in the master tab of the lumtri color panel) it ripples to all instances of that same clip in the timeline.
https://www.youtube.com/watch?v=TGoAsiFgxZc
If your clips come in multiple instances though (they are separate master clips / separate videos) you will need to adjust each master clip effect separately. You cannot group multiple clips together to apply the same master effect to each. At least to my knowledge.
One workflow then could be to always find (CMD + F / CTRL + F, find all) your commonly named clips and then remove/paste the lumetri effect each time you wish to adjust it. Just give each of those clips ‘a common part’ in their naming and search for that every time. Alternatively you could also set it up to use the same video track for each of the clips you want to ‘group’ and just lock the other tracks (SHIFT click the lock to lock all and unlock only the wanted track) when selecting and then removing/replacing the lumetri effect.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Lo and behold: finally the release of the MacPro! With an upgrade from a 256 GB SSD to 512 GB SSD for only 999$!
Now seriously: isn’t it likely the MacPro?
-
For my case: highly unlikely. Since I am an Adobe user it’s not very likely this machine will scale well with the software (yet). I’ve never found Xeon architectures to be better than say Core i7 or i9 systems for Premiere Pro. I also have too much H.264 in my workload for now and Xeon does not handle it well. So it’s still quite possible that say a maxed out 9900k 2019 iMac is ‘better value’ for a lot of people like me. Or buying a Windows workstation and Nvidia GPUs of course.
I also find the value of the starting spec abysmally bad (256 GB SSD, 32 GB memory and an RX580 for 6000 dollars?), so I expect for the machine to improve your current setup you’ll need to invest at least 10k or more. I am very curious though about performance (I hope to be surprised), about the actual upgrade prices and about the afterburner card. The latter is a mystery box right now.
-
The explanation that this mac is outdated feels like BS to me. While I can’t replicate your setup, I would try some of the following:
A/ Run the ‘standard’ maintenance for Premiere Pro:
– Manually delete caches and databases:
https://community.adobe.com/t5/Premiere-Pro/FAQ-How-to-clean-delete-or-trash-media-cache-files/td-p/8324672– Reset preferences and plugins:
https://community.adobe.com/t5/Premiere-Pro/FAQ-How-to-reset-trash-preferences-in-Premiere-Pro/m-p/8236158Be aware the reset does just that: reset all your preferences. So remember to go through preferences again and re-activate your key layout.
– Reset or re-create workspaces if the UI behaves strangely.
B/ Make sure to run the right drivers for Nvidia on MacOS.
I strongly advice you to use Nvidia’s web drivers instead of Apple’s, you can find the latest here:
https://www.nvidia.com/en-us/drivers/cuda/mac-driver-archive/Also never update to MacOS Mojave or beyond, as CUDA is no longer supported since MacOS 10.14.
C/ Test for hardware faults.
Dropped frames may also occur due to drive or RAM memory failure. Test the use of your system on other software (Free DaVinci resolve), run tests on the drive and memory. Check the status of the RAID, the speed of the drives (blackmagic disk speed test), test the memory (https://www.makeuseof.com/tag/check-memory-mac/targetText=Testing%20your%20RAM%20with%20Apple's,and%20let%20the%20test%20complete.)
Good luck on your troubleshooting hunt!
-
I don’t mean to pry but I strongly disagree on the suggestion for a Ryzen in your case. Since you already own a Z370 board, it would be more cost-efficient to upgrade along the Intel i7 or i9 path. Getting Ryzen also means getting a new board for your system. And more importantly: the intel CPU’s are a better match for premiere pro if you are using GOP-compressed footage. You shoot GH5, which delivers a difficult H264 or HEVC compression. Because Intel CPU’s have access to an ‘onboard’ GPU, it allows Premiere Pro to use what is called ‘QuickSync’, a technology that helps decode the GOP-compressed stream. Ryzen, Threadripper, Xeon, Core-X are all CPU-brands that have no access to QuickSync and are therefore ‘slower’ at editing H264 footage (be it DSLR, GoPro or drones).
In fact, even now, your 8600K can use this tech. Just make sure to enable the onboard graphics (enable ‘IGPU’ in the bios) and enable the hardware accelerated decoding in the prefs of PPRO (under the media tab).
This is a good vid explaining some more: https://www.youtube.com/watch?v=ofdh-THQFpE
On to actual recommendations:
For CPU:
Since you are limited in budget I would suggest trying to find something like a 9700k for around 350 dollars. If you can’t: a 6-core 8700k will also be a good upgrade compared to the 8600k. The best upgrade path is the 9900k, which is phenomenal for Premiere Pro right now, but it will cost you higher. Whatever you choose: never pick any of the ‘KF’ series (9700KF, 9900KF), since those don’t have an IGPU. And you really do want QuickSync.For GPU:
I would actually advise you to get this first. Compared to no GPU, pretty much any GPU will mean a really good improvement. General advice for Adobe apps is to get NVIDIA cards. They beat AMD’s offerings in almost every scenario. PPRO is much more optimized with CUDA than OpenCL as the Mercury Playback Engine setting. For CUDA you need NVIDIA cards. Reasonable budget options today are the GTX1660Ti or regular GTX1060. If you can afford it: get an RTX card, RTX 2060 or 2060 Super.These articles on Puget Systems btw give you great insight about the performance of various CPU and GPU options. That way you can easily compare to more expensive upgrades.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
I also just remembered: this version of PPRO (v13.1) is also one with ‘added support’ for multi-GPU workflows. That could also be a lead: this version in particular is maybe ‘coded differently’ than the ones before it. This was some info on multi-gpu and egpu in the 13.1 version:
https://www.youtube.com/watch?v=drlUWYh_U4I
I’m still betting on a possible mismatch between your specific Mojave version and PPRO though.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
I assume you already dumped cache en reset preferences and the usual suspects. So it seems something hardware related then.
Apple’s Trashcan has a poor reputation concerning its GPU’s. But since you are editing GPU-accelerated and just not exporting, it is a bit of a mystery. And since you’ve had success in the past, it is not super likely your D500’s are broke either. But judging from your video it is clearly the GPU giving you the issues though. Have you tried a GPU-accelerated export in other software than Adobe’s? Just to make sure it is not occuring with other developers as well. Maybe try DaVinci Resolve 15 and check the GPU when exporting.
I would bet on an unfortunate mismatch between the 13.1.4 version of Premiere and the GPU drivers in 10.14.6 MacOS. I have a D500 nMPro on High Sierra 10.13.6 as an encoding machine and I don’t recall any issues with it on our shop using metal or openCL. But I should confirm that with our assistant.
Sadly since you can not control drivers in MacOS, so you may only be able to A/ wait for Adobe to fix the mismatch (if it is confirmed as a mismatch) or B/ try a downgrade of the OS to High Sierra (this will mean a full clean install).
-
Hello Felix,
The guys over at Puget systems do an insane amount of hardware tests with content creation software. They publish all results on their blogs and website. It is a good resource to compare hardware options when building a machine.
Given the info in the above article there are a few roads you may consider:
– The 9980XE, while technically being the fastest, may not be the most ‘valuable’ option. Like you can see: the 16-core and 14-core come insanely close to the same level of performance in Premiere Pro. So consider getting the 16 or 14-core version of the Core-X instead and spend the money you save on more RAM or GPU.
If you are also considering the ‘mainstream’ line of CPU’s, the 9900K is THE way to go. The i9 is the best scoring CPU for After Effects and Photoshop (because of high clock speed) and is great for editing GOP-based codecs (H.264/HEVC). An intel CPU with integrated graphics allows premiere pro to playback and export GOP-codecs faster than Xeon or Core-X.
– If you choose to save money on the 18-core CPU, buy a better GPU. While the RTX 2060 is good value overall, it gets beat by an RTX 2080 Ti by a fair margin. It’s kind of a weird combo to do a RTX 2060 with a really expensive 18-core CPU. Get the 2080 Ti, it is the ‘best value’ compared to other really expensive GPU’s like quadro or titan. Other apps like Resolve will also love you for the better GPU.
– You didn’t mention RAM: I would do 64 GB or more if you can for a machine of this budget. (I assume you are going fairly expensive since you are planning to buy an 9980XE). 32 GB is the minimum for comfortable 4K.
– You are absolutely right about the NVMe SSD: get them as much as you can. Get one of about 256-512 GB for booting and apps, and get one of 1 TB+ for storing the Premiere Pro Cache and Database and/or storing media.
-
Hey Chris,
As always all depends on the codec and source material. But in general this system will perform perfectly fine with 4K. Just make sure that (depending on codec) you store media on a fast enough drive. Don’t expect ProRes444 in 4K and 60 fps to perform off of a spinning drive. SSD’s or RAID are the way to go there.
ProRes, DNxHD, RED RAW, Cineform and the likes will run great on this beauty of yours. But as always: don’t expect H.264 or HEVC to perform as good as those I-Frame codecs (when scrubbing in particular). Playback of those at full res will be OK (I can do that with an 8700K), but the ‘general responsiveness’ of GOP codecs is always ‘struggling’ a little compared to others. Just temper your expectations or if you want ultra butter smooth scrubbing: transcode. This is general good advice for H.264 or HEVC.
Also don’t forget to enable iGPU in the BIOS of the board. This will allow you to turn on hardware accelerated decoding (under the PPRO preferences, ‘media’) and will allow hardware accelerated encoding when exporting H.264 or HEVC. PPRO uses the ‘QuickSync’ chip on the 9900K to help work with H.264 and HEVC. This will improve your overall experience with both codecs. But remember that the exports take a slight hit in quality when done through the hardware accelerated mode (but it’s great for rendering out previews or when in stress of time) Here’s a video explaining the iGPU for ASUS boards: https://www.youtube.com/watch?v=0BoktTdEZFE
Also make sure to install the latest NVIDIA studio drivers to prevent any issues with the CUDA acceleration.
And concerning the choice vs. the 3900x. I personally believe the 9900K is a better choice for premiere pro and after effects. Performance of both should be generally close (the 3900x may win slightly in straight up tests), but the presence of an integrated GPU on the intel chip allows for this QuickSync tech to help with the GOP-based codecs. Which is a big win for intel and this neglects the slight difference in performance I think.
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Ive been using the updated version a few days now, I haven’t noticed anything seriously out of order. Have you tried deleting cache and database + resetting preferences on the app?
https://forums.adobe.com/thread/2126506
https://forums.adobe.com/thread/2152942Especially between updates I always do this as a standard measure to help iron out any conflicts between the databases, caches and pref files of a previous version with the updated app. You can also try to reimport your old project into a freshly created one (made with the updated version) and see if it solves anything for your sequences as a whole.
Good luck!