Re: [FFmpeg-devel] Next developer meeting

2020-12-05 Thread Jean-Baptiste Kempf
On Thu, 3 Dec 2020, at 21:50, Thilo Borgmann wrote:
> no more replies against, so we shift the time to 15:00 UTC (7:00 US West, 
> 16:00 
> Berlin/London/Paris, 23:00 Peking).
> 
> Happening at #ffmpeg-meeting.

This is in 1 hour, now.

-- 
Jean-Baptiste Kempf -  President
+33 672 704 734
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-12-03 Thread Thilo Borgmann

Hi,


we haven't had a meeting for quite some time and are beyond schedule anyway. So 
I'd propose having another developer meeting before end of year.

Please give your preferences for a date here:
https://framadate.org/g1FPmOpfEz9mSLg9


one week later, we have settled for having the FFDev meeting on

Saturday, Dec 5th.

Based on last time, I told we aim for 17 UTC for the vote. Steven made some 
comments I don't fully understand...

If someone want to shift it, please propose a better time. An overview might be:
https://www.timeanddate.de/zeitzonen/konferenz?iso=20201205&p1=224&p2=37&p3=33

What about shift to  16 UTC?
Because it’s 01:00:00 AM in Peking if aim 17 UTC. :D




I've got it even worse, 1700 UTC is 3AM for me (Australia, UTC+10). Shifting 
back even further
to 1300/1400 UTC (11pm/12am) would be greatly appreciated (if even possible).

Not only no problem but also feel happy in Peking. Haha :D


If there's no US comment about too early bird for them...?


no more replies against, so we shift the time to 15:00 UTC (7:00 US West, 16:00 
Berlin/London/Paris, 23:00 Peking).


Happening at #ffmpeg-meeting.

-Thilo
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-19 Thread Thilo Borgmann
Am 19.11.20 um 06:01 schrieb Steven Liu:
> 
> 
>> 2020年11月19日 下午12:05,Zane van Iperen  写道:
>>
>>
>>
>> On 19/11/20 1:46 pm, Steven Liu wrote:
 2020年11月18日 下午8:59,Thilo Borgmann  写道:

 Hi,

> we haven't had a meeting for quite some time and are beyond schedule 
> anyway. So I'd propose having another developer meeting before end of 
> year.
>
> Please give your preferences for a date here:
> https://framadate.org/g1FPmOpfEz9mSLg9

 one week later, we have settled for having the FFDev meeting on

 Saturday, Dec 5th.

 Based on last time, I told we aim for 17 UTC for the vote. Steven made 
 some comments I don't fully understand...

 If someone want to shift it, please propose a better time. An overview 
 might be:
 https://www.timeanddate.de/zeitzonen/konferenz?iso=20201205&p1=224&p2=37&p3=33
>>> What about shift to  16 UTC?
>>> Because it’s 01:00:00 AM in Peking if aim 17 UTC. :D

>>
>> I've got it even worse, 1700 UTC is 3AM for me (Australia, UTC+10). Shifting 
>> back even further
>> to 1300/1400 UTC (11pm/12am) would be greatly appreciated (if even possible).
> Not only no problem but also feel happy in Peking. Haha :D

If there's no US comment about too early bird for them...?

-Thilo
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-18 Thread Steven Liu


> 2020年11月19日 下午12:05,Zane van Iperen  写道:
> 
> 
> 
> On 19/11/20 1:46 pm, Steven Liu wrote:
>>> 2020年11月18日 下午8:59,Thilo Borgmann  写道:
>>> 
>>> Hi,
>>> 
 we haven't had a meeting for quite some time and are beyond schedule 
 anyway. So I'd propose having another developer meeting before end of year.
 
 Please give your preferences for a date here:
 https://framadate.org/g1FPmOpfEz9mSLg9
