On 06/07/2019 20:59, Pancho wrote:
> On 06/07/2019 09:25, James Harris wrote:
>
>>> VLC is clearly already using H.264 hardware decode at 1080. I guess HEVC
>>> hardware decode will come with time. I haven't seen any mention of vp9
>>> and of course av1 is a potential in the near future.
>>
>> I'm not sure I understand that. Do you mean that the Pi has hardware
>> which will do - or will help with - HEVC decode but VLC doesn't take
>> advantage of it yet?
>>
>
> Yes, VLC doesn't use it now but probably will in future. LibreElec may
> already be set up to use hardware HEVC.
>
>>>
>>> The main problem is that Chromium isn't using gpu support.
>>>
>>> I could show the output of typing chrome://gpu into chromium, if anyone
>>> is interested.
>>
>> Please do.
>>
>
> Graphics Feature Status
> Canvas: Software only, hardware acceleration unavailable
> Flash: Software only. Hardware acceleration disabled
> Flash Stage3D: Software only. Hardware acceleration disabled
> Flash Stage3D Baseline profile: Software only. Hardware acceleration
> disabled
> Compositing: Software only. Hardware acceleration disabled
> Multiple Raster Threads: Enabled
> Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
> Out-of-process Rasterization: Disabled
> Hardware Protected Video Decode: Disabled
> Rasterization: Software only. Hardware acceleration disabled
> Skia Renderer: Disabled
> Surface Control: Disabled
> Surface Synchronization: Enabled
> Video Decode: Software only. Hardware acceleration disabled
> Viz Service Display Compositor: Enabled
> WebGL: Software only, hardware acceleration unavailable
> WebGL2: Software only, hardware acceleration unavailable
For comparison, here's what I see on a vanilla install on RPi2 - and on
a 1920x1200 screen, if that's relevant.
Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration
unavailable
Compositing: Software only. Hardware acceleration disabled
Multiple Raster Threads: Enabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only, hardware acceleration unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
VPx Video Decode: Software only, hardware acceleration unavailable
WebGL: Hardware accelerated but at reduced performance
WebGL2: Unavailable
> Problems Detected
> Native GpuMemoryBuffers have been disabled, either via about:flags or
> command line.
> Disabled Features: native_gpu_memory_buffers
> Skia renderer is not used by default.
> Disabled Features: skia_renderer
Problems Detected
Accelerated video decode is unavailable on Linux: 137247
Disabled Features: accelerated_video_decode
Only enable WebGL for the Mesa Gallium llvmpipe driver: 571899
Disabled Features: webgl2, accelerated_vpx_decode, gpu_compositing,
flash_stage3d, gpu_rasterization, flash_3d, flash_stage3d_baseline,
accelerated_2d_canvas, panel_fitting, accelerated_video_decode,
accelerated_video_encode
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Mesa drivers in Linux handle varyings without static use incorrectly: 333885
Applied Workarounds: count_all_in_varyings_packing
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Limited enabling of Chromium GL_INTEL_framebuffer_CMAA: 535198
Applied Workarounds: disable_framebuffer_cmaa
Disable partial swaps on Mesa drivers (detected with GL_VERSION): 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Decode and encode before generateMipmap for srgb format textures on os
except macosx: 634519
Applied Workarounds: decode_encode_srgb_for_generatemipmap
Mesa driver GL 3.3 requires invariant and centroid to match between
shaders: 639760, 641129
Applied Workarounds: remove_invariant_and_centroid_for_essl3
Gpu compositing has been disabled, either via blacklist, about:flags or
the command line. The browser will fall back to software compositing and
hardware acceleration will be unavailable.
Disabled Features: gpu_compositing
Native GpuMemoryBuffers have been disabled, either via about:flags or
command line.
Disabled Features: native_gpu_memory_buffers
> Version Information
> Data exported 2019-07-06T18:28:56.621Z
> Chrome version Chrome/74.0.3729.157
> Operating system Linux 4.19.50-v7l+
> Software rendering list URL
>
https://chromium.googlesource.com/chromium/src/+/7b16107ab85c5364cdcd0b2dea2539
a1f2dc327a/gpu/config/software_rendering_list.json
> Driver bug list URL
>
https://chromium.googlesource.com/chromium/src/+/7b16107ab85c5364cdcd0b2dea2539
a1f2dc327a/gpu/config/gpu_driver_bug_list.json
> ANGLE commit id unknown hash
> 2D graphics backend Skia/74 ae4b97edd5b9eeee9e4fe9814f67e3abc4ba1a75-
> Command Line /usr/lib/chromium-browser/chromium-browser-v7
> --disable-quic --enable-tcp-fast-open
> --ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so
> --ppapi-flash-args=enable_stagevideo_auto=0
> --ppapi-flash-version=32.0.0.207 --disable-gpu --enable-pinch
> --flag-switches-begin --ignore-gpu-blacklist --flag-switches-end
>
> [snip]
>
>> Since 4k panels are so prevalent I guess 4k is the way to go so I went
>> into PC World yesterday to see some examples of what that would look
>> like in practice. But to my surprise they did not even have one example
>> of such a setup in place. 4k TVs but no 4k monitors connected to computers.
>>
>
> Have you considered using a 4k TV as a monitor?
>
I have a 4k TV I can try but no computer with 4k output. Why I went into
PC World was in the hope of seeing two things:
1. What a 4k desktop was like in practice on different size screens.
2. What, if any, curvature would be best.
Unfortunately, as I said, they didn't just lack a /selection/ of options
to view but had no 4k desktop on display whatsoever.
--
James Harris
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | FidoUsenet Gateway (3:770/3)
|