On Sun, 11 Jul 2021, RVP wrote:
GPU-acceleration does not necessarily imply HW-assisted video decoding.
This latter depends heavily on the decoding capabilities of one's CPU
and the video being played. Some CPUs don't do H.265.
I forgot to mention this: it also depends on the decoding
On Sun, 11 Jul 2021, Rhialto wrote:
It doesn't tell me that it does, and I've never seen any indication of
it, so this is indeed as I expected.
If you have FreeBSD (or Linux) installed, you can use the same `I'
key to see what HW-assisted video decoding looks like. Keep `top'
running, then
I've somehow misconfigured something and can't work out what. On one
NetBSD 9.2 system, if I pkgin install something, then "pkg_info -u"
reports it as installed. On the other, pkg_info doesn't seem to know
anything about what I installed with pkgin, though "pkgin show-keep"
still shows it fine.
On Sun, 11 Jul 2021, Rhialto wrote:
If I play a much "harder" video, say H.265 at 1920x1080, the default
output from mpv gets way behind and starts to drop lots of frames.
The default output is "sdl", which I think uses MesaLib/GL. Which is
claimed to be accellerated: (output from glxinfo)
On Sun, 11 Jul 2021, Rhialto wrote:
I also use estd to dymamically throttle down the cpu freqency when the
system is not so busy. So most of the time it is set to 800 MHz, the
lowest possible value.
From what nia@ tells me (and this is also in the guide: section 11.1.4.),
you shouldn't
On Sun 11 Jul 2021 at 20:13:08 +, RVP wrote:
> GPU-acceleration does not necessarily imply HW-assisted video decoding.
I'm not really expecting that. With XVideo, as I understand it, the cpu
has to do the decoding. XVideo just scales and puts the image in a video
overlay. But still, this
On Sun 11 Jul 2021 at 14:09:45 -, Michael van Elst wrote:
> In the best case, the CPU is still decoding the input stream and
> filling the display pipeline. If the CPU is too slow, or the decoder
> latency cannot be anticipated, the decoded results will come too
> late and frames get dropped.
On 11/07/2021 14:13, Rhialto wrote:
I keep having weird things with graphics performance. I got myself a new
box ("Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz") with 6 cores. I got a
"new" old Radeon HD-5450 because at least that chipset is supported for
dri/drm.
I also use estd to dymamically
rhia...@falu.nl (Rhialto) writes:
>How can this be? If it's GPU-accellerated, this should be independent of
>the CPU frequency, I would think?
In the best case, the CPU is still decoding the input stream and
filling the display pipeline. If the CPU is too slow, or the decoder
latency cannot be
I keep having weird things with graphics performance. I got myself a new
box ("Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz") with 6 cores. I got a
"new" old Radeon HD-5450 because at least that chipset is supported for
dri/drm.
I also use estd to dymamically throttle down the cpu freqency when the
10 matches
Mail list logo
