On 12/27/23 01:58, Kieran O Leary wrote:
On Tue 26 Dec 2023 at 22:53, Mark Filipak
Oh, no! Mister Billipedia! Hahahaha... (where people who are as ill
informed as you are, get to
pontificate)
I think you must have misread the tone of Devin’s email, and I would hardly
call him ill informed.
I'm testing out an Intel Flex 140 card and I am attempting to transcode 4
inputs to 1 output using the xstack_qsv filter. My command takes in 4 udp
multicast ts files (h264 encoded) and outputs one h264_qsv encoded udp
transport stream. My command looks like so:
/tmp/ffmpeg_g -nostats -logl
On Wed, 27 Dec 2023 at 18:40, Shane Warren wrote:
>
> I'm testing out an Intel Flex 140 card and I am attempting to transcode 4
> inputs to 1 output using the xstack_qsv filter. My command takes in 4 udp
> multicast ts files (h264 encoded) and outputs one h264_qsv encoded udp
> transport stream.
I have created a bug and linked a sample video that changes resolutions on the
fly:
https://trac.ffmpeg.org/ticket/10762
Get back to me if you need anything else I can help with.
From: ffmpeg-user on behalf of Dennis Mungai
Sent: Wednesday, December 27, 2023 1
Hi,
I'm using this command line to print four consecutive random numbers:
ffmpeg -loglevel repeat -f lavfi -i color=gray:size=1x1,format=gray -vf
geq=lum='st(0,0.123);print(random(0));print(random(0));print(random(0));print(random(0));0'
-frames 1 -y out.png
The output is always the same fou
On Wed, Dec 27, 2023 at 4:51 PM Michael Koch
wrote:
>
> Hi,
>
> I'm using this command line to print four consecutive random numbers:
>
> ffmpeg -loglevel repeat -f lavfi -i color=gray:size=1x1,format=gray -vf
> geq=lum='st(0,0.123);print(random(0));print(random(0));print(random(0));print(random(0
Am 27.12.2023 um 23:04 schrieb Devin Heitmueller:
On Wed, Dec 27, 2023 at 4:51 PM Michael Koch
wrote:
Hi,
I'm using this command line to print four consecutive random numbers:
ffmpeg -loglevel repeat -f lavfi -i color=gray:size=1x1,format=gray -vf
geq=lum='st(0,0.123);print(random(0));print(r
Michael:
On 2023-12-27 13:51, Michael Koch wrote:
...I'm using this command line to print four consecutive random numbers:
...
I do not have an answer to your question about the behaviour of the
random() function. However, I cannot reproduce your results on my
machine. I get an error complaini
Am 27.12.2023 um 23:59 schrieb Jim DeLaHunt:
Michael:
On 2023-12-27 13:51, Michael Koch wrote:
...I'm using this command line to print four consecutive random numbers:
...
I do not have an answer to your question about the behaviour of the
random() function. However, I cannot reproduce your re
Michael:
On 2023-12-27 15:20, Michael Koch wrote:
Am 27.12.2023 um 23:59 schrieb Jim DeLaHunt:
Michael:
On 2023-12-27 13:51, Michael Koch wrote:
...I'm using this command line to print four consecutive random
numbers:
...
I do not have an answer to your question about the behaviour of the
r
> I have created a bug and linked a sample video that changes resolutions on the
> fly:
>
> https://trac.ffmpeg.org/ticket/10762
>
> Get back to me if you need anything else I can help with.
>
> From: ffmpeg-user on behalf of Dennis Mungai
>
> Sent: Wednesday,
On 12/27/2023 3:54 PM, Jim DeLaHunt wrote:
The documentation says, "x is the index of the internal variable which will
be used to save the seed/state."
(https://ffmpeg.org/ffmpeg-all.html#Expression-Evaluation). I don't know
what it means by "index of the internal variable", and I don't know wh
This is important to me. I sent it yesterday, but from the wrong account, so it didn't get to
ffmpeg-user. If you somehow got 2 of them, please accept my apology.
On 12/27/23 01:58, Kieran O Leary wrote:
On Tue 26 Dec 2023 at 22:53, Mark Filipak
Oh, no! Mister Billipedia! Hahahaha... (where
This is important to me. I sent it yesterday, but from the wrong account, so it wasn't accepted by
ffmpeg-user. If you somehow got 2 of them, please accept my apology. (Between TBird's quirks and
Gmail's quirks, email is driving me nuts.)
On 12/27/23 01:58, Kieran O Leary wrote:
On Tue 26 Dec
Hi Mark
On Wed 27 Dec 2023 at 08:53, Mark Filipak
wrote:
> On 12/27/23 01:58, Kieran O Leary wrote:
> > On Tue 26 Dec 2023 at 22:53, Mark Filipak
> >> Oh, no! Mister Billipedia! Hahahaha... (where people who are as ill
> >> informed as you are, get to
> >> pontificate)
> >
> >
> > I think you
On Thu, 28 Dec 2023, 05:15 Xiang, Haihao, <
haihao.xiang-at-intel@ffmpeg.org> wrote:
>
> > I have created a bug and linked a sample video that changes resolutions
> on the
> > fly:
> >
> > https://trac.ffmpeg.org/ticket/10762
> >
> > Get back to me if you need anything else I can help with.
>
I was encoding with VBR native FFMPEG's AAC encoder i.e using `-q:a.`
https://trac.ffmpeg.org/wiki/Encode/AAC
The above page says that effective range for -q:a is `0.1 to 2.0.`
But, I tried to encode with `-q:a 5.0` and FFMPEG didn't gave any error for
encoding the audio. I was suprised!
And I
17 matches
Mail list logo