I am having issues with DashCast when performing simple local RTSP streaming. I've recently updated ffmpeg, x264 and gpac. I am using vlc as the streaming server with command:
with the simple dashcast.conf: [v1]
type=video
width=640
height=480
bitrate=800000
which results to several "[DashCast] Capture lost xxx video frames" and lost frames can be also observed when viewing the output with MP4Client. Any suggestions where the problems is, maybe it is some conf. issue? I have also tested with .mp4 and the result is the same.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
-npts has issues with some webcams settings, especially asking X FPS and getting Y!= X FPS: in this case -npts option won't notice any frame drop and the segments will have broken timing.
However this is not fully functional I fear, we need to do some code cleanup here ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having issues with DashCast when performing simple local RTSP streaming. I've recently updated ffmpeg, x264 and gpac. I am using vlc as the streaming server with command:
vlc video.avi --sout='#rtp{sdp=rtsp//:8554/session.sdp}'
and DashCast
DashCast -v rtsp://@localhost:8554/session.sdp -vres 640x480 -vfr 30 -conf dashcast.conf -live
with the simple dashcast.conf:
[v1]
type=video
width=640
height=480
bitrate=800000
which results to several "[DashCast] Capture lost xxx video frames" and lost frames can be also observed when viewing the output with MP4Client. Any suggestions where the problems is, maybe it is some conf. issue? I have also tested with .mp4 and the result is the same.
Is the viewing fine with a regular RTSP client ?
Could you try adding -npts switch to DashCast command line ?
Thank you for the answer, -npts worked for me in most cases, especially with webcam. Can you say why DashCast gives these errors without -npts switch?
Yes, regular clients, such as FFplay works just fine for the stream.
-npts has issues with some webcams settings, especially asking X FPS and getting Y!= X FPS: in this case -npts option won't notice any frame drop and the segments will have broken timing.
However this is not fully functional I fear, we need to do some code cleanup here ...