[HEVC] x265.EXE: mingw builds

[vhelp]

ok, success. i found the latest update rev693, file L-SMASH-Works_r693.7z

avisynth script preporation for opening videos (including hevc encoded) using l-smash

  v = "g:\zzzbinst.hevc"
  LoadPlugin( "C:\PLUGINS\LSMASHSource.dll" )
  LWLibavVideoSource(v, cache=true , seek_mode=0 )#.selectevery(2,0) # <-- some videos need this.

haah. i beat el heggunte to it!!

[Selur]

Congratulation, btw. I mentioned that it worked for me with L-SMASH-Works rev 693 thirty+ posts ago.

[vhelp]

yes, you did. but i also saw similar postings like that a week ago or so but couldn't find it. today, i found it. go figure.

[Selur]

nukadoko is always posting in his blog when a new L-Smash-Works update is available (download link and rss feed is on the right side).

[x265.cc]

Another x265 0.5+397-1544cf94837d sample..

BigBuckBunny 720p

--crf 24 -w -i 240 --bframe-bias 20 --rdpenalty 1 --rd 2 --aq-mode 1 (same as LigH)

//edit:

@114.80.189.185 (or the guy who tried to download THIS ~74000 times in 3 days):

Feel free to contact me at "ddos@x265.cc" and i will tell you how a DoS/DDoS attack works,
and why a GET Flood (2 Threads / every 5 sec ) attack from a Personal ISP against an hardened nginx will fail.

btw.

iptables -A INPUT -s 114.80.189.185 -j DROP

The only thing a (real) attack can result in, is that i have to disable HTTPS (TLS1.2),
enable access logs and setup an firewalled 10 gbit reverse proxy as frontend. Anyway next
time i will consider to shoot back.

//edit2: I think he reads this thread. He changed his ip to 114.80.189.187.

iptables -A INPUT -s 114.80.0.0/12 -j DROP

I'm sorry for "CHINANET SHANGHAI" users.

[deadrats]

that ip addy originated in china, tell me that one of the x265 guys actually tried to ddos your site, LOL.

[Famille_CB]

Hello,

Developers of "MeGui" seems to be interest by the x265 project. They integrate it in there great encoder.
I will test it...
Can you tell me what do you think about this? Does it works as well as x265gui?

Regards.

[LigH.de]

The first of the two "D" in "DDoS" means "Distributed" = "from many different locations = IPs"; this is fortunately not yet the case. That is not even a simple "Denial of Service" attack attempt yet.
__

People reported an early release of the x265 test version of MeGUI crashing with the first update. I don't recommend such attempts yet, x265 is not yet "to be let loose on the public", or is it?

Well. while I am typing here, Zathor just officially released r2423. "But you need to delete the MeGUI\allprofiles\x265 folder while MeGUI is closed."
__

P.S.: A lot of patches keep arriving; will we know here when the developer team would like to have a specific state tested by many testers?

[Selur]

I don't recommend such attempts yet, x265 is not yet "to be let loose on the public", or is it?

Just released Hybrid with x265 support a few hours ago.
Would I recommend to use x265 for any more than testing purposes atm. ? -> definitely no
Do I think it's a good idea to offer users an easy way to use x265 -> yes
Would I declare x265 above the level of alpha software atm. -> definitely no

[deadrats]

yeah, number 1000!!! seriously though, is this the longest thread in videohelp history at this point?

edit: wait, the counter doesn't go up to 1000? it goes to 0 and starts over?!?

[LigH.de]

edit: wait, the counter doesn't go up to 1000? it goes to 0 and starts over?!?

This is called AJAX; refresh the page.

[x265.cc]

The first of the two "D" in "DDoS" means "Distributed" = "from many different locations = IPs"; this is fortunately not yet the case. That is not even a simple "Denial of Service" attack attempt yet.

It's a bad try (kiddie style) of HTTP GET flooding / bandwidth wasting so it could never lead to an denial of (http) service, correct.

I don't recommend such attempts yet, x265 is not yet "to be let loose on the public", or is it?

Just released Hybrid with x265 support a few hours ago.

[Baldrick]

When should I add x265 to the tools list? And what link should I use? I want windows builds...not just source code.

[LigH.de]

Not before v0.9

[deadrats]

@x265.cc

is that a gui you have available for testing? if so were is the download?

[Selur]

When should I add x265 to the tools list?

personally I would say: wait a bit more

And what link should I use?

x265.cc seems to be the most reliable source atm.

[Selur]

@deadrats: https://bitbucket.org/ozok/x265gui/downloads

[x265.cc]

I want windows builds...not just source code.

Currently builds x265 8/16bpp with MinGW (x86) and VC12 (x86 / x86-64).
Newer VC12 builds will be build static, older builds may need VC redist.

https://x265.cc/

jfyi, the current file paths are fixed and will not be changed. (except for vc13 rtm)

is that a gui you have available for testing?

not yet. If there are "too much" or an "perfect" gui(s), i will never release it.

@deadrats: https://bitbucket.org/ozok/x265gui/downloads

nope "x265.cc UI" != "x265GUI"

[alom]

You guys are making those GUIs to work with 64bit versions of x265, right? Since you know it's 2013 ;-p
...and speed increase really matters in this case, and anybody who will be doing any serious HEVC encoding will have PC running 64bit system. right?

[ozok]

I haven't looked at x265 and x265GUI in ages. Is the GUI working well with new releases of x265? Should I update/add/remove/change anything in the GUI?

[El Heggunte]

yeah, number 1000!!! seriously though, is this the longest thread in videohelp history at this point?

Of course it isn't; OR, perhaps, it depends on what you mean by "at this point"

https://forum.videohelp.com/threads/108004-Word-Association

deadrats
Join Date: 29th Nov 2005

[hiritsuki]

Hi , I get error crash in 0.5+414-1449a1a2041f
and it's random...

[El Heggunte]

Hi , I get error crash in 0.5+414-1449a1a2041f
and it's random...

Please, define the exact command-lines(s) you have tried, PLUS the details of your sources (width, height, fps, frame count), and also, what type of executable (8bpp, 16bpp, VC build, GCC build, 32-bits, 64-bits), Windows 8 or not-Windows-8, ...
Yes, all these and those details do matter.

[hiritsuki]

Windows Server 2012 R2
I used VC12 64-bits 8bpp on x265.cc

Source 43154frame

VideoID                                       : 320 (0x140)
Menu ID                                  : 211 (0xD3)
Format                                   : MPEG Video
Format version                           : Version 2
Format profile                           : Main@High
Format settings, BVOP                    : Yes
Format settings, Matrix                  : Custom
Format settings, GOP                     : M=3, N=15
Codec ID                                 : 2
Duration                                 : 30mn 0s
Bit rate mode                            : Variable
Bit rate                                 : 17.5 Mbps
Maximum bit rate                         : 24.0 Mbps
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 29.970 fps
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Interlaced
Scan order                               : Top Field First
Compression mode                         : Lossy
Bits/(Pixel*Frame)                       : 0.282
Time code of first frame                 : 19:29:27:09
Time code source                         : Group of pictures header
Stream size                              : 3.67 GiB (94%)
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709

command-line is

avs2yuv "リトルバスターズ！～Refrain～　第１話[新]-20131007.avs" -raw - | x265 --input - --input-res 1920x1080 --fps 30000/1001 --no-sao -q 20 --output "リトルバスターズ！～Refrain～　第１話[新]-20131007.h265"

and avs script is

