Am 27.11.19 um 01:35 schrieb sean darcy:
> On 11/26/19 5:36 PM, Carl Eugen Hoyos wrote:
>> Am Di., 26. Nov. 2019 um 21:26 Uhr schrieb sean darcy
>> :
>>
> enable-stripping is the default
>>
>>> Well one reason to have superfluous --enable options, is so you can
>>> remember how to disable
On 11/26/19 5:36 PM, Carl Eugen Hoyos wrote:
Am Di., 26. Nov. 2019 um 21:26 Uhr schrieb sean darcy :
enable-stripping is the default
Well one reason to have superfluous --enable options, is so you can
remember how to disable them. For instance, stripping isn't working.
strip -o ffprobe
Thanks very Micael for your assistance, the main problem was the path,
looks like android hide the true path, I found the real with a video player
app
On Tue, Nov 26, 2019, 00:29 Micael Silva wrote:
> On Mon, 25 Nov 2019, 22:54 fernando guerrero,
> wrote:
>
> > Ok, thanks for reply
> >
> > Now
Am Di., 26. Nov. 2019 um 21:26 Uhr schrieb sean darcy :
> >> enable-stripping is the default
> Well one reason to have superfluous --enable options, is so you can
> remember how to disable them. For instance, stripping isn't working.
>
> strip -o ffprobe ffprobe_g
>
Am 26.11.19 um 21:50 schrieb Carl Eugen Hoyos:
> Am Di., 26. Nov. 2019 um 21:45 Uhr schrieb Dennis Mungai :
>>
>>> enable-runtime-cpudetect does not do what you think it does,
>>> remove it.
>>
>> Why then is it enabled by default? See
>>
Am Di., 26. Nov. 2019 um 21:45 Uhr schrieb Dennis Mungai :
>
> > enable-runtime-cpudetect does not do what you think it does,
> > remove it.
>
> Why then is it enabled by default? See
> https://lists.ffmpeg.org/pipermail/ffmpeg-cvslog/2012-September/054876.html
(How is your question related?)
The
> enable-runtime-cpudetect does not do what you think it does,
> remove it.
Why then is it enabled by default? See
https://lists.ffmpeg.org/pipermail/ffmpeg-cvslog/2012-September/054876.html
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
On 11/26/19 3:03 PM, sean darcy wrote:
On 11/26/19 12:28 PM, Carl Eugen Hoyos wrote:
Am Mo., 25. Nov. 2019 um 23:45 Uhr schrieb sean darcy
:
On Fedora 31, today's git:
libavcodec/qsvenc.c: In function 'qsv_retrieve_enc_vp9_params':
libavcodec/qsvenc.c:827:25: error: 'vp9_extend_buf'
On 11/26/19 12:28 PM, Carl Eugen Hoyos wrote:
Am Mo., 25. Nov. 2019 um 23:45 Uhr schrieb sean darcy :
On Fedora 31, today's git:
libavcodec/qsvenc.c: In function 'qsv_retrieve_enc_vp9_params':
libavcodec/qsvenc.c:827:25: error: 'vp9_extend_buf' undeclared (first
use in th>
827 |
On 26-11-2019 10:53 pm, Michael Koch wrote:
Am 26.11.2019 um 17:48 schrieb Michael Koch:
Am 26.11.2019 um 17:32 schrieb Michael Koch:
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no
input file
required for reproducing.
There are
Am Di., 26. Nov. 2019 um 18:34 Uhr schrieb Carl Zwanzig :
>
> On 11/26/2019 9:28 AM, Carl Eugen Hoyos wrote:
> > Unrelated:
>
> > enable-vaapi has no effect.
> > enable-postproc has no effect
> > enable-indev=jack has no effect
> > enable-avfilter has no effect
>
> No effect ever or none with the
Am Mo., 25. Nov. 2019 um 10:52 Uhr schrieb :
>
> I am experimenting and reviewing the usefulness of hevc for me by
> transcoding h.264/avc .mp4 files into hevc .mp4 using nvenc.
(Without looking at your actual command line that looks very complicated)
Every (re-) encode is equivalent to a loss
On 11/26/2019 9:28 AM, Carl Eugen Hoyos wrote:
Unrelated:
enable-vaapi has no effect.
enable-postproc has no effect
enable-indev=jack has no effect
enable-avfilter has no effect
No effect ever or none with the other options/architecture? If those options
never affect the config, should
Am Mo., 25. Nov. 2019 um 23:45 Uhr schrieb sean darcy :
>
> On Fedora 31, today's git:
>
> libavcodec/qsvenc.c: In function 'qsv_retrieve_enc_vp9_params':
> libavcodec/qsvenc.c:827:25: error: 'vp9_extend_buf' undeclared (first
> use in th>
>827 | (mfxExtBuffer*)_extend_buf,
>|
Am 26.11.2019 um 17:48 schrieb Michael Koch:
Am 26.11.2019 um 17:32 schrieb Michael Koch:
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no input
file
required for reproducing.
There are two graphs: The first one uses signalstats and
Am Di., 26. Nov. 2019 um 14:55 Uhr schrieb Jon Cook :
> I'm having a problem trying to encode using mjpeg_qsv. The
> command I'm using is:
>
> ffmpeg.exe -y -i sample.avi -c:v mjpeg_qsv output.mp4
Complete, uncut console output missing.
Carl Eugen
Am 26.11.2019 um 17:32 schrieb Michael Koch:
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no input
file
required for reproducing.
There are two graphs: The first one uses signalstats and drawgraph, and
the second one uses astats and
Am 26.11.2019 um 14:26 schrieb Paul B Mahol:
I have a new example with testsrc2 and anoisesrc. There is no input file
required for reproducing.
There are two graphs: The first one uses signalstats and drawgraph, and
the second one uses astats and adrawgraph. The problem is that the two
graphs
Unfortunately I am unable to release a sample at this time.
Is there any way you could give me some intuition as to what might be causing
the error?
Or any other information I can provide that might help?
Gary Conley
From: ffmpeg-user
Hi,
I'm having a problem trying to encode using mjpeg_qsv. The command I'm
using is:
ffmpeg.exe -y -i sample.avi -c:v mjpeg_qsv output.mp4
but it gives this error:
[mjpeg_qsv @ 016fbde08240] Error submitting the frame for encoding.
Googling for that error shows up nothing. I've tried
On 11/26/19, Michael Koch wrote:
>
>>> Thanks for your suggestion. Adding -r 25 does indeed solve the problem.
>>> Although I don't understand why it is required. The input framerate is
>>> 25 and it's detected correctly when I use the simpler filter chain.
>>>
>> Ah, I know why this happens, you
Thanks for your suggestion. Adding -r 25 does indeed solve the problem.
Although I don't understand why it is required. The input framerate is
25 and it's detected correctly when I use the simpler filter chain.
Ah, I know why this happens, you need to use settb=1/FPS filter after vstack.
This
On 11/26/19, Michael Koch wrote:
> Am 26.11.2019 um 09:55 schrieb Carl Eugen Hoyos:
>>
>>> Am 26.11.2019 um 09:40 schrieb Michael Koch
>>> :
>>>
Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
> Am 25.11.2019 um 23:36 schrieb Michael Koch
> :
>
> [mp4 @
Am 26.11.2019 um 09:55 schrieb Carl Eugen Hoyos:
Am 26.11.2019 um 09:40 schrieb Michael Koch :
Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
Am 25.11.2019 um 23:36 schrieb Michael Koch :
[mp4 @ 006288c0] Frame rate very high for a muxer not efficiently
supporting it.
Please
> Am 26.11.2019 um 09:40 schrieb Michael Koch :
>
>> Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
>>
>>> Am 25.11.2019 um 23:36 schrieb Michael Koch :
>>>
>>> [mp4 @ 006288c0] Frame rate very high for a muxer not efficiently
>>> supporting it.
>>> Please consider specifying a
Am 26.11.2019 um 07:11 schrieb Carl Eugen Hoyos:
Am 25.11.2019 um 23:36 schrieb Michael Koch :
[mp4 @ 006288c0] Frame rate very high for a muxer not efficiently
supporting it.
Please consider specifying a lower framerate, a different muxer
Did you see this?
I did not read the whole
26 matches
Mail list logo