Paul B Mahol gmail.com> writes:
> I'm still for removing this.
Please provide a new commit message.
> I added 10-bit support to native decoder.
This is a good reason for the removal.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On 2/14/16, James Almer wrote:
> On 2/14/2016 12:20 PM, Carl Eugen Hoyos wrote:
>> James Almer gmail.com> writes:
>>
>>> How do you plan to get around the fact the only working
>>> version of this library is an obscure outdated fork that
>>> doesn't even compile on most OSes
>>
>> I am sorry, I d
On 2/14/2016 12:20 PM, Carl Eugen Hoyos wrote:
> James Almer gmail.com> writes:
>
>> How do you plan to get around the fact the only working
>> version of this library is an obscure outdated fork that
>> doesn't even compile on most OSes
>
> I am sorry, I did not realize this:
> On which syste
James Almer gmail.com> writes:
> How do you plan to get around the fact the only working
> version of this library is an obscure outdated fork that
> doesn't even compile on most OSes
I am sorry, I did not realize this:
On which system does it not compile?
Carl Eugen
On 2/14/2016 11:53 AM, Carl Eugen Hoyos wrote:
> Paul B Mahol gmail.com> writes:
>
>> Because there is not more maintainer for this, I will
>> push this very soon.
>
> I will try to maintain it for the foreseeable future.
>
> Carl Eugen
How do you plan to get around the fact the only working
Paul B Mahol gmail.com> writes:
> Because there is not more maintainer for this, I will
> push this very soon.
I will try to maintain it for the foreseeable future.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/m
On 2/10/16, Derek Buitenhuis wrote:
> * Upstream libutvideo doesn't build as a lib, and Linux is not supported.
> It has no API.
> * The fork that was used as an argument to keep support is *also* broken and
> unmaintained now, and it's maintainer/author is fine with removal.
> * A third fork
Derek Buitenhuis gmail.com> writes:
> On 2/12/2016 5:03 PM, Paul B Mahol wrote:
> > make install (as root)and then build FFmpeg with
> > libutvideo support.
>
> Last time I tried this, it failed to configure, due to
> duplicated symbol 'main'.
It works fine here for 32 and 64 bit for unpatched
On 2/12/2016 11:51 AM, Carl Eugen Hoyos wrote:
Derek Buitenhuis gmail.com> writes:
On 2/10/2016 4:33 PM, Paul B Mahol wrote:
I'm fine by this, but it would be nice to have SIMD and
10 bit support in decoder.
I agree with the latter.
I'd argue, however, we don't actually support 10-bit via
On 2/12/2016 5:03 PM, Paul B Mahol wrote:
> make install (as root)and then build FFmpeg with
>> libutvideo support.
Last time I tried this, it failed to configure, due to duplicated symbol 'main'.
- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpe
On 2/12/16, Carl Eugen Hoyos wrote:
> Derek Buitenhuis gmail.com> writes:
>
>> On 2/10/2016 4:33 PM, Paul B Mahol wrote:
>> > I'm fine by this, but it would be nice to have SIMD and
>> > 10 bit support in decoder.
>>
>> I agree with the latter.
>>
>> I'd argue, however, we don't actually support
Derek Buitenhuis gmail.com> writes:
> On 2/10/2016 4:33 PM, Paul B Mahol wrote:
> > I'm fine by this, but it would be nice to have SIMD and
> > 10 bit support in decoder.
>
> I agree with the latter.
>
> I'd argue, however, we don't actually support 10-bit via the
> wrapper anyway, since you c
Hi,
On Fri, Feb 12, 2016 at 11:24 AM, Carl Eugen Hoyos wrote:
> Derek Buitenhuis gmail.com> writes:
>
> > On 2/12/2016 2:24 PM, Carl Eugen Hoyos wrote:
> > > It works here with a repo I found on my hard disc
> >
> > This means nothing to users, unless you want to mail
> > your harddisk to each
Derek Buitenhuis gmail.com> writes:
> On 2/12/2016 2:24 PM, Carl Eugen Hoyos wrote:
> > It works here with a repo I found on my hard disc
>
> This means nothing to users, unless you want to mail
> your harddisk to each user.
It works fine after "git pull".
How do I ask git where it pulled from
On 2/12/2016 9:24 AM, Carl Eugen Hoyos wrote:
Derek Buitenhuis gmail.com> writes:
On 2/10/2016 4:33 PM, Paul B Mahol wrote:
I'm fine by this, but it would be nice to have SIMD
and 10 bit support in decoder.
I agree with the latter.
I'd argue, however, we don't actually support 10-bit via t
On 2/12/2016 2:24 PM, Carl Eugen Hoyos wrote:
> It works here with a repo I found on my hard disc
This means nothing to users, unless you want to mail
your harddisk to each user.
- Derek
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmp
Derek Buitenhuis gmail.com> writes:
> On 2/10/2016 4:33 PM, Paul B Mahol wrote:
> > I'm fine by this, but it would be nice to have SIMD
> > and 10 bit support in decoder.
>
> I agree with the latter.
>
> I'd argue, however, we don't actually support 10-bit via the
> wrapper anyway, since you c
On Wed, 10 Feb 2016 15:47:52 +
Derek Buitenhuis wrote:
> * Upstream libutvideo doesn't build as a lib, and Linux is not supported.
> It has no API.
> * The fork that was used as an argument to keep support is *also* broken and
> unmaintained now, and it's maintainer/author is fine with re
On 2/10/2016 4:33 PM, Paul B Mahol wrote:
> I'm fine by this, but it would be nice to have SIMD and 10 bit support
> in decoder.
I agree with the latter.
I'd argue, however, we don't actually support 10-bit via the
wrapper anyway, since you can't even build the library. ;)
- Derek
__
On 2/10/16, Carl Eugen Hoyos wrote:
> Derek Buitenhuis gmail.com> writes:
>
>> * The ASM in libutvideo doesn't even work on x86_64.
>
> Just to make sure (I am only guessing):
> 32bit libutvideo (on 64bit) is faster than 64bit native decoder / encoder?
Maybe on Windows. On Linux it crashes.
Derek Buitenhuis gmail.com> writes:
> * The ASM in libutvideo doesn't even work on x86_64.
Just to make sure (I am only guessing):
32bit libutvideo (on 64bit) is faster than 64bit native decoder / encoder?
Carl Eugen
___
ffmpeg-devel mailing list
ffm
On 2/10/16, Derek Buitenhuis wrote:
> * Upstream libutvideo doesn't build as a lib, and Linux is not supported.
> It has no API.
> * The fork that was used as an argument to keep support is *also* broken and
> unmaintained now, and it's maintainer/author is fine with removal.
> * A third fork
* Upstream libutvideo doesn't build as a lib, and Linux is not supported.
It has no API.
* The fork that was used as an argument to keep support is *also* broken and
unmaintained now, and it's maintainer/author is fine with removal.
* A third fork on github, *also* doesn't work.
* The only work
23 matches
Mail list logo