Newbe Dev Stack

Answer : Yes, using ffmpeg . Open a terminal and direct it to the directory containing the H.265 encoded files, assuming you have ffmpeg and the appropriate libraries installed and assuming they are in MKV format copy and paste the following into the terminal window. INPUT="$1" for i in *.mkv ; do ffmpeg -i "$i" -bsf:v h264_mp4toannexb -sn -map 0:0 -map 0:1 -vcodec libx264 "$i.ts" mv "$i.ts" "$i.mpg" sleep 3 done There you have it. This will convert to h.264 in an MPG container in the same directory. Explanation of the command switches: for i in *.mkv ; do ... done This sets up all .mkv files in a directory to be included in the batch process. This may be changed to accommodate the container extension of the files you wish to process. ffmpeg -i "$i" Executes the program ffmpeg and calls for files to be processed. -bsf:v activates the video bit stream filter to be used. h264_mp4toannexb - Is...

Answer : FFmpeg does not include text file based presets and profiles anymore for libx264, i.e. what you've used with the -vpre option. These have been depreciated and removed in favor of accessing the actual x264 presets, profiles (and tunes) with the -preset , -profile:v , and -tune options. The old text files only emulated the official x264 presets and profiles, and due to several limitations could not offer full functionality that the new system provides. It is also much easier to maintain. Additionally, many encoders have their own separate options; also called "private options". You will have to look into the audio and video encoder options for common codecs in the FFmpeg online documentation, or check the output of ffmpeg -h full for a complete list of supported options. For example, x264 lists its options under libx264 AVOptions in the full help output. If your ffmpeg supports -preset then any text file presets should not be used, and FFmpeg no longer ...

Answer : ffmpeg is not preinstalled (pretty much just ImageMagick); to see exactly what's installed check out the Dockerfile here: https://github.com/GoogleCloudPlatform/nodejs-docker/blob/master/runtime-image/Dockerfile. However, you can upload arbitrary binaries when you upload your code using gcloud beta functions deploy because everything in the current directory (except node_modules ) is uploaded. Note: you only have disk write access at /tmp/ . Option 1: use ffmpeg-static npm module ffmpeg-static is an npm module that builds the correct ffmpeg binary based on the current system during npm install . Since Cloud Functions builds your code in the cloud, it'll build the correct ffmpeg binary. https://github.com/eugeneware/ffmpeg-static You can see it in action in the Cloud Functions for Firebase examples repo. const ffmpeg = require('fluent-ffmpeg'); const ffmpeg_static = require('ffmpeg-static'); var cmd = ffmpeg('/tmp/video.avi') ....