Confusingly, avconv is actually LibAv, a vicious fork of ffmpeg, maintained by a cadre of developers who stormed out on the head of the ffmpeg project. The former has been around since 2000, and has generally implemented all the features of the latter. And honestly, I was too shagged out to look at any others once I finished. To turn the frame sequences into video files, either use the sequence as a source in Adobe Media Encoder or use a command-line tool like ffmpeg or avconv. I returned to the tip I from the last post, which had convinced me that this could be done easily in Node, the upshot of which was: The only additional PureMVC note is to point you to the npmvc package for Node.js, which works like a charm. For that reason, I won’t describe the scaffolding of the microservice, just the important bits it will need to implement. And setting one up requires very little effort. PureMVC is prescriptive, so once you’ve seen one PureMVC app, you’ve seen them all.
#Fluent ffmpeg add watermark code#
Node.js is a natural choice for microservices when they are developed hand-in-hand with an HTML5 client (particularly if the same developer is working on both in a ‘full-stack’ role). Writing Javascript in both places reduces the cognitive friction associated with shifting your focus between the client code and server code.Īnd since our client is built on PureMVC, it’s a further comfort for the microservices to employ the same architecture. Most configurations approach a third of the price. The Goog even has a TCO calculator that shows you how much your rig would cost if you deployed it on AWS. Plus I can take VM snapshots at any point along the way to ensure that if things go astray on the server (like a spurious sudo rm -rf executed in the wrong folder), I can get back to sanity with the click of a button. They blaze, compared to my previous provider Godaddy, and cost half as much to host. I was already familiar with the console, which compares favorably to AWS in nearly every detail, after recently moving my company and personal sites from Godaddy to Google Cloud on this setting. If you choose the smallest disk (10GB), and the smallest machine (f1-micro: 1vCPU, 0.6 GB RAM), it’ll cost you a whopping US$4.95 to operate. So, I launched a Bitnami VM with a Node.js stack. At a minimum it would impact our pricing model. There will be a lot of frames pushed down the socket to Node, so that would be a real issue for us on AWS. We’d originally planned to use Amazon Web Services for hosting, but decided on Google Cloud, since there is no ingress bandwidth charge. In this article I’ll be discussing the early progress of my exploration into that approach. In the previous article, I detailed how we arrived at the idea of rendering our music visualizer’s WebGL frames in the web browser, and shipping them to the server for assembly into a final video.