| How to speed up Adobe Premiere and after effects

SOME FACTORS THAT AFFECT THE PERFORMANCE OF YOUR MOUNTING COMPUTER

current as of 01.2019

CUDA/OpenCL and Premiere:

Starting with version CS5, Adobe Premiere and After Effects use graphics card processing power. The availability of such support depends on the combination of graphics card version, driver version, program version and their settings.
The technical ability to use GPU acceleration does not mean that the program will start working on the GPU instead of the CPU. A number of computational tasks can be solved on the GPU. If such tasks do not appear during installation or export, then the GPU does not participate in the program.
This article describes: a) how to enable all available hardware resources, b) how to organize a workflow so that the maximum number of computing tasks are performed on the GPU.

Adobe Premiere directly supports the GPU acceleration capabilities of almost all video cards NVIDIA, with CUDA and at least 1 GB of memory. Chipsets ATI supported by Premier via OpenCL since CS6 version for Mac (6750M, 6770M), actually since CC. From chipsets Intel support started with laptop Intel Iris 5100 and Iris Pro 5200 via OpenCL in Premiere CC 2014 (version 8.0), now Iris 6100, 6200, 6300, P6300, 540/550, 580, P580 have been added; HD Graphics 5000, 6000.

Plugins, such as Magic Bullet Looks, Elements3D are standalone programs and may or may not use the GPU, regardless of Adobe software settings.

What gives GPU acceleration

The work of Adobe Premiere can be simplistically thought of as the following pipeline: reading files from disk > decoding compressed video to internal memory video format > timeline processing > video codec compression > writing the file to disk. Read/write operations are independent of the GPU and CPU, they depend on the speed of the disks. The graphic processor of video cards (GPU) during video editing can be used for the remaining three operations. These operations are performed sequentially and independently. Sequential means that the video frame goes through all stages of the pipeline from the beginning to the end, independently means that the speed of work at each stage does not depend on others. All together, this means that if at some stage the speed is low, then at others it will be idle from the word. The task of optimization is not to eliminate downtime, but to minimize delays.

To perform these operations, the GPU has independent hardware blocks that deal with: decoding common formats (nvdec/vce/qsv); image processing on universal computing cores gpu (shaders, CUDA); coding to common formats (nvenc/vce/qsv). If these blocks are not on the video card or Premiere does not support them, then the operations are performed on the processor.

The biggest impact on performance is:
1) geometric transformations over video (resizing, rotation, field transformation, frame rate transformation), color space transformation, color correction, other image manipulations, which is supported by many filters, effects and plugins
2) hardware video encoding, which is topical for h.264, h.265 formats

This different ways use, with different effects. For example, with simple editing of DV video end-to-end, without effects and subsequent encoding in h264, hardware acceleration according to the first method will not give any acceleration. the video remains unchanged. But if you use the second method (the plugin is installed voukoder, or a fresh version of Premiere with Intel hardware encoding enabled Quick Sync, etc., while the GPU of your video card or processor is supported by a hardware encoder), then the speed of the final render will increase significantly. Read more about hardware encoding.
Another example is editing 1080p AVCHD video with color correction, Warp Stabilizer, Neat Video noise reduction and then exporting to DVD. In acceleration using the first Warp Stabilizer method, the difference will be hardly noticeable, Neat Video will speed up, and the GPU's contribution to resizing and color correction operations will speed up overall result factor of; the second method will not give the effect due to the lack of hardware acceleration in the mpeg encoder.

All encoding and decoding units on video cards are high-speed and differ mainly in supported resolutions. The speed of shaders is directly proportional to their number and clock frequency, and the frequencies on video cards are approximately at the same level, and the number of cores varies greatly.

Material decoding

There remains a third way to use the GPU of a video card - this is the decoding of the source material. The effect will be when working on the timeline when CPU fails to decode. This will not speed up the work with heavy effects in any way, but it will be useful for cases when the processor does not have time to decompress heavy video - 4K, 1080p50 AVCHD/XAVC/HEVC video with a high bitrate (100mbps), owners of weak laptops will notice the acceleration best of all. This functionality has been added for Intel processors with QSV since 2015.3.

Mercury Playback Engine GPU Acceleration

For professional work, the speed with which the video is processed is fundamental. Shaders are responsible for all image manipulations. The counting speed on CUDA for such operations as transcoding from 1080p25 to 576i will increase by about 5-6 times. Color correction is also highly dependent on the GPU. The image quality in this case is much better than when working on the central processor. Thus, the video renderer must be Mercury Playback Engine GPU Acceleration CUDA or OpenCL (enabled in File|Project settings|General).

At the moment, the program automatically detects the presence of a suitable video card. However, there are nuances: Adobe is gradually phasing out support for old models of video cards (on the one hand, this means that new versions of programs are simply not tested on old cards, on the other hand, video card manufacturers stop supporting old models in new drivers); there is a version of Premiere that came out earlier than the video card, and he does not know this; For one reason or another, older versions of Premiere might not detect or enable acceleration. You can try to prompt the Premier manually.
If your NVidia video card is not defined as having GPU acceleration, and only Mercury Playback Engine Software Only is available in the Project Settings panel instead of GPU Acceleration:

then you need to write it in the file C:\Program Files\Adobe\Adobe Premiere Pro CS6\cuda_supported_cards.txt. The list of officially supported ATI (Radeon) video cards is in the file opencl_supported_cards.txt and can be added manually in the same way. In Premiere CC, Adobe allowed support for all CUDA and OpenCL chipsets, it was enough to go to this settings panel at the first start and turn on the GPU manually. Theoretically, it is not required to register manually, but in practice, if Premiere CC does not see your video card, you will need to create this file yourself and enter your video card into it (example file NVidia CUDA, Radeon OpenCL).

You can easily check the reason by calling the console (Ctrl + F12) and running the GPUsniffer command in it. In the text output there will be a reason: * Not chosen because of insufficient video memory- little memory on the video card, * Not chosen because of old driver- old video card driver, etc.

New versions of Premiere need new driver versions, if the new drivers do not support new features for your old video card or do not support the old video card at all, then you will have to work on more old version Premiere. Also, CC2015 and newer may not see Kepler video cards after the first launch of the program after loading, you need to exit the premiere and start it again. FROM AMD drivers Radeon Crimson will not have GPU acceleration on older AMD Radeon HD 7xxx and earlier cards.

Adobe Premiere CS3, CS4 do not support CUDA/OpenCL hardware acceleration and it makes no sense to prescribe a video card in them.

There is a peculiarity in the work of effects: if among the effects applied to the clip there is one that does not support GPU acceleration, then all other effects are also switched to CPU mode. Adjustment layer this applies to the fullest.

this picture shows how GPU accelerated effects are marked in Premiere

AMD dual or quad core - 96 gpu cores or more
AMD FX 6 or 8 core - 384 or more
Intel dual core - 96 or more
intel core quad - 192 or more
Intel I7 first generation - 384
Intel I7 Ivy Bridge - 1344
Intel I7 Ivy Bridge/6 cores - 1664
Intel I7 Coffee Lake/6 - 2944

The GPU may have fewer cores, but then editing will slow down.
If you have old computer, for example quad core at 2.0 GHz with 4 gigabytes of memory, it makes no sense to buy a GTX-780. For such a system, it is better to add memory and use a video card with about 300 cuda cores. If you have a very weak Core Duo, then there is an opportunity on the market to buy a used xeon cut for your socket for cheap.

Export

For h.264 hardware encoding, there are the following options:
1. Install plugin voukoder(NVidia/AMD) - the plugin encodes the video card in h264/h265 format, the speed is not lower than realtime.
2. If you have an Intel processor with Quick Sync and Premiere 2017.1+, use hardware encoding in the standard Premiere export.

3. Use external hardware encoders through the Advanced Frame Server plugin.
4. For Premiere CS 5.x, 6.x install the package Rovi Total Code 6.03 which includes the h.264 codec with CUDA support (does not work with video cards of the Kepler architecture and newer, i.e. 6xx and newer series of video cards are not supported).
There is no hardware encoding for exporting to mpeg, prores and other formats.

Premiere versions and performance

Newer versions show better performance. Testing CC 7.2 vs CC 2015 9.1 on the Lumetri effect by loading one 1 LUT .cube. Lumetri in Premiere CC, unlike CC 2015, does not yet use GPU acceleration, but it is interesting that in pure software mode CC 2015 is faster:
cc7.2 GPU ON, 3.4fps CPU 35%
cc7.2 GPU OFF 2.9fps CPU 45%
cc9.1 GPU ON, 25 fps CPU 22% GPU 8%
cc9.1 GPU OFF 3.2 fps CPU 43%.

The downside of new versions may be higher resource requirements. This can manifest itself as various failures in the work on the project and during export.
Program changes are not always good for performance. Prior to version CC 2014, Multicam worked fine, but since this version, there have been serious performance problems when editing material with interframe compression with a project length of more than 5-10 minutes. The problem is that if Premiere does not have time to read the frame, then the delay starts to accumulate exponentially, making normal work impossible.

Premiere and Memory:

It would seem that Premiere is not so critical to the size of the memory, however, in some situations, the lack of memory can paralyze the work. When memory is low, let's say 4 GB, Adobe programs can use a maximum of 2.5 GB for their work. That is, if only Premiere is running, without After Effects and Photoshop, then it has at its disposal best case 2.5 GB of memory. This is enough for simple DSLR video editing, but if the project becomes more complicated, for example, AVCHD 1080p50 with Warp Stabilizer, Neat Video noise reduction, Lumetri color correction, h.264 encoding, then the computer starts to freeze seriously, so much so that the mouse slows down. If you look at such moments in the task manager, it becomes clear that the system goes into a deep swap, although there may be 1 GB of memory free.

