For record with vaapi i use command:
>DRI_PRIME=1 LIBVA_DRIVER_NAME=radeonsi ffmpeg -y -hwaccel vaapi
-vaapi_device /dev/dri/renderD128 -hwaccel_output_format vaapi \
-framerate 30 -video_size 1920x1080 -f x11grab -i :0.0 -f pulse -ac 2 -i
default \
-vf
When I try to seek within a 5 GB MOV file (24 hours 12 minutes of video;
someone screwed up) over http, it seems that ffmpeg downloads a lot more data
than is necessary, and so is fairly slow to start (delay of minutes on a
medium-speed network connection), seemingly unnecessarily so. In
Hi there,
> Always i got error:
> >Impossible to convert between the formats supported by the filter
> 'Parsed_format_' and the filter 'auto_scaler_' Error reinitializing
> filters! Failed to inject frame into filter network: Function not
> implemented
There is an automatic format conversion
On Sun, Jun 7, 2020 at 10:06 PM pdr0 wrote:
> Intra only compression , using -g 1 makes it lossless . Maybe a clue there
>
Aye - I can confirm that -g 1 produces matching framemd5s.
K
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Intra only compression , using -g 1 makes it lossless . Maybe a clue there
Not sure why there is a discrepancy between aomenc, and ffmpeg libaom-av1
--
Sent from: http://www.ffmpeg-archive.org/
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Hi Carl,
On Sun, Jun 7, 2020 at 9:18 PM Carl Eugen Hoyos wrote:
> Am So., 7. Juni 2020 um 19:16 Uhr schrieb Kieran O Leary
> :
>
> > On Sun 7 Jun 2020, 17:56 pdr0, wrote:
> >
> > > Kieran O Leary wrote
> > > > Any idea what's happening? Will I get the libx264-style answer:
> 'this is
> > > >
Carl Eugen Hoyos-2 wrote
> Could it be the number of cores in your system / is the issue reproducible
> with -threads 1 ?
Issue is still present with -threads 1
Does not appear to be related to pixel format (eg. affects yuv420p source
test as well)
--
Sent from:
Am So., 7. Juni 2020 um 19:16 Uhr schrieb Kieran O Leary
:
> On Sun 7 Jun 2020, 17:56 pdr0, wrote:
>
> > Kieran O Leary wrote
> > > Any idea what's happening? Will I get the libx264-style answer: 'this is
> > > googles issue,
> >
> > I can replicate the ffmpeg issue (and with other sources), but
Hi
On Sun 7 Jun 2020, 17:56 pdr0, wrote:
> Kieran O Leary wrote
> > Any idea what's happening? Will I get the libx264-style answer: 'this is
> > googles issue,
>
> I can replicate the ffmpeg issue (and with other sources), but I don't know
> what the problem is
>
> It's not a "google" issue,
Kieran O Leary wrote
> Any idea what's happening? Will I get the libx264-style answer: 'this is
> googles issue,
I can replicate the ffmpeg issue (and with other sources), but I don't know
what the problem is
It's not a "google" issue, because AOM aomenc.exe works, and produces
lossless output
*ffmpeg -fflags +genpts -vsync 0 -hwaccel_device 1 -hwaccel_output_format
cuda -format_code pal -f decklink -i 'DeckLink Quad (4)' -vf
"format=yuv420p|cuda,yadif_cuda=0:-1:0,scale_npp=1280:720" -b:v 3M -bf 2
-aspect 16:9 -profile:v main -preset:v medium -c:v h264_nvenc -c:a aac -b:a
128k -ar
11 matches
Mail list logo
