Quote:
An interesting observation I have made with encoding x265 4K. Encoding with a lower CRF takes more time. CRF 21 is a little slower than CRF 22 and CRF 20 is significantly slower.
I would have thought that if you wanted a better quality and use less compression, it should be faster to encode but it is the opposite. So, it is interesting on how to decide which CRF to use. Not only it depends on the quality you want, you have to consider how slow the encoding will be. I'm thinking that for me 4K CRF 20 is a no go for me. Too slow.
|
here is a benchmark:
https://forum.doom9.org/showthread.php?t=180438
Quote:
|
In 2.1.0.5 beta, Tools > Folders > Templates menu tries to open a wrong folder, TemplatesV2.
|
Will be fixed in the next build.
Quote:
In PowerShell, it fails with this error message:
On the other hand, it does not produce any error but encodes the file successfully in the Command Prompt.
|
Not every command line that works in cmd works also in ps, at least not without modification, piping to x265 does not work unless you do:
Code:
cmd /s /c --% "regular command line between this quotes"
https://docs.microsoft.com/en-us/pow...powershell-5.1
That is similar to what staxrip does, calling cmd /s /c "" with the dotnet Process class with shellex disabled, it uses CreateProcess in Win32.
I think it was quot27 who gave me this clue.
In the next build there are some terminal related improvements:
https://github.com/staxrip/staxrip/b...r/Changelog.md