Forwarding consulting job offer to mailing list with
permission from sender. -Compn :
Hi,
we are a transcription company that does transcription of broadcast
news. For that purpose, we need several TV stations constantly recorded
in chunks. We have developed software to
we need the mp4 file to test.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
kv and avi seems like a bad idea as they use the same tags.
https://www.matroska.org/technical/guides/faq/index.html
> A mux whitelist would be just as much as splitting the list. (Although
> having separate mux lists would be a good idea t
On Fri, 4 May 2018 08:19:27 -0400, Compn wrote:
> my idea would be to create a whitelist of codec ids we can encode to,
> instead of splitting up the decode fourcc list amongst formats.
that would also be a nightmare to maintain and users would ask for
support for "xxx codec"
ess with the decoder
fourccs at all.
please let me know if my idea would work, i am probably missing some
huge flaw somewhere...
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
ec/siren.c | 847
>
> 5 files changed, 858 insertions(+)
does this also decode msnsiren? or no?
did you use this patch ?
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2012-July/127801.html
good work paul!
-compn
__
rate = 6400;
wow great!
now there is only the other vivo video codec left and then this format
can finally be completed?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
at all. its a
technical problem, and ffmpeg is all about technical problems.
ssl heartbleed was a technical problem that was also posted to our news
page. i dont remember the vitriol about that ssl news post.
-compn
___
ffmpeg-devel mailing list
ffmpe
gt; SDK,
> even though it's not what they need.
>
> This will make it complain about ffnvcodec instead.
i'm not objecting.
but if you put a error message that explains what a person needs when
it errors , that might also be a good idea (and it would also only be
ges of internet policy are going to affect everyone in different
ways. to ignore this is folly.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sun, 4 Mar 2018 09:45:03 -0500, "Ronald S. Bultje"
wrote:
> Hi,
>
> On Sun, Mar 4, 2018 at 9:24 AM, Compn wrote:
>
> > On Thu, 1 Mar 2018 06:59:45 -0500, "Ronald S. Bultje"
> > wrote:
> > > Again, please: no advertising, no politics.
ing.
what is your significant issue with the politics?
could you share your opinion please?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
nd disabling javascript
everywhere else. Complaining about a 3rd party javascript, in this day
and age, means you've already thrown in the towel on your browser
security.
or in lieu of a news post, make the widget only on ffmpeg.org/index ,
not on DOCS pages. I ran into the widget a few times too when it was
misbehaving.
I am not objecting outright, net neutrality is pretty important.
And yes, you foreigners should be helping the USA with this, as
THIS WILL affect the backbones. how many internet backbones are owned
by US companies? non-usa people can help in some ways:
1. ask friends in usa to help
2. post on your own blogs and websites, spread the word
3. contact your local political representatives to tell them how net
neutrality is important.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Mon, 26 Feb 2018 00:01:29 +0100, Stephan Holljes
wrote:
> My name is Stephan Holljes, on IRC I go by klaxa. Some may remember me
> from GSoC 2015 where I implemented the (how I later found out
> controversly debated) HTTP-Server API.
welcome back! :
On Fri, 23 Feb 2018 22:32:41 +0530, sunsi...@iitk.ac.in wrote:
> Hello, my name is Gagandeep Singh and I am a sophomore at Indian Institute
> Gagandeep Singh
> IRC NICK:
> gagandeep
> gagandeep_
> gagandeep__
welcome to ffmpeg and the open source
ags because
other software uses them and samples exist in the wild.
not sure if i've helped here.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
ch files.
hope this helps.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
ticket per file.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Fri, 22 Dec 2017 14:39:40 -0500, Compn wrote:
> carl if you have a suggestion for better wording, please send patch ?
also as the other ml admin, i agree with lou's commit and
community agreed upon policy change.
what discussions do you want to have on -cvslog that would not be
bett
but i also understand -cvslog mailing
lists have evolved to make things easier and simpler for developers to
not have to follow two lists for discussion.
also possibly git log has replaced -cvslog for many developers.
carl if you have a suggestion for bette
tive plastic bag.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sun, 17 Dec 2017 22:16:50 +, Josh de Kock
wrote:
> On Sun, 17 Dec 2017 17:12:24 -0500
> Compn wrote:
>
> > On Sun, 17 Dec 2017 21:57:07 +, Josh de Kock
> > wrote:
> >
> > > On Sun, 17 Dec 2017 15:36:53 -0500
> > > Compn wrote:
&
On Sun, 17 Dec 2017 21:57:07 +, Josh de Kock
wrote:
> On Sun, 17 Dec 2017 15:36:53 -0500
> Compn wrote:
>
> > [...]
> >
> > emergency moderation has now been enabled.
> >
> > why do i have to enforce the COC?
> >
> > the ffmpeg
ill not be tolerated.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
en read the list right now.
maybe the patchset without the included header could get reviewed some
more and possibly applied while we wait for the external repo changes.
remember we are mostly volunteers working on ffmpeg. which means we all
have regular non-ffmp
se comes along i have no problem
with this. but its also not my call, just my personal opinion.
to make it easier on users who dont have to go around looking for sdk
and extracting headers and all that baloney.
-compn
___
ffmpeg-devel mailing list
ffmpeg-
with some more reviews.
please be patient.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
v
speaks for the entire project.
wm4 is entitled to fork whatever open source project he wants, and hes
welcome to post here and review patches and be a developer.
carl you dont have to respond to every aggressive post. nor do you have
to attack people.
paul and wm4 please stop insulting developers a
to that ?
that would cut down on our objections and maintainership and git
history concerns... i think? so long as its easy for non amd users to
flip a config switch to disable pulling those amd headers down.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
d on irc.freenode.net #ffmpeg-devel as well for real
time chat.
tl;dr my suggestions:
1. split docs patch
2. less words, rephrase for brevity
3. welcome to open source team collaboration :)
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
ngs would be too much
> extra
> cost (>15/shirt I'd say).
i am fine with green or white. i hope that the green (light green?) is
visible on a black shirt of course.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
that your only suggestion how to do this? Because it's a bad one.
michael, do you have other suggestions how to solve this problem? are
you going to fix the errors in the doxygen that you noticed due to
merges?
wm4, would you object to adding another special field? if
someone else edited
And just another cook in the kitchen
> would also more likely avoid conensus here.
thilo, can we bribe you to massage this patch a little?
it seems like wm4 and michael both are not budging...
a third party might be able to settle the stalemate.
-compn
ng it passes fate...
just submit patch here , we'll review it.
even if ffmpeg does not accept it, its possible that other people will
use your patch for their setup.
thanks!
welcome to ffmpeg.
-compn
___
ffmpeg-devel mailing list
ffmpeg-deve
if we scare off devs who get frustrated that the COC was not fully
fairly applied to everyone? e.g. one dev gets moderated while another
skates ? thats where the strife gains momentum.
thoughts?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
sive troll, and always have
> > > been when it came to things related to Libav.
calling people names like troll probably not good idea in professional
environment. also maybe CoC violation.
> Let me make this clear: we WILL be friendly with the Libav project. We
> WILL work t
nal website, like many other developers do.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
nevermind , bad idea.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
urity email"
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
subscribed if they want.
thanks for reading.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Mon, 06 Feb 2017 13:22:31 +, Kieran Kunhya
wrote:
> On Mon, 6 Feb 2017 at 05:54 Compn wrote:
>
> > people new to the project join #ffmpeg-devel and ask us for help on how
> > to start contributing to ffmpeg.
> >
>
> A simple one is work on making decode
people new to the project join #ffmpeg-devel and ask us for help on how
to start contributing to ffmpeg.
usually none of us have any cohesive answers. mostly suggestions are to
review bugs or patches or code. nothing really concise or organized.
i've reviewed a few bugs and think these may be goo
On Sat, 4 Feb 2017 12:59:13 +0100, wm4 wrote:
> On Sat, 4 Feb 2017 00:02:16 +0200
> Ivo Andonov wrote:
>
> > 2017-02-03 23:18 GMT+02:00 Compn :
> >
> > > On Fri, 3 Feb 2017 15:46:20 +0200, Ivo Andonov
> > > wrote:
> > >
> > > > I
peg? they must ship ffmpeg source as well, the
modified ffmpeg source may contain the patch needed to play such
dvr files.
where can we see this pinetron library ?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman
On Thu, 2 Feb 2017 09:30:30 +0100, Carl Eugen Hoyos wrote:
> 2017-02-01 19:36 GMT+01:00 Compn :
>
> >> How are we supposed to access the samples?
> >
> > files uploaded with the vlc http upload
> > http://streams.videolan.org/upload/
> >
> > are im
your file:
http://streams.videolan.org/upload/
thank you.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Wed, 1 Feb 2017 17:45:16 +0100, Carl Eugen Hoyos wrote:
> 2017-02-01 14:10 GMT+01:00 compn :
>
> > [05:41] Compn, http://streams.videolan.org/upload/
> > should work more or less
> >
> > ^ this is currently where we should send users to upload files.
> &
On Wed, 1 Feb 2017 07:34:11 +0100
wm4 wrote:
> On Wed, 1 Feb 2017 00:09:41 -0500
> compn wrote:
>
> > not sure if this is the right way to do it, maybe its easier to ask
> > for someone on twitter?
> >
> > it would be nice to have a backup just in case videol
not sure if this is the right way to do it, maybe its easier to ask for
someone on twitter?
it would be nice to have a backup just in case videolan has problems.
then we dont have to ask users to use datafilehost heh.
i dont want to burden ffmpeg admins to maintain some ftp either.
carl, what do
t we need is someone to run a small ftp drop for large files, i
guess i'll post a patch for the ffmpeg.org page requesting such hosting
temporarily.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
would prefer we added avlg as well, even if we don't have samples.
-compn
xalg.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
s replaces a strcpy with a memcpy, is this intended (and safe?)?
(possibly this is a dumb question, if so, please ignore this mail.)
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
6854583/compiling-ffmpeg-for-kali-linux-2
this change looks unrelated.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
e_ffmpeg_aspect.ts
someone should probably organize a small suite of res changing
samples...
i think someone had a bunch of them, maybe michael or stefano?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
r-ffmpeg/
hi! it is impressive for a first patch! well done.
your patch is missing docs (document -huffman optimal by creating mjpeg
encoder section in doc/encoders.texi)
and changelog entry (Optimal Huffman tables for MJPEG encoding).
-compn
___
ffmpe
tested patch...
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
is a problem, i would rather make it more difficult for the user
to encode mp2. by defaulting to mp3 and / or printing a warning message
about mp2. honestly i cant remember any good coming from someone using
mp2.
mp2 is dead, long live mp3.
also please share yo
o have a replacement. one
that accepts large files.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> As for how libavcodec can do provide this part, see the Libav/avconv
> vaapi support (none of that is in ffmpeg yet).
same question here.
i am not arguing one way or the other, just asking.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sun, 11 Dec 2016 17:39:58 +0100
Nicolas George wrote:
> This reverts commit 2f07830e69bd14eaba348eb739b9503e7eb7cd4b.
would you rather the people doing the fuzzing use this feature as a
separate patch so it does not contaminate master?
-co
yeah.
-compndiff --git a/src/index b/src/index
index c203676..f6c925f 100644
--- a/src/index
+++ b/src/index
@@ -86,15 +86,6 @@
We recommend users, distributors, and system integrators, to upgrade
unless they use current git master.
- July 10th, 2016, ffserver program being dropped
On Fri, 2 Dec 2016 00:40:02 +0100
Carl Eugen Hoyos wrote:
> 2016-12-01 19:58 GMT+01:00 compn :
>
> > if (codec_tag &&
> > (codec_tag != format &&
> > + (codec_tag != AV_RL32("AV1x") || format !=
> > AV_RL32
'AVUP': 'Avid 10bit Packed (Quick Time)',
possibly AVin
sample here : http://samples.ffmpeg.org/ffmpeg-bugs/trac/ticket524/AVCI50.mov
do any of these isoms need to be added to the list in mov.c ?
otherwise, looks ok if tested with our av1x/avup samples.
thanks,
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
h sides are
unable to come to a compromise.
sometimes you have to cut off the toe to save the patient. :)
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
maybe when there is a conflict of opinion on a patch, we should agree
to disagree on said patch and ignore it?
instead of arguing endlessly about it?
not specifically targeting you, james, but a lot of people in this
thread.
-compn
___
ffmpeg-devel
On Sat, 26 Nov 2016 18:05:52 +0100
Nicolas George wrote:
> Le sextidi 6 frimaire, an CCXXV, compn a écrit :
> > so unlikely that i cannot even imagine the odds.
>
> Any scientific reason why?
if one wants to be worried about security issues, there are bigger fish
to fry.
for o
On Sat, 26 Nov 2016 17:15:36 +0100 (CET)
Marton Balint wrote:
>
> On Sat, 26 Nov 2016, compn wrote:
>
> > On Fri, 25 Nov 2016 11:11:23 +0100 (CET)
> > Marton Balint wrote:
> >
> >>
> >> On Mon, 21 Nov 2016, Michael Niedermayer wrote:
> >
If somebody does not
> use his account for a year or so, his/her access should be revoked.
any scientific reason why?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
fate tests, and it should be done.
hopefully you have test samples made of these pixfmts you want to add.
that makes testing for us easier, as we can test on multiple cpu
arch's to make sure the code is safe and works.
-compn
___
ffmpeg-devel ma
;ll add some
> > #if/%if around it...
> >
>
> They were already there but one %endif was misplaced. Fixed locally.
is nice to resend patch just so "we" (by we i mean michael) can keep
checking for problems like this ;)
unless you already tested on x86...
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
lmedia_mp3_dynamic_handler);
should probably l24 be under gsm as this list looks like alphabetical
order.
i've only seen l16 rtsp samples, have not seen l24 yet.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
s this in september, after the news entry was posted
http://ffmpeg.org/pipermail/ffmpeg-devel/2016-September/199686.html
i'd suggest talking to that person before applying said patch.
we can talk before applying a patch still, right? :)
-compn
_
testing the D3D11 stuff in there (and I
do you want a windows box with a d3d11 card? there are many companies
now using ffmpeg and they want to get boxes into developer hands for
testing.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://f
nd correct one.
why are SAR and DAR in the output twice now? it might be confusing to
users? or just me...
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
come to learn why the things are done in a certain way.
> A good place to start might be the musl mailing list.
after reading this thread, the thing i realize now is that our
developers would rather do a line by line audit of another libc
software project than an audit of ffmpeg
musl could handle it better sure, but should they really write a full
c-checker into their lib? would make it as bloated as glibc!
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
#x27;s box.
on irc i pointed dalias to this thread.
or you can just ask on #musl in freenode.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
de, just my observation.
feel free to tell me that i am wrong.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
this prevents all of those files from trying to be decoded as aac ?
if so, good.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
; there search ml archives by going through them month by month.
possible with google using:
searchterm site:ffmpeg.org inurl:ffmpeg-cvslog
searchterm site:ffmpeg.org inurl:ffmpeg-devel
i dont know if mailman has a search feature.
https://wiki.list.org/DOC/How%20do%20I%20make%20the%20arc
t; Before coding anything I'd like to get a feeling for what kind of
> solution
>
> could be acceptable for the project.
there is qt fast start feature in ffmpeg. which is similar , but for
mp4 files.
i am not sure if the devs want this feature to be copied into mkv, you
better
hat headache.
>
> The header is still MIT licensed and thus fine to bundle with ffmpeg.
is ok with me. but i am not maintainer.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sat, 27 Aug 2016 13:49:25 +0200
Timo Rothenpieler wrote:
>I'll push for another attempt of including the header in ffmpeg
including nvidia header in linux kernel was a no-go ?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.
h, i hope there is a way to fix this.
do we have any apple contacts to report this bug?
is it possible to use a different getaddrinfo on ios?
thanks for patch.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
rogram.
>
> that would be great, do you have any specific ideas for a easy
> project ?
reviewing all (or maybe 500) bugs in trac, testing with latest git
version and updating or closing old bugs?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@f
2016, on the 1st week-end of September: 2-4 September 2016, in
> > Berlin.
>
> I'm just aware of Thomas Volkert and myself who are attending for
> sure.
>
> Who else is planning to come?
i'm planning to go. it will be interesting for me to see this qtcon as
well :)
mit
> message.
http://www.openh264.org/faq.html
https://github.com/cisco/openh264
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
i just
our ffmpeg software is free and available at ffmpeg.org.
we dont know what software you are using, you have contacted the wrong
people.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, 14 Jul 2016 16:26:09 -0400
compn wrote:
> shouldnt these other 4 tags also be added?
also i think adding a comment in isom.c about adding any new prores tags
to this hack in mov.c would be useful.
i am assuming prores will have more tags in the future.
-co
'n') }, /* Apple ProRes 422 Standard
Definition */
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', 'c', 's') }, /* Apple ProRes 422 LT */
{ AV_CODEC_ID_PRORES, MKTAG('a', 'p', 'c',
to ffmpeg, smitbose.
welcome to the world of open source.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Mon, 4 Jul 2016 12:43:03 +0300
Sami Hult wrote:
> My five cents would be to advice every aspiring contributor to focus
> on bugs or lacking features that are an issue for themselves. That
> ensures motivation to really fix it :)
that is good advice, thank you
. i just want to
have a solid number (100-300+) of bugs that are somewhat easy to
understand, implement, review and finish.
have a great summer (for those in the northern hemisphere),
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, 23 Jun 2016 23:00:48 +0200
Michael Niedermayer wrote:
> what shall FFmpeg 3.1 be called ?
> Are there other suggestions?
has fibonacci been used?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/li
or trying.
why is no one happy?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
did call him a troll. :D
> the CoC then you're welcome to call a vote for whatever action you
nah, i actually dont give a shit. i'm for free speech, not nonsense
censorship. :)
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.o
On Thu, 16 Jun 2016 09:12:39 -0400
Rick Kern wrote:
> Person in MAINTAINERS hasn't responded to a patch on the ML or private
> email, and doesn't maintain the files according to git.
LGTM
-compn
___
ffmpeg-devel mailing list
ffmpeg-
On Wed, 15 Jun 2016 21:21:28 -0300
James Almer wrote:
...
you are aware that we have voted in a code of conduct.[1]
you may want to review it, again.
https://ffmpeg.org/developer.html#Code-of-conduct
calling developers names will not be tolerated.
-compn
[1] http://lists.ffmpeg.org
s lack of free time. thats
whats nice about open source, you can pick it up and drop it whenever.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Sat, 4 Jun 2016 13:03:47 +0200
Michael Niedermayer wrote:
> On Fri, Jun 03, 2016 at 10:19:29PM -0400, compn wrote:
> > On Fri, 3 Jun 2016 21:13:09 +0200
> > Michael Niedermayer wrote:
> >
> > > On Fri, Jun 03, 2016 at 08:32:51PM +0200, Christophe Gisquet
>
1 - 100 of 271 matches
Mail list logo
