somesrc ! asfmux ! rtpasfpay ! udpsink
because the ASF headers need to be updated after the stream ends and those values are needed by rtpasfpay.
Additionally, I can't get an ASF from a file and feed it to rtpasfpay because the buffers would be unaligned with the ASF objects and packets, requiring rtpasfpay to parse the data before doing anything related to RTP. I'd say we need a parser.
The idea is to do all the parsing at the parser (obvious) and only some checks of conformance at the rtp payloader. As I had already started developing the payloader, I took it as farther as I could (without using a parser) and its current state is now at the repository. It is still unfinished (read: doesn't work).
The parser
Now I'm starting to develop the asfparse element. ASF files have 3 main parts: first there are headers, then the data (where the packets are) and lastly a series of indexes objects. The parser would, sequentially:
- Group all the headers into a single buffer and push it
- Push the "Data object" header (everything but the packets)
- Put each packet into a separate buffer and push them
- Put each of the indexes object into a separate buffer and push them
- EOS
The parser should work both in pull or push mode, I'll start with push mode.
No comments:
Post a Comment