SOURCE URL: https://flowplayer.org/docs/encoding.html

Video encoding

To ease the task of encoding your original videos to the various formats we are building an online video platform on top of Amazon's infrastructure. Try the free version now!

Otherwise consider using one of the existing online platforms - like encoding.com or Zencoder - which offers the services that comply with your wishes.

For those determined not to delegate this task a few tips are to follow.

General advice

Always bear in mind that encoding for delivery over the wire differs fundamentally from encoding for a desktop viewing program. Your content has to pass through the needle hole of a connection whose speed is not under your control.

The results will and can only be a compromise between desired quality and delivery speed achieved by lossy compression. Moreover they will vary depending on the content of the original. A simple headshot is way more compression friendly than a movie containing high motion scenes and/or pan shots. You have to decide on which side of the scales you make more sacrifices, also in view of your target audience and the assumed speed of their connections.

  • Be extremely miserly about bitrate and dimensions! Downscaling is a waste of resources and often a video in the dimensions of the player container element on the page displays reasonably well in fullscreen too.
  • Encode to a constant frame rate. Variable frame rate will break playback in various scenarios, depending on engine, browser or platform.
  • If the input video is interlaced, you should apply a deinterlace filter.
  • If the input video does not have a sample ratio of 1/1 (square pixels), you must apply a filter enforcing a sample ratio of 1/1 because some versions of Internet Explorer cannot handle anamorphic MP4 and Flash is agnostic of display aspect ratio, knows only about width and height.

Assuming your original video has an aspect ratio of 16/9 and keeping the above caveats in mind you should aim for:

  • a resolution of 640x360 pixels
  • an average video bitrate between 400 and 1000 kilobits per second
  • an average audio bitrate between 40 and 80 kilobits per second

Take your time to try out various encoding settings on a small sample representative of your content. Good transcoding programs offer a constant quality switch. Try it and inspect the resulting bitrate. For the final encode use 2-pass encoding which distributes the bitrate better while keeping a good quality balance.

Codecs

MP4, WEBM and OGG are the containers for the following video and audio codecs:

Container video codec audio codec
MP4 H.264 aka MPEG-4 AVC or MPEG-4 Part 10 AAC
WEBM VP8 Vorbis
OGG Theora Vorbis

We did not cover the MPEG-4 Visual or MPEG-4 Part 2 video codec because it is not suitable as Flash fallback and will also not play in Internet Explorer in HTML5 mode. To avoid bad surprises encode to the more modern MPEG-4 AVC.

Ogg video

Unless you want to cover all your bases, consider omitting it. Except for a few corner cases concerning older browsers where you can failover to MP4 playback in Flash mode, either WEBM or MP4 will do the job as well, and better.

MP4 and metadata

H.264 encoded videos carry their metadata - duration, frame rate etc. - in the so called "moov atom".

By default encoding programs will insert the moov atom at the end of the video file which is suitable for playback of a local file in a desktop program. However, any kind of progressive download requires the metadata to be available right away for immediate playback. Otherwise the player has to wait for the entire video to be downloaded before playback starts.

Make sure to select an option in your transcoding program which puts the moov atom at the beginning of the file!

In case you already have a lot of MP4 videos with the moov atom at the end of the file, use a dedicated program such as QTIndexSwapper or MOOV Relocator to move it to the beginning.

MP4 for iOS and mobile devices

MPEG-4 AVC is a powerful codec which allows very effective compression at various profiles and levels. As higher profiles and levels are decoding intensive, they are not supported by mobile devices to ease their processor workload.

Let's take iOS as an example: Even the latest iPads will only play videos encoded at H.264 Main profile Level 3.1. But if you want to cater safely for the widest audience including viewers with iPhones and iPods and older iOS versions you should stick with:

  • Baseline Profile
  • Level 3.0
  • 1 reference frame
  • Resolution of maximum 640px width and maximum 480px height

Encoding samples

To give you an idea to what the above considerations lead we choose the commandline syntax of the FFmpeg program - there are also graphical frontends for FFmpeg, like Handbrake or ffmpegX (for Mac OS). There are many other transcoding programs around, and you should of course choose one you feel most comfortable with. Be aware though that often the quality of the program is directly proportional to its learning curve. It's also recommended to use the very latest version of the respective program because development in this area is moving fast.

In the following replace x in -pass x with 1 and 2 for the first and second pass/run respectively. We assume the original movie in.suffix has an aspect ratio of 16/9 and a frame rate of 25 frames per second.

WEBM encoding sample

ffmpeg -y -i in.suffix \
-filter:v scale=640:360,setsar=1/1 -pix_fmt yuv420p \
-vpre libvpx-720p -b:v 500k -r:v 25/1 -force_fps \
-c:a libvorbis -b:a 80k -pass x out.webm

MP4 encoding sample

ffmpeg -y -i in.suffix \
-filter:v scale=640:360,setsar=1/1 -pix_fmt yuv420p \
-c:v libx264 -preset:v slow -profile:v baseline \
-x264opts level=3.0:ref=1 -b:v 700k -r:v 25/1 -force_fps \
-movflags +faststart -c:a libfaac -b:a 80k -pass x out.mp4

Disclaimer: The above commandlines are very basic, and the syntax may differ in older FFmpeg versions. This cannot be the place for detailed information on how to handle the transcoding program(s) of your choice. Please consult the respective manuals, online documentation or mailing lists for in-depth advice regarding your transcoding software.