>>> 
>>> one week later, we have settled for having the FFDev meeting on
>>> 
>>> Saturday, Dec 5th.
>>> 
>>> Based on last time, I told we aim for 17 UTC for the vote. Steven made some 
>>> comments I don't fully understand...
>>> 
>>> If someone want to shift it, please propose a better time. An overview 
>>> might be:
>>> https://www.timeanddate.de/zeitzonen/konferenz?iso=20201205&p1=224&p2=37&p3=33
>> What about shift to  16 UTC?
>> Because it’s 01:00:00 AM in Peking if aim 17 UTC. :D
>>> 
> 
> I've got it even worse, 1700 UTC is 3AM for me (Australia, UTC+10). Shifting 
> back even further
> to 1300/1400 UTC (11pm/12am) would be greatly appreciated (if even possible).
Not only no problem but also feel happy in Peking. Haha :D

> 
> Zane
> ___
> 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".

Thanks

Steven Liu



___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-18 Thread Zane van Iperen



On 19/11/20 1:46 pm, Steven Liu wrote:




2020年11月18日 下午8:59,Thilo Borgmann  写道:

Hi,


we haven't had a meeting for quite some time and are beyond schedule anyway. So 
I'd propose having another developer meeting before end of year.

Please give your preferences for a date here:
https://framadate.org/g1FPmOpfEz9mSLg9


one week later, we have settled for having the FFDev meeting on

Saturday, Dec 5th.

Based on last time, I told we aim for 17 UTC for the vote. Steven made some 
comments I don't fully understand...

If someone want to shift it, please propose a better time. An overview might be:
https://www.timeanddate.de/zeitzonen/konferenz?iso=20201205&p1=224&p2=37&p3=33

What about shift to  16 UTC?
Because it’s 01:00:00 AM in Peking if aim 17 UTC. :D




I've got it even worse, 1700 UTC is 3AM for me (Australia, UTC+10). Shifting 
back even further
to 1300/1400 UTC (11pm/12am) would be greatly appreciated (if even possible).

Zane
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-18 Thread Steven Liu


> 2020年11月18日 下午8:59,Thilo Borgmann  写道:
> 
> Hi,
> 
>> we haven't had a meeting for quite some time and are beyond schedule anyway. 
>> So I'd propose having another developer meeting before end of year.
>> 
>> Please give your preferences for a date here:
>> https://framadate.org/g1FPmOpfEz9mSLg9
> 
> one week later, we have settled for having the FFDev meeting on 
> 
> Saturday, Dec 5th.
> 
> Based on last time, I told we aim for 17 UTC for the vote. Steven made some 
> comments I don't fully understand...
> 
> If someone want to shift it, please propose a better time. An overview might 
> be:
> https://www.timeanddate.de/zeitzonen/konferenz?iso=20201205&p1=224&p2=37&p3=33
What about shift to  16 UTC?
Because it’s 01:00:00 AM in Peking if aim 17 UTC. :D
> 
> 
>> Current agenda proposals, feel free to add to it:
>> 
>> - Tech / Comm committees how-to in practice
>> - GSoC adaptations for upcoming years
>> - splitting libraries (lavf->lavio)
>> - writing down development rules
>> - switching to a merge request-like system
>> - ...
> 
> 
> -Thilo
> ___
> 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".

Thanks

Steven Liu



___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-18 Thread Thilo Borgmann
Hi,

> we haven't had a meeting for quite some time and are beyond schedule anyway. 
> So I'd propose having another developer meeting before end of year.
> 
> Please give your preferences for a date here:
> https://framadate.org/g1FPmOpfEz9mSLg9

one week later, we have settled for having the FFDev meeting on 

Saturday, Dec 5th.

Based on last time, I told we aim for 17 UTC for the vote. Steven made some 
comments I don't fully understand...

If someone want to shift it, please propose a better time. An overview might be:
https://www.timeanddate.de/zeitzonen/konferenz?iso=20201205&p1=224&p2=37&p3=33


> Current agenda proposals, feel free to add to it:
> 
> - Tech / Comm committees how-to in practice
> - GSoC adaptations for upcoming years
> - splitting libraries (lavf->lavio)
> - writing down development rules
> - switching to a merge request-like system
> - ...


