Prepping HW upgrade options for AV1 de-/encoding
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc...... I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible. But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware: 1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics 2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ... References: AV1 Encoding on a Budget: The Intel Arc A380 Approach https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38... https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve... AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e... Terje J. H
On Sunday, December 3, 2023 10:29:30 PM CET, Terje J. Hanssen via Cin wrote:
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU?
Is this a question with 'can I playback an AV-1 encoded movie' or 'can I edit AV-1 encoded material'? I really would wonder which camera would prefer encoding in AV-1. -- Stefan
пн, 4 дек. 2023 г., 00:41 Stefan de Konink via Cin < [email protected]>:
On Sunday, December 3, 2023 10:29:30 PM CET, Terje J. Hanssen via Cin wrote:
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU?
Is this a question with 'can I playback an AV-1 encoded movie' or 'can I edit AV-1 encoded material'? I really would wonder which camera would prefer encoding in AV-1.
not exactly camera, but my phony tablet apparently have av1 decoder at whooping 512*512 (videoconferencing?). I think decoding via libdav1d should already be relatively fast .. for one or two streams. Encoding is where av1 is a snail ....
-- Stefan -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 03.12.2023 22:41, skrev Stefan de Konink via Cin:
On Sunday, December 3, 2023 10:29:30 PM CET, Terje J. Hanssen via Cin wrote:
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU?
Is this a question with 'can I playback an AV-1 encoded movie' or 'can I edit AV-1 encoded material'? I really would wonder which camera would prefer encoding in AV-1.
IMO AV1 transcoding from other formats, intermediate or uncompressed, and for AV1 playback yes. The increasing interest in the 5 years newer AV1 vs HEVC is royalty free, some higher compression at the same or better quality for video streaming or file download. (AV1 decoding is to be supported on high end smartphones).
пн, 4 дек. 2023 г., 00:29 Terje J. Hanssen via Cin < [email protected]>:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
I digged up this: https://community.intel.com/t5/Media-Intel-Video-Processing/ffmpeg-6-using-q... url is ...eeeh. I hope vaapi/qsv by themselves does not consume too much cpu during video operations. Only opengl/opencl performance probably might be not really great ...
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach
https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38...
https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
Terje J. H
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs: * Featuring 8 Xe-cores, the*A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. * Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16 That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?) My existing Skylake WS 2) above has PCie 3.0 only. PCIe 4.0 https://no.wikipedia.org/wiki/PCI_Express https://www.techreviewer.com/learn-about-tech/what-is-pcie-40/ Motherboards Support PCIe 4.0 https://www.makeuseof.com/best-budget-pcie-4-motherboards/ https://www.techreviewer.com/tech-answers/which-motherboards-support-pcie-40... Maybe also information of interest for WS building will be clarified within a week, when Intel release their new "Meteor Lake, Core Ultra mobile processors(?) https://en.wikipedia.org/wiki/Meteor_Lake
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38... https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
пт, 8 дек. 2023 г., 13:37 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs:
- Featuring 8 Xe-cores, the* A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. - Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16
That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?)
well, despite so much time spend looking at dev process for mesa3d I still do not know full details and media encoder process. But isn't it like putting uncompressed frame in vram (as long as you have enough of it - so probably n raw frames between keyframe ideally?) let media engine chw on it, pull resulting compressed bitstream out of vram via pci-express? So I speculate pcie bandwidth in itself will only matter if you compress both big frame size and long keyframes, so dma engine on card must constantly pump new raw frame data via bus. I saw some mention of big (resizeable) BAR as requirement for good performance, but opengl/vulkan IMO a bit different because they send often big amount of tiny objects (vertices) via bus for each frame. But may be default 256 Mb in size bar feels a bit small for sending like 1 second of 25 4k frames (300 mb/s)? gpus today use their own memory paging system, so may be this add additional restriction on how fast you can push frames to them. .... Also, windows and Linux drivers might differ ( I bet most reviews are from windows land). May be someone will post linux review of this particular aspect of Arc graphics, either video or text ... If this Suse Studio service still works may be you can compose your own live image with all components required to test that and walk to some offline place where you can testdrive new card .... { If weather feels favourable enough - we have around -14 C airtemp so I and my dog prefer short dashes around and back to warm place shortly} My existing Skylake WS 2) above has PCie 3.0 only.
PCIe 4.0 https://no.wikipedia.org/wiki/PCI_Express https://www.techreviewer.com/learn-about-tech/what-is-pcie-40/
Motherboards Support PCIe 4.0 https://www.makeuseof.com/best-budget-pcie-4-motherboards/
https://www.techreviewer.com/tech-answers/which-motherboards-support-pcie-40...
Maybe also information of interest for WS building will be clarified within a week, when Intel release their new "Meteor Lake, Core Ultra mobile processors(?) https://en.wikipedia.org/wiki/Meteor_Lake
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach
https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38...
https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
пт, 8 дек. 2023 г., 13:57 Andrew Randrianasulu <[email protected]>:
пт, 8 дек. 2023 г., 13:37 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs:
- Featuring 8 Xe-cores, the* A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. - Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16
That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?)
well, despite so much time spend looking at dev process for mesa3d I still do not know full details and media encoder process. But isn't it like putting uncompressed frame in vram (as long as you have enough of it - so probably n raw frames between keyframe ideally?) let media engine chw on it, pull resulting compressed bitstream out of vram via pci-express?
So I speculate pcie bandwidth in itself will only matter if you compress both big frame size and long keyframes, so dma engine on card must constantly pump new raw frame data via bus.
I saw some mention of big (resizeable) BAR as requirement for good performance, but opengl/vulkan IMO a bit different because they send often big amount of tiny objects (vertices) via bus for each frame. But may be default 256 Mb in size bar feels a bit small for sending like 1 second of 25 4k frames (300 mb/s)?
https://forums.gentoo.org/viewtopic-t-1165048.html?sid=1b9518b86afdcd1fa5e77... not exactly about av1 in ffmpeg 6.1 but lists some components you need for vaapi/qsv encoder on Arc 380 - also from dmesg resizeable bar support is not essential ?
gpus today use their own memory paging system, so may be this add additional restriction on how fast you can push frames to them. ....
Also, windows and Linux drivers might differ ( I bet most reviews are from windows land).
May be someone will post linux review of this particular aspect of Arc graphics, either video or text ...
If this Suse Studio service still works may be you can compose your own live image with all components required to test that and walk to some offline place where you can testdrive new card .... { If weather feels favourable enough - we have around -14 C airtemp so I and my dog prefer short dashes around and back to warm place shortly}
My existing Skylake WS 2) above has PCie 3.0 only.
PCIe 4.0 https://no.wikipedia.org/wiki/PCI_Express https://www.techreviewer.com/learn-about-tech/what-is-pcie-40/
Motherboards Support PCIe 4.0 https://www.makeuseof.com/best-budget-pcie-4-motherboards/
https://www.techreviewer.com/tech-answers/which-motherboards-support-pcie-40...
Maybe also information of interest for WS building will be clarified within a week, when Intel release their new "Meteor Lake, Core Ultra mobile processors(?) https://en.wikipedia.org/wiki/Meteor_Lake
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach
https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38...
https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 08.12.2023 12:50, skrev Andrew Randrianasulu:
пт, 8 дек. 2023 г., 13:57 Andrew Randrianasulu <[email protected]>:
пт, 8 дек. 2023 г., 13:37 Terje J. Hanssen via Cin <[email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs:
* Featuring 8 Xe-cores, the*A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. * Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16
That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?)
well, despite so much time spend looking at dev process for mesa3d I still do not know full details and media encoder process. But isn't it like putting uncompressed frame in vram (as long as you have enough of it - so probably n raw frames between keyframe ideally?) let media engine chw on it, pull resulting compressed bitstream out of vram via pci-express?
So I speculate pcie bandwidth in itself will only matter if you compress both big frame size and long keyframes, so dma engine on card must constantly pump new raw frame data via bus.
I saw some mention of big (resizeable) BAR as requirement for good performance, but opengl/vulkan IMO a bit different because they send often big amount of tiny objects (vertices) via bus for each frame. But may be default 256 Mb in size bar feels a bit small for sending like 1 second of 25 4k frames (300 mb/s)?
Nothing would be better than that A380 does work with older PCIe 3.0 motherboards and CPUs and without too much decrease in performance. I've also extracted from the following two articles: Intel Arc Desktop Graphics Card Gets Requirement List: Resizable BAR Enabled & Support on 10th Gen and Above CPUs https://wccftech.com/intel-arc-desktop-graphics-card-gets-requirement-list-r... /We are supporting Intel platforms with resizable BAR and will add support for AMD platforms with Smart Access Memory as Intel Arc graphics cards become available for sale as components. Motherboard requirement:/ * Full-size PCIe 3.0 (or newer) x16 slot * Resizeable BAR Arc A770 Loses Up to 24 Percent Performance Without Resizable Bar | Tom's Hardware https://www.tomshardware.com/news/arc-a770-loses-25-percent-performance-with... * Arc isn't for older systems. * Intel has revitalized the midrange graphics card market with the company's latest Arc A770, which will make its way into the list of best graphics cards. Starting at $329, the Arc Alchemist graphics card brings GeForce RTX 3060-like performance to the table with Resizable BAR (ReBAR) enabled, of course. But, without ReBAR or similar technology like Smart Access Memory (SAM), it's another story. * With Arc, Intel recommends potential consumers make sure their systems support ReBAR or SAM. * In addition to testing ReBAR, TechPowerUp also evaluated whether the speed of the expansion slot impacts the Arc A770's performance. As a reminder, the Arc A770 comes with a conventional PCIe 4.0 x16 interface. However, the tests revealed that PCIe 3.0 is still plenty for the Arc A770 as long as ReBAR is enabled. Furthermore, TechPowerUp only recorded a performance difference of up to 2% between PCIe 3.0 and PCIe 4.0, so ReBAR support is more important than the expansion slot. Regarding ReBAR, only Intel 10th Generation Comet Lake <https://www.tomshardware.com/news/intel-comet-lake-s-cores-53-ghz-high-power-better-pricing>, 11th Generation Rocket Lake <https://www.tomshardware.com/news/intel-11th-gen-rocket-lake-s-specifications-pricing>, and 12th Generation Alder Lake <https://www.tomshardware.com/features/intel-shares-alder-lake-pricing-specs-and-gaming-performance> processors support that feature. As for AMD, SAM support is only present on Ryzen 3000 <https://www.tomshardware.com/news/amd-third-gen-ryzen-7nm-launch-intel-cpu,39449.html> Zen 2 chips and newer. So while Arc's performance looks attractive and priced fairly, its requirements effectively lock out users with older systems. Arc also demands Windows 10 20H2 or Windows 11 <https://www.tomshardware.com/tag/windows-11> as the operating system, so Windows 7 users, who are reluctant to upgrade, are also out of the picture.
https://forums.gentoo.org/viewtopic-t-1165048.html?sid=1b9518b86afdcd1fa5e77...
not exactly about av1 in ffmpeg 6.1 but lists some components you need for vaapi/qsv encoder on Arc 380 - also from dmesg resizeable bar support is not essential ?
gpus today use their own memory paging system, so may be this add additional restriction on how fast you can push frames to them. ....
Also, windows and Linux drivers might differ ( I bet most reviews are from windows land).
May be someone will post linux review of this particular aspect of Arc graphics, either video or text ...
If this Suse Studio service still works may be you can compose your own live image with all components required to test that and walk to some offline place where you can testdrive new card .... { If weather feels favourable enough - we have around -14 C airtemp so I and my dog prefer short dashes around and back to warm place shortly}
My existing Skylake WS 2) above has PCie 3.0 only.
PCIe 4.0 https://no.wikipedia.org/wiki/PCI_Express https://www.techreviewer.com/learn-about-tech/what-is-pcie-40/
Motherboards Support PCIe 4.0 https://www.makeuseof.com/best-budget-pcie-4-motherboards/ https://www.techreviewer.com/tech-answers/which-motherboards-support-pcie-40...
Maybe also information of interest for WS building will be clarified within a week, when Intel release their new "Meteor Lake, Core Ultra mobile processors(?) https://en.wikipedia.org/wiki/Meteor_Lake
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38... https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 08.12.2023 23:56, skrev Terje J. Hanssen:
Den 08.12.2023 12:50, skrev Andrew Randrianasulu:
пт, 8 дек. 2023 г., 13:57 Andrew Randrianasulu <[email protected]>:
пт, 8 дек. 2023 г., 13:37 Terje J. Hanssen via Cin <[email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs:
* Featuring 8 Xe-cores, the*A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. * Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16
That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?)
well, despite so much time spend looking at dev process for mesa3d I still do not know full details and media encoder process. But isn't it like putting uncompressed frame in vram (as long as you have enough of it - so probably n raw frames between keyframe ideally?) let media engine chw on it, pull resulting compressed bitstream out of vram via pci-express?
So I speculate pcie bandwidth in itself will only matter if you compress both big frame size and long keyframes, so dma engine on card must constantly pump new raw frame data via bus.
I saw some mention of big (resizeable) BAR as requirement for good performance, but opengl/vulkan IMO a bit different because they send often big amount of tiny objects (vertices) via bus for each frame. But may be default 256 Mb in size bar feels a bit small for sending like 1 second of 25 4k frames (300 mb/s)?
Nothing would be better than that A380 does work with older PCIe 3.0 motherboards and CPUs and without too much decrease in performance.
Then I got the following reply to my support request from ASRock TSD regarding https://www.asrock.com/Graphics-Card/Intel/Intel%20Arc%20A380%20Challenger%2... Skylake platform does not match the system minimum requirements. Please refer to the below link for further information. https://www.intel.com/content/www/us/en/support/articles/000091128/graphics....
I've also extracted from the following two articles:
Intel Arc Desktop Graphics Card Gets Requirement List: Resizable BAR Enabled & Support on 10th Gen and Above CPUs
https://wccftech.com/intel-arc-desktop-graphics-card-gets-requirement-list-r... /We are supporting Intel platforms with resizable BAR and will add support for AMD platforms with Smart Access Memory as Intel Arc graphics cards become available for sale as components. Motherboard requirement:/
* Full-size PCIe 3.0 (or newer) x16 slot * Resizeable BAR
Arc A770 Loses Up to 24 Percent Performance Without Resizable Bar | Tom's Hardware
https://www.tomshardware.com/news/arc-a770-loses-25-percent-performance-with...
* Arc isn't for older systems. * Intel has revitalized the midrange graphics card market with the company's latest Arc A770, which will make its way into the list of best graphics cards. Starting at $329, the Arc Alchemist graphics card brings GeForce RTX 3060-like performance to the table with Resizable BAR (ReBAR) enabled, of course. But, without ReBAR or similar technology like Smart Access Memory (SAM), it's another story.
* With Arc, Intel recommends potential consumers make sure their systems support ReBAR or SAM.
* In addition to testing ReBAR, TechPowerUp also evaluated whether the speed of the expansion slot impacts the Arc A770's performance. As a reminder, the Arc A770 comes with a conventional PCIe 4.0 x16 interface. However, the tests revealed that PCIe 3.0 is still plenty for the Arc A770 as long as ReBAR is enabled. Furthermore, TechPowerUp only recorded a performance difference of up to 2% between PCIe 3.0 and PCIe 4.0, so ReBAR support is more important than the expansion slot. Regarding ReBAR, only Intel 10th Generation Comet Lake <https://www.tomshardware.com/news/intel-comet-lake-s-cores-53-ghz-high-power-better-pricing>, 11th Generation Rocket Lake <https://www.tomshardware.com/news/intel-11th-gen-rocket-lake-s-specifications-pricing>, and 12th Generation Alder Lake <https://www.tomshardware.com/features/intel-shares-alder-lake-pricing-specs-and-gaming-performance> processors support that feature. As for AMD, SAM support is only present on Ryzen 3000 <https://www.tomshardware.com/news/amd-third-gen-ryzen-7nm-launch-intel-cpu,39449.html> Zen 2 chips and newer. So while Arc's performance looks attractive and priced fairly, its requirements effectively lock out users with older systems. Arc also demands Windows 10 20H2 or Windows 11 <https://www.tomshardware.com/tag/windows-11> as the operating system, so Windows 7 users, who are reluctant to upgrade, are also out of the picture.
https://forums.gentoo.org/viewtopic-t-1165048.html?sid=1b9518b86afdcd1fa5e77...
not exactly about av1 in ffmpeg 6.1 but lists some components you need for vaapi/qsv encoder on Arc 380 - also from dmesg resizeable bar support is not essential ?
gpus today use their own memory paging system, so may be this add additional restriction on how fast you can push frames to them. ....
Also, windows and Linux drivers might differ ( I bet most reviews are from windows land).
May be someone will post linux review of this particular aspect of Arc graphics, either video or text ...
If this Suse Studio service still works may be you can compose your own live image with all components required to test that and walk to some offline place where you can testdrive new card .... { If weather feels favourable enough - we have around -14 C airtemp so I and my dog prefer short dashes around and back to warm place shortly}
My existing Skylake WS 2) above has PCie 3.0 only.
PCIe 4.0 https://no.wikipedia.org/wiki/PCI_Express https://www.techreviewer.com/learn-about-tech/what-is-pcie-40/
Motherboards Support PCIe 4.0 https://www.makeuseof.com/best-budget-pcie-4-motherboards/ https://www.techreviewer.com/tech-answers/which-motherboards-support-pcie-40...
Maybe also information of interest for WS building will be clarified within a week, when Intel release their new "Meteor Lake, Core Ultra mobile processors(?) https://en.wikipedia.org/wiki/Meteor_Lake
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38... https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
пн, 11 дек. 2023 г., 16:13 Terje J. Hanssen via Cin < [email protected]>:
Den 08.12.2023 23:56, skrev Terje J. Hanssen:
Den 08.12.2023 12:50, skrev Andrew Randrianasulu:
пт, 8 дек. 2023 г., 13:57 Andrew Randrianasulu <[email protected]>:
пт, 8 дек. 2023 г., 13:37 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs:
- Featuring 8 Xe-cores, the* A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. - Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16
That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?)
well, despite so much time spend looking at dev process for mesa3d I still do not know full details and media encoder process. But isn't it like putting uncompressed frame in vram (as long as you have enough of it - so probably n raw frames between keyframe ideally?) let media engine chw on it, pull resulting compressed bitstream out of vram via pci-express?
So I speculate pcie bandwidth in itself will only matter if you compress both big frame size and long keyframes, so dma engine on card must constantly pump new raw frame data via bus.
I saw some mention of big (resizeable) BAR as requirement for good performance, but opengl/vulkan IMO a bit different because they send often big amount of tiny objects (vertices) via bus for each frame. But may be default 256 Mb in size bar feels a bit small for sending like 1 second of 25 4k frames (300 mb/s)?
Nothing would be better than that A380 does work with older PCIe 3.0 motherboards and CPUs and without too much decrease in performance.
Then I got the following reply to my support request from ASRock TSD regarding
https://www.asrock.com/Graphics-Card/Intel/Intel%20Arc%20A380%20Challenger%2...
Skylake platform does not match the system minimum requirements. Please refer to the below link for further information.
https://www.intel.com/content/www/us/en/support/articles/000091128/graphics....
well, if you can get card for brief (two weeks?) testing and return if it
really does not work - it will be better than leaning on official answer, IMO. after all, Intel, like any company tries to sell you a bridge .....
I've also extracted from the following two articles:
Intel Arc Desktop Graphics Card Gets Requirement List: Resizable BAR Enabled & Support on 10th Gen and Above CPUs
https://wccftech.com/intel-arc-desktop-graphics-card-gets-requirement-list-r... *We are supporting Intel platforms with resizable BAR and will add support for AMD platforms with Smart Access Memory as Intel Arc graphics cards become available for sale as components. Motherboard requirement:*
- Full-size PCIe 3.0 (or newer) x16 slot - Resizeable BAR
Arc A770 Loses Up to 24 Percent Performance Without Resizable Bar | Tom's Hardware
https://www.tomshardware.com/news/arc-a770-loses-25-percent-performance-with...
- Arc isn't for older systems. - Intel has revitalized the midrange graphics card market with the company's latest Arc A770, which will make its way into the list of best graphics cards. Starting at $329, the Arc Alchemist graphics card brings GeForce RTX 3060-like performance to the table with Resizable BAR (ReBAR) enabled, of course. But, without ReBAR or similar technology like Smart Access Memory (SAM), it's another story.
- With Arc, Intel recommends potential consumers make sure their systems support ReBAR or SAM.
- In addition to testing ReBAR, TechPowerUp also evaluated whether the speed of the expansion slot impacts the Arc A770's performance. As a reminder, the Arc A770 comes with a conventional PCIe 4.0 x16 interface. However, the tests revealed that PCIe 3.0 is still plenty for the Arc A770 as long as ReBAR is enabled. Furthermore, TechPowerUp only recorded a performance difference of up to 2% between PCIe 3.0 and PCIe 4.0, so ReBAR support is more important than the expansion slot. Regarding ReBAR, only Intel 10th Generation Comet Lake <https://www.tomshardware.com/news/intel-comet-lake-s-cores-53-ghz-high-power-better-pricing>, 11th Generation Rocket Lake <https://www.tomshardware.com/news/intel-11th-gen-rocket-lake-s-specifications-pricing>, and 12th Generation Alder Lake <https://www.tomshardware.com/features/intel-shares-alder-lake-pricing-specs-and-gaming-performance> processors support that feature. As for AMD, SAM support is only present on Ryzen 3000 <https://www.tomshardware.com/news/amd-third-gen-ryzen-7nm-launch-intel-cpu,39449.html> Zen 2 chips and newer. So while Arc's performance looks attractive and priced fairly, its requirements effectively lock out users with older systems. Arc also demands Windows 10 20H2 or Windows 11 <https://www.tomshardware.com/tag/windows-11> as the operating system, so Windows 7 users, who are reluctant to upgrade, are also out of the picture.
https://forums.gentoo.org/viewtopic-t-1165048.html?sid=1b9518b86afdcd1fa5e77...
not exactly about av1 in ffmpeg 6.1 but lists some components you need for vaapi/qsv encoder on Arc 380 - also from dmesg resizeable bar support is not essential ?
gpus today use their own memory paging system, so may be this add additional restriction on how fast you can push frames to them. ....
Also, windows and Linux drivers might differ ( I bet most reviews are from windows land).
May be someone will post linux review of this particular aspect of Arc graphics, either video or text ...
If this Suse Studio service still works may be you can compose your own live image with all components required to test that and walk to some offline place where you can testdrive new card .... { If weather feels favourable enough - we have around -14 C airtemp so I and my dog prefer short dashes around and back to warm place shortly}
My existing Skylake WS 2) above has PCie 3.0 only.
PCIe 4.0 https://no.wikipedia.org/wiki/PCI_Express https://www.techreviewer.com/learn-about-tech/what-is-pcie-40/
Motherboards Support PCIe 4.0 https://www.makeuseof.com/best-budget-pcie-4-motherboards/
https://www.techreviewer.com/tech-answers/which-motherboards-support-pcie-40...
Maybe also information of interest for WS building will be clarified within a week, when Intel release their new "Meteor Lake, Core Ultra mobile processors(?) https://en.wikipedia.org/wiki/Meteor_Lake
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach
https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38...
https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I tried to create an encoding profile for av1_vaapi. I attach the preset. It does not work and I get the following error: [av1_vaapi @ 0x7f8c94163500] A hardware frames reference is required to associate the encoding device. FFMPEG::open_encoder err: Invalid argument int FFMPEG::open_encoder(const char*, const char*): open failed av1_vaapi:/home/paz/test_av1_vaapi.webm Render::render_single: Session finished. Any idea what it might be?
вт, 12 дек. 2023 г., 18:16 Andrea paz <[email protected]>:
I tried to create an encoding profile for av1_vaapi. I attach the preset. It does not work and I get the following error:
[av1_vaapi @ 0x7f8c94163500] A hardware frames reference is required to associate the encoding device. FFMPEG::open_encoder err: Invalid argument int FFMPEG::open_encoder(const char*, const char*): open failed av1_vaapi:/home/paz/test_av1_vaapi.webm Render::render_single: Session finished.
Any idea what it might be?
well, does your GPU support it in the first place?
well, does your GPU support it in the first place?
The h264_vaapi.mp4 profile works for me without any problem. I tried adding "cin_hw_dev=vaapi" to the profile and now the error is: [av1_vaapi @ 0x7f926c088e00] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented I have an AMD RT5700XT and it should support vaapi well.
вт, 12 дек. 2023 г., 18:31 Andrea paz <[email protected]>:
well, does your GPU support it in the first place?
The h264_vaapi.mp4 profile works for me without any problem. I tried adding "cin_hw_dev=vaapi" to the profile and now the error is:
[av1_vaapi @ 0x7f926c088e00] No usable encoding profile found. FFMPEG::open_encoder err: Function not implemented
guess setting cin-specific parameter like this upsets libavcodec ....
I have an AMD RT5700XT and it should support vaapi well.
well, av1 is new hw feature ... https://www.amd.com/en/support/graphics/amd-radeon-5700-series/amd-radeon-rx... this site lists its architecture as rdna, and av1 support started from rdna2 ? ah, pc arms race when 4 years old card already feels old .....
You're right, my card does not support av1. The 6000 series supports av1 only in decoding while the latest 7000 series also supports encoding. Damn AMD!
Den 12.12.2023 16:52, skrev Andrea paz via Cin:
You're right, my card does not support av1. The 6000 series supports av1 only in decoding while the latest 7000 series also supports encoding. Damn AMD!
Another overview table for AV1 hardware https://en.wikipedia.org/wiki/AV1#Hardware
On Tue, Dec 12, 2023 at 8:17 AM Andrea paz via Cin < [email protected]> wrote:
I tried to create an encoding profile for av1_vaapi. I attach the preset. It does not work and I get the following error:
[av1_vaapi @ 0x7f8c94163500] A hardware frames reference is required to associate the encoding device. FFMPEG::open_encoder err: Invalid argument
A lot of "muddy waters" when searching this on the internet but the bottom line is for us in looking for what are the current ffmpeg 6.1 supported encoders, key in: # ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep av1 V....D *libaom-av1* libaom AV1 (codec av1) A....D *wmav1 * Windows Media Audio 1 which means the first line of av1_vaapi.webm can only be "webm libaom-av1" which will not provide vaapi; that is the line used in av1.webm. Just to ensure that the " ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep your_request" works as expected, keyin: # ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep h264 V....D *libx264* libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (codec h264) V....D *libx264rgb* libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 RGB (codec h264) V....D *h264_nvenc* NVIDIA NVENC H.264 encoder (codec h264) V..... *h264_v4l2m2m * V4L2 mem2mem H.264 encoder wrapper (codec h264) V....D *h264_vaapi* H.264/AVC (VAAPI) (codec h264)
On 12/14/23 18:38, Phyllis Smith via Cin wrote:
On Tue, Dec 12, 2023 at 8:17 AM Andrea paz via Cin <[email protected]> wrote:
I tried to create an encoding profile for av1_vaapi. I attach the preset. It does not work and I get the following error:
[av1_vaapi @ 0x7f8c94163500] A hardware frames reference is required to associate the encoding device. FFMPEG::open_encoder err: Invalid argument
A lot of "muddy waters" when searching this on the internet but the bottom line is for us in looking for what are the current ffmpeg 6.1 supported encoders, key in:
# ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep av1 V....D *libaom-av1* libaom AV1 (codec av1) A....D *wmav1 * Windows Media Audio 1
which means the first line of av1_vaapi.webm can only be "webm libaom-av1" which will not provide vaapi; that is the line used in av1.webm.
Hm, I wonder why so few av1 encoders are enabled? In comparison I get this list from Packman's ffmpeg 6.0.1 on Tumbleweed-Slowroll: fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1) V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1 ffmpeg -hwaccels -hide_banner Hardware acceleration methods: vdpau cuda vaapi qsv drm vulkan Additional references: https://trac.ffmpeg.org/wiki/HWAccelIntro https://trac.ffmpeg.org/wiki/Hardware/VAAPI https://trac.ffmpeg.org/wiki/Hardware/QuickSync https://www.reddit.com/r/AV1/comments/14zwron/guidance_for_av1_hwaccel/
Just to ensure that the " ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep your_request" works as expected, keyin:
# ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep h264 V....D *libx264* libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (codec h264) V....D *libx264rgb* libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 RGB (codec h264) V....D *h264_nvenc* NVIDIA NVENC H.264 encoder (codec h264) V..... *h264_v4l2m2m * V4L2 mem2mem H.264 encoder wrapper (codec h264) V....D *h264_vaapi* H.264/AVC (VAAPI) (codec h264)
пт, 15 дек. 2023 г., 01:21 Terje J. Hanssen via Cin < [email protected]>:
On 12/14/23 18:38, Phyllis Smith via Cin wrote:
On Tue, Dec 12, 2023 at 8:17 AM Andrea paz via Cin < [email protected]> wrote:
I tried to create an encoding profile for av1_vaapi. I attach the preset. It does not work and I get the following error:
[av1_vaapi @ 0x7f8c94163500] A hardware frames reference is required to associate the encoding device. FFMPEG::open_encoder err: Invalid argument
A lot of "muddy waters" when searching this on the internet but the bottom line is for us in looking for what are the current ffmpeg 6.1 supported encoders, key in:
# ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep av1 V....D *libaom-av1* libaom AV1 (codec av1) A....D *wmav1 * Windows Media Audio 1
which means the first line of av1_vaapi.webm can only be "webm libaom-av1" which will not provide vaapi; that is the line used in av1.webm.
Hm, I wonder why so few av1 encoders are enabled?
Because additional ones tend to have external dependencies we normally do not carry? Also, at least on aarch64 librav1e was a bit of disappointment, at least on default settings it was SLOW.
In comparison I get this list from Packman's ffmpeg 6.0.1 on Tumbleweed-Slowroll:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1) V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
ffmpeg -hwaccels -hide_banner Hardware acceleration methods: vdpau cuda vaapi qsv drm vulkan
Additional references: https://trac.ffmpeg.org/wiki/HWAccelIntro https://trac.ffmpeg.org/wiki/Hardware/VAAPI https://trac.ffmpeg.org/wiki/Hardware/QuickSync https://www.reddit.com/r/AV1/comments/14zwron/guidance_for_av1_hwaccel/
Just to ensure that the " ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep your_request" works as expected, keyin:
# ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep h264 V....D *libx264* libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (codec h264) V....D *libx264rgb* libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 RGB (codec h264) V....D *h264_nvenc* NVIDIA NVENC H.264 encoder (codec h264) V..... *h264_v4l2m2m * V4L2 mem2mem H.264 encoder wrapper (codec h264) V....D *h264_vaapi* H.264/AVC (VAAPI) (codec h264)
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
# ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep av1 V....D *libaom-av1* libaom AV1 (codec av1) A....D *wmav1 * Windows Media Audio 1
Hm, I wonder why so few av1 encoders are enabled?
Because additional ones tend to have external dependencies we normally do not carry? Also, at least on aarch64 librav1e was a bit of disappointment, at least on default settings it was SLOW.
In addition to what Andrew reported, when building FFmpeg, you have to specifically *enable libsvtav1* which has not been done, but could be if someone tests that and finds it useful. But what is actually more interesting is that there is still no vaapi_av1 which is what Andrea was trying to get working (just to find out that his hardware would not support anyway). There may be some other trick to that too since it certainly seems to exist as a codec in this file: ./cinelerra-5.1/thirdparty/ffmpeg-6.1/libavcodec/allcodecs.c
In comparison I get this list from Packman's ffmpeg 6.0.1 on Tumbleweed-Slowroll:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1) V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
ffmpeg -hwaccels -hide_banner Hardware acceleration methods: vdpau cuda vaapi qsv drm vulkan
пт, 15 дек. 2023 г., 02:18 Phyllis Smith <[email protected]>:
# ./thirdparty/ffmpeg-6.1/ffmpeg -encoders | grep av1 V....D *libaom-av1* libaom AV1 (codec av1) A....D *wmav1 * Windows Media Audio 1
Hm, I wonder why so few av1 encoders are enabled?
Because additional ones tend to have external dependencies we normally do not carry? Also, at least on aarch64 librav1e was a bit of disappointment, at least on default settings it was SLOW.
In addition to what Andrew reported, when building FFmpeg, you have to specifically *enable libsvtav1* which has not been done, but could be if someone tests that and finds it useful.
But what is actually more interesting is that there is still no vaapi_av1 which is what Andrea was trying to get working (just to find out that his hardware would not support anyway). There may be some other trick to that too since it certainly seems to exist as a codec in this file: ./cinelerra-5.1/thirdparty/ffmpeg-6.1/libavcodec/allcodecs.c
may be libva should be new enough? And/or oneVPL framework ...
In comparison I get this list from Packman's ffmpeg 6.0.1 on Tumbleweed-Slowroll:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1) V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
ffmpeg -hwaccels -hide_banner Hardware acceleration methods: vdpau cuda vaapi qsv drm vulkan
Den 11.12.2023 14:23, skrev Andrew Randrianasulu:
пн, 11 дек. 2023 г., 16:13 Terje J. Hanssen via Cin <[email protected]>:
Den 08.12.2023 23:56, skrev Terje J. Hanssen:
Den 08.12.2023 12:50, skrev Andrew Randrianasulu:
пт, 8 дек. 2023 г., 13:57 Andrew Randrianasulu <[email protected]>:
пт, 8 дек. 2023 г., 13:37 Terje J. Hanssen via Cin <[email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs:
* Featuring 8 Xe-cores, the*A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. * Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16
That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?)
well, despite so much time spend looking at dev process for mesa3d I still do not know full details and media encoder process. But isn't it like putting uncompressed frame in vram (as long as you have enough of it - so probably n raw frames between keyframe ideally?) let media engine chw on it, pull resulting compressed bitstream out of vram via pci-express?
So I speculate pcie bandwidth in itself will only matter if you compress both big frame size and long keyframes, so dma engine on card must constantly pump new raw frame data via bus.
I saw some mention of big (resizeable) BAR as requirement for good performance, but opengl/vulkan IMO a bit different because they send often big amount of tiny objects (vertices) via bus for each frame. But may be default 256 Mb in size bar feels a bit small for sending like 1 second of 25 4k frames (300 mb/s)?
Nothing would be better than that A380 does work with older PCIe 3.0 motherboards and CPUs and without too much decrease in performance.
Then I got the following reply to my support request from ASRock TSD regarding https://www.asrock.com/Graphics-Card/Intel/Intel%20Arc%20A380%20Challenger%2...
Skylake platform does not match the system minimum requirements. Please refer to the below link for further information. https://www.intel.com/content/www/us/en/support/articles/000091128/graphics....
well, if you can get card for brief (two weeks?) testing and return if it really does not work - it will be better than leaning on official answer, IMO.
after all, Intel, like any company tries to sell you a bridge .....
Yes, they always want to sell new hardware and do not want to support older boxes longer than required. So I may give it try on the new year. The point is to get av1 encoding to faster with gpu hwaccel, even if it seems to be limited to about 75% speed: Today I also got confirmed from MSI technical support: BIOS of Z170-A Pro MB doesn’t have Resizable (Re-Size) BAR support, the mainboard doesn’t support Intel Arc A380 GPU. For the MB that support Resizable BAR(Re-Size BAR), please find the Intel/AMD chipse https://www.msi.com/news/detail/MSIIsReadyToSupportResizableBARReSizeBARForN...
I've also extracted from the following two articles:
Intel Arc Desktop Graphics Card Gets Requirement List: Resizable BAR Enabled & Support on 10th Gen and Above CPUs
https://wccftech.com/intel-arc-desktop-graphics-card-gets-requirement-list-r... /We are supporting Intel platforms with resizable BAR and will add support for AMD platforms with Smart Access Memory as Intel Arc graphics cards become available for sale as components. Motherboard requirement:/
* Full-size PCIe 3.0 (or newer) x16 slot * Resizeable BAR
Arc A770 Loses Up to 24 Percent Performance Without Resizable Bar | Tom's Hardware
https://www.tomshardware.com/news/arc-a770-loses-25-percent-performance-with...
* Arc isn't for older systems. * Intel has revitalized the midrange graphics card market with the company's latest Arc A770, which will make its way into the list of best graphics cards. Starting at $329, the Arc Alchemist graphics card brings GeForce RTX 3060-like performance to the table with Resizable BAR (ReBAR) enabled, of course. But, without ReBAR or similar technology like Smart Access Memory (SAM), it's another story.
* With Arc, Intel recommends potential consumers make sure their systems support ReBAR or SAM.
* In addition to testing ReBAR, TechPowerUp also evaluated whether the speed of the expansion slot impacts the Arc A770's performance. As a reminder, the Arc A770 comes with a conventional PCIe 4.0 x16 interface. However, the tests revealed that PCIe 3.0 is still plenty for the Arc A770 as long as ReBAR is enabled. Furthermore, TechPowerUp only recorded a performance difference of up to 2% between PCIe 3.0 and PCIe 4.0, so ReBAR support is more important than the expansion slot. Regarding ReBAR, only Intel 10th Generation Comet Lake <https://www.tomshardware.com/news/intel-comet-lake-s-cores-53-ghz-high-power-better-pricing>, 11th Generation Rocket Lake <https://www.tomshardware.com/news/intel-11th-gen-rocket-lake-s-specifications-pricing>, and 12th Generation Alder Lake <https://www.tomshardware.com/features/intel-shares-alder-lake-pricing-specs-and-gaming-performance> processors support that feature. As for AMD, SAM support is only present on Ryzen 3000 <https://www.tomshardware.com/news/amd-third-gen-ryzen-7nm-launch-intel-cpu,39449.html> Zen 2 chips and newer. So while Arc's performance looks attractive and priced fairly, its requirements effectively lock out users with older systems. Arc also demands Windows 10 20H2 or Windows 11 <https://www.tomshardware.com/tag/windows-11> as the operating system, so Windows 7 users, who are reluctant to upgrade, are also out of the picture.
https://forums.gentoo.org/viewtopic-t-1165048.html?sid=1b9518b86afdcd1fa5e77...
not exactly about av1 in ffmpeg 6.1 but lists some components you need for vaapi/qsv encoder on Arc 380 - also from dmesg resizeable bar support is not essential ?
gpus today use their own memory paging system, so may be this add additional restriction on how fast you can push frames to them. ....
Also, windows and Linux drivers might differ ( I bet most reviews are from windows land).
May be someone will post linux review of this particular aspect of Arc graphics, either video or text ...
If this Suse Studio service still works may be you can compose your own live image with all components required to test that and walk to some offline place where you can testdrive new card .... { If weather feels favourable enough - we have around -14 C airtemp so I and my dog prefer short dashes around and back to warm place shortly}
My existing Skylake WS 2) above has PCie 3.0 only.
PCIe 4.0 https://no.wikipedia.org/wiki/PCI_Express https://www.techreviewer.com/learn-about-tech/what-is-pcie-40/
Motherboards Support PCIe 4.0 https://www.makeuseof.com/best-budget-pcie-4-motherboards/ https://www.techreviewer.com/tech-answers/which-motherboards-support-pcie-40...
Maybe also information of interest for WS building will be clarified within a week, when Intel release their new "Meteor Lake, Core Ultra mobile processors(?) https://en.wikipedia.org/wiki/Meteor_Lake
References: AV1 Encoding on a Budget: The Intel Arc A380 Approach https://medium.com/@contact_45426/av1-encoding-on-a-budget-the-intel-arc-a38... https://history-computer.com/intel-arc-a380-full-review-of-intels-entry-leve...
AV1 fixed-function hardware encoder is included in Alchemist GPUs as part of the Intel Quick Sync Video core. https://en.wikipedia.org/wiki/Intel_Arc#Alchemist https://en.wikipedia.org/wiki/AV1#Hardware https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
ср, 13 дек. 2023 г., 19:02 Terje J. Hanssen <[email protected]>:
Den 11.12.2023 14:23, skrev Andrew Randrianasulu:
пн, 11 дек. 2023 г., 16:13 Terje J. Hanssen via Cin < [email protected]>:
Den 08.12.2023 23:56, skrev Terje J. Hanssen:
Den 08.12.2023 12:50, skrev Andrew Randrianasulu:
пт, 8 дек. 2023 г., 13:57 Andrew Randrianasulu <[email protected]>:
пт, 8 дек. 2023 г., 13:37 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
A budget friendly first "AV1 HW upgrade" of the workstation 2) if possible, would be to add a new GPU as Intel Arc A380. But the question is if this will work at all on that much older (2015) Skylake platform with i7-6700K CPU? I've seen CPU bottlenecks has been mentioned and that Arc A380 is targeted at newer generations CPU ...
Extracted from the first wikipedia reference below about Intel Alchemist GPUs:
- Featuring 8 Xe-cores, the* A380 supports PCI Express 4.0* and has a total board power (TBP) of 75W. The graphics card is equipped with 6GB GDDR6 memory and a graphics memory interface of 96 bits, providing a memory bandwidth of 186GB/s. - Bus interface A380: PCIe 4.0 x8 and for >=A580: PCIe 4.0 x16
That is, the keyword here seems to be PCIe 4.0 bus speed as a requirement to utilize the Arc A380 GPU for HWA AV1 encoding (maybe also for other GPUs?)
well, despite so much time spend looking at dev process for mesa3d I still do not know full details and media encoder process. But isn't it like putting uncompressed frame in vram (as long as you have enough of it - so probably n raw frames between keyframe ideally?) let media engine chw on it, pull resulting compressed bitstream out of vram via pci-express?
So I speculate pcie bandwidth in itself will only matter if you compress both big frame size and long keyframes, so dma engine on card must constantly pump new raw frame data via bus.
I saw some mention of big (resizeable) BAR as requirement for good performance, but opengl/vulkan IMO a bit different because they send often big amount of tiny objects (vertices) via bus for each frame. But may be default 256 Mb in size bar feels a bit small for sending like 1 second of 25 4k frames (300 mb/s)?
Nothing would be better than that A380 does work with older PCIe 3.0 motherboards and CPUs and without too much decrease in performance.
Then I got the following reply to my support request from ASRock TSD regarding
https://www.asrock.com/Graphics-Card/Intel/Intel%20Arc%20A380%20Challenger%2...
Skylake platform does not match the system minimum requirements. Please refer to the below link for further information.
https://www.intel.com/content/www/us/en/support/articles/000091128/graphics....
well, if you can get card for brief (two weeks?) testing and return if it
really does not work - it will be better than leaning on official answer, IMO.
after all, Intel, like any company tries to sell you a bridge .....
Yes, they always want to sell new hardware and do not want to support older boxes longer than required. So I may give it try on the new year. The point is to get av1 encoding to faster with gpu hwaccel, even if it seems to be limited to about 75% speed:
Today I also got confirmed from MSI technical support:
BIOS of Z170-A Pro MB doesn’t have Resizable (Re-Size) BAR support, the mainboard doesn’t support Intel Arc A380 GPU. For the MB that support Resizable BAR(Re-Size BAR), please find the Intel/AMD chipse
https://www.msi.com/news/detail/MSIIsReadyToSupportResizableBARReSizeBARForN...
This is Reddit so take it with mountain of salt, but https://www.reddit.com/r/AV1/comments/17pv7gu/whats_your_intel_arc_hw_av1_en... ==== quote ==== r/AV1 <https://www.reddit.com/r/AV1/> 1 mo. ago SeaOfTorment <https://www.reddit.com/user/SeaOfTorment/> Whats your Intel Arc HW AV1 Encoding speeds? Hello! I recently got an Asrock Intel Arc A380 Low Profile 6GB card and the first thign I did when i get it, I replaced my gpu with it to test the encoding speed, I installed all the arc drivers (Intel Driver Assistance did everything), restarted and went to handbrake, selected screen recording I recorded with H264 using Geforce Shadowplay, select AV1 QSYNC (or something like that), I selected quality and the encoding speed was about 45-60, I've tested other A380s that require vga power using cable and they've had speeds of like 140-160, what gives? I want to compare mine with other people, currently I don't have rebar enabled and the pcie lane speed is pcie x8 3.0, i've tested a380s with identical systems and got 140-160 just fine, I do have nvidia drivers too in the same system, but I doubt it's that.
==== quote end. And other users reported up to 250 fps on 1080p transcode. 70 fps is for 4k. I guess this was on Windows machine. So *may be* resizeable PCIE bar is not as hard requirement as it touted to be? it also interesting to see that your machine already can go quite fast with SVT-AV1 in software mode. {snip}
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread). This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1 To start with the workstation 2) above, I want suggestions how to test the possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings. System output as background info: fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1) V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1 libaom3 v. 3,7.1 libSvtAv1Enc1 v. 1.7.0 libva-vdpau-driver v. 0.7.4 vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc --------------- inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram ------------------
вс, 10 дек. 2023 г., 20:32 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread).
This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1
To start with the workstation 2) above, I want suggestions how to test the possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings.
System output as background info:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1)
From phoronix articles librav1e and SVT-AV1 should be faster, but sometimes
at quality cost. Sorry, not tried them personally due to svt demanding 64-bit system and rav1e demanding rust. So for this task you are on your own .. sorry!
V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
libaom3 v. 3,7.1
libSvtAv1Enc1 v. 1.7.0
libva-vdpau-driver v. 0.7.4
vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
---------------
inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
------------------
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
On 12/10/23 18:37, Andrew Randrianasulu wrote:
вс, 10 дек. 2023 г., 20:32 Terje J. Hanssen via Cin <[email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread).
This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1
To start with the workstation 2) above, I want suggestions how to test the possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings.
System output as background info:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1)
From phoronix articles librav1e and SVT-AV1 should be faster, but sometimes at quality cost.
Sorry, not tried them personally due to svt demanding 64-bit system and rav1e demanding rust.
So for this task you are on your own .. sorry!
Ok, I leave those out here for now. The actual rest seems to be libaom-av1 and av1_nvenc I also wonder if there is a ffmpeg code line or equivalent behind the av1.webm profile that can be tested?
V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
libaom3 v. 3,7.1
libSvtAv1Enc1 v. 1.7.0
libva-vdpau-driver v. 0.7.4
vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
---------------
inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
------------------
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
вс, 10 дек. 2023 г., 21:03 Terje J. Hanssen <[email protected]>:
On 12/10/23 18:37, Andrew Randrianasulu wrote:
вс, 10 дек. 2023 г., 20:32 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread).
This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1
To start with the workstation 2) above, I want suggestions how to test the possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings.
System output as background info:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1)
From phoronix articles librav1e and SVT-AV1 should be faster, but sometimes at quality cost.
Sorry, not tried them personally due to svt demanding 64-bit system and rav1e demanding rust.
So for this task you are on your own .. sorry!
Ok, I leave those out here for now. The actual rest seems to be libaom-av1 and av1_nvenc
I think nvidia hw only started to support av1 in latest 4000 series ? So no help on gt730 ...
I also wonder if there is a ffmpeg code line or equivalent behind the av1.webm profile that can be tested?
well, I think you can just put all arguments in one line ?
V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
libaom3 v. 3,7.1
libSvtAv1Enc1 v. 1.7.0
libva-vdpau-driver v. 0.7.4
vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
---------------
inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
------------------
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
вс, 10 дек. 2023 г., 20:37 Andrew Randrianasulu <[email protected]>:
вс, 10 дек. 2023 г., 20:32 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread).
This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1
To start with the workstation 2) above, I want suggestions how to test the possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings.
System output as background info:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1)
From phoronix articles librav1e and SVT-AV1 should be faster, but sometimes at quality cost.
Sorry, not tried them personally due to svt demanding 64-bit system and rav1e demanding rust.
So for this task you are on your own .. sorry!
https://ottverse.com/analysis-of-svt-av1-presets-and-crf-values/ may be crf 26 (ish) and preset 6 ? On 36 core machine with avx512 it surely was fast, but on 4c .. I guess 1.25 fps or so will be best you can get? (for fullhd source)
V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
libaom3 v. 3,7.1
libSvtAv1Enc1 v. 1.7.0
libva-vdpau-driver v. 0.7.4
vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
---------------
inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
------------------
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 10.12.2023 19:04, skrev Andrew Randrianasulu:
вс, 10 дек. 2023 г., 20:37 Andrew Randrianasulu <[email protected]>:
вс, 10 дек. 2023 г., 20:32 Terje J. Hanssen via Cin <[email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread).
This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1
I took my first AV1 rendering test with CinGGs default av1.webm preset by loading a standard SD DV file clip. du -sh dv* 389M dv01_07.dv 30M dv01_07.webm ffprobe -hide_banner dv01_07.dv [dv @ 0x5595e79b4580] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv01_07.dv': Metadata: timecode : 01:09:35:09 Duration: 00:01:53.28, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 25000 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s ffprobe -hide_banner dv01_07.webm [libdav1d @ 0x560ccddb3380] libdav1d 1.0.0 Input #0, matroska,webm, from 'dv01_07.webm': Metadata: ENCODER : Lavf60.16.100 Duration: 00:01:53.28, start: 0.000000, bitrate: 2220 kb/s Stream #0:0: Video: av1 (Main), yuv420p(tv, bt470bg/unknown/unknown), 720x576 [SAR 1:1 DAR 5:4], 25 fps, 25 tbr, 1k tbn, 1k tbc Metadata: DURATION : 00:01:53.243000000 Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp Metadata: DURATION : 00:01:53.281000000 Rendering took 0:03:33 or 1.87 x the Duration This webm file was displayed ok in VLC and FFplay on Leap 15.5
To start with the workstation 2) above, I want suggestions how to test the possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings.
System output as background info:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1)
From phoronix articles librav1e and SVT-AV1 should be faster, but sometimes at quality cost.
Sorry, not tried them personally due to svt demanding 64-bit system and rav1e demanding rust.
So for this task you are on your own .. sorry!
https://ottverse.com/analysis-of-svt-av1-presets-and-crf-values/
may be crf 26 (ish) and preset 6 ?
On 36 core machine with avx512 it surely was fast, but on 4c .. I guess 1.25 fps or so will be best you can get? (for fullhd source)
V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
libaom3 v. 3,7.1
libSvtAv1Enc1 v. 1.7.0
libva-vdpau-driver v. 0.7.4
vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
---------------
inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
------------------
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 11.12.2023 00:02, skrev Terje J. Hanssen:
Den 10.12.2023 19:04, skrev Andrew Randrianasulu:
вс, 10 дек. 2023 г., 20:37 Andrew Randrianasulu <[email protected]>:
вс, 10 дек. 2023 г., 20:32 Terje J. Hanssen via Cin <[email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread).
This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1
I took my first AV1 rendering test with CinGGs default av1.webm preset by loading a standard SD DV file clip.
du -sh dv* 389M dv01_07.dv 30M dv01_07.webm
ffprobe -hide_banner dv01_07.dv [dv @ 0x5595e79b4580] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv01_07.dv': Metadata: timecode : 01:09:35:09 Duration: 00:01:53.28, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 25000 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
ffprobe -hide_banner dv01_07.webm [libdav1d @ 0x560ccddb3380] libdav1d 1.0.0 Input #0, matroska,webm, from 'dv01_07.webm': Metadata: ENCODER : Lavf60.16.100 Duration: 00:01:53.28, start: 0.000000, bitrate: 2220 kb/s Stream #0:0: Video: av1 (Main), yuv420p(tv, bt470bg/unknown/unknown), 720x576 [SAR 1:1 DAR 5:4], 25 fps, 25 tbr, 1k tbn, 1k tbc Metadata: DURATION : 00:01:53.243000000 Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp Metadata: DURATION : 00:01:53.281000000
Rendering took 0:03:33 or 1.87 x the Duration This webm file was displayed ok in VLC and FFplay on Leap 15.5
SVT-AV1 re-encoding --------------------------------- I will add the re-encoded sample SD DV file using ffmpeg SVT-AV1, as I was positive surprised how much faster (preset 10 about 25 sec) it was than rendering AV1 with CinGG (libaom?) . I've tested three presets: 8, 10 and 12. "Useable visible quality" for all. ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 8 -crf 35 -c:a libvorbis dv01_07_svt-av1_pr8.webm frame= 2832 fps= 66 q=35.0 Lsize= 28836kB time=00:01:53.26 bitrate=2085.6kbits/s speed=2.65x ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 10 -crf 35 -c:a libvorbis dv01_07_svt-av1_pr10.webm frame= 2832 fps=112 q=35.0 Lsize= 34419kB time=00:01:53.26 bitrate=2489.4kbits/s speed=4.47x ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 12 -crf 35 -c:a libvorbis dv01_07_svt-av1_pr12.webm frame= 2832 fps=262 q=35.0 Lsize= 35913kB time=00:01:53.26 bitrate=2597.5kbits/s speed=10.5x du -sh * 30M dv01_07_av1_cingg.webm 389M dv01_07.dv 34M dv01_07_svt-av1_pr10.webm 36M dv01_07_svt-av1_pr12.webm 29M dv01_07_svt-av1_pr8.webm I add full output for preset 10 only: ffprobe -hide_banner dv01_07_svt-sv1_pr10.webm [libdav1d @ 0x55ba878325c0] libdav1d 1.3.0 Input #0, matroska,webm, from 'dv01_07_svt-sv1_pr10.webm': Metadata: TIMECODE : 01:09:35:09 ENCODER : Lavf60.3.100 Duration: 00:01:53.28, start: 0.000000, bitrate: 2488 kb/s Stream #0:0: Video: av1 (Main), yuv420p(tv), 720x576, SAR 16:15 DAR 4:3, 25 fps, 25 tbr, 1k tbn Metadata: ENCODER : Lavc60.3.100 libsvtav1 DURATION : 00:01:53.283000000 Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp Metadata: ENCODER : Lavc60.3.100 libvorbis DURATION : 00:01:53.283000000 [libdav1d @ 0x55ba8788e6c0] libdav1d 1.3.0 ---------- ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 10 -crf 35 -c:a libvorbis dv01_07_svt-sv1_pr10.webm ffmpeg version 6.0.1 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 13 (SUSE Linux) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --incdir=/usr/include/ffmpeg --extra-cflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --optflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --disable-htmlpages --enable-pic --disable-stripping --enable-shared --disable-static --enable-gpl --enable-version3 --disable-openssl --enable-gnutls --enable-ladspa --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libdc1394 --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libjack --enable-libjxl --enable-librist --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopenh264-dlopen --enable-libopus --enable-libpulse --enable-librav1e --enable-librubberband --enable-libsvtav1 --enable-libsoxr --enable-libspeex --enable-libssh --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lto --enable-lv2 --enable-libmfx --enable-vaapi --enable-vdpau --enable-version3 --enable-libfdk-aac-dlopen --enable-nonfree --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libx264 --enable-libx265 --enable-libxvid libavutil 58. 2.100 / 58. 2.100 libavcodec 60. 3.100 / 60. 3.100 libavformat 60. 3.100 / 60. 3.100 libavdevice 60. 1.100 / 60. 1.100 libavfilter 9. 3.100 / 9. 3.100 libswscale 7. 1.100 / 7. 1.100 libswresample 4. 10.100 / 4. 10.100 libpostproc 57. 1.100 / 57. 1.100 [dv @ 0x55c1b0b87380] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv01_07.dv': Metadata: timecode : 01:09:35:09 Duration: 00:01:53.28, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 25000 kb/s, 25 fps, 25 tbr, 25 tbn Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s File 'dv01_07_svt-sv1_pr10.webm' already exists. Overwrite? [y/N] y Stream mapping: Stream #0:0 -> #0:0 (dvvideo (native) -> av1 (libsvtav1)) Stream #0:1 -> #0:1 (pcm_s16le (native) -> vorbis (libvorbis)) Press [q] to stop, [?] for help Svt[info]: ------------------------------------------- Svt[info]: SVT [version]: SVT-AV1 Encoder Lib v1.7.0 Svt[info]: SVT [build] : GCC 13.2.1 20230912 [revision b96e66fd4ef3e36983969fb8cdd1956f551a074b] 64 bit Svt[info]: LIB Build date: Nov 3 2023 00:00:00 Svt[info]: ------------------------------------------- Svt[info]: Number of logical cores available: 8 Svt[info]: Number of PPCS 107 Svt[info]: [asm level on system : up to avx2] Svt[info]: [asm level selected : up to avx2] Svt[info]: ------------------------------------------- Svt[info]: SVT [config]: main profile tier (auto) level (auto) Svt[info]: SVT [config]: width / height / fps numerator / fps denominator : 720 / 576 / 25 / 1 Svt[info]: SVT [config]: bit-depth / color format : 8 / YUV420 Svt[info]: SVT [config]: preset / tune / pred struct : 10 / PSNR / random access Svt[info]: SVT [config]: gop size / mini-gop size / key-frame type : 161 / 32 / key frame Svt[info]: SVT [config]: BRC mode / rate factor : CRF / 35 Svt[info]: ------------------------------------------- Output #0, webm, to 'dv01_07_svt-sv1_pr10.webm': Metadata: timecode : 01:09:35:09 encoder : Lavf60.3.100 Stream #0:0: Video: av1, yuv420p(bottom coded first (swapped)), 720x576 [SAR 16:15 DAR 4:3], q=2-31, 25 fps, 1k tbn Metadata: encoder : Lavc60.3.100 libsvtav1 Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp Metadata: encoder : Lavc60.3.100 libvorbis frame= 2832 fps=112 q=35.0 Lsize= 34419kB time=00:01:53.26 bitrate=2489.4kbits/s speed=4.47x video:32865kB audio:1495kB subtitle:0kB other streams:0kB global headers:4kB muxing overhead: 0.171717%
To start with the workstation 2) above, I want suggestions how to test the possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings.
System output as background info:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1)
From phoronix articles librav1e and SVT-AV1 should be faster, but sometimes at quality cost.
Sorry, not tried them personally due to svt demanding 64-bit system and rav1e demanding rust.
So for this task you are on your own .. sorry!
https://ottverse.com/analysis-of-svt-av1-presets-and-crf-values/
may be crf 26 (ish) and preset 6 ?
On 36 core machine with avx512 it surely was fast, but on 4c .. I guess 1.25 fps or so will be best you can get? (for fullhd source)
V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
libaom3 v. 3,7.1
libSvtAv1Enc1 v. 1.7.0
libva-vdpau-driver v. 0.7.4
vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
---------------
inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
------------------
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
чт, 14 дек. 2023 г., 01:53 Terje J. Hanssen <[email protected]>:
Den 11.12.2023 00:02, skrev Terje J. Hanssen:
Den 10.12.2023 19:04, skrev Andrew Randrianasulu:
вс, 10 дек. 2023 г., 20:37 Andrew Randrianasulu <[email protected]>:
вс, 10 дек. 2023 г., 20:32 Terje J. Hanssen via Cin < [email protected]>:
Den 03.12.2023 22:29, skrev Terje J. Hanssen:
Already touched this topic barely in another thread https://lists.cinelerra-gg.org/pipermail/cin/2023-December/007346.html
But so many SW and HW pieces are mentioned around, it is almost a full-time reading and study: VAAPI, MESA, VULKAN, Intel Quick Sync Video etc......
I realize my aging hardware which is fast enough for other tasks, needs some "AV1 upgrade", if possible.
But first I wonder, what is expected possible to do (obtain) with AV1 de-/encoding on my existing 64bit hardware:
1) laptop 2018: Dell XPS 13-9370: quad core i7-8550U CPU (8. gen Kabylake) and Intel UHD Graphics
2) WS infinity: MSI Z170A mobo: quad core i7-6700K CPU (6. gen Skylake), NVIDIA GeForce GT-730 graphics
I continue the "AV1 de-/encoding on my existing 64bit hardware" question above as a branch here (instead of a new related thread).
This part is also related to another 2021 thread, [Cin] tried to update av1.webm profile https://www.mail-archive.com/[email protected]/msg02804.html which refere to FFmpeg's AV1 Video Encoding Guide https://trac.ffmpeg.org/wiki/Encode/AV1
I took my first AV1 rendering test with CinGGs default av1.webm preset by loading a standard SD DV file clip.
du -sh dv* 389M dv01_07.dv 30M dv01_07.webm
ffprobe -hide_banner dv01_07.dv [dv @ 0x5595e79b4580] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv01_07.dv': Metadata: timecode : 01:09:35:09 Duration: 00:01:53.28, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 25000 kb/s, 25 fps, 25 tbr, 25 tbn, 25 tbc Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s
ffprobe -hide_banner dv01_07.webm [libdav1d @ 0x560ccddb3380] libdav1d 1.0.0 Input #0, matroska,webm, from 'dv01_07.webm': Metadata: ENCODER : Lavf60.16.100 Duration: 00:01:53.28, start: 0.000000, bitrate: 2220 kb/s Stream #0:0: Video: av1 (Main), yuv420p(tv, bt470bg/unknown/unknown), 720x576 [SAR 1:1 DAR 5:4], 25 fps, 25 tbr, 1k tbn, 1k tbc Metadata: DURATION : 00:01:53.243000000 Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp Metadata: DURATION : 00:01:53.281000000
Rendering took 0:03:33 or 1.87 x the Duration This webm file was displayed ok in VLC and FFplay on Leap 15.5
SVT-AV1 re-encoding --------------------------------- I will add the re-encoded sample SD DV file using ffmpeg SVT-AV1, as I was positive surprised how much faster (preset 10 about 25 sec) it was than rendering AV1 with CinGG (libaom?) . I've tested three presets: 8, 10 and 12. "Useable visible quality" for all.
Good! If you come to rebuilding cingg on your machine you can always try to add "--enable-libsvtav1" for embedded ffmpeg, along with libs (`pkg-config --libs svtav1` probably?) and create new profile, even if by default we do not use this encoder.
ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 8 -crf 35 -c:a libvorbis dv01_07_svt-av1_pr8.webm frame= 2832 fps= 66 q=35.0 Lsize= 28836kB time=00:01:53.26 bitrate=2085.6kbits/s speed=2.65x
ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 10 -crf 35 -c:a libvorbis dv01_07_svt-av1_pr10.webm frame= 2832 fps=112 q=35.0 Lsize= 34419kB time=00:01:53.26 bitrate=2489.4kbits/s speed=4.47x
ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 12 -crf 35 -c:a libvorbis dv01_07_svt-av1_pr12.webm frame= 2832 fps=262 q=35.0 Lsize= 35913kB time=00:01:53.26 bitrate=2597.5kbits/s speed=10.5x
du -sh * 30M dv01_07_av1_cingg.webm 389M dv01_07.dv 34M dv01_07_svt-av1_pr10.webm 36M dv01_07_svt-av1_pr12.webm 29M dv01_07_svt-av1_pr8.webm
I add full output for preset 10 only:
ffprobe -hide_banner dv01_07_svt-sv1_pr10.webm [libdav1d @ 0x55ba878325c0] libdav1d 1.3.0 Input #0, matroska,webm, from 'dv01_07_svt-sv1_pr10.webm': Metadata: TIMECODE : 01:09:35:09 ENCODER : Lavf60.3.100 Duration: 00:01:53.28, start: 0.000000, bitrate: 2488 kb/s Stream #0:0: Video: av1 (Main), yuv420p(tv), 720x576, SAR 16:15 DAR 4:3, 25 fps, 25 tbr, 1k tbn Metadata: ENCODER : Lavc60.3.100 libsvtav1 DURATION : 00:01:53.283000000 Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp Metadata: ENCODER : Lavc60.3.100 libvorbis DURATION : 00:01:53.283000000 [libdav1d @ 0x55ba8788e6c0] libdav1d 1.3.0
----------
ffmpeg -i dv01_07.dv -c:v libsvtav1 -preset 10 -crf 35 -c:a libvorbis dv01_07_svt-sv1_pr10.webm ffmpeg version 6.0.1 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 13 (SUSE Linux) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --incdir=/usr/include/ffmpeg --extra-cflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --optflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --disable-htmlpages --enable-pic --disable-stripping --enable-shared --disable-static --enable-gpl --enable-version3 --disable-openssl --enable-gnutls --enable-ladspa --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libdc1394 --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libjack --enable-libjxl --enable-librist --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopenh264-dlopen --enable-libopus --enable-libpulse --enable-librav1e --enable-librubberband --enable-libsvtav1 --enable-libsoxr --enable-libspeex --enable-libssh --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lto --enable-lv2 --enable-libmfx --enable-vaapi --enable-vdpau --enable-version3 --enable-libfdk-aac-dlopen --enable-nonfree --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libx264 --enable-libx265 --enable-libxvid libavutil 58. 2.100 / 58. 2.100 libavcodec 60. 3.100 / 60. 3.100 libavformat 60. 3.100 / 60. 3.100 libavdevice 60. 1.100 / 60. 1.100 libavfilter 9. 3.100 / 9. 3.100 libswscale 7. 1.100 / 7. 1.100 libswresample 4. 10.100 / 4. 10.100 libpostproc 57. 1.100 / 57. 1.100 [dv @ 0x55c1b0b87380] Estimating duration from bitrate, this may be inaccurate Input #0, dv, from 'dv01_07.dv': Metadata: timecode : 01:09:35:09 Duration: 00:01:53.28, start: 0.000000, bitrate: 28800 kb/s Stream #0:0: Video: dvvideo, yuv420p, 720x576 [SAR 16:15 DAR 4:3], 25000 kb/s, 25 fps, 25 tbr, 25 tbn Stream #0:1: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s File 'dv01_07_svt-sv1_pr10.webm' already exists. Overwrite? [y/N] y Stream mapping: Stream #0:0 -> #0:0 (dvvideo (native) -> av1 (libsvtav1)) Stream #0:1 -> #0:1 (pcm_s16le (native) -> vorbis (libvorbis)) Press [q] to stop, [?] for help Svt[info]: ------------------------------------------- Svt[info]: SVT [version]: SVT-AV1 Encoder Lib v1.7.0 Svt[info]: SVT [build] : GCC 13.2.1 20230912 [revision b96e66fd4ef3e36983969fb8cdd1956f551a074b] 64 bit Svt[info]: LIB Build date: Nov 3 2023 00:00:00 Svt[info]: ------------------------------------------- Svt[info]: Number of logical cores available: 8 Svt[info]: Number of PPCS 107 Svt[info]: [asm level on system : up to avx2] Svt[info]: [asm level selected : up to avx2] Svt[info]: ------------------------------------------- Svt[info]: SVT [config]: main profile tier (auto) level (auto) Svt[info]: SVT [config]: width / height / fps numerator / fps denominator : 720 / 576 / 25 / 1 Svt[info]: SVT [config]: bit-depth / color format : 8 / YUV420 Svt[info]: SVT [config]: preset / tune / pred struct : 10 / PSNR / random access Svt[info]: SVT [config]: gop size / mini-gop size / key-frame type : 161 / 32 / key frame Svt[info]: SVT [config]: BRC mode / rate factor : CRF / 35 Svt[info]: ------------------------------------------- Output #0, webm, to 'dv01_07_svt-sv1_pr10.webm': Metadata: timecode : 01:09:35:09 encoder : Lavf60.3.100 Stream #0:0: Video: av1, yuv420p(bottom coded first (swapped)), 720x576 [SAR 16:15 DAR 4:3], q=2-31, 25 fps, 1k tbn Metadata: encoder : Lavc60.3.100 libsvtav1 Stream #0:1: Audio: vorbis, 48000 Hz, stereo, fltp Metadata: encoder : Lavc60.3.100 libvorbis frame= 2832 fps=112 q=35.0 Lsize= 34419kB time=00:01:53.26 bitrate=2489.4kbits/s speed=4.47x video:32865kB audio:1495kB subtitle:0kB other streams:0kB global headers:4kB muxing overhead: 0.171717%
To start with the workstation 2) above, I want suggestions how to test the
possible AV1 encoding options (libaom, SVT-AV1, MESA, VAAPI, VDPAU) using my system enabled ffmpeg 6.0.1 commands,, and also suggestions to required change in system/graphics settings.
System output as background info:
fmpeg -encoders -hide_banner | grep av1 V....D libaom-av1 libaom AV1 (codec av1) V....D librav1e librav1e AV1 (codec av1)
From phoronix articles librav1e and SVT-AV1 should be faster, but sometimes at quality cost.
Sorry, not tried them personally due to svt demanding 64-bit system and rav1e demanding rust.
So for this task you are on your own .. sorry!
https://ottverse.com/analysis-of-svt-av1-presets-and-crf-values/
may be crf 26 (ish) and preset 6 ?
On 36 core machine with avx512 it surely was fast, but on 4c .. I guess 1.25 fps or so will be best you can get? (for fullhd source)
V..... libsvtav1 SVT-AV1(Scalable Video Technology for AV1) encoder (codec av1) V....D av1_nvenc NVIDIA NVENC av1 encoder (codec av1) V....D av1_amf AMD AMF AV1 encoder (codec av1) A....D wmav1 Windows Media Audio 1
libaom3 v. 3,7.1
libSvtAv1Enc1 v. 1.7.0
libva-vdpau-driver v. 0.7.4
vainfo Trying display: wayland error: XDG_RUNTIME_DIR is invalid or not set in the environment. Trying display: x11 libva info: VA-API version 1.20.0 libva info: Trying to open /usr/lib64/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_20 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.20 (libva 2.20.0) vainfo: Driver version: Mesa Gallium driver 23.2.1 for NV106 vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
---------------
inxi -zdGCS System: Kernel: 6.6.1-1-default arch: x86_64 bits: 64 Desktop: GNOME v: 45.1 Distro: openSUSE Tumbleweed-Slowroll 20231119 CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/4200 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: NVIDIA GK208B [GeForce GT 730] driver: nouveau v: kernel Device-2: Microdia Camera driver: snd-usb-audio,uvcvideo type: USB Device-3: MACROSILICON USB3.0 UHD driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB Display: server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 driver: X: loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau resolution: 2560x1440~60Hz API: OpenGL v: 4.3 vendor: mesa v: 23.2.1 renderer: NV106 API: EGL Message: EGL data requires eglinfo. Check --recommends. Drives: Local Storage: total: 8.8 TiB used: 5.02 TiB (57.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: MZVPV512HDGL-00000 size: 476.94 GiB ID-2: /dev/sda vendor: Intel model: SSDSA2CW160G3 size: 149.05 GiB ID-3: /dev/sdb vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-4: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB ID-5: /dev/sdd vendor: Seagate model: Expansion HDD size: 7.28 TiB type: USB Optical-1: /dev/sr0 vendor: HL-DT-ST model: BD-RE BH10LS30 dev-links: cdrom Features: speed: 40 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
------------------
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
participants (5)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith -
Stefan de Konink -
Terje J. Hanssen