Premiere CC GPU Bug

Another strange behavior in Premiere CC. Again something new and "Exciting" So if you have an Anamorphic sequence, for example XDCAM EX 1080 50i (1,333 Ratio) and GPU acceleration - "ON" you will get this:
http://www.youtube.com/watch?v=AnxqMNElOiI&feature=youtu.be
Same thing happens if you place an anamorphic video on a progressive timeline.
My video Card is Nvidia GTX660 2GB, Windows7, 32GB RAM. In CS6 that worked fine. I just can't get it. If it's not a new feature and it all worked fine in previous version, how can it can be broken with a new release?
With each day i'm waiting for a bugfix patch more and more

Here are a few threads with a similar problem:
http://forums.adobe.com/message/5471506#5471506
http://forums.adobe.com/message/5386622#5386622
http://forums.adobe.com/message/5385912
One suggestion is to roll back to a previous driver.

Similar Messages

Premiere pro cc2014 bugs?

Hello
Has anyone updated Premier pro cc 2014 to the latest version. I havent touched it in ages because of all the bugs and constant crashing but im eager to return to several CC 2014 projects that I need to start using again.
Have the bugs been fixed is it worth using again?
Thanks
Philip

Here's a breakdown and he's the link to the original post. There's some feedback from other customers there: What's Fixed in Premiere Pro CC2014.2
As noted in the blog post for the 2014.2 release, while this update includes a few new features, it is chiefly geared toward addressing known issues. The blog post lists the higher profile fixes. Below is is a more comprehensive list.
Import
Red frames in MXF clips from a particular model of camera.
Cannot import ARRI Alexa Open Gate clips
Import fails for IMX 30 MXF clips stored on certain proprietary media asset management systems. Error: Unsupported format or damaged file.
Some XDCAM HD Proxy files show red frames
Some .VOB clips play only audio or shows media pending indefinitely
Premiere does not recognize timecode for audio-only MXF files written by some third-party programs.
Only the first frame of video plays for AVC-Intra50 MXF files stored on certain third-party media asset management systems.
Spanned DVCPRO clips have incomplete audio if an XMP file is present but no media cache/pek file are found.
Some metadata from an Adobe Clip project does not get correctly logged on import.
Exporting & Rendering
Rendering fails for MXF media with Posterize Time effect applied
ProRes exports can be very slow when smart rendering
Encoded output can include black frames, corrupted frames, or frames from elsewhere in the sequence
Canceling export to P2 can result in low-level exception if the sequence duration is greater than a few minutes
Aspect ratio for IMX 30 widescreen anamorphic encodes is incorrect.
Edit to Tape: Audio drops out while playing out to tape
The Height setting for encodes to the GoPro Cineform codec is constrained to multiples of 8.
Smart Rendering: GoPro 2.7K footage cannot be smart rendered
AAF
Distorted audio in AAF exports with 24 bit embed option selected.
If a multichannel sequence has been nested into 2 channel sequence, then an AAF export yields the number of channels in the nest rather than the 2-channel mix-down
Certain third-party programs have problems relinking to video with Premiere's AAF exports. (Windows only)
If the first of two adjacent audio clips has a Fade Out applied, exporting as AAF converts it to a Fade In onthe second clip. (Mac only)
When AAF exports are opened in some third party apps, audio crossfades are treated as cuts or fade-ins.
Crash during AAF export if a video clip has multiple effects applied.
When AAF exports are opened in some third party apps, some audio clips and tracks are incorrect.
Crash upon exporting to AAF with disabled clips that have cross fades applied
If a multicam sequence with mono audio is nested onto a stereo or adaptive track, then exporting to AAF yields a stereo clip with the audio panned fully to the left.
When AAF exports are opened in some third party apps, rendered audio of is relinked automatically, but the video needs to be manually linked.
Playback
If a UHD ProRes clip is in an SD sequence an scaled to less than 50%, then scaling is ignored during playback at Full Resolution [GPU acceleration only]
Poor playback performance with certain third-party I/O hardware on OS X 10.9.
Crash during playback of R3D content [CUDA GPU acceleration only]
Audio
Audio sync is lost with some XDCAM content wrapped in QuickTime reference movie
Audio sync is lost when user starts scrubbing during playback while using certain I/O hardware.
When playing past an audio transition, the sound sometimes surges and has pops/clicks introduced
Audio dropouts, and Events panel reports "audio dropouts detected." [Prefetch purge related]
Audio dropouts in some scenarios after releasing memory (e.g., cycling focus to another app)[Prefetch-related]
Shuttling for an extensive time can cause audio dropouts
Project
If current user does not have write access to certain folders, the crash error message is uninformative (Mac only)
In Adobe Anywhere, crash when using keyboard shortcut to open Convert Project to Production dialog or the New Production dialog.
If multiple clients on a network use the same media cache location, then upon importing a given asset each client writes its own accelerator files.
The Find features in the Project panel and Timeline cannot search by Korean characters.
In Search Bins, moving focus by keyboard from one clip to another can cause the tree view to expand to show the bin where the clip is stored.
Project Manager/Consolidate & Transcode
If the destination drive has insufficient space, Premiere throws an "unknown error" rather than an informative message.
Project Manager writes some clips outside of folders
Consolidate and Transcode does not warn the user if the destination drive has insufficient space.
Unknown error can result from using Consolidate & Transcode with P2 content in the sequence.
In some cases, Consolidate & Transcode copies and renames the component assets for merged clips.
If Exclude Unused Clips is deselected, the components for merged clips sometimes still get copied; if the option is selected, the presence of merged clips can yield Unknown Error.
If the sequence being transcoded contains overlapping "soft" subclips, then some clips may be missing from the sequence in the consolidated version, and In/Out points may be incorrect for the subclips.
If Exclude Unused Clips is turned off and the project being transcoded contains "soft" subclips, then the consolidated version of the project does not have transcoded copies of the subclips.
If a sequence contains only audio from an A/V clip, using Consolidate and Transcode to some presets will fail with unknown error
If the sequences being transcoded contains two copies of a master clip, one of which was the product of Duplicating or Copying/Pasting in Project panel, the consolidated version of the project has only one instance of the master clip.
If the project contains multiple master clips for the same asset and Interpret Footage is applied, then the consolidated version will have multiple transcoded copies of the source asset.
If the transcoded sequence contains a hard subclip (i.e., "Restrict Trims to Subclip Boundaries" enabled), the resulting project item is a master clip rather than a subclip.
Merged Clips
Comment markers added to a merged clip get inserted to the component clips, but the Name & Comment entries are not saved.
Hang on right-clicking the current marker in a merged clip in certain circumstances.
Editing/Timeline
Crash on clicking the very bottom of clip in the Timeline and dragging to move the clip. [SubViewImpl.cpp-724]
Crash on Ripple Trim Previous Edit to Playhead for a clip group when that action completely deletes one of the component clips in the group. (TrackItemGroup.cpp-821)
Indefinite hang if sequence contains a QuickTime .mov with an unusual framerate and a CEA-708 caption track
Crash upon creating a sequence from a source with no frame rate specified (e.g., a title imported from a third-party-generated XML)
If a rendered-and-replaced clip has been trimmed, then Restore Unrendered can result in content being out of sync
Multicam
Audio is lost when flattening multicam sequences that were created with dual stereo movies.
If a multicam clip was created with Switch/mono and placed into stereo tracks, then flattening incorrectly maps the audio channels to stereo, with the right channel disabled.
Playing a multicam sequence in the Source Monitor can result in an unacceptable ratio of dropped frames.
Effects & Transitions
With Warp Stabilizer applied, Program Monitor shows only upper left corner of the frame, sometimes with alternating whole frames [GPU acceleration only]
Sub-pixel positioning is incorrect for non-linear alpha compositing [GPU acceleration only]
GPU transitions that depend on other layers cannot access those layers
Crash upon clicking outside the Direct Manipulation control for some effects.
Memory leak with certain third-party effects
Crash on clicking Setup button for some third-party transitions.
Loudness Radar' Track FX Editor intercepts keystrokes intended for editing titles (e.g., spacebar)
Crash (Pure Virtual Function Call) on adjusting parameters for some third-party effects.
Some third-party effects get frames from the wrong time in the clip.
UI/Workspaces
All open Project panels get reset to root upon switching between projects that use the same workspace.
The order of open Timelines sometimes gets jumbled upon closing and reopening the project.
Bezier handles for keyframe can be nearly invisible at default brightness.
Closing the Source Monitor when it's showing a scope (e.g., YC Waveform) crashes Premiere (error: CheckBoxControl.cpp-105)
HTML5 panels do not receive Tab events.
Redraw errors on maximizing an HTML5 panel.
Performance (Note: Most of these fixes are also listed under a product area)
In certain scenarios, performance is unacceptable when doing basic editing operations with waveforms displayed in the Timeline.
Scrubbing a growing file on an Xsan can result in very high bandwidth usage with some network configurations.
Playing a multicam sequence in the Source Monitor can result in an unacceptable ratio of dropped frames.
ProRes exports can be very slow when smart rendering.
Poor playback performance with certain third-party I/O hardware on OS X 10.9.

2013 Mac Pro, 10.9.3/4 and Premiere Pro - GPU Issues

Hello All
Since the introduction of Mavericks 10.9.3 and subsequently in 10.9.4, Apple Mac Pro (Late 2013 model) users have been affected with issues relating to video editing applications such as Adobe Premiere Pro CC and Da Vinci Resolve. It appears that since these updates the compatibility with the AMD D500 or D700 GPUs is broken and causing significant workflow problems.
Some of these problems include (particularly that I have experienced):
White lines appearing on the video in the program window during playback and encoding
Green and Pink lines appearing as mentioned above
Other odd image artefacts during playback
Poor performance when playing any clips with GPU accelerated effects or parameters
Struggling to playback footage at full resolution (not 4K just HD material which shouldn't be a problem)
Freezing and crashing of the application
Slow loading of media and saving of projects
Consequently, this is significantly affecting my workflow and I know I am not the only video editor suffering these issues. I have spoken to Adobe who are aware of the issue and say they are working with their partners to find a resolution. I assume and hope that one of those partners is yourselves and implore you to please elevate this issue to a more serious status as it really is becoming highly frustrating and starting to effect my business.
I'd be interested to hear from other users that are experiencing these issues and hopefully together encourage Apple and Adobe to get their heads together and fix what is broken and fix it ASAP. It isn't good enough that for a machine this pricey we are left out on a limb without an urgent fix being presented.
I hope we see a fix for this soon but failing that please make 10.9.2 available so we can at least roll back and become productive again.
Kind Regards
Alex
Owner and Principal Cinematographer
Camera On Films

Hello All
Since the introduction of Mavericks 10.9.3 and subsequently in 10.9.4, Apple Mac Pro (Late 2013 model) users have been affected with issues relating to video editing applications such as Adobe Premiere Pro CC and Da Vinci Resolve. It appears that since these updates the compatibility with the AMD D500 or D700 GPUs is broken and causing significant workflow problems.
Some of these problems include (particularly that I have experienced):
White lines appearing on the video in the program window during playback and encoding
Green and Pink lines appearing as mentioned above
Other odd image artefacts during playback
Poor performance when playing any clips with GPU accelerated effects or parameters
Struggling to playback footage at full resolution (not 4K just HD material which shouldn't be a problem)
Freezing and crashing of the application
Slow loading of media and saving of projects
Consequently, this is significantly affecting my workflow and I know I am not the only video editor suffering these issues. I have spoken to Adobe who are aware of the issue and say they are working with their partners to find a resolution. I assume and hope that one of those partners is yourselves and implore you to please elevate this issue to a more serious status as it really is becoming highly frustrating and starting to effect my business.
I'd be interested to hear from other users that are experiencing these issues and hopefully together encourage Apple and Adobe to get their heads together and fix what is broken and fix it ASAP. It isn't good enough that for a machine this pricey we are left out on a limb without an urgent fix being presented.
I hope we see a fix for this soon but failing that please make 10.9.2 available so we can at least roll back and become productive again.
Kind Regards
Alex
Owner and Principal Cinematographer
Camera On Films

Premiere Pro CC Bug Fix Update (7.2.2)

Hi,
Today a bug fix update was released for Premeire Pro CC. Check out this link for full details: http://blogs.adobe.com/premierepro/2014/04/premiere-pro-cc-7-2-2.html?scid=social21455164
Thanks,
Kevin

Hi Richard,
rnaphoto wrote:
Hi Kevin-
I see on another thread that lots of folks are having this issue. Since a Plural Eyes workflow if very common, I would expect that your testers would check that out pretty thouroughly.
We have beta testers and QE engineering constantly testing out common workflows, including with third party applications like PluralEyes.
Regarding this issue: we tried to test those problems with PluralEyes in house after we heard about them, but have not been able to reproduce the problem. That's why we're collecting media and project files from users.
rnaphoto wrote:
In the meantime, is there any way that folks can go back to 7.2.1? I think it would be good if Adobe would give us the option to go back when things go wrong.
Sure, I wrote a blog post about that: http://blogs.adobe.com/kevinmonahan/2014/01/29/revert-to-a-previous-version-of-premiere-pr o-cc-or-any-creative-cloud-application/
Hope that helps you.
rnaphoto wrote:
One really gets tired of dealing with these issues since they seem to be happening much more now that the CC allows fairly constant updates. Although constant updates may seem like a good idea to some, for many of us it seems like a lot of risk for not much gain since we are usually under the gun to get stuff done...
Sorry you feel that way, and not sure what other problems you were having, but most folks are enjoying the updates and not experiencing issues like that. FWIW, you never have to update if you don't want to.
rnaphoto wrote:
But I can't emphasize enough that part of the updating MUST include extensive testing using common workflows. I could have told you you had a problem within 15 minutes of installing this update...
I'm sorry, Richard. Unfortunately, it's not that easy. We could not even reproduce the issue in-house. So, there must be something different with your system, media, workflow, that we have not found yet. We are investigating the issue thoroughly, and hope to have a fix as soon as we can.
Thanks for understanding,
Kevin

Mercury Engine GPU bug/error/problem

Hi there
Im experiencing a very strange phenomenon with the Mercury Engine in hardware mode. I recently upgraded my computer so I am running on new hardware. I ran Production Premium on my laptop and my older desktop, both working without problems.
My new configuration is a 2600k i7, 16gig Ram, GTX 570. The problem will be best described with screenshots:
The top image was taken in software mode. This is the correct result, displaying like it does on my laptop and old pc. The bottom pic shows the same frame in GPU acceleration mode.
1. It looks like the Title texts' edge is shrunk by a pixel or so.
2. The layer below the text, the strap, is an animated AE composition. It contains a drop shadow at 50%. In hardware mode it looks like its about 20%
3. I have a 2 pixel 40% opacity black stroke applied to the strap. In hardware mode its almost completely invisible. I think the outline is shrunk as well.
To make it even wierder, if I click on the Title layer in the preview window in Premiere, ie, if I select it, it suddenly displays correctly. When I deselect it, its wrong. If I open the title editor, the text displays correctly. When I close the title editor, its wrong again in the playback window. The straps all display correctly when I work on them in AE.
This is forcing me to switch to software mode before I render, otherwise the rendered result is faulty. I'm 99% sure its a CUDA thing.
Im running the latest nvidia drivers. Any ideas?

Actually this is how hardware mode works. I know it's wierd but its due to what is called "Linear color/ light processing" Basically it will cause the issue your seeing. Hardware mode handles video this way. Currently you can't do anything about it, sadly. I always just have to make things darker to compensate. The reason it looks correct in titler is because the titler displays the still in software mode, or at least this is what I have noticed so I assumed this a long time ago.
Basically though if you export your video in software mode then check max render quality when you export it cause the same issue that having MPE+GPU enabled does. That's because enabling max render quality causes even software mode to use 32-bit linear color processing. So most likely I think this is what is causing the issue you're seeing. You can verify it, by setting your sequence to software mode. Then exporting and checking max render quality when you export, then looking at the end result and you'll see the opacity differences.
You can check out this thread for more in depth info.
http://forums.adobe.com/thread/773441

[Premiere Pro CS6] Bug, vidéo coupée en deux

Bonjour, j'ai un problème très embêtant sur première pro : mes vidéos importées (chutier, moniteur source) et celles dans la table de montage sont coupées en deux ! Je ne sais pas du tout à quoi cela est dû, d'autant plus que j'ai commencé mon projet sans aucun souci.
J'ai fait une capture d'écran : http://img819.imageshack.us/img819/269/zuil.png
Le plus bizarre, c'est que les vidéos ne sont pas toutes touchées (le bug s'arrête à la vidéo "SDV_936"). Je viens de remarquer que les vidéos de format mp4 ne sont pas atteintes mais les vidéos wmv oui. Comme vous pouvez le constater, cela est très ennuyant. Et cela me serait long de tout reconvertir en mp4. Le son en revanche marche nickel.
Quelqu'un sait comment réparer ce problème ? Merci d'avance.
Références :
Windows 7 64 bits
Adobe Premiere Pro CS6
Formats vidéo utilisés : .wmv (=format présentant le bug) ; .mp4
Note : j'ai effectué un premier rendu de mon projet juste avant le bug après réutilisation du logiciel. J'ai ensuite supprimé les fichiers de rendu et le bug s'est propagé sur ma table de montage.

Je n'ai pas Photoshop.
PP est dans sa version 6.0.0 , je devrais donc installer la maj 6.0.3 alors.
Ma configuration du projet est bonne. Ce qui est bizarre, c'est que ce problème est intervenu seulement il y a quelques jours alors que je procède de la même façon depuis des mois.
D'ici là, je fais la maj et je dis si ça règle les choses.

Premiere Pro CS5 bug editing clip name: 1 second edit time

When editing the name of a clip in the project window, Premiere forces completion an instant after entering edit mode. This doesn't happen all of the time, but after using the program for a while it starts happening. Restarting the app quites the issue for some time. Has anyone else experienced this?

Just an example that may help: I have a Wacom tablet, and it started behaving badly in Cinema 4D despite the fact that it had worked perfectly just hours before. The only thing I had done in between was rip some of my CD collection to FLAC using Exact Audio Copy. EAC was not open when the C4D pen issue appeared. I rebooted, and pen operation in C4D returned to normal. I ripped a CD or two with EAC, and the bad pen behavior in C4D returned.
I have no idea why EAC should affect pen/tablet behavior in C4D, but it does. So the issue you see in Pr may well be from unexpected and illogical sources. Regardless, I hope you get it sorted quickly.
Jeff

Premiere pro update bugs

I updated yesterday (Dec 9, 2014) to the latest Premiere Pro and there are all kinds of problems.
1. It freezes up and/or crashes multiple times within an hour.
2. Anytime I nest a clip and do warp stabilizer it appears to delete frames giving a ridiculous flicker effect.
I need help ASAP. Need to finish projects.

Hi Jorge,
Jorge Jaramillo Hdz wrote:
I don't know that to do about it.
Can you try contacting support? If they help you with the issue, please report back. Here's the link: Contact Customer Care
Just click the blue button to get a chat or phone call started.
Thanks,
Kevin

Premiere pro cc bug??? - timeline indicator goes beyond end of sequence...

Not sure if anyone else has come across this. But for some reason, in my premiere pro cc (2014.2) verison, my timeline indicator doesn't stop at the end of my sequence but goes a good distance beyond that. I zoomed in all the way and already verified that there are no video or audio clips where it stops.
The timeline needle should stop at 00;08;09;20 which is the end of my sequence.
But instead it stops at 00;08;14;51. No idea why:

Not sure if anyone else has come across this. But for some reason, in my premiere pro cc (2014.2) verison, my timeline indicator doesn't stop at the end of my sequence but goes a good distance beyond that. I zoomed in all the way and already verified that there are no video or audio clips where it stops.
The timeline needle should stop at 00;08;09;20 which is the end of my sequence.
But instead it stops at 00;08;14;51. No idea why:

Premiere 7 XML Bug?

Hello There,
I've been testing the waters considering my first Premiere CC project. I've been using Premiere almost exclusively for a year and a half.
I've read here that opening projects created in CS6 in CS7 results in performance issues for some so I exported an XML of some footage from a CS6 project, and imported to CS7. All the color corrections came in wrong, looking like a bleach bypass:
When I import the sequence from CS7 it looks fine:
Thanks!
Gerry

Hi Gerry.
When we updated from CS6 to CC, we found that the projects opened without a hitch. It asked us to save off a new project but aprt from that, it was like using the original project file. We've done this nearly 30 times now, each with CS6 project files opening up in CC and now issues.
Have you actually had permormance issues with this?
Paul

Premiere pro/audition bug? Mixdown file won't play in sequence

Howdy.
Never had this happen before, so I thought I'd ask you academic types what's going on.
I created a sequence in PP that contained multiple audio (wav)/video files. I exported the audio to Audition, balanced the amplification, declicked, popped, etc. Created a mixdown of the files and exported (wav). I imported the mixdown to PP and placed it into the sequence (I've done this thousands of times before). Unfortunately, there were no waveforms on the file and no audio can be heard.
However, if I open the same file in the source monitor the waveforms are there and the file plays as it should. I can also open and play the wav file in media play, for example, and everything appears to be fine.
Any ideas on why it won't play in the program monitor/timeline/sequence?
Thanks

Oh well, not a big deal. I was able to use the clip by creating a new sequence, dragging from source monitor to new sequence, then copy/paste from the new sequence to the sequence I needed.

Bug list and wish list premiere pro cs4

Iam realy interesting someone, sometime work with Premiere pro cs4 from Adobe team ? I gues not!! Some bug might not seen only people who not work on premiere !!! 2 russian video editing forum named premiere cs4 most worst of version premiere. Old bugs not fixed on premiere cs3 adobe make premiere cs4 with new most worst bugs and some options was remove(Fast export to frame\movie) What for ????!!!!! Cuting the clip i must press 2 button - what for ? Cut it most usful operation and adobe make 2 button press to cut. And domenation effects then adding to clip, please try add some effect to clip then add someone again. Why new effects adds not to last posotion ?
And time warp, posterize time work only with neast sequence!!! What for !!!Its make work with premiere faster ????
ADOBE PLEASE WORK YOUR SELF ON PREMIERE PRO CS4 SOMETIME !!!

FAQ:How/Where do I report a bug?
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Trouble with GPU Acceleration in Premiere Pro CS6 (GTX 670)

I recently bought a new GTX 670 with the hopes that it would accelerate my video editing in Premiere. After using the "nVidia hack" to add it to the list of CUDA supported cards, I started up Premiere, enabled GPU acceleration in the general project preferences window, and was disappointed to find that my performance appeared to be identical to what I had experienced with my non compatible HD 6870s.
When I checked with MSI Afterburner, my GPU usage remained around 0%, even when playing through videos. I'm quite certain that my card was successfully added to the list, so I have no idea what's going on.
Is there any chance that I am misunderstanding what GPU acceleration is supposed to do? I'm very new to Premiere, so I don't know too much about it yet. The reason I bought my new card, aside from improved performance in 3D games, was to allow me to scrub through my project (comprised of 1080p AVI videos captured with FRAPS) without hiccups and poor FPS. Was this not a reasonable expectation for GPU rendering?
Here's a short list of my PC's specs if it's any help:
-Intel i5 2500k (currently not overclocked)
-8GB DDR3 Dual Channel RAM (at 1600MHz)
-1TB 7200RPM HDD
-nVidia GTX 670 OC 2GB VRAM
-Gigabyte Z68XP-UD3 Motherboard
Thanks in advance for any advice!

Did you go to project>project settings>general and verify that GPU (cuda) accleration is enabled? If it's set to software only then change it and see if that helps. If it's enabled my next question is what is the bitrate of your FRAPS videos? Because I have seen some fraps video's with bit-rates that are really high which would require a RAID array that is only holding video clips to playback smoothly. In your case it appears you have your OS and your apps and your footage all playing from the same 7200rpm drive. Which isn't really sufficent for 1080p editing. However it might be as simple as enabling it from within premiere pro like I mention earlier. If it's enabled though please check the bit-rate of your video you're attempting to edit with because I'm assuming that might be the issue.

Crashes in Premiere Elements 9

Why am I getting the error message (Premiere Elements De bug event) and shutdown in remiere Elements 9. It appears to happen when I try to add Still Photos to the Timeline at the end of video footage! Appears to work without crashing when video only is on the timeline!
Dave

Many thanks John,
I think you have pointed me in the right direction. At least I am getting something out of the product.
Dave R.

Premiere Pro CS5.5 encoding speed

Hi,
I noticed that the time for encoding a video in Premiere with GPU acceleration enabled doesn't change according to the shaders clock speed. The time is exactly the same with or without GPU overclocking, is this normal?
Another question: the encoding speed is faster during the first 50% of the process, then decreases a bit. Is this related to some option in the program or it's normal?
Thanks in advance.
Luis

I've made an encoding test where we can see that GPU participates more actively in the first half of the encoding process and therefore I don't understand why you said "The GPU is not involved in encoding, that is a purely CPU matter". From 50% until the end of the process CPU takes the lead.
Luis

Premiere CC GPU Bug

Similar Messages

Maybe you are looking for