-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vceenc 7.0 is the last version working on my computer, the later ones stop while encoding. #62
Comments
I'm having no problem with RX460 or RX5500XT with 22.7.1 driver. Would you please let me know which graphics driver you are having problem with? |
i have release 22.8.2 of graphics driver |
Thanks, also tried 22.8.2 driver with RX5500XT at Win11 but worked fine at my side. Would you please provide result of below to give further information?
|
VCEEnc (x64) 7.00 (r1066) by rigaya, Apr 30 2022 18:34:01 (VC 1931/Win)
OpenCL platform #0 [0x0000020246B38350] thank you for help |
Thank you for the information. I think the information are detected fine in this case, it's hard to find out what is causing the issue. Would you please also share the output with VCEEnc 7.08 (or the one it crushes)? (I'm sorry I didn't mention about this.)
That might give us the hint where and why the current version crushes. |
VCEEnc (x64) 7.08 (r1175) by rigaya, Aug 25 2022 13:14:12 (VC 1933/Win)
OpenCL platform #0 [0x000001DA4DCA2E90]
device #0: AMD Radeon H.264/AVC input: H.264/AVC output: H.265/HEVC encode features H.265/HEVC input: H.265/HEVC output: device #0: AMD Radeon H.264/AVC output: H.265/HEVC decode features H.265/HEVC output: MPEG2 decode features MPEG2 output: VP9 decode features VP9 output: VC-1 decode features VC-1 output: yes, crush without error messages |
Thanks you very much. Seems like that GPU is detected fine, OpenCL is detected fine, and VCE/VCN features are also detected fine. It's weird that encoding crushes without any error messages even with "--log-level debug", difficult to know what is happening... Would you please let me know the exact command line you're giving when encoding? |
yesterday i used version 7.08 and i was able to encode a 4k 10bit h265 movie without any problem. I hope I have solved it, if that happens I will post the log here with the debug option, but it is a very, very large file. |
my friend yesterday vceenc version 7.08 stopped 3 times on three different films, as per your request this is the log file with log level debug. |
Dear Rigaya, Here is the report |
Thank you for the report. I'm still not sure what is causing the problem, as 7.01 includes many changes from 7.00, including changes in OpenCL filtering (d9e005c) and HEVC bitstream filter (c88b1bf). It is possible that the problem is caused by HEVC hw decode, in that case it would be possible to avoid the error by using --avsw (but might be slow...) |
I just did an encoding with the --avsw option and version 7.08 |
…定性改善を図る変更。( #62 ) VCEEnc 7.01以降、エンコードが途中で黙って異常終了するという報告があった。 d9e005c でcl_khr_image2d_from_bufferがサポートされないとき、一度確保したimageを使いまわすように変更したが、 このときcl_khr_image2d_from_bufferがサポートされる場合に、bufferから作成したimageの解放タイミングが後ろにずれてしまっており、 これが不安定性の一因ではないかと思われるため、元に戻す。 7.00まで & 今回の変更後 1. image from buffer の作成 2. kernel処理の発行 3. image from buffer の解放指示 4. エンコーダ投入前の同期 -- 次のフレームの処理 -- 5. 前段処理からbufferにデータ書き込み指示 1. に戻る d9e005c の変更後 (7.01-7.08) 1. image from buffer の作成 2. kernel処理の発行 3. エンコーダ投入前の同期 -- 次のフレームの処理 -- 4. 前段処理からbufferにデータ書き込み指示 5. image from buffer の解放指示 <<<< 後ろにずれている 1. に戻る
VCEEnc 7.09 effectively moves back OpenCL related change made in VCEEnc 7.01, which might be the cause of the problem. Would you please have a try with this? |
Domo origato!
|
thank you very much, you are the best, with version 7.09 all work fine |
@alex-cccip and @swadomlic Thank you for your information and cooperation to debugging this problem with your reports, I'm glad to hear that the problem is gone! |
Hello,
i have AMD Ryzen 7 Pro 4750G and vceenc 7.00 is the last version working on my computer, the later ones stop while encoding without error messages.
The text was updated successfully, but these errors were encountered: