From: live-devel-boun...@ns.live555.com
[mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross Finlayson
Sent: mardi 29 novembre 2011 02:07
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] MPEG-2 Program Map Table PID
My opinion would be to use 0x30, as it is
> My opinion would be to use 0x30, as it is legal for both ATSC and DVB, and
> seems to be valid for
> any transport stream.
Ok, thanks. I've just installed a new version (2011.11.29) of the "LIVE555
Streaming Media" code that changes this constant.
Ross Finlayson
Live Networks, Inc.
http://w
Hi Ross,
Thanks for your prompt response.
>>That's odd. I've seen several Transport Stream files that use 0x10 as the
"Program_map_PID", and Table 2-3 of ISO/IEC 13818-1 says that PIDs in the
range 0x10 through 0x1FFE "May be assigned as network_PID, Program-map_PID,
elementary_PID, or for other
> I am using the LIVE555 libraries to wrap H.264 video data inside an MPEG-2
> transport stream. Everything is working great except for one problem: The
> MPEG2TransportStreamMultiplexor class is currently using a hard-coded Program
> Map Table PID of 0x10 (OUR_PROGRAM_MAP_PID), which is not al
Hi Ross,
I am using the LIVE555 libraries to wrap H.264 video data inside an MPEG-2
transport stream. Everything is working great except for one problem: The
MPEG2TransportStreamMultiplexor class is currently using a hard-coded
Program Map Table PID of 0x10 (OUR_PROGRAM_MAP_PID), which is not
