<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">пт, 6 дек. 2024 г., 05:14 Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com" target="_blank" rel="noreferrer">terjejhanssen@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<br>
<br>
<br>
<div>Den 06.12.2024 01:08, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">пт, 6 дек. 2024 г., 02:06
Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com" rel="noreferrer noreferrer" target="_blank">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
<br>
<br>
<div>Den 03.12.2024 22:20, skrev Andrew Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">вт, 3 дек.
2024 г., 23:59 Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
From a previous thread:<br>
Re: [Cin] another set of test profiles<br>
<br>
<div>Den 18.10.2024 02:08, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">чт,
17 окт. 2024 г., 15:06 Terje J.
Hanssen <<a href="mailto:terjejhanssen@gmail.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
<div>Den 17.10.2024 13:51, skrev
Andrew Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">чт,
17 окт. 2024 г., 13:40
Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
<div>Den 14.10.2024
00:38, skrev
Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">пн, 14 окт. 2024 г., 01:36 Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" rel="noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">phylsmith2017@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_default" style="font-size:small">Andrew, so it seems
prudent to
check into
GIT, the
av1_vaapi.mp4
render format
(after
successfully
tested of
course); but
what about the
QSV encoders?<br>
</div>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">wait
for Terje's
testing OR try
to build
oneVPL-cpu (it
sort of
circles back
to different
branch of
ffmpeg, so
ffmpeg will
think it uses
qsv but it in
fact will use
another ffmpeg
.... well, in
theory! it
does not work
for me on
32-bit!)</div>
<div dir="auto">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
I wonder if Hw
accellerated
encoding support via
Vaapi and QSV is to
be embedded in
future Cingg
Appimage and/or
packages if
possible?<br>
What about a list of
supported
dGPUs/iGPUs?<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Problem is -
QSV/vaapi basically
search for driver
component and this one
might be in different
location on different
distros, and interface
between two also not set
in stone.</div>
<div dir="auto"><br>
</div>
<div dir="auto">For appimage
you can just unpack them
and remove libva.so so on
startup cingg will link to
system's libva.</div>
<div dir="auto"><br>
</div>
<div dir="auto">QSV as we
learned is another layer
with their own runtime
path for yet another set
of driver components. So,
while building libvpl
itself is relatively
easily making sure it
finds its drivers is not
easy (at least for me).</div>
<div dir="auto"><br>
</div>
<div dir="auto">speaking
about GPU list I think it
will be fairly short,
you,Phyllis and Andrea
probably only ones who use
it and report back.
Stephan noticed some
troubles and reverted back
to software. I can test
nvdec/nvenc on livecd but
this is not my everyday
setup (Nvidia proprietary
drivers enforce 64-bit
system).</div>
<div dir="auto"><br>
</div>
<div dir="auto">But well,
feel free to post short
summary of that works on
your GPUs in cingg as
another thread, hopefully
others will chime in!</div>
</div>
</blockquote>
<br>
If we get available a packaged
Cingg test build (rpm/Leap for
me), it would be more useful to
do this test. Then I have
available three gen. Intel,
legacy Skylake/Kabylake iGPUs
and current DG2/Arc GPU. I also
have/had a Nvidia GPU on
Skylake, but it looks like it
past away.<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I think you can build
rpm yourself, but for this we need to
update spec file, so it will point at
new source and add openvpl as
requirements.</div>
<div dir="auto"><br>
</div>
<div dir="auto">In meantime you can
just make your own appimage from just
build cingg-with-system-ffmpeg, so it
hopefully will not be lost after few
system updates.</div>
<div dir="auto"><br>
</div>
<br>
</div>
</blockquote>
<br>
Andrew, <br>
I don't know how busy you are currently with
other tasks, but i case you have time, I
would be interested to fulfill this rpm and
(possibly Appimage) exercise?<br>
That is from my current build with
third-party (internal) ffmpeg7.0.<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">for rpm you need to
edit blds/cinelerra.spec at the very top there is
date, I think latest tar version is </div>
<div dir="auto"><br>
</div>
<div dir="auto"><a href="https://cinelerra-gg.org/download/src/cin_5.1.20241031-src.tgz" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://cinelerra-gg.org/download/src/cin_5.1.20241031-src.tgz</a></div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">so replace 2020 something with
20241031</div>
<div dir="auto"><br>
</div>
<div dir="auto">but then it need to be patched up,
and I do not have tested procedure for doing this.
Probably rpm should wait until new tagged release
.... you can search for rpmbuild command on your
system and read its manpage/help and may be test
run it on some other (faster to rebuild) .spec
file in meantime </div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Appimage should be simpler from
existing source directory</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">just run</div>
<div dir="auto"><br>
</div>
<div dir="auto">bld_appimage.sh</div>
<div dir="auto"><br>
</div>
<div dir="auto">but be sure to get additional file
and put it where it belong as described in
comment:</div>
<div dir="auto">=====</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div dir="auto"># Get the appropriate appimagetool
from <a href="https://github.com/AppImage/AppImageKit/releases" rel="noreferrer noreferrer noreferrer" target="_blank">https://github.com/AppImage/AppImageKit/releases</a></div>
<div dir="auto"># and put it in your path. Only
install the version for your platform</div>
<div dir="auto"># and mark it executable. The file
name must start with "appimagetool".</div>
<div dir="auto"><br>
</div>
<div dir="auto">====</div>
<div dir="auto"><br>
</div>
<div dir="auto">probably /usr/local/bin will be
simplest place to put it as root?</div>
</div>
</div>
</blockquote>
<br>
<font face="Courier New, Courier, monospace">/Cin # sh
./bld_appimage.sh<br>
.....snip<br>
-- Copying files into AppDir -- <br>
Copying file image/cin.desktop to
AppDir/usr/share/applications/cin.desktop <br>
Copying file image/cin.svg to
AppDir/usr/share/icons/hicolor/scalable/apps/cin.svg <br>
<br>
-- Deploying files into AppDir root directory -- <br>
Deploying files to AppDir root using desktop file:
AppDir/usr/share/applications/cin.desktop <br>
Deploying desktop file to AppDir root:
AppDir/usr/share/applications/cin.desktop <br>
Creating symlink for file
AppDir/usr/share/applications/cin.desktop in/as AppDir
<br>
Deploying icon to AppDir root:
AppDir/usr/share/icons/hicolor/scalable/apps/cin.svg <br>
Creating symlink for file
AppDir/usr/share/icons/hicolor/scalable/apps/cin.svg
in/as AppDir <br>
Deploying AppRun symlink for executable in AppDir
root: AppDir/usr/bin/cin <br>
Creating symlink for file AppDir/usr/bin/cin in/as
AppDir/AppRun <br>
Found appimagetool:
/usr/local/bin/appimagetool-x86_64.AppImage<br>
Running command:
/usr/local/bin/appimagetool-x86_64.AppImage
"appimagetool" "AppDir" "</font><br>
<br>
<br>
Thanks, I think I got AppImage(?) built and it seemingly
runs OK.<br>
<br>
That is when I found the CinGG executable file, because
I expected a file somewhere with a name
"CinGG*.AppImage"<br>
<br>
<font face="Courier New, Courier, monospace">/Cin # file
-sh AppDir/*<br>
AppDir/AppRun: symbolic link to usr/bin/cin<br>
AppDir/cin.desktop: symbolic link to
usr/share/applications/cin.desktop<br>
AppDir/cin.svg: symbolic link to
usr/share/icons/hicolor/scalable/apps/cin.svg<br>
AppDir/usr: directory<br>
<br>
<br>
Cin # du -sh AppDir<br>
216M AppDir<br>
<br>
/Cin # du -sh AppDir/*/*<br>
198M AppDir/usr/bin<br>
19M AppDir/usr/lib<br>
100K AppDir/usr/share<br>
<br>
<br>
/Cin # AppDir/usr/bin/cin<br>
Cinelerra Infinity - built: Nov 20 2024 22:06:05<br>
.......<br>
BC_DisplayInfo::gl_fb_config failed<br>
build plugin index for:
/home/cinelerra/cinelerra-5.1/AppDir/usr/bin/plugins<br>
PluginFFilter::new_ffilter(overlay_qsv)<br>
err: Input/output error<br>
PluginFFilter::new_ffilter(hstack_qsv)<br>
err: Operation not permitted<br>
PluginFFilter::new_ffilter(vstack_qsv)<br>
err: Operation not permitted<br>
PluginFFilter::new_ffilter(xstack_qsv)<br>
err: Operation not permitted<br>
build lv2 index for: $CIN_PATH/lv2<br>
build ladspa plugin index for:
/home/cinelerra/cinelerra-5.1/AppDir/usr/bin/ladspa<br>
<br>
Loaded hdv09_04.m2t (tff interlaced)<br>
Tested rendering using preset hevc_qsv_10b420 which
worked fine<br>
<br>
libva info: VA-API version 1.22.0<br>
libva info: Trying to open
/usr/lib64/dri/iHD_drv_video.so<br>
libva info: Found init function __vaDriverInit_1_22<br>
libva info: va_openDriver() returns 0<br>
libva info: VA-API version 1.22.0<br>
libva info: Trying to open
/usr/lib64/dri/iHD_drv_video.so<br>
libva info: Found init function __vaDriverInit_1_22<br>
libva info: va_openDriver() returns 0<br>
Render::render_single: Session finished.<br>
** rendered 5972 frames in 19.320 secs, 309.110 fps<br>
<br>
---------------------------<br>
<br>
So some questions when comparing the above AppDir
result with the pre-build Appimage file I download to
and run from<br>
<br>
<br>
du -sh ~/Applications/Cin*<br>
171M CinGG-20241031-x86_64.AppImage<br>
<br>
./</font><font face="Courier New, Courier, monospace">CinGG-20241031-x86_64.AppImage</font><br>
<font face="Courier New, Courier, monospace"><br>
I notice the prebuild has no symlink as in the above
AppDir<br>
<br>
My own built appimage has not startup errors:<br>
<br>
(AppImageLauncher:127697): GdkPixbuf-CRITICAL **:
23:56:28.831: gdk_pixbuf_get_rowstride: assertion
'GDK_IS_PIXBUF (pixbuf)' failed<br>
<br>
<br>
I wonder the larger total space 216M vs 171M is due to
oneVPL and maybe some other additional libs ?<br>
<br>
How to possibly build an equivalent single AppImage
file directly?<br>
</font></div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">make sure you have mksquashfs installed?</div>
</div>
</blockquote>
<br>
No "mksquashfs" package installed or found, but "quashfs" was
installed.<br>
<br>
<br>
<font face="Courier New, Courier, monospace">Cin # zypper se squash<br>
Loading repository data...<br>
Reading installed packages...<br>
<br>
S | Name |
Summary | Type<br>
---+------------------+----------------------------------------------------+--------<br>
| libsquashfuse0 | FUSE module to mount squashfs
images | package<br>
i | squashfs | A Read-Only File System with Efficient
Compression | package<br>
| squashfuse | FUSE module to mount squashfs
images | package<br>
| squashfuse-devel | FUSE module to mount squashfs
images | package<br>
| squashfuse-tools | Squafs Tools for
squashfsfuse | package</font><br>
<br>
Not sure if they are required, but add-installed also the other on
this list.<br>
<br>
<br>
<blockquote type="cite">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">I think last part (compressing appdir into
single file and bolting on run-time decompressor to it) failed
in your case .....</div>
<br>
</div>
</blockquote>
<font face="Courier New, Courier, monospace"><br>
Tried bld_appimage once more:<br>
<br>
/Cin # sh ./bld_appimage.sh<br>
<br>
..........snip<br>
<br>
Setting rpath in ELF file AppDir/usr/lib/libz.so.1.3.1 to $ORIGIN
<br>
<br>
-- Deploying icons -- <br>
Deploying icon image/cin.svg <br>
<br>
-- Deploying desktop files -- <br>
Deploying desktop file image/cin.desktop <br>
<br>
-- Copying files into AppDir -- <br>
Copying file image/cin.desktop to
AppDir/usr/share/applications/cin.desktop <br>
Copying file image/cin.svg to
AppDir/usr/share/icons/hicolor/scalable/apps/cin.svg <br>
<br>
-- Deploying files into AppDir root directory -- <br>
Deploying files to AppDir root using desktop file:
AppDir/usr/share/applications/cin.desktop <br>
Deploying desktop file to AppDir root:
AppDir/usr/share/applications/cin.desktop <br>
Creating symlink for file
AppDir/usr/share/applications/cin.desktop in/as AppDir <br>
Deploying icon to AppDir root:
AppDir/usr/share/icons/hicolor/scalable/apps/cin.svg <br>
Creating symlink for file
AppDir/usr/share/icons/hicolor/scalable/apps/cin.svg in/as AppDir
<br>
Deploying AppRun symlink for executable in AppDir root:
AppDir/usr/bin/cin <br>
Creating symlink for file AppDir/usr/bin/cin in/as AppDir/AppRun <br>
Found appimagetool: /usr/local/bin/appimagetool-x86_64.AppImage<br>
Running command: /usr/local/bin/appimagetool-x86_64.AppImage
"appimagetool" "AppDir" "<br>
/usr/bin/AppImageLauncher: /lib64/libcurl.so.4: no version
information available (required by
/usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)<br>
<br>
<br>
====>>>> AppImageLauncher popup here and want to
integrate/run, and maybe break something (?)<br></font></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><a href="https://github.com/TheAssassin/AppImageLauncher/issues/602" target="_blank" rel="noreferrer">https://github.com/TheAssassin/AppImageLauncher/issues/602</a></div><div dir="auto"><br></div><div dir="auto">====</div><div dir="auto">AppImageLauncher would need to be updated to support Zstd, unsure why it
still doesn't support it yet (is AppImageLauncher still maintained?).
But for now AppImage authors need to use another compression format than
the default one by passing either <code>--comp xz</code> or <code>--comp gzip</code> to appimagetool to have it work with AppImageLauncher.</div><div dir="auto"><br></div><div dir="auto">=====</div><div dir="auto"><br></div><div dir="auto">workaround is to remove (temporarily?) AppImagelauncher until it fixed ... see end of issue, it was still not done as of 2 weeks ago.</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><font face="Courier New, Courier, monospace">
<br>
<br>
Squashfs image uses (null) compression, this version supports only
xz, zlib.<br>
ERROR: appimage_shall_not_be_integrated : sqfs_open_image error:
/usr/local/bin/appimagetool-x86_64.AppImage<br>
AppImageLauncher error: appimage_shall_not_be_integrated() failed
(returned -1)<br>
Squashfs image uses (null) compression, this version supports only
xz, zlib.<br>
ERROR: appimage_is_terminal_app : sqfs_open_image error:
/usr/local/bin/appimagetool-x86_64.AppImage<br>
AppImageLauncher error: appimage_is_terminal_app() failed
(returned -1)<br>
fusermount3 version: 3.16.2<br>
execv error: No such file or directory<br>
localhost:/Cin # <br>
localhost:/Cin # du -sh AppDir<br>
216M AppDir<br>
localhost:/Cin # ls -la AppDir<br>
total 12<br>
drwxr-xr-x 3 root root 4096 Dec 6 02:50 .<br>
drwxr-xr-x 31 root root 4096 Dec 6 02:50 ..<br>
lrwxrwxrwx 1 root root 11 Dec 6 02:50 AppRun -> usr/bin/cin<br>
lrwxrwxrwx 1 root root 34 Dec 6 02:50 cin.desktop ->
usr/share/applications/cin.desktop<br>
lrwxrwxrwx 1 root root 45 Dec 6 02:50 cin.svg ->
usr/share/icons/hicolor/scalable/apps/cin.svg<br>
drwxr-xr-x 5 root root 4096 Dec 6 02:50 usr<br>
localhost:/Cin # <br>
localhost:/Cin # ls /usr/local/bin/appimagetool-x86_64.AppImage<br>
/usr/local/bin/appimagetool-x86_64.AppImage<br>
localhost:/Cin # <br>
localhost:/Cin # ls -la
/usr/local/bin/appimagetool-x86_64.AppImage<br>
-rwxr-xr-x 1 root root 12718856 Dec 6 </font><br>
</div>
</blockquote></div></div></div>