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

Question

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: '' 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!

BCole2019 · Answer

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](https://docs.aws.amazon.com/mediaconvert/latest/ug/reference-codecs-containers-input.html).

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

Mike-ME · Answer

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:///

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

Contenuto pertinente