From ceb5729a5e7cc27a377b4be9515fcb54672017fa Mon Sep 17 00:00:00 2001 From: Hangyu Kuang Date: Wed, 13 Sep 2017 11:09:27 -0700 Subject: [PATCH] MediaMuxer: Fix a typo in java doc. Bug: 63965858 Test: None as just document. Change-Id: I4c849a02c3b19d8cf23e92a960cfde023e213ca1 --- media/java/android/media/MediaMuxer.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/media/java/android/media/MediaMuxer.java b/media/java/android/media/MediaMuxer.java index 832b2974f53c7..91e57ee073b02 100644 --- a/media/java/android/media/MediaMuxer.java +++ b/media/java/android/media/MediaMuxer.java @@ -70,7 +70,7 @@ import java.util.Map;

Per-frame metadata is useful in carrying extra information that correlated with video or audio to facilitate offline processing, e.g. gyro signals from the sensor could help video stabilization when - doing offline processing. Metaadata track is only supported in MP4 container. When adding a new + doing offline processing. Metadata track is only supported in MP4 container. When adding a new metadata track, track's mime format must start with prefix "application/", e.g. "applicaton/gyro". Metadata's format/layout will be defined by the application. Writing metadata is nearly the same as writing video/audio data except that the data will not be from mediacodec. Application just needs