Flowplayer-encoding的更多相关文章

  1. javac -encoding utf8 in linux

    由于另外负责编码的同事用的是utf-8,我用的默认的编码格式gbk,在提交代码时,为了迁就他,我打算把格式用工具转成utf-8. 转化成果后,然后在make一下,发现javac -encoding u ...

  2. 创建Odoo8数据库时的“new encoding (UTF8) is incompatible with the encoding of the template database (SQL_ASCII)“问题

    Odoo8创建数据库时,显示如下错误信息: DataError: new encoding (UTF8) is incompatible with the encoding of the templa ...

  3. Node.js Base64 Encoding和Decoding

    如何在Node.js中encode一个字符串呢?是否也像在PHP中使用base64_encode()一样简单? 在Node.js中有许多encoding字符串的方法,而不用像在JavaScript中那 ...

  4. java Properties异常:Malformed \uxxxx encoding.

    昨天项目中遇到一个 java.lang.IllegalArgumentException: Malformed \uxxxx encoding.这样的一个异常,debug了一下发现是读取propert ...

  5. svn: Can't convert string from 'UTF-8' to native encoding 的解决办法(转)

    http://www.cnblogs.com/xuxm2007/archive/2010/10/26/1861223.html svn 版本库中有文件是以中文字符命名的,在 Linux 下 check ...

  6. C# 字符编码类Encoding

    在网络通信中,很多情况下都是将字符信息转成字节序列进行传输.将字符序列转为字节序列的过程称为编码.当这些字节传送到接收方,接收方需要逆向将字节序列转为字符序列.这个过程就是解码. 常见编码有ASCII ...

  7. 字符集和字符编码(Charset & Encoding)

    字符集和字符编码(Charset & Encoding)[转] 1.基础知识 计算机中储存的信息都是用二进制数表示的:而我们在屏幕上看到的英文.汉字等字符是二进制数转换之后的结果.通俗的说,按 ...

  8. 使用英文版eclipse保存代码,出现some characters cannot be mapped using "Cp1251" character encoding.

    some characters cannot be mapped using "Cp1251" character encoding. 解决办法:方案一: eclipse-> ...

  9. <?xml version="1.0" encoding="UTF-8"?> 的作用?

    version="1.0" 声明用的xml版本是1.0 encoding="UTF-8" 声明用xml传输数据的时候的字符编码,假如文档里面有中文,编码方式不是 ...

  10. 关于Unicode和URL encoding入门的一切以及注意事项

    本文同时也发表在我另一篇独立博客 <关于Unicode和URL encoding入门的一切以及注意事项>(管理员请注意!这两个都是我自己的原创博客!不要踢出首页!不是转载!已经误会三次了! ...

随机推荐

  1. Hibernate配置Log4J,很有参考价值的

    hibernate3 自带的默认的日志框架是slf4j,hibernate3的slf只是一个日志的接口,而hibernate3 自带默认的日志框架,在实际开发中很少有公司或者是项目中用到,这里记录一种 ...

  2. 开发回归测试之Selenium开发环境搭建

    前言 在解bug的过程中,经常遇到解完某个bug带来新的bug,原因一般是因为回归测试不足或不全面,下面我们来看看怎么利用selenium工具来完成开发后的回归测试, 虽然这可能是QA的事,不过有利于 ...

  3. javaWeb中servlet开发(3)——Servlet生命周期

    生命周期:是一个程序的存在周期,servlet由于是受容器的管理,所以容器来决定其生命周期 1.servlet生命周期 2.servlet生命周期对应的方法 3.servlet生命周期代码 publi ...

  4. iOS摄像头和相册-UIImagePickerController常用操作

    在一些应用中,我们需要用到iOS设备的摄像头进行拍照,视频.并且从相册中选取我们需要的图片或者视频. 关于iOS摄像头和相册的应用,可以使用UIImagePickerController类来完成控制. ...

  5. iOS应用架构谈 网络层设计方案

    网络层在一个App中也是一个不可缺少的部分,工程师们在网络层能够发挥的空间也比较大.另外,苹果对网络请求部分已经做了很好的封装,业界的AFNetworking也被广泛使用.其它的ASIHttpRequ ...

  6. thinkphp的钩子的两种配置和两种调用方法

    thinkphp的钩子行为类是一个比较难以理解的问题,网上有很多写thinkphp钩子类的文章,我也是根据网上的文章来设置thinkphp的钩子行为的,但根据这些网上的文章,我在设置的过程中,尝试了十 ...

  7. 白话学习MVC(八)Action的执行二

    一.概述 上篇博文<白话学习MVC(七)Action的执行一>介绍了ASP.NET MVC中Action的执行的简要流程,并且对TempData的运行机制进行了详细的分析,本篇来分析上一篇 ...

  8. centos7 systemctl命令

    systemctl命令是系统服务管理器指令,它实际上将 service 和 chkconfig 这两个命令组合到一起. 实例: 启动nfs服务:systemctl start nfs-server.s ...

  9. 自定义view中错误:No resource identifier found for attribute X in package X

  10. ios - block数据的回调

    block在代理,kvo中传递数据效率最高 实现原理 控制器B想传递数据给控制器A.通过在B控制器中创建Block类型的类,创建方法,方法参数是刚才创建的block类型的变量.在方法实现的内部调用参数 ...