QSV profile debuggin thread
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added -loglevel debug ? and post full output here. Then we can set same loglevel in bin/ffmpeg/encode.opts so we hopefully will spot difference in parameters send down to line ... then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error then hopefully we can tweak qsv_av1 profile back into usability. Repeat for vp9/h264.
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy. 1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1 cat dv01_07_av1_qsv.log ffmpeg version 7.0.2 Copyright (c) 2000-2024 the FFmpeg developers built with gcc 14 (SUSE Linux) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --incdir=/usr/include/ffmpeg --extra-cflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --optflags='-O2 -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -ffat-lto-objects -g' --disable-htmlpages --enable-pic --disable-stripping --enable-shared --disable-static --enable-gpl --enable-version3 --enable-libsmbclient --disable-openssl --enable-gnutls --enable-ladspa --enable-libshaderc --enable-vulkan --enable-libplacebo --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libdc1394 --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgsm --enable-libjack --enable-libjxl --enable-librist --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopenh264-dlopen --enable-libopus --enable-libpulse --enable-librav1e --enable-librubberband --enable-libsvtav1 --enable-libsoxr --enable-libspeex --enable-libssh --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lto --enable-lv2 --enable-libvpl --enable-vaapi --enable-vdpau --enable-version3 --enable-libfdk-aac-dlopen --enable-nonfree --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libx264 --enable-libx265 --enable-libxvid libavutil 59. 8.100 / 59. 8.100 libavcodec 61. 3.100 / 61. 3.100 libavformat 61. 1.100 / 61. 1.100 libavdevice 61. 1.100 / 61. 1.100 libavfilter 10. 1.100 / 10. 1.100 libswscale 8. 1.100 / 8. 1.100 libswresample 5. 1.100 / 5. 1.100 libpostproc 58. 1.100 / 58. 1.100 Splitting the commandline. Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'. Reading option '-hwaccel_output_format' ... matched as option 'hwaccel_output_format' (select output format used with HW accelerated decoding) with argument 'qsv'. Reading option '-qsv_device' ... matched as option 'qsv_device' (set QSV hardware device (DirectX adapter index, DRM path or X11 display name)) with argument '/dev/dri/renderD128'. Reading option '-i' ... matched as input url with argument 'dv01_07.dv'. Reading option '-c:v' ... matched as option 'c' (select encoder/decoder ('copy' to copy stream without reencoding)) with argument 'av1_qsv'. Reading option '-preset' ... matched as AVOption 'preset' with argument '4'. Reading option '-b:v' ... matched as option 'b' (video bitrate (please use -b:v)) with argument '1570k'. Reading option 'dv01_07_av1_qsv_pr4_bv1570k.webm' ... matched as output url. Finished splitting the commandline. Parsing a group of options: global . Applying option loglevel (set logging level) with argument debug. Applying option qsv_device (set QSV hardware device (DirectX adapter index, DRM path or X11 display name)) with argument /dev/dri/renderD128. [AVHWDeviceContext @ 0x5570f626b440] libva: VA-API version 1.22.0 [AVHWDeviceContext @ 0x5570f626b440] libva: User requested driver 'iHD' [AVHWDeviceContext @ 0x5570f626b440] libva: Trying to open /usr/lib64/dri/iHD_drv_video.so [AVHWDeviceContext @ 0x5570f626b440] libva: Found init function __vaDriverInit_1_22 [AVHWDeviceContext @ 0x5570f626b440] libva: va_openDriver() returns 0 [AVHWDeviceContext @ 0x5570f626b440] Initialised VAAPI connection: version 1.22 [AVHWDeviceContext @ 0x5570f626b440] Format 0x41524742 -> bgra. [AVHWDeviceContext @ 0x5570f626b440] Format 0x41424752 -> rgba. [AVHWDeviceContext @ 0x5570f626b440] Format 0x58524742 -> bgr0. [AVHWDeviceContext @ 0x5570f626b440] Format 0x58424752 -> rgb0. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30335241 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30334241 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30335258 -> x2rgb10le. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30334258 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x36314752 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x56555941 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x56555958 -> vuyx. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30303859 -> gray. [AVHWDeviceContext @ 0x5570f626b440] Format 0x3231564e -> nv12. [AVHWDeviceContext @ 0x5570f626b440] Format 0x3132564e -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x32595559 -> yuyv422. [AVHWDeviceContext @ 0x5570f626b440] Format 0x59565955 -> uyvy422. [AVHWDeviceContext @ 0x5570f626b440] Format 0x32315659 -> yuv420p. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30323449 -> yuv420p. [AVHWDeviceContext @ 0x5570f626b440] Format 0x50313134 -> yuv411p. [AVHWDeviceContext @ 0x5570f626b440] Format 0x48323234 -> yuv422p. [AVHWDeviceContext @ 0x5570f626b440] Format 0x56323234 -> yuv440p. [AVHWDeviceContext @ 0x5570f626b440] Format 0x50343434 -> yuv444p. [AVHWDeviceContext @ 0x5570f626b440] Format 0x33434d49 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30313050 -> p010le. [AVHWDeviceContext @ 0x5570f626b440] Format 0x32313050 -> p012le. [AVHWDeviceContext @ 0x5570f626b440] Format 0x36313050 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30313259 -> y210le. [AVHWDeviceContext @ 0x5570f626b440] Format 0x32313259 -> y212le. [AVHWDeviceContext @ 0x5570f626b440] Format 0x36313259 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x30313459 -> xv30le. [AVHWDeviceContext @ 0x5570f626b440] Format 0x32313459 -> xv36le. [AVHWDeviceContext @ 0x5570f626b440] Format 0x36313459 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x50424752 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] Format 0x50524742 -> unknown. [AVHWDeviceContext @ 0x5570f626b440] VAAPI driver: Intel iHD driver for Intel(R) Gen Graphics - 24.3.4 (). [AVHWDeviceContext @ 0x5570f626b440] Driver not found in known nonstandard list, using standard behaviour. [AVHWDeviceContext @ 0x5570f626b380] Use Intel(R) oneVPL to create MFX session, API version is 2.13, the required implementation version is 1.3 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 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 [AVHWDeviceContext @ 0x5570f626b380] Initialize MFX session: implementation version is 2.12 Successfully parsed a group of options. Parsing a group of options: input url dv01_07.dv. Applying option hwaccel_output_format (select output format used with HW accelerated decoding) with argument qsv. Successfully parsed a group of options. Opening an input file: dv01_07.dv. [AVFormatContext @ 0x5570f636eb00] Opening 'dv01_07.dv' for reading [file @ 0x5570f64bf000] Setting default whitelist 'file,crypto,data' [dv @ 0x5570f636eb00] Format dv probed with size=2048 and score=75 [dv @ 0x5570f636eb00] Before avformat_find_stream_info() pos: 0 bytes read:32768 seeks:0 nb_streams:1 [dv @ 0x5570f636eb00] Probe buffer size limit of 5000000 bytes reached [dv @ 0x5570f636eb00] Estimating duration from bitrate, this may be inaccurate [dv @ 0x5570f636eb00] After avformat_find_stream_info() pos: 4752000 bytes read:4752000 seeks:0 frames:66 Input #0, dv, from 'dv01_07.dv': Metadata: timecode : 01:09:35:09 Duration: 00:01:53.28, start: 0.000000, bitrate: 28800 kb/s Stream #0:0, 33, 1/60000: Video: dvvideo, 1 reference frame, yuv420p(topleft), 720x576 [SAR 16:15 DAR 4:3], 0/1, 28800 kb/s, 60k fps, 25 tbr, 60k tbn Stream #0:1, 33, 1/14112000: Audio: pcm_s16le, 48000 Hz, stereo, s16, 1536 kb/s Successfully opened the file. Parsing a group of options: output url dv01_07_av1_qsv_pr4_bv1570k.webm. Applying option c:v (select encoder/decoder ('copy' to copy stream without reencoding)) with argument av1_qsv. Applying option b:v (video bitrate (please use -b:v)) with argument 1570k. Successfully parsed a group of options. Opening an output file: dv01_07_av1_qsv_pr4_bv1570k.webm. [out#0/webm @ 0x5570f6367f40] No explicit maps, mapping streams automatically... [vost#0:0/av1_qsv @ 0x5570f648d940] Created video stream from input stream 0:0 detected 20 logical cores [aost#0:1/libopus @ 0x5570f64d5b40] Created audio stream from input stream 0:1 File 'dv01_07_av1_qsv_pr4_bv1570k.webm' already exists. Overwrite? [y/N] Not overwriting - exiting Error opening output file dv01_07_av1_qsv_pr4_bv1570k.webm. [AVIOContext @ 0x5570f64d2080] Statistics: 4752000 bytes read, 0 seeks
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?) 1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1 2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
пт, 11 окт. 2024 г., 23:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?)
I think only parts where we see setup.of MXF session are important, but I hope log files compress well. If they still too big post them to me directly.
1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1
2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
Den 11.10.2024 22:39, skrev Andrew Randrianasulu:
пт, 11 окт. 2024 г., 23:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?)
I think only parts where we see setup.of MXF session are important, but I hope log files compress well. If they still too big post them to me directly.
I posted them directly this time as .gz If you tell me what to 'grep' or search for I can extract it and post it here next (searched 'mxf without finding something) .
1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1
2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
сб, 12 окт. 2024 г., 00:04 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:39, skrev Andrew Randrianasulu:
пт, 11 окт. 2024 г., 23:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?)
I think only parts where we see setup.of MXF session are important, but I hope log files compress well. If they still too big post them to me directly.
I posted them directly this time as .gz If you tell me what to 'grep' or search for I can extract it and post it here next (searched 'mxf without finding something) .
true, it was prefixed by [av1_qsv @ try to search for av1_qsv lines ? Anyway, I think we get our working baseline, now (or may be tomorrow? depend on localtime) it will be time to get creative with ffmpeg switches. You probably can save lig files in folders named working param1_level10_profile_main param2_level30_profile_main10 param3_level0_profile_high_notworking so it will be easer to see where working vs non-working logs are. Quote a chore. I suggest to create just few working and few non-working cases. May be for tommorow?
1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1
2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
Den 11.10.2024 23:13, skrev Andrew Randrianasulu:
сб, 12 окт. 2024 г., 00:04 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:39, skrev Andrew Randrianasulu:
пт, 11 окт. 2024 г., 23:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?)
I think only parts where we see setup.of MXF session are important, but I hope log files compress well. If they still too big post them to me directly.
I posted them directly this time as .gz If you tell me what to 'grep' or search for I can extract it and post it here next (searched 'mxf without finding something) .
true, it was prefixed by
[av1_qsv @
try to search for av1_qsv lines ?
Anyway, I think we get our working baseline, now (or may be tomorrow? depend on localtime) it will be time to get creative with ffmpeg switches.
You probably can save lig files in folders named
"lig files" (similar for h264/hevc/vp9 ?)
working param1_level10_profile_main param2_level30_profile_main10 param3_level0_profile_high_notworking
so it will be easer to see where working vs non-working logs are.
Quote a chore. I suggest to create just few working and few non-working cases.
May be for tommorow?
Late now, so good suggestion. Tomorrow I will be some on and off.
1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1
2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
сб, 12 окт. 2024 г., 00:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 23:13, skrev Andrew Randrianasulu:
сб, 12 окт. 2024 г., 00:04 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:39, skrev Andrew Randrianasulu:
пт, 11 окт. 2024 г., 23:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?)
I think only parts where we see setup.of MXF session are important, but I hope log files compress well. If they still too big post them to me directly.
I posted them directly this time as .gz If you tell me what to 'grep' or search for I can extract it and post it here next (searched 'mxf without finding something) .
true, it was prefixed by
[av1_qsv @
try to search for av1_qsv lines ?
Anyway, I think we get our working baseline, now (or may be tomorrow? depend on localtime) it will be time to get creative with ffmpeg switches.
You probably can save lig files in folders named
"lig files" (similar for h264/hevc/vp9 ?)
log files - typo!
working param1_level10_profile_main param2_level30_profile_main10 param3_level0_profile_high_notworking
so it will be easer to see where working vs non-working logs are.
Quote a chore. I suggest to create just few working and few non-working cases.
May be for tommorow?
Late now, so good suggestion. Tomorrow I will be some on and off.
I tend to stay up at night, but then I'll sleep most of light day! (depending on my dog of course). so .. see you!
1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1
2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
Den 12.10.2024 00:04, skrev Andrew Randrianasulu:
сб, 12 окт. 2024 г., 00:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 23:13, skrev Andrew Randrianasulu:
сб, 12 окт. 2024 г., 00:04 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:39, skrev Andrew Randrianasulu:
пт, 11 окт. 2024 г., 23:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?)
I think only parts where we see setup.of MXF session are important, but I hope log files compress well. If they still too big post them to me directly.
I posted them directly this time as .gz If you tell me what to 'grep' or search for I can extract it and post it here next (searched 'mxf without finding something) .
true, it was prefixed by
[av1_qsv @
try to search for av1_qsv lines ?
Anyway, I think we get our working baseline, now (or may be tomorrow? depend on localtime) it will be time to get creative with ffmpeg switches.
You probably can save lig files in folders named
"lig files" (similar for h264/hevc/vp9 ?)
log files - typo!
working param1_level10_profile_main param2_level30_profile_main10 param3_level0_profile_high_notworking
so it will be easer to see where working vs non-working logs are.
Quote a chore. I suggest to create just few working and few non-working cases.
May be for tommorow?
Late now, so good suggestion. Tomorrow I will be some on and off.
I tend to stay up at night, but then I'll sleep most of light day! (depending on my dog of course).
so .. see you!
Two additional ffmpeg code lines 3) and 4 for HEVC QSV follow. These are not correspondingly to 1) and 2), but working codes I have tested before. Log files via email. 3) 1080i HDV-> HEVC_QSV -------------------- ffmpeg -hide_banner -loglevel debug -hwaccel_output_format qsv -i hdv09_04.m2t -pix_fmt p010le -c:v hevc_qsv -profile:v main10 hdv09_04_hevc_qsv.mp4 > hdv09_04_hevc_qsv.log 2>&1 4) HEVC qsv decode + HEVC qsv encode --------------------------------- ffmpeg -hide_banner -loglevel debug -hwaccel_output_format qsv -c:v hevc_qsv -i h265_yuv420p+opus.mp4 -c:v hevc_qsv hevc_yuv420p+opus_qsv.mp4 > hevc_yuv420p+opus_qsv.log 2>&1
1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1
2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
Den 12.10.2024 11:11, skrev Terje J. Hanssen:
Den 12.10.2024 00:04, skrev Andrew Randrianasulu:
сб, 12 окт. 2024 г., 00:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 23:13, skrev Andrew Randrianasulu:
сб, 12 окт. 2024 г., 00:04 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:39, skrev Andrew Randrianasulu:
пт, 11 окт. 2024 г., 23:36 Terje J. Hanssen <[email protected]>:
Den 11.10.2024 22:13, skrev Terje J. Hanssen:
Den 11.10.2024 21:04, skrev Andrew Randrianasulu:
So, Terje, can you run your usual working ffmpeg command encoding av1 via system fmmpeg/qsv but with added
-loglevel debug
?
and post full output here.
Then we can set same loglevel in bin/ffmpeg/encode.opts
so we hopefully will spot difference in parameters send down to line ...
then we can try to make ffmpeg fail by adding say -profile=main to ffmpeg's command line and see more detailed error
then hopefully we can tweak qsv_av1 profile back into usability.
Repeat for vp9/h264.
Andrew, I think use two input video examples 1) SD-DV 2) HDV
Currently ffmpeg-7-7.0.2 on Tumbleweed-Slowroll (but have also ffmpeg-7-7.1 on Leap if wanted) I use output.log file. For some reason the terminal output alone is seemingly more verbose, and longer than I can scroll back to copy.
Oh, the reason was the ffmpeg output file existed and it wasn't overwritten. I also shows that the output is too long for Cingg messages, and I try to post the two log files compressed by email if acceptable(?)
I think only parts where we see setup.of MXF session are important, but I hope log files compress well. If they still too big post them to me directly.
I posted them directly this time as .gz If you tell me what to 'grep' or search for I can extract it and post it here next (searched 'mxf without finding something) .
true, it was prefixed by
[av1_qsv @
try to search for av1_qsv lines ?
Anyway, I think we get our working baseline, now (or may be tomorrow? depend on localtime) it will be time to get creative with ffmpeg switches.
You probably can save lig files in folders named
"lig files" (similar for h264/hevc/vp9 ?)
log files - typo!
working param1_level10_profile_main param2_level30_profile_main10 param3_level0_profile_high_notworking
so it will be easer to see where working vs non-working logs are.
Quote a chore. I suggest to create just few working and few non-working cases.
May be for tommorow?
Late now, so good suggestion. Tomorrow I will be some on and off.
I tend to stay up at night, but then I'll sleep most of light day! (depending on my dog of course).
so .. see you!
Two additional ffmpeg code lines 3) and 4 for HEVC QSV follow. These are not correspondingly to 1) and 2), but working codes I have tested before. Log files via email.
3) 1080i HDV-> HEVC_QSV -------------------- ffmpeg -hide_banner -loglevel debug -hwaccel_output_format qsv -i hdv09_04.m2t -pix_fmt p010le -c:v hevc_qsv -profile:v main10 hdv09_04_hevc_qsv.mp4 > hdv09_04_hevc_qsv.log 2>&1
4) HEVC qsv decode + HEVC qsv encode --------------------------------- ffmpeg -hide_banner -loglevel debug -hwaccel_output_format qsv -c:v hevc_qsv -i h265_yuv420p+opus.mp4 -c:v hevc_qsv hevc_yuv420p+opus_qsv.mp4 > hevc_yuv420p+opus_qsv.log 2>&1
I add one run with h264_qsv as well, log file by email 5) Software decode + h264 qsv encode with 5Mbps using CBR mode ffmpeg -loglevel debug -init_hw_device qsv=hw -filter_hw_device hw -i hdv09_04.m2t -vf hwupload=extra_hw_frames=64,format=qsv -c:v h264_qsv -b:v 5M -maxrate 5M hdv09_04_h264_qsv.mp4 > hdv09_04_h264_qsv.log 2>&1
1) 576i SD-DV -> AV1_QSV at bv1570k -------------------------------- ffmpeg -loglevel debug -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -i dv01_07.dv -c:v av1_qsv -preset 4 -b:v 1570k dv01_07_av1_qsv_pr4_bv1570k.webm > dv01_07_av1_qsv.log 2>&1
2) 1080i HDV->AV1_QSV at bv3700k ----------------------------- fmpeg -hide_banner -hwaccel_output_format qsv -qsv_device /dev/dri/renderD128 -extra_hw_frames 16 -i hdv09_04.m2t -c:v av1_qsv -preset 4 -b:v 3700k hdv09_04_av1_qsv_pr4_bv3700k.webm > hdv09_04_av1_qsv.log 2>&1
participants (2)
-
Andrew Randrianasulu -
Terje J. Hanssen