Results 1 to 6 of 6

Thread: NVENC not available on Windows g2.2xlarge EC2 instance

  1. #1
    Join Date
    Jan 2014
    Posts
    11

    Default NVENC not available on Windows g2.2xlarge EC2 instance

    Hello,
    We just upgraded to Wowza Streaming Engine 4.
    I am trying to enable the hardware encoding on our Windows 2008 server g2.2xlarge EC2 instance and I followed the steps below with no success:

    1) enable the transcoder in the application

    2) set the video/transcoder element as follows:
    <Encode>
    <Enable>true</Enable>
    <Name>main</Name>
    <StreamName>mp4:${SourceStreamName}_main</StreamName>
    <Video>
    <!-- H.264, H.263, PassThru, Disable -->
    <Codec>H.264</Codec>
    <!-- default, QuickSync, CUDA, NVENC -->
    <Transcoder>NVENC</Transcoder>
    <GPUID>-1</GPUID>


    When I start streaming I see the following feedback in the wowza log file:
    JNI:VideoEncoderH264QuickSyncHost[global]: QuickSync: hardware acceleration is not available (software only)
    JNI:TranscoderSession.isCUDAAvailable[_defaultVHost_:MVC/_definst_/studio1]: NVidia hardware acceleration is NOT available
    JNI:TranscoderSession.isQuickSyncAvailable[_defaultVHost_:MVC/_definst_/studio1]: Intel Quick Sync hardware acceleration is NOT available.

    that shows that the software encoder is used.

    Is anybody using NVENC on EC2 GPU licenses successfully?
    Thanks'

  2. #2
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Hi,

    There are a couple of necessary added steps which are detailed here.

    Richard

  3. #3
    Join Date
    Jan 2014
    Posts
    11

    Default

    Thanks for the quick replay,
    we are actually using Windows EC2 licenses, the steps that you mentioned are for a Linux instance.
    Do we need to switch to a Linux server environment for NVENC? I am more comfortable with Windows though.

  4. #4
    Join Date
    Dec 2007
    Posts
    21,962

  5. #5
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Also, side-note on the instance types with 10g througput: it is our understanding that you can only get near that level of throughput between Wowza servers using internal DNS. So you can support a large edge cluster of small ec2 instances. But you are also limited by Java to about 5g of utiiization per JVM. It is possible to run two instances of Wowza on one machine for greater utilization of the network bandwidth

    Richard

  6. #6
    Join Date
    Jan 2014
    Posts
    11

    Default

    [QUOTE=rrlanham;134851]Have you seen this article?
    This is what I was missing. I will have to take some time to follow its' steps.
    Thanks'

Similar Threads

  1. NVENC and CUDA on Amazon EC2 instances: has it been tried?
    By niemion in forum Wowza Streaming Engine in the Cloud
    Replies: 3
    Last Post: 02-23-2016, 08:10 AM
  2. Replies: 1
    Last Post: 11-03-2014, 11:49 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •