Re: [Live-devel] : Re: how to add arbitrary data to an MPEG2

2019-08-14 Thread Ross Finlayson


> On Aug 14, 2019, at 1:14 AM, Hallmann, Dietmar  
> wrote:
> 
> Hi Ross, 
>  
> yes of course it should be standardized and not arbitrary. To be more 
> clearly, I mean KLV encoded data as defined in the SMPTE standard ST 336.

I’m not very familiar with how this type of data should be packetized within a 
Transport Stream, but you might be able to do this by subclassing 
“MPEG2TransportStreamMultiplexor”, as we already do to implement 
“MPEG2TransportStreamFromESSource”.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/


___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel


Re: [Live-devel] : Re: how to add arbitrary data to an MPEG2

2019-08-14 Thread Hallmann, Dietmar
Hi Ross,

yes of course it should be standardized and not arbitrary. To be more clearly, 
I mean KLV encoded data as defined in the SMPTE standard ST 336.

Best regards

Dietmar

> On Aug 12, 2019, at 6:05 AM, Hallmann, Dietmar  
> wrote:
>
> I?m working on a project where I capture a video framebuffer, encode it with 
> NVIDIA encoder and stream it as an elementary h264/265 video stream via 
> live555 mpeg2 transport container. It works fine and it?s really fast with 
> negligible latencies.  I use an instance of MPEG2TransportStreamFromESSource 
> and add an elementary video stream by using addNewVideoSource. I saw that 
> this is possible for both video and audio elementary streams.
> Maybe it?s a stupid question and I don?t want to waste your time but is it 
> possible to add arbitrary data, for instance meta data, as a source to the 
> same container

Probably not with the existing code; it assumes that the streams being 
multiplexed into a Transport Stream are audio or video.

If we were to support adding a new type of stream to a Transport Stream, it 
would have to be something that?s been standardized (not some arbitrary, 
non-standard data).

An alternative would be to stream your H.264/H.265 video data as RTP, rather 
than packing it into a Transport Stream.  Then, if your metadata is textual 
(timed text), then you could also stream it as RTP, using our ?T140TextRTPSink? 
class.


Ross Finlayson
Live Networks, Inc.
http://www.live555.com/



The information in this e-mail is confidential. The contents may not be 
disclosed or used by anyone other than the addressee. Access to this e-mail by 
anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and 
delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of 
this e-mail as it has been sent over public networks. If you have any concerns 
over the content of this message or its Accuracy or Integrity, please contact 
Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus 
scanning software but you should take whatever measures you deem to be 
appropriate to ensure that this message and any attachments are virus free.
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel