On 12-03-2019 01:04 AM, Ulf Zibis wrote:
Am 11.03.19 um 20:27 schrieb Paul B Mahol:
On 3/11/19, Ulf Zibis wrote:
Am 09.03.19 um 09:39 schrieb Paul B Mahol:
On 3/9/19, Ulf Zibis wrote:
Another question is, why the fillborders doesn't check if the input is
writable, as suggested in
follow up
On Mon, Mar 11, 2019 at 10:54 PM Sai Balaji wrote:
> Can I change the values of x264 parameters on the fly? The only parameter
> which I want to change is keyint.
>
> ffmpeg -f avfoundation -video_size 800x600 -framerate 30 -i 0 -vcodec
> libx264 -x264-params keyint=30:scenecut=0
On Sun, Mar 10, 2019, at 3:05 AM, Bouke wrote:
>
> I reverted to webmail, and missed some stuff here and there. (One of my
> accounts bounces a lot of mails from the FF list for some reason.)
If I recall correctly it is related to the DMARC policy of your mail provider.
I made a change last
Am 11.03.19 um 20:43 schrieb Carl Eugen Hoyos:
> Our jpeg encoder only supports 8-bit yuv
Ok, that's the reason, thanks.
> No need to post Mediainfo output, all necessary information
> is in the FFmpeg console output.
Maybe for you. ;-)
For me it is not obvious. I guess you mean the info could
2019-03-11 20:31 GMT+01:00, Ulf Zibis :
>
> Am 11.03.19 um 20:14 schrieb Carl Eugen Hoyos:
>> 2019-03-11 20:05 GMT+01:00, Ulf Zibis :
>>> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
2019-03-09 10:44 GMT+01:00, Ulf Zibis :
> Which format should I use with option -f ?
You should
Am 11.03.19 um 20:27 schrieb Paul B Mahol:
> On 3/11/19, Ulf Zibis wrote:
>> Am 09.03.19 um 09:39 schrieb Paul B Mahol:
>>> On 3/9/19, Ulf Zibis wrote:
Another question is, why the fillborders doesn't check if the input is
writable, as suggested in doc/writing_filters.txt.
>>>
Am 11.03.19 um 20:14 schrieb Carl Eugen Hoyos:
> 2019-03-11 20:05 GMT+01:00, Ulf Zibis :
>> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
>>> 2019-03-09 10:44 GMT+01:00, Ulf Zibis :
Which format should I use with option -f ?
>>> You should never need the option -f (except when reading
>>>
On 3/11/19, Ulf Zibis wrote:
>
> Am 09.03.19 um 09:39 schrieb Paul B Mahol:
>> On 3/9/19, Ulf Zibis wrote:
>>> Another question is, why the fillborders doesn't check if the input is
>>> writable, as suggested in doc/writing_filters.txt.
>>>
>> Because it request writtable frames.
>
> Hey Paul,
Am 09.03.19 um 09:39 schrieb Paul B Mahol:
> On 3/9/19, Ulf Zibis wrote:
>> Another question is, why the fillborders doesn't check if the input is
>> writable, as suggested in doc/writing_filters.txt.
>>
> Because it request writtable frames.
Hey Paul, how is this managed?
I don't see something
2019-03-11 20:05 GMT+01:00, Ulf Zibis :
>
> Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
>> 2019-03-09 10:44 GMT+01:00, Ulf Zibis :
>>> Which format should I use with option -f ?
>> You should never need the option -f (except when reading
>> raw g.729 and similar rare raw formats), what did you
Am 09.03.19 um 10:58 schrieb Carl Eugen Hoyos:
> 2019-03-09 10:44 GMT+01:00, Ulf Zibis :
>> Which format should I use with option -f ?
> You should never need the option -f (except when reading
> raw g.729 and similar rare raw formats), what did you try?
When I use
$ ffmpeg -i 16.jpg -vf
2019-03-11 19:53 GMT+01:00, Ulf Zibis :
>
> Am 11.03.19 um 11:58 schrieb Carl Eugen Hoyos:
>>> Is native vs. x264 encoder something different?
>> The native (FFmpeg-internal) encoders may be a little less
>> sophisticated than x264 (and they don't know a special
>> adaptive interlaced setting
Am 11.03.19 um 11:58 schrieb Carl Eugen Hoyos:
> So our suspicion after visual inspection was right.
Yes, indeed.
>> So I buyed the DVD now. Except that it has 3 audio tracks to choose and
>> the VHS head switching artefacts are missing, it unfortunately has the
>> equal bad quality than my DVD
Can I change the values of x264 parameters on the fly? The only parameter
which I want to change is keyint.
ffmpeg -f avfoundation -video_size 800x600 -framerate 30 -i 0 -vcodec
libx264 -x264-params keyint=30:scenecut=0 -acodec aac -b:v 1M -b:a 192k
-f dash -use_template 0 -use_timeline 0
Hello,
I have a setup where I am transcoding live feeds from OTA broadcasts to H264
using the Nvidia NVENC encoder. I am also transcoding the audio to AAC. We are
trying to output 3 cbr streams and various bitrates. The problem I am running
into is that the PTS and DTS on the multiple outputs
2019-02-21 11:31 GMT+01:00, Ulf Zibis :
>
> Am 21.02.19 um 01:41 schrieb Carl Eugen Hoyos:
>> 2019-02-04 23:29 GMT+01:00, Ulf Zibis :
>>> Now I've checked the files with mediainfo:
>>> - The vob file is stated as interlaced top first. (I know, this does
>>> nothing say about the content, only the
2019-02-26 10:40 GMT+01:00, Tom Worton :
> In your last email you said that I was missing the complete uncut console
> output. If I am doing it correct. I replied with the missing information. Do
> you have any further advice?
No.
You are not the recipient of the warning message.
If your output
Am 11.03.2019 um 09:01 schrieb Gerardo Ballabio:
Ok, thank you Michael. I'll try haldclut then. This means I have to do
some research into Gimp too...
For the described workflow you can also use any other graphics program,
if it can read and write uncompressed or lossless compressed images
On Sun, 10 Mar 2019, 07:29 Venkateswaran.S,
wrote:
> Hi all,
>
> I wants to detect glitches in my video. Is there any filter to achieve it.?
>
Have you looked into the signalstats filter? It is often used in the
QCTools application in order to find glitches in digitised/migrated
Ok, thank you Michael. I'll try haldclut then. This means I have to do
some research into Gimp too...
Gerardo
Il giorno dom 10 mar 2019 alle ore 22:20 Michael Koch
ha scritto:
>
> Am 10.03.2019 um 22:05 schrieb Michael Koch:
> > Am 10.03.2019 um 21:33 schrieb Gerardo Ballabio:
> >> Thank you
20 matches
Mail list logo
