Merlin Vandenbossche
Forum Replies Created
-
Hello Preet,
Obviously try to update GPU drivers to see if CUDA performance returns to normal, if possible to Nvidia’s creator ready drivers: https://www.nvidia.com/Download/driverResults.aspx/145178/en-us
But I expect you are well beyond this?
Also I am still amazed at how many people on this forum are trying to edit high resolution H.264 or H.265 files natively and expect it to be butter smooth. Both codecs are horrible for any editing situation as they are GOP-based and rely heavily on CPU for decoding in most apps. H.264 or HEVC, while it is improving, will almost never scrub or play back as perfectly as an I-frame only codec. Try transcoding or optimizing media to ProRes or DNxHD codecs and relinking to those files. See if it improves your situation.
As always: resetting prefs for premiere (ALT+SHIFT while app launches) and deleting cache and databases (https://forums.adobe.com/thread/2152942) are two standard operations you should always do when troubleshooting.
Good luck to you!
Merlin
-
Hey Josh,
Native H.264 4K will always get your computer to struggle with playback, even on beter hardware than yours. An even on Resolve. A better workflow would be to transcode to an I-frame only codec for smoother playback and scrubbing, say DNxHD or ProRes. That always will improve your experience.
That being said: it is not normal operation for CUDA not to work or for even H.264 4K to cause the program to freeze with standard handling. So I suggest you to also look into other issues than just the codec. I think a 6700K is fine to handle this kind of work normally. (obviously a 9900k would be better)
So try the following things, preferably all of them: do so in a clean project without any data in it.
– Reset preferences and plugins: holding down SHIFT+ALT while launching the app or clean project. Remember to check your preferences and change them again after resetting. Including your keyboard layout.
– Delete the cache files and databases: Premiere will then regenerate these files. https://forums.adobe.com/thread/2152942
– If your project was an update of an old project from CC18: create a clean new project in CC19 and re-import your old one (through the import dialogue).
– Update your GPU drivers to the latest, this should fix your CUDA hopefully: It is a good idea to follow Nvidia’s new and slower development ‘creator ready’ drivers. https://www.nvidia.com/Download/driverResults.aspx/145178/en-us
These drivers work for my 1080ti.
Good luck!
-
I just saw you were exporting a multichannel mix: is your timeline just stereo then? Try copying the whole timeline in a multichannel (8-channels) sequence instead. If multichannel: are all tracks properly routed in your track mixer (sending the whole mix to 1-2? maybe some channels are sent elsewhere?)
-
You can:
– Try to render all audio and audio effects before exporting the timeline
(go to the Sequence dropdown menu and choose ‘Render Audio’)– Try to ‘Render and Replace’ the troublesome clips before exporting
(right-click on the clip and choose ‘Render and Replace’, this will render an exact trimmed copy of this audio next to the original file on disk, it is trimmed, with all effects baked in and in uncompressed WAV form)
(you can ‘Restore unrendered’ by right-clicking the rendered clips again, to restore the original link to the source file)– Try a mixdown of your mix instead: render taudio only to AIFF or WAV and place this as a sole stereo mix under your videotrack. (this solution is the least favourable one as it is just a workaround for a project in progress)
Best of luck!
-
Maybe try resetting preferences and plugins? I always do that after any update. Since the Transmit Playback is a preference, it might help.
You can reset prefs by holding down ALT+ CMD + SHIFT when opening Premiere. Remember to go through your settings again, since they obviously will be reset.
-
The right answer is indeed that it depends on your source footage and how you are using it. You should analyze your workflow before you can determine what the bottleneck might be.
To answer your specific question and give some info on hardware in general:
Within Premiere Pro, the GPU is mainly used to accelerate certain things. Primarily the use of ‘GPU-accelerated’ effects (those have the icon of a folder and play symbol next to them). When using those effects PPRO can leverage the GPU to maintain real-time playback. The GPU also accelerates export times greatly and can only help decode (and so play back) certain RAW formats like R3D.
The CPU is still the main driver of all things encoding (exporting) and decoding (playback). Certain codecs in particular are CPU heavy as they are heavily compressed: like e.g. H.264 or HEVC. That requires the CPU to work harder to decompress them. Others that are less compressed (ProRes, DNxHD) require less CPU power and can for instance be used on laptops more easily. H.264 in particular also benefits enormously from certain CPU technologies like Intel’s QuickSync, a tech only found in the mainstream line (and not for example in Xeon or Core X CPU’s). It is notorious how for instance a regular i7/i9 iMac will completely outperform a Xeon-based iMac Pro using H264 footage.
On top of that there is hard drive speed as an important factor. The less compressed formats (ProRes, DNxHD), especially when in higher resolution, require drives that are faster than ‘normal’. That means SSD’s or RAID systems. Compressed formats like H264 have smaller data rates and can work fine on slower spinning drives.
As you can see: depending on your source footage you need a very different situation to get optimal results.
Doing a lot of H.264?
Get a ‘top end’ mainstream 6-8 core CPU (i7/i9), never do XEON. Fast drives are welcome but not your primary concern.Doing a lot of ProRes or other optimized?
You will do fine with professional CPU lines like XEON or CORE X, especially at 4K or above. For normal HD resolution you can go with cheaper mainstream CPU’s. Fast drives like SSD and RAID may be necessary depending on resolution and complexity of the codec (ProRes 444 vs Prores 422).Looking at your specs: the XEON is certainly the culprit if you are trying to work natively with H.264 footage (GOPRO, DSLR’s, etc.). If you are now just struggling to playback real time effects and lumetri etc., getting a better GPU like the RTX series or 1080Ti will help you for sure. They will also help if you are doing RED RAW. Or maybe you are using regular spinning disk to play back high data rate codecs (ProRes 444?) or RAW?
Good luck in diagnosing your workflow, hope you find a good solution!
-
Also check for updates or uninstall third party plugins (Red Giant, etc.). Updates of Premiere Pro usually require updates of the plugins as well.
-
One of the first things I would try to do is the combination of:
– Deleting the media cache database in the library folder (user/library/application support/adobe/common).
– Reset preferences of the app: holding down CTRL + CMD + ALT while launching the application.
– Create a new clean project and re-import my old one.
– Reset my workspace or delete my old one and re-create it in the new version.Performance on a Mac from 10.13 and onward should be best using Metal as the renderer (project settings).
-
I dont know much about troubleshooting CS6 compared to CC, but maybe the same Adobe logic applies already for years. Some things that may help:
– Resetting preferences of the app: https://forums.adobe.com/thread/2126506.
– Resetting or deleting/re-making your workspace.
– Creating a new clean project and try re-importing the old one (dont know if CS6 allows this).
– I’d say cleaning your media cache folders, but this doesn’t seem this kind of problem.If all else fails: a clean install of OS/software could be imminent. I do this almost once every year.
-
Hi Oliver,
No experience with iMacPro, but quite a lot with the regular iMac.
I run about five edit suites of Premiere, all iMac Retina 5K connecting through a 10Gbe network to a GRACK 12 storage. I use Sonnet Twin 10G adapters. Running on MacOS 10.13.6, using AFP protocol.
Two of them have almost never had issues, they are 2015 models (TB 2) connected to a Thunderbolt 2 Sonnet adapter. The other three are 2017 models (TB 3) connecting through a newer model Thunderbolt 3 Sonnet Twin 10G. On those three TB 3 I’ve experienced several issues over the last year. Often times no connection showing after a fresh boot, the Sonnet adapters not showing connection lights, etc… Trial and error, reconfiguring the cables would eventually solve the issue; but almost randomly it seemed. Have tried things like fixed IP’s and re-installing drivers to no success.
I have sent the TB 3 adapters out for repair and hooked up the 2017 iMacs with some old Sonnet TB 2 adapters I still had lying around. So far smooth sailing for a month or two (despite having to connect these using a TB2-TB3 adapter now). I havent tried using the repaired TB 3 Sonnet yet (got them returned about a week ago). The speeds are consistent I believe all year round: about 500-600 MB/s on the blackmagic disk speed test.
One more thing: in the past I have had poor experiences using SMB protocol, also with random disconnects or inconsistent speed behaviour. This was on MacOS 10.12, where apparently there were bugs with SMB signing (you even had to trick the service using terminal). I haven’t used SMB ever since: AFP seems stable, the GRACK supports it and the speeds are sufficient for our work.
Hope my case study teaches you something and best of luck!
Merlin