Attached tested vaapi hwaccel presets as gzip'd tar file av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
Den 26.11.2024 23:52, skrev Terje J. Hanssen:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
Video Acceleration API (VA-API) format support may vary dependent of available hardware, graphics processing units and system. https://en.wikipedia.org/wiki/Video_Acceleration_API The above presets are tested on Intel Arc A750 (DG2) GPU and the following system: inxi -CGSz System: Kernel: 6.6.59-1-longterm arch: x86_64 bits: 64 Desktop: GNOME v: 47.1 Distro: openSUSE Tumbleweed-Slowroll 20241103 CPU: Info: 12-core (8-mt/4-st) model: 12th Gen Intel Core i7-12700KF bits: 64 type: MST AMCP cache: L2: 12 MiB Speed (MHz): avg: 800 min/max: 800/4900:5000:3800 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 Graphics: Device-1: Intel DG2 [Arc A750] driver: i915 v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Display: x11 server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 2560x1440~60Hz API: OpenGL v: 4.6 vendor: intel mesa v: 24.2.7 renderer: Mesa Intel Arc A750 Graphics (DG2) API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib API: EGL Message: EGL data requires eglinfo. Check --recommends.
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware? P.S. There will not be new Appimages created at the end of this month, but will wait until December. On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders .... "Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch re-attached so you do not need to hunt them in mailthreads .... I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin <[email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
вт, 3 дек. 2024 г., 00:01 Terje J. Hanssen <[email protected]>:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem?
yes It was said it was "default to off", so I wonder if it will be available or
"on" in the upcoming rpm?
Depend on installation of onevpl-devel on buildfarm and flipping (adding) this parameter (--with-onevpl) to configure ....
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 02.12.2024 22:48, skrev Andrew Randrianasulu:
вт, 3 дек. 2024 г., 00:01 Terje J. Hanssen <[email protected]>:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin <[email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem?
yes
It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
Depend on installation of onevpl-devel on buildfarm and flipping (adding) this parameter (--with-onevpl) to configure ....
Andrey?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems. I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems. On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin <[email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Unfortunately, it won't even build when I add: --with-onevpl on the configure line: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop. This is my 6 year old AMD laptop. On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen < [email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
вт, 3 дек. 2024 г., 02:36 Phyllis Smith <[email protected]>:
Unfortunately, it won't even build when I add: --with-onevpl on the configure line: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
This is my 6 year old AMD laptop.
you need to install https://github.com/intel/libvpl I used 2.13 for my dummy tests, but something down to 2.6 (I think) should work, at least as build requirement.
On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen < [email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Well, yes, BUT the point is people have procedures set up to build this automatically for years and now all of a sudden they will have to install more software. Probably not a good idea. On Mon, Dec 2, 2024 at 4:40 PM Andrew Randrianasulu <[email protected]> wrote:
вт, 3 дек. 2024 г., 02:36 Phyllis Smith <[email protected]>:
Unfortunately, it won't even build when I add: --with-onevpl on the configure line: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
This is my 6 year old AMD laptop.
you need to install
https://github.com/intel/libvpl
I used 2.13 for my dummy tests, but something down to 2.6 (I think) should work, at least as build requirement.
On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen < [email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
вт, 3 дек. 2024 г., 02:42 Phyllis Smith <[email protected]>:
Well, yes, BUT the point is people have procedures set up to build this automatically for years and now all of a sudden they will have to install more software. Probably not a good idea.
Note, we do not talk about changing default globally, just about machinery behind https://github.com/einhander/cin-gg-packages/releases but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;) Good night, sorry I did not looked at labels issue yet
On Mon, Dec 2, 2024 at 4:40 PM Andrew Randrianasulu < [email protected]> wrote:
вт, 3 дек. 2024 г., 02:36 Phyllis Smith <[email protected]>:
Unfortunately, it won't even build when I add: --with-onevpl on the configure line: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
This is my 6 year old AMD laptop.
you need to install
https://github.com/intel/libvpl
I used 2.13 for my dummy tests, but something down to 2.6 (I think) should work, at least as build requirement.
On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen < [email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen < [email protected]> wrote:
> Attached tested vaapi hwaccel presets as gzip'd tar file > > av1_vaapi_10b420.mp4 > av1_vaapi_10b420.webm > av1_vaapi_8b420.mp4 > av1_vaapi_8b420.webm > h264_vaapi_8b420.mp4 > hevc_vaapi_10b420.mp4 > hevc_vaapi_10b422.mp4 > hevc_vaapi_8b420.mp4 > vp9_vaapi_10b420.mp4 > vp9_vaapi_10b420.webm > vp9_vaapi_8b420.mp4 > vp9_vaapi_8b420.webm > > > -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 03.12.2024 01:16, skrev Andrew Randrianasulu:
вт, 3 дек. 2024 г., 02:42 Phyllis Smith <[email protected]>:
Well, yes, BUT the point is people have procedures set up to build this automatically for years and now all of a sudden they will have to install more software. Probably not a good idea.
Note, we do not talk about changing default globally, just about machinery behind
Possibly a test-build will clarify(?)
but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;)
Good night, sorry I did not looked at labels issue yet
On Mon, Dec 2, 2024 at 4:40 PM Andrew Randrianasulu <[email protected]> wrote:
вт, 3 дек. 2024 г., 02:36 Phyllis Smith <[email protected]>:
Unfortunately, it won't even build when I add: --with-onevpl on the configure line:
configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
This is my 6 year old AMD laptop.
you need to install
https://github.com/intel/libvpl
I used 2.13 for my dummy tests, but something down to 2.6 (I think) should work, at least as build requirement.
On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin <[email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Note, we do not talk about changing default globally, just about machinery behind
Sorry, I misunderstood and thought you meant default for all instead of Andrey's packages. (I need to pay more attention to the details in the email.) FYI - I believe for Fedora 40, oneVPL is installed with the O/S by default BUT I had to install oneVPL-devel to build CinGG. but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;) Andrew, I just send email when I happen to see it, hoping that you ignore it until the next day - I will endeavor to track time better. I did not looked at labels issue yet MatN will not be able to address the labels issue until Wednesday so we should probably wait until we hear back from him -- it may be an anomaly that may not be a bug due to some kind of interruption or it could just be a really esoteric bug. I did update the BT #666. On Mon, Dec 2, 2024 at 5:16 PM Andrew Randrianasulu <[email protected]> wrote:
вт, 3 дек. 2024 г., 02:42 Phyllis Smith <[email protected]>:
Well, yes, BUT the point is people have procedures set up to build this automatically for years and now all of a sudden they will have to install more software. Probably not a good idea.
Note, we do not talk about changing default globally, just about machinery behind
https://github.com/einhander/cin-gg-packages/releases
but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;)
Good night, sorry I did not looked at labels issue yet
On Mon, Dec 2, 2024 at 4:40 PM Andrew Randrianasulu < [email protected]> wrote:
вт, 3 дек. 2024 г., 02:36 Phyllis Smith <[email protected]>:
Unfortunately, it won't even build when I add: --with-onevpl on the configure line: configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
This is my 6 year old AMD laptop.
you need to install
https://github.com/intel/libvpl
I used 2.13 for my dummy tests, but something down to 2.6 (I think) should work, at least as build requirement.
On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen < [email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen < [email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
> Andrew, should these and the QSV presets be checked into GIT now > that Terje has tested them on his specific hardware? >
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
> P.S. There will not be new Appimages created at the end of this > month, but will wait until December. > > > On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen < > [email protected]> wrote: > >> Attached tested vaapi hwaccel presets as gzip'd tar file >> >> av1_vaapi_10b420.mp4 >> av1_vaapi_10b420.webm >> av1_vaapi_8b420.mp4 >> av1_vaapi_8b420.webm >> h264_vaapi_8b420.mp4 >> hevc_vaapi_10b420.mp4 >> hevc_vaapi_10b422.mp4 >> hevc_vaapi_8b420.mp4 >> vp9_vaapi_10b420.mp4 >> vp9_vaapi_10b420.webm >> vp9_vaapi_8b420.mp4 >> vp9_vaapi_8b420.webm >> >> >> -- > Cin mailing list > [email protected] > https://lists.cinelerra-gg.org/mailman/listinfo/cin >
On 03.12.2024 17:25, Phyllis Smith wrote:
Note, we do not talk about changing default globally, just about machinery behind
Sorry, I misunderstood and thought you meant default for all instead of Andrey's packages. (I need to pay more attention to the details in the email.) FYI - I believe for Fedora 40, oneVPL is installed with the O/S by default BUT I had to install oneVPL-devel to build CinGG.
I started Cingg on Leap 15.5 with the latest RPM Cinelerra Infinity - built: Dec 29 2024 03:47:56 and tried to test the "h264/5_vaapi,mp4" and "h264/5_qsv.mp4" presets. But as they didn't work, I guess the onVPL support is not added (yet)?
but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;)
Andrew, I just send email when I happen to see it, hoping that you ignore it until the next day - I will endeavor to track time better.
I did not looked at labels issue yet
MatN will not be able to address the labels issue until Wednesday so we should probably wait until we hear back from him -- it may be an anomaly that may not be a bug due to some kind of interruption or it could just be a really esoteric bug. I did update the BT #666.
On Mon, Dec 2, 2024 at 5:16 PM Andrew Randrianasulu <[email protected]> wrote:
вт, 3 дек. 2024 г., 02:42 Phyllis Smith <[email protected]>:
Well, yes, BUT the point is people have procedures set up to build this automatically for years and now all of a sudden they will have to install more software. Probably not a good idea.
Note, we do not talk about changing default globally, just about machinery behind
https://github.com/einhander/cin-gg-packages/releases
but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;)
Good night, sorry I did not looked at labels issue yet
On Mon, Dec 2, 2024 at 4:40 PM Andrew Randrianasulu <[email protected]> wrote:
вт, 3 дек. 2024 г., 02:36 Phyllis Smith <[email protected]>:
Unfortunately, it won't even build when I add: --with-onevpl on the configure line:
configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
This is my 6 year old AMD laptop.
you need to install
https://github.com/intel/libvpl
I used 2.13 for my dummy tests, but something down to 2.6 (I think) should work, at least as build requirement.
On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin <[email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
On 29.12.2024 17:04, Terje J. Hanssen wrote:
On 03.12.2024 17:25, Phyllis Smith wrote:
Note, we do not talk about changing default globally, just about machinery behind
Sorry, I misunderstood and thought you meant default for all instead of Andrey's packages. (I need to pay more attention to the details in the email.) FYI - I believe for Fedora 40, oneVPL is installed with the O/S by default BUT I had to install oneVPL-devel to build CinGG.
I started Cingg on Leap 15.5 with the latest RPM Cinelerra Infinity - built: Dec 29 2024 03:47:56
and tried to test the "h264/5_vaapi,mp4" and "h264/5_qsv.mp4" presets.
Sorry, a bit too hurry - I was partly deceived by trivial file accesses. * The correct is that h264/hevc/av1 vaapi work (libva) * while h264/hevc/av1 qsv cant find codec (libvpl)
But as they didn't work, I guess the onVPL support is not added (yet)?
but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;)
Andrew, I just send email when I happen to see it, hoping that you ignore it until the next day - I will endeavor to track time better.
I did not looked at labels issue yet
MatN will not be able to address the labels issue until Wednesday so we should probably wait until we hear back from him -- it may be an anomaly that may not be a bug due to some kind of interruption or it could just be a really esoteric bug. I did update the BT #666.
On Mon, Dec 2, 2024 at 5:16 PM Andrew Randrianasulu <[email protected]> wrote:
вт, 3 дек. 2024 г., 02:42 Phyllis Smith <[email protected]>:
Well, yes, BUT the point is people have procedures set up to build this automatically for years and now all of a sudden they will have to install more software. Probably not a good idea.
Note, we do not talk about changing default globally, just about machinery behind
https://github.com/einhander/cin-gg-packages/releases
but at 3am (GMT+3) I think we surely can stop holding our breath for same-minute answer ;)
Good night, sorry I did not looked at labels issue yet
On Mon, Dec 2, 2024 at 4:40 PM Andrew Randrianasulu <[email protected]> wrote:
вт, 3 дек. 2024 г., 02:36 Phyllis Smith <[email protected]>:
Unfortunately, it won't even build when I add: --with-onevpl on the configure line:
configure: error: requires onevpl support. make: *** No targets specified and no makefile found. Stop.
This is my 6 year old AMD laptop.
you need to install
https://github.com/intel/libvpl
I used 2.13 for my dummy tests, but something down to 2.6 (I think) should work, at least as build requirement.
On Mon, Dec 2, 2024 at 4:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 02.12.2024 23:32, skrev Phyllis Smith:
Adding OneVPL by default, which only works on the latest Intel computers and not on older ones or AMD, would not be a good idea; especially not for the RPM packaging. That is my opinion based on our attempt to keep CinGG generically usable on older computers and even 32-bit systems.
I didn't think "onevpl on" would prohibit other than Intel hardware to work as else, and that hwaccell work or not, dependent of the platform support. Actually my thought was to test what legacy Intel hardware are good for. Is possibly a Cingg user-switch possible instead?
I have yet to go through the last 5 attachment patches that Andrew graciously put all in one place for viability on all systems.
On Mon, Dec 2, 2024 at 2:01 PM Terje J. Hanssen <[email protected]> wrote:
Den 30.11.2024 01:03, skrev Andrew Randrianasulu:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin <[email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
Is the onevpl patch already included in the buildsystem? It was said it was "default to off", so I wonder if it will be available or "on" in the upcoming rpm?
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I tested vaapi presets with the compile of the new CinGG release. Previously vaapi was not working for me in either encoding or decoding. Now I have no errors or warnings. I used the Big Buck Bunny 1080p and 30 fps file with h264 codec. With some presets the rendering fails with the following errors in the terminal: - av1_vaapi_10b420.mp4 [av1_vaapi @ 0x7d304c2269c0] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed av1_vaapi:/home/paz/test_vaapi.mp4 - av1_vaapi_10b420.mp4 [av1_vaapi @ 0x7d304c2269c0] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed av1_vaapi:/home/paz/test_vaapi.mp4 - hevc_vaapi_10b420.mp4 Render::render_single: Session finished. FFStream::encode_frame: vaapi encode failed. file: /home/paz/test_vaapi.mp4 err: Input/output error FFMPEG::mux_video err: Operation not permitted FFStream::encode_frame: vaapi encode failed. file: /home/paz/test_vaapi.mp4 err: Input/output error FFMPEG::mux_video err: Operation not permitted Assertion !pic->prev failed at libavcodec/vaapi_encode.c:962 [CRASH] - hevc_vaapi_10b422.mp4 [AVHWFramesContext @ 0x76b6f40eab40] Failed to create surface: 14 (the requested RT Format is not supported). [AVHWFramesContext @ 0x76b6f40eab40] Unable to allocate a surface from internal buffer pool. Failed to initialize HW frame context. err: Cannot allocate memory [hevc_vaapi @ 0x76b6f400be40] Specified pixel format y210le is not supported by the hevc_vaapi encoder. [hevc_vaapi @ 0x76b6f400be40] Supported pixel formats: [hevc_vaapi @ 0x76b6f400be40] vaapi FFMPEG::open_encoder err: Invalid argument int FFMPEG::open_encoder(const char*, const char*): open failed hevc_vaapi:/home/paz/test_vaapi.mp4 Render::render_single: Session finished. - vp9_vaapi_10b420.mp4 [vp9_vaapi @ 0x76b63c0350c0] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed vp9_vaapi:/home/paz/test_vaapi.mp4 - vp9_vaapi_8b420.mp4 [vp9_vaapi @ 0x76b6180d7fc0] No usable encoding entrypoint found for profile VAProfileVP9Profile0 (19). FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed vp9_vaapi:/home/paz/test_vaapi.mp4 Other presets work more or less well: - h264.mp4 --> 78 fps - h264_vaapi.mp4 --> 118 fps - h264_vaapi_8b420.mp4 --> 80 fps - hevc_vaapi.mp4 --> 81 fps - hevc_vaapi_8b420.mp4 --> 110 fps IMPORTANT: These tests are not indicative, as I always have new problems with my Radeon RX 5700 XT with every driver update. PS: Compilation time got a lot longer, is it because of the new patches? PPS: I have not followed the various threads very well and so I do not know the conclusions you have reached....
On 02.01.2025 10:38, Andrea paz wrote:
I tested vaapi presets with the compile of the new CinGG release. Previously vaapi was not working for me in either encoding or decoding. Now I have no errors or warnings.
I used the Big Buck Bunny 1080p and 30 fps file with h264 codec. With some presets the rendering fails with the following errors in the terminal:
- av1_vaapi_10b420.mp4
[av1_vaapi @ 0x7d304c2269c0] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed av1_vaapi:/home/paz/test_vaapi.mp4
- av1_vaapi_10b420.mp4
[av1_vaapi @ 0x7d304c2269c0] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed av1_vaapi:/home/paz/test_vaapi.mp4
Your gpu has av1 10-bit encoding capability? Possibly try to comment out profile=main
- hevc_vaapi_10b420.mp4
Render::render_single: Session finished. FFStream::encode_frame: vaapi encode failed. file: /home/paz/test_vaapi.mp4 err: Input/output error FFMPEG::mux_video err: Operation not permitted FFStream::encode_frame: vaapi encode failed. file: /home/paz/test_vaapi.mp4 err: Input/output error FFMPEG::mux_video err: Operation not permitted Assertion !pic->prev failed at libavcodec/vaapi_encode.c:962 [CRASH]
- hevc_vaapi_10b422.mp4
[AVHWFramesContext @ 0x76b6f40eab40] Failed to create surface: 14 (the requested RT Format is not supported). [AVHWFramesContext @ 0x76b6f40eab40] Unable to allocate a surface from internal buffer pool. Failed to initialize HW frame context. err: Cannot allocate memory [hevc_vaapi @ 0x76b6f400be40] Specified pixel format y210le is not supported by the hevc_vaapi encoder. [hevc_vaapi @ 0x76b6f400be40] Supported pixel formats: [hevc_vaapi @ 0x76b6f400be40] vaapi FFMPEG::open_encoder err: Invalid argument int FFMPEG::open_encoder(const char*, const char*): open failed hevc_vaapi:/home/paz/test_vaapi.mp4 Render::render_single: Session finished.
- vp9_vaapi_10b420.mp4
[vp9_vaapi @ 0x76b63c0350c0] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed vp9_vaapi:/home/paz/test_vaapi.mp4
Try to comment out profile=0 or edit it to profile=2
- vp9_vaapi_8b420.mp4
[vp9_vaapi @ 0x76b6180d7fc0] No usable encoding entrypoint found for profile VAProfileVP9Profile0 (19). FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed vp9_vaapi:/home/paz/test_vaapi.mp4
Other presets work more or less well:
- h264.mp4 --> 78 fps - h264_vaapi.mp4 --> 118 fps - h264_vaapi_8b420.mp4 --> 80 fps - hevc_vaapi.mp4 --> 81 fps - hevc_vaapi_8b420.mp4 --> 110 fps
IMPORTANT: These tests are not indicative, as I always have new problems with my Radeon RX 5700 XT with every driver update.
PS: Compilation time got a lot longer, is it because of the new patches? PPS: I have not followed the various threads very well and so I do not know the conclusions you have reached....
I get all presets above to work from the suse15 RPM installation on Leap 15.6 On the other hand, I don't get vaapi rendering to work from the 31.12 AppImage, while they work from my 24.11 IntelHW AppImage, except vp9 10bit that looks distorted video.
Your gpu has av1 10-bit encoding capability? Possibly try to comment out profile=main
You are right; my graphics card (VCN 2.0) is not capable of AV1 hardware encoding at 8-10bit. I propose to add a note to the presets similar to: # The GPU must be capable of 8-10bit hardware encoding.
Try to comment out profile=0 or edit it to profile=2
No; I have the same errors.
On 02.01.2025 14:47, Andrea paz wrote:
Your gpu has av1 10-bit encoding capability? Possibly try to comment out profile=main You are right; my graphics card (VCN 2.0) is not capable of AV1 hardware encoding at 8-10bit. I propose to add a note to the presets similar to:
# The GPU must be capable of 8-10bit hardware encoding.
Yes, or possibly a bit more generic reminder to check out # Require gpu encoding capability For example I just tested Andrey's cin_5.1.20250103.ubuntu2204_amd64.deb on my ultrabook, Dell XPS 13-9370, and found the Intel UHD 620 iGPU (KBL) has h264_vaapi_8b410 and _10b420, but not hevc_vaapi capability.
Try to comment out profile=0 or edit it to profile=2 No; I have the same errors.
Checked into GIT as Andrea recommended below to add a similar note tohardware render presets. Also, updated date from 2024 to 2025 in versioninfo.h. On Thu, Jan 2, 2025 at 6:47 AM Andrea paz <[email protected]> wrote:
I propose to add a note to the presets similar to:
# The GPU must be capable of 8-10bit hardware encoding.
I am having a minor issue with the 2 of the attached patches. No problem: 0001-Add-mediacodec-based-encoder-profiles-for-termux.patch No problem: 0001-Exp-do-not-set-ildct-flag-for-qsv_av1-h264-vp9.patch Reversed by 0002 below: 0001-yet-another-10bit-attempt.patch No problem BUT see next line: 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch at least the one I tried of the new mp4 presets_vaapi.tar file did not work for me. Error message is "cant find codec_av1_vaapi' - I am not real sure about this, so I need to test some more. I have Use HW device set to vaapi and did the build with --enable-libsvtav1. The vaapi.webm preset seem to work of the 1 I tried. No problem BUT see next line: 0001-y4mdenoise-fails-on-clang-19.1.2-on-termux-disable.patch There is a huge advantage in y4mdenoise which I don't know if CinGG is coded to take advantage of or even it it could be fixed to do so. Could there be another way to fix this rather than removing it? On Fri, Nov 29, 2024 at 5:03 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen <[email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
вт, 10 дек. 2024 г., 00:02 Phyllis Smith <[email protected]>:
I am having a minor issue with the 2 of the attached patches. No problem: 0001-Add-mediacodec-based-encoder-profiles-for-termux.patch No problem: 0001-Exp-do-not-set-ildct-flag-for-qsv_av1-h264-vp9.patch
Reversed by 0002 below: 0001-yet-another-10bit-attempt.patch No problem BUT see next line: 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch at least the one I tried of the new mp4 presets_vaapi.tar file did not work for me. Error message is "cant find codec_av1_vaapi' - I am not real sure about this, so I need to test some more.
does your hw support av1 _encoding_ ? I think vainfo should tell you I have Use HW device set to vaapi and did the build with
--enable-libsvtav1. The vaapi.webm preset seem to work of the 1 I tried.
No problem BUT see next line: 0001-y4mdenoise-fails-on-clang-19.1.2-on-termux-disable.patch There is a huge advantage in y4mdenoise which I don't know if CinGG is coded to take advantage of or even it it could be fixed to do so. Could there be another way to fix this rather than removing it?
I do not think cingg as-is uses this specific *binary* - it does not copied around into bin and there is no link failure ... I think only non-ffmpeg mpeg2 encoder uses this feature ? I'll look around mjpegtools project to see if there was patch for this already, it was a bit beyond my simplegoogling around.
On Fri, Nov 29, 2024 at 5:03 PM Andrew Randrianasulu < [email protected]> wrote:
сб, 30 нояб. 2024 г., 01:07 Phyllis Smith via Cin < [email protected]>:
Andrew, should these and the QSV presets be checked into GIT now that Terje has tested them on his specific hardware?
yes, but 10bit ones require patch for themselves and recent one removing addition of ildct flag for some qsv encoders ....
"Exp: do not set ildct flag for qsv_av1/h264/vp9" 0001-yet-another-10bit-attempt.patch 0002-Hopefully-wire-up-various-cin_pix_fmt-for-vaapi-enco.patch
re-attached so you do not need to hunt them in mailthreads ....
I also have mediacodec/termux related profiles, and one hackfix for mjpegtools failing to build here on clang.
P.S. There will not be new Appimages created at the end of this month, but will wait until December.
On Tue, Nov 26, 2024 at 3:52 PM Terje J. Hanssen < [email protected]> wrote:
Attached tested vaapi hwaccel presets as gzip'd tar file
av1_vaapi_10b420.mp4 av1_vaapi_10b420.webm av1_vaapi_8b420.mp4 av1_vaapi_8b420.webm h264_vaapi_8b420.mp4 hevc_vaapi_10b420.mp4 hevc_vaapi_10b422.mp4 hevc_vaapi_8b420.mp4 vp9_vaapi_10b420.mp4 vp9_vaapi_10b420.webm vp9_vaapi_8b420.mp4 vp9_vaapi_8b420.webm
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
does your hw support av1 _encoding_ ?
No! I probably should have checked that first !
I do not think cingg as-is uses this specific *binary* - it does not copied around into bin and there is no link failure ... I think only non-ffmpeg mpeg2 encoder uses this feature
Will put in patch and if some genius comes along, they can fix it. I am quite sure that this is non-ffmpeg rendering of mpeg from the original Cinelerra version when ffmpeg was not even a thing. But I still use it for creating DVDs and users with old VHS tapes could certainly benefit if y4mdenoise was integrated.
participants (4)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith -
Terje J. Hanssen