|

»

consume and publish a remote stream

View: New views

4 Messages — Rating Filter: Alert me

	consume and publish a remote stream by Scott Sayles-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message I'm attempting to subscribe to an existing stream (served by an FMS server [rtmp/live h.264]) and re-publish/proxy it into Red5 with RTMPClient. I've seen StreamingProxy but this works from the perspective of the source server which I don't have access to. After digging around for a few days now, I've decided on the following approach: 1. create a RTMPClient subscriber - connected to the remote FMS server 2. play the stream and grab RTMPEvents 3. create another RTMPClient to publish - connected to the localhost Red5 server 4. create a new stream to publish to Red5, then feed in the events as RTMPMessages to RTMPClient.publishStreamData() I'm able to connect with the demo publisher flash client to the source fms server and playback the video. I'm hoping that I can simply proxy the stream and playback via the red5 server. I'm entirely new to Red5/Flash/etc. and I'm wondering if this seems like a plausible approach. Perhaps there's some other approach I should take? Has anyone done anything like this? I'd appreciate any suggestions. Thanks, Scott _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org
	Re: consume and publish a remote stream by Andy Shaules :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Some parts of this message have been removed. Learn more about Nabble's security policy. The easiest way is to write some additional handlers in the fcs application. But if you do not own the fcd servers, then are you rebroadcasting somebody else's stream? If you do own the units, then you can write action script for the fcs and then red5 will simply handle the stream as is. ----- Original Message ----- From: scott.sayles@... To: red5@... Sent: Thursday, July 09, 2009 9:58 AM Subject: [Red5] consume and publish a remote stream I'm attempting to subscribe to an existing stream (served by an FMS server [rtmp/live h.264]) and re-publish/proxy it into Red5 with RTMPClient. I've seen StreamingProxy but this works from the perspective of the source server which I don't have access to. After digging around for a few days now, I've decided on the following approach: 1. create a RTMPClient subscriber - connected to the remote FMS server 2. play the stream and grab RTMPEvents 3. create another RTMPClient to publish - connected to the localhost Red5 server 4. create a new stream to publish to Red5, then feed in the events as RTMPMessages to RTMPClient.publishStreamData() I'm able to connect with the demo publisher flash client to the source fms server and playback the video. I'm hoping that I can simply proxy the stream and playback via the red5 server. I'm entirely new to Red5/Flash/etc. and I'm wondering if this seems like a plausible approach. Perhaps there's some other approach I should take? Has anyone done anything like this? I'd appreciate any suggestions. Thanks, Scott _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org
	Re: consume and publish a remote stream by Scott Sayles-2 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message We actually do own the fmis server (what I think you're calling fcs), but our idea is that we build a flexible solution that can subscribe to arbitrary streams from wherever. We then want to do some transcoding of that stream via xuggler (add overlays, etc.). We could publish from our fmis server, but it's not the solution we're currently investigating. Scott On Thu, Jul 9, 2009 at 1:28 PM, Andy Shaules <bowljoman@...> wrote: The easiest way is to write some additional handlers in the fcs application. But if you do not own the fcd servers, then are you rebroadcasting somebody else's stream? If you do own the units, then you can write action script for the fcs and then red5 will simply handle the stream as is. ----- Original Message ----- From: scott.sayles@... To: red5@... Sent: Thursday, July 09, 2009 9:58 AM Subject: [Red5] consume and publish a remote stream I'm attempting to subscribe to an existing stream (served by an FMS server [rtmp/live h.264]) and re-publish/proxy it into Red5 with RTMPClient. I've seen StreamingProxy but this works from the perspective of the source server which I don't have access to. After digging around for a few days now, I've decided on the following approach: 1. create a RTMPClient subscriber - connected to the remote FMS server 2. play the stream and grab RTMPEvents 3. create another RTMPClient to publish - connected to the localhost Red5 server 4. create a new stream to publish to Red5, then feed in the events as RTMPMessages to RTMPClient.publishStreamData() I'm able to connect with the demo publisher flash client to the source fms server and playback the video. I'm hoping that I can simply proxy the stream and playback via the red5 server. I'm entirely new to Red5/Flash/etc. and I'm wondering if this seems like a plausible approach. Perhaps there's some other approach I should take? Has anyone done anything like this? I'd appreciate any suggestions. Thanks, Scott _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org
	Re: consume and publish a remote stream by Dave Feltenberger :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Bump. I also have an interest in this. Does anybody here have a working example of code that plays and/or publishes streams from a remote client? I'm able to use Xuggler (and their Red5 adapter) inside a Red5 application to publish a stream to Red5, but still haven't been able to figure out a way to publish a stream from a remote Java client. Anybody have any suggestions? Thanks. Dave On Thu, Jul 9, 2009 at 1:53 PM, Scott Sayles <scott.sayles@...> wrote: We actually do own the fmis server (what I think you're calling fcs), but our idea is that we build a flexible solution that can subscribe to arbitrary streams from wherever. We then want to do some transcoding of that stream via xuggler (add overlays, etc.). We could publish from our fmis server, but it's not the solution we're currently investigating. Scott On Thu, Jul 9, 2009 at 1:28 PM, Andy Shaules <bowljoman@...> wrote: The easiest way is to write some additional handlers in the fcs application. But if you do not own the fcd servers, then are you rebroadcasting somebody else's stream? If you do own the units, then you can write action script for the fcs and then red5 will simply handle the stream as is. ----- Original Message ----- From: scott.sayles@... To: red5@... Sent: Thursday, July 09, 2009 9:58 AM Subject: [Red5] consume and publish a remote stream I'm attempting to subscribe to an existing stream (served by an FMS server [rtmp/live h.264]) and re-publish/proxy it into Red5 with RTMPClient. I've seen StreamingProxy but this works from the perspective of the source server which I don't have access to. After digging around for a few days now, I've decided on the following approach: 1. create a RTMPClient subscriber - connected to the remote FMS server 2. play the stream and grab RTMPEvents 3. create another RTMPClient to publish - connected to the localhost Red5 server 4. create a new stream to publish to Red5, then feed in the events as RTMPMessages to RTMPClient.publishStreamData() I'm able to connect with the demo publisher flash client to the source fms server and playback the video. I'm hoping that I can simply proxy the stream and playback via the red5 server. I'm entirely new to Red5/Flash/etc. and I'm wondering if this seems like a plausible approach. Perhaps there's some other approach I should take? Has anyone done anything like this? I'd appreciate any suggestions. Thanks, Scott _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list Red5@... http://osflash.org/mailman/listinfo/red5_osflash.org