Uploading Content

From ThirdPresence Wiki

Contents

Supported file formats and encoding standards

We support most video/audio file formats and encoding standards. Here is a partial list of supported file formats:

AVI, MPEG, FLV, ASF, WMV, WMA, MOV, MP4, 3GP, OGG, MKV, WAV, MXF

A partial list of supported codecs:

H.264, H.263, MPEG-4, MPEG 1/2, VP5/6, DIVX, XviD, Theora, MJPEG, WMV, VC-1, DV, Sorenson

If the format you want to use is not supported, please send a sample file to support@thirdpresence.com and we will contact you to find a solution.

How to optimize video quality

The technical quality of the source video files that you upload to ThirdPresence also determines the quality of the mobile versions, so please upload the best (i.e. high bitrate) version that you have available. Any high-quality on-line video file will ensure good result.

Here is an example set of encoding parameters that will guarantee good results:

  File format: MPEG-4 (.mp4)
  Video codec: AVC, baseline level 3
  Video size: 640x360
  Frame rate: 24
  Bit rate: 1200 kbps
  Audio codec: AAC-LC
  Sampling rate: 44.1 KHz
  Bit rate: 125 kbps

Note: You only need to upload the original source video file. You don't need to create a separate "mobile compatible" version of the video file for ThirdPresence.

ThirdPresence will automatically convert the video to multiple different mobile versions as required to support all the different handsets with optimal quality.

ThirdPresence retains the original aspect ratio of the uploaded video and in some cases (e.g. with standard H.263 which limits the video sizes to certain pre-defined values) pads the extra horizontal or vertical lines with black colour in case the video would need to be squeezed.

How to upload content

Video content can be uploaded to ThirdPresence in three different ways:

  • FTP: Easy way to upload video files for publishing using Internet's standard File Transfer Protocol
  • RSS: Really Simple Syndication is a web feed format that content management systems are usually able to publish. ThirdPresence supports constant RSS feed polling for determining when new videos are published on your system for automatizing the publishing process
  • API: ThirdPresence provides RESTful API that you can use to ThirdPresence mobile platform directly to your service

It is up to you to decide which method you want to use. If your content is updated often, using either RSS or API is recommended.

For more information about the uploading content see subchapters Uploading with FTP, Uploading with RSS or jump to Developer's guide to API.

Uploading with FTP

For detailed instructions of how to upload your video content to ThirdPresence using File Transfer Protocol (FTP), see chapter uploading with FTP.

Uploading with RSS

For detailed instructions of how to upload your video content to ThirdPresence using Really Simple Syndication (RSS) feeds, see chapter uploading with RSS.

Uploading using the API

Detailed instructions about the API can be found here.

How to do live streaming

Live video and audio streams usually contain e.g. a linear TV channel or radio channel. We can make mobile device-compatible versions of most of the web live streams. To publish live video and audio streams, please send the current live stream URLs to support@thirdpresence.com.

The quality of the source stream defines the quality of the stream that is provided to mobile phone users. If you have several versions of the live stream, we prefer to use the one with the highest bitrate.

Here is an example of a good live stream to use as a source for ThirdPresence:

http://wstreaming.zdf.de/encoder/3sat_vh.asx

The ThirdPresence platform will connect to the live stream and convert it into the different formats required by different mobile devices. ThirdPresence will then provide to you a single URL that you can use in your mobile web site or in your application (see Publishing your content).

ThirdPresence currently supports the following live stream formats as input:

HTTP, MMS, RTSP, RTMP

Make sure that the live video/audio URLs are accessible by our encoding server farm. The server farm used for live streaming is located in the U.K., so you might need to adjust your geo-ip access settings accordingly.

This page was last modified on 1 February 2010, at 06:46.