<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">Le ven. 7 déc. 2018 05 h 11, Wolfgang Grandegger <<a href="mailto:wg@grandegger.com">wg@grandegger.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
hmm, the long story: My camera records AVCHD video with 1920x1080 pixel<br>
and 50 frames/sec. Then I convert it to an 50 FPS AVI raw video using:<br>
<br>
$ ffmpeg -i input.mts -vcodec rawvideo -y output-50fps.avi<br>
<br>
To get the same video running at 60 FPS I do:<br>
<br>
$ ffmpeg -i input.mts -filter:v "setpts=0.83333333*PTS" \<br>
-r 60 -vcodec rawvideo -y output-60fps.avi<br>
<br>
I assume that this video uses the same raw frames just with different<br>
time stamps. What do I miss?<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Understand that this could also be the threshold your receiving socket can carry with its current setting. It cost nothing to try and increase it, see buffer-size on udp-sink and sysctl net.core.rmem_max setting of your Linux kernel (if Linux is your host OS).</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
<br>
Wolfgang.<br>
<br>
Am 07.12.2018 um 10:13 schrieb Ian Davidson:<br>
> You start with a video recorded at 50 fps and convert it to 60 fps. So,<br>
> for each 5 frames of the original video, something has to 'invent' 1<br>
> extra frame. It is never going to be 'perfect'.<br>
> <br>
> <br>
> On 06/12/18 19:50, Wolfgang Grandegger wrote:<br>
>><br>
>> Not sure if I understand you correctly. I do not change FPS on the fly.<br>
>> I convert my MJPEG video from 50 to 60 FPS on the remote side with<br>
>><br>
>> $ ffmpeg ... -filter:v "setpts=0.83333333*PTS" -r 60 ...<br>
>><br>
>> and then send it to the network. The video with 50 FPS is recorded<br>
>> and displayed fine. The one with 60 FPS causes jerking on the display.<br>
>> The jerking is also visible on the recorded video... hm, can I assume<br>
>> that the "rtpjitterbuffer" calculated jerky timestamps then?<br>
>><br>
> <br>
> _______________________________________________<br>
> gstreamer-devel mailing list<br>
> <a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">gstreamer-devel@lists.freedesktop.org</a><br>
> <a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank" rel="noreferrer">gstreamer-devel@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
</blockquote></div></div></div>