Re: [FFmpeg-user] Listing the hardware accelerators

2019-09-27 Thread Michael Koch
Am 26.09.2019 um 23:06 schrieb Carl Eugen Hoyos: Am Do., 26. Sept. 2019 um 21:13 Uhr schrieb Verachten Bruno : I have different environments (X86, ARM, Jetson Nano) on which I'd like to use hardware encoders and decoders if available. I guess that I won't be able to use them if they have not be

[FFmpeg-user] loudnorm and experimental audio codecs

2019-09-27 Thread Jonathan Baecker
Hello, I tried to use the loudnorm filter with experimental audio codec - I need mostly s302m - but I had some issues. I make a report here to: https://trac.ffmpeg.org/ticket/8131 But because it is an experimental codec, I think the priority is very low to fix here something. The problem i

Re: [FFmpeg-user] Listing the hardware accelerators

2019-09-27 Thread Moritz Barsnick
On Fri, Sep 27, 2019 at 09:14:07 +0200, Michael Koch wrote: > Does that mean > a) List all hardware acceleration methods supported in this build of > ffmpeg, regardless if the hardware is really built into this computer, > or does it mean > b) List all hardware acceleration methods supported in thi

Re: [FFmpeg-user] Listing the hardware accelerators

2019-09-27 Thread Carl Eugen Hoyos
Am Fr., 27. Sept. 2019 um 10:17 Uhr schrieb Moritz Barsnick : > > On Fri, Sep 27, 2019 at 09:14:07 +0200, Michael Koch wrote: > > Does that mean > > a) List all hardware acceleration methods supported in this build of > > ffmpeg, regardless if the hardware is really built into this computer, > > or

Re: [FFmpeg-user] Listing the hardware accelerators

2019-09-27 Thread Verachten Bruno
Thanks a lot for your answers and new questions. When I run the -hwaccels, I get: ffmpeg -hwaccels ffmpeg version 4.2.1 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1) configuration: --enable-gpl --enable-version3 --disable-static --enable-shared

Re: [FFmpeg-user] Listing the hardware accelerators

2019-09-27 Thread Carl Eugen Hoyos
Am Fr., 27. Sept. 2019 um 15:04 Uhr schrieb Verachten Bruno : > > Thanks a lot for your answers and new questions. > When I run the -hwaccels, I get: > ffmpeg -hwaccels > ffmpeg version 4.2.1 Copyright (c) 2000-2019 the FFmpeg developers > built with gcc 7 (Ubuntu 7.4.0-1ubuntu1~18.04.1) > con

Re: [FFmpeg-user] Listing the hardware accelerators

2019-09-27 Thread Michael Koch
Carl Eugen, @Michael: Please understand that (at least most) developers do not have the time to copy the change you already suggested into their local tree. Instead install a git client of your choice and send the documentation patches to the development mailing list where they will find more fr

Re: [FFmpeg-user] Listing the hardware accelerators

2019-09-27 Thread Carl Eugen Hoyos
Am Fr., 27. Sept. 2019 um 15:53 Uhr schrieb Michael Koch : > > Carl Eugen, > > > @Michael: Please understand that (at least most) developers do > > not have the time to copy the change you already suggested into > > their local tree. Instead install a git client of your choice and send > > the docu

Re: [FFmpeg-user] Stereoscopic hwaccel

2019-09-27 Thread JackDesBwa
I answer to myself. > (1) Which way could I be certain that it is not currently supported or > if there is some option to pass? By reading the source code, I found how it is set in libx264 codec, but there is nothing similar at all in nvenc nor in vaapi. In nvenc, I saw stereo fields in the confi

Re: [FFmpeg-user] Stereoscopic hwaccel

2019-09-27 Thread Carl Eugen Hoyos
Am Fr., 27. Sept. 2019 um 18:06 Uhr schrieb JackDesBwa : > > I answer to myself. > > > (1) Which way could I be certain that it is not currently supported or > > if there is some option to pass? > > By reading the source code, I found how it is set in libx264 codec, > but there is nothing similar a

Re: [FFmpeg-user] Stereoscopic hwaccel

2019-09-27 Thread JackDesBwa
> I wonder if VAProfileH264StereoHigh is really what you are looking > for... It is hard to find information about it, as most answers come from a pasting of the results of vainfo command. However, I could have determined (through driver code for example) that it is related to Multiview Video Codi