Minimal example: transcode from MP3 to WMA:
ffmpeg -i input.mp3 output.wma
You can get the list of supported formats with:
ffmpeg -formats
You can get the list of installed codecs with:
| # assumes you have ubuntu-desktop installed which includes stock libpulse | |
| sudo add-apt-repository ppa:therealkenc/wsl-pulseaudio | |
| sudo apt-get update && sudo apt-get upgrade | |
| # Download the stable or development Chrome .deb package - dev if you want headless functionality | |
| wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb | |
| sudo dpkg -i google-chrome-stable_current_amd64.deb | |
| sudo apt -f install # probably | |
| wget https://github.com/therealkenc/libudev-stub/releases/download/v0.9.0/libudev-stub-0.9.0-WSL.deb |
| # Clone repo | |
| git clone --mirror [email protected]/fernandoaleman/app.git app/.git | |
| # Change into app directory | |
| cd app | |
| # Update git config | |
| git config --unset core.bare | |
| # Checkout master branch |
| <!-- | |
| This demo shows two ways to detect changes to a DOM node `.textContent`, one | |
| using a `MutationObserver` and the other using an ES2015 `Proxy`. | |
| From testing, a `Proxy` appears to be 6-8x faster than using a MO in Chrome 50. | |
| **Update**: removing the `Proxy` altogether speeds up the MO to be inline with the Proxy. | |
| This has something to do with how the browser queues/prioritizes Proxies over MO. |
| var 真 = true; | |
| var 假 = !真; | |
| function 如果(condation, then){ | |
| if(condation) then(); | |
| return { | |
| 否则: function(then){ | |
| if(!condation) then(); | |
| } |
| /* bling.js */ | |
| window.$ = document.querySelector.bind(document); | |
| window.$$ = document.querySelectorAll.bind(document); | |
| Node.prototype.on = window.on = function(name, fn) { this.addEventListener(name, fn); }; | |
| NodeList.prototype.__proto__ = Array.prototype; | |
| NodeList.prototype.on = function(name, fn) { this.forEach((elem) => elem.on(name, fn)); }; |
| * { | |
| font-size: 12pt; | |
| font-family: monospace; | |
| font-weight: normal; | |
| font-style: normal; | |
| text-decoration: none; | |
| color: black; | |
| cursor: default; | |
| } |
| /** | |
| * VH and VW units can cause issues on iOS devices: http://caniuse.com/#feat=viewport-units | |
| * | |
| * To overcome this, create media queries that target the width, height, and orientation of iOS devices. | |
| * It isn't optimal, but there is really no other way to solve the problem. In this example, I am fixing | |
| * the height of element `.foo` —which is a full width and height cover image. | |
| * | |
| * iOS Resolution Quick Reference: http://www.iosres.com/ | |
| */ | |
Google Chrome Developers says:
The new WOFF 2.0 Web Font compression format offers a 30% average gain over WOFF 1.0 (up to 50%+ in some cases). WOFF 2.0 is available since Chrome 36 and Opera 23.
Some examples of file size differences: WOFF vs. WOFF2
A painfully obsessive cheat sheet to favicon sizes/types. Compiled from: