On Sun, 2020-09-06 at 15:25 +0100, Mark Thompson wrote:
> On 04/09/2020 19:24, Rogozhkin, Dmitry V wrote:
> > On Thu, 2020-09-03 at 01:02 +, Rogozhkin, Dmitry V wrote:
> > > >
> > > > (If you do implement it then you can delete all of the ad-hoc
> > > > treatment in ffmpeg, like has been done
On 04/09/2020 19:24, Rogozhkin, Dmitry V wrote:
On Thu, 2020-09-03 at 01:02 +, Rogozhkin, Dmitry V wrote:
(If you do implement it then you can delete all of the ad-hoc
treatment in ffmpeg, like has been done for the other hardware
codecs.)
I like deleting code:). Ok, this sounds good.
On Thu, 2020-09-03 at 01:02 +, Rogozhkin, Dmitry V wrote:
> >
> > (If you do implement it then you can delete all of the ad-hoc
> > treatment in ffmpeg, like has been done for the other hardware
> > codecs.)
>
> I like deleting code:). Ok, this sounds good. Let's try to understand
> what
On Wed, 2020-09-02 at 20:37 +0100, Mark Thompson wrote:
> > > I still don't see the full picture. What I am looking for at the
> > > first
> > > place is how maintainers and architects envision hwaccel to work
> > > in
> > > general. Basically, there are few ways to specify the device (-
> > >
On Wed, 2020-09-02 at 20:37 +0100, Mark Thompson wrote:
> > In general, per my taste, I would try to use the following device
> > specification working with QSV on Linux across all command lines:
> >
> > -init_hw_device vaapi=va:/dev/dri/renderD129 -init_hw_device
> > qsv=hw@va
> >
On Wed, 2020-09-02 at 20:37 +0100, Mark Thompson wrote:
> On 02/09/2020 15:36, Rogozhkin, Dmitry V wrote:
> > On Wed, 2020-09-02 at 14:21 +, Rogozhkin, Dmitry V wrote:
> > > On Wed, 2020-09-02 at 08:41 +, Soft Works wrote:
> > > > ...
> >
> > Small suggestion: let's move discussion around
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Mark Thompson
> Sent: Wednesday, September 2, 2020 9:38 PM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv decoders to use
> initialized device
>
> On 02/09/20
On 02/09/2020 15:36, Rogozhkin, Dmitry V wrote:
On Wed, 2020-09-02 at 14:21 +, Rogozhkin, Dmitry V wrote:
On Wed, 2020-09-02 at 08:41 +, Soft Works wrote:
...
Small suggestion: let's move discussion around -qsv_device and
-hwaccel_device options entirely to the "ffmpeg_qsv: use
45 AM
> > > To: ffmpeg-devel@ffmpeg.org
> > > Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv
> > > decoders
> > > to use
> > > initialized device
> > >
> > > On Wed, 2020-09-02 at 04:32 +, Soft Works wrote:
> > &g
gt; Soft Works
> > > > Sent: Wednesday, September 2, 2020 6:13 AM
> > > > To: FFmpeg development discussions and patches > > > de...@ffmpeg.org>
> > > > Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv
> > > > decoders
> &g
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Rogozhkin, Dmitry V
> Sent: Wednesday, September 2, 2020 8:45 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv decoders to use
> initialized device
>
>
n
> > > > Sent: Wednesday, September 2, 2020 4:44 AM
> > > > To: ffmpeg-devel@ffmpeg.org
> > > > Cc: Dmitry Rogozhkin
> > > > Subject: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv decoders
> > > > to
> > > > use initial
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Wednesday, September 2, 2020 6:13 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv decoders to use
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Soft Works
> Sent: Wednesday, September 2, 2020 5:33 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv decoders to use
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Dmitry Rogozhkin
> Sent: Wednesday, September 2, 2020 4:44 AM
> To: ffmpeg-devel@ffmpeg.org
> Cc: Dmitry Rogozhkin
> Subject: [FFmpeg-devel] [PATCH] lavc/qsvdec: allow qsv decoders to use
> initialized
qsv decoders did not allow to use devices explicitly initialized on
the command line and actually were using default device. This starts
to cause confusion with intel discrete GPUs since in this case decoder
might run on default integrated GPU device (/dev/dri/renderD128) and
encoder on the device
16 matches
Mail list logo
