Re: [Live-devel] Relaying a unicast stream.

2017-10-30 Thread Ross Finlayson
> On Oct 30, 2017, at 2:35 PM, Mark Woodard wrote: > > OK. So testRelay is a good starting basis. Well, that depends on how the source stream is generated. If the source stream comes from a RTSP server - i.e., is accessed using a “rtsp://“ URL - then you wouldn’t use “testRelay” at all. Ins

[Live-devel] Relaying a unicast stream.

2017-10-30 Thread Mark Woodard
OK. So testRelay is a good starting basis. The only difference in my case is that the source stream is unicast, not multicast. Do I need to modify anything about the BasicUDPSink (or anything else) to accommodate a unicast source? ___ Mark Woodard M

Re: [Live-devel] Relaying a unicast stream.

2017-10-30 Thread Ross Finlayson
> On Oct 30, 2017, at 1:48 PM, Mark Woodard wrote: > > OK, Ross, let me rephrase the question. > > Does the testRelay example accept RTP packets from a source and pass them on > unchanged to the destination? The “testRelay” demo application - as written - receives UDP packets (from a multic

[Live-devel] Relaying a unicast stream.

2017-10-30 Thread Mark Woodard
OK, Ross, let me rephrase the question. Does the testRelay example accept RTP packets from a source and pass them on unchanged to the destination? If the packets are not unchanged, what is changed about them? ___ Mark Woodard Mutualink, Inc. 313 S J

Re: [Live-devel] Relaying a unicast stream.

2017-10-30 Thread Ross Finlayson
> On Oct 30, 2017, at 11:14 AM, Mark Woodard wrote: > > My source is the Milestone ONVIF Bridge, which I believe was built using > Live555 libraries. It deals with RTP over UDP. I have no idea whether or not the "Milestone ONVIF Bridge” was built using the LIVE555 libraries. But if it’s a R

[Live-devel] Relaying a unicast stream.

2017-10-30 Thread Mark Woodard
My source is the Milestone ONVIF Bridge, which I believe was built using Live555 libraries. It deals with RTP over UDP. My destination is a Mutualink Edge Server. It also expects RTSP packets. ___ Mark Woodard Mutualink, Inc. 313 S Jupiter Allen, TX

Re: [Live-devel] Relaying a unicast stream.

2017-10-30 Thread Ross Finlayson
> Anyway, once I created the socket on the heap, my program worked with no > errors. However, the code at the destination address does not recognize > anything playable. I was under the impression that the testRelay sample was > relaying the data as RTP/UDP. I'm pretty sure that's what the desti

[Live-devel] Relaying a unicast stream.

2017-10-30 Thread Mark Woodard
Thanks, Ross. Yes, my class OurRelaySink is derived from BasicUDPSink, and it's only method is CreateNew (just to hide the mess of creating the socket). My problem was this: In the testRelay sample, the output Groupsock was created on the stack, so I created mine on the stack. Of course, that only

Re: [Live-devel] Relaying a unicast stream.

2017-10-28 Thread Ross Finlayson
> I have adapted the testRTSPClient sample to receive a stream from my UDP > source. Now I need to relay the data to another UDP address. Is your ‘UDP source’ a RTP/UDP source, or a raw-UDP source. If it’s the former, then why not also relay the data as RTP/UDP packets (and why not use the “LI

[Live-devel] Relaying a unicast stream.

2017-10-27 Thread Mark Woodard
I have adapted the testRTSPClient sample to receive a stream from my UDP source. Now I need to relay the data to another UDP address. So I tried replacing the "DummySink" in testRTSPClient with the BasicUDPSink used in testRelay. It was almost a one-for-one replacement. But it doesn't work: it cra