Ross Finlayson wrote: > It sounds like you are trying to implement your own (nonstandard) RTP > payload format - therefore I'm not able to help you. However, if you > still wish to proceed down this route, then you will need to (i) > implement your own subclass of "MultiFramedRTPSink" for transmitting > your payload format. And then, because your payload format won't be > understandable by any standard client, you will also need to (ii) > implement your own subclass of "MultiFramedRTPSource" for receiving > your data, and use it to implement your own client. At this point > you're on your own. Good luck. > I tried to. I actually need only to receive nonstandard data, and not trasmitting it, so I implemented my own subclass of "MultiFramedRTPSource" only.
The only problem is: "MultiFramedRTPSource" is created in MediaSubsession::initiate. This means I should create my own subclass of "MediaSubsession" too? Because it will mean creating also my own subclass of "MediaSubSession", and of "MediaSubsessionIterator", as far as I know. Is this the way to go? Or there's another way of using my custom MultiFramedRTPSource subclass without changing all these other classes? Thanks, -- Belloni Cristiano Imavis Srl. www.imavis.com <http://www.imavis.com> [EMAIL PROTECTED] <mailto://[EMAIL PROTECTED]> _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
