... or is the ADTS chunk as simple as writing ADTSAudioRTPSink and
passing that to a PassiveServerMediaSubsession?
No, "ADTS" is a file format (for MPEG-4 audio data), not a codec.
You will use a "MPEG4GenericRTPSink" - just as is done by the
"ADTSAudioFileServerMediaSubsession" class.
Also,
ADTS -- Since the library only includes
ADTSAudioFileServerMediaSubsession, I'm assuming I need to create a
subclass of ServerMediaSubsession capable of reading from our
in-memory frames instead of a file, yes?
Yes.
Moving from Multicast to Unicast: The multicast version's working
with of
hi Ross,
I am doing live streaming from my hardware H.264 encoder. From my encoder side,
i am writing to a socket and passing encoded data from it.
I looked at BasicUDPSource and it data from the socket. When I pass the data
from the BasicUDPSource to my H264RTPVideoSink, i see nothing
played
I need to use certain predefined port numbers for RTP streaming, for
example 60004 for audio substream, 60006 for audio...
Is your streaming multicast or unicast? If it's multicast, you can
easily define and use a single port number. However, if your
streaming is unicast, then you can't do t
I need to use certain predefined port numbers for RTP streaming, for
example 60004 for audio substream, 60006 for audio...
I tried to set response header for "DESCRIBE" to use those numbers, like:
m=video 60004 RTP/AVP 32\r\n vs. m=video 0 RTP/AVP 32\r\n but it
doesn't seem to make any difference
... or is the ADTS chunk as simple as writing ADTSAudioRTPSink and passing that
to a PassiveServerMediaSubsession?
*goes off to find coffee*
-t
On Feb 8, 2010, at 1:44 PM, Tom Pepper wrote:
> Hello again:
>
> We're writing a live encoding application which reads whole frames in-memory
> from
Hello again:
We're writing a live encoding application which reads whole frames in-memory
from an ADTS and H264 encoder and forwards them to Wowza via live.
Two questions:
ADTS -- Since the library only includes ADTSAudioFileServerMediaSubsession, I'm
assuming I need to create a subclass of
thanks, guys. Mainconcept returns 2 full NALs in a single buffer with both the
SPS and PPS encoded, which I just needed to separate, base64encode, put a comma
between, and return. The harder part is figuring out the middle byte to send
for the profile_id header, now. If anyone needs help with
