Note: For AAC the header byte is always 0xaf Here is the basic code to fill in the codec config data.įtRateIndex(AACUtils.sampleRateToIndex(sampleRate)) įtChannelIndex(AACUtils.channelCountToIndex(sampleRate)) ĪACUtils.encodeAACCodecConfig(frame, codecConfig, 0) Note: For AAC the codec config data is generally a two byte packet that describes the stream. Layout of the header byte of data (table goes from least significant bit to most significant bit): It needs to have a special very short header which I think is described in the server-side API docs for the Publisher API: Basic packet format: I assume Wowza already knows how to stream the raw h.264 data using RTP packets after stripping off the RTP header, but do developers have access to those functions? If so, does anyone have some example code for how to add raw h.264 data using Publisher.addVideoData()? I know I can package up the source h.264 data into RTP packets and then have Wowza read them from the RTP port, but that seems like a lot of extra steps that are not needed and would introduce latency, since I have access to the raw h.264 data directly. Does FLVUtils provide functions for doing that? But I’m not sure what to do when trying to read in raw h.264 bytes. That is, I have code for FLV files that can read in the data, create an AMFPacket using FLVUtils.readHeader() and FLVUtils.readChunk(), and then publish it to the stream using Publisher.addVideoData().
My code works fine when reading in an FLV file. I am trying to stream an h.264 encoded video using its raw h.264 byte stream that I read in from a file (not through RTP).
0 kommentar(er)
