x265 HEVC Encoder - Page 2

Kurtnoise · 1st October 2013, 09:56

Quote:

Originally Posted by LigH

That won't make much sense without specific testing parameters.

Looking at the graph, you will see the parameters used : x264 -placebo + no-psy vs x265 defaults

professor_desty_nova · 1st October 2013, 10:21

Maybe in a few weeks/months, when x265 has Weight P and Weight B working and more stuff borrowed from x264 (look at their TODO list), it will be more "fair" to compare...

mandarinka · 1st October 2013, 19:03

I don't think those are specifically the problem. It's probably the rate control that is most important.

LigH · 2nd October 2013, 08:28

@ Kurtnoise:

I thought zerowalker asked for any comparison screenshots, not specifically from the test above. That's why I continued thinking about its general sense in the current stage of development...

Apart from other working features, there is also some need for useful default values. From my experience so far, a default quantizer of 32 in x265 is not really a sensible value.

BadFrame · 2nd October 2013, 08:50

Really love how development has picked up on the x265 project, I'm getting some good 'x264 vibes'

Is there a tool to decode the x265 generated raw hevc stream to another format at the moment?

LigH · 2nd October 2013, 09:17

The Osmo4 player in the GPAC Nightly Builds (Win32) can play it (muxed as MP4 with e.g. MP4Box in this package, or a current L-SMASH).

The HM reference decoder (ver. 12.0 currently?) can decode it to Y4M. JEEB's build (TAppDecoder.exe).

BadFrame · 2nd October 2013, 09:27

Thanks LigH!

Kurtnoise · 2nd October 2013, 22:22

Wanna play with avisynth & libx265 on windows platforms ?

I've made a fresh compile of avconv from libav + patches from Daemon404...

Not all options from x265 cli are available yet but it's a good start.

Kurtnoise · 3rd October 2013, 07:37

Maybe...when hevc support in matroska (i.e in Mosu's mkvtoolnix, not Rovi) will be officially supported.

nakTT · 14th October 2013, 08:47

Quote:

Originally Posted by lainiwaku

is it hard to use command line version ? i always used MeGui for x264

Same here. I hope some GUI like MeGUI etc could integrate this encoder. I would love to do testing with this new encoder.

Selur · 14th October 2013, 13:24

gui support in MeGui and other tools will probably not come unless input via std::in is supported.
Most GUIs won't support tools which require huge temporary files as input.

LigH · 14th October 2013, 13:53

Apart from that, x265 is not yet available for users, only for testers with sound background knowledge in video coding algorithms, and working with CLI encoders (at least by editing a batch file) is the least issue in the current stage of development.

There is no complete feature implementation yet.
There is no stabe set of command line options yet.
How often do you expect a GUI to follow sudden and unexpected changes in the set of encoder options?

And yes: There is not even support for streaming video sources (pipe / AviSynth) yet. GUIs could not efficiently serve frames to such an encoder.

nekrosoft13 · 14th October 2013, 17:32

anyone could share a sample file encoded in x265?

JEEB · 14th October 2013, 17:48

Quote:

Originally Posted by nekrosoft13

anyone could share a sample file encoded in x265?

Daemon404's test encodes are available in the directory.

filler56789 · 14th October 2013, 18:15

Quote:

Originally Posted by nekrosoft13

anyone could share a sample file encoded in x265?

This thread @ Videohelp has various sample videos:

http://forum.videohelp.com/threads/357754-%5BHEVC%5D-x265-EXE-mingw-builds

LigH · 15th October 2013, 08:30

Here are also a few of mine.

Also there are some new builds, compiled with MSys/MinGW GCC for x86 or with MSVC11 for x86 and AMD64 (latter may have a minimum requirement of Windows 7 and the MSVC 2012 Redistributable; a CPU with AVX support and 8 GB RAM are reommended): https://x265.cc/

Kurtnoise · 15th October 2013, 10:48

Quote:

Originally Posted by LigH

Also there are some new builds, compiled with MSys/MinGW GCC for x86 or with MSVC11 for x86 and AMD64 (latter may have a minimum requirement of Windows 7 and the MSVC 2012 Redistributable; a CPU with AVX support and 8 GB RAM are reommended): https://x265.cc/

who has created this buildbot ? It's from official devs ?

For MSVC builds, it's quite easy to support XP platforms and remove the c++ runtime.

I'll create a patch if needed.

LigH · 15th October 2013, 10:56

The user registered with the nick "x265.cc" in the VideoHelp forum; I don't know if he is related to the development team.

16th October 2013, 00:10

Quote:

Originally Posted by LigH

The user registered with the nick "x265.cc" in the VideoHelp forum; I don't know if he is related to the development team.

He is not.

Tom
MulticoreWare

Kurtnoise · 16th October 2013, 05:48

Here is the patch:

Code:

# HG changeset patch
# User Kurtnoise <kurtnoise@free.fr>
# Date 1381898006 -7200
#      Wed Oct 16 06:33:26 2013 +0200
# Node ID 723e554191e14e6289342043225e485e656c27d7
# Parent  a998daed845922b3b880b48c0cafa32c422c941e
Add Windows XP support in MSVC11 builds. This requires CMake 2.8.11 or later.

diff -r a998daed8459 -r 723e554191e1 build/vc11-x86/make-solutions.bat
--- a/build/vc11-x86/make-solutions.bat	Tue Oct 15 20:57:47 2013 -0500
+++ b/build/vc11-x86/make-solutions.bat	Wed Oct 16 06:33:26 2013 +0200
@@ -3,4 +3,4 @@
 :: run this batch file to create a Visual Studion solution file for this project.
 :: See the cmake documentation for other generator targets
 ::
-cmake -G "Visual Studio 11" ..\..\source && cmake-gui ..\..\source
+cmake -G "Visual Studio 11" -T "v110_xp" ..\..\source && cmake-gui ..\..\source
diff -r a998daed8459 -r 723e554191e1 build/vc11-x86_64/make-solutions.bat
--- a/build/vc11-x86_64/make-solutions.bat	Tue Oct 15 20:57:47 2013 -0500
+++ b/build/vc11-x86_64/make-solutions.bat	Wed Oct 16 06:33:26 2013 +0200
@@ -3,4 +3,4 @@
 :: run this batch file to create a Visual Studion solution file for this project.
 :: See the cmake documentation for other generator targets
 ::
-cmake -G "Visual Studio 11 Win64" ..\..\source && cmake-gui ..\..\source
+cmake -G "Visual Studio 11 Win64" -T "v110_xp" ..\..\source && cmake-gui ..\..\source
diff -r a998daed8459 -r 723e554191e1 source/CMakeLists.txt
--- a/source/CMakeLists.txt	Tue Oct 15 20:57:47 2013 -0500
+++ b/source/CMakeLists.txt	Wed Oct 16 06:33:26 2013 +0200
@@ -7,7 +7,7 @@
 endif()
 
 project (x265)
-cmake_minimum_required (VERSION 2.8.8) # OBJECT libraries require 2.8.8
+cmake_minimum_required (VERSION 2.8.11) # OBJECT libraries require 2.8.11
 
 # X265_BUILD must be incremented each time the public API is changed
 set(X265_BUILD 1)

XP platforms require v110_xp as toolset instead of v110. Otherwise, applications don't run correctly on this platform.

This patch requires CMake 2.8.11 because the flag dedicated to the toolset has been fixed in this version.

2nd October 2013, 08:28	#24 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 7,095	@ Kurtnoise: I thought zerowalker asked for any comparison screenshots, not specifically from the test above. That's why I continued thinking about its general sense in the current stage of development... Apart from other working features, there is also some need for useful default values. From my experience so far, a default quantizer of 32 in x265 is not really a sensible value. __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

2nd October 2013, 09:17	#26 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 7,095	The Osmo4 player in the GPAC Nightly Builds (Win32) can play it (muxed as MP4 with e.g. MP4Box in this package, or a current L-SMASH). The HM reference decoder (ver. 12.0 currently?) can decode it to Y4M. JEEB's build (TAppDecoder.exe). __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid Last edited by LigH; 2nd October 2013 at 09:21.

14th October 2013, 13:24	#31 \| Link
Selur Registered User Join Date: Oct 2001 Location: Germany Posts: 7,431	gui support in MeGui and other tools will probably not come unless input via std::in is supported. Most GUIs won't support tools which require huge temporary files as input. __________________ Hybrid here in the forum, homepage

14th October 2013, 13:53	#32 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 7,095	Apart from that, x265 is not yet available for users, only for testers with sound background knowledge in video coding algorithms, and working with CLI encoders (at least by editing a batch file) is the least issue in the current stage of development. There is no complete feature implementation yet. There is no stabe set of command line options yet. How often do you expect a GUI to follow sudden and unexpected changes in the set of encoder options? And yes: There is not even support for streaming video sources (pipe / AviSynth) yet. GUIs could not efficiently serve frames to such an encoder. __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

15th October 2013, 08:30	#36 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 7,095	Here are also a few of mine. Also there are some new builds, compiled with MSys/MinGW GCC for x86 or with MSVC11 for x86 and AMD64 (latter may have a minimum requirement of Windows 7 and the MSVC 2012 Redistributable; a CPU with AVX support and 8 GB RAM are reommended): https://x265.cc/ __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid Last edited by LigH; 15th October 2013 at 10:13.

1st October 2013, 10:21	#22 \| Link
professor_desty_nova Registered User Join Date: Nov 2006 Posts: 55	Maybe in a few weeks/months, when x265 has Weight P and Weight B working and more stuff borrowed from x264 (look at their TODO list), it will be more "fair" to compare...

1st October 2013, 19:03	#23 \| Link
mandarinka Registered User Join Date: Jan 2007 Posts: 729	I don't think those are specifically the problem. It's probably the rate control that is most important.

2nd October 2013, 08:50	#25 \| Link
BadFrame Registered User Join Date: Jun 2013 Posts: 98	Really love how development has picked up on the x265 project, I'm getting some good 'x264 vibes' Is there a tool to decode the x265 generated raw hevc stream to another format at the moment?

2nd October 2013, 09:27	#27 \| Link
BadFrame Registered User Join Date: Jun 2013 Posts: 98	Thanks LigH!

2nd October 2013, 22:22	#28 \| Link
Kurtnoise Swallowed in the Sea Join Date: Oct 2002 Location: Aix-en-Provence, France Posts: 5,191	Wanna play with avisynth & libx265 on windows platforms ? I've made a fresh compile of avconv from libav + patches from Daemon404... Not all options from x265 cli are available yet but it's a good start.

3rd October 2013, 07:37	#29 \| Link
Kurtnoise Swallowed in the Sea Join Date: Oct 2002 Location: Aix-en-Provence, France Posts: 5,191	Maybe...when hevc support in matroska (i.e in Mosu's mkvtoolnix, not Rovi) will be officially supported.

14th October 2013, 17:32	#33 \| Link
nekrosoft13 Registered User Join Date: Jun 2003 Location: Chicagoland or Poland Posts: 193	anyone could share a sample file encoded in x265?

15th October 2013, 10:56	#38 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 7,095	The user registered with the nick "x265.cc" in the VideoHelp forum; I don't know if he is related to the development team. __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode