Quantcast
Channel: Adobe Community : Popular Discussions - Adobe Media Encoder (AME)
Viewing all 7030 articles
Browse latest View live

How to convert MOV file to WMV in Adobe Media Encoder CC 2019?

$
0
0

Hi,

I can't find any presets for convert from MOV or any files to WMW in Adobe Media Encoder CC 2019?

Is this function still existing?

Could you help me for the way to do?

 

Thank You


Export Error. Error compiling movie. Disk Full.

$
0
0

I have the following error since CS6 when exporting some videos: Export Error. Error compiling movie. Disk Full.

 

All my drives have plenty of space, NTFS 7200rpm, everything was fine with CS5.5. Same problem with Encoder or Premiere Pro.

 

Much of the stuff I export is going fine but I have this error with some sequences and formats.

 

It always crash to this error when exporting sequences with "Match Sequence Settings".

 

For one of my projects, when exporting to wmv, out of 6 sequences one always crash to Export Error. Error compiling movie. Disk Full.

 

If I encode those sequences to mpeg2, everything is fine.

 

I installed the new update this morning but it doesn't help.

No audio when using 2017 Media Encoder

$
0
0

Hi,

I'm having issues with the 2017 version of Media Encoder.

 

To start, I exported my files from Adobe Premiere CC 2017 version. I have no problems with audio. Sound is there with the file(s). Everything looks good.

 

Then, when I use the media encoder to change to another format, I get no audio at all. All of my clips from the new ME has no audio.

 

I have cleaned the media cache from both Premiere and ME. I also re-installed Media Encoder 2017. So far, nothing has worked. Still no audio on files.

 

Everything was fine with previous version. Any suggestions?

Media Encoder render extremely slow

$
0
0

Render speed of Media Encoder (2018) is x4 slower than premiere pro cc 2018 in same File export with same rendering settings.

Rendering time of the file (4K video. H.264 Mp4.  2 min. length) :  Premiere Pro - 9 min, 

                                                                                                          Media encoder - 41 min

My System:  AMD Ryzen Threadripper x1950 (16-core)

                     GeForce GTX 1070

                     64G RAM of DDR4

                     2 x 256G SSD

720p MP4 Export settings

$
0
0

Hello Forum,

 

Can anyone recommend decent quality 720p MP4 settings with an MPEG4 container? 

 

I can only do 720p versions in a quicktime or h264 container which will not play in windows. 

 

Source is ProRes 422 1080p.  Client requests MP4.  However, the settings for MP4 under the MPEG4 container does not allow for a high enough data rate for 720p.

 

Thanks!

- Ryan

How to convert MOV file to WMV in Adobe Media Encoder CC 2019?

$
0
0

Hi,

I can't find any presets for convert from MOV or any files to WMW in Adobe Media Encoder CC 2019?

Is this function still existing?

Could you help me for the way to do?

 

Thank You

Black Screen from AE export to AME

$
0
0

Hi,

 

I have just started using AE CC and I was trying to output some videos but there was some bugs with the time using render queue but I had found the problem and fix it. But while solving this issue I found an odd problem with the Adobe Media Encoder CC. Everytime I click on export to Media Encoder it renders the video with no content just a black blank screen. The temp AE files it generates is fine no issues just the video file is blank. I tried a different animation that I had also created same problem. I got someone who knows AE and he tried using different codecs but its blank too. There is no problems with AE or the working file because I can render videos with no problems using the internal render queue, Its only media encoder having this odd issue.

 

I had tried updating Media Encoder to 7.01 even though its already 7.01 but still the same problem. How do I uninstall and reinstall? I have media encoder cs6 installed on my mac too. Will that cause any conflicts?

 

Currently I have these Adobe software installed - Adobe CS6 Design Premium (Illustrator, Photoshop, Acrobat Pro, Fireworks, Flash, Indesign, Dreamweaver - Full Liscene Version) and (Audition CS6, Edge Animate, Encore CS6, Premiere Pro CS6, Photoshop Light Room 5, After Effects CC - All Trial Versions).

 

I am using a Macbook Pro with Mountain Lion 10.8.5. All software up to date.

EError: “AEGP Plugin AEDynamicLinkServer: Adobe Media Encoder is not installed

$
0
0

