[Bug 784899] New: examples/test-launch needs for each stream one connection to source

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Thu Jul 13 12:14:37 UTC 2017


https://bugzilla.gnome.org/show_bug.cgi?id=784899

            Bug ID: 784899
           Summary: examples/test-launch needs for each stream one
                    connection to source
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: other
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-rtsp-server
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: gsttester at vnedu.me
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 355503
  --> https://bugzilla.gnome.org/attachment.cgi?id=355503&action=edit
example image

I have noticed that the examples/test-launch needs for each reviver/client a
new connection to the source. 

Other example applications need only one connection. I have modivied
test-readme to use the same source as test-lauch and it only connets one time
to the source.

It’s not only the connection, it’s also the whole piplie with encoder etc.
If you look at the CPU usage you can see that for each reciver the video gets
seperated encodet (more reciver more CPU usage).

I’m not sure but when I look in the history of of test-lauch I gues it didn’t
behave like that from the start.

In my attachment I use an IP Cam as source and VLC Player as reciver. I also
testet it with other sources and reciver.


Also nearly all of your test applications have the same comments in code. The
individual code gets no explanation only the code witch is in all applications
the same. What is the use of an example if you don’t explan it?
Perhaps there is no bug in test-lauch but since it’s function is not explained
I don’t know.
If there is some dokumentation for the test applications it’s not easy to
find...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list