Skip to content

MediaConvert job notification via EventBridge returns incorrect output path

0

My application creates jobs in MediaConvert that output both an MP4 and VTT file to an S3 bucket.

I have a rule set up with EventBridge that notifies my API when the job has completed. In the outputGroups of the event payload, the outputFilePaths for the MP4 file is correct, however the path for the VTT file is incorrect, and is missing the .vtt file extension. How can I get MediaConvert/EventBridge to consistently send the correct paths for both outputs?

Here is an example event payload received by my server:

"outputGroupDetails": [
  {
    "outputDetails": [
      {
        "outputFilePaths": [
          "s3://bucket-name/path/to/video-file.mp4"
        ],
        "durationInMs": 3208,
        "videoDetails": {
          "widthInPx": 2160,
          "heightInPx": 978
        }
      },
      {
        "outputFilePaths": [
           "s3://bucket-name/path/to/subtitles-file"
        ],
        "durationInMs": 0
      }
    ]
  }
]

When I inspect the S3 bucket, the subtitles file has been successfully generated with the .vtt extension, making the outputFilePath in the event payload incorrect.

2 Answers
0

When AWS Elemental MediaConvert completes a job, it sends a notification through EventBridge that includes details about the output files. Based on your example, it appears that there's an issue with the file extension for your VTT subtitle file in the notification payload.

This is likely related to how MediaConvert handles different output types in the EventBridge notifications. The outputFilePaths property provides the file path to either the media or the manifest, depending on the output group type. For standard output files in a FILE_GROUP (which appears to be what you're using), MediaConvert should include the complete file path including the extension.

Since your VTT file is being correctly generated in S3 with the proper extension, but the notification is missing the extension, this appears to be inconsistent behavior.

To address this issue, you could:

  1. Consider adding logic in your application to append the ".vtt" extension to subtitle file paths when processing the notification.

  2. Verify that your MediaConvert job configuration correctly specifies the VTT output with the proper extension.

  3. Contact AWS Support to report this inconsistency, as the EventBridge notification should ideally include the complete file path with extension for all output files.

In the meantime, since you know the files are being correctly generated in S3, you could modify your application to handle this specific case by checking for subtitle outputs and appending the appropriate extension when needed.
Sources
Output file names and paths - MediaConvert
File group - MediaConvert

answered a year ago

  • Contact AWS Support to report this inconsistency, as the EventBridge notification should ideally include the complete file path with extension for all output files.

    Is it possible to report a bug via AWS support without paying for a support plan?

0

I tried the same setup and I see both outputs are presented in notification message from event bridge:

"status":"COMPLETE", "userMetadata":{},"outputGroupDetails":[

{"outputDetails":[{"outputFilePaths":["s3://bucket/EventBridgeTesting2/colored-subs_media.mp4"],"durationInMs":30040,"videoDetails":{"widthInPx":1920,"heightInPx":1080,"averageBitrate":512800,"qvbrAvgQuality":1.35,"qvbrMinQuality":1.0,"qvbrMaxQuality":6.25,"qvbrMinQualityLocation":0,"qvbrMaxQualityLocation":28560}},

{"outputFilePaths":["s3://bucket/EventBridgeTesting2/colored-subs_vtt.vtt"],"durationInMs":0}],"type":"FILE_GROUP"}],"paddingInserted":0,"blackVideoDetected":0 ,"warnings":[{"code":230001,"count":1},{"code":230005,"count":1},{"code":240001,"count":1}]

AWS

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.