When using using hevc, and clicking on the profile ... button, and selecting a tune, such as animation, the DE Client just keeps starting the servers over and over with no progress. Changing it back to default (removes the --tune option) allows it to work again.

I've had the same error occur as Ryushin, and only when DE is active. Single machine processing, no problem.

Adding to this, another problem only in DE mode is, anytime I attempt to de-noise with KNLMeansCL (any mode, including adaptive), the encoding on remote servers stalls. All remote servers (two of them) have dedicated GPUs, and both show OpenCL to be active. I've installed all the Visual C++ runtimes via a repack from repacks.net. De-noising with only MDegrain2 works perfectly in DE mode, if it matters.

What's the proper way to add an Avisynth plugin? I'm trying to use AutoAdjust from LaTo at: https://forum.doom9.org/showthread.php?t=167573 . I've manually loaded the .dll in the script, and it shows to be shared when looking at the .avs in the chunks directory, yet encoding fails. I've tried both the 32 and 64 bit versions.

What's the proper way to add an Avisynth plugin? I'm trying to use AutoAdjust from LaTo at: https://forum.doom9.org/showthread.php?t=167573 . I've manually loaded the .dll in the script, and it shows to be shared when looking at the .avs in the chunks directory, yet encoding fails. I've tried both the 32 and 64 bit versions.

@byteshare:
Three z270, 7700k, 64gb ram, 2tb 970 Evo, vega64 with Win10pro 17763.292 (at home)
Two x470, 2700x, 64gb, 1tb 960 Evo, RX550 with Win10pro 17134.xxx (at work)
Only ms defender as av.
Issue with each of them. One z270 has a fresh reinstall today (17763.107 iso + Cu292) + drivers.
Does not happen with an old local install of RB1.23.

Hmm, I can't think of what is common between both of your machines, and what is different about my 4 boxes that I'm not having that issue with. Maybe Atak might have an idea.

Quote:

Originally Posted by LigH

@byteshare: It's not the HEVC standard, but the x265 encoder, which reached version 3.0.

I didn't intend to make that claim, but yes, I agree with you and thank you for mentioning that if anyone was confused by that.
I can understand HEVC/x265 being confused, as I did...since they are synonymous to me at this point.

The last few days I've had artifact issues with encoding a VC-1 blu-ray source. I must have re-encoded a dozen times with different settings trying to figure out what was wrong. Even tried handbrake to no avail. Eventually I tried a lossless h.264 encode using CRF 0 and I still had the artifacts. Googling seems to point to a decoding issue:https://forum.videohelp.com/threads/...g-in-Handbrake

So I installed XMedia Recode and I selected the DXVA decoder for VC-1 in the settings and I'm now saving it as a lossless jpeg. The preview did not show any artifacts. If it remains clean I'll use RB to encode that to x265.

Atak, I never knew of this issue with VC-1. Reading the thread says using the MS decoder solves the problem. Is it possible to implement a solution that solves the decoder problems for all VC-1 sources. Looks like ffmpeg might have just fixed this bug very recently as well.

The last few days I've had artifact issues with encoding a VC-1 blu-ray source.

So I installed XMedia Recode and I selected the DXVA decoder for VC-1 in the settings and I'm now saving it as a lossless jpeg. The preview did not show any artifacts. If it remains clean I'll use RB to encode that to x265.

Had to end up doing a lossless H.265 encode as input to RB as RB did not understand the lossless jpeg. The issue was very much the decoder.

Do not get to excited too early! Make sure that this version is frame accurate first! In other words check if chunks start from correct frame! There is good reason why I use two versions of ffms2 plugin in RipBot264.

Do not get to excited too early! Make sure that this version is frame accurate first! In other words check if chunks start from correct frame! There is good reason why I use two versions of ffms2 plugin in RipBot264.

Oh, I think I remember the other bug now about it being frame accurate. You fixed that last time I found an issue.

Other decoders are not frame accurate. Especially those using DirectShowSource interface.

Yep, 4 minutes in, corruption. So I'll revert that.

Maybe another way around this is to have an option to convert from VC-1 to h.264/5 lossless using a single machine and then encode from that. The user would have to know his source would grow much larger then the original.