Terje, I am building an AppImage now and will let you know when it is available.
I also read your next email of your test results.  But if you have the time, I would still appreciate you testing the appimage I will be downloading since it is the default one that will go out to the users on Dec. 31.

did not have the correct Nvidia hardware or software.  Why? I do not know but will try one more later.
The above is my problem also and the one computer that I did the previous test on and is quoted in the manual, was updated without the Nvidia drivers.  More later.  Thanks for the help.


On Tue, Dec 24, 2024 at 5:29 AM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:



Den 24.12.2024 00:58, skrev Phyllis Smith:
Downloaded latest version of nv-codec-headers release and built CinGG with it and no problems here.  Unfortunately the 4 different computers I attempted to test on did not have the correct Nvidia hardware or software.  Why? I do not know but will try one more later.

If you want and have a test download, I can give it a try on my legacy GF GTX 960 SkyLake workstation, to see if your new AppImage (still) works as previously.


On Sat, Dec 21, 2024 at 4:04 PM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:


вс, 22 дек. 2024 г., 01:53 Phyllis Smith <phylsmith2017@gmail.com>:
Andrew,
most likely our nv headers drifted from that ffmpeg-7.0/proprietary driver assumes at runtime.
I have been wondering about nv-codec-headers as we are at:
but I am unsure about updating to:
because if you look at:
the release versions go from 12.xx to 8.x and it is really weird AND there is no year on the release dates but just day and month.
Since it is such an important part of ffmpeg inside CinGG, I am concerned but will at least try the 12.2.72.0 just to see what it does.

in theory it should give users of new nvidia hardware av1 encoding ...... but not sure how it will work with older drivers and hardware.





you can try to install something like nv-codec-headers and then add