splitmuxsink doubt

[bfork]

Hi guys,
First of all, thanks for such a great product!

I am willing to implement a pipeline to record to a set a files the video coming from the Rasperberry PI camera. I have Rpi3.
I have succesfully installed from sources v 1.12.2

But when trying the sample from the documentation () I get this error>

gst-launch-1.0 -e v4l2src num-buffers=500 ! video/x-raw,width=320,height=240 ! videoconvert ! queue ! timeoverlay ! x264enc key-int-max=10 ! h264parse ! splitmuxsink location=video%02d.mov max-size-time=10000000000 max-size-bytes=1000000
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Redistribute latency...
**
ERROR:gstv4l2bufferpool.c:1119:gst_v4l2_buffer_pool_qbuf: assertion failed: ("Value of time " "timestamp" " is out of timeval's range" && ((timestamp) / GST_SECOND) < G_MAXLONG)
Aborted


Any clues?

Thanks in advance.

[Baby Octopus]

Can you search in the gstreamer source code from where this error message is coming? My first suspect would with v4l2 driver of the device

[Nicolas Dufresne-5]

Le lundi 31 juillet 2017 à 09:56 -0700, bfork a écrit :

> I am willing to implement a pipeline to record to a set a files the video
> coming from the Rasperberry PI camera. I have Rpi3.
> I have succesfully installed from sources v 1.12.2
>
> But when trying the sample from the documentation () I get this error>
>
> gst-launch-1.0 -e v4l2src num-buffers=500 ! video/x-raw,width=320,height=240
> ! videoconvert ! queue ! timeoverlay ! x264enc key-int-max=10 ! h264parse !
> splitmuxsink location=video%02d.mov max-size-time=10000000000
> max-size-bytes=1000000
> Setting pipeline to PAUSED ...
> Pipeline is live and does not need PREROLL ...
> Setting pipeline to PLAYING ...
> New clock: GstSystemClock
> Redistribute latency...
> **
> ERROR:gstv4l2bufferpool.c:1119:gst_v4l2_buffer_pool_qbuf: assertion failed:
> (*"Value of time " "timestamp" " is out of timeval's range" && ((timestamp)
> / GST_SECOND) < G_MAXLONG*)
> Aborted
>
>
> Any clues?

Can you file a bug at bugs.gnome.org. I think we should reset the
timestamp to -1 in the buffer pool reset() virtual function to avoid
this. Timestamp when queuing into a capture device are meaningless.
It's first time that get reported, but it can only occur on 32bit
platform.

regards,
Nicolas
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-5]

Le lundi 31 juillet 2017 à 10:33 -0700, Baby Octopus a écrit :
> Can you search in the gstreamer source code from where this error message is
> coming? My first suspect would with v4l2 driver of the device

It is, again, please file a bug, I'll provide with details over there.

regards,
Nicolas
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel