Hi Ross,
Thank you very much for your attention.
I am facing with some kind of difficulties, because I don't know what is
missing, the data just seems not to be fed to the output of the filter.
That looks fine - but don't forget to enter the event loop, by calling
> env->taskScheduler().doEventLoo
> 2. One of the biggest performance hits in my profiling is memcpy (I use an
> embedded platform, so memcpy gets pricy fast), much of it due to copying
> media buffers. Would you ever consider adding (or consider accepting ;) code
> that allows live555 to work in the calling library's buffers in
Hi
I modify the OpenRtspClient so that
-- Now instead of writing frames to file I collect them in a queue
with incoming presenttaion times
-- Then give the h264 frames to MP4 muxer [ Geraint Davies MP4 mux filter]
-- Finally write muxed data to file...
So I can able to save h264 stream into MP4
Hi,
My RTSP Source's RTCP SR are not reliable...So calculated timestamps
frequently resulting in large negative jumps.
So how can i tell Live555 [ using OpenRtspClient ] NOT to use RTCP
timestamps or simply ignore RTCP info?
Best Wishes
___
live-de
> I am trying to create a ts file from h264 video from a live source.
> Everything looks identical to streams that work from a different muxer but
> when these streams are segmented and served to the Apple
> mediastreamvalidator, it complains with “error: (-12976) unable to parse
> segment as e
This is the exact stream format I get from my encoders
Given nal type 7 = SPS,8 = PPS, 5 = IDR slices, and 1 = Diff frames
I see [7][8][5][1][1][1][1][1] of 6fps streams less than Mp
I see [7][8][5][5][5][1][1][1][1][1] on 6ms multimega-pixel streams.
Some streams to NOT have the SPS and PPS in
Trust me I have done my due diligence on this before asking here. After a whole
week, it appears to be down to the headers in the ts stream created by the
MPEG2TransportStreamMultiplexor. The deliverPAT and the deliverPMT functions.
Aplle is very very picky and vauge :(
From: live-devel-boun.
Hi Ross,
>> On further examination of my encoded frame data, it looks like an I-frame
consists of 3 NAL units, each preceded by 00 00 00 01, the first NALU is 17
bytes long, the second NALU is 9 bytes long, and the 3rd NALU is the rest of
the frame size. Each P-frame is just one NALU.
>> My code
> I am trying to create a ts file from h264 video from a live source.
> Everything looks identical to streams that work from a different muxer but
> when these streams are segmented and served to the Apple
> mediastreamvalidator, it complains with “error: (-12976) unable to parse
> segment as e
I am trying to create a ts file from h264 video from a live source. Everything
looks identical to streams that work from a different muxer but when these
streams are segmented and served to the Apple mediastreamvalidator, it
complains with "error: (-12976) unable to parse segment as either MPEG-
On Dec 21, 2011, at 6:49 AM, David J Myers wrote:
> On further examination of my encoded frame data, it looks like an I-frame
> consists of 3 NAL units, each preceded by 00 00 00 01, the first NALU is 17
> bytes long, the second NALU is 9 bytes long, and the 3rd NALU is the rest of
> the frame
On further examination of my encoded frame data, it looks like an I-frame
consists of 3 NAL units, each preceded by 00 00 00 01, the first NALU is 17
bytes long, the second NALU is 9 bytes long, and the 3rd NALU is the rest of
the frame size. Each P-frame is just one NALU.
My code is now using H26
> There can’t be much wrong with my encoded data because it displays fine in
> VLC (apart from some frames being truncated) when I use H264VideoStreamFramer
> instead of H264VideoStreamDiscreteFramer.
Well, a "nal_unit_type" of 0 is definitely wrong. But if only a few of the
encoded NAL units
>> So I've tried using H264VideoStreamDiscreteFramer and removing the first
4 bytes (which is always 00 00 00 01) from the encoded frame data, but this
fails with the output:-
>> Warning: Invalid 'nal_unit_type': 0.
>OK, that means that your encoder is producing invalid H.264 output.
>> I'm g
> So I’ve tried using H264VideoStreamDiscreteFramer and removing the first 4
> bytes (which is always 00 00 00 01) from the encoded frame data, but this
> fails with the output:-
> Warning: Invalid 'nal_unit_type': 0.
OK, that means that your encoder is producing invalid H.264 output.
> I’m gu
> Basically, I want to have in the same computer a web server (in my example
> apache) and the live555 media server as RTSP server
You CANNOT do this if these two servers use the same port number. I.e., if you
already have an Apache web server running using port 80, then
"live555MediaServer" c
Hi Ross,
>That's your problem. Because your "StreamSource" object is delivering
discrete NAL units (in this case, discrete frames, where each frame is a
single NAL unit) - i.e., delivering one NAL unit at a time - then you should
be using "H264VideoStreamDiscreteFramer".
>Just make sure that you
Thank Ross for your rapid answer
Basically, I want to have in the same computer a web server (in my
example apache) and the live555 media server as RTSP server,therefore I
need apache working as an HTTP proxy for RTSP requests (?)... but in my
tests it did not work. (I don't know if I need to
> We are developping an application using an Mpeg 2 TS (H264/AAC) streaming.
> And we are wondering about the meaning of the boolean parameters of the
> SimpleRTPSink constructor, and the SimpleRTPsource constructor. We are having
> some problems synchronizing audio and video, and demuxing the o
> Yes, I am trying to stream H.264 compressed live images from my camera sensor
> which are 2144x1944 pixels, so just under 5MegaPixels.
I'm not sure what that translates into in terms of "bytes", but (as noted
several times already on this mailing list) you really shouldn't be streaming a
very
Hi,
We are developping an application using an Mpeg 2 TS (H264/AAC) streaming.
And we are wondering about the meaning of the boolean parameters of the
SimpleRTPSink constructor, and the SimpleRTPsource constructor. We are
having some problems synchronizing audio and video, and demuxing the output
Hi Ross
You wrote:
>But in your first message, you talked about "5MP" images. Did you mean "5
MByte images"; "5 Megapixel images"? In any case, what codec is this?
I.e., what kind of data are you trying to stream?
Yes, I am trying to stream H.264 compressed live images from my camera
sensor
In general, I see no reason why RTSP-over-HTTP would not work through a HTTP
proxy.
However, I'm confused by your last statement:
> Is there any other possibility in order to support RTSP over HTTP and a web
> service over 80 port in the same machine?
By this, do you mean a RTSP-over-HTTP clien
Hi,
I am trying to recieve using openRTSP an RTSP stream over HTTP using
Apache as a "proxy" (using mod_proxy and mod_http_proxy).
My Apache configuration is the following:
/
ProxyRequests Off
Order deny,allow
Allow from all
ProxyPass /media/ http://127.0.0.1:8080/
ProxyPassRevers
24 matches
Mail list logo
