Open neilyoung opened 2 years ago
Here the unexpected messages:
Neils-MBP:GStreamer-Python neilyoung$ python3 main_prg.py
Unexpected message received. <flags GST_MESSAGE_LATENCY of type Gst.MessageType>
Pipeline state changed from null to ready.
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Pipeline state changed from ready to paused.
Unexpected message received. <flags GST_MESSAGE_NEW_CLOCK of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
0:00:00.495428000 9335 0x7fead986c4c0 FIXME default gstutils.c:4026:gst_pad_create_stream_id_internal:<fakesrc0:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
Unexpected message received. <flags GST_MESSAGE_STREAM_STATUS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_STREAM_STATUS of type Gst.MessageType>
Unexpected message received. <flags GST_MESSAGE_PROGRESS of type Gst.MessageType>
Well, yes. TCP is a very optimistic assumption...
And then this with 720p...
I420
720
1280
Traceback (most recent call last):
File "/Users/neilyoung/Documents/Python/GStreamer-Python/vid_streamv3.py", line 78, in new_buffer
arr = self.gst_to_opencv(sample)
File "/Users/neilyoung/Documents/Python/GStreamer-Python/vid_streamv3.py", line 68, in gst_to_opencv
arr = np.ndarray(
TypeError: buffer is too small for requested array
Works:
Does not work: