On 22.01.2016 09:55, wm4 wrote:
> In any case, what was going on with hw decoding and frame threading
> seemed pretty insane.
Claiming that things 'seem pretty insane' is a lame argument. One can
say that about a lot of things that people expect to work.
> So even if this is a "regression",
It i
On Fri, 22 Jan 2016 00:14:15 +0100
Andreas Cadhalpun wrote:
> On 21.01.2016 23:56, Hendrik Leppkes wrote:
> > On Thu, Jan 21, 2016 at 8:36 PM, Andreas Cadhalpun
> > wrote:
> >> On 21.01.2016 02:10, Hendrik Leppkes wrote:
> >>> Looks like they added extensive locking around everything to prev
On 21.01.2016 23:56, Hendrik Leppkes wrote:
> On Thu, Jan 21, 2016 at 8:36 PM, Andreas Cadhalpun
> wrote:
>> On 21.01.2016 02:10, Hendrik Leppkes wrote:
>>> Looks like they added extensive locking around everything to prevent
>>> this, which is not something that should be required.
[...]
>>> No,
On Thu, Jan 21, 2016 at 8:36 PM, Andreas Cadhalpun
wrote:
> On 21.01.2016 02:10, Hendrik Leppkes wrote:
>> On Thu, Jan 21, 2016 at 1:14 AM, Andreas Cadhalpun
>>> I'm still not sure of the scope that this problem has.
>>>
>>> If image corruption always happens with MT+HWAccel, why didn't VLC
>>> ch
On 21.01.2016 02:10, Hendrik Leppkes wrote:
> On Thu, Jan 21, 2016 at 1:14 AM, Andreas Cadhalpun
>> I'm still not sure of the scope that this problem has.
>>
>> If image corruption always happens with MT+HWAccel, why didn't VLC
>> change this long ago due to users complaining about that?
>
> I don
On Thu, Jan 21, 2016 at 1:14 AM, Andreas Cadhalpun
wrote:
> On 20.01.2016 10:22, Hendrik Leppkes wrote:
>> On Tue, Jan 19, 2016 at 11:54 PM, Andreas Cadhalpun
>>> Can the crashes be reproduced with VLC?
>>> If so, are they reported in the VLC bug tracker?
>>
>> Who knows, I didn't test every singl
On 20.01.2016 10:22, Hendrik Leppkes wrote:
> On Tue, Jan 19, 2016 at 11:54 PM, Andreas Cadhalpun
>> Can the crashes be reproduced with VLC?
>> If so, are they reported in the VLC bug tracker?
>
> Who knows, I didn't test every single player that uses avcodec.
> The image corruption on Intel GPUs
On 20.01.2016 10:11, wm4 wrote:
> On Tue, 19 Jan 2016 23:54:48 +0100
> Andreas Cadhalpun wrote:
>> On 19.01.2016 21:46, wm4 wrote:
>>> It was discussed to death on #libav-devel too.
>>
>> And the conclusion was to allow hwaccel with frame threads?
>
> From what I remember, the VLC developer in
Hendrik Leppkes wrote:
On Wed, Jan 20, 2016 at 12:13 PM, Andy Furniss wrote:
wm4 wrote:
On Wed, 20 Jan 2016 09:59:12 + Andy Furniss
wrote:
wm4 wrote:
On Wed, 20 Jan 2016 00:42:18 + Andy Furniss
wrote:
Hendrik Leppkes wrote:
I do not agree that it should be a warning. As outl
On Wed, Jan 20, 2016 at 12:13 PM, Andy Furniss wrote:
> wm4 wrote:
>>
>> On Wed, 20 Jan 2016 09:59:12 + Andy Furniss
>> wrote:
>>
>>> wm4 wrote:
On Wed, 20 Jan 2016 00:42:18 + Andy Furniss
wrote:
> Hendrik Leppkes wrote:
>
I do not agree that it shoul
wm4 wrote:
On Wed, 20 Jan 2016 09:59:12 + Andy Furniss
wrote:
wm4 wrote:
On Wed, 20 Jan 2016 00:42:18 + Andy Furniss
wrote:
Hendrik Leppkes wrote:
I do not agree that it should be a warning. As outlined
in the commit message and this thread, there are serious
flaws with frame thr
On Wed, 20 Jan 2016 09:59:12 +
Andy Furniss wrote:
> wm4 wrote:
> > On Wed, 20 Jan 2016 00:42:18 + Andy Furniss
> > wrote:
> >
> >> Hendrik Leppkes wrote:
> >>
> > I do not agree that it should be a warning. As outlined in
> > the commit message and this thread, there are ser
wm4 wrote:
On Wed, 20 Jan 2016 00:42:18 + Andy Furniss
wrote:
Hendrik Leppkes wrote:
I do not agree that it should be a warning. As outlined in
the commit message and this thread, there are serious flaws
with frame threading and hwaccel.
I'm fine with it being an error, but since it is
On Tue, Jan 19, 2016 at 11:54 PM, Andreas Cadhalpun
wrote:
> On 19.01.2016 21:46, wm4 wrote:
>> On Tue, 19 Jan 2016 21:31:19 +0100
>> Hendrik Leppkes wrote:
>>> On Tue, Jan 19, 2016 at 9:27 PM, Andreas Cadhalpun
>>> wrote:
On 19.01.2016 21:22, Hendrik Leppkes wrote:
> On Tue, Jan 19, 20
On Tue, 19 Jan 2016 23:54:48 +0100
Andreas Cadhalpun wrote:
> On 19.01.2016 21:46, wm4 wrote:
> > On Tue, 19 Jan 2016 21:31:19 +0100
> > Hendrik Leppkes wrote:
> >> On Tue, Jan 19, 2016 at 9:27 PM, Andreas Cadhalpun
> >> wrote:
> >>> On 19.01.2016 21:22, Hendrik Leppkes wrote:
> On
On Wed, 20 Jan 2016 00:42:18 +
Andy Furniss wrote:
> Hendrik Leppkes wrote:
>
> >>> I do not agree that it should be a warning. As outlined in the
> >>> commit message and this thread, there are serious flaws with
> >>> frame threading and hwaccel.
> >>
> >> I'm fine with it being an error
Hendrik Leppkes wrote:
I do not agree that it should be a warning. As outlined in the
commit message and this thread, there are serious flaws with
frame threading and hwaccel.
I'm fine with it being an error, but since it is an API change, it
should follow the usual deprecation period to allow
Hi Ronald,
On 19.01.2016 21:53, Ronald S. Bultje wrote:
> Crashes are never good and should be fixed immediately.
>
> What exact issue is left after the crash is fixed, and why?
The issue is that VLC from git master doesn't compile with FFmpeg from git
master,
unless all hardware acceleration o
On 19.01.2016 21:46, wm4 wrote:
> On Tue, 19 Jan 2016 21:31:19 +0100
> Hendrik Leppkes wrote:
>> On Tue, Jan 19, 2016 at 9:27 PM, Andreas Cadhalpun
>> wrote:
>>> On 19.01.2016 21:22, Hendrik Leppkes wrote:
On Tue, Jan 19, 2016 at 9:13 PM, Andreas Cadhalpun
wrote:
They don't la
Hi,
On Tue, Jan 19, 2016 at 3:41 PM, Andreas Cadhalpun <
andreas.cadhal...@googlemail.com> wrote:
> On 19.01.2016 21:31, Hendrik Leppkes wrote:
> > On Tue, Jan 19, 2016 at 9:27 PM, Andreas Cadhalpun
> > wrote:
> >> On 19.01.2016 21:22, Hendrik Leppkes wrote:
> >>> On Tue, Jan 19, 2016 at 9:13 PM
On Tue, 19 Jan 2016 21:31:19 +0100
Hendrik Leppkes wrote:
> On Tue, Jan 19, 2016 at 9:27 PM, Andreas Cadhalpun
> wrote:
> > On 19.01.2016 21:22, Hendrik Leppkes wrote:
> >> On Tue, Jan 19, 2016 at 9:13 PM, Andreas Cadhalpun
> >> wrote:
> >>> On 22.10.2015 11:44, Hendrik Leppkes wrote:
> >
On 19.01.2016 21:31, Hendrik Leppkes wrote:
> On Tue, Jan 19, 2016 at 9:27 PM, Andreas Cadhalpun
> wrote:
>> On 19.01.2016 21:22, Hendrik Leppkes wrote:
>>> On Tue, Jan 19, 2016 at 9:13 PM, Andreas Cadhalpun
>>> wrote:
On 22.10.2015 11:44, Hendrik Leppkes wrote:
They now made VLC's conf
On Tue, Jan 19, 2016 at 9:27 PM, Andreas Cadhalpun
wrote:
> On 19.01.2016 21:22, Hendrik Leppkes wrote:
>> On Tue, Jan 19, 2016 at 9:13 PM, Andreas Cadhalpun
>> wrote:
>>> On 22.10.2015 11:44, Hendrik Leppkes wrote:
On Thu, Oct 22, 2015 at 11:27 AM, Wang Bin wrote:
> VLC is using frame
On 19.01.2016 21:22, Hendrik Leppkes wrote:
> On Tue, Jan 19, 2016 at 9:13 PM, Andreas Cadhalpun
> wrote:
>> On 22.10.2015 11:44, Hendrik Leppkes wrote:
>>> On Thu, Oct 22, 2015 at 11:27 AM, Wang Bin wrote:
VLC is using frame threading with hwaccel
>>>
>>> Then they should fix their usage, i
On Tue, Jan 19, 2016 at 9:13 PM, Andreas Cadhalpun
wrote:
> On 22.10.2015 11:44, Hendrik Leppkes wrote:
>> On Thu, Oct 22, 2015 at 11:27 AM, Wang Bin wrote:
>>> VLC is using frame threading with hwaccel
>>
>> Then they should fix their usage, its broken by design, as explained
>> in detail my pos
On 22.10.2015 11:44, Hendrik Leppkes wrote:
> On Thu, Oct 22, 2015 at 11:27 AM, Wang Bin wrote:
>> VLC is using frame threading with hwaccel
>
> Then they should fix their usage, its broken by design, as explained
> in detail my post earlier in this thread.
Care to provide a patch for them?
The
On Thu, Oct 29, 2015 at 8:31 PM, Andy Furniss wrote:
> Hendrik Leppkes wrote:
>>
>> On Thu, Oct 22, 2015 at 11:27 AM, Wang Bin
>> wrote:
>>>
>>> VLC is using frame threading with hwaccel
>>
>>
>> Then they should fix their usage, its broken by design, as explained
>> in detail my post earlier in
Hendrik Leppkes wrote:
On Thu, Oct 22, 2015 at 11:27 AM, Wang Bin
wrote:
VLC is using frame threading with hwaccel
Then they should fix their usage, its broken by design, as explained
in detail my post earlier in this thread.
Seems ffmpeg cli does the same by default - OK so users can speci
On Thu, Oct 22, 2015 at 11:27 AM, Wang Bin wrote:
> VLC is using frame threading with hwaccel
Then they should fix their usage, its broken by design, as explained
in detail my post earlier in this thread.
- Hendrik
___
ffmpeg-devel mailing list
ffmpeg-
VLC is using frame threading with hwaccel
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, 21 Oct 2015 11:53:46 +0200
Hendrik Leppkes wrote:
> On Wed, Oct 21, 2015 at 11:44 AM, Gwenole Beauchesne
> wrote:
> > 2015-10-21 11:27 GMT+02:00 Hendrik Leppkes :
> >> On Sat, Oct 17, 2015 at 9:28 PM, Hendrik Leppkes
> >> wrote:
> >>> On Sat, Oct 17, 2015 at 9:27 PM, Hendrik Leppk
On Wed, Oct 21, 2015 at 11:44 AM, Gwenole Beauchesne wrote:
> 2015-10-21 11:27 GMT+02:00 Hendrik Leppkes :
>> On Sat, Oct 17, 2015 at 9:28 PM, Hendrik Leppkes wrote:
>>> On Sat, Oct 17, 2015 at 9:27 PM, Hendrik Leppkes
>>> wrote:
---
libavcodec/utils.c | 6 ++
1 file changed
2015-10-21 11:27 GMT+02:00 Hendrik Leppkes :
> On Sat, Oct 17, 2015 at 9:28 PM, Hendrik Leppkes wrote:
>> On Sat, Oct 17, 2015 at 9:27 PM, Hendrik Leppkes wrote:
>>> ---
>>> libavcodec/utils.c | 6 ++
>>> 1 file changed, 6 insertions(+)
>>>
>>
>> Above patch is submitted as an RFC, however I
On Sat, Oct 17, 2015 at 9:28 PM, Hendrik Leppkes wrote:
> On Sat, Oct 17, 2015 at 9:27 PM, Hendrik Leppkes wrote:
>> ---
>> libavcodec/utils.c | 6 ++
>> 1 file changed, 6 insertions(+)
>>
>
> Above patch is submitted as an RFC, however I strongly believe its the
> only way to keep hwaccels
On Sat, 17 Oct 2015 21:28:50 +0200
Hendrik Leppkes wrote:
> On Sat, Oct 17, 2015 at 9:27 PM, Hendrik Leppkes wrote:
> > ---
> > libavcodec/utils.c | 6 ++
> > 1 file changed, 6 insertions(+)
> >
>
> Above patch is submitted as an RFC, however I strongly believe its the
> only way to keep
On Sat, Oct 17, 2015 at 9:27 PM, Hendrik Leppkes wrote:
> ---
> libavcodec/utils.c | 6 ++
> 1 file changed, 6 insertions(+)
>
Above patch is submitted as an RFC, however I strongly believe its the
only way to keep hwaccels sane in the future.
There are several known problems when a hwaccel
---
libavcodec/utils.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavcodec/utils.c b/libavcodec/utils.c
index 0e4f3c0..52b480a 100644
--- a/libavcodec/utils.c
+++ b/libavcodec/utils.c
@@ -1006,6 +1006,12 @@ static int setup_hwaccel(AVCodecContext *avctx,
AVHWAccel *hwa = find
37 matches
Mail list logo
