Hi Andrey,
On 26.01.2016 20:53, Andrey Gursky wrote:
> recently I noticed a warning from vlc developers regarding the upcoming
> FFmpeg 2.9 release [1]. Are you already aware of it?
Yes, we're aware of that, but thanks for notifying us anyway.
This will be fixed upstream in FFmpeg shortly.
> I'm
Hi,
recently I noticed a warning from vlc developers regarding the upcoming
FFmpeg 2.9 release [1]. Are you already aware of it? I'm wondering,
whether mplayer and mpv are also affected. Could this delay the
transition to FFmpeg 2.9 until the issue will be resolved or it is
already done?
Regards,
On 02.11.2015 18:58, Felipe Sateler wrote:
> On 2 November 2015 at 14:40, Andreas Cadhalpun
> wrote:
>> On 02.11.2015 00:57, Felipe Sateler wrote:
>>> On 1 November 2015 at 19:51, Andreas Cadhalpun
>>> wrote:
building: 30
simple changes: 61
complex changes:21
On 2 November 2015 at 14:40, Andreas Cadhalpun
wrote:
> On 02.11.2015 00:57, Felipe Sateler wrote:
>> On 1 November 2015 at 19:51, Andreas Cadhalpun
>> wrote:
>>>
>>> building: 30
>>> simple changes: 61
>>> complex changes:21
>>> --
>>> total: 112
On 02.11.2015 00:57, Felipe Sateler wrote:
> On 1 November 2015 at 19:51, Andreas Cadhalpun
> wrote:
>>
>> building: 30
>> simple changes: 61
>> complex changes:21
>> --
>> total: 112
>
> How did you come up with those numbers? Did you actually ma
On 1 November 2015 at 19:51, Andreas Cadhalpun
wrote:
> Hi,
>
> ffmpeg upstream removed some deprecated APIs, so the next release will require
> a transition. A large number of reverse dependencies need source code patches.
> Most of those are simple changes like renaming functions/macros, but som
Hi,
ffmpeg upstream removed some deprecated APIs, so the next release will require
a transition. A large number of reverse dependencies need source code patches.
Most of those are simple changes like renaming functions/macros, but some are
more complex:
building: 30
simple changes:
