These operations are performed by the Processor using specialized Codec plug-ins. The input and output formats of a particular plug-in can be determined through the getSupportedInputFormats and getSupportedOutputFormats methods. The formats of the data streamed by the DataSource created by the session manager are well-defined to facilitate packetization and depacketization of the formatted data. In some cases, if the necessary encoder or decoder is available, you might only need to write a packetizer or depacketizer. Custom packetizers and depacketizers can be combined with custom encoders and decoders, or you can implement independent packetizer and depacketizer plug-ins.
Data flow with a custom depacketizer plug-in.
RTP Data Handling 1 Data is transferred between the session manager and a Player or Processor using the Buffer object. Therefore, all DataSources created by the Processor with an RTP-specific format are buffer DataSources . Similarly, all DataSources created by the session manager and handed over to the Manager for Player creation are buffer DataSources . For example, gsm RTP encapsulated packets have the encoding set to AudioFormat. Payload-specific headers are not part of the RTPHeader .