[Live-devel] [External] Re: Encoded data to live555 library for live streaming

Trivedi, Rushina RUSHINA.TRIVEDI at Honeywell.com
Tue Oct 22 21:12:18 PDT 2024


Hi Ross,

Thanks for your suggestion. We don't know the buffer pointer (and buffer size) at the time that we create  “ByteStreamMemoryBufferSource” object. So, we need to define and implement our own “FramedSource” subclass. We will work on it and meanwhile if you can also help us for structure of the FramedSource” subclass, It would be helpful for us.

Please let us know on which separate email ID we can contact you or you drop us mail on this id, we can reply to you.

Thanks & Regards,
Rushina.

-----Original Message-----
From: live-devel <live-devel-bounces at us.live555.com> On Behalf Of Ross Finlayson
Sent: Tuesday, October 22, 2024 9:14 PM
To: LIVE555 Streaming Media - development & use <live-devel at us.live555.com>
Subject: Re: [Live-devel] [External] Re: Encoded data to live555 library for live streaming



> On Oct 22, 2024, at 7:54 PM, Trivedi, Rushina via live-devel <live-devel at us.live555.com> wrote:
>
> But when creating subsession for live streaming , I don't have encoded data buffer and its length. So I just pass env and reuseFirstSource as below.
>
> sms->addSubsession(H264LiveServerMediaSubsession::createNew(env,true));
>
> So, how to pass my encoded data, its length and presentation time with session handle to ByteStreamMemoryBufferSource whenever I get data from one of our thread during runtime?

If you know the buffer pointer (and buffer size) at the time that you create your “ByteStreamMemoryBufferSource” object (i.e., in your reimplementation of the “createNewStreamSource” virtual function), then you can pass them (as parameters to “ByteStreamMemoryBufferSource::createNew()”) then.

Otherwise you will need to define and implement your own “FramedSource” subclass (perhaps using the “ByteStreamMemoryBufferSource” code as a model) that does what you want.

(And re. “threads”: remember that a LIVE555-based application - such as yours - must run as a single thread of control, with “triggerEvent()” being the only LIVE555 function that can be called by a separate (non-LIVE555 thread); see http://live555.com/liveMedia/faq.html#threads


> For any further help, do you provide any paid service?

Possibly.  Please contact me via a separate email (i.e., outside this mailing list) about this.


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


_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel



More information about the live-devel mailing list