whiteblue3/httplivestreaming

iOS / Mac OSX H.264 / AAC Hardware Encoding and Streaming over RTP / RTSP using Video Tool Box

README

This project is stop the developing now. Will restart later.

This project is streaming H.264/AAC using iOS Video Tool Box to encode and send packet over RTP / RTSP

This project is association with Wowza Media Server 4.3 over.

Known Issue

• H264 Hardware Encoding working on iOS. Mac OS X is not working perfectly.

• for Mac OS X, AVFoundation is using hardware encoding. I using it.

• AAC Hardware Encoding is not working on iOS (Software Encoding). Mac OS X only (AVFoundation)

• H264 Hardware Decoder is working perfectly.

• H264 MaxSlice option is not working. I use packetization mode 0 (Single NAL)

• H264 kVTCompressionPropertyKey_ExpectedFrameRate is not working on Mac OS X. (15 fps static only)

• H264 bitrate is only working iOS. not Mac OS X.

• RTSP Client is only working for stream publisher.

TODO

• MPEG4 container format support

• MPEG2-TS container format support

LICENSE

This project is under GPLv2

httplivestreaming's Issues

TESTING WITH A LOCAL SERVER ON MAC AND IPHONE AS STREAM GENERATOR

@whiteblue3 Thanks for the great framework. Could you please let me know how can we create rtp server on Mac Vlc player and run your sample on iPhone. And can we watch this stream on Mac vlc player which is on same network. Could you please let me know is this possible.

How to decode?

How to use H264HWDecoder for decoding?

There is an error in decoding directly using the packet of gotH264EncodedData.

Decompressed error: Error Domain=NSOSStatusErrorDomain Code=-12705 "(null)"
Decompressed error: Error Domain=NSOSStatusErrorDomain Code=-12705 "(null)"
Decompressed error: Error Domain=NSOSStatusErrorDomain Code=-12705 "(null)"

bug aac 6s

貌似在6s 手机采集不到音频数据

Unsupported RTP version packet received0/0

I've tried to connect to the streaming with ffplay rtp://127.0.0.1:10001 ffplay rtp://127.0.0.1:10000. it says Unsupported RTP version packet received0/0`

I compared the data with standard rtp data I've found the data begins with 01 while a standard packet begins with 8

Do you implement a standard RTP protocol ?

One question: how about your TODO works?

Hi, very like your great work and how about your todo work like MPEG2-TS container format support?

Hello, your framework is very good, but I would like to ask a few questions, can you?

Hello, your framework is very good, but I would like to ask a few questions, can you?