Re: [FFmpeg-devel] Patch which requires a new library

2024-03-07 Thread Sergio Garcia Murillo
On Thu, Mar 7, 2024 at 7:02 PM Rémi Denis-Courmont wrote: > Le torstaina 7. maaliskuuta 2024, 19.30.46 EET Sergio Garcia Murillo a > écrit : > > > The point is we don't want to use the external lib. > > > > For what? This is aws lib implementing the aws s3 signat

Re: [FFmpeg-devel] Patch which requires a new library

2024-03-07 Thread Sergio Garcia Murillo
El jue, 7 mar 2024, 18:21, Kieran Kunhya escribió: > On Thu, 7 Mar 2024, 17:16 Sergio Garcia Murillo, < > sergio.garcia.muri...@gmail.com> wrote: > > > El jue, 7 mar 2024, 16:30, Kieran Kunhya escribió: > > > > > On Thu, 7 Mar 2024 at 15:07, Sergio Garci

Re: [FFmpeg-devel] Patch which requires a new library

2024-03-07 Thread Sergio Garcia Murillo
El jue, 7 mar 2024, 16:30, Kieran Kunhya escribió: > On Thu, 7 Mar 2024 at 15:07, Sergio Garcia Murillo < > sergio.garcia.muri...@gmail.com> wrote: > > > > > Could anyone give me any pointers on what is the best way of doing this? > > > > You should use a

[FFmpeg-devel] Patch which requires a new library

2024-03-07 Thread Sergio Garcia Murillo
Hi all! I would like to contribute a patch that adds sig v4 authentication ( https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html) to the http module. This would allow for example to play/store an MPEG DASH content stored on an S3 Bucket which requires authenticatio

Re: [FFmpeg-devel] WHIP - Webrtc Http Ingest Protocol

2020-09-16 Thread Sergio Garcia Murillo
On 11/09/2020 22:51, Kieran Kunhya wrote: Because when you have a WebRTC server/service, you need WebRTC ingest. You may be surprised by the amount of mixed RTC/streaming services that are being implemented as we speak since COVID. Why is that the case? Mainly because if you already have WebR

Re: [FFmpeg-devel] WHIP - Webrtc Http Ingest Protocol

2020-09-11 Thread Sergio Garcia Murillo
On 11/09/2020 17:29, Kieran Kunhya wrote: On Fri, 11 Sep 2020 at 11:31, Sergio Garcia Murillo < sergio.garcia.muri...@gmail.com> wrote: Hi all! WebRTC can be an intimidating monster, and we all are aware of that. Also, the fact that every webrtc media server/service has their own

Re: [FFmpeg-devel] WHIP - Webrtc Http Ingest Protocol

2020-09-11 Thread Sergio Garcia Murillo
El vie., 11 sept. 2020 15:23, Lynne escribió: > On 11/09/2020 14:16, Sergio Garcia Murillo wrote: > > On 11/09/2020 13:49, Lynne wrote: > > > > WebRTC uses rtp muxing to send all data in the same udp port, and lip > > sync based on rtcp (also muxed on same udp port).

Re: [FFmpeg-devel] WHIP - Webrtc Http Ingest Protocol

2020-09-11 Thread Sergio Garcia Murillo
On 11/09/2020 13:49, Lynne wrote: On 11/09/2020 12:31, Sergio Garcia Murillo wrote: Hi all! WebRTC can be an intimidating monster, and we all are aware of that. Also, the fact that every webrtc media server/service has their own custom protocol has not helped to increase its adoption in the

[FFmpeg-devel] WHIP - Webrtc Http Ingest Protocol

2020-09-11 Thread Sergio Garcia Murillo
Hi all! WebRTC can be an intimidating monster, and we all are aware of that. Also, the fact that every webrtc media server/service has their own custom protocol has not helped to increase its adoption in the streaming world, with still relies heavily on other protocols like RTMP, SRTP or even