New NvStreammux GStreamer error: clock problem

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) GPU
• DeepStream Version 6.1
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only) 510
• Issue Type( questions, new requirements, bugs) issue
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)

I am trying to use the new nvstreammux with sync-inputs=1 and max-latency=1*1e9. It is working as expected. It drops frames when nvinfer is not able to keep up with rtsp source rate of 25fps. It processes only latest frames. However, it is flooding the message bus with WARNING and ERROR

Here is my bus on_message callback

gboolean
    cb_bus_call_handle_exit_on_eos(GstBus *bus, GstMessage *msg, gpointer data)
    {
        CallBkData *clbkdata = (CallBkData *)data;
        GMainLoop *loop = (GMainLoop *)
                              clbkdata->loop;
        switch (GST_MESSAGE_TYPE(msg))
        {
        case GST_MESSAGE_EOS:

            logw("EOS from element {}",
                 GST_OBJECT_NAME(msg->src));
            logd("Mode exit_on_eos : End of stream received; Exiting loop");
            g_main_loop_quit(loop);
            break;
        case GST_MESSAGE_WARNING:
        {
            gchar *debug;
            GError *error;
            gst_message_parse_warning(msg, &error, &debug);
            logw("WARNING from element {}: {}",
                 GST_OBJECT_NAME(msg->src), error->message);
            g_free(debug);
            loge("Warning: {}", error->message);
            g_error_free(error);
            break;
        }
        case GST_MESSAGE_ERROR:
        {
            gchar *debug;
            GError *error;
            gst_message_parse_error(msg, &error, &debug);
            loge("ERROR from element {}: {}",
                 GST_OBJECT_NAME(msg->src), error->message);
            if (debug)
                loge("Error details: {}", debug);
            g_free(debug);
            g_error_free(error);
            break;
        }
        case GST_MESSAGE_ELEMENT:
        {
            if (gst_nvmessage_is_stream_eos(msg))
            {
                guint stream_id;
                if (gst_nvmessage_parse_stream_eos(msg, &stream_id))
                {
                    logw("Got EOS from source (number)-{}",
                         stream_id);
                    logd("Mode exit_on_eos : End of stream received; Exiting loop");
                    g_main_loop_quit(loop);
                }
            }
            break;
        }
        default:
            break;
        }
        return TRUE;
    }

When I run the application, this is the error message I see

17:05:36.952813 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:36.952978 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:36.952979 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.011514 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.011516 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.011632 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.011632 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.070121 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.070125 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.070800 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.070801 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.070910 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.070911 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.090217 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.090219 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.125362 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.125363 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.
17:05:37.125539 dsutils.hpp:769 WRN[483311] WARNING from element stream-muxer: GStreamer error: clock problem.
17:05:37.125540 dsutils.hpp:772 ERR[483311] Warning: GStreamer error: clock problem.

What can be done?

What’s your whole pipeline like and did you use our demo code? Does this error affect the normal operation of pipeline?

There are 4 cameras connected to the pipeline, followed by nvstreammux, nvinfer, tee and a 3 sinks - appsink, displaysink and filesink. The error doesn’t seem to impact normal operation of pipeline.

Could this error be related to system time vs rtsp PTS time ? My system clock is not in sync with the camera timestamps.

There is no update from you for a period, assuming this is not an issue anymore.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

It may be related to this problem. Could you help to narrow down the scope of the problem?
1.try to add some queue in your pipeline.
2.use only one source and one sink
3.try to set a larger value for max-latency

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.