Skip to content

Instantly share code, notes, and snippets.

关于H264, 通用的5个进阶文档为

  • [H.264_MPEG-4 Part 10 White Paper]
  • [Video coding using the H.264 MPEG-4 AVC compression standard]
  • [H.264 and MPEG-4 video compression]
  • [Overview of the H.264_AVC Video Coding Standard]
  • [Overview and Introduction to the Fidelity Range Extensions]

分三个阶段学习

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocksConfig version="1">
<editor>
<colour_sets>
<ACTIVE_COLOUR_SET>
<str>
<![CDATA[modnokai night shift v2]]>
</str>
</ACTIVE_COLOUR_SET>
<ACTIVE_LANG>
@branneman
branneman / better-nodejs-require-paths.md
Last active February 3, 2026 09:31
Better local require() paths for Node.js

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

@pguillory
pguillory / gist:729616
Created December 5, 2010 23:51
Hooking into Node.js stdout
var util = require('util')
function hook_stdout(callback) {
var old_write = process.stdout.write
process.stdout.write = (function(write) {
return function(string, encoding, fd) {
write.apply(process.stdout, arguments)
callback(string, encoding, fd)
}