GNOME Bugzilla – Bug 778375
tcpserversink on Windows not working as it should.
Last modified: 2018-01-20 11:03:55 UTC
I may have found a bug regarding tcpserversink / tcpclientsrc on Windows 10 with GStreamer 10.0.3 32 bit . If I start 2 pipelines like: get-launch-1.0 -v videotestsrc ! gdppay ! tcpserversink and get-launch-1.0 -v tcpclientsrc ! gdpdepay ! glimagesink or get-launch-1.0 -v tcpclientsink ! gdpdepay ! fakesink silent=false the receiving pipeline only gets the first image and then freezes. The same pipelines on linux work as they should. If I stop ther server pipeline the client pipeline also exits, what means it is still alive but not processing incoming buffers. Further testing indicates that the problem is located on the tcpserversink side: 1.) Switching client server like: > get-launch-1.0 -v videotestsrc ! gdppay ! tcpclientsink and > get-launch-1.0 -v tcpserversrc ! gdpdepay ! glimagesink works on Windows! 2.) Sending the data through local LAN to another Computer (Mac-OSX) also only failed if the tcpserversink is sending from Windows. If I start the server pipeline on the OSX side, data is received and plays on the windows side.
Can you provide a log from the server and client where it fails?
Closing as no futher information has been provided. But there's also a newer/active bug, so I will dup this to that insteda. *** This bug has been marked as a duplicate of bug 791766 ***