You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cleaning up the doc. Fixed an issue. Trying to make the documentation more accessible.
4
+
### Updates 2020/05/09
5
+
Update to FFMpeg 4.2
6
6
7
7
# What is Cloud Transcode?
8
8
Cloud Transcode (CT) is your own distributed transcoding stack. With it you can transcode media files in a distributed way, at scale.
@@ -42,13 +42,13 @@ Those Activities listen to the Amazon SFN (Step functions) service for incoming
42
42
Tasks and Workflows (aka `State Machine`) are defined in the AWS SFN console, and are identified by their AWS ARNs (AWS resources identifier). You can then start `N` activity workers that will start listening for incoming jobs and execute them.
43
43
44
44
You can scale your infrastructure in AWS based on your volume, capacity, cost, resources, etc.
45
-
You can run those SFN Activities on Docker, which is recommended. A Dockerfile is provided for you.
45
+
You can run those SFN Activities on Docker, which is recommended. A Dockerfile is provided for you.
46
46
But you can run on anything and anywhere.
47
47
48
48
Your client applications can initiate new SFN workflows using the AWS SDK of your choice. The client apps will pass JSON input date to AWS SFN. <br>
49
49
SFN will then pass this input to your activities, which will then return a JSON output. This output can be passed on to the next activities.
50
50
51
-
Thanks to the `CloudProcessingEngine-SDK` you can build your own workflow and call any activities you want. You can implement your own activities as well.
51
+
Thanks to the `CloudProcessingEngine-SDK` you can build your own workflow and call any activities you want. You can implement your own activities as well.
52
52
53
53
Cloud Transcode could use help on the following Activities if you are interested in participating:
54
54
@@ -87,16 +87,16 @@ One TranscodeAssetActivity worker processes all outputs wanted, in sequence, not
87
87
88
88
Activities are standalone scripts writen in PHP (legacy reasons, but it's clean!) that can be started in command line.
89
89
90
-
```
90
+
```
91
91
bash $> ./src/activities/ValidateAssetActivity.php -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:ValidateAsset
92
92
bash $> ./src/activities/TranscodeAssetActivity.php -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:TranscodeAsset
93
93
```
94
94
95
95
Or using Docker
96
96
97
97
```
98
-
$> sudo docker run sportarc/cloudtranscode ValidateAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:ValidateAsset
99
-
$> sudo docker run sportarc/cloudtranscode TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:TranscodeAsset
98
+
$> sudo docker run sportarc/cloudtranscode:4.2 ValidateAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:ValidateAsset
99
+
$> sudo docker run sportarc/cloudtranscode:4.2 TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:TranscodeAsset
100
100
```
101
101
102
102
Using these commands, you can start an activity worker that processes one type of activity. In these cases `ValidateAssetActivity` and `TranscodeAssetActivity`
@@ -128,7 +128,7 @@ A Dockerfile like this for example:
128
128
129
129
130
130
```Dockerfile
131
-
FROM sportarc/cloudtranscode:3.3
131
+
FROM sportarc/cloudtranscode:4.2
132
132
MAINTAINER bFAN Sports
133
133
134
134
COPY clientInterfaces /usr/src/clientInterfaces
@@ -140,10 +140,10 @@ Then build your own image as follow: `sudo docker build -t sportarc/cloudtransco
140
140
Then you can start your workers like this:
141
141
142
142
```
143
-
$> sudo docker run sportarc/cloudtranscode-prod ValidateAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:ValidateAsset -C /usr/src/clientInterfaces/ValidateAssetClientInterfaces.php
144
-
$> sudo docker run sportarc/cloudtranscode-prod TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:TranscodeAllOutputAssets -C /usr/src/clientInterfaces/TranscodeAllOutputAssetsClientInterfaces.php
145
-
$> sudo docker run sportarc/cloudtranscode-prod TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:TranscodeImageAsset -C /usr/src/clientInterfaces/TranscodeImagesAssetsClientInterfaces.php
146
-
$> sudo docker run sportarc/cloudtranscode-prod TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:OnDemandTranscodeAsset -C /usr/src/clientInterfaces/OnDemandTranscodeAssetClientInterfaces.php
143
+
$> sudo docker run sportarc/cloudtranscode-prod:4.2 ValidateAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:ValidateAsset -C /usr/src/clientInterfaces/ValidateAssetClientInterfaces.php
144
+
$> sudo docker run sportarc/cloudtranscode-prod:4.2 TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:TranscodeAllOutputAssets -C /usr/src/clientInterfaces/TranscodeAllOutputAssetsClientInterfaces.php
145
+
$> sudo docker run sportarc/cloudtranscode-prod:4.2 TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:TranscodeImageAsset -C /usr/src/clientInterfaces/TranscodeImagesAssetsClientInterfaces.php
146
+
$> sudo docker run sportarc/cloudtranscode-prod:4.2 TranscodeAssetActivity -A arn:aws:states:eu-west-1:XXXXXXXXXXXX:activity:OnDemandTranscodeAsset -C /usr/src/clientInterfaces/OnDemandTranscodeAssetClientInterfaces.php
147
147
```
148
148
149
149
As you can see, you can create many SFN tasks. Each task will execute the same activity code, but they are connected to different client applications using different Interface classes.
@@ -227,12 +227,12 @@ Thanks for contributing !
227
227
228
228
# FFmpeg
229
229
230
-
CloudTranscode uses FFmpeg 3.3
230
+
CloudTranscode uses FFmpeg 4.2
231
231
232
232
The CloudTranscode Docker image is based on two other images:
233
233
234
-
-https://hub.docker.com/r/sportarc/ffmpeg/: Base image containing: Ubuntu 14, PHP CLI 5.6, FFmpeg
235
-
-https://hub.docker.com/r/sportarc/cloudtranscode-base/: Adds `ImageMagic` to the above image
0 commit comments