After having noticed for some time that neroAacEnc.exe inserts a slight - non-modifiable - audio-delay (appr. 40 ms) at the start of the audio; see also:   https://hydrogenaud.io/index.php/topic,69803.0.html I have been looking for a replacement of this audio encoder. Not so many otions out there but qaac   https://sites.google.com/site/qaacpage/cabinet/qaac_2.58.zip?attredirects=0&d=1 is a command line AAC/ALAC encoder frontend based on the very good Apple encoder - and in contrast to the Nero encoder it is still actively developed and offers a lot of options. I have changed the NVEnc_export code to work with this encoder and expanded Premiere's audio settings by a new field "Audio Start" with a default setting of 22 ms. This value gives me congruence with the ADOBE PCM audio for my settings. If you set it to 0 you will get the original delay introduced by the qaac encoder. The Nero encoder will *not* work with this version of the Plug-in. This Plug-in can be downloaded from Google Drive (nvenc_export.prm.qaac - Premiere will show it as NVENC_export 1.12Wc_W7; rename it after download as usual to nvenc_export.prm):   https://drive.google.com/file/d/0BwViiZKy_eFpMjhVQ3hCejdnY0E/view?usp=sharing It has been compiled with NVIDIAs Windows 7 library; and I have not yet found any problems using it with Windows 10 with NVIDIA's latest driver. But in order to use this Plug-in you have to install all necessary qaac- and Apple-components as explained on the qaac-pages. As always when installing a changed Plug-in, delete all your current NVENC_export settings and reset the Plug-in cache as described in this document   https://helpx.adobe.com/premiere-pro/kb/features-presets-missing-premiere-pro.html as well as in nvenc4everyone's documentation and in my previous posts. Omitting this step will garble your Premiere Export settings window. Perhaps nvenc4everyone could consider to officially include this audio encoder in a future version of NVENC_export instead or as an alternative to the Nero encoder. ... View more

The Plug-in definitely works on Premiere CC. The problems seen with the settings interface (missing content of the dialog-boxes) may be caused by not having deleted  ALL NVENC_export user settings after the upgrade to version 1.11. To do that, you have to navigate to:                   C:\Users\nn\AppData\Roaming\Adobe\Common\AME\xx\Presets nd there delete ALL NVENC_export presets. Alternatively, you can run Adobe Media Encoder, and from there, delete ALL NVENC_export presets. The next time you open the NVENC_export plugin, Adobe will rebuild a default-preset from scratch.  And hopefully, all of the missing dialog-boxes/options should there. After that the settings can be customized to your need. ... View more

Well, I have to investigate this problem. The Plug-in has been build with newest libraries for Windows 10 - maybe some libraries are not backwards compatible with Windows 7? Is anybody also having problems with Premiere CC on Windows 10? Is the previous Plug-in "1.11Wa" from entry 246 working with Premiere CC on Windows 7? ... View more

The Plug-in has been rebuild with NVIDIA's and ADOBE's latest libraries - the Adobe namestring of the Plug-in is "NVENC_export 1.11Wb" - no other changes compared to 1.11Wa. The Plug-in has been tested with H.264- (with GTX 670 and GTX 960) and HEVC/H.265- (with GTX 960) footage under Windows 10 with ADOBE CS6 (Premiere and Media Encoder) and there it works flawlessly. This Plug-in can be downloaded from Google Drive:                              https://drive.google.com/file/d/0BwViiZKy_eFpeEE4dl9PZGRYVFk/view?usp=sharing If your system refuses the download because of a virus warning, you have to temporarily disable your scanner for the time of the download. Its a fake warning and I also get it on some systems. Do then a virus scan of the downloaded item. All the previous outdated versions of my compilations of the Plug-in will eventually be removed from Google Drive; those references will no longer be accessible - please use always the newest one. ... View more

Same problems here with latest version (v1.11) of the Plug-in. After disabling output of the the MediaInfo string at all places in the code - nothing else has been changed - the Plug-in works as before. You can download the revised plugin - the Adobe namestring is "NVENC-export 1.11Wa" - here; and please give some feedback: https://drive.google.com/open?id=0BwViiZKy_eFpLU5xUjdVbG4weWM If your system refuses the download because of a virus warning, you have to temporarily disable your scanner for the time of the download. Its a fake warning and I also get it on some systems. Do then a virus scan of the downloaded item - i do this with the tool "virustotal". ... View more

I have extended the plugin with the possibility to set the final output path differently from the export path set in Premiere Pro. The procedure: (a)   define the user variable ADOBEOUT in Properties->Advanced->Environmental Variables (b)   set its value as the path where you want to output your rendered final output file e. g. S:\MyOutputDir or S:\MyOutputDir\ (c)   in the Export settings in Premiere Pro set the Export filename to e. g. E:\MyScratchDirectory\MyOutputfileName.mp4 The result: (a)   the pre-muxed streams will be put on E:\MyScratchDirectory and will be deleted after successfull muxing (b)   the final output will be S:\MyOutputDir\MyOutputfileName.mp4 If the user variable ADOBEOUT is not set in the Environmental Variables, the plugin works as before. This version of the plugin can be downloaded at: nvenc_export.prm - Google Drive ... View more

Is anybody else having new problems with this latest iteration of the plugin? I am only able to test some H.264 (with GTX 670 and GTX 960) and HEVC/H.265 (with GTX 960) footage under CS6 and that works flawlessly. If you do experiencing problems, you should try to reproduce them with my settings you find above and report your specific HW and SW environment. ... View more

Short update of my last post: the problem with the wrong image-height in the header files of HEVC output seems to be a problem with the muxers. Using the latest versions of mp4box and mkvmerge is correcting that - in my test footage the correct size is now written into the header and MediaInfo is displaying it properly. ... View more

Here is another slightly improved version of the plugin: https://drive.google.com/file/d/0BwViiZKy_eFpWHhHY0dIak1oNkk/view?usp=sharing There are still some problems with the plugin - e.g. outputting with the HEVC codec is writing the wrong image-height into the header of the file (1088 instead of 1080 and 2176 instead of 2160). I have not yet found the position in the source code in order to correct that. But for example MPC-HC seems to play the file correctly by not using the wrong image dimensions from the header. Be aware that this is still a "proof-of-concept" plugin as nvenc4everyone stated it - and it might be rough at some edges. I am mostly using the following H.264-settings and outputting aac/mp4 audio and only change the vido-settings under NV_ENC_PRESET, NV_ENC_LEVEL_H264 and under the  "Sample basic video param group": With these settings I do get file sizes comparable to what the original Adobe-Encoder (Mainconcept) delivers.  ... View more

Same problems here with NVIDIAs latest drivers. I have expanded the code in CNVEncoder - where the error occurs - with all missing input formats and thus removed the error message. Another problem named in this thread is the missing possibility to use the HQ preset and output an MP4 file with AAC audio. This was probably  caused by the fact that the original plugin did produce garbage from the settings of the embedded MediaInfo string at the beginning of the output file. After completely removing this MediaInfo string, now the output with the HQ preset to an MP4 file with AAC audio is working. You can download the revised plugin here:                 https://drive.google.com/open?id=0BwViiZKy_eFpfkxHeVI0Y0RHU0Yycm9NQ3pLMldsOFA0RU9ZclZBdHhkblJ3dzFJeEZIY0E&authuser=0 ... View more