-Thilo
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-12 Thread Nicolas George
Ronald S. Bultje (12020-11-11):
> > Also, I believe it would be good for us internally, since it would
> > - allow other libraries to do IO cleanly without depending on lavf
> > - force us to clean up avio public API, which is not in a great shape
> 
> Avio public API would be great, regardless of library split. Certain
> companies using ffmpeg in their transcoding system want only their own I/O.

We completely can decide to clean up the public API without splitting
any library. And I completely agree, this would be an excellent and
useful task.

> I doubt they care much for the binary size saved from not linking to lavio,
> but stable public API is important.

Anyway, any project that cares about the binary size will not rely on
pre-built FFmpeg, they will build their own. That is why splitting the
libraries is useless in that regard: the ability to disable components
gives the same benefits, but more and better.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Ronald S. Bultje
Hi,

On Wed, Nov 11, 2020 at 10:45 AM Anton Khirnov  wrote:

> Quoting James Almer (2020-11-11 14:13:07)
> > I don't recall anything about splitting IO, but what does it achieve
> > beyond making lavf lighter? Are there users out there that could care
> > about linking to an hypothetical lavio while not caring about other lavf
> > functionality?
>
> Yes, I recall several people expressing interest in a separate libavio.
>
> Also, I believe it would be good for us internally, since it would
> - allow other libraries to do IO cleanly without depending on lavf
> - force us to clean up avio public API, which is not in a great shape


Avio public API would be great, regardless of library split. Certain
companies using ffmpeg in their transcoding system want only their own I/O.
I doubt they care much for the binary size saved from not linking to lavio,
but stable public API is important.

Ronald
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Lynne
Nov 11, 2020, 12:20 by thilo.borgm...@mail.de:

> Hi,
>
> we haven't had a meeting for quite some time and are beyond schedule anyway. 
> So I'd propose having another developer meeting before end of year.
>
> Please give your preferences for a date here:
> https://framadate.org/g1FPmOpfEz9mSLg9
>
> Current agenda proposals, feel free to add to it:
>
> - Tech / Comm committees how-to in practice
> - GSoC adaptations for upcoming years
> - splitting libraries (lavf->lavio)
> - writing down development rules
> - switching to a merge request-like system
>
This x1000.
The volume of ML emails is too much ATM for me to reading everything.


> - ...
>

SWS rewrite, and a concat bsf?
Also porting dav1d's codebase?
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Paul B Mahol
Absolutely disagree, please leave.

On Wed, Nov 11, 2020 at 5:21 PM Nicolas George  wrote:

> Vittorio Giovara (12020-11-11):
> > Sounds like a good topic to discuss at a developer meeting!
>
> No, that's precisely not, this is the kind of topic that needs
> paragraphs, not lines.
>
> Regards,
>
> --
>   Nicolas George
> ___
> 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".
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Nicolas George
Vittorio Giovara (12020-11-11):
> Sounds like a good topic to discuss at a developer meeting!

No, that's precisely not, this is the kind of topic that needs
paragraphs, not lines.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Vittorio Giovara
On Wed, Nov 11, 2020 at 4:52 PM Nicolas George  wrote:

> Anton Khirnov (12020-11-11):
> > I gave you arguments last time this was discussed. You keep ignoring
> > them,
>
> I did not ignore them, I replied to them, by pointing to you that there
> are better ways to achieve the things in your arguments.
>

Sounds like a good topic to discuss at a developer meeting!

my 2 cents: 👍 higher level api 👎 libffmpeg.so
-- 
Vittorio
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Carl Eugen Hoyos
Am Mi., 11. Nov. 2020 um 16:49 Uhr schrieb Anton Khirnov :

> I gave you arguments last time this was discussed. You keep ignoring
> them, because presumably you are the sole arbiter of what is actual and
> practical.

