h.265 / HEVC

[mean]

Thanks, i"ll give it a whirl asap

[sl1pkn07]

@KoolAidMan your branch fail build

(x265 qt4 plugin)

Code Select Expand


[ 13%] Building CXX object ADM_videoEncoder/x265/CMakeFiles/ADM_ve_x265_qt4.dir/ADM_x265Setup.cpp.o
/home/sl1pkn07/aplicaciones/avidemux-2.6-git/src/avidemux/avidemux_plugins/ADM_videoEncoder/x265/ADM_x265Setup.cpp: In function 'void dumpx265Setup(x265_param*)':
/home/sl1pkn07/aplicaciones/avidemux-2.6-git/src/avidemux/avidemux_plugins/ADM_videoEncoder/x265/ADM_x265Setup.cpp:356:8: error: 'x265_param' has no member named 'saoLcuBoundary'
     PI(saoLcuBoundary);
        ^
/home/sl1pkn07/aplicaciones/avidemux-2.6-git/src/avidemux/avidemux_plugins/ADM_videoEncoder/x265/ADM_x265Setup.cpp:262:46: note: in definition of macro 'PI'
#define PI(x) printf(#x"\t:%d\n",(int)param->x)
                                              ^
/home/sl1pkn07/aplicaciones/avidemux-2.6-git/src/avidemux/avidemux_plugins/ADM_videoEncoder/x265/ADM_x265Setup.cpp:357:8: error: 'x265_param' has no member named 'saoLcuBasedOptimization'
     PI(saoLcuBasedOptimization);
        ^
/home/sl1pkn07/aplicaciones/avidemux-2.6-git/src/avidemux/avidemux_plugins/ADM_videoEncoder/x265/ADM_x265Setup.cpp:262:46: note: in definition of macro 'PI'
#define PI(x) printf(#x"\t:%d\n",(int)param->x)
                                              ^
ADM_videoEncoder/x265/CMakeFiles/ADM_ve_x265_qt4.dir/build.make:113: recipe for target 'ADM_videoEncoder/x265/CMakeFiles/ADM_ve_x265_qt4.dir/ADM_x265Setup.cpp.o' failed
make[2]: *** [ADM_videoEncoder/x265/CMakeFiles/ADM_ve_x265_qt4.dir/ADM_x265Setup.cpp.o] Error 1
CMakeFiles/Makefile2:146: recipe for target 'ADM_videoEncoder/x265/CMakeFiles/ADM_ve_x265_qt4.dir/all' failed
make[1]: *** [ADM_videoEncoder/x265/CMakeFiles/ADM_ve_x265_qt4.dir/all] Error 2
Makefile:120: recipe for target 'all' failed
make: *** [all] Error 2


[sl1pkn07]

i use x265 1.4

https://bitbucket.org/multicoreware/x265/get/1.4.tar.bz2

greetings

[sl1pkn07]

offtopic:

if you can fix the multithread compilation.....

if use more than 1 core, the build crash

EDIT: yes. now build OK

[Nik]

any news about the version feat. x265?
(is there any windows x32/x64 build I can download?)

[Jan Gruuthuse]

You might try this one: avidemux_r041214_1043_win64.7z 16.2 MB Dec 4 2014 8:02 PM 64-bit only.

[Nik]

thanks

[Nik]

hmm, something's missing though ^^;
(the x265, and if I understand it right, it was fixed after 14th of Dec)

[Jan Gruuthuse]

No, it was fixed on 2014-12-14T16:34:32Z
patch provided by KoolAidMan and tested
build with commit ca38492

No longer having any experience with windows: could be you need to install HEVC / x265 ? Don't know if you're required to build from source yourself or if codec is available for installation?
http://www.videolan.org/developers/x265.html

[Nik]

I thought the dlls are included in the avidemux builds?
the newest build in the folder (x64 branch) you named is from Dec 4th
(at least I don't see any dll that looks like x265 and there's also no x265 mentioned in help->plugins)
hmm

[Jan Gruuthuse]

I'm very sorry, no idea how that could happen: that I overlooked the 1 not being in the release date avidemux_r041214_1043_win64.7z. It is indeed from 4th of December and not 14 December as I did announce. So as it looks this feature is currently only available in self builds from the latest source.
Hope mean can still provide this build for window, time permitting.

My apologies for my mistake . Never the less, still happy a New year.

[Nik]

don't worry, Jan, that's no problem
and the x265 part is still very new so I guess there'll be builds containing it in the future

but I want to take the chance and ask this here:
I only used the builds in x32 folder (and x64, but IIRC the x32 builds had more features in the past so I used these instead).
are there any important differences in self builds compared to the builds in the x32/x64 folders?
I only  have visual studio installed and I guess I need something else to compile self builds, right? that currently is no option for me because I don't really know what I (have to) do

The Dec 4th build indeed is a little faster than avidemux x32 build from Oct 19th. Though it's only around 2 fps

Happy New Year

[KoolAidMan]

Hi Nik. The December 4th build is based on the 2.4 branch of ffmpeg, while the builds prior are based on ffmpeg 1.2. Any performance enhancements probably come from there.

As for HEVC support on windows, currently there is no cross compile script for the x265 library included, so a dll is not being built for the x265 library.

[Nik]

hey KAM
so I can't just use a x265 dll which I copied into the avidemux folder? (didn't try that yet)

yeah, I've read about the ffmpeg speedup

[Jan Gruuthuse]

Bot did build a newer release: 2015/01/15: for windows 64-bit: http://avidemux.org/smuf/index.php?action=post;topic=16247.15;last_msg=71596