[Cin] You also can use fifo file and external encoder with cingg

[Andrew Randrianasulu]

On Tue, Jul 16, 2024 at 7:12 PM Terje J. Hanssen
<terjejhanssen at gmail.com> wrote:
>
>
>
> Den 16.07.2024 12:54, skrev Andrew Randrianasulu:
>
> Like this:
>
>  mkfifo /dev/shm/renderfarm.y4m <-- random name from previous test
>
> cin /home/admin/huawei_matepad_t/sdcard1/video/20200101_000443A.mp4
>
> ............
>
> encoded 397 frames in 400.09s (0.99 fps), 4154.67 kb/s, Avg QP:32.22
>
> =====
>
> Initially i set cingg cache to low value like 16 Mb and  render
> aborted at around 8 sec, then I set cache to 256 Mb and it finished
> for complete 13 seconds/ 397 frames....
>
> So, you can use external ffmpeg (and its array of encoders), or x265
> directly this way. (if you use normal file it will be 4.7 Gb per 13
> seconds of 4k30 video ...)
>
>
> The principle sounds interestingly. Although I'm used with simple pipes, I have never used fifo file (name pipes).
> But a real case ("workshop") example could make it clearer for me.
>
> 1. Will it be applicable for pre-built CinGG installed from appimages, or  from packages (einander) where "cin" can be started in a terminal ?
>
> 2. And let CinGG utilize my "system" ffmpeg (from Packman) for qsv gpu hwaccel encoding?
>
> ffmpeg -hide_banner -encoders | grep qsv
>  V..... av1_qsv              AV1 (Intel Quick Sync Video acceleration) (codec av1)
>  V..... h264_qsv             H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel Quick Sync Video acceleration) (codec h264)
>  V..... hevc_qsv             HEVC (Intel Quick Sync Video acceleration) (codec hevc)
>  V..... mjpeg_qsv            MJPEG (Intel Quick Sync Video acceleration) (codec mjpeg)
>  V..... mpeg2_qsv            MPEG-2 video (Intel Quick Sync Video acceleration) (codec mpeg2video)
>  V..... vp9_qsv              VP9 video (Intel Quick Sync Video acceleration) (codec vp9)
>
>
> 3. Suggestion to this pipe line setup and running av1_qsv encoding from CinGG Render .webm?
>
>


I tried to capture workflow (for some reason  this time it encoded 1
frame less ?)

https://youtu.be/Xr8_07CzyvQ

>
>
>
>
>
>
>
>