[Cin] ffmpeg 7.0 soon to be released

[Andrew Randrianasulu]

ср, 24 апр. 2024 г., 19:43 Andrea paz <gamberucci.andrea at gmail.com>:

> > I assume attached tar archive then only about TEST1 ?
>
> ?
>
> In test 1 I used a VP8/mov source without audio [4-3_3-2.mov] combined
> with an
> mp3/wav audio and in addition the render result [igor_test3.webm]:
> VP9/webm with audio
> Vorbis (webm.webm preset). [I didn't notice that the wav audio was
> mp3, maybe I need to
> use PCM audio?]
> In test 2 I used Big Buck Bunny_sunflower in h264/mp4 version with mp3
> audio.
>
> In both tests I simply loaded (in test 1, the project and in test
> 2, the file) with the “replace current project” option and then did a
> little
> playback/scrolling.
>
> The messages shown are everything that appeared between starting and
> closing CinGG
> (I just removed the normal start/end messages that CinGG has).
>
> The problems with vaapi are probably due to the combination of AMD,
> mesa, amdgpu and
> rocm, since every time they are updated the behavior always changes and
> new problems always arise...
> However in CinGG/ffmpeg7 it seems that vaapi is working (test 2
> [bbb_sunflower_1080p_30fps_normal.mp4]: no line “HW device init failed,
> using SW
> decode"). In test 1 you have errors with vaapi with VP8 [4-3_3-2.mov],
> which I believe is
> not supported. But there are no errors with VP9 [igor_test3.webm],
> which certainly
> supports vaapi.
>

Ah, sorry I was not sure if error messages show up serially right after
loading file or they can  show up asynchronous ...


Sorry for taking your time. I know vaapi is fragile, nice to see at least
sw fallback in our code still works as intended, even if it makes checking
vaapi runtime status harder ...



> > I wonder if plain system ffmpeg still  works for hw decoding?
>
> In Arch I still have ffmpeg 6.1.1. I have tried transcoding from mp4 to
> mp4, via
> decoding and encoding in vaapi, but I don't understand if decoding in
> vaapi works,
> while encoding works (https://trac.ffmpeg.org/wiki/Hardware/VAAPI):
>
> $ ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128
> -hwaccel_output_format vaapi
> -i mixkit-worried-and-sad-woman-outdoors-8739.mp4  -c:v h264_vaapi
> -b:v 2M -maxrate 2M
> output.mp4
>
> [...]
> Input #0, mov,mp4,m4a,3gp,3g2,mj2, from
> 'mixkit-worried-and-sad-woman-outdoors-8739.mp4':
>   Metadata:
>     major_brand     : M4V
>     minor_version   : 1
>     compatible_brands: isomavc1mp42
>     creation_time   : 2020-06-21T18:53:40.000000Z
>   Duration: 00:00:15.00, start: 0.000000, bitrate: 24801 kb/s
>   Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661),
> yuv420p(tv, bt709,
> progressive), 1920x1080 [SAR 1:1 DAR 16:9], 24798 kb/s, 24 fps, 24
> tbr, 24k tbn (default)
>     Metadata:
>       creation_time   : 2020-06-21T18:53:40.000000Z
>       handler_name    : ETI ISO Video Media Handler
>       vendor_id       : [0][0][0][0]
>       encoder         : Elemental H.264
> Stream mapping:
>   Stream #0:0 -> #0:0 (h264 (native) -> h264 (h264_vaapi))
> Press [q] to stop, [?] for help
> [h264_vaapi @ 0x571d363508c0] Driver does not support some wanted
> packed headers (wanted
> 0xd, found 0x1).
> Output #0, mp4, to 'output.mp4':
>   Metadata:
>     major_brand     : M4V
>     minor_version   : 1
>     compatible_brands: isomavc1mp42
>     encoder         : Lavf60.16.100
>   Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), vaapi(tv,
> bt709, progressive),
> 1920x1080 [SAR 1:1 DAR 16:9], q=2-31, 2000 kb/s, 24 fps, 12288 tbn
> (default)
>     Metadata:
>       creation_time   : 2020-06-21T18:53:40.000000Z
>       handler_name    : ETI ISO Video Media Handler
>       vendor_id       : [0][0][0][0]
>       encoder         : Lavc60.31.102 h264_vaapi
> [out#0/mp4 @ 0x571d3632dc80] video:3649kB audio:0kB subtitle:0kB other
> streams:0kB global
> headers:0kB muxing overhead: 0.064330%
> frame=  360 fps=196 q=-0.0 Lsize=    3652kB time=00:00:14.95
> bitrate=1999.9kbits/s
> speed=8.14x
>

may be mpv can be used to check decoding? It usually linked to system's
ffmpeg. Not sure if tools like radeontop still works with new amdgpu
supported  AMD hardware.

Anyway, thanks for testing, I hope it not ate too much time from your day.

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20240424/f96d1429/attachment.htm>