> -Original Message-
> From: live-devel-boun...@ns.live555.com [mailto:live-devel-
> boun...@ns.live555.com] On Behalf Of Christophe Lemoine
> Sent: mardi 2 novembre 2010 10:36
> To: live-de...@ns.live555.com
> Subject: [Live-devel] H264 streaming with trick play
>
> Hi,
>
> I'm looking
The SPS and PPS showed up on the network once, per wireshark, so
they did get sent out once at the beginning of the multicasting. So
the questions, does that mean all the clients join later will not
see SPS or/and PPS at all? How should that work? What do I need to
do? Through SDP?
Yes, in th
!
--- On Wed, 2/25/09, gather bzbz wrote:
> From: gather bzbz
> Subject: Re: [Live-devel] H264 streaming problem
> To: "LIVE555 Streaming Media - development & use"
> Date: Wednesday, February 25, 2009, 10:25 PM
> Right after I capture the buffer from the hardware
SPS and PPS. So
who dropped them?
--- On Wed, 2/25/09, gather bzbz wrote:
> From: gather bzbz
> Subject: Re: [Live-devel] H264 streaming problem
> To: live-de...@ns.live555.com
> Date: Wednesday, February 25, 2009, 2:27 PM
>
> The problem is that special headers called SPS a
The problem is that special headers called SPS and PPS (sequence
parameter set and picture parameter set) are not included in the file.
Those headers may be carried in-band (which is probably not your case)
or in the SDP.
My guess is that your source sent them in the SDP and not in-band (in
th
Are you sure you correctly sent the SPS/PPS nals ? Post the .264 file
if you're not sure, I might be able to take a look and help.
Etienne
On 24 Feb 2009, at 11:55, gather bzbz wrote:
I rename the file hellovideo-H264-2 to hello.264, "file hello.264"
gives "hello.264: JVT NAL sequence", m
live555.com
> [mailto:live-devel-boun...@ns.live555.com] On Behalf Of gather bzbz
> Sent: Tuesday, February 24, 2009 12:56 PM
> To: live-de...@ns.live555.com
> Subject: Re: [Live-devel] H264 streaming problem
>
>
> I rename the file hellovideo-H264-2 to hello.264, "file
&
I rename the file hellovideo-H264-2 to hello.264, "file hello.264" gives
"hello.264: JVT NAL sequence", mplayer gives
Playing hello.264.
H264-ES file format detected.
Video: Cannot read properties.
No stream found.
at least, mplayer can play hellovideo-H264-2 with color bar, but it can not
pl
Try rename it to have the extension .264. ("hellovideo-H264-2.264")
In that way the vlc player will know to treat it as annex-B H264 stream.
Regards,
Amit Yedidia
Elbit System Ltd.
Email: amit.yedi...@elbitsystems.com
Tel: 972-4-8318905
--
: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] H264 streaming
Does openRTSP support H.264 streaming
Yes, our RTSP client code (including the "openRTSP" application) can receive
standard H.264 RTSP/RTP streams.
--
Ross Finlayson
Live Networks, Inc.
http://w
Does openRTSP support H.264 streaming
Yes, our RTSP client code (including the "openRTSP" application) can
receive standard H.264 RTSP/RTP streams.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/___
live-devel mailing list
live-devel@l
Does openRTSP support H.264 streaming, I am using VLC latest version as
streaming server.
Regards
Aditya
From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Aditya Vikram
Sent: Monday, January 19, 2009 1:04 PM
To: LIVE
I need to stream H264 video from linux device to PC. I write both
the sender and receiver part but would like to comply to the
standard way of streaming it, so:
How should I packetize the video? Should it be NAL packets or should
I put it into transport stream?
For streaming, it is generally b
13 matches
Mail list logo
