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
If you're viewing times in Encoding Queue in our login area, note that the times are displayed in the Central US time zone. You can change this default, easily, by following the directions here: http://www.encoding.com/how_can_i_change_the_time_zone_setting_on_my_queue
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.
Yes! You can select the following choices in our watch folders to create files specifically targeted for playback via Roku. Click on any of the links below to expose the templates that we use for each preset: roku_800 roku_1200 roku_1800 roku_2700 roku_hls
Roku 2700k Template
Roku 1800k Template
Roku 1200k Template