Find your answers here.
Are you used to sending XMLs to Encoding.com's API? Vid.ly XMLs are a bit different. Have a look! Note the usage of the source & sourcefile tags. All API action requests are sent to the http://m.vid.ly/api/ page. Client must send HTTP(S) POST request with single parameter named “xml”. The server response is a normal XML Read more
Sounds like you have lots of encoding to do there! With Encoding.com's powerful API or snappy watch folders, you can request a maximum of 100 tasks per encode, or folder respectively.
Do you have a bunch of files that require encoding, but want to know more about the source media properties? Use this workflow to achieve this: Step 1: Send source media to the API via the AddMediaBenchmark action. Manage.encoding.com will accept this request and assign a Media ID for the video. http://www.encoding.com/api/category/category/complete_api_documentation#addmedia_action Step 2: Send Read more
Within the format tag, you can now specify the duration and length of the fade that you would like to apply to your encodes. via XML: Definitions: FadeInStart: Start of fade_in effect in seconds FadeInDuration: Duration of fade_in effect in seconds FadeOutStart: Start of fade_out effect in seconds. If you specify this parameter equal to 0, Read more
With Encoding.com, you can easily add a dissolve at the start and end of your encodes via our fade commands. Click on this link for more information.
Roku 2700k Template
Roku 1800k Template
Roku 1200k Template
Standard Template for 800k
Use a PNG with alpha-channel as Logo source. If your logo source is PNG with alpha-channel, set logo_mode equal to 1, to keep transparency. Note: the logo_transparent tag is only for usage with the vp6_flix output via XML. Example XML: