GNOME Bugzilla – Bug 784899
examples/test-launch creates for each reciver a new pipeline
Last modified: 2017-07-13 12:51:17 UTC
Created attachment 355503 [details] 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...