By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

AWS Elemental MediaConvert fails to transcode some iOS videos that were transferred to MacBook

0

We have recently migrated from Telestream Flip to AWS Elemental MediaConvert as our video transcoding solution. Most of the functionality works as expected, but we are encountering an issue when uploading videos from iOS devices via a desktop browser.

Here are the steps we follow:

  1. Record a video on an iOS device using the camera or screen recording.
  2. Transfer the video to a MacBook using Airdrop, iCloud, Photos, or other methods.
  3. Upload the video through our web app.

However, when attempting to process the uploaded videos using MediaConvert, we encounter the following error for files with the extensions .mov or .MP4:

3404: '<https://SOME-BUCKET.s3-eu-west-1.amazonaws.com/2023/09/21/10/46/08/12345-1234-1234-1234-1a2a3a4a/some-video.mov?REMOVED=true>' not found.

We have verified that the file does exist in the specified bucket. Interestingly, if we change the file extension of any MP4 videos to lowercase (mp4), the upload and transcoding process is successful. However, no amount of modifying the file names for mov files seems to make a difference.

These tests are successful via Telestream Flip

Has anyone encountered a similar issue when using AWS Elemental MediaConvert for transcoding iOS videos? Any insights or suggestions would be greatly appreciated. Thank you!

Topics
Media ServicesCompute
Tags
AWS Elemental MediaConvertVideo Transcoding
Language
English
David
asked 7 months ago296 views
2 Answers
0

David, thank you for your question. Can you provide additional details about the transcode workflow?

  • Are the MediaConvert jobs being created automatically, via a lambda function or some other code?
  • Is the MediaConvert in the same account as the S3 buckets providing the source files?

A few observations:

  • The source file has an http:// reference, which indicates the source could come from beyond the AWS account where MediaConvert resides. Cross account accessing of files would require IAM roles that allow that. If the S3 bucket and MediaConvert are in the same account, you may want to consider using the format s3://<bucket_name>/<path>/<source_file_name>, where <bucket_name> does not include 's3.amazonaws.com'.
  • Can you indicate why the parameter 'REMOVED=true' is in source file path name? You may want to try removing that and seeing if the results are better.
  • MediaConvert should be able to handle both .mp4 and .mov source file formats. If the errors are only indicating 'not found', getting beyond that may allow both to be ingested.
AWS
Mike-ME
answered 7 months ago
0

Hello David,

I looked through the MediaConvert Documentation and found a "Note" that is on topic:

"Note: MediaConvert doesn't support external reference MOV, external reference MXF, or fragmented MP4 initialization segments. Your MOV, MXF, or MP4 inputs must be self-contained."

It might be the case that you are getting the "not found" error because MediaConvert does not detect the media files within your MOV file. Try and check to ensure that your MOV file has all of the necessary video components within the file, and is not referring to external files. It needs to be a standalone file - meaning that everything needed to play back that file is contained within the file itself.

Here is a Complete list of MediaConvert compatible inputs.

I hope this helps, and please do not hesitate to contact us if you need to continue the conversation.

AWS
EXPERT
BCole2019
answered 7 months 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.

Guidelines for Answering Questions

Relevant content