Flavio Ribeiro
Flavio Ribeiro
There's some [players](http://support.jwplayer.com/customer/portal/articles/1407439-adding-preview-thumbnails) that uses WebVTT to display the thumbnails.
When a job is finished with HLS outputs, the API is not exposing the master manifest url: ```json { "output": { "destination": "s3://cbsi-encode-outputs/f1a54dbd56cdf180/" }, "progress": 100, "providerJobId": "ff6a5a82-4802-4667-9732-15eac6a35e7b", "providerName": "bitmovin",...
I could find some similar code on encodingcom and zencoder integration. I bet we can find more. We should create a helpers module to avoid duplicated code: Examples: https://github.com/NYTimes/video-transcoding-api/blob/master/provider/encodingcom/encodingcom.go#L130-L138 and...
We have providers reporting `advanced_hls`, `mpeg-ts` and other containers on the container field for hls jobs. We should normalize this on the transcoding api.
We could at least return job ID's. This will help us on debugging what's going on.
moving from #148 Since we have the concept of `LocalPreset`s now, we can support all encoding services even if they don't have API's to handle presets. Do you guys think...
The rate controls is always `VBR` no matter if we're passing `CBR` or `VBR` on the preset.