Testing Appimage with OneVPL and QSV presets on legacy Intel hardware
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware. Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e... * The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration, * The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration, 1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A) ~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0 Loaded hdv09_04.m2t (tff interlaced) Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished. 2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel ~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0 Loaded hdv09_04.m2t (tff interlaced) Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default) Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished. Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
Great! somehow we need to get all of this documented as far as the build procedure and usage goes to include in the Manual. It would be difficult for anyone who does not have this "gourmet" hardware to do that. In addition, I can put Terje's AppImage on the website for other users to download for testing and usage -- that would be appreciated. Since the AppImage is large, it would have to be first uploaded to a "drop site" for me to download. But that is up to Terje. Thanks for this great effort and info. On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
- The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
- The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 07.12.2024 19:25, skrev Phyllis Smith:
Great! somehow we need to get all of this documented as far as the build procedure and usage goes to include in the Manual. It would be difficult for anyone who does not have this "gourmet" hardware to do that. In addition, I can put Terje's AppImage on the website for other users to download for testing and usage -- that would be appreciated. Since the AppImage is large, it would have to be first uploaded to a "drop site" for me to download. But that is up to Terje. Thanks for this great effort and info.
Phyllis, of course I can upload the Appimage for what it is worth. If you have a url to a drop site, you can possibly mail it to me. Currently I have none in use myself. I was wondering a bit why this AppImage size is "just" 94.8 MB compared with 178.8 MB for the usual CinGG-20241031-x86_64.AppImage (?) And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
* The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
* The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
I will find a drop site and email it, but it may not be until tomorrow. The difference in size of the AppImage is due to the addition of the Online Manual that Georgy incorporated 4 years ago. It is definitely advantageous to have and easy to do but looks like I did not put this in the Manual so I will write that up. Basically before you produce your AppImage (after the build is finished), you just copy all of the HTML files to bin/doc so that there are there when you create the AppImage. More later.. On Sat, Dec 7, 2024 at 12:17 PM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:
Den 07.12.2024 19:25, skrev Phyllis Smith:
Great! somehow we need to get all of this documented as far as the build procedure and usage goes to include in the Manual. It would be difficult for anyone who does not have this "gourmet" hardware to do that. In addition, I can put Terje's AppImage on the website for other users to download for testing and usage -- that would be appreciated. Since the AppImage is large, it would have to be first uploaded to a "drop site" for me to download. But that is up to Terje. Thanks for this great effort and info.
Phyllis, of course I can upload the Appimage for what it is worth. If you have a url to a drop site, you can possibly mail it to me. Currently I have none in use myself. I was wondering a bit why this AppImage size is "just" 94.8 MB compared with 178.8 MB for the usual CinGG-20241031-x86_64.AppImage (?)
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
- The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
- The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 07.12.2024 22:10, skrev Phyllis Smith:
I will find a drop site and email it, but it may not be until tomorrow. The difference in size of the AppImage is due to the addition of the Online Manual that Georgy incorporated 4 years ago. It is definitely advantageous to have and easy to do but looks like I did not put this in the Manual so I will write that up. Basically before you produce your AppImage (after the build is finished), you just copy all of the HTML files to bin/doc so that there are there when you create the AppImage. More later..
Yes, I see from the "bld_appimage.sh" output that there were executed two cp commands for html cp -a cinelerra.html /home/cinelerra/cinelerra-5.1/doc/../bin/doc/. cp -a shortcuts.html /home/cinelerra/cinelerra-5.1/doc/../bin/doc/. The problem is there were just a few basic html files in /home/cinelerra/cinelerra-5.1/doc/ and no real online manual? cinelerra.html doc_2002.html installation.html ShellCmds_ru.html configuration.html help_br_index.html ShellCmds_en.html shortcuts.html current.html history.html ShellCmds_es.html doc_2000.html index.html ShellCmds.html So I need to know from where and how to copy these html files? A minor question is that the default file name from the bld script is "cin-x86_64.AppImage" Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
On Sat, Dec 7, 2024 at 12:17 PM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:
Den 07.12.2024 19:25, skrev Phyllis Smith:
Great! somehow we need to get all of this documented as far as the build procedure and usage goes to include in the Manual. It would be difficult for anyone who does not have this "gourmet" hardware to do that. In addition, I can put Terje's AppImage on the website for other users to download for testing and usage -- that would be appreciated. Since the AppImage is large, it would have to be first uploaded to a "drop site" for me to download. But that is up to Terje. Thanks for this great effort and info.
Phyllis, of course I can upload the Appimage for what it is worth. If you have a url to a drop site, you can possibly mail it to me. Currently I have none in use myself. I was wondering a bit why this AppImage size is "just" 94.8 MB compared with 178.8 MB for the usual CinGG-20241031-x86_64.AppImage (?)
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
* The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
* The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 08.12.2024 15:44, skrev Terje J. Hanssen:
Den 07.12.2024 22:10, skrev Phyllis Smith:
I will find a drop site and email it, but it may not be until tomorrow. The difference in size of the AppImage is due to the addition of the Online Manual that Georgy incorporated 4 years ago. It is definitely advantageous to have and easy to do but looks like I did not put this in the Manual so I will write that up. Basically before you produce your AppImage (after the build is finished), you just copy all of the HTML files to bin/doc so that there are there when you create the AppImage. More later..
Yes, I see from the "bld_appimage.sh" output that there were executed two cp commands for html
cp -a cinelerra.html /home/cinelerra/cinelerra-5.1/doc/../bin/doc/. cp -a shortcuts.html /home/cinelerra/cinelerra-5.1/doc/../bin/doc/.
The problem is there were just a few basic html files in /home/cinelerra/cinelerra-5.1/doc/ and no real online manual?
cinelerra.html doc_2002.html installation.html ShellCmds_ru.html configuration.html help_br_index.html ShellCmds_en.html shortcuts.html current.html history.html ShellCmds_es.html doc_2000.html index.html ShellCmds.html
I'm confused here, because opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
So I need to know from where and how to copy these html files?
A minor question is that the default file name from the bld script is "cin-x86_64.AppImage" Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
On Sat, Dec 7, 2024 at 12:17 PM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:
Den 07.12.2024 19:25, skrev Phyllis Smith:
Great! somehow we need to get all of this documented as far as the build procedure and usage goes to include in the Manual. It would be difficult for anyone who does not have this "gourmet" hardware to do that. In addition, I can put Terje's AppImage on the website for other users to download for testing and usage -- that would be appreciated. Since the AppImage is large, it would have to be first uploaded to a "drop site" for me to download. But that is up to Terje. Thanks for this great effort and info.
Phyllis, of course I can upload the Appimage for what it is worth. If you have a url to a drop site, you can possibly mail it to me. Currently I have none in use myself. I was wondering a bit why this AppImage size is "just" 94.8 MB compared with 178.8 MB for the usual CinGG-20241031-x86_64.AppImage (?)
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
* The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
* The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Sorry for the late reply. Since you have a gmail address as do I, the simplest way is just to email the AppImage file directly to only me: phylsmith2017@gmail.com --- what happens when there is a big file is that gmail will automatically upload the file to a specific spot and provide a link for me to download. Not sure if you want to add the Help Manual documentation first as explained below. So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date. opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version
4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance. And not to forget: it is thanks to Andrew's patchwork and time consuming
guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
Den 08.12.2024 21:15, skrev Phyllis Smith:
Sorry for the late reply. Since you have a gmail address as do I, the simplest way is just to email the AppImage file directly to only me: phylsmith2017@gmail.com --- what happens when there is a big file is that gmail will automatically upload the file to a specific spot and provide a link for me to download. Not sure if you want to add the Help Manual documentation first as explained below.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
Den 08.12.2024 21:44, skrev Terje J. Hanssen:
Den 08.12.2024 21:15, skrev Phyllis Smith:
Sorry for the late reply. Since you have a gmail address as do I, the simplest way is just to email the AppImage file directly to only me: phylsmith2017@gmail.com --- what happens when there is a big file is that gmail will automatically upload the file to a specific spot and provide a link for me to download. Not sure if you want to add the Help Manual documentation first as explained below.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
And yes, AppImage exceeded the google server's limit and could not send. My Thunderbird email client popup a notice that recommends a Filelink service for large attachments. I'll try to look at it https://support.mozilla.org/en-US/kb/filelink-large-attachments#w_thunderbir...
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it. I try first to send it without the manual, in case issues to get it
included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh. Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date. opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version
4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance. And not to forget: it is thanks to Andrew's patchwork and time consuming
guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway. It was merely intended for possibly others coming to and read this later :)
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong: cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB) While Manual Help works for the latter, it doesn't load for the new AppImage: ~/Applications> ./CinGG-20241120-x86_64.AppImage Alt+h Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205. Is this a known issue and possibly how to solve it? I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it
included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version
4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming
guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc Alt+h sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
пн, 9 дек. 2024 г., 17:09 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it
included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in
cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc
Alt+h
sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
so, it was more correct first time, just perl script was unable to find Contents.html may be it was named contents.html, from lowercase c ?
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra",
Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming
guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 09.12.2024 15:14, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:09 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in
cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc
Alt+h
sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
so, it was more correct first time, just perl script was unable to find Contents.html
may be it was named contents.html, from lowercase c ?
"Contents.html" looks to be the correct one as verified here from the latest Manual folder: cd /Cin/AppDir/usr/bin/doc/CinelerraGG_Manual ls Content* content* Contents.html contents.png There looks to be a doc build difference somewhere between my AppImage vs the the official AppImage?
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra", Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
пн, 9 дек. 2024 г., 17:36 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 15:14, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:09 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it
included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in
cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc
Alt+h
sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
so, it was more correct first time, just perl script was unable to find Contents.html
may be it was named contents.html, from lowercase c ?
"Contents.html" looks to be the correct one as verified here from the latest Manual folder:
cd /Cin/AppDir/usr/bin/doc/CinelerraGG_Manual
ls Content* content* Contents.html contents.png
There looks to be a doc build difference somewhere between my AppImage vs the the official AppImage?
well, for just bin folder I removed anything from bin/doc then re run 'make install' then copied html docu folder like this: cp -r CinelerraGG_Manual bin/doc/ firefox startup a bit slow but it worked .... in termux.
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra",
Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time consuming
guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 09.12.2024 15:42, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:36 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 15:14, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:09 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it included. I've experienced issues before with file attachments larger than ca. 30 MB, either it is due to the sender or receiver side, I don't know.
> > So I need to know from where and how to copy > these html files? > > https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz > Just download the tgz file and tar xvf to wherever > you have bin/doc so it can be copied to AppDir/usr > in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in
cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc
Alt+h
sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
so, it was more correct first time, just perl script was unable to find Contents.html
may be it was named contents.html, from lowercase c ?
"Contents.html" looks to be the correct one as verified here from the latest Manual folder:
cd /Cin/AppDir/usr/bin/doc/CinelerraGG_Manual
ls Content* content* Contents.html contents.png
There looks to be a doc build difference somewhere between my AppImage vs the the official AppImage?
well, for just bin folder
I removed anything from bin/doc
then re run 'make install'
then copied html docu folder like this:
cp -r CinelerraGG_Manual bin/doc/
firefox startup a bit slow but it worked .... in termux.
I tried to repeat your steps, but confusingly I still got the previous error: rm /Cin/bin/doc/** ls /Cin/bin/doc/ /Cin # make install cp -r CinelerraGG_Manual /Cin/bin/doc/ ls /Cin/bin/doc/ CinelerraGG_Manual du -sh /Cin/bin/doc/ 76M /Cin/bin/doc/ /Cin bin/cin Cinelerra Infinity - built: Nov 20 2024 22:06:05 BC_DisplayInfo::gl_fb_config failed Alt+h sh: line 1: /home/cinelerra/cinelerra-5.1/bin/doc/ContextManual.pl: No such file or directory
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
> > Can the bld_appimage.sh take the wanted file > name as argument, or is it just fine to rename > it afterwards? > > It is just fine to name it afterwards; that is what > I do when renaming for the website to include the date. > > opening index.html and "cinelerra.html" is > "Secrets of Cinelerra", Version 4.1 by Adam Williams > > We always want to have these files with the source > to recognize Cinelerra's origin and continuance. > > And not to forget: it is thanks to Andrew's > patchwork and time consuming guiding that has > made this possible ! > > Yes, that goes without saying, but I should have > said it anyway.
It was merely intended for possibly others coming to and read this later :)
> >
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
In trying to determine where the error is, I was not able to ascertain where things went wrong so I started from scratch to get the steps correct. Although I can say for sure that the last error of:
Alt+h sh: line 1: /home/cinelerra/cinelerra-5.1/bin/doc/ContextManual.pl: No such file or directory
is for sure telling me that the default file, which is part of the original source and you should still see in /home/cinelerra/cinelerra-5.1/doc, is missing in /home/cinelerra/cinelerra-5.1/bin/doc; that is ContextManual.pl. Something must have gotten deleted or not copied to AppDir/usr in its entirety. If it is not too much trouble, I would do a fresh build and only then execute directly "in the bin/doc directory": tar xvf HTML_Manual-20241031.tgz then before running your appimage build, check by executing "bin/cin" and doing Alt h. If that works then the copy via bld_appimage.sh should result in Help being automatically included. Standing by here for results. On Mon, Dec 9, 2024 at 8:36 AM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:
Den 09.12.2024 15:42, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:36 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 15:14, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:09 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it
> included. I've experienced issues before with file attachments larger than > ca. 30 MB, either it is due to the sender or receiver side, I don't know. > > So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in
cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc
Alt+h
sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
so, it was more correct first time, just perl script was unable to find Contents.html
may be it was named contents.html, from lowercase c ?
"Contents.html" looks to be the correct one as verified here from the latest Manual folder:
cd /Cin/AppDir/usr/bin/doc/CinelerraGG_Manual
ls Content* content* Contents.html contents.png
There looks to be a doc build difference somewhere between my AppImage vs the the official AppImage?
well, for just bin folder
I removed anything from bin/doc
then re run 'make install'
then copied html docu folder like this:
cp -r CinelerraGG_Manual bin/doc/
firefox startup a bit slow but it worked .... in termux.
I tried to repeat your steps, but confusingly I still got the previous error:
rm /Cin/bin/doc/** ls /Cin/bin/doc/
/Cin # make install
cp -r CinelerraGG_Manual /Cin/bin/doc/ ls /Cin/bin/doc/ CinelerraGG_Manual
du -sh /Cin/bin/doc/ 76M /Cin/bin/doc/
/Cin bin/cin Cinelerra Infinity - built: Nov 20 2024 22:06:05
BC_DisplayInfo::gl_fb_config failed
Alt+h sh: line 1: /home/cinelerra/cinelerra-5.1/bin/doc/ContextManual.pl: No such file or directory
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra",
Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time
consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Den 09.12.2024 20:31, skrev Phyllis Smith:
In trying to determine where the error is, I was not able to ascertain where things went wrong so I started from scratch to get the steps correct. Although I can say for sure that the last error of:
Alt+h sh: line 1: /home/cinelerra/cinelerra-5.1/bin/doc/ContextManual.pl: No such file or directory
is for sure telling me that the default file, which is part of the original source and you should still see in /home/cinelerra/cinelerra-5.1/doc, is missing in /home/cinelerra/cinelerra-5.1/bin/doc; that is ContextManual.pl. Something must have gotten deleted or not copied to AppDir/usr in its entirety.
If it is not too much trouble, I would do a fresh build and only then execute directly "in the bin/doc directory": tar xvf HTML_Manual-20241031.tgz then before running your appimage build, check by executing "bin/cin" and doing Alt h. If that works then the copy via bld_appimage.sh should result in Help being automatically included.
Standing by here for results.
Actually there are three doc locations in my /Cin: ./doc ./bin/doc ./AppDir/usr/bin/doc and as the first doc folder is empty, I have a feeling I myself by accident cleaned up wrong doc folder. But what do we preserve backup for 😉 Actually I found the missing file in my backup /Cin # ls /Cin/bin_use_system_ffmpeg-702/doc/ContextManual.pl /Cin/bin_use_system_ffmpeg-702/doc/ContextManual.pl Then I cleaned up the first two doc folders above and copied all doc files from the backup and added the Cinelerra-GG_Manual. So in worst case there might be some extra doc files now :) Tested that Help files worked in CinGG, re-built the AppImage and tested successful. ~/Applications> du -sh Cin* 171M CinGG-20241031-x86_64.AppImage 181M CinGG-20241120-x86_64.AppImage Phyllis, look up for a new file-link for the complete AppImage in a few minutes 😉
On Mon, Dec 9, 2024 at 8:36 AM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:
Den 09.12.2024 15:42, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:36 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 15:14, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:09 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin <cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith: > > There must be some kind of interference when you > try to email the large file. Did you actually > send from your Gmail account or your teknikk > account.? When I try to send a large file from > my gmail account, it says it is too big and > automatically uploads it to the google drive and > gives me a link. I just sent you one now so you > can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
> > I try first to send it without the > manual, in case issues to get it > included. I've experienced issues > before with file attachments larger > than ca. 30 MB, either it is due to > the sender or receiver side, I don't > know. > >> >> So I need to know from where and how to >> copy these html files? >> >> https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz >> Just download the tgz file and tar xvf to >> wherever you have bin/doc so it can be copied >> to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in
cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc
Alt+h
sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
so, it was more correct first time, just perl script was unable to find Contents.html
may be it was named contents.html, from lowercase c ?
"Contents.html" looks to be the correct one as verified here from the latest Manual folder:
cd /Cin/AppDir/usr/bin/doc/CinelerraGG_Manual
ls Content* content* Contents.html contents.png
There looks to be a doc build difference somewhere between my AppImage vs the the official AppImage?
well, for just bin folder
I removed anything from bin/doc
then re run 'make install'
then copied html docu folder like this:
cp -r CinelerraGG_Manual bin/doc/
firefox startup a bit slow but it worked .... in termux.
I tried to repeat your steps, but confusingly I still got the previous error:
rm /Cin/bin/doc/** ls /Cin/bin/doc/
/Cin # make install
cp -r CinelerraGG_Manual /Cin/bin/doc/ ls /Cin/bin/doc/ CinelerraGG_Manual
du -sh /Cin/bin/doc/ 76M /Cin/bin/doc/
/Cin bin/cin Cinelerra Infinity - built: Nov 20 2024 22:06:05
BC_DisplayInfo::gl_fb_config failed
Alt+h sh: line 1: /home/cinelerra/cinelerra-5.1/bin/doc/ContextManual.pl: No such file or directory
I thought Manual Help should work before I send the complete AppImage.
> > Oh, there it is. Actually I had stored a 2023 > version on my system, but now tried to > "download" the HTML manual from here, and it > only displayed in Firefox :) > https://cinelerra-gg.org/download/CinelerraGG_Manual/ > >> >> Can the bld_appimage.sh take the wanted >> file name as argument, or is it just fine >> to rename it afterwards? >> >> It is just fine to name it afterwards; that is >> what I do when renaming for the website to >> include the date. >> >> opening index.html and "cinelerra.html" is >> "Secrets of Cinelerra", Version 4.1 by Adam >> Williams >> >> We always want to have these files with the >> source to recognize Cinelerra's origin and >> continuance. >> >> And not to forget: it is thanks to Andrew's >> patchwork and time consuming guiding that >> has made this possible ! >> >> Yes, that goes without saying, but I should >> have said it anyway. > > It was merely intended for possibly others > coming to and read this later :) > >> >> >
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Just an easy fix. I downloaded the latest appimage and will upload it to the website tomorrow and put a note in News. I will do this when I power up the desktop and check in Andrew's 5 patches. On Mon, Dec 9, 2024 at 4:05 PM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:
Den 09.12.2024 20:31, skrev Phyllis Smith:
In trying to determine where the error is, I was not able to ascertain where things went wrong so I started from scratch to get the steps correct. Although I can say for sure that the last error of:
Alt+h sh: line 1: /home/cinelerra/cinelerra-5.1/bin/doc/ContextManual.pl: No such file or directory
is for sure telling me that the default file, which is part of the original source and you should still see in /home/cinelerra/cinelerra-5.1/doc, is missing in /home/cinelerra/cinelerra-5.1/bin/doc; that is ContextManual.pl. Something must have gotten deleted or not copied to AppDir/usr in its entirety.
If it is not too much trouble, I would do a fresh build and only then execute directly "in the bin/doc directory": tar xvf HTML_Manual-20241031.tgz then before running your appimage build, check by executing "bin/cin" and doing Alt h. If that works then the copy via bld_appimage.sh should result in Help being automatically included.
Standing by here for results.
Actually there are three doc locations in my /Cin:
./doc ./bin/doc ./AppDir/usr/bin/doc
and as the first doc folder is empty, I have a feeling I myself by accident cleaned up wrong doc folder. But what do we preserve backup for 😉
Actually I found the missing file in my backup
/Cin # ls /Cin/bin_use_system_ffmpeg-702/doc/ContextManual.pl /Cin/bin_use_system_ffmpeg-702/doc/ContextManual.pl
Then I cleaned up the first two doc folders above and copied all doc files from the backup and added the Cinelerra-GG_Manual. So in worst case there might be some extra doc files now :) Tested that Help files worked in CinGG, re-built the AppImage and tested successful.
~/Applications> du -sh Cin* 171M CinGG-20241031-x86_64.AppImage 181M CinGG-20241120-x86_64.AppImage
Phyllis, look up for a new file-link for the complete AppImage in a few minutes 😉
On Mon, Dec 9, 2024 at 8:36 AM Terje J. Hanssen <terjejhanssen@gmail.com> wrote:
Den 09.12.2024 15:42, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:36 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 15:14, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 17:09 Terje J. Hanssen <terjejhanssen@gmail.com>:
Den 09.12.2024 13:29, skrev Terje J. Hanssen:
Den 09.12.2024 13:25, skrev Andrew Randrianasulu:
пн, 9 дек. 2024 г., 15:22 Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org>:
Den 08.12.2024 23:06, skrev Terje J. Hanssen:
Den 08.12.2024 22:39, skrev Phyllis Smith:
There must be some kind of interference when you try to email the large file. Did you actually send from your Gmail account or your teknikk account.? When I try to send a large file from my gmail account, it says it is too big and automatically uploads it to the google drive and gives me a link. I just sent you one now so you can see and delete it.
My old teknikk account is expired. I use Thunderbird as email client IMAP connected to my gmail account. For one or another reason the connection has been horrible slow since yesterday. But now I have sent you a filelink I hope you receive.
I try first to send it without the manual, in case issues to get it
>> included. I've experienced issues before with file attachments larger than >> ca. 30 MB, either it is due to the sender or receiver side, I don't know. >> >> So I need to know from where and how to copy these html files?
https://cinelerra-gg.org/download/images/HTML_Manual-20241031.tgz Just download the tgz file and tar xvf to wherever you have bin/doc so it can be copied to AppDir/usr in bld_appimage.sh.
Yes, I copied all manual files to bin/doc, and repeat the steps as follows, to get verified if something is wrong:
cp HTML_Manual-20241031/CinelerraGG_Manual/** /home/cinelerra/cinelerra-5.1/bin/doc
so now the total in AppDir/usr/bin/doc is 1007 elements, 80.3 MB
Ran bld_appimage.sh again and now have CinGG-20241120-x86_64.AppImage 166.5 MB (which still is smaller than the previous CinGG-20241031-x86_64.AppImage 178.8 MB)
While Manual Help works for the latter, it doesn't load for the new AppImage:
~/Applications> ./CinGG-20241120-x86_64.AppImage
Alt+h
Cannot open /tmp/.mount_CinGG-24Mpo2/usr/bin/doc/CinelerraGG_Manual/Contents.html: No such file or directory at /home/terje/.bcast5/ContextManual.pl line 205.
Is this a known issue and possibly how to solve it?
may be you should move in folder named CinelerraGG_Manual and not its content?
Yeah, I thought of that, but forgot to ask that question. I was in doubt as I think "all html files" was mentioned Try to cleanup and make appimage again.
Still no success to put the whole Manual folder in
cp -r HTML_Manual-20241031/CinelerraGG_Manual /home/cinelerra/cinelerra-5.1/bin/doc
Alt+h
sh: line 1: /tmp/.mount_CinGG-iDrVm0/usr/bin/doc/ContextManual.pl: No such file or directory
so, it was more correct first time, just perl script was unable to find Contents.html
may be it was named contents.html, from lowercase c ?
"Contents.html" looks to be the correct one as verified here from the latest Manual folder:
cd /Cin/AppDir/usr/bin/doc/CinelerraGG_Manual
ls Content* content* Contents.html contents.png
There looks to be a doc build difference somewhere between my AppImage vs the the official AppImage?
well, for just bin folder
I removed anything from bin/doc
then re run 'make install'
then copied html docu folder like this:
cp -r CinelerraGG_Manual bin/doc/
firefox startup a bit slow but it worked .... in termux.
I tried to repeat your steps, but confusingly I still got the previous error:
rm /Cin/bin/doc/** ls /Cin/bin/doc/
/Cin # make install
cp -r CinelerraGG_Manual /Cin/bin/doc/ ls /Cin/bin/doc/ CinelerraGG_Manual
du -sh /Cin/bin/doc/ 76M /Cin/bin/doc/
/Cin bin/cin Cinelerra Infinity - built: Nov 20 2024 22:06:05
BC_DisplayInfo::gl_fb_config failed
Alt+h sh: line 1: /home/cinelerra/cinelerra-5.1/bin/doc/ContextManual.pl: No such file or directory
I thought Manual Help should work before I send the complete AppImage.
Oh, there it is. Actually I had stored a 2023 version on my system, but now tried to "download" the HTML manual from here, and it only displayed in Firefox :) https://cinelerra-gg.org/download/CinelerraGG_Manual/
Can the bld_appimage.sh take the wanted file name as argument, or is it just fine to rename it afterwards?
It is just fine to name it afterwards; that is what I do when renaming for the website to include the date.
opening index.html and "cinelerra.html" is "Secrets of Cinelerra",
Version 4.1 by Adam Williams
We always want to have these files with the source to recognize Cinelerra's origin and continuance.
And not to forget: it is thanks to Andrew's patchwork and time
consuming guiding that has made this possible !
Yes, that goes without saying, but I should have said it anyway.
It was merely intended for possibly others coming to and read this later :)
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Now you can try it and use it if you are lucky enough to have the supporting hardware on a newer Intel system. https://cinelerra-gg.org/download/images/CinGG-20241120-x86_64-IntelHW.AppIm... As far as I can tell, this appimage runs in the standard way on AMD / Fedora version 40 as expected. So probably it will run about anywhere - just without the hardware encoding/decoding enhanced features (QSV and oneVPL). And being an appimage, it will run for several years as is. Thanks again, Terje AND Andrew !!! AND thanks to MatN who made it possible to keep providing binaries for the users for the past 4 year via his scripts to create the appimages !!! On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
- The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
- The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
one small possible addition to our document at https://cinelerra-gg.org/download/CinelerraGG_Manual/Build_CinGG_AppImage_fr... may be note that older appimagetool (from 2020) might work better on some systems compared to latest release there ? And also note that you can download manual separately (not via git)? ср, 11 дек. 2024 г., 02:47 Phyllis Smith via Cin <cin@lists.cinelerra-gg.org
:
Now you can try it and use it if you are lucky enough to have the supporting hardware on a newer Intel system.
https://cinelerra-gg.org/download/images/CinGG-20241120-x86_64-IntelHW.AppIm... As far as I can tell, this appimage runs in the standard way on AMD / Fedora version 40 as expected. So probably it will run about anywhere - just without the hardware encoding/decoding enhanced features (QSV and oneVPL). And being an appimage, it will run for several years as is.
Thanks again, Terje AND Andrew !!!
AND thanks to MatN who made it possible to keep providing binaries for the users for the past 4 year via his scripts to create the appimages !!!
On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
- The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
- The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
Thank you Andrew for the suggestion that I have finally clarified in the manual and checked into GIT. Also, a few days ago, I updated News on the website about Terje's appimage availability. I hope it is technically correct. https://www.cinelerra-gg.org/news-updates/november-2024-news-of-special-inte... I am slowly making a few other manual clarifications On Mon, Dec 16, 2024 at 2:27 AM Andrew Randrianasulu < randrianasulu@gmail.com> wrote:
one small possible addition to our document at
https://cinelerra-gg.org/download/CinelerraGG_Manual/Build_CinGG_AppImage_fr...
may be note that older appimagetool (from 2020) might work better on some systems compared to latest release there ?
And also note that you can download manual separately (not via git)?
ср, 11 дек. 2024 г., 02:47 Phyllis Smith via Cin < cin@lists.cinelerra-gg.org>:
Now you can try it and use it if you are lucky enough to have the supporting hardware on a newer Intel system.
https://cinelerra-gg.org/download/images/CinGG-20241120-x86_64-IntelHW.AppIm... As far as I can tell, this appimage runs in the standard way on AMD / Fedora version 40 as expected. So probably it will run about anywhere - just without the hardware encoding/decoding enhanced features (QSV and oneVPL). And being an appimage, it will run for several years as is.
Thanks again, Terje AND Andrew !!!
AND thanks to MatN who made it possible to keep providing binaries for the users for the past 4 year via his scripts to create the appimages !!!
On Sat, Dec 7, 2024 at 10:40 AM Terje J. Hanssen via Cin < cin@lists.cinelerra-gg.org> wrote:
After the successful Appimage build with OneVPL for QSV on Alder Lake (i7-12700/Arc A750), the time has come as proof of contest to test if it also works on legacy Intel iGPU hardware.
Extracted from the Fixed-function Quick Sync Video format support for HEVC one should expect
https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video#Hardware_decoding_and_e...
- The Skylake microarchitecture implementation adds a full fixed-function H.265/HEVC 8-bit 4:2:0 decoding and encoding acceleration, hybrid and partial HEVC 10-bit decoding acceleration,
- The Kaby Lake, Coffee Lake, Whiskey Lake and Comet Lake microarchitectures implementation adds full fixed-function H.265/HEVC 10-bit 4:2:0 decoding and encoding acceleration,
1) Sky Lake: ------------ CPU: Info: quad core model: Intel Core i7-6700K bits: 64 type: MT MCP cache: Graphics: Device-1: Intel HD Graphics 530 driver: i915 v: kernel (Device-2: NVIDIA GM206 [GeForce GTX 960] driver: N/A)
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 66.227 secs, 90.175 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4918 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b420 failed --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7fe508025980] Low power mode is unsupported [hevc_qsv @ 0x7fe508025980] Current pixel format is unsupported [hevc_qsv @ 0x7fe508025980] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/run/media/terje/video/hdv09_04_hevc_qsv_10b420.mp4 Render::render_single: Session finished.
2) Kaby Lake ----------- CPU: Info: quad core model: Intel Core i7-8550U bits: 64 type: MT MCP cache: Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel
~/Application> ./cin-x86_64.AppImage Cinelerra Infinity - built: Nov 20 2024 22:0
Loaded hdv09_04.m2t (tff interlaced)
Rendered to hevc_qsv_8b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 59.564 secs, 100.262 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_8b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main) (hev1 / 0x31766568), yuvj420p(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 4018 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Rendered to hevc_qsv_10b420 --------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 Render::render_single: Session finished. ** rendered 5972 frames in 79.061 secs, 75.537 fps
ffprobe -hide_banner hdv09_04_hevc_qsv_10b420.mp4 Stream #0:0[0x1](und): Video: hevc (Main 10) (hev1 / 0x31766568), yuv420p10le(pc, smpte170m/unknown/unknown, top coded first (swapped)), 1440x1080 [SAR 4:3 DAR 16:9], 25630 kb/s, 25 fps, 25 tbr, 12800 tbn (default)
Test hevc_qsv_10b422 failed: ---------------------------- libva info: VA-API version 1.22.0 libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_22 libva info: va_openDriver() returns 0 [hevc_qsv @ 0x7f8e74000bc0] Low power mode is unsupported [hevc_qsv @ 0x7f8e74000bc0] Current pixel format is unsupported [hevc_qsv @ 0x7f8e74000bc0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. FFMPEG::open_encoder err: Function not implemented int FFMPEG::open_encoder(const char*, const char*): open failed hevc_qsv:/home/terje/Videos/hdv09_04_hevc_qsv_10b422.mp4 Render::render_single: Session finished.
Conclusion: ------------------- The above simple tests show that the QSV enabled Appimage with OneVPL works also on legacy and other Intel hardware.
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
-- Cin mailing list Cin@lists.cinelerra-gg.org https://lists.cinelerra-gg.org/mailman/listinfo/cin
participants (3)
-
Andrew Randrianasulu -
Phyllis Smith -
Terje J. Hanssen