September 27, 2021 9:04 PM, "James Almer" wrote:
> Signed-off-by: James Almer
> ---
> tests/fate/checkasm.mak | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/fate/checkasm.mak b/tests/fate/checkasm.mak
> index cec6d28286..6e7edbe655 100644
> --- a/tests/fate/checkasm.mak
> +++
September 12, 2021 1:15 PM, "Jean-Baptiste Kempf" wrote:
> Hello folks,
>
> This is a topic that has come regularly on the table, in various discussions
> in the community, in
> IRL, on IRC and on the mailing list; but also when talking with downstreams
> applications and
> distributions...
>
These are some cosmetic changes and also priming the decoder for sprite
support (which i plan on adding). This patch was mainly for me to get
used to the git email patch flow, if anything. Of course the decoder
still works as it was before (i tested it).
---
libavcodec/truemotion1.c | 41 +
On 2021-07-10 03:42, Lynne wrote:
This doesn't move the pointer back to the file end if par->block_align
is set.
I think that's fine though, since the function writes the trailer,
which should
mean that nothing more needs to be written.
Patch LGTM. But please, someone yell at Apple to support O
On 2021-07-10 15:20, Paul B Mahol wrote:
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 60 ++
libavfilter/Makefile |1 +
libavfilter/af_afwtdn.c | 1349 ++
libavfilter/allfilters.c |1 +
4 files changed, 1411 insertions(+)
create
On 2021-07-04 17:58, ffmpegandmahanstreamer@lolcow.email wrote:
These are some cosmetic changes and also priming the decoder for
sprite support (which i plan on adding). This patch was mainly for me
to get used to the git email patch flow, if anything. Of course the
decoder still works as it was
On 2021-07-14 09:17, Derek Buitenhuis wrote:
On 7/14/2021 12:27 PM, Nicolas George wrote:
Looking at the headers, it looks like the delay happens at Google
before
the mail arrives to the mailing-list.
Yours arrived quickly. Mine will too, I guess.
Sending from GMail, I have had anywhere from
On 2021-07-14 09:43, Derek Buitenhuis wrote:
On 7/14/2021 2:35 PM, ffmpegandmahanstreamer@lolcow.email wrote:
I have been bringing this up consstently for years, and been told
it's
a "non-issue", but it is incredibly annoying.
I am not sure if it's due to Google having iss
On 2021-07-14 14:55, Nicolas George wrote:
ffmpegandmahanstreamer@lolcow.email (12021-07-14):
I'm not against fixing the mailing list. No, not at all. It need to be
fixed. But Google is big company and trying to figure out how to make
their
mail deliver successfully might be a proble
On 2021-07-14 14:51, Michael Niedermayer wrote:
Signed-off-by: Michael Niedermayer
---
htdocs/robots.txt | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/htdocs/robots.txt b/htdocs/robots.txt
index eb05362..4bbc395 100644
--- a/htdocs/robots.txt
+++ b/htdocs/rob
This adds the Reddit subreddit to the forum section. It has over 7000
participants. Many of the developers on here, like Gyan and Paul,
participate on there already. I also think Gyan is the moderator of that
subreddit as well. And reddit is more popular than superuser.
---
src/contact | 3 +++
to"), I have decided to
make the switch. I also looked into the person behind the cow service
and he has been involved in some less than trustworthy things
that's beyond the scope of this mailing list.
On 2021-07-14 14:55, Nicolas George wrote:
ffmpegandmahanstreamer@lolc
Put the fact that -re is equivalent to -readrate 1 in the deprecated message so
people know what to switch to.
Other than that looks good to me.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To u
TrueMotion v1 decoder presently only decodes 16-bit TM1 data and
- * outputs RGB555 (or RGB565) data. 24-bit TM1 data is not supported yet.
+ * The TrueMotion v1 decoder presently decodes 16-bit/24-bit TM1 data and
+ * outputs RGB555 (or RGB565) data.
+ * ffmpegandmahanstreamer@e.email: added sprite
v1 decoder presently only decodes 16-bit TM1 data and
>> - * outputs RGB555 (or RGB565) data. 24-bit TM1 data is not supported yet.
>> + * The TrueMotion v1 decoder presently decodes 16-bit/24-bit TM1 data and
>> + * outputs RGB555 (or RGB565) data.
>> + * ffmpegandmahanstrea
Well obviously i'm not committer yet or responsible for this but I think its a
good idea for Lynne to get the hardware she needs. Price looks reasonable, I
would give the goahead.
July 28, 2021 7:07 PM, "Lynne" wrote:
> 9 Jul 2021, 12:59 by d...@lynne.ee:
>
>> 8 Jul 2021, 22:32 by stefa...@gm
I always meant to ask what is meaning of your profile picture?
July 28, 2021 6:51 PM, "Derek Buitenhuis" wrote:
> On 7/27/2021 2:08 PM, James Almer wrote:
>
>> Since we can't blindly trust the keyframe flag in packets and assume its
>> contents are a valid Sync Sample, do some basic bitstream p
B
U
M
P
so i can submit new patches
July 22, 2021 4:27 PM, ffmpegandmahanstreamer@e.email wrote:
> Overrides previous patch i submitted regarding this as the old patch I
> submitted had a bug that is
> fixed in this one.
>
> ---
> libavcodec/t
July 31, 2021 8:25 AM, "Andreas Rheinhardt"
wrote:
> ffmpegandmahanstreamer@e.email:
>
>> Overrides previous patch i submitted regarding this as the old patch I
>> submitted had a bug that is
>> fixed in this one.
>
> This is not an acceptable comm
two or three sentences
while others just have one sentence.
How much do you want me to write? There's not much to it.
July 31, 2021 10:01 AM, "Nicolas George" wrote:
> ffmpegandmahanstreamer@e.email (12021-07-31):
>
>> In my next patch how about "This
Per Andreas Rheinhardt request i'm splitting the working patches in two.
---
This cleans up the code in the decode24bit and decode16bit functions by putting
it in way that expresses the true intent while making it easier to read.
libavcodec/truemotion1.c | 36
.
+ * ffmpegandmahanstreamer@e.email: added sprite support 7/22/21
*/
#include
@@ -56,9 +57,15 @@ typedef struct TrueMotion1Context {
int flags;
int x, y, w, h;
+
+int xoffset;
+int yoffset;
+int spritew;
+int spriteh;
uint32_t y_predictor_table[1024
lgtm after you fix nitpick about if statements in my opinon
August 1, 2021 10:54 AM, "Nachiket Tarate"
wrote:
> Apple HTTP Live Streaming Sample Encryption:
>
> https://developer.apple.com/library/ios/documentation/AudioVideo/Conceptual/HLS_Sample_Encryption
>
> Signed-off-by: Nachiket Tarate
hello PAUL.
August 1, 2021 10:21 AM, "Paul B Mahol" wrote:
> Signed-off-by: Paul B Mahol
> ---
> doc/filters.texi | 31
> libavfilter/Makefile | 2 +
> libavfilter/allfilters.c | 2 +
> libavfilter/f_separate.c | 346 +++
> 4 files changed, 381 insertions(+)
August 1, 2021 1:01 PM, "Nicolas George" wrote:
> Paul B Mahol (12021-08-01):
>
>> Signed-off-by: Paul B Mahol
>> ---
>> doc/filters.texi | 31
>> libavfilter/Makefile | 2 +
>> libavfilter/allfilters.c | 2 +
>> libavfilter/f_separate.c | 346 +++
>> 4 file
August 1, 2021 1:06 PM, "Nicolas George" wrote:
> ffmpegandmahanstreamer@e.email (12021-08-01):
>
>> Seperate is best word
>
> No, it is not, I have explained why. Chemists separate. Do you have
> arguments?
>
https://www.merriam-webster.com/dictionary/separa
August 1, 2021 1:11 PM, "Nicolas George" wrote:
> ffmpegandmahanstreamer@e.email (12021-08-01):
>
>> https://www.merriam-webster.com/dictionary/separateDefinition of separate
>> (Entry 1 of 3)
>> transitive verb
>>
>> 1a: to set or keep apart : DI
Have you checked the mailing list archives? Maybe its slow to get to others but
fast to get on the ML.
Regardless, maybe its just a gmail problem. The multiple (non Gmail) providers
ive been using/have used all work even faster than gmail. I think Nicolas Lynne
and Niedermayer along with Kieran
August 2, 2021 5:57 PM, "Derek Buitenhuis" wrote:
> On 8/2/2021 10:48 PM, ffmpegandmahanstreamer@e.email wrote:
>
>> Have you checked the mailing list archives? Maybe its slow to get to others
>> but fast to get on the
>> ML.
>
> No, it is not. It&#
August 3, 2021 10:07 AM, "Sergio M. Ammirata, Ph.D."
wrote:
> PES packet with too much padding trigger unlimited error
> messages "PES packet size mismatch" because the code that
> corrects the length is wrong.
> Here is a sample file: http://99.93.62.129/smpte2038.ts
> PID 300 is the one trigge
August 4, 2021 11:17 AM, "Derek Buitenhuis" wrote:
> On 8/3/2021 11:59 PM, Michael Niedermayer wrote:
>
>> somehow this reads a bit offensive to me, iam not sure its meant to
>
> It's not meant as an attack towards you pesonally, but rather to point out
> the absurdity of the situation:
>
> *
August 6, 2021 7:20 AM, "Michael Niedermayer" wrote:
> On Wed, Aug 04, 2021 at 11:28:19PM +0100, Derek Buitenhuis wrote:
>
>> On 8/4/2021 11:03 PM, Michael Niedermayer wrote:
>>
>> * There is no public documentation on:
>> * Who owns the physical infra.
>>
>> its all donated one way or another
August 10, 2021 10:37 AM, "Soft Works" wrote:
> Hi,
>
> A while ago there was a discussion about moving forward and
> migrating the ffmpeg development process from the mailing list to
> another platform (like GitLab).
> That discussion had died without further results and an important
> takea
E.email comes with this capability built in.
August 10, 2021 10:02 AM, "Michael Niedermayer" wrote:
> On Tue, Aug 10, 2021 at 09:47:31AM +, Soft Works wrote:
>
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of
>> Nicolas George
>> Sent: Tuesday, 10 August 2021 11:16
>> To: F
August 11, 2021 9:44 AM, "Soft Works" wrote:
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of
>> ffmpegandmahanstreamer@e.email
>> Sent: Wednesday, 11 August 2021 15:01
>> To: FFmpeg development discussions and patches > de...@ffmp
August 12, 2021 8:39 AM, "Kieran Kunhya" wrote:
> On Thu, 12 Aug 2021, 13:35 Nicolas George, wrote:
>
>> Kieran Kunhya (12021-08-12):
>> And how do the 1.5 billion Gmail users use SMTP without disabling
>> security
>> features?
>>
>> Do I need to do tech support for Google too?
>>
>> https://
August 12, 2021 5:11 AM, "Soft Works" wrote:
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of
>> Nicolas George
>> Sent: Thursday, 12 August 2021 10:51
>> To: FFmpeg development discussions and patches > de...@ffmpeg.org>
>> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nice
August 12, 2021 4:51 AM, "Nicolas George" wrote:
> Paul Buxton (12021-08-12):
>
>> From the point of view of someone who is currently developing a filter for
>> ffmpeg and will be submitting a patch to the list for the first time, I
>> think this is a great idea.Whilst following simple instructi
August 13, 2021 11:10 AM, "Mario Winkler" wrote:
> Dear Developers
>
> I direct a media project involving a huge variety of online available videos.
> We will analyse these
> videos with available and state of the art machine learning tools, but need
> to pre-process the
> videos and bring the
August 13, 2021 9:30 PM, "Soft Works" wrote:
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of Lynne
>> Sent: Saturday, 14 August 2021 03:08
>> To: FFmpeg development discussions and patches
>> Subject: Re: [FFmpeg-devel] [RFC] Suggestion for a Nicer Integration with
>> GitHub
>>
Mike, i was told you can push this?
August 11, 2021 9:04 AM, ffmpegandmahanstreamer@e.email wrote:
> ping
>
> August 1, 2021 12:22 PM, ffmpegandmahanstreamer@e.email wrote:
>
>> Per Andreas Rheinhardt request i'm splitting the working patches in two.
>> ---
>
August 13, 2021 10:11 PM, "James Zern" wrote:
> this prevents some mismatches in config values for realtime and all
> intra modes, avoiding failures like:
>
> [libaom-av1 @ ...] Failed to initialize encoder: Invalid parameter
> [libaom-av1 @ ...] Additional information: g_lag_in_frames out of
>
August 13, 2021 10:11 PM, "James Zern" wrote:
> this prevents some mismatches in config values for realtime and all
> intra modes, avoiding failures like:
>
> [libaom-av1 @ ...] Failed to initialize encoder: Invalid parameter
> [libaom-av1 @ ...] Additional information: g_lag_in_frames out of
>
August 13, 2021 8:42 PM, "Ronald S. Bultje" wrote:
> Hi,
>
> On Thu, Aug 12, 2021 at 4:51 AM Nicolas George wrote:
>
>> Paul Buxton (12021-08-12):
>> From the point of view of someone who is currently developing a filter
>> for
>> ffmpeg and will be submitting a patch to the list for the first
August 14, 2021 12:34 AM, "zhilizhao(赵志立)" wrote:
>> On Aug 14, 2021, at 11:27 AM, ffmpegandmahanstreamer@e.email wrote:
>>
>> August 13, 2021 8:42 PM, "Ronald S. Bultje" wrote:
>>
>>> Hi,
>>>
>>> On Thu, Aug 12,
This cleans up the code in the decode24bit and decode16bit functions by putting
it in way that expresses the true intent while making it easier to read.
---
libavcodec/truemotion1.c | 35 ---
1 file changed, 12 insertions(+), 23 deletions(-)
diff --git a/libavcode
> On Sun, Aug 01, 2021 at 04:22:28PM +, ffmpegandmahanstreamer@e.email
> wrote:
>
>> Per Andreas Rheinhardt request i'm splitting the working patches in two.
>
> And this results in a commit message like this:
> Author: ffmpegandmahanstreamer@e.email
This cleans up the code in the decode24bit and decode16bit functions by putting
it in way that expresses the true intent while making it easier to read.
---
libavcodec/truemotion1.c | 35 ---
1 file changed, 12 insertions(+), 23 deletions(-)
diff --git a/libavcode
The other patch has more subject line aligned to other devs, go to that one
instead.
August 14, 2021 7:24 AM, "ffmpegandmahanstreamer"
wrote:
> This cleans up the code in the decode24bit and decode16bit functions by
> putting it in way that
> expresses the true intent whi
August 14, 2021 7:43 AM, "Nicolas George" wrote:
> ffmpegandmahanstreamer (12021-08-14):
>
>> Once again this proves the superioity of the graphical stuff.
>
> Start with not top-posting and we may take your opinion on the
> superiority of stuff seriously.
I top
August 14, 2021 12:40 PM, "Jean-Baptiste Kempf" wrote:
> On Sat, 14 Aug 2021, at 03:13, Soft Works wrote:
>
>> The continuing attempt to declare developers who are favoring modern
>> workflows and tooling as newbies and unexperienced is a really disgusting
>> rhetoric.
>
> I agree.
>
> Very co
August 14, 2021 7:56 AM, "Nicolas George" wrote:
> ffmpegandmahanstreamer (12021-08-14):
>
>> I top post only when i want to reply to the message as a whole.
>
> The rules of the list are clear: DO NOT TOP-POST
The rules of the list also say you should be
August 14, 2021 12:47 PM, "Nicolas George" wrote:
> Jean-Baptiste Kempf (12021-08-14):
>
>> The continuing attempt to declare developers who are favoring modern
>> workflows and tooling as newbies and unexperienced is a really disgusting
>> rhetoric.
>> I agree.
>
> Good thing it is not what I
August 14, 2021 12:53 PM, "Nicolas George" wrote:
> Diederick C. Niehorster (12021-08-14):
>
>> Is there a mechanism to trigger such a vote? I hope the core developers
>> have one soon so the project can get moving on this.
>
> There is a mechanism. But as I explained there:
>
> https://ffmpeg
August 14, 2021 1:01 PM, "Nicolas George" wrote:
> ffmpegandmahanstreamer (12021-08-14):
>
>> The real person winning here is Soft Works. He must be laughing right now.
>>
>> Ah, your math degree coming into work here - "if and only if" ;
August 17, 2021 3:58 AM, "Nicolas George" wrote:
> Xiang Xiao (12021-08-17):
>
>> Nicolas, do you have any more progress? I am very interested in your
>> proposal and want to test your change in our special device.
>
> Sorry. I have been focusing on other projects while looking for a good
> way
lgtm
August 19, 2021 11:30 AM, "Nicolas George" wrote:
> Signed-off-by: Nicolas George
> ---
> libavfilter/formats.h | 85 +++
> 1 file changed, 85 insertions(+)
>
> diff --git a/libavfilter/formats.h b/libavfilter/formats.h
> index d94977a3aa..7c8258ed08
August 19, 2021 10:53 AM, "Nicolas George" wrote:
> Signed-off-by: Nicolas George
> ---
> libavfilter/formats.h | 85 +++
> 1 file changed, 85 insertions(+)
>
> diff --git a/libavfilter/formats.h b/libavfilter/formats.h
> index ed513c265a..b3e780a41d 10064
August 24, 2021 9:49 AM, "Mapul Bhola" wrote:
> The x265 configuration and installation guide has moved to Bitbucket so the
> updated link reflects
> that one.
>
> As the openCV site currently only has docs for opencv3 and the filter in
> libavfilter is an opencv2
> an alternative link is prov
59 matches
Mail list logo
