Yuya Tanaka

@selsamman flush() was used to **seek** to beginning of video after determining output format. That's why I thought similar issues can happen on some devices. If you have affected device...

Ah, you're right, flush()ing is different than skipping leading frames (seeking). I'm afraid that just skipping frames can cause another unexpected codec bug or not. I'll test with device farm...

It seems weird error specific to Samsung's codec. I have no idea how to fix it for now. https://stackoverflow.com/search?q=0xffffec77

Is the issue reproducing always or intermittently? Also please try Full HD (1920x1080) mp4.

See https://github.com/ypresto/android-transcoder/issues/40#issuecomment-277697028 . Supported resolutions (and combinations of it and bitrate) can be different by devices. And currently, there is no easy way to detect it. `/etc/media_profiles.xml` or etc. on...

For example, my device has below file: (It seems used by CamcorderProfile) ```xml ... ... ... ```

[CTS](https://source.android.com/compatibility/cts/index.html) contains encoding test for 1280x720 and it is listed in [Supported Media Formats](https://developer.android.com/guide/topics/media/media-formats.html#recommendations). But other resolution like 960x540 (iOS can encode in this res) causes broken video at least...

This could be happen when: - Input video uses MPEG4 Visual codec. - This library have chosen not to transcode video. Latter might be because resolution of input video is...

See this: https://github.com/ypresto/android-transcoder/issues/40#issuecomment-277697028 Android device has restriction around mp4 format. Because this library is hardware solution, there is no way to make it 100% compatible with videos from other devices.

In my idea: ``` java AndroidTranscoder.for("/path/to/video_file.mp4") .geometry(1280, 800) // or enum for presets..? .videoBitrate(8000 * 1000) // or Kbps..? .audioBitRate(128 * 1000) // default: as-is .audioChannels(1) // default: as-is .faststart(false)...