When Kodi tries to play a specific live stream it returns error 403 after
some time due to the update of a cookie.
I've done a patch to ffmpeg and version 2.8.2 works like a charm with the
command line like: ffmpeg -i "fullurl.m3u8" -c copy "teste.ts"
But with the new Kodi 12.0 beta that has the 2
Hello, I was looking into AMD VCE encoder and I did realize that there is
only a Windows SDK. Should I try to add a Windows only feature? And it
won't be able to compile on Linux. What do you guys think about it?
___
ffmpeg-devel mailing list
ffmpeg-devel
Em sex, 30 de out de 2015 às 07:44, Michael Niedermayer
escreveu:
> On Tue, Oct 27, 2015 at 11:28:32AM +0000, Lucas Andrade wrote:
> > Here is the patch to backport it to release/2.8. To be fixed on 2.8.2.
> > Anything else I should do?
> >
> > ps. Sorry, that&#x
Em ter, 27 de out de 2015 às 09:28, Lucas Andrade
escreveu:
> Here is the patch to backport it to release/2.8. To be fixed on 2.8.2.
> Anything else I should do?
>
> ps. Sorry, that's my first time on opensource project, I'm a little
> confused that I needed to add
Here is the patch to backport it to release/2.8. To be fixed on 2.8.2.
Anything else I should do?
ps. Sorry, that's my first time on opensource project, I'm a little
confused that I needed to add it to the release branch.
b3f3eab029eb429660fc1651a33dafe097cbac0e.patch
Description: Binary data
__
Can this patch be added to 2.9-dev? I think it should be released on 2.8.1
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Ok, I know I did it wrong with the PR. I've used the PR to create the
patch. Sorry for trying to help.
Anyway, here it is the all-in-one patch.
Update Cookies response with Setcookie.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-de
Ok, I'll try to merge all those patches at a single one.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Here it is. Also sent as PR on github.
Update Cookies Setcookie response.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
I did test with a similar command posted on the tracker, cookies were
updated correctly.
Em sex, 25 de set de 2015 às 10:26, wm4 escreveu:
> On Fri, 25 Sep 2015 02:00:29 +
> Lucas Andrade wrote:
>
> > diff --git a/libavformat/hls.c b/libavformat/hls.c
> > index ad
Here it goes.
Update Cookies on Setcookie response.diff
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
I've tested and this works. Cookies is being set correctly. As you can see,
I've removed the opts2 as it isn't needed anymore. I've added the cookie
update to open_url (setting the HLSContext->cookies and the opts (maybe
used on ciphered stream).
diff --git a/libavformat/hls.c b/libavformat/hls.c
Sorry about top posting.. That's the gmail default. Anyway, I've double
checked and think you're right. I'll add that to open_url, but I need to
set the right HLSContext cookies. Right now it isn't passed as parameter to
open_url, that way, I'll have to pass it ahead.
About the opts, it isn't trash
You're right, I should at least check if ret == 0. I'll update the patch
and check if it works.
Em ter, 22 de set de 2015 às 08:09, Lucas Andrade
escreveu:
> I think the other code paths already sets the cookie.
>
> Em Ter, 22 de set de 2015 04:41, wm4 escreveu:
>
>&g
I think the other code paths already sets the cookie.
Em Ter, 22 de set de 2015 04:41, wm4 escreveu:
> On Tue, 22 Sep 2015 04:37:48 +
> Lucas Andrade wrote:
>
> > This fixes the https://trac.ffmpeg.org/ticket/4808, as it sets the
> cookie
> > on playlist respon
This fixes the https://trac.ffmpeg.org/ticket/4808, as it sets the cookie
on playlist response with setcookie header.
Update Cookies on Setcookie playlist response
---
libavformat/hls.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavformat/hls.c b/libavformat/hls.c
index 82dd744..e5c8
I'm trying to run a HLS Live Stream on Kodi and I'm getting an error 403
after 5 minutes. Checking the wireshark capture I did realize that the
ffmpeg requests aren't changing a cookie that is set on every response.
Do you guys confirm that is a FFMpeg issue?
GET
/dvr/m/off24ha/master-playlist.m3
17 matches
Mail list logo
