In data domenica 30 marzo 2014 21:13:43, Mario *LigH* Rohkrämer ha scritto:
While all other people replying to a previous
mail can be sorted so that you can see who replied to whom, your mails
appear to start a new, unrelated thread.
Are you sure? Because I see his answer as part of the
In data mercoledì 5 marzo 2014 11:38:41, Steve Borho ha scritto:
I'd like to understand the steps you took to encode 10bit video
I simply misunderstood the 16bpp flag: it doesn't enable high bit depth but
only 16 bit variables.
Niccolò
--
www.linuxsystems.it
http://www.linuxsystems.it/2014/03/new-screenshots-comparator-loads-new-x264-x265-vp8-vp9-tests/
Congratulations to the x265 team: at low bitrates x265 completely CRUSH x264
if you use a very high quality source like the Blu-ray of “The Hobbit: An
Unexpected Journey”.
Hopefully in the future it
In data lunedì 24 febbraio 2014 19:18:26, Steve Borho ha scritto:
On the tip, the VUI and timing info
are now optional, you have to pass the --timinginfo flag to enable
them.
I tried --timinginfo but it does not work :(
I'm using 0.7+259-5e2043f89aa1
Niccolò
--
www.linuxsystems.it
Hi,
I encode my videos with
ffmpeg -v 0 -i ~/PlanetEarthBirds.mkv -threads 4 -vsync 0 -an -pix_fmt yuv420p
-f yuv4mpegpipe - | ./x265 - --y4m --preset placebo --crf 28 -o prova.h265
The source is 23.98 fps but the encoded video shows 25 fps instead:
Stream #0:0: Video: hevc (Main),
Il 25/02/2014 02:18, Steve Borho ha scritto:
We should probably make timing info default to enabled.
Agree, at least to be consistent with the x264 behaviour (which is what
your users will expect).
Niccolò
--
http://www.linuxsystems.it
___
Hi,
I did a quick x264 vs x265 comparison in my blog, hopefully someone
will be intersted watching it:
http://www.linuxsystems.it/2014/02/washed-video-x264-vs-x265-placebo-comparison/
Cheers,
Niccolò
___
x265-devel mailing list
In data domenica 23 febbraio 2014 14:22:01, Tom Vaughan ha scritto:
Does the MKV contain video that was ripped straight from the Blu-ray
Disc?
The video in the MKV is only 14 Mbps... I would have expected a
higher bit
rate (and more detail) if this was not re-encoded. It would be best
to
