SL Project has ended the long-term support for version
1.1.1
https://www.theregister.com/2023/09/12/openssl_111_end_of_life/
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
27;s 20+year history.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
or Paul and let him speak for
himself. if he wants to.
Developers leave, come back, and leave again. its a project made up of
volunteers. No one is forced to join and forced to stay forever.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
mmit message from
avformat/matroskaenc: Use native id instead of VfW for FFV1
to
avformat/matroskaenc: Use native id V_FFV1 instead of V_MS/VFW/FOURCC/FFV1
if you think its appropriate anyway.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.or
On Sun, 25 May 2025 23:29:45 +0100, Kieran Kunhya via ffmpeg-devel
wrote:
> Hi Michael,
>
> Here is how this should be handled.
stop with this nonsense.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman
recreate their mkv. which is something that
archivists do sometimes.
e.g. old ffv1 mkv vfw codec_id
vs
new ffv1 mkv codec_id
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, v
ong behavior was.
otherwise said developer can never learn. i'm not saying this has to be
public, it can be private.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit l
tps://lists.ffmpeg.org/pipermail/ffmpeg-devel/2024-December/337845.html
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2024-December/337860.html
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
dministration and moderation if they have an inter-personal conflict
with me.
i think i've sent my thoughts to the previous CC on this issue. but if
the new CC would like to talk, i'm available.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ff
ub with a mailinglist or with gitlab?
theres no reason why we cant have multiple ways to contribute to ffmpeg.
have pull requests send notifications to this mailing list?
https://github.com/settings/notifications
-compn
___
ffmpeg-devel mailing list
ffm
On Tue, 28 Jan 2025 23:26:39 -1000, compn wrote:
> hi,
>
> as i asked on irc this week, and as many of you may have seen it, the
> owner of twitter/x did a thing at a political rally last week:
> https://www.youtube.com/watch?v=wubITdJ_MCw
>
> when asked if he meant the ges
nt get our way, we'll quit/fork" stuff. its
not a friendly nor professional ultimatum.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
On Wed, 29 Jan 2025 21:13:13 +0800, Steven Liu wrote:
> compn 于2025年1月29日 周三17:26写道：
>
> > hi,
>
> Hi compn
>
>
>
> >
> > as i asked on irc this week, and as many of you may have seen it, the
> > owner of twitter/x did a thing at a political
count and point to alternate modes of ffmpeg
communication
thank you
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org
cineon ?
p.s. i see you are a colorist, please no more orange/teal.
http://theabyssgazes.blogspot.com/2010/03/teal-and-orange-hollywood-please-stop.html
thanks
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/list
On Tue, 21 Jan 2025 02:26:24 +0100, Michael Niedermayer wrote:
> I also dont think we even need a vote to just setup a Forgejo on ffmpeg.org
> when it replaces nothing but just adds an option
i agree lets turn on and test these options instead of endlessly
discussing and voting.
it-send-mail?
thanks
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
t think this was a requirement. i'm just saying if you
made a complaint , it was SOP to not get a response.
going forwards, it would be nice if the new cc (or whats left of it),
would respond to complainants to let them know if the complaint was
heard, ignored, acted on, fixed
On Thu, 2 Jan 2025 02:23:08 +, Kieran Kunhya via ffmpeg-devel wrote:
> On Wed, Jan 1, 2025 at 11:10 PM compn wrote:
> >
> > On Tue, 31 Dec 2024 17:28:31 +, Kieran Kunhya via ffmpeg-devel
> > wrote:
> >
> > > I personally don't want any c
snt require a vote. just
a simple patch to src/download and whoever volunteers to admin the
backup server.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or e
d NONE of these problems (not saying it was perfect - it did
> have other problems, but not these)
> * there is no hope for this project as long as you continue to hold the
> reins and I've wasted enough of my life on it.
>
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2011-
On Sat, 21 Dec 2024 01:42:32 +0100, Michael Niedermayer wrote:
> Hi
>
> On Thu, Dec 19, 2024 at 04:53:48PM -1000, compn wrote:
> > On Thu, 19 Dec 2024 21:04:50 +0100, Michael Niedermayer wrote:
> > if our goal is to attract new developers it would be better to invite
>
" leads exactly to the situation we have now, and all the
> similar situations we've had in the past.
>
> No, Michael, it's not "unfriendly people". It's you. It's always been
> you. Other projects do not have these problems at such a re
On Thu, 19 Dec 2024 21:04:50 +0100, Michael Niedermayer wrote:
> Hi Kieran
>
> (also thx to compn for reminding me about this mail)
>
> On Fri, Dec 13, 2024 at 01:30:43AM +, Kieran Kunhya via ffmpeg-devel
> wrote:
> > Hello,
> >
> > This person asked fo
On Fri, 20 Dec 2024 01:35:01 +, Kieran Kunhya via ffmpeg-devel
wrote:
> On Thu, Dec 19, 2024 at 9:11 PM compn wrote:
> >
> > On Thu, 19 Dec 2024 20:40:55 +, Kieran Kunhya via ffmpeg-devel
> > wrote:
> >
> > > Please can you confirm you will b
being ml admin.
i took the initiative to moderate the thread from flames, but as
another ml admin undid said moderation. not much i can do. i'm
not getting into any revert wars with other admins.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ff
On Thu, 19 Dec 2024 20:35:43 +, Kieran Kunhya via ffmpeg-devel
wrote:
> On Thu, 19 Dec 2024, 20:30 compn, wrote:
>
> > On Thu, 19 Dec 2024 20:15:10 +, Kieran Kunhya via ffmpeg-devel
> > wrote:
> >
> > > Some Animals are More Equal Than Others.
> >
On Thu, 19 Dec 2024 20:15:10 +, Kieran Kunhya via ffmpeg-devel
wrote:
> Some Animals are More Equal Than Others.
>
> Kieran
and now a CC candidate calling devs animals ?
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.
On Thu, 19 Dec 2024 17:51:24 +0100, Anton Khirnov wrote:
> Quoting compn (2024-12-19 17:32:26)
> > On Thu, 19 Dec 2024 14:58:34 +0100, Anton Khirnov wrote:
> > > I saw no announcement of any CC action related to that thread.
> >
> > i didnt moderate that st
On Thu, 19 Dec 2024 13:16:23 -0300, James Almer wrote:
> On 12/19/2024 1:12 PM, compn wrote:
> > On Thu, 19 Dec 2024 10:04:53 -0300, James Almer wrote:
> >> I have no idea who added the rule for "upcoming vote", but i just
> >> removed it.
> >>
>
did , as specified here:
https://lists.ffmpeg.org/pipermail/ffmpeg-devel/2024-December/337678.html
> Which mail? I added rules to block two threads as notified publicly by
> Ronald since said threads were too heated.
>
> > >
> > > Indirect evidence points towards co
> How is this fair that one person can unilaterally decide this?
as ml admin if i see flames i try to tamper them down a bit.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscr
ded rules to block two threads as notified publicly by
> Ronald since said threads were too heated.
>
> >
> > Indirect evidence points towards compn adding the block in both cases.
> > IMO it's utterly unacceptable that a random unelected person (not even a
> &g
what other dev.
> For a long time FFmpeg booths
as for booth discussion i think no one is ever going to apologize one
way or the other. so just ignore it and move on.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mail
On Wed, 11 Dec 2024 14:56:23 +0100, Timo Rothenpieler wrote:
> On 11/12/2024 10:10, Arnaud Masserann wrote:
> > Hi, any feedback on this patch ?
>
> I do not appear to have received the mail you are replying to here
https://ffmpeg.org//pipermail/ffmpeg-devel/2024-December/336971.html
But also to encourage
developers to remove personal discussion and resend their development
mails free of negativity.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit li
ok, sounds good to me.
> > ill wait a day or 2 before creating it, in case someone wants to
> > suggest another one
>
> repository created:
> g...@git.ffmpeg.org:ffmpeg-internals
can you move doc/infra.txt there.
no reason to have it in tru
og/2016-July/101287.html
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
le have issues with me having
> access I'd gladly remove myself and leave the work to the other root
> administrators. Also I'm available on IRC (nickname Raz-) or via email
> if you have any questions or just want to chat. :)
>
> Cheers,
> Nik
i&#
e. everyone should go to korea if they get the chance, its great!!
thanks for organizing.
(and i'm sorry to CC for threadjacking. i'll do better.)
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/
On Tue, 26 Nov 2024 10:15:02 -0500
Vittorio Giovara wrote:
> On Mon, Nov 25, 2024 at 7:33 PM compn wrote:
>
> > On Mon, 25 Nov 2024 18:52:02 -0500
> > Vittorio Giovara wrote:
> >
> > > On Mon, Nov 25, 2024 at 6:11 PM compn wrote:
> > >
On Mon, 25 Nov 2024 18:52:02 -0500
Vittorio Giovara wrote:
> On Mon, Nov 25, 2024 at 6:11 PM compn wrote:
>
> > On Mon, 25 Nov 2024 17:37:52 -0500
> > Vittorio Giovara wrote:
> >
> > > On Mon, Nov 25, 2024 at 5:09 PM compn wrote:
> > >
>
On Mon, 25 Nov 2024 17:37:52 -0500
Vittorio Giovara wrote:
> On Mon, Nov 25, 2024 at 5:09 PM compn wrote:
>
> > you'll have to get the trademark owners agreement to publish any rules
> > of his trademark like this.
> >
>
> >not sure what point you'
On Mon, 25 Nov 2024 17:01:47 -0500
Vittorio Giovara wrote:
> On Mon, Nov 25, 2024 at 4:52 PM compn wrote:
>
> > On Mon, 25 Nov 2024 14:27:13 -0500
> > Vittorio Giovara wrote:
> >
> > > +* To represent FFmpeg in any product, conference, or tradeshow, you m
g my
credibility. its awfully annoying.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
then start a thread about
coming up with a community trademark name. and what legal entity will
own said community trademark, which countries it will be registered in ,
etc.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.
On Mon, 25 Nov 2024 20:15:58 +0200
Rémi Denis-Courmont wrote:
> Le sunnuntaina 24. marraskuuta 2024, 22.51.08 EET compn a écrit :
> > a non-ff developer at vdd said i was "inactive for years".
>
> FWIW, while I do recall people criticising your answers in the FFmeg m
st popular format that i see on a
daily basis , just behind mkv. with support by default in
windows, mac/ios, android and web browsers, mov/mp4 is probably the #1
popular format in the world currently. testing and speeding up our
mov/mp4 demuxer is a good idea.
3
On Sat, 23 Nov 2024 06:35:57 +0100
Anton Khirnov wrote:
> At his own request, he can remove the entry whenever he likes.
if its his wish.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-de
On Sat, 23 Nov 2024 06:35:56 +0100
Anton Khirnov wrote:
> To be used at their own request, when they do not wish to receive vote
> emails.
good idea, i have not tested patch.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
fmpeg committers and part of the
community. it was a shock when someone asked who they were.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
rt. see the nightmares here https://samples.ffmpeg.org/mov/
if hurts, i wonder if buffer pools could be used only for specific high
bitrate codecs in mov demuxer?
not important just curious. nice job on the speedup!
-compn
___
ffmpeg-devel mailing list
ff
re)"
shouldnt it already be covered by another rule in the CoC?
specifying it out , and having the GA vote on it, will give the CC more
guidance for easier enforcement and less ambiguity.
thank you for your time.
-compn
diff --git a/doc/community.texi b/doc/community.texi
index 97a49f15e
any id3v2 vulnerabilities in so many software projects
over the years.
my suggestion/request is, if you do change id3v2, please
consider extensively security testing it before commit.
thanks
compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
h
On Thu, 21 Nov 2024 16:49:25 -0500
Vittorio Giovara wrote:
> On Thu, Nov 21, 2024 at 3:53 PM compn wrote:
>
> > On Thu, 21 Nov 2024 22:42:58 +0200
> > Rémi Denis-Courmont wrote:
> >
> > > Le torstaina 21. marraskuuta 2024, 22.34.42 EET compn a écrit :
&
On Thu, 21 Nov 2024 22:42:58 +0200
Rémi Denis-Courmont wrote:
> Le torstaina 21. marraskuuta 2024, 22.34.42 EET compn a écrit :
> > > Why does Michael need to ask the profession of an immediate colleague of
> > > his? How can he claim that the answer (or lack therof) is a
On Thu, 21 Nov 2024 20:43:22 +0200
Rémi Denis-Courmont wrote:
> Le torstaina 21. marraskuuta 2024, 17.19.57 EET compn a écrit :
> > > - Why is Michael asking what my profession is?
> >
> > Michael was asking your profession to find out if you administrate
>
On Thu, 21 Nov 2024 14:07:26 +0100
"J. Dekker" wrote:
> compn writes:
> These mails simply leave me confused:
My apologies. I was trying to clarify things but this mail I wrote was
so bad it only caused grief. It was not my intent and thats why I asked
people to ignore my m
On Wed, 20 Nov 2024 14:39:49 -0500
Vittorio Giovara wrote:
>I care about the process for using the ffmpeg name at a public event.
wouldnt any question of commercial use of the ffmpeg trademarked name
have to go through fabrice ?
i'm seriously asking, i dont know.
ontractual issue is not the same as legal issue.
>
what remi means is that any recording of the ffbooth will have to comply
with whatever recording rules that the venue and SCALE event has.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
On Tue, 19 Nov 2024 18:16:45 +0200
Rémi Denis-Courmont wrote:
> Le tiistaina 19. marraskuuta 2024, 5.18.52 EET compn a écrit :
> > Since no one mentioned it this time around, i'll repeat what was
> > said in the past. "ffmpeg" the name/trademark is not future
dont know more details, i just thought the script should be
documented and preserved from the ml if its useful.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above,
On Tue, 19 Nov 2024 14:03:51 +
Derek Buitenhuis wrote:
> On 11/12/2024 7:55 PM, compn wrote:
> > On Tue, 12 Nov 2024 16:46:42 +
> > Derek Buitenhuis wrote:
> >
> >> On 11/11/2024 7:34 PM, compn wrote:
> >>> one of my goals is to m
On Sat, 16 Nov 2024 10:12:13 -1000
compn wrote:
> Here is a list of things people want documented. gathered from
> previous emails and memories:
>
> 1. Complete list of infrastructure
> 2. where servers are hosted (see infra.txt, our Telepoint.bg host)
> 3. who has what ac
t had access before
>
> wm4
is wm4 still active? nothing since ~2018?
https://patchwork.ffmpeg.org/project/ffmpeg/list/?submitter=110
not on irc. no longer in mpv project either.
ugh i bet "active in last 5 years" is grim.
-compn
_
/software).
4. Who owns avcodec.org? Who runs these DNS servers? Who has access?
Who has contacts?
5. info on backup storage of mailing lists, servers, git repos etc
6. document the release tarball checksum patch in docs/website
thanks
-compn
___
ffmpeg
On Wed, 13 Nov 2024 10:44:29 -1000
compn wrote:
> the server admins know who has access. the access list isnt a public
> document. some developers want it to be a public document.
> i dont particularly care if the list is public or not.
>
> i am curious to know why this is now an
und it to the
> > nearest similar value.
>
> yes, it should do something better than just failing with a message
> that confuses the user
>
> also [fc#-1 @ 0x55b30de5f000] Error applying option 'in_v_chr_pos' to
> filter 'scale': Option not found and o
big binary blob in the repo.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
this mail might have come off angry, i didnt mean for this to be an
angry email.
can safely ignore this mail.
-compn
On Tue, 12 Nov 2024 12:51:23 -1000
compn wrote:
> are you talking about the same Josh who asked not to have their photo
> taken during vdd?
>
> you want a ro
rofession is, and have
no way of verifying who they are via photograph? and who says they
"worked on embedded devices across ... military sectors" (on the about
page of their website)?
thanks
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
On Tue, 12 Nov 2024 16:46:42 +
Derek Buitenhuis wrote:
> On 11/11/2024 7:34 PM, compn wrote:
> > if your goal is to post old quotes, thats cool.
>
> Woosh.
the quotes are from michael in 2015 saying elect a new leader. pretty
sure we never elected one.
feel free
s at a dinner ? thats your level of
security?
its fine, i'm just curious.
(you'd think korea would have superior anti-mosquito technology by now)
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo
On Tue, 12 Nov 2024 10:00:56 +
Kieran Kunhya via ffmpeg-devel wrote:
> On Tue, 12 Nov 2024, 04:07 compn, wrote:
>
> > haven't seen arpi in a while so remove his root authorized key +
> > remove him from maintainers. maybe he'll come back?
> >
> >
haven't seen arpi in a while so remove his root authorized key + remove
him from maintainers. maybe he'll come back?
anyone know how to contact tim nicholson? his mails are
bouncing. https://uk.linkedin.com/in/tim-nicholson-7a2a3963
-compn
diff --git a/MAINTAINERS b/MAINTAINERS
index
On Mon, 11 Nov 2024 18:17:11 +
Kieran Kunhya via ffmpeg-devel wrote:
> On Mon, Nov 11, 2024 at 5:31 PM compn wrote:
> >
> > what is your goal?
> >
> > thanks
> > -compn
>
> Here are some quotes presented without comment:
if your goal is to post o
nsider, should they not
like our bulgarian host.
if your goal is to endlessly argue , well thats ok too.
what is your goal?
thanks
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsu
>
> "A 94x speed improvement demonstrated using handwritten assembly"
are you trying to say that ffmpeg should take down the tweet?
well you can come on #ffmpeg-devel irc too, if you dont like twitter.
-compn
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
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:
&
1 - 100 of 349 matches
Mail list logo
