I am trying to get a simple udpsink/udpsrc example to work using two windows machines connected to a local lan but it’s not working.
Sender is windows xp with the following pipeline using the launch tool:
audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 !
udpsink clients="192.168.1.101:5004" The ip address used by the sender is for the receiving [destination] machine. The sender machine has the windows firewall disabled.
Receiver is windows 7 x86 with the following pipeline using the launch tool:
udpsrc ! fakesink dump=true The inspect tool shows that the default port for udpsrc is 5004. I allowed this port through the windows firewall on the receiving machine.
Wireshark on the receiver machine shows data coming in from the sender machine on port 5004 but nothing is displayed. No pipeline errors are reported for either machine.
I’m using GStreamer 1.6.4 with your windows pre-built binaries.
I must be tripping over something simple. Any ideas on what I might be doing wrong? Thanks, Bill _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
On Mo, 2016-06-13 at 21:29 +0000, William Salibrici wrote:
> I am trying to get a simple udpsink/udpsrc example to work using two > windows machines connected to a local lan but it’s not working. > > Sender is windows xp with the following pipeline using the launch > tool: > > audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! > > udpsink clients="192.168.1.101:5004" > > The ip address used by the sender is for the receiving [destination] > machine. The sender machine has the windows firewall disabled. > > > > Receiver is windows 7 x86 with the following pipeline using the > launch tool: > > udpsrc ! fakesink dump=true > > The inspect tool shows that the default port for udpsrc is 5004. I > allowed this port through the windows firewall on the receiving > machine. > > > > Wireshark on the receiver machine shows data coming in from the > sender machine on port 5004 but nothing is displayed. No pipeline > errors are reported for either machine. > > I’m using GStreamer 1.6.4 with your windows pre-built binaries. > > I must be tripping over something simple. Any ideas on what I might > be doing wrong? property on the udpsrc to 192.168.1.101 (the address where you're sending to)? That shouldn't be necessary, but maybe it helps. Also please get a debug log with GST_DEBUG=6 of the receiver. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
Sebastian,
I cannot seem to find where I can get the 1.8.2 version with binaries for windows. The Gstreamer home page seems to indicate that binaries for windows are not yet available [as of 6/9/16]. I can get the 1.8.1 version from here: https://gstreamer.freedesktop.org/data/pkg/windows/1.8.1/ Should I use the 1.8.1? Regards, Bill -----Original Message----- From: gstreamer-devel [mailto:[hidden email]] On Behalf Of Sebastian Dröge Sent: Tuesday, June 14, 2016 2:17 AM To: Discussion of the development of and with GStreamer <[hidden email]> Subject: Re: udpsrc has no data for windows On Mo, 2016-06-13 at 21:29 +0000, William Salibrici wrote: > I am trying to get a simple udpsink/udpsrc example to work using two > windows machines connected to a local lan but it’s not working. > > Sender is windows xp with the following pipeline using the launch > tool: > > audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! > > udpsink clients="192.168.1.101:5004" > > The ip address used by the sender is for the receiving [destination] > machine. The sender machine has the windows firewall disabled. > > > > Receiver is windows 7 x86 with the following pipeline using the launch > tool: > > udpsrc ! fakesink dump=true > > The inspect tool shows that the default port for udpsrc is 5004. I > allowed this port through the windows firewall on the receiving > machine. > > > > Wireshark on the receiver machine shows data coming in from the sender > machine on port 5004 but nothing is displayed. No pipeline errors are > reported for either machine. > > I’m using GStreamer 1.6.4 with your windows pre-built binaries. > > I must be tripping over something simple. Any ideas on what I might be > doing wrong? Can you try with 1.8.2, and also try with setting the "address" property on the udpsrc to 192.168.1.101 (the address where you're sending to)? That shouldn't be necessary, but maybe it helps. Also please get a debug log with GST_DEBUG=6 of the receiver. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
In reply to this post by Sebastian Dröge-3
Sebastian,
I put version 1.8.1 on the receiver machine. That was the newest version I could find with windows pre-built binaries. Here is my receiver pipeline: gst-launch-1.0 -e --gst-debug=*:6 udpsrc address="192.168.1.101" ! fakesink dump=TRUE I have attached the level 6 debug log for the receiver. The pipeline never goes to the playing state for this debug level, it just hangs. If I back down to debug level 4 the pipeline does go to the playing state. I attached that debug log as well. Still no data being displayed for either case above. Your help is much appreciated. Bill -----Original Message----- From: gstreamer-devel [mailto:[hidden email]] On Behalf Of Sebastian Dröge Sent: Tuesday, June 14, 2016 2:17 AM To: Discussion of the development of and with GStreamer <[hidden email]> Subject: Re: udpsrc has no data for windows On Mo, 2016-06-13 at 21:29 +0000, William Salibrici wrote: > I am trying to get a simple udpsink/udpsrc example to work using two > windows machines connected to a local lan but it’s not working. > > Sender is windows xp with the following pipeline using the launch > tool: > > audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! > > udpsink clients="192.168.1.101:5004" > > The ip address used by the sender is for the receiving [destination] > machine. The sender machine has the windows firewall disabled. > > > > Receiver is windows 7 x86 with the following pipeline using the launch > tool: > > udpsrc ! fakesink dump=true > > The inspect tool shows that the default port for udpsrc is 5004. I > allowed this port through the windows firewall on the receiving > machine. > > > > Wireshark on the receiver machine shows data coming in from the sender > machine on port 5004 but nothing is displayed. No pipeline errors are > reported for either machine. > > I’m using GStreamer 1.6.4 with your windows pre-built binaries. > > I must be tripping over something simple. Any ideas on what I might be > doing wrong? property on the udpsrc to 192.168.1.101 (the address where you're sending to)? That shouldn't be necessary, but maybe it helps. Also please get a debug log with GST_DEBUG=6 of the receiver. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
In reply to this post by Sebastian Dröge-3
Sebastian,
I put version 1.8.1 on the receiver machine. That was the newest version I could find with windows pre-built binaries. Here is my receiver pipeline: gst-launch-1.0 -e --gst-debug=*:6 udpsrc address="192.168.1.101" ! fakesink dump=TRUE I got the level 6 debug log for the receiver. The pipeline never goes to the playing state for this debug level, it just hangs. If I back down to debug level 4 the pipeline does go to the playing state. Still no data being displayed for either debug case above. Your help is much appreciated. I replied to you yesterday and attached the log files to the reply email. However, I got this message back: Your mail to 'gstreamer-devel' with the subject RE: udpsrc has no data for windows Is being held until the list moderator can review it for approval. The reason it is being held: Message body is too big: 3016793 bytes with a limit of 1024 KB How else can I get the debug log files to you? Bill PS - If I run the sender and receiver on the same machine [windows 7 at gstreamer version 1.8.1] all works well! -----Original Message----- From: gstreamer-devel [mailto:[hidden email]] On Behalf Of Sebastian Dröge Sent: Tuesday, June 14, 2016 2:17 AM To: Discussion of the development of and with GStreamer <[hidden email]> Subject: Re: udpsrc has no data for windows On Mo, 2016-06-13 at 21:29 +0000, William Salibrici wrote: > I am trying to get a simple udpsink/udpsrc example to work using two > windows machines connected to a local lan but it’s not working. > > Sender is windows xp with the following pipeline using the launch > tool: > > audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! > > udpsink clients="192.168.1.101:5004" > > The ip address used by the sender is for the receiving [destination] > machine. The sender machine has the windows firewall disabled. > > > > Receiver is windows 7 x86 with the following pipeline using the launch > tool: > > udpsrc ! fakesink dump=true > > The inspect tool shows that the default port for udpsrc is 5004. I > allowed this port through the windows firewall on the receiving > machine. > > > > Wireshark on the receiver machine shows data coming in from the sender > machine on port 5004 but nothing is displayed. No pipeline errors are > reported for either machine. > > I’m using GStreamer 1.6.4 with your windows pre-built binaries. > > I must be tripping over something simple. Any ideas on what I might be > doing wrong? Can you try with 1.8.2, and also try with setting the "address" property on the udpsrc to 192.168.1.101 (the address where you're sending to)? That shouldn't be necessary, but maybe it helps. Also please get a debug log with GST_DEBUG=6 of the receiver. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
In reply to this post by William Salibrici
On Mi, 2016-06-15 at 17:23 +0000, William Salibrici wrote:
> Sebastian, > I put version 1.8.1 on the receiver machine. That was the newest > version I could find with windows pre-built binaries. > Here is my receiver pipeline: > > gst-launch-1.0 -e --gst-debug=*:6 udpsrc > address="192.168.1.101" ! fakesink dump=TRUE > > I have attached the level 6 debug log for the receiver. The pipeline > never goes to the playing state for this debug level, it just hangs. > If I back down to debug level 4 the pipeline does go to the playing > state. I attached that debug log as well. > > Still no data being displayed for either case above. > Your help is much appreciated. logs (in the middle of a line). Can you run in gdb and get a backtrace of all threads once it got stuck with printing debug logs? Can you also provide some part of the wireshark capture? -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
Hi Sebastian,
Sorry for the delay – I was away on vacation. Regarding gdb, I’m not familiar with it and it’s not a native windows tool. I looked around and found a website that has 32-bit and 64-bit binaries of gdb for Windows for download here. http://www.equation.com/servlet/equation.cmd?fa=gdb Would you recommend I use a different one? Anyway, they have gdb version 7.9 which is not the latest one [but pretty close]. I downloaded the 64 bit executable [and the manual for it] just to try it. I ran the udp receiver pipeline I shared with you in an earlier email. I set my environment to capture a level 6 debug log. I changed the port to 5018 because netstat showed port 5004 on my windows 7 machine was being used by another process. I captured a screen shot of the gdb debug session as shown in attached file gdb-debug.txt. It looks like the symbols from the launch executable were read in ok. The pipeline hangs just as you saw in the debug file I sent you earlier. At that point I have no gdb prompt either. The signal SIGINT is from my CTL-C to stop the pipeline. The backtrace doesn’t seem to show anything useful but perhaps I’m not using gdb correctly. Maybe the warnings above regarding some windows DLLs indicate that gdb is not functioning properly. Regarding a wireshark capture, please see the attached pcap file. I’m using version 2.0.4, 64 bit. My capture filter is “udp port 5018”. You can see that packets coming from the sender [an xp machine on the same local LAN] are reaching the receiver machine [windows 7 64 bit] running the gdb debug session mentioned above. However, no data is displayed to the screen. As a sanity check, I ran my own C++ udp receiver test app and data from the sender pipeline is received and displayed correctly. This seems to confirm that your udpsrc element is not working properly for a simple receiver case. I’m a little surprised that this is true since udpsrc has been around a while. Anyway, I appreciate your help to resolve this issue. Regards, Bill -----Original Message----- From: gstreamer-devel [mailto:[hidden email]] On Behalf Of Sebastian Dröge Sent: Friday, June 17, 2016 7:34 AM To: Discussion of the development of and with GStreamer <[hidden email]> Subject: Re: udpsrc has no data for windows On Mi, 2016-06-15 at 17:23 +0000, William Salibrici wrote: > Sebastian, > I put version 1.8.1 on the receiver machine. That was the newest > version I could find with windows pre-built binaries. > Here is my receiver pipeline: > > gst-launch-1.0 -e --gst-debug=*:6 udpsrc address="192.168.1.101" ! > fakesink dump=TRUE > > I have attached the level 6 debug log for the receiver. The pipeline > never goes to the playing state for this debug level, it just hangs. > If I back down to debug level 4 the pipeline does go to the playing > state. I attached that debug log as well. > > Still no data being displayed for either case above. > Your help is much appreciated. Can you also provide some part of the wireshark capture? -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
On Fr, 2016-06-24 at 20:45 +0000, William Salibrici wrote:
> Hi Sebastian, > Sorry for the delay – I was away on vacation. > > Regarding gdb, I’m not familiar with it and it’s not a native windows > tool. I looked around and found a website that has 32-bit and 64-bit > binaries of gdb for Windows for download here. > > http://www.equation.com/servlet/equation.cmd?fa=gdb > > Would you recommend I use a different one? > > Anyway, they have gdb version 7.9 which is not the latest one [but > pretty close]. I downloaded the 64 bit executable [and the manual for > it] just to try it. I ran the udp receiver pipeline I shared with you > in an earlier email. I set my environment to capture a level 6 debug > log. I changed the port to 5018 because netstat showed port 5004 on > my windows 7 machine was being used by another process. I captured a > screen shot of the gdb debug session as shown in attached file gdb- > debug.txt. It looks like the symbols from the launch executable were > read in ok. > > The pipeline hangs just as you saw in the debug file I sent you > earlier. At that point I have no gdb prompt either. The signal SIGINT > is from my CTL-C to stop the pipeline. The backtrace doesn’t seem to > show anything useful but perhaps I’m not using gdb correctly. Maybe > the warnings above regarding some windows DLLs indicate that gdb is > not functioning properly. the gdb from here: https://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20(Win64%20hosted)/gdb/ > Regarding a wireshark capture, please see the attached pcap file. I’m > using version 2.0.4, 64 bit. My capture filter is “udp port 5018”. > You can see that packets coming from the sender [an xp machine on the > same local LAN] are reaching the receiver machine [windows 7 64 bit] > running the gdb debug session mentioned above. However, no data is > displayed to the screen. > > As a sanity check, I ran my own C++ udp receiver test app and data > from the sender pipeline is received and displayed correctly. This > seems to confirm that your udpsrc element is not working properly for > a simple receiver case. I’m a little surprised that this is true > since udpsrc has been around a while. contains parts of a huge packet that is fragmented in various smaller packets. udpsrc (and in general an UDP socket) is not going to receive those unless all of them are actually captured. What exactly is your sender application for this? It should really use smaller UDP packets. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
Sebastian,
Here is my sender pipeline running on a separate machine: gst-launch-1.0 -e audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! udpsink clients="192.168.1.101:5018" I'm not sure what the default udp packet size would be for this pipeline. I see from the inspect tool that udpsink has bytes-to-serve and buffer-size properties. They both have default values of 0 so it doesn't seem like they would affect the udp packet size. My own C++ udp receiver test app receives and displays data from the sender pipeline above just fine. Regards, Bill -----Original Message----- From: gstreamer-devel [mailto:[hidden email]] On Behalf Of Sebastian Dröge Sent: Monday, June 27, 2016 3:38 AM To: Discussion of the development of and with GStreamer <[hidden email]> Subject: Re: udpsrc has no data for windows On Fr, 2016-06-24 at 20:45 +0000, William Salibrici wrote: > Hi Sebastian, > Sorry for the delay – I was away on vacation. > > Regarding gdb, I’m not familiar with it and it’s not a native windows > tool. I looked around and found a website that has 32-bit and 64-bit > binaries of gdb for Windows for download here. > > http://www.equation.com/servlet/equation.cmd?fa=gdb > > Would you recommend I use a different one? > > Anyway, they have gdb version 7.9 which is not the latest one [but > pretty close]. I downloaded the 64 bit executable [and the manual for > it] just to try it. I ran the udp receiver pipeline I shared with you > in an earlier email. I set my environment to capture a level 6 debug > log. I changed the port to 5018 because netstat showed port 5004 on my > windows 7 machine was being used by another process. I captured a > screen shot of the gdb debug session as shown in attached file gdb- > debug.txt. It looks like the symbols from the launch executable were > read in ok. > > The pipeline hangs just as you saw in the debug file I sent you > earlier. At that point I have no gdb prompt either. The signal SIGINT > is from my CTL-C to stop the pipeline. The backtrace doesn’t seem to > show anything useful but perhaps I’m not using gdb correctly. Maybe > the warnings above regarding some windows DLLs indicate that gdb is > not functioning properly. The output from gdb looks rather useless unfortunately. I usually use the gdb from here: https://sourceforge.net/projects/mingw-w64/files/External%20binary%20packages%20(Win64%20hosted)/gdb/ > Regarding a wireshark capture, please see the attached pcap file. I’m > using version 2.0.4, 64 bit. My capture filter is “udp port 5018”. > You can see that packets coming from the sender [an xp machine on the > same local LAN] are reaching the receiver machine [windows 7 64 bit] > running the gdb debug session mentioned above. However, no data is > displayed to the screen. > > As a sanity check, I ran my own C++ udp receiver test app and data > from the sender pipeline is received and displayed correctly. This > seems to confirm that your udpsrc element is not working properly for > a simple receiver case. I’m a little surprised that this is true since > udpsrc has been around a while. The pcap capture does not contain a single valid packet. It only contains parts of a huge packet that is fragmented in various smaller packets. udpsrc (and in general an UDP socket) is not going to receive those unless all of them are actually captured. What exactly is your sender application for this? It should really use smaller UDP packets. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
On Mo, 2016-06-27 at 15:04 +0000, William Salibrici wrote:
> Sebastian, > Here is my sender pipeline running on a separate machine: > > gst-launch-1.0 -e audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! udpsink clients="192.168.1.101:5018" > > I'm not sure what the default udp packet size would be for this pipeline. 2048 bytes: 16 bits per sample, 1024 samples per buffer. Does it work better with samplesperbuffer=512 on the audiotestsrc? In general it's a bad idea to send UDP packets that are bigger than the MTU, which usually is 1500 bytes (minus UDP header size) or less. Also try setting the buffer-size property on udpsrc (and maybe the sink) to some higher value, like 1MB. > I see from the inspect tool that udpsink has bytes-to-serve and buffer-size properties. > They both have default values of 0 so it doesn't seem like they would affect the udp packet size. They are unrelated to the packet size. The packet size is defined by the buffer size that goes into udpsink. > My own C++ udp receiver test app receives and displays data from the sender pipeline above just fine. Unlikely that it did with the wireshark capture you just sent though. However if there is no packet loss, it should indeed work :) -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
Hi Sebastian,
I did as you suggested. I set the samplesperbuffer=512 on the audiotestsrc. I also set the buffer-size property on udpsrc/udpsink to 1MB. Send pipeline now is: gst-launch-1.0 -e audiotestsrc wave=2 samplesperbuffer=512 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! udpsink buffer-size=1000000 clients="192.168.1.101:5018" Receive pipeline now is: gst-launch-1.0 -e udpsrc address="192.168.1.101" buffer-size=1000000 port=5018 caps="audio/x-raw,format=S16LE,rate=8000,channels=1" ! fakesink dump=TRUE Still no data displayed for the receiver pipeline on my windows 7 machine! I attached the new wireshark capture file obtained from the receiver machine which now shows no fragmentation. I think the IP layer does support fragmentation and reassembly but there are a number of possible drawbacks there as well. I followed the udp stream in wireshark [40 packets total for test session] and saved the raw packet data to a file [size 40960 bytes]. I used Audacity [a free, open source, cross-platform software for recording and editing sounds from here: http://audacity.sourceforge.net/ ] to import the raw audio data, gave it the audio data format, and it plays just fine. I used my own C++ udp receiver test app to capture data during the same test session as above and also saved it to a raw file. I compared it to the wireshark capture file and it is identical. This shows that my test app is in fact receiving all the udp data for the no-fragmentation case. As I mentioned in an earlier email of our conversation, if I run the sender and receiver on the same machine [windows 7 at gstreamer version 1.8.1] all works well! Regards, Bill -----Original Message----- From: gstreamer-devel [mailto:[hidden email]] On Behalf Of Sebastian Dröge Sent: Tuesday, June 28, 2016 3:34 AM To: Discussion of the development of and with GStreamer <[hidden email]> Subject: Re: udpsrc has no data for windows On Mo, 2016-06-27 at 15:04 +0000, William Salibrici wrote: > Sebastian, > Here is my sender pipeline running on a separate machine: > > gst-launch-1.0 -e audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! udpsink clients="192.168.1.101:5018" > > I'm not sure what the default udp packet size would be for this pipeline. 2048 bytes: 16 bits per sample, 1024 samples per buffer. Does it work better with samplesperbuffer=512 on the audiotestsrc? In general it's a bad idea to send UDP packets that are bigger than the MTU, which usually is 1500 bytes (minus UDP header size) or less. Also try setting the buffer-size property on udpsrc (and maybe the sink) to some higher value, like 1MB. > I see from the inspect tool that udpsink has bytes-to-serve and buffer-size properties. > They both have default values of 0 so it doesn't seem like they would affect the udp packet size. They are unrelated to the packet size. The packet size is defined by the buffer size that goes into udpsink. > My own C++ udp receiver test app receives and displays data from the sender pipeline above just fine. Unlikely that it did with the wireshark capture you just sent though. However if there is no packet loss, it should indeed work :) -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel udp-recv-test-2.pcap (57K) Download Attachment |
On Mi, 2016-06-29 at 17:07 +0000, William Salibrici wrote:
> Hi Sebastian, > I did as you suggested. I set the samplesperbuffer=512 on the > audiotestsrc. I also set the buffer-size property on udpsrc/udpsink > to 1MB. > > Send pipeline now is: > gst-launch-1.0 -e audiotestsrc wave=2 samplesperbuffer=512 ! audio/x- > raw,format=S16LE,rate=8000,channels=1 ! udpsink buffer-size=1000000 > clients="192.168.1.101:5018" > > Receive pipeline now is: > gst-launch-1.0 -e udpsrc address="192.168.1.101" buffer-size=1000000 > port=5018 caps="audio/x-raw,format=S16LE,rate=8000,channels=1" ! > fakesink dump=TRUE > > Still no data displayed for the receiver pipeline on my windows 7 > machine! > > I attached the new wireshark capture file obtained from the receiver > machine which now shows no fragmentation. I think the IP layer does > support fragmentation and reassembly but there are a number of > possible drawbacks there as well. debug log with GST_DEBUG=2,*udp*:6 from the receiver side? Also which GStreamer version is this again? Basically we'll have to find out what works different between udpsrc and your C++ code that handles the sockets. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
In reply to this post by William Salibrici
Send pipeline now is: Sorry to hijack this thread but I was having similar problems on Windows. Here's the thread: http://gstreamer-devel.966125.n4.nabble.com/Multicast-RTP-not-working-on-Windows-td4677923.html Couldn't figure a solution to this. _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
On Do, 2016-06-30 at 13:19 +0530, Anuj Pahuja wrote:
> > Sorry to hijack this thread Please don't do that, it's confusing for everybody :) > but I was having similar problems on Windows. Here's the thread: > > http://gstreamer-devel.966125.n4.nabble.com/Multicast-RTP-not-working > -on-Windows-td4677923.html > > Couldn't figure a solution to this. You didn't reply to my last suggestion there. Can you reply to the original thread with the results of that? You're doing multicast, this one here is unicast... can be completely different problems. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
In reply to this post by Sebastian Dröge-3
Sebastian,
I decided to review our entire conversation on this question from the very beginning [my initial post 6/13/16] before starting down the path you suggested. It turns out that I only had to do the following three things on my windows machine to get the udp receiver working. 1. Upgrade to gstreamer version 1.8.1, 2. Modify my windows firewall to open the udp port, and 3. Set the "address" property on the udpsrc. Here is the sender pipeline [no change from my initial post, works ok]: audiotestsrc wave=2 ! audio/x-raw,format=S16LE,rate=8000,channels=1 ! udpsink clients="192.168.1.101:5004" Here is the initial windows receiver pipeline THAT DID NOT WORK: udpsrc ! fakesink dump=true Here is the working windows receiver pipeline today: udpsrc address="192.168.1.101" ! fakesink dump=TRUE I tried so many different combinations and permutations that I must have confused myself somewhere along the way. I could not reproduce some scenarios I thought didn’t work. At one point it looked like dump=TRUE was the problem and dump=true worked ok, but I cannot reproduce that case. They both seem to work ok today. Another time I thought your default port 5004 was the problem because it looked like another app on my machine was using it, but using your default port now works ok, etc. Another thing I realized is I powered down and restarted my windows development machine multiple times during the time period of our conversation. That may have cleared out some weird internal windows problem that occurred as a result of some the tests I tried. Anyway, my simple windows udp receiver pipeline [as shown above] appears to be finally working ok. There’s no need to go any further on this. Thank you for your insights though – I still learned a lot through it all! Regards, Bill -----Original Message----- From: gstreamer-devel [mailto:[hidden email]] On Behalf Of Sebastian Dröge Sent: Thursday, June 30, 2016 2:47 AM To: Discussion of the development of and with GStreamer <[hidden email]> Subject: Re: udpsrc has no data for windows On Mi, 2016-06-29 at 17:07 +0000, William Salibrici wrote: > Hi Sebastian, > I did as you suggested. I set the samplesperbuffer=512 on the > audiotestsrc. I also set the buffer-size property on udpsrc/udpsink to > 1MB. > > Send pipeline now is: > gst-launch-1.0 -e audiotestsrc wave=2 samplesperbuffer=512 ! audio/x- > raw,format=S16LE,rate=8000,channels=1 ! udpsink buffer-size=1000000 > clients="192.168.1.101:5018" > > Receive pipeline now is: > gst-launch-1.0 -e udpsrc address="192.168.1.101" buffer-size=1000000 > port=5018 caps="audio/x-raw,format=S16LE,rate=8000,channels=1" ! > fakesink dump=TRUE > > Still no data displayed for the receiver pipeline on my windows 7 > machine! > > I attached the new wireshark capture file obtained from the receiver > machine which now shows no fragmentation. I think the IP layer does > support fragmentation and reassembly but there are a number of > possible drawbacks there as well. Ok, this should clearly work like that then. Can you get a GStreamer debug log with GST_DEBUG=2,*udp*:6 from the receiver side? Also which GStreamer version is this again? Basically we'll have to find out what works different between udpsrc and your C++ code that handles the sockets. -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
On Fr, 2016-07-01 at 20:55 +0000, William Salibrici wrote:
> Anyway, my simple windows udp receiver pipeline [as shown above] > appears to be finally working ok. There’s no need to go any further > on this. Thank you for your insights though – I still learned a lot > through it all! Great, I'm glad that it works for you now :) Thanks for letting me know -- Sebastian Dröge, Centricular Ltd · http://www.centricular.com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel signature.asc (968 bytes) Download Attachment |
Free forum by Nabble | Edit this page |