Hi Ross,
On Wed, 24 Apr 2024 at 19:26, Ross Finlayson wrote:
>
>
> > On Apr 24, 2024, at 1:46 PM, Flavio Alves <
> flavio.al...@vitalintelligencedata.com> wrote:
> >
> > My first implementation uses the approach you mentioned. I implemented
> it using x264 and it worked fine.
> >
> > But my requ
> On Apr 24, 2024, at 1:46 PM, Flavio Alves
> wrote:
>
> My first implementation uses the approach you mentioned. I implemented it
> using x264 and it worked fine.
>
> But my requirement is to use the Nvidia Jetson Nano hardware encoder. Nvidia
> provides an API to handle the encoder. This
Hi Ross,
Thank you for your response.
Indeed ... I'm struggling with the latency challenge.
My first implementation uses the approach you mentioned. I implemented it
using x264 and it worked fine.
But my requirement is to use the Nvidia Jetson Nano hardware encoder.
Nvidia provides an API to ha
> On Apr 18, 2024, at 1:07 PM, Flavio Alves
> wrote:
>
> Hello,
>
> I'm working on a live streaming service using Live55 using an Nvidia Jetson
> Nano board.
>
> I'm capturing the frames from an USB webcam and I am encoding using Nvidia's
> hardware encoder. Then Live555 is responsible for
I believe I have found a solution.
I implemented a strategy where my circular buffer keeps waiting until a new
frame arrives, similar to a blocking socket read operation. Then everything
goes well.
Then I do not need to worry about the variables anymore, just like expected
from a DeviceSource.
B
