I did leave out one detail. Currently kodi is using v4.0.4. It's possible there was a fix since that prevents rt->rtsp_hd being NULL in the call to rtsp_send_cmd_with_content_async in the first place.
Won't be able to test with 4.2 and kodi until the version gets bumped to see if it persists without the patch. Could be that a flow used in kodi causes this to go to NULL. However, checking if rt->rtsp_hd_out is not null before calling rtsp_send_cmd_with_content_async should cause no harm either. On Thu, 29 Aug 2019 at 00:20, Jun Li <junli1...@gmail.com> wrote: > On Wed, Aug 28, 2019 at 3:09 PM Carl Eugen Hoyos <ceffm...@gmail.com> > wrote: > > > Am Mo., 5. Aug. 2019 um 09:19 Uhr schrieb Ross Nicholson < > > phunkyf...@gmail.com>: > > > > > > Example stream that does not work: rtsp:// > > > 184.72.239.149/vod/mp4:BigBuckBunny_115k.mov > > > > Is this still valid? > > > > > Carl, you can try this one for validation: rtsp:// > wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov > > Hi Ross, > Just curious, is there any case the rt->rtsp_hd_out is NULL ? > Looks like the hd_out is either TCP or HTTP(http tunnel case) for RTSP > connection. And I only see it is set to NULL in ff_rtsp_close_connections, > which is called after your check. > > -Jun > > I get a time-out both with and without your patch. > > > > Carl Eugen > > _______________________________________________ > > ffmpeg-devel mailing list > > ffmpeg-devel@ffmpeg.org > > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > > > To unsubscribe, visit link above, or email > > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