The way out in such a situation may be the following: Edit / Preferences / Memory - Optimize rendering for: Memory. As a last resort, you can try turning off the Maximum bit depth option (when working on the GPU, this option is always enabled, regardless of the user's choice. When working on the CPU, turning it off negatively affects the quality of any color correction).

You can export when there is not enough memory through Adobe Media Encoder (Queue button), after which you can close Premiere.

You can also disable the Superfetch system service, which is engaged in advanced caching, which is pointless and harmful when there is a shortage of memory.

New Premiere versions low physical memory can be a problem, there are often complaints that "Premiere 2017 crashes in the middle of exporting". In such a situation, a significant increase in the paging file can help. Since extensive use of the swap file cannot improve performance, we avoid it. First you can try to optimize the effects, try to encode in a simpler codec.

The number of processor cores and hyperthreading do not affect memory requirements, which can be easily verified by disabling the cores in task manager. If you have a lot system memory, do not give it all to adobe programs - during operation, disk operations are actively cached, and the presence of free system memory can speed up the work.

Adobe Media Encoder

In a programme MediaEncoder, CUDA acceleration has appeared since update 7.1 for Media Encoder CC from 10/31/2013. For it to work, the appropriate renderer must be selected.

If your NVidia video card has CUDA, but it is not possible to select the Mercury Playback Engine GPU Acceleration renderer, then you need to manually create a file C:\Program Files\Adobe\Adobe Media Encoder CC 2014\cuda_supported_cards.txt and register your video card there. The situation with Radeons is similar.

You need to understand that transcoding video files in MediaEncoder and exporting a project from Premiere/AfterEffects are different operations. When converting video files from one format to another, the render engine AME enables GPU acceleration when resizing/frame rate of the video, and if only the conversion to another codec is done, then nothing is accelerated. The Premiere/AfterFX project is calculated in a different way: for this, AME loads the premiere/afterfx core into memory and GPU acceleration when calculating all effects and transformations within the project does not depend on the Media Encoder, but on the Premiere settings in the project. In order for GPU acceleration to work on all Premiere effects when rendering in MediaEncoder, the Import sequences natively option must be off.

When properly configured, export speeds from Premiere and AME versions 7.1 and later will be the same.

How to control the operation of the GPU

You can check how the graphics card chipset (GPU) is actually used by the GPU-Z program. GPU-Z shows with checkmarks whether your NVidia video card has CUDA, or your Radeon OpenCL, and during rendering it is clearly visible how the GPU of your video card is loaded (GPU Load). Please note that other programs running on the system, as well as plug-ins (for example, Magic Bullet Looks) can load the GPU on their own and regardless of the settings of Adobe programs, and this will also be displayed.
The line Video Engine Load during export (encoding) shows the load of the nvenc block, while working on the timeline (decoding) the load of the block responsible for decoding.

CUDA and After Effects Acceleration:

When working in After Effects, the program can use graphics card resources in the following ways:
- acceleration of the 2D interface of the program - works on all video cards;
- OpenGL - available on almost all video cards, accelerated preview (Fast Draft), OpenGL plugins (for example, Element 3D);
- an alternative core for rendering 3D layers (with a camera, light sources) called Ray-traced 3D - only for NVidia video cards.
AE 14.0 has a new renderer for 3D layers - the built-in Cinema 4D core.
Gradually, GPU acceleration appears for built-in effects: in version 14, these are Lumetri, Fast Blur, Brightness and Contrast, Find Edges, Hue / Saturation, Mosaic, Glow, Tint and Invert.

When exporting, After Effects works in the following order: first, a frame on the timeline is rendered (all layers with all effects), then the rendered frame is compressed (encoded) into the output file format. At the first stage, AE uses the available accelerations of the video card described above, at the second stage the situation depends entirely on codecs and is described in the section on Premiere.

Anyway, After Effects needs a fast CPU and a lot of memory(16 GB or better 32 or more), without this, the presence of a powerful video card will not have any effect, in addition, many heavy plugins simply do not use CUDA and work only on the central processor or on the universal OpenGL acceleration. Unlike Premiere, the presence of GPU acceleration on the video card will speed up work in fewer projects.

Difference between OpenGL and CUDA
Hardware acceleration of video cards is provided by special units on the GPU chip: Render output units (ROP), Texture mapping units (TMU), Unified shaders (CUDA cores). There are two technologies for using the GPU of video cards: OpenGL and CUDA (for video cards from ATI and Intel, the analogue of CUDA is called OpenCL).
OpenGL describes the entire 3D scene, and this description is in no way dependent on the video card, but it cannot perform all the functions of After Effects by means of it. OpenGL performance primarily depends on the number and power of ROPs and TMUs involved in 3D rendering. OpenGL is also responsible for 2D graphics in the system - for acceleration user interface(Hardware BlitPipe), video mode control, video memory operations. The OpenGL-powered Fast Draft mode of the Composition window is optimized for very fast draft quality previews.
From an AE point of view, the OpenGL features are not enough to use it in the final render, but for plugins that use it, its performance is very important.
CUDA means direct programming of GPU cores, it is a direct full access to the computing power of the video card. To put it simply, many CUDA cores quickly process a lot of numbers, but they do not work with an image as with a 2D or 3D scene. Some kind of OpenGL functionality for CUDA is made by NVidia through the OptiX library, where the main program running on the CPU performs mathematical calculations on CUDA shaders. Rendering through this library in After Effects is called Ray-traced 3D. Ray-traced 3D doesn't support all After Effects features, but with the right compositions, it can outperform a CPU render many times over. Whether you win or not is best determined by test-rendering your working project.
From the point of view of working in AE, on compositions with 3D layers, this can give a good increase in speed, and CUDA and OpenCL can be directly used by plugins.

Does the graphics card support OpenGL and CUDA
OpenGL is supported by all NVidia, AMD, Intel graphics accelerators. Fast Draft requires OpenGL 2.0 or higher and Shader Model 4.0 or higher. As a rule, there are no problems with this. CUDA version The driver must be 4.0 or higher (CC requires version 5.0+). Versions can be checked in EDIT/Preferences/Preview/GPU Information.

If the versions are lower, then you need to update the drivers from the NVidia website. If it doesn't help, then it's time to buy a new video card. If your video card has CUDA, but GPU acceleration is not available, and only software mode is possible, then you can manually add your video card to the file C:\Program Files\Adobe\Adobe After Effects CS6\Support Files\raytracer_supported_cards.txt. For After Effects CC and newer, it may be sufficient to check the Enable untested GPU... checkbox in the EDIT/Preferences/Preview/GPU Information panel

Ray traced 3D
3d ray tracing render Ray traced 3D appeared since CS 6 (version 11.0.2 and newer), it calculates 3D layers, camera, light sources on the video card in the composition in which it is selected by render. Only CUDA GPUs of NVidia video cards are supported. There are features of work: the final render can become many times faster, or it can turn out to be slower than the classic CPU render, depending on the composition and video card. Also when turned on graphics core Ray-traced 3D simultaneously speeds up display in the Composition window when editing a project.
There are limitations: the GPU renderer does not support a number of program functions related to blending modes, track matte, and a number of effects, such as the Pin Tool, i.e. not suitable for all compositions.
Versions prior to CC 2015.1 do not support Maxwell chipsets - GeForce GTX 750Ti, all 9x0 series. Pascal chipsets are not supported in 2017.2. Apparently Adobe does not have time to update the license for someone else's library, but nothing prevents us from doing it manually by replacing optix.1.dll (download OptiX 3.9) in the Adobe After Effects CC 20xx/Support Files folder.
As an alternative to Ray-traced 3D, you can use Video Copilot Element 3d, Zaxwerks 3d Invigorator, Mettle ShapeShifter plugins in projects, which are faster and more powerful than Ray-traced 3D. Version 14 introduced a built-in Cinema 4D renderer.

To enable Ray-traced 3D you need:
1. Turn it on in AE by going to the menu EDIT/Preferences/Preview/GPU Information (picture above)
2. Specify it for each composition in which you decide to use it:

IMPORTANT TO UNDERSTAND!!!- CUDA (Ray-traced 3D) in AfterEffects only processes 3D layers in a composition that is rendered as Ray-traced 3D. 2D layers are rendered in Classic 3D anyway. If CPU is selected in the EDIT/Preferences/Preview/GPU Information panel, then regardless of the renderer specified in the composition, Classic 3D will be enabled.
The use of CUDA does not guarantee total acceleration: if you make 3D from a 2D layer and turn on Ray-traced 3D, then CUDA will turn on, but the speed will drop, because on the transformation simple elements in space Classic 3D is faster. But if you complicate the scene: add lights, shadows and depth of field, then the performance of Classic 3D drops sharply and Ray-traced 3D becomes confidently faster. Thus, Ray-traced 3D should be installed only for those compositions of the project where it gives acceleration, while wrong choice rendering will slow down. If a composition has a layer with another Ray-traced 3D composition nested, the render selection for them is independent.
Understand how it works better by doing Ray-traced 3D/Classic 3D test renders. Before the test, do not forget to clear the caches - Edit/Purge/All Memory & Disk Cache. Time and monitor CUDA load. You can control the GPU load in GPU-Z(GPU Load value).
All this is convenient and correct - in the project you need to combine 3D elements optimized for video card accelerators with 2D and 3D elements that use the entire functionality of After Effects.

Speed ​​up editing. Enabling OpenGL

In order to use the raytraced 3D core working through Cuda when editing a project, you need to select the GPU in the EDIT/Preferences/Preview/GPU Information panel.

It is also possible to use GPU resources through OpenGL, that is, to use the capabilities of AMD (ATI), Intel HD Graphics and the same NVidia video cards through the API of 3d OpenGL accelerators. This speeds up work when editing a project: used when rendering previews, for rendering the AE interface when editing a project, and for some effects (Cartoon, Magic Bullet Looks and Colorista effects use OpenGL for both editing and exporting).

OpenGL for display in the Composition window when editing and for previews is enabled by the Fast Preview / Fast Draft button in the Composition window. Due to limitations of the OpenGL standard, not all After Effects features work, so Fast Draft is not applicable to all projects.

Another option to speed up your work in editing: enable Hardware Accelerate Composition(if you have CC 2015, then you need version 13.6+): In the Edit / Preferences menu, select Display, and enable Hardware Accelerate Composition. This option is responsible for hardware combining layers and drawing interface elements in the Composition window (Hardware BlitPipe).

Multiprocessing: speeding up the final rendering

After Effects has a long history of development, going back to the time when the program was called CoSa AfterFX and the computer had one processor with one core. Accordingly, not all program functions, and not all external plug-ins can parallelize their work on several cores. This problem with every new version is removed, but for older versions or the use of older plugins it may be relevant.

More memory makes it possible to use the option Multiprocessing. To enable it, select Memory & Multiprocessing from the Edit / Preferences menu. In the middle of the window that appears, turn on Render Multiple Frames Simultaneously (render multiple frames at the same time). After that, it will be possible to set the amount of memory available for each processor core for rendering. Optionally, select a value based on the installed amount of memory and the number of CPU cores. If there is not enough memory, After FX will automatically reduce the number of cores involved. Note that as of Media Encoder and AE CC 2015.0 this option is disabled.

In some cases, this option allows speed up rendering, but at the cost of more memory. On the final render, additional copies of After Effects will be launched in addition to the copy of After Effects in memory, according to the number of CPU cores involved, only without the user interface. That is, on a 4-core processor with Hyper-threading, 9 copies of After Effects will be in memory. You need to understand that AE will not work 8 times faster from this: if some effect can parallelize its work on several cores by calculating one frame, then there will be no acceleration from Multiprocessing, because in order to process 8 frames at the same time, you need to prepare in 8 times more information, send 8 times more information from memory and manage 8 processing threads in a consistent manner, for example, about 1 GB of memory is reserved for processing a 17 megapixel photo, therefore, 8 GB is needed for eight threads. This is an extra overhead. If, however, when calculating the effect, only one core is involved, and the rest are idle, then giving each core a frame to calculate will certainly be effective. The actual effectiveness of this method depends on many conditions and it is best to check empirically by monitoring the processor load in the Task Manager (Task Manager). Adobe recommends running 4-6 threads with 8 cores.

network render
After Effects allows you to set up rendering over a network, on multiple computers. Before you start doing this, remember that the fonts/codecs used in the project must be installed on all machines involved in the rendering.

Export to h264 and After Effects CC
Starting with the CC version, export to h264, WMV and MPEG is disabled by default. And since the SS 2014 version, it has been completely disabled. This was done due to the fundamental impossibility of using two-pass codecs in After Effects. For these formats, developers recommend exporting via Adobe Media Encoder. IN real work it is most practical to directly export to any format without interframe compression, for example, avi UT video codec, qt Cineform codec, PNG; and then re-encode to h.264.

For the After Effects CC version, the possibility of single-pass h.264 encoding remains, for which you need to enable direct export to h264 in the settings, and manually configure the Output Module in the render queue:

It remains possible to directly export to h264 via Quicktime, unfortunately the h264 codec in QT is of poor quality. You can also install external AfterCodecs codecs based on ffmpeg.

Adobe Media Encoder
Adobe Media Encoder does not support Render Multiple Frames Simultaneously - an option in AE to speed up rendering, but it supports many export formats, and you can also connect hardware-accelerated codecs in it.
In reality, AME's biggest drawback is that it doesn't support Ray-traced 3D, and worst of all, when encoding a frame with interframe codecs, Media Encoder makes AE constantly recalculate all the previous frames in the group.
In summary, before exporting via AME, try exporting a few frames directly and keep track of the time. If the speed drops when exporting via AME, then it is more practical to export directly (for example, TIFF sequense, avi / UT video, mov / Cineform) and then convert your video to the desired format.

Simultaneous work of AE with others Adobe programs
After Effects tends to cache all preview rendering results, and uses all available memory, no matter how small. Such caching significantly speeds up editing in AE, but the lack of memory leads to various crashes and crashes at the most inopportune moment. To minimize this, when switching between AE and Photoshop or Premiere, simply free up memory: Edit/Purge/All Memory.

GENERAL ISSUES

Video card memory
You need at least 1 GB of memory on the video card, and it is better if it is DDR5. DDR3 memory is usable, but if you're buying a new graphics card, DDR5 makes more sense. For full HD operation, formally with a large margin, 2 GB is enough, however, when one frame is composed of several source frames (picture in picture) or effects are used that simultaneously process several frames (noise reduction, etc.), memory consumption increases several times. If GPU acceleration is used, then all this memory must be on the video card. Therefore, 2 GB is a reasonable choice, while 4 GB is better and a must for UHD/4K video.

OpenGL in Premiere
OpenGL Premier does not use OpenGL, some plugins use it. OpenGL support is provided at the system level. If you install a video card, OpenGL acceleration is added along with its drivers. Performance settings are made from the utilities installed with the video card drivers. All this is well known to gamers.

Quadro
The only reason to use Quadro video cards in video editing is in the case of 10-bit material and a 10-bit monitor, such as HP Dreamcolor. Otherwise, Quadros aren't fast enough or too expensive.

Nutrition
NVIDIA GeForce cards draw between 200 and 700 watts at full load (paired or SLI).
It should be remembered that other components of the system also consume energy. The second in terms of power consumption is the central processor, for the quad core Q9650 it is 65 W, in this case a 300 W power supply is sufficient. Or the I7-930 draws up to 130W, and a 500W PSU might not be enough.

Cooling
It is necessary to control the operating temperature of the video card. There are several programs that allow you to do this. For example, the same GPU-Z or HWMonitor (you can download from www.cpuid.com). If necessary, additional cooling is provided. Also monitor the temperature of the CPU.

Regardless of the measures taken, at least once every half a year it is necessary to clean the radiators and the fan from dust.

Working with multiple GPUs
Graphics cards like the GTX 690, Titan are essentially dual graphics cards already. Premiere CC works with them, and, moreover, it works if there are several video cards in the system, and SLI mode is not required, which means that video cards of different series can be used. This mode of operation is also known as MultipleGPU. The performance gain here is not unambiguous and depends on the balance of the computer configuration.
Additional opportunities for maneuver are given by the use of the GPU by third-party plugins. In this case, you can assign the CUDA acceleration of one video card to the Premier, and assign the OpenGL acceleration of another video card (for example, Radeon) to the plug-in (for example, the Magic Bullet series works through OpenGL). In addition, there are more and more plug-ins that directly use MultipleGPU - Neat Video 4, Beauty Box 4, Twixtor, DE:Noise, ReelSmart Motion Blur.

Disk Optimization
It is necessary to prevent fragmentation of working disks, control it and, if necessary, perform defragmentation. For Premiere, place the Media Cache on a dedicated rapid HDD is better than SSD. For Adobe After Effects enable Disc Cache in Preferences/Media & Disc Cache and place it on a dedicated rapid disk, ideally an SSD; also enable Disc Cache = Current Settings in the Render Settings of the Render Queue.

Photo
If you upload photos of ~20 megapixels to the project, and then work with them, for example, reducing them to 25%, then it is better to reduce them in Photoshop first. Thus, each such operation with this photo in Premiere, each effect will be performed 4 times faster.
In addition, there is a limitation of GPU acceleration in Premiere: ((width*height)/16,384) megabytes of memory on the video card is reserved for frame processing. If the value received exceeds the amount of available memory, Premiere's rendering switches to the CPU. This means that on this frame GPU acceleration will not work on any effect. For example, the image size from the Canon 550D is 5184×3456 pixels. As a result of the calculation, we get 1,094MB, which is physically more than 1GB of memory on the Quadro FX 3800.

CEPHtmlEngine
This process is part of Adobe's new approach to interfaces: responsible for the operation of the Library panel (access to cloud media resources) and for the new Premiere launch window; every 5 seconds climbs into the cloud and on processors without HT can take 30% of performance. Adobe offers patches to treat crooked AngularJS code. We believe that the code that stupidly polls I / O in a multitasking system is not acceptable in principle, and we demolish the CEPHtmlEngine folder located in c:\Program Files\Adobe\Adobe Premiere Pro CC 2015\

AdobeIPCBroker
Approximately every 30 seconds, a process named AdobeIPCBroker.exe sends 1 to 1.5 kb encrypted data to Adobe servers. Since we need to work, and not be constantly connected to the cloud, the file c:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\IPC\AdobeIPCBroker.exe can be replaced with this .

Lumetri Scopes
If the timeline playback is not fast enough, then keep in mind that the displayed Lumetri Scopes panel requires a lot of resources.

Aero
Aero runs on GPU acceleration and consumes resources. So it can be turned off

https://helpx.adobe.com/premiere-pro/system-requirements.html - system requirements
http://blogs.adobe.com/aftereffects/category/technical-focus
https://www.cpubenchmark.net/common_cpus.html

3 ways to speed up android!

Smartphones and tablets are all over the world. Approximately 80% of users of these gadgets are located on the Android OS. But, despite the sheer popularity of this operating system has a drawback: android slows down! And this is far from an isolated case.

So, this article is about how to speed up Android? Immediately note what to buy new phone, in a fit of irritation due to unstable work is not necessary. Well, let's look at a number of simple steps to speed up the android, which you should also be able to handle.

Method #1: Android Presets

This method will have a strong impact on the speed of the processor. Now I will show you how to set up the power mode. On different Androids, the installation is different.

1. Settings -\u003e Power-\u003e Power Mode you need to select the "High Performance" mode.

2. Settings - My device - Energy saving - Processor - Uncheck (Limit the maximum processor performance). However, this will drain the battery faster.

If you want both fast performance and , then even here there are options. For example, you can check the boxes for Display (Use low power for the screen) and leave the box checked for Turn off tactile feedback. feedback» (may extend battery life). These two points will not affect the speed of work, but the battery charge will be saved.

3. In Android 4.0 +, you need to speed up the graphics subsystem:

Settings->For developers->check the box "Accelerate the GPU" (GPU acceleration)

At the same time, the graphics processor will adapt to many games. But some applications may refuse to work. Some devices may not have the listed menus. Perhaps the manufacturer has already optimized them.

Note! I'm sure there are quite a few newbie users out there. And by accelerating the processor, you may not achieve anything, because all the memory is completely clogged with rubbish.It is with this problem that we will fight in the second method, described below.

Method number 2. How to clean up Android and speed it up?

The system needs to be cleaned regularly or just keep an eye on all the installed applications:

• Try to install applications as needed, and not for fun, pay attention to the weight of programs, read reviews before downloading.
• If you do not use any application for a long time, then delete it, do not think that you may need it. if you really need it, then download to Google Play again.
• Install Antivirus. Perhaps the system is buggy due to viruses. Perfect for Kaspersky.
• Remove autostart of unused services:

Settings->Applications->Running Services

Settings->Application management->Running

We stop unnecessary ones. To prevent them from starting after a reboot, you need to disable them via special application- process manager. There are a lot of them on Google Play. After getting rid of unnecessary services, the system will start to boot faster and become faster.

In Android 2.3, you need to remove synchronization with services that you do not use:

Settings-> Accounts and synchronization and on the "Account Management" tab, disable synchronization with all unnecessary services.

Yes, in Google account It doesn't hurt to disable the synchronization of contacts, Gmail, Picasa, calendar and similar services. When no services are being used, the Auto Sync check box in the Accounts & sync window should be cleared.

Android account settings

By removing the auto-update of applications on Google Play, you will not only speed up your smartphone, your device will keep its battery longer and save traffic if your mobile Internet is not unlimited. If you need to update, you can also do it manually.

To disable auto-update apps in Google Play Store necessary:

Open Google Play Store -> Settings - Auto-update applications - Never or Only via Wi-Fi, save GPRS traffic and take care of the battery.

It is advisable to turn off the animation: Settings-> Display-> Animation-> item "No animation"

To speed up Android, remove the live wallpaper, put, a simple picture on the screen saver, it is advisable not to put photos. Set the home screen to simple mode. To do this, open the settings - My device - Home screen mode - Simple mode. Advantage easy mode is that it makes the device easier to use with a simplified screen layout and large icons.

Also don't forget to delete home page unnecessary widgets, like time, calendar, search and more. I place a flashlight on the main page as much as possible, because there is no other way to turn it on.

You can remove the widget from the monitor screen by pinching and dragging it to the trash.

Disable geolocation and GPS

Surely you do not use GPS as often as you have it in active mode. That is why turn off such gadgets. This affects both the speed of the smartphone and the battery.

You can pull down the shutter from the top of the monitor and turn off the GPS. Second option: Settings -> Coordinates ("Location" or "Location data", etc.), then uncheck the boxes.

Clear app and browser cache

If you regularly clear the cache on your smartphone, you will make a big contribution to speeding up your Android.

Settings->Apps->App Management

Settings - Options - Application Manager

Now it remains to select one or another application, click on it and press the "Clear cache" button. Do not be afraid that some important data will be deleted (this will not happen), however, it is better to remember passwords. The browser can be cleaned by directly opening it.

Method number 3. How to speed up Android if you use microCD

Now people massively use microCD-cards. A beginner should ask the question, what side is the memory card in the article about the speed of the smartphone. So, when you buy a microside card, you pay attention only to the volume in GB, but you should think about more than that.

The main indicator of modern flash drives is the speed class. This moment as well as the amount of memory is written on the media itself.

Speed, as a rule, is indicated by a number that is inscribed in the Latin letter C: 2, 4, 6 and 10 (speed classes). They indicate how many megabytes per second can be written to a memory card. if Class is 10th, then the speed can exceed 10 MB/s. This used to be the case, but today most classes with the letter C are obsolete. You should pay attention to the real speed of writing to a flash drive, which is indicated directly on the memory card, so as not to confuse anyone.

In addition to the above designations, there are others, for example, for microSD with increased write speed, the UHS (Ultra High Speed) standard is used. It is designated by the number of the speed class inscribed inside the Latin letter U.

UHS Speed ​​Class 1 - from 10 to 104 MB/s, UHS Speed ​​Class 3 - from 30 to 312 MB/s.

But here it is very important not to get confused. Along with UHS, there is a similar designation of card types: UHS-I and UHS-II.

It is important not to confuse with UHS-II and UHS-I. There are two rows of contacts on the back of the UHS-II card. A novelty that provides even higher data transfer speed. So far, the smartphone does not support UHS-II.

Many of us have experienced unsatisfactory performance of our Android devices. Lags, "glitches" - all this pretty much gets on your nerves. In this article, I will try to list some sources of the problem and how to fix them.

Live wallpaper

Widgets and desktop icons

Unnecessary applications

Application autostart

Now I will list not problems, but ways to optimize devices.

"Acceleration"

Firmware

Clearing the App Cache

Increasing the speed of the video subsystem (4.0+)

Disable Animation

You perform all manipulations with your device at your own peril and risk, I am not responsible for them. I hope I helped you.

The presence of powerful hardware does not always mean fast operation of the device. In some cases, optimization leaves much to be desired and the user can try to speed up their smartphone or tablet on their own. There are several methods that can help in the implementation of the task. These methods are discussed in our article.

Remove all unnecessary applications

There are applications that can use extra resources. If these applications are not used, it is worth uninstalling them.

This includes applications that are installed on the smartphone upon purchase. Some of them cannot be removed, they are built into the firmware, while others, if you do not need them, it is better to remove them.

Don't use live wallpapers

Live wallpapers, oddly enough, require additional resources. Of course, they look beautiful and are pleasing to the eye, but if you need speed, you should still say goodbye to them.

Don't use third party launchers

Don't use additional widgets

Approximately the same can be said about widgets, which can be placed on the desktop in abundance. Try to keep only those widgets that you really can't do without, like the clock or the weather forecast. Other widgets should be removed from the desktop, because they, albeit a little, but still “eat up” memory.

Disable unnecessary applications

There are applications that work in background but they are rarely needed. In this case, we are talking about third-party applications, and not about system ones, which are not recommended to be disabled, since this can lead to a crash in the system.

Disabling the app is easy. Go to the settings, find the section with applications, select the desired application, go into it and click "Stop".

Turn off GPS and geolocation

Location settings are very important, but they should only be used when needed.

This, by the way, will help, among other things, increase the autonomy of the device.

Clean up with third-party apps

Do not forget to delete the cache and other temporary data, which can also affect the speed of the system. As a rule, this third party applications like Clean Master, which allow you to delete temporary files, but on some devices they are already embedded in the firmware.

Use GPU acceleration

Go to the menu, find the "For Developers" or "Developer Options" section.

If you do not see such a section in your site, you need to enable it. Find the “About phone”, “About tablet” or “About device” section, go into it and click on the “Build number” item 7 times (sometimes you need to click a little more times, the system will tell you about it).

In developer options, enable forced GPU processing (2D hardware acceleration in apps).

At the same time, you can turn off the animation. Look for items like "Window Animation Scale".

Disable animation. Just be careful when editing parameters, some of them can lead to problems in the system.

Update Firmware

Sometimes performance problems are related to the firmware itself, which are solved by updating this firmware itself. Therefore (and not only) it is so important to update the software of your smartphone or tablet in time.

Do you have ideas different from ours? We will be glad if you tell us about them by commenting on the article.

Many owners of Android gadgets are faced with the problem of slow operation of the device and its.

How to speed up your tablet or smartphone? We will give some useful and really helpful tips, but first it's worth a little introduction. Android is an operating system that is almost the same as the familiar Windows. It has background processes, applications, operational and inner memory, processors. These factors affect the speed of a smartphone or tablet to varying degrees. Therefore, the issue of speeding up Android is solved in a complex way.

First, let's speed up the gadget on our own.

Power saving mode

The easiest way to speed up android work- set the power supply / energy saving mode to "Performance" or "Disabled". The exact wording depends on the firmware version and the device. This can significantly increase the speed of the system, but it will load the battery a little, because of which it will become. Although the difference is unlikely to be very noticeable.

GPU acceleration

Every Android device has a "For Developers" section in its settings. It is sometimes hidden from the crooked hands of prying eyes, so it needs to be unlocked. Go to "Settings" - "About phone" and several times click on the item "Build number". Now go to new section settings and check the box next to "Speed ​​up the GPU". If you don't find it, then given function works automatically, you can skip the step.

Disable Animation

Animation when opening windows and transitions can adversely affect the speed of a smartphone, especially a budget one. Visually it looks nice, but speed is much more important.

Go to developer settings and find two menus: "Window: Zoom" and "Transition: Zoom". Turn off the animation in both.

Installing and storing applications

Here are some banal but very important tips:

• Install and store in memory only those programs and games that you use regularly.
• If possible, try to install lightweight applications that are not demanding on system resources.
• Ruthlessly delete games and programs that you do not use.

It is important to understand that clogged physical memory is one of the reasons for the unstable operation of the device. by deleting unnecessary applications and games.

Desktop, widgets, live wallpapers.

Three indicators are included in one subheading not by chance. It is important to keep your desktop in order, not to clutter it with icons, widgets and beautiful live wallpapers. This, of course, is beautiful, but speed requires sacrifice.

Autorun and background processes

As soon as you turn on your smartphone or tablet, various services and background applications automatically start on it. Very often in this list there are completely unnecessary and unnecessary programs that you do not use. They need to be disabled:

• Go to Settings - Applications - Running.
• Disable those programs and games that are not needed. IMPORTANT: do not touch system services like Google Services, Settings, etc.

Disable account sync

You can connect several accounts to any smartphone or tablet running on Android: Gmail, VK, Twitter and others. They are automatically synchronized with the device, while consuming system resources and the Internet.

Go to "Settings" - "Accounts and sync" and disable synchronization with those profiles that are not needed.

Auto-update apps

By default, our favorite Google Play store automatically updates everything installed games and programs. Of course, this can cause system slowdowns, so it is also recommended to disable this feature. This is discussed in more detail in a special.

This is where the basic capabilities for overclocking Android ended - it's time to turn to third-party programs and methods.

Special applications

There are several decent programs in the app store designed to speed up smartphones. The most popular and recognized is DU Speed ​​Booster (Cleaner).

If for some reason you do not like the utility (although this is unlikely), you can find .

Cleaning the system of debris

The operating system of the "Green Robot" tends to be clogged with cache files, cookies, history of downloads and pages visited in the browser. Memory occupies, means slows down work. For a comprehensive cleaning of the system from garbage and unnecessary temporary files, we recommend using.

Also, programs to optimize battery life will help speed up the phone. Everything is interconnected. An excellent solution would be Battery Doctor, which we are talking about.

These programs automatically scan systems for unnecessary processes and data and, with our consent, delete files, folders and other garbage. Thus, both physical memory and RAM are freed, and the processor is also unloaded.

Memory card

Most smartphone owners have a memory card installed, which is necessary for storing photos, videos, applications and other files. But it can also cause the gadget to slow down. This is because memory cards can either be slow or outdated.

MicroSD cards have special designations (2, 4, 6, 10) that correspond to the speed of information exchange. The higher this number, the better. Age cards and those that come with devices are usually type 6 and below. This may be one of the reasons why Android is slow. It is recommended to replace the card with a new one with indicators above 6. You can learn more about choosing a flash drive.

Firmware

If nothing helps, then the only way out remains - flashing to custom, the most popular of which is .

Custom Firmware have a number of advantages over stock:

• The absence of unnecessary pre-installed applications that slow down the system and clog RAM. As a result, the device works stably.
• Rich functionality (the ability to increase and decrease the frequency of the processor to save battery, etc.).
• Timely system updates (especially useful for devices that are no longer supported by the manufacturer). With each new update, developers fix bugs and add exactly what users need, as in most cases they conduct discussions on the forums.

There are also disadvantages:

• Flashing a smartphone entails a loss of warranty and sometimes the possibility of turning into a “brick”.
• Unofficial firmware sometimes has some flaws (for example, if the phone has two cards, they may not be displayed correctly).