<HTML><BODY>Do you have any idea about it? I don't know how to fix it<br><br><br><blockquote style="border-left:1px solid #0857A6; margin:10px; padding:0 0 0 10px;">
Среда, 17 апреля 2019, 13:14 +03:00 от Ахмед Анам <ahmedanam@mail.ru>:<br>
<br>
<div id="">
<div class="js-helper js-readmsg-msg">
<style type="text/css"></style>
<div>
<div id="style_15554960830000001019_BODY"><div class="class_1555591453">
> <span data-mce-style="font-family: monospace, monospace;" style="font-family: monospace, monospace;">Are the video streams 4K? My guest is you are running out of memory on the GPU.</span><br><br>No, the streams have HD resolution. I run my programm with debug log level and here is output:<br><br><p><em>[h264 @ 0000013f85b22440] Failed setup for format cuda: hwaccel initialisation returned error</em><br><em>[h264 @ 0000013f85b22440] Format cuda not usable, retrying get_format() without it.</em><br><em>[h264 @ 0000013f85b22440] decode_slice_header error</em><br><em>[h264 @ 0000013f85b22440] no frame!</em><br><em>[h264 @ 0000013f85b22440] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2</em><br><em>[h264 @ 0000013f85b22440] Format cuda chosen by get_format().</em><br><em>[h264 @ 0000013f85b22440] Format cuda requires hwaccel initialisation.</em><br><em>[h264 @ 0000013f85b22440] Loaded lib: nvcuvid.dll</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidGetDecoderCaps</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCreateDecoder</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidDestroyDecoder</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidDecodePicture</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidGetDecodeStatus</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidReconfigureDecoder</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidMapVideoFrame64</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidUnmapVideoFrame64</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCtxLockCreate</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCtxLockDestroy</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCtxLock</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCtxUnlock</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCreateVideoSource</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCreateVideoSourceW</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidDestroyVideoSource</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidSetVideoSourceState</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidGetVideoSourceState</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidGetSourceVideoFormat</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidGetSourceAudioFormat</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidCreateVideoParser</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidParseVideoData</em><br><em>[h264 @ 0000013f85b22440] Loaded sym: cuvidDestroyVideoParser</em><br><em>[h264 @ 0000013f85b22440] NVDEC capabilities:</em><br><em>[h264 @ 0000013f85b22440] format supported: yes, max_mb_count: 65536</em><br><em>[h264 @ 0000013f85b22440] min_width: 48, max_width: 4096</em><br><em>[h264 @ 0000013f85b22440] min_height: 16, max_height: 4096</em><br><em>[h264 @ 0000013f85bd04c0] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2</em><br><em>[h264 @ 0000013f1cec7580] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2</em><br><em>[h264 @ 0000013f6efb0f40] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 2<br><br></em><span>I've attached the most important code snippet to this mail. Hope it will help.</span><em><br></em></p><br><br><br><blockquote style="border-left:1px solid #0857A6;margin:10px;padding:0 0 0 10px;">
Среда, 17 апреля 2019, 12:21 +03:00 от Hristo Ivanov <<a href="mailto:hivanov.ffmailing@gmail.com">hivanov.ffmailing@gmail.com</a>>:<br>
<br>
<div id="">
<div class="js-helper_mailru_css_attribute_postfix js-readmsg-msg_mailru_css_attribute_postfix">
<style></style>
<div>
<div id="style_15554929160000000771_BODY_mailru_css_attribute_postfix"><div class="class_1555502464_mailru_css_attribute_postfix"><div dir="ltr"><div dir="ltr"><font face="monospace, monospace">Hi.<br></font></div><div dir="ltr"><font face="monospace, monospace"><br></font></div><div dir="ltr"><font face="monospace, monospace">> Is it because of NVIDIA GPUs have concurrent session limitation?</font></div><div dir="ltr"><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">There is a session limitation for encoding for sure, but I think there is no such thing for decoding:</font></div><div><font face="monospace, monospace"><a rel="noopener noreferrer" href="https://developer.nvidia.com/video-encode-decode-gpu-support-matrix" target="_blank">https://developer.nvidia.com/video-encode-decode-gpu-support-matrix</a><br></font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">> By the way, I don't understand where these messages are come from. They are just printed in my console.<br></font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Those messages are from the ffmpeg log. The ffmpeg code is full with calls to 'av_log(void *avcl, int level, const char *fmt, ....)'.</font></div><div><font face="monospace, monospace">Depending on the loglevel in use the messages are printed or ignored.</font></div><div><font face="monospace, monospace">For the ffmpeg tool the '-loglevel' flag can be used to configure what messages should be printed and what messages should not.</font></div><div><font face="monospace, monospace">With the C-API, the '<span style="color:rgb(0,0,0);white-space:pre-wrap">av_log_set_level(int level)' function can be used to configure the log level.</span></font></div><div><font face="monospace, monospace">The different log levels can be seen here:</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace"><a rel="noopener noreferrer" href="https://ffmpeg.org/doxygen/trunk/group__lavu__log__constants.html" target="_blank">https://ffmpeg.org/doxygen/trunk/group__lavu__log__constants.html</a> </font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Running your program with log level verbose or maybe even debug could give you some clue to why the creation of the 6th decoder fails.</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Are the video streams 4K? My guest is you are running out of memory on the GPU.</font></div><div><font face="monospace, monospace"><br></font></div><div><font face="monospace, monospace">Regards.</font></div></div>
</div></div>
<div>_______________________________________________<br>
Libav-user mailing list<br>
<a rel="noopener noreferrer" href="//e.mail.ru/compose/?mailto=mailto%3aLibav%2duser@ffmpeg.org">Libav-user@ffmpeg.org</a><br>
<a rel="noopener noreferrer" href="https://ffmpeg.org/mailman/listinfo/libav-user" target="_blank">https://ffmpeg.org/mailman/listinfo/libav-user</a><br>
<br>
To unsubscribe, visit link above, or email<br>
<a rel="noopener noreferrer" href="//e.mail.ru/compose/?mailto=mailto%3alibav%2duser%2drequest@ffmpeg.org">libav-user-request@ffmpeg.org</a> with subject "unsubscribe".</div>
</div>
</div>
</div>
</blockquote>
<br>
<br>-- <br>С уважением, Ахмед Анам.<br>Best regards, Akhmed Anam.<br>
</div></div>
</div>
</div>
</div>
</blockquote>
<br>
<br>-- <br>С уважением, Ахмед Анам.<br>Best regards, Akhmed Anam.<br></BODY></HTML>