x265 - Work already started?

[filler56789]

well, what else can I suggest? half a year has passed and x265 has no such basic feature as pipe support, so obviously it's infinitely hard to implement :D

Overdue update: 7.4 months have passed since their "zeroth" commit:

Steve Borho 09fe406 commit JCT-VC HM source with cmake based build scripts 2013-03-07

( currently at the bottom of the page:
https://bitbucket.org/multicoreware/x265/commits/all?page=152 )

[benwaggoner]

Overdue update: 7.4 months have passed since their "zeroth" commit:
They are cranking HARD on improving image quality, and there's tons of x264 features to port over. I'd expect that "utility" features like this aren't going to get a lot of attention for a while yet.

[MoSal]

@filler56789

Note: I didn't test x265 myself yet.

You can have pipe support with all applications at a higher level if the application does not seek.

In *nix for example, you can use process substitution which is a feature provided by shells:


# Substitute dump_command with any command that outputs to stdout
x265 -o outfile <(dump_command)


If the application is dumb enough to rely on file extensions, you can use named pipes (FIFOs):


mkfifo dump.yuv
x265 -o outfile dump.yuv


On a 2nd shell:
dump_command > dump.yuv

However, If seeking is used on input files, neither this nor LoRd_MuldeR's patch will work.

[LigH]

Both may not be helpful for Windows users...

Well, it is for testers. Testers are expected to have some "pioneer attitude". ;)

A few short "standard trailers" (e.g. Blender movies) will be fine for first experiences. Some of these are even downloadable as Y4M, I believe?