I am not convinced that you are in an ideal position for personal attacks.

Carl Eugen
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Nicolas George
Anton Khirnov (12020-11-11):
> I gave you arguments last time this was discussed. You keep ignoring
> them,

I did not ignore them, I replied to them, by pointing to you that there
are better ways to achieve the things in your arguments.

>   because presumably you are the sole arbiter of what is actual and
> practical.

This was ad-hominem. I understand the frustration, but please realize
that I feel the same frustration at your ignoring of my arguments.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Anton Khirnov
Quoting Nicolas George (2020-11-11 15:05:35)
> What about the people who want to keep the libs separate give actual
> practical arguments?

I gave you arguments last time this was discussed. You keep ignoring
them, because presumably you are the sole arbiter of what is actual and
practical.

I am not especially motivated to spend my time repeating the same
arguments that you ignore.

-- 
Anton Khirnov
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Anton Khirnov
Quoting James Almer (2020-11-11 14:13:07)
> On 11/11/2020 10:05 AM, Thilo Borgmann wrote:
> > Am 11.11.20 um 14:04 schrieb Thilo Borgmann:
> >> Am 11.11.20 um 13:01 schrieb Steven Liu:
> >>> Thilo Borgmann  于2020年11月11日周三 下午7:20写道:
> 
>  Hi,
> 
>  we haven't had a meeting for quite some time and are beyond schedule 
>  anyway. So I'd propose having another developer meeting before end of 
>  year.
> 
>  Please give your preferences for a date here:
>  https://framadate.org/g1FPmOpfEz9mSLg9
> 
>  Current agenda proposals, feel free to add to it:
> 
>  - Tech / Comm committees how-to in practice
>  - GSoC adaptations for upcoming years
> >>
>  - splitting libraries (lavf->lavio)
> >>> Need more introduce for this line, libavformat and libavio ?
> >>
> >> AFAICT i/o operations shall not be separated from lavformat. If I 
> >> understood it correctly.
> > 
> > ... shall BE sepearated...
> 
> What i know we were discussing was to merge lavd into lavf, since their 
> current dependency state is pretty hacky and makes development and 
> extension of certain lavf public structs a pain.
> It's why i didn't apply my iterate api set just yet.

When this topic last came up, it seemed that nobody disagrees about
merging lavd into lavf, so I am currently working on it. Patches soon.

> 
> I don't recall anything about splitting IO, but what does it achieve 
> beyond making lavf lighter? Are there users out there that could care 
> about linking to an hypothetical lavio while not caring about other lavf 
> functionality?

Yes, I recall several people expressing interest in a separate libavio.

Also, I believe it would be good for us internally, since it would
- allow other libraries to do IO cleanly without depending on lavf
- force us to clean up avio public API, which is not in a great shape

-- 
Anton Khirnov
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Kieran Kunhya
On Wed, 11 Nov 2020 at 11:20, Thilo Borgmann  wrote:

> Current agenda proposals, feel free to add to it:
>

I would like to propose FFmpeg/SPI purchase a Mac Mini ARM machine for
development (and FATE if required).
Obviously this will be an important platform in the coming years.

Kieran
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Nicolas George
Steven Liu (12020-11-11):
> What about make and option in configure and let the option be choosed by 
> users?

It is the worst of the two options combined, with extra drawbacks: we
still have to deal with all the avpriv nonsense, and we get to maintain
both systems.

