Recherche avancée

Sur d’autres sites (1465)

• AWS lambda SAM deploy error - Template format error : Unresolved resource dependencies

  1er juin 2022, par mozenge

  I have am trying to deploy an aws lambda function using the SAM cli. I have some layers defined in the sam template. Testing locally using sam local start-api works quite well. The but deploying using the sam deploy --guided command throws the following error
Error: Failed to create changeset for the stack: sam-app, ex: Waiter ChangeSetCreateComplete failed: Waiter encountered a terminal failure state: For expression "Status" we matched expected path: "FAILED" Status: FAILED. Reason: Template format error: Unresolved resource dependencies [arn:aws:lambda:us-west-1:338231645678:layer:ffmpeg:1] in the Resources block of the template

  


  The SAM template is as follows

  


  AWSTemplateFormatVersion: '2010-09-09'
Transform: AWS::Serverless-2016-10-31
Description: >
  video-processor-functions

  Functions to generate gif and thumbnail from uploaded videos
  
# More info about Globals: https://github.com/awslabs/serverless-application-model/blob/master/docs/globals.rst
Globals:
  Function:
    Timeout: 3
    Tracing: Active

Resources:
  VideoProcessorFunctions:
    Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
    Properties:
      CodeUri: src/
      Handler: app.lambdaHandler
      Runtime: nodejs14.x
      # timeout in seconds - 2 minutes
      Timeout: 120
      Layers:
        - !Ref VideoProcessorDepLayer
        - !Ref arn:aws:lambda:us-west-1:338231645678:layer:ffmpeg:1
      Architectures:
        - x86_64
      Events:
        HelloWorld:
          Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
          Properties:
            Path: /hello
            Method: get

  VideoProcessorDepLayer:
    Type: AWS::Serverless::LayerVersion
    Properties:
      LayerName: mh-video-processor-dependencies
      Description: Dependencies for sam app [video-processor-functions]
      ContentUri: dependencies/
      CompatibleRuntimes:
        - nodejs14.17
      LicenseInfo: 'MIT'
      RetentionPolicy: Retain

Outputs:
  # ServerlessRestApi is an implicit API created out of Events key under Serverless::Function
  # Find out more about other implicit resources you can reference within SAM
  # https://github.com/awslabs/serverless-application-model/blob/master/docs/internals/generated_resources.rst#api
  HelloWorldApi:
    Description: "API Gateway endpoint URL for Prod stage for Hello World function"
    Value: !Sub "https://${ServerlessRestApi}.execute-api.${AWS::Region}.amazonaws.com/Prod/hello/"
  VideoProcessorFunctions:
    Description: "Generate GIF and Thumnail from Video"
    Value: !GetAtt VideoProcessorFunctions.Arn
  VideoProcessorFunctionsIamRole:
    Description: "Implicit IAM Role created for MH Video Processor function"
    Value: !GetAtt VideoProcessorFunctionsRole.Arn



  


  Any ideas what i'm doing wrong ?

  


• Rails 5 with Carrierwave and S3 - creating multiple video formats for DASH streaming works but mpd file breaks

  22 novembre 2019, par Milind

  what I am doing -
  i have a Rails 5 app for video streaming(DASH MPEG) that uses FFMPEG to get encoded stream videos by converting any single video into multiple videos of multiple bit rates/size and primarily also MPD FILE that can be played easily on html video player, which i have already tested by manually running the ffmpeg scripts on the console that generates all the files.However, I want to automate this process and hence carrierwave comes into the pictures.
  Here, i use carrierwave to generate different versions(size/bitrate) of videos(mp4/webm) to upload to s3 but during running the version, where all the versions are successfully created in tmp folder, only the last version(mpd) that needs to create .mpd file, carrierwave creates a mp4 video file and just replaces the extension instead of actually creating the mpd file.

  So in the aws s3(screenshot added below), i can see my all versions and mpd file , but that mpd file which must be xml file is actually a mp4 video file or uploaded version file itself.
  I have also tried to create new file during the process, but it never works.
  Has some one encountered this problem ?

  any help will be greatly appreciated ?

  Ny code snippets below - model,uploader,output of script on the console during upload, s3 screenshot

     ##### models/video.rb ##########
  
  
  
      mount_uploader :video, VideoUploader  
  
  
  
     ####### uploaders/video_uploader.rb #########
  
  
  
      class VideoUploader < CarrierWave::Uploader::Base
  
  
  
  
  
      include CarrierWave::MiniMagick
  
      include CarrierWave::Video
  
      include CarrierWave::Video::Thumbnailer
  
      include ::CarrierWave::Backgrounder::Delay
  
  
  
      ####### for streaming ..first get the audio and then convert the input video into multiple bitrates/scale #######
  
  
  
      ###first get audio and then get all different versions of same video
  
      version :video_audio do
  
        process :get_audio
  
  
  
        def get_audio
  
          `ffmpeg -y -i "#{file.path}" -c:a aac -ac 2 -ab 128k -vn video_audio.mp4`
  
        end
  
  
  
          def full_filename(for_file)
  
            "video_audio.mp4"
  
          end
  
  
  
          def filename
  
            "video_audio.mp4"
  
          end        
  
      end 
  
  
  
      ####### similar to the above i have various version like ...#########
  
  
  
      version :video_1080 do...end
  
      version :video_720 do... end
  
      version :video_480 do ...end
  
      ...and so on..and all these versions are successfully created and uploaded to s3, however..in next version ...show it also creates a video file whereas i need a simple mpd file ONLY.
  
  
  
           ###this is where even after everything works, in S3, i can see a video file of version mpd and not actual mpd file
  
           version :mpd  do
  
             process :get_manifest
  
                ###here in the command below, the video.mpd file is successfully obtained but its uploaded as video.mpd file of added/uploaded video file and not a new mpd file
  
                ###tried with ffmpeg -f webm_dash_manifest -i too, but s3 still shows a mp4 file
  
                `MP4Box -dash 1000 -rap -frag-rap -profile onDemand -out video.mpd video_1080.mp4 video_720.mp4 video_480.mp4 video_360.mp4 video_240.mp4 video_audio.mp4 `
  
  
  
             end
  
            end
  
  
  
           ######### sidekiq console output - successful mpd is generated ################
  
                DASH-ing files - single segment
  
                Subsegment duration 1.000 - Fragment duration: 1.000 secs
  
                Splitting segments and fragments at GOP boundaries
  
                DASHing file video_1080.mp4
  
                DASHing file video_720.mp4                                  
  
                DASHing file video_480.mp4                                  
  
                DASHing file video_360.mp4                                  
  
                DASHing file video_240.mp4                                  
  
                DASHing file video_audio.mp4                                
  
               \[DASH\] Generating MPD at time 2019-11-22T00:01:59.872Z      
  
                mpd_1mb.mp4
  
                mpd_video.mpd

  this is what the uploaded files looks on s3, notice the video.mpd, its a mp4 video file just like others which should have been a simple mpd file of not more than 2kb.

  Is there something that I am missing ?
  Can Carrierwave do this or is it not made for this ?
  Do I have to write a callback and then programmatically upload files to s3, if carrierwave is not helping in this regard ?

  Kindly provide any suggestion or useful advice so that I can move ahead.

  

• Adaptive part in MPD using MP4box

  28 janvier 2019, par enigmaVada

  I have used ffmpeg to encode audio and video files of my video sample.mp4 for the dash player. The commands are as follows :

  ffmpeg -i sample.mp4 -s 426x240 -c:v libx264 -b:v 640k -g 90 -an sample_video_240.mp4
  
  ffmpeg -i sample.mp4 -s 480x360 -c:v libx264 -b:v 960k -g 90 -an sample_video_360.mp4
  
  ffmpeg -i sample.mp4 -s 640x480 -c:v libx264 -b:v 1280k -g 90 -an sample_video_480.mp4
  
  ffmpeg -i sample.mp4 -s 1280x720 -c:v libx264 -b:v 2560k -g 90 -an sample_video_720.mp4
  
  
  
  ffmpeg -i sample.mp4 -c:a aac -b:a 128k -vn sample_audio.mp4

  I have generated 240p,360p,480p and 720p videos and audio file.

  Then I have used mp4box to generate the mpd file using the following command :

  mp4box -dash 10000 -rap -profile dashavc264:onDemand -mpd-title BBB -out sample.mpd -frag 5000 sample_audio.mp4 sample_video_240.mp4 sample_video_360.mp4 sample_video_480.mp4 sample_video_720.mp4 

  I am using the dash.js player to play the video. The problem is, the adaptive part of DASH isn’t working. The player is just using the 240p video and not switching to a better format even if proper bandwidth is available. I am checking using the network tab of chrome dev tools.

  What am i doing wrong ? Please help.

  Here is the mpd file for reference :

  <?xml version="1.0"?>
  
  
  
  <mpd xmlns="urn:mpeg:dash:schema:mpd:2011" minbuffertime="PT1.500S" type="static" mediapresentationduration="PT0H1M9.869S" maxsegmentduration="PT0H0M9.985S" profiles="urn:mpeg:dash:profile:isoff-on-demand:2011,http://dashif.org/guidelines/dash264">
  
   <programinformation moreinformationurl="http://gpac.io">
  
    
  
   </programinformation>
  
  
  
   <period duration="PT0H1M9.869S">
  
    <adaptationset segmentalignment="true" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="audio/mp4" codecs="mp4a.40.2" audiosamplingrate="44100" startwithsap="1" bandwidth="130920">
  
      <audiochannelconfiguration schemeiduri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"></audiochannelconfiguration>
  
      <baseurl>sample_audio_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="902-1017">
  
        <initialization range="0-901"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
    <adaptationset segmentalignment="true" group="1" maxwidth="426" maxheight="240" maxframerate="30" par="426:240" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="video/mp4" codecs="avc1.640015" width="426" height="240" framerate="30" sar="1:1" startwithsap="1" bandwidth="590708">
  
      <baseurl>sample_video_240_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="914-1053">
  
        <initialization range="0-913"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
    <adaptationset segmentalignment="true" group="1" maxwidth="640" maxheight="480" maxframerate="30" par="4:3" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="video/mp4" codecs="avc1.64001E" width="480" height="360" framerate="30" sar="1:1" startwithsap="1" bandwidth="883873">
  
      <baseurl>sample_video_360_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="914-1053">
  
        <initialization range="0-913"></initialization>
  
      </segmentbase>
  
     </representation>
  
     <representation mimetype="video/mp4" codecs="avc1.64001E" width="640" height="480" framerate="30" sar="1:1" startwithsap="1" bandwidth="1188712">
  
      <baseurl>sample_video_480_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="913-1052">
  
        <initialization range="0-912"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
    <adaptationset segmentalignment="true" group="1" maxwidth="1280" maxheight="720" maxframerate="30" par="16:9" lang="und" subsegmentalignment="true" subsegmentstartswithsap="1">
  
     <representation mimetype="video/mp4" codecs="avc1.64001F" width="1280" height="720" framerate="30" sar="1:1" startwithsap="1" bandwidth="2365717">
  
      <baseurl>sample_video_720_dashinit.mp4</baseurl>
  
      <segmentbase indexrangeexact="true" indexrange="914-1053">
  
        <initialization range="0-913"></initialization>
  
      </segmentbase>
  
     </representation>
  
    </adaptationset>
  
   </period>
  
  </mpd>