I have a corporate license to Adobe software. I am using Premiere Pro CC 2015 and After Effects CC 2015.  Today, I was having an issue using an MP2 file with Premiere Pro.  So I saw something and ran "Updates" hoping it would solve the issue.  I don't know what it did but it broke After Effects.  When trying to export a lower thirds project, I got the following error: “AEGP Plugin AEDynamicLinkServer: Adobe Media Encoder is not installed. Please download and install it to use this feature. Go to https://creative.adobe.com/apps."   which is then followed by AEGP Plugin AEDynamicLinkServer: Failed to connect to Adobe Media Encoder.”  I uninstalled After Effects and Premiere Pro and re-installed them both.  I still get the same error.  I assumed Adobe Media Encoder was installed but when I go look in the same folder where the other Adobe software is (Programs), it's not there. 


How does Adobe Media Encoder get installed (part of PP or AE)? I also found a URL where I could download an AE "update" - ran that and I get an error saying the "patch is not applicable to you".  I think somehow through this process Adobe Media Encoder was uninstalled and not re-installed with either PP or AE.


ProRes presets for Media Encoder CC now available for download

$
0
0

Hi everyone,

 

We have new ProRes output presets available for Media Encoder CC. You can download the presets here

 

While the new presets do not add new functionality to Media Encoder, they do provide added convenience. By definition, these presets are for use on Mac OS. If you are on Mac OS X 10.8, or 10.9, the ProRes codecs come installed with your operating system. If you are using Mac OS X 10.7, you will need to install one of the Apple Pro apps (Final Cut Pro, Motion, Compressor, etc.) for the presets to function correctly.

 

Here’s what’s new with the Media Encoder CC ProRes presets:

 

  • Preset names have been updated to say "SD" (instead of “DV")
  • The Field Order of PAL SD presets changed from "Lower" to "Upper"
  • Frame Size of NTSC SD presets changed from 720x480 to 720x486. This is based on Apple's ProRes specifications. If 720x480 versions are needed you can create your own User presets with these settings.
  • Enhanced support for multi-track audio sources. New "Audio Track Layout" and "Channel Layout" sections let you specify the number of exported tracks, track types (single track, dual mono, or stereo pairs), and channel mapping for 5.1 audio

 

Please note: the ProRes presets should only be installed on AME CC (7.x). They may not work correctly in AME CS6 or earlier versions.

 

If you have any questions, please let us know.

 

Eric

No audio when using 2017 Media Encoder

$
0
0

Hi,

I'm having issues with the 2017 version of Media Encoder.

 

To start, I exported my files from Adobe Premiere CC 2017 version. I have no problems with audio. Sound is there with the file(s). Everything looks good.

 

Then, when I use the media encoder to change to another format, I get no audio at all. All of my clips from the new ME has no audio.

 

I have cleaned the media cache from both Premiere and ME. I also re-installed Media Encoder 2017. So far, nothing has worked. Still no audio on files.

 

Everything was fine with previous version. Any suggestions?

HOW TO CREATE VIDEO DVD WITH ADOBE MEDIA ENCODER

$
0
0

I AM NEW TO ADOBE PREMIERE. AFTER SOME HOURS OF LEARNING FINALLY I FINISHED EDITING 30 MIN OF VIDEO. NOW I DONT KNOW HOW TO OUTPUT TO DVD ( VIDEO DVD ) TO PLAY IN DVD PLAYERS. PLS HELP.

Media Encoder CC 2019 keeps crashing when I try to add source

$
0
0

Like the headline says, as of this morning (Tuesday April 16 2019) Adobe Media Encoder CC 2+10 keeps crashing whenever I try to add a source file to render. This is happening whether I try to add source directly, or whether I have After Effects add to render queue. It isn't creating a log or error report when it does this. It is happening when I try to add files that I had previously rendered successfully so I know it's not the source files that are the issue. The last time I used it to render a file was Saturday, April 13, 2019 and everything worked flawlessly. I'm including a screenshot of my about screen since that's all I've got to share. I just uninstalled Adobe ME and reinstalled it and the same thing is still happening.

 

I'm using the new NVidia creators optimized drivers for my GPU, but that was also true on Saturday when everything worked correctly. I've tried turning GPU acceleration off, and on, same thing happens.

 

FWIW Here is my system specs:

Windows 10 Professional 64
Adobe CC 2019

Asrock extreme 4 Z77 motherboard

Intel i7-3770k

Crucial MX500ssd 500GB (Programs, Apps, Project Files)

Samsung 850EVO SSD 500GB (Render Output Folders)

Kingston UV400 SSD 480GB (Current Project Assets)

Samsung 860EVO SSD 250GB (Adobe Cache)

Seagate Barracuda 1TB HDD (Slow Bulk Storage)

32GB G.Skill Ripjaws-Z 1600mhz

MSI GTX 1060 Gaming-X

EV3A G3 750 Supernova

Thermalright Macho Cooler

 

MEBuild.png

Exporter returned bad result

$
0
0

I just updated both Premiere and Encoder to the latest versions and opened an older Premiere project (from CC 9.1) to export them through Encoder as 422HQ Quicktime file. Both open fine and seem to export fine directly through Premiere, and Queue up fine in Encoder...however, the encoding fails instantly (before any progress bar can even appear).

 

Consistently getting the following error on any Quicktime export (422, 422HQ, Animation, etc.) although H264 renders work fine. Any ideas? I've never seen such a long error code, nor had renders fail so quickly.

 

Running CC on a 2012 iMac, 3.2Ghz Intel Core i5 running OS 10.11.6.

 

Thanks for any insight!

 

 

 

- Encoding Time: 00:00:01

08/09/2016 04:57:15 PM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

 

Export Error

 

Exporter returned bad result.

 

Writing with exporter: QuickTime

Writing to file: /Volumes/RHP_10_2016_Delivery/EvilExhumed_DELIVERY/EVILEXHUMED_MASTER/EvilExhumed_Master_ 422HQ.mov

Around timecode: 00:00:00:00

Component: QuickTime of type Exporter

Selector: 9

Error code: 1667785070

720p MP4 Export settings

$
0
0

Hello Forum,

 

Can anyone recommend decent quality 720p MP4 settings with an MPEG4 container? 

 

I can only do 720p versions in a quicktime or h264 container which will not play in windows. 

 

Source is ProRes 422 1080p.  Client requests MP4.  However, the settings for MP4 under the MPEG4 container does not allow for a high enough data rate for 720p.

 

Thanks!

- Ryan

Export Error. Error compiling movie. Disk Full.

$
0
0

I have the following error since CS6 when exporting some videos: Export Error. Error compiling movie. Disk Full.

 

All my drives have plenty of space, NTFS 7200rpm, everything was fine with CS5.5. Same problem with Encoder or Premiere Pro.

 

Much of the stuff I export is going fine but I have this error with some sequences and formats.

 

It always crash to this error when exporting sequences with "Match Sequence Settings".

 

For one of my projects, when exporting to wmv, out of 6 sequences one always crash to Export Error. Error compiling movie. Disk Full.

 

If I encode those sequences to mpeg2, everything is fine.

 

I installed the new update this morning but it doesn't help.


Adobe Media encoder plugin is missing in After Effects. How do you install the plugin?

$
0
0

Adobe Media encoder plugin is missing in After Effects. How do you install the plugin?

NVidia GPU-accelerated H264-encoder plugin, ready for public testing

$
0
0

Hi all,

 

I have written a 'proof-of-concept' GPU-accelerated H264-encoder for Adobe Media Encoder (CS6).  It requires an NVidia 6xx/7xx series "Kepler" GPU (CUDA capability 3.0), and uses the dedicated GPU's builtin hardware-encoder (NVENC) to offload the H264-encoding process from the host-CPU.  This software is "proof-of-concept", so it's missing some critical features (no interlaced-video support, no AAC-audio or Dolby AC-3 audio), and of course, it could be buggy!  But it's free.

 

!!!! Disclaimer: NVENC-export is third-party software that is not supported by either Adobe or NVidia.  It comes with no warranty -- use at your own risk.

 

Software/hardware Requirements:

 

(1)Adobe Premiere Pro CS6 or Media Encoder CS6 (Windows version)

Sorry, MacOSX is not supported. (NVidia NVENC SDK doesn't support MacOSX.)

 

(1)NVidia KeplerGPU <GKxxx> with 1GB VRAM or more  (GTX650 or above, GT650M or above)

(Sorry, NVidia Fermi <GFxxx> is NOT supported, it doesn't have the NVENC hardware feature)

Note,if you have MPE-acceleration enabled, keep in mind the NVENC-plugin consumes some additional VRAM because it uses your GPU to perform H264-encoding.

Strongly recommend a 2GB card

 

(2) Microsoft Visual C++ 2010 SP1 x64 redistributables

          (download this from Microsoft's website)

 

Installation instructions:

 

     In Adobe Premiere Pro CS6:

     (1)      On your system, locate the installation-directory for Premiere Pro CS6.

               Usually, this is C:/Program Files/Adobe/Adobe Premiere Pro CS6

    (2)     Copy the included file Plug-ins/Common/nvenc_export.prm

               to <installation dir>/Plug-ins/Common/

 

     -> To choose the NVENC-plugin in Premiere Pro,

          In the format-menu, select <NVENC_export>

 

     In Adobe Media Encoder CS6:

     (1)    On your system, locate the installation-directory for Media Encoder CS6.

          Usually, this is C:/Program Files/Adobe/Adobe Media Encoder CS6

     (2)     Copy the included file Plug-ins/Common/nvenc_export.prm

          to <installation dir>/Plug-ins/Common/

 

     -> To choose the NVENC-plugin in Media Encoder,

          in the format-menu, select <NVENC_export>

 

Performance & quality notes:

 

(1) How much faster is NVENC-export than Adobe's built-in Mainconcept H264 encoder?

 

Depends on your PC system.  On my test-system, which is ordinary desktop PC with Intel i5-3570K (4-core 3.4GHz), NVENC-plugin is roughly 4x faster than Mainconcept. On a dual-socket Xeon Ivy Bridge-E system, NVENC would probably only be 2x faster (in Media Encoder.)

 

(2)How does the video-quality compare?

 

Comparing similar settings/video-bitrate, Mainconcept performs better at lower-bitrates(less artifacts).  At medium-high bitrates, NVENC is comparable to Mainconcept.

 

(3) How does NVENC-export encode the video?

The plugin fetches videoFrames from the Adobe application, then converts the frames from YUV420 to NV12 surface-format (using host-CPU.)  Then it passes the converted frames to the NVENC front-end.  From here, NVENC hardware takes over, and handles all aspects of the video compression. When NVENC hardware is done, it calls the plugin to output write the elementary bitstream (to the selected filepath.) NVENC-hardware does NOT encode audio, nor does not multiplex the A/Vbitstreams -- this is still done in software (on the host-CPU)

 

The NVENC hardware block has very little CPU-overhead.  But since video-encoding is just 1 step in the entire Adobe rendering path, CPU-usage will likely still be quite high when using NVENC-plugin.

 

(4) What's the maximum-size video NVENC-export can handle?

H264 High-profile @ Level 5.1, which works out to roughly 3840x2160 @ 30fps. (Note the actual encoding-speed will probably be less than 30fps.)

 

(5) How fast is the NVENC-export hardware in Kepler GPU?

Assuming the Adobe application host is infinitely fast (i.e. can send video to plugin in zero-time), NVENC-hardware will encode High-profile (CABAC, 2 refframes, 1-bframe) 1920x1080p video @ ~100fps. At 3840x2160p (4k video), the hardware encode-speed drops to roughly 20-25fps.  That is still faster than a desktop PC.

 

NVENC-speed is generally same across the Kepler family - the high-end Geforce GTX Titan (or GTX780) is no faster than the entry-level Geforce GTX650, because all Kepler models share the same NVENC hardware-block, which is totally separate and independent of the GPU's 3D-graphics engine.

 

In premiere Pro 6, MPE acceleration will greatly affect how quickly Adobe can render video to the exporter.  So a more powerful Kepler GPU will probalby complete projects faster than a less powerful one (up to NVENC's performance ceiling.)  For more info, please refer to NVidia's NVENC whitepaper at their developer website (public)

 

(6) I have a multi-GPU setup, can I encode with multiple GPUs?

No, NVENC targets and uses only a single physical GPU.  (You can choose which one.)

 

Known limitations and problems:

 

NVENC-plugin is a 'proof-of-concept' program -- it is not a finished product.  So it's missing some features, and other things are known to be broken:

 

    • Interlaced video encdoing does not work at all (not supported in current consumer Geforce drivers)

 

    • Audio support is very limited: uncompressed PCM)

no AAC or Dolby-Digital

 

    • Multiplexer support is very limited: MPEG-2 TS only, using an included third-party tool TSMuxer.EXE

no MPEG-4 muxing (*.MP4)

 

    • When the muxed MPEG-2 TS file in Windows Media Player (WMP), there is no sound.  This is because WMP doesn't recognize PCM-audio in mpeg-2 ts files.  You have 2 choices; you can use a third-party media-player such as MPC-HC or VLC.  Or you can postprocess the audio-WAV file into a compatible format (Dolby Digital/AC-3)

 

    • in the pop-up plugin User-interface, the <multiplexer> tab is missing or not shown properly.

(To fix: Select a different codec, then re-select NVENC_export.)

 

    • Doesn't support older NVidia GPUs (GTX5xx and older, GT630 and lower)

Sorry, NVENC hardware was introduced with NVidia's Kepler family (2012)  Anything older than that will NOT work with the plugin.

Adobe Media encoder plugin is missing in After Effects. How do you install the plugin?

$
0
0

Adobe Media encoder plugin is missing in After Effects. How do you install the plugin?

AME error code -1609629695

$
0
0

Hi, I'm using AME to render my video from After Effects.

 

I used to get the same error code for the renders (-1609629695) all the time, but all of sudden it was working fine for a few renders.

 

And now I'm getting the error again.

 

For different compositions, this has been occuring often, and I couldn't figure out what is causing this error or find any information about this online.

 

I'm using AME CC 2018 version 12.1 / After Effects CC 2018 version 15.1.0

Processor Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)

Windows Version 10.0.15063 Build 15063

Intel HD graphics P530

NVIDIA Quadro M1000M

 

 

 

 

and here's what I get about why my rendering is failing

 

------------------------------------------------------------

- Encoding Time: 00:00:41

11/28/2018 04:00:20 PM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

 

 

Render Error

 

 

Render returned error.

 

 

Writing with exporter: H.264

Writing to file: \\?\C:\Users\seungmi_lee\Documents\Personal Project\deliverable-test\asset\WIP\wip_AME\scene-07_1.mp4

Writing file type: H264

Around timecode: 00;00;08;18

Rendering at offset: 4.037 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629695

 

 

------------------------------------------------------------

NVidia GPU-accelerated H264-encoder plugin, ready for public testing

$
0
0

Hi all,

 

I have written a 'proof-of-concept' GPU-accelerated H264-encoder for Adobe Media Encoder (CS6).  It requires an NVidia 6xx/7xx series "Kepler" GPU (CUDA capability 3.0), and uses the dedicated GPU's builtin hardware-encoder (NVENC) to offload the H264-encoding process from the host-CPU.  This software is "proof-of-concept", so it's missing some critical features (no interlaced-video support, no AAC-audio or Dolby AC-3 audio), and of course, it could be buggy!  But it's free.

 

!!!! Disclaimer: NVENC-export is third-party software that is not supported by either Adobe or NVidia.  It comes with no warranty -- use at your own risk.

 

Software/hardware Requirements:

 

(1)Adobe Premiere Pro CS6 or Media Encoder CS6 (Windows version)

Sorry, MacOSX is not supported. (NVidia NVENC SDK doesn't support MacOSX.)

 

(1)NVidia KeplerGPU <GKxxx> with 1GB VRAM or more  (GTX650 or above, GT650M or above)

(Sorry, NVidia Fermi <GFxxx> is NOT supported, it doesn't have the NVENC hardware feature)

Note,if you have MPE-acceleration enabled, keep in mind the NVENC-plugin consumes some additional VRAM because it uses your GPU to perform H264-encoding.

Strongly recommend a 2GB card

 

(2) Microsoft Visual C++ 2010 SP1 x64 redistributables

          (download this from Microsoft's website)

 

Installation instructions:

 

     In Adobe Premiere Pro CS6:

     (1)      On your system, locate the installation-directory for Premiere Pro CS6.

               Usually, this is C:/Program Files/Adobe/Adobe Premiere Pro CS6

    (2)     Copy the included file Plug-ins/Common/nvenc_export.prm

               to <installation dir>/Plug-ins/Common/

 

     -> To choose the NVENC-plugin in Premiere Pro,

          In the format-menu, select <NVENC_export>

 

     In Adobe Media Encoder CS6:

     (1)    On your system, locate the installation-directory for Media Encoder CS6.

          Usually, this is C:/Program Files/Adobe/Adobe Media Encoder CS6

     (2)     Copy the included file Plug-ins/Common/nvenc_export.prm

          to <installation dir>/Plug-ins/Common/

 

     -> To choose the NVENC-plugin in Media Encoder,

          in the format-menu, select <NVENC_export>

 

Performance & quality notes:

 

(1) How much faster is NVENC-export than Adobe's built-in Mainconcept H264 encoder?

 

Depends on your PC system.  On my test-system, which is ordinary desktop PC with Intel i5-3570K (4-core 3.4GHz), NVENC-plugin is roughly 4x faster than Mainconcept. On a dual-socket Xeon Ivy Bridge-E system, NVENC would probably only be 2x faster (in Media Encoder.)

 

(2)How does the video-quality compare?

 

Comparing similar settings/video-bitrate, Mainconcept performs better at lower-bitrates(less artifacts).  At medium-high bitrates, NVENC is comparable to Mainconcept.

 

(3) How does NVENC-export encode the video?

The plugin fetches videoFrames from the Adobe application, then converts the frames from YUV420 to NV12 surface-format (using host-CPU.)  Then it passes the converted frames to the NVENC front-end.  From here, NVENC hardware takes over, and handles all aspects of the video compression. When NVENC hardware is done, it calls the plugin to output write the elementary bitstream (to the selected filepath.) NVENC-hardware does NOT encode audio, nor does not multiplex the A/Vbitstreams -- this is still done in software (on the host-CPU)

 

The NVENC hardware block has very little CPU-overhead.  But since video-encoding is just 1 step in the entire Adobe rendering path, CPU-usage will likely still be quite high when using NVENC-plugin.

 

(4) What's the maximum-size video NVENC-export can handle?

H264 High-profile @ Level 5.1, which works out to roughly 3840x2160 @ 30fps. (Note the actual encoding-speed will probably be less than 30fps.)

 

(5) How fast is the NVENC-export hardware in Kepler GPU?

Assuming the Adobe application host is infinitely fast (i.e. can send video to plugin in zero-time), NVENC-hardware will encode High-profile (CABAC, 2 refframes, 1-bframe) 1920x1080p video @ ~100fps. At 3840x2160p (4k video), the hardware encode-speed drops to roughly 20-25fps.  That is still faster than a desktop PC.

 

NVENC-speed is generally same across the Kepler family - the high-end Geforce GTX Titan (or GTX780) is no faster than the entry-level Geforce GTX650, because all Kepler models share the same NVENC hardware-block, which is totally separate and independent of the GPU's 3D-graphics engine.

 

In premiere Pro 6, MPE acceleration will greatly affect how quickly Adobe can render video to the exporter.  So a more powerful Kepler GPU will probalby complete projects faster than a less powerful one (up to NVENC's performance ceiling.)  For more info, please refer to NVidia's NVENC whitepaper at their developer website (public)

 

(6) I have a multi-GPU setup, can I encode with multiple GPUs?

No, NVENC targets and uses only a single physical GPU.  (You can choose which one.)

 

Known limitations and problems:

 

NVENC-plugin is a 'proof-of-concept' program -- it is not a finished product.  So it's missing some features, and other things are known to be broken:

 

    • Interlaced video encdoing does not work at all (not supported in current consumer Geforce drivers)

 

    • Audio support is very limited: uncompressed PCM)

no AAC or Dolby-Digital

 

    • Multiplexer support is very limited: MPEG-2 TS only, using an included third-party tool TSMuxer.EXE

no MPEG-4 muxing (*.MP4)

 

    • When the muxed MPEG-2 TS file in Windows Media Player (WMP), there is no sound.  This is because WMP doesn't recognize PCM-audio in mpeg-2 ts files.  You have 2 choices; you can use a third-party media-player such as MPC-HC or VLC.  Or you can postprocess the audio-WAV file into a compatible format (Dolby Digital/AC-3)

 

    • in the pop-up plugin User-interface, the <multiplexer> tab is missing or not shown properly.

(To fix: Select a different codec, then re-select NVENC_export.)

 

    • Doesn't support older NVidia GPUs (GTX5xx and older, GT630 and lower)

Sorry, NVENC hardware was introduced with NVidia's Kepler family (2012)  Anything older than that will NOT work with the plugin.

Viewing all 7030 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>