Sure, here's 1.09 recompiled against the latest NVENC libraries: nvenc_export 1.09 - j1.zip If someone who can't load 1.11 wants to try this, it should give a good indication if the problem originates from a code change in 1.11, or just the use of the newer NVENC libraries. ... View more

Sorry, I don't know how else to help you. I'm running 361.43 drivers on Win10 and everything works fine. Unfortunately I don't have access to a Win7 machine with an NVidia video card, so I can't try it out under a debugger. Maybe nvenc4everyone or irisb50359875 could. Best of luck. ... View more

Other than the MSVC runtime the only other dependencies are the NVIDIA driver and D3D9. Since 1.09 works for you, you obviously have d3d9, but make sure you have at least version 359.0 of the NVIDIA driver (according to nvenc4everyone's release notes for 1.11). If that doesn't work I don't know what else you could try. ... View more

I don't think the registry issue is the culprit, either way it tries to load the plugin from disk. But, you can try deleting the plugin's regkey and restarting the app. The regkey is at: "HKEY_CURRENT_USER\SOFTWARE\Adobe\<product>\<version>\PluginCache.64\<locale>\<plugin file name>" where <product> is "Premiere Pro", "Premiere Elements", or "Adobe Media Encoder". Based on your log, and if your locale is en_us, it would be: "HKEY_CURRENT_USER\SOFTWARE\Adobe\Premiere Pro\9.0\PluginCache.64\en_US\nvenc_export111j3_64.prm" ... View more

Try the j3 version, it's built against the VC2013 runtime (to be consistent with nvenc4everyone's builds). The j2 build requires the VC2015 runtime to be installed. There are links to both in my previous post. ... View more

Ah... I think I know what happened. I didn't notice that Visual Studio 2015 automatically updated the project to use the 2015 toolset. So those binaries would need the Visual C++ 2015 redist. You can either grab that, or you can grab an updated build that uses the 2013 toolset: nvenc_export 1.11 - j3.zip ... View more

Oops, it looks like I included debug binaries by mistake. Here's a new link with release binaries: nvenc_export 1.11 - j2.zip Sorry about that. ... View more

I just tested, and a non-animated text with no video background causes the same issue as a still image. A blank screen does as well. Basically, anywhere that Premiere can tell that the image doesn't change for some number of frames, it will send a single frame to the exporter with instructions to repeat it X times. Before my fix, the exporter was ignoring the repeat count and only encoding the frame once. This then messed up audio sync because the resultant video stream was missing frames. Try my fixed prm file, or try a simplified sequence with no text/blanks/images in it to verify if it's something specific to your project or if everything exports with sync issues. ... View more

Hopefully nvenc4everyone sets up a code repository (GitHub or otherwise) so that people can contribute fixes to a central location. But in the meantime, here's a version that is based on 1.11 and includes the following changes: - Fixes mp4box.exe crash from MediaInfo text being encoded in the file (Thanks to irisb50359875 for describing their fix) - Fixes still images having only one frame rendered (which also caused audio/video to fall out of sync) Zip file contains x86 and x64 binaries, but only the x64 binary has been tested. You can download it here (nvenc_export 1.11 - j1.zip). ... View more

Do you have a still image in your timeline? The plug-in has a bug where it only encodes one frame of a still image rather than the whole duration it's supposed to be shown, which causes a/v to fall out of sync. A workaround is to set an effect keyframe (on say, opacity) on the first frame of the still image. ... View more