Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
24th April 2023, 15:51 | #41 | Link | |
Lost my old account :(
Join Date: Jul 2017
Posts: 322
|
Quote:
I encode at work on a CPU comparable to the 5975WX (32C threadripper), at preset veryslow it gets about 1-1,5fps, and I can do two simultaneously at about 1fps. But even professionally, for production I never go below slower, there just isnt any ROI at that point, and have up to this point yet encountered anyone using something like x265 placebo in production environments, thats just bad business as there are so much diminishing returns at that point. Even if we had hw were the raw throughput was usable, i doubt I would even go to veryslow, slower does indeed already use most of the potential in the encoder. At that point most gains comes from content and compression level specific tuning. Last edited by excellentswordfight; 24th April 2023 at 16:30. |
|
24th April 2023, 20:06 | #42 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
You're absolutely right that most of the quality improvements beyond slower (and maybe beyond medium) come from content or scenario specific tuning. Last night's test encode had a 1033 character command line, 762 just of parameters excluding paths and file names. |
|
26th April 2023, 22:41 | #43 | Link |
Registered User
Join Date: Oct 2003
Posts: 157
|
I tried x265 (official build) with DEE for Dolby Vision Profile 7 encoding (FEL). I used a Ryzen 3990X (64 cores). That's terribly slow: something like 1 hour for a 5 seconds footage. The CPU usage never exceeded 30%. I couldn't test with znver2 because it doesn't seem to be included in the parameters.
|
Thread Tools | Search this Thread |
Display Modes | |
|
|