What about the people who want to keep the libs separate give actual
practical arguments?

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Steven Liu
Steven Liu  于2020年11月11日周三 下午9:29写道:
>
> Nicolas George  于2020年11月11日周三 下午9:20写道:
> >
> > James Almer (12020-11-11):
> > > What i know we were discussing was to merge lavd into lavf, since their
> > > current dependency state is pretty hacky and makes development and 
> > > extension
> > > of certain lavf public structs a pain.
> > > It's why i didn't apply my iterate api set just yet.
> > >
> > > I don't recall anything about splitting IO, but what does it achieve 
> > > beyond
> > > making lavf lighter? Are there users out there that could care about 
> > > linking
> > > to an hypothetical lavio while not caring about other lavf functionality?
> >
> > Well, I think by now everybody knows what I think of the splitting of
> > the libraries (we should move towards a single libffmpeg.so,
> Yes, merge libs to libffmpeg.so or libffmpeg.a is very convenient to
> mobile developing,
> for example only link one lib is ok.
> we merge libs to libffmpeg.so by outselves now, and i saw ijkplayer do
> it so too.

What about make and option in configure and let the option be choosed by users?
> > else makes our work more complicated for no practical benefit that could
> > be achieved another simpler way).
> >
> > But I would like to add:
> >
> > This is a tricky technical discussion. Arguing it properly requires time
> > to state things clearly and to gather arguments. A developer meeting in
> > real-time chat is absolutely not the place for it. It can be the place
> > to finish the discussion if necessary, but not the place to lead the
> > bulk of it.
> >
> > In fact, nothing should be on a developers meeting agenda that has not
> > already been extensively discussed on the list.
> >
> > Regards,
> >
> > --
> >   Nicolas George
> Thanks
> Steven
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Jean-Baptiste Kempf
On Wed, 11 Nov 2020, at 14:20, Nicolas George wrote:
> In fact, nothing should be on a developers meeting agenda that has not
> already been extensively discussed on the list.

Absolutely totally disagree.

A meeting is here to discuss about things. Including things not on the agenda. 
By discussing, you have more ideas.
That's why literally every non-profit/open-source meetings has open questions 
at the end.
Discussing by voice is very different than by mail, and is very much faster to 
get a roughly consensus/idea/direction, and shut down ideas that noone shares.

As we're not voting in those meetings, agenda can be and should be flexible.
--
Jean-Baptiste Kempf -  President
+33 672 704 734
 

___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Steven Liu
Nicolas George  于2020年11月11日周三 下午9:20写道:
>
> James Almer (12020-11-11):
> > What i know we were discussing was to merge lavd into lavf, since their
> > current dependency state is pretty hacky and makes development and extension
> > of certain lavf public structs a pain.
> > It's why i didn't apply my iterate api set just yet.
> >
> > I don't recall anything about splitting IO, but what does it achieve beyond
> > making lavf lighter? Are there users out there that could care about linking
> > to an hypothetical lavio while not caring about other lavf functionality?
>
> Well, I think by now everybody knows what I think of the splitting of
> the libraries (we should move towards a single libffmpeg.so,
Yes, merge libs to libffmpeg.so or libffmpeg.a is very convenient to
mobile developing,
for example only link one lib is ok.
we merge libs to libffmpeg.so by outselves now, and i saw ijkplayer do
it so too.
> else makes our work more complicated for no practical benefit that could
> be achieved another simpler way).
>
> But I would like to add:
>
> This is a tricky technical discussion. Arguing it properly requires time
> to state things clearly and to gather arguments. A developer meeting in
> real-time chat is absolutely not the place for it. It can be the place
> to finish the discussion if necessary, but not the place to lead the
> bulk of it.
>
> In fact, nothing should be on a developers meeting agenda that has not
> already been extensively discussed on the list.
>
> Regards,
>
> --
>   Nicolas George
Thanks
Steven
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Nicolas George
James Almer (12020-11-11):
> What i know we were discussing was to merge lavd into lavf, since their
> current dependency state is pretty hacky and makes development and extension
> of certain lavf public structs a pain.
> It's why i didn't apply my iterate api set just yet.
> 
> I don't recall anything about splitting IO, but what does it achieve beyond
> making lavf lighter? Are there users out there that could care about linking
> to an hypothetical lavio while not caring about other lavf functionality?

Well, I think by now everybody knows what I think of the splitting of
the libraries (we should move towards a single libffmpeg.so, anything
else makes our work more complicated for no practical benefit that could
be achieved another simpler way).

But I would like to add:

This is a tricky technical discussion. Arguing it properly requires time
to state things clearly and to gather arguments. A developer meeting in
real-time chat is absolutely not the place for it. It can be the place
to finish the discussion if necessary, but not the place to lead the
bulk of it.

In fact, nothing should be on a developers meeting agenda that has not
already been extensively discussed on the list.

Regards,

-- 
  Nicolas George


signature.asc
Description: PGP signature
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Thilo Borgmann
Am 11.11.20 um 14:13 schrieb James Almer:
> On 11/11/2020 10:05 AM, Thilo Borgmann wrote:
>> Am 11.11.20 um 14:04 schrieb Thilo Borgmann:
>>> Am 11.11.20 um 13:01 schrieb Steven Liu:
 Thilo Borgmann  于2020年11月11日周三 下午7:20写道:
>
> Hi,
>
> we haven't had a meeting for quite some time and are beyond schedule 
> anyway. So I'd propose having another developer meeting before end of 
> year.
>
> Please give your preferences for a date here:
> https://framadate.org/g1FPmOpfEz9mSLg9
>
> Current agenda proposals, feel free to add to it:
>
> - Tech / Comm committees how-to in practice
> - GSoC adaptations for upcoming years
>>>
> - splitting libraries (lavf->lavio)
 Need more introduce for this line, libavformat and libavio ?
>>>
>>> AFAICT i/o operations shall not be separated from lavformat. If I 
>>> understood it correctly.
>>
>> ... shall BE sepearated...
> 
> What i know we were discussing was to merge lavd into lavf, since their 
> current dependency state is pretty hacky and makes development and extension 
> of certain lavf public structs a pain.
> It's why i didn't apply my iterate api set just yet.
> 
> I don't recall anything about splitting IO, but what does it achieve beyond 
> making lavf lighter? Are there users out there that could care about linking 
> to an hypothetical lavio while not caring about other lavf functionality?

I can't tell, just listing the input I got.


> - writing down development rules
> - switching to a merge request-like system
> - ...
>>>
>>> -Thilo
>>> ___
>>> 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".
>>>
>>
>> ___
>> 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".
>>
> 
> ___
> 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".

___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread James Almer

On 11/11/2020 10:05 AM, Thilo Borgmann wrote:

Am 11.11.20 um 14:04 schrieb Thilo Borgmann:

Am 11.11.20 um 13:01 schrieb Steven Liu:

Thilo Borgmann  于2020年11月11日周三 下午7:20写道:


Hi,

we haven't had a meeting for quite some time and are beyond schedule anyway. So 
I'd propose having another developer meeting before end of year.

Please give your preferences for a date here:
https://framadate.org/g1FPmOpfEz9mSLg9

Current agenda proposals, feel free to add to it:

- Tech / Comm committees how-to in practice
- GSoC adaptations for upcoming years



- splitting libraries (lavf->lavio)

Need more introduce for this line, libavformat and libavio ?


AFAICT i/o operations shall not be separated from lavformat. If I understood it 
correctly.


... shall BE sepearated...


What i know we were discussing was to merge lavd into lavf, since their 
current dependency state is pretty hacky and makes development and 
extension of certain lavf public structs a pain.

It's why i didn't apply my iterate api set just yet.

I don't recall anything about splitting IO, but what does it achieve 
beyond making lavf lighter? Are there users out there that could care 
about linking to an hypothetical lavio while not caring about other lavf 
functionality?







- writing down development rules
- switching to a merge request-like system
- ...


-Thilo
___
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".



___
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".



___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Thilo Borgmann
Am 11.11.20 um 14:04 schrieb Thilo Borgmann:
> Am 11.11.20 um 13:01 schrieb Steven Liu:
>> Thilo Borgmann  于2020年11月11日周三 下午7:20写道:
>>>
>>> Hi,
>>>
>>> we haven't had a meeting for quite some time and are beyond schedule 
>>> anyway. So I'd propose having another developer meeting before end of year.
>>>
>>> Please give your preferences for a date here:
>>> https://framadate.org/g1FPmOpfEz9mSLg9
>>>
>>> Current agenda proposals, feel free to add to it:
>>>
>>> - Tech / Comm committees how-to in practice
>>> - GSoC adaptations for upcoming years
> 
>>> - splitting libraries (lavf->lavio)
>> Need more introduce for this line, libavformat and libavio ?
> 
> AFAICT i/o operations shall not be separated from lavformat. If I understood 
> it correctly.

... shall BE sepearated...



>>> - writing down development rules
>>> - switching to a merge request-like system
>>> - ...
> 
> -Thilo
> ___
> 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".
> 

___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Thilo Borgmann
Am 11.11.20 um 13:01 schrieb Steven Liu:
> Thilo Borgmann  于2020年11月11日周三 下午7:20写道:
>>
>> Hi,
>>
>> we haven't had a meeting for quite some time and are beyond schedule anyway. 
>> So I'd propose having another developer meeting before end of year.
>>
>> Please give your preferences for a date here:
>> https://framadate.org/g1FPmOpfEz9mSLg9
>>
>> Current agenda proposals, feel free to add to it:
>>
>> - Tech / Comm committees how-to in practice
>> - GSoC adaptations for upcoming years

>> - splitting libraries (lavf->lavio)
> Need more introduce for this line, libavformat and libavio ?

AFAICT i/o operations shall not be separated from lavformat. If I understood it 
correctly.


>> - writing down development rules
>> - switching to a merge request-like system
>> - ...

-Thilo
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Paul B Mahol
On Wed, Nov 11, 2020 at 1:08 PM Steven Liu  wrote:

> Thilo Borgmann  于2020年11月11日周三 下午7:20写道:
> >
> > Hi,
> >
> > we haven't had a meeting for quite some time and are beyond schedule
> anyway. So I'd propose having another developer meeting before end of year.
> >
> > Please give your preferences for a date here:
> > https://framadate.org/g1FPmOpfEz9mSLg9
> >
> > Current agenda proposals, feel free to add to it:
> >
> > - Tech / Comm committees how-to in practice
> > - GSoC adaptations for upcoming years
> > - splitting libraries (lavf->lavio)
> Need more introduce for this line, libavformat and libavio ?
>
>
No split of libraries will happen. Only merges may happen.


> > - writing down development rules
> > - switching to a merge request-like system
> > - ...
> >
> > Thx,
> > Thilo
> > ___
> > 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".
> ___
> 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".
___
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".

Re: [FFmpeg-devel] Next developer meeting

2020-11-11 Thread Steven Liu
Thilo Borgmann  于2020年11月11日周三 下午7:20写道:
>
> Hi,
>
> we haven't had a meeting for quite some time and are beyond schedule anyway. 
> So I'd propose having another developer meeting before end of year.
>
> Please give your preferences for a date here:
> https://framadate.org/g1FPmOpfEz9mSLg9
>
> Current agenda proposals, feel free to add to it:
>
> - Tech / Comm committees how-to in practice
> - GSoC adaptations for upcoming years
> - splitting libraries (lavf->lavio)
Need more introduce for this line, libavformat and libavio ?

> - writing down development rules
> - switching to a merge request-like system
> - ...
>
> Thx,
> Thilo
> ___
> 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".
___
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".

Re: [FFmpeg-devel] Next developer meeting...

2019-12-09 Thread Jean-Baptiste Kempf
On Thu, Dec 5, 2019, at 00:22, Jean-Baptiste Kempf wrote:
> will do our next meeting, Monday 9 December 2019, at 17:00 
> Berlin/Paris/Brussels time.
> 
> The time is selected so that people in China and in South America can join us.
> 
> It will be online, with live comments/discussion on IRC.

See you soon on #ffmpeg-meeting on freenode.

-- 
Jean-Baptiste Kempf -  President
+33 672 704 734
___
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".