View Full Version : Updating cli
cockpit
14th May 2023, 12:10
So I don't encode very often and I was going to update my x265 cli today but none of the files at http://msystem.waw.pl/x265/ worked.
After a bit of digging I found out my old file was a user generated build called "Asuna". I have no idea why I am using this file or if I even should, but for some reason it is the only file that will actually start encoding.
So my question is should I bother updating to something else? this Asuna build is from 2021.
I only encode pc game footage.
And also is there a list of preferred settings for video game footage?
Thanks.
benwaggoner
17th May 2023, 16:21
The main x265 thread includes new binaries when there are new commits. I suggest just grabbing one of those.
cockpit
20th May 2023, 22:13
Ok apparently I have had this issue before judging from my old posts. The issue is x265 doesn't natively support Avisynth, that's why I've been using this Asuna build.
Should I use FFmpeg's libx265 encoder instead or just stick with this old version?
Ok, I found new "fork" of that build so I'll just use that.
StainlessS
21st May 2023, 00:06
x265 doesn't natively support Avisynth
Patman mods usually do support AVS,
x265 with Patman mods (AVS, AQ-MODE 5, ...) :- https://github.com/jpsdr/x265/releases
Looks like you already found suitable x265, but above an alternative.
Updated tools quite often appear here::: New versions of free software used in the GUI's :- https://forum.doom9.org/showthread.php?t=184719
cockpit
21st May 2023, 10:32
Yup thanks. I also took a screenshot of the encoder working. Does anything here strike you as "wrong"? It's going on YT.
https://i.postimg.cc/rpq95Mv4/cmd-KBZPU9s6he.png
Also I use this .bat file to convert mkv to mp4 with FFmpeg. But since I updated x265 I now get this error message. Video seems to work fine still. Anything to worry about?
https://i.postimg.cc/R0zvRbRK/cmd-08y-Db3gtqb.png
Asmodian
26th May 2023, 02:52
It looks like the MP4 conversion is missing the information about the frame rate (likely related to the no timestamps error). Your source is 60 fps, but the MP4 is using ffmpeg's default of 25 fps.
cockpit
26th May 2023, 21:54
Is this something I can fix or should I just ignore it? The mp4 it makes is still 60 fps.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.