LoadPlugin("C:\Program Files (x86)\MeGUI\tools\dgindex\DGDecode.dll")
Load_Stdcall_Plugin("C:\Program Files (x86)\MeGUI\tools\yadif\yadif.dll")
DGDecode_mpeg2source("G:\BSD\2013-10\リトルバスターズ！～Refrain～\リトルバスターズ！～Refrain～　第１話[新]-20131007.d2v").sorathread().Yadif(mode=1,order=1).sorathread().SelectEven
__film = last
__t0 = __film.trim(693, 6625)
__t1 = __film.trim(8425, 22030)
__t2 = __film.trim(23830, 46845)
__t3 = __film.trim(48645, 49242)
__t0 ++ __t1 ++ __t2 ++ __t3

[El Heggunte]

Hmmm.... I can be wrong, but I think you shouldn't be using *non-ASCII* or Unicode filenames in Avisynth
Maybe that's not a problem for the "latest and greatest" version of Avisynth, but it could be a problem for the version of avs2yuv you have
Anyway, we still don't know what was the error message you were talking about...

[hiritsuki]

I used Windows System Lang in Japanese , non-ASCII is no problem.avs2yuv is latest version.
I don't know why it's error too ... older version x265 is fine.

3days ago x265 is fine.

[x265.cc]

You guys are making those GUIs to work with 64bit versions of x265, right? Since you know it's 2013 ;-p
...and speed increase really matters in this case, and anybody who will be doing any serious HEVC encoding will have PC running 64bit system. right?

my "x265.cc UI project" will mainly target current (Windows 7/8/8.1 | Server 2012 / 2012 R2) 64 Bit systems with AVX capable cpus. So the main version will be bundled (if ever released) with the "8bpp x64 VC12" build.

Should I update/add/remove/change anything in the GUI?

Remove the 3rd party components (jedi vcl, etc.) and i will join or fork it

Hi , I get error crash in 0.5+414-1449a1a2041f
and it's random...

Currently encoding an 1080p file with this version since ~16 hours, no errors yet. (ffmpeg input > x265)

[hiritsuki]

Well ... what happened

問題の署名:
  問題イベント名:    BEX64
  アプリケーション名:    x265.exe
  アプリケーションのバージョン:    0.0.0.0
  アプリケーションのタイムスタンプ:    528c0dd4
  障害モジュールの名前:    MSVCR120.dll
  障害モジュールのバージョン:    12.0.21005.1
  障害モジュールのタイムスタンプ:    524f83ff
  例外オフセット:    0000000000074a30
  例外コード:    c0000409
  例外データ:    0000000000000007
  OS バージョン:    6.3.9600.2.0.0.400.8
  ロケール ID:    1041
  追加情報 1:    b4e2
  追加情報 2:    b4e20d17b7c789d049b007418a7f5680
  追加情報 3:    317b
  追加情報 4:    317b62db11e40d3658f976280f5add40


オンラインのプライバシーに関する声明をお読みください:
  http://go.microsoft.com/fwlink/?linkid=280262


オンラインのプライバシーに関する声明が利用できない場合は、プライバシーに関する声明をオフラインでお読みください:
  C:\Windows\system32\ja-JP\erofflps.txt

[Selur]

You guys are making those GUIs to work with 64bit versions of x265, right?

The GUIs all only call a binary and don't care whether it's a 64bit or 32bit binary. -> no special 64bit optimization required

Hi , I get error crash in 0.5+414-1449a1a2041f
and it's random...

Looking at your avs script -> have you tried without 'sorathread()' ?

[alom]

You guys are making those GUIs to work with 64bit versions of x265, right?

The GUIs all only call a binary and don't care whether it's a 64bit or 32bit binary. -> no special 64bit optimization required

well I might not be an expert here, but for example I'm using StaxRip which uses avisynth or some other input methods and pipes it to x264 binary, and if you switched to binary to 64bit it didn't work.
(there is a workaround where you place "fake" (32bit) x264.exe instead that in turn pipes it to real x264_64.exe)

I'm guessing you need 64bit version of avisynth or ffmpeg in order to pipe it to 64bit x265? At least this is what I'm doing right now