On Thu, Mar 26, 2015 at 2:31 PM, Roger Pack wrote:
> If I install AviSynth 2.60 32-bit then use 32 bit ffmpeg.exe, I am
> able to consume a file like this:
>
> Version()
> So at least it's not totally broken for me here., I think.
> GL!
> -roger-
I tested yesterday afternoon with 64-bit AviSynth+
On 3/26/15, John Warburton wrote:
>> On Wed, Mar 25, 2015 at 7:50 PM, Michael Niedermayer
>> wrote:
>>> On Wed, Mar 25, 2015 at 01:59:18PM -0400, Stephen Hutchinson wrote:
On Wed, Mar 25, 2015 at 12:49 PM, Michael Niedermayer
wrote:
> ive applied patch 4 from the patchset too, doe
On Thu, Mar 26, 2015 at 11:43 AM, John Warburton wrote:
> Unfortunately, although FFmpeg compiles successfully, a simple
> AviSynth+ script that works perfectly in the 64-bit version of MPC-HC
> will not work in today's FFmpeg build. The error is "unknown error
> occurred". If there are additional
> On Wed, Mar 25, 2015 at 7:50 PM, Michael Niedermayer wrote:
>> On Wed, Mar 25, 2015 at 01:59:18PM -0400, Stephen Hutchinson wrote:
>>> On Wed, Mar 25, 2015 at 12:49 PM, Michael Niedermayer
>>> wrote:
>>> > ive applied patch 4 from the patchset too, does that fix it ?
>
>> applied the patches
On Wed, Mar 25, 2015 at 7:50 PM, Michael Niedermayer wrote:
> On Wed, Mar 25, 2015 at 01:59:18PM -0400, Stephen Hutchinson wrote:
>> On Wed, Mar 25, 2015 at 12:49 PM, Michael Niedermayer
>> wrote:
>> > ive applied patch 4 from the patchset too, does that fix it ?
> applied the patches
Thank yo
On Wed, Mar 25, 2015 at 01:59:18PM -0400, Stephen Hutchinson wrote:
> On Wed, Mar 25, 2015 at 12:49 PM, Michael Niedermayer
> wrote:
> > ive applied patch 4 from the patchset too, does that fix it ?
> > if not please check the remaining 2 patches, i had not applied them
> > as they remove 2.5 sup
On Wed, Mar 25, 2015 at 12:49 PM, Michael Niedermayer wrote:
> ive applied patch 4 from the patchset too, does that fix it ?
> if not please check the remaining 2 patches, i had not applied them
> as they remove 2.5 support and i wanted to wait first to see if
> someone posts a solution that keeps
On Wed, Mar 25, 2015 at 09:58:15AM -0600, Roger Pack wrote:
> On 3/25/15, Michael Niedermayer wrote:
> > On Tue, Mar 24, 2015 at 07:40:33PM +0100, Martin Herkt wrote:
> >> Merge commit 1530732 broke compilation with AviSynth enabled.
> >>
> >> There's really no reason to keep outdated, incompatibl
On 3/25/15, Michael Niedermayer wrote:
> On Tue, Mar 24, 2015 at 07:40:33PM +0100, Martin Herkt wrote:
>> Merge commit 1530732 broke compilation with AviSynth enabled.
>>
>> There's really no reason to keep outdated, incompatible copies of
>> these headers in the FFmpeg source tree. No one should
On Wed, Mar 25, 2015 at 11:41 AM, Michael Niedermayer wrote:
> On Tue, Mar 24, 2015 at 07:40:33PM +0100, Martin Herkt wrote:
>> Merge commit 1530732 broke compilation with AviSynth enabled.
>>
>> There's really no reason to keep outdated, incompatible copies of
>> these headers in the FFmpeg sourc
On Tue, Mar 24, 2015 at 07:40:33PM +0100, Martin Herkt wrote:
> Merge commit 1530732 broke compilation with AviSynth enabled.
>
> There's really no reason to keep outdated, incompatible copies of
> these headers in the FFmpeg source tree. No one should be using
> AviSynth 2.5 either.
> ---
> comp
Martin Herkt in gmane.comp.video.ffmpeg.devel (Tue, 24 Mar 2015 19:40:33
+0100):
>Merge commit 1530732 broke compilation with AviSynth enabled.
I ran into the same problem when cross-compiling for Windows on Ubuntu:
CC libavformat/avisynth.o
In file included from libavformat/avisynth.c:33:0:
Merge commit 1530732 broke compilation with AviSynth enabled.
There's really no reason to keep outdated, incompatible copies of
these headers in the FFmpeg source tree. No one should be using
AviSynth 2.5 either.
---
compat/avisynth/avisynth_c.h | 880 -
13 matches
Mail list logo