On 03/05/2018 09:02 PM, Daniel van Vugt wrote:
> Doug,
>
> Ideally it will be automatically installed, or at least gets installed
> with ubuntu-restricted-addons. See:
> https://wiki.ubuntu.com/IntelQuickSyncVideo
>
Good to know about the add-ons package, been quite awhile here that I've
used it.
Doug,
Ideally it will be automatically installed, or at least gets installed
with ubuntu-restricted-addons. See:
https://wiki.ubuntu.com/IntelQuickSyncVideo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This seems fixed as of today's updates but does beg the question of how would
most users even know to install the gstreamer1.0-vaapi package?
It doesn't show up here in ubuntu software no matter what I search..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I might do that but:
(a) We would have to exclude the old fix (upgrade plugins-bad) at the same
time; and
(b) It is almost EOW here. I can probably bet on everything just working by
next week :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Fri, Mar 02, 2018 at 02:42:41AM -, Daniel van Vugt wrote:
> Oops. I wasn't testing the new packages yet. I guess we're waiting on:
>
> gst-plugins-base1.0 (1.13.1-1) experimental; urgency=medium
You could probably (carefully!) extract it from bionic-proposed if you
want to test it that
Oops. I wasn't testing the new packages yet. I guess we're waiting on:
gst-plugins-base1.0 (1.13.1-1) experimental; urgency=medium
** Changed in: gst-plugins-base1.0 (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Thanks Laney. It was in the back of my mind -- I knew upstream had done
a fix identical to mine, but they just moved it. I had not stopped to go
looking for it...
I can verify everything seems to be working with the latest bionic
updates.
** Also affects: gst-plugins-base1.0 (Ubuntu)
Daniel - with 1.13 -gl has moved from -bad to -base. I think that
b769f022619db7b46851986494621492342eaafb is the same as your fix, so I
have dropped your patch. Please let me know if that's wrong somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: totem
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage
** Changed in: mutter
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage
** Changed in: mutter
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: steam (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
** Also affects: steam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
** Tags added: wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage notifications about this bug go to:
Thanks. I learned something new.
Yes, as you discovered I would only expect VLC hardware decoding to work
in a "Ubuntu on Xorg" session with the VLC option "VA-API video decoder
via X11". Because that's the only combination of session and VLC option
that's even theoretically compatible at all.
Andrea, it appears bug 1716800 already covers the problem to some
extent. I suggest you subscribe there instead.
This bug is already conflated by different issues in different players.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: vlc (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage
Generate video h264 file (however I get the same behavior for every file I
tested).
$ ffmpeg -f lavfi -i color=white;fade=t=out:d=10 -t 10 -c:v libx264 test.mkv
Within the "Ubuntu" session
Selecting the option "Decoder VA-API throught DRM"
$ vlc test.mkv
VLC media player 2.2.6 Umbrella
Andrea,
What errors do you see in VLC relating to this bug?
** Also affects: vlc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: vlc (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: vlc
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage
** Changed in: mutter
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage notifications
It appears forwarding was blocked by uncertainty around comments made by
the upstream reporter saying he would not accept it (although I'm not
sure he himself is upstream):
https://bugzilla.gnome.org/show_bug.cgi?id=783169#c7
At the time I ignored that comment because it's not a good enough
What is the plan for this "Forwarded: no" patch in gst-plugins-bad?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To
Please ignore above comment, my bad.
(- to save some time on fresh install of 17.10 I copied mpv.conf from 16.04
It has an autofit-larger option for the psuedo-gui that isn't compatible with
wayland.
Sorry..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
In Regards to mpv:
While vaapi has now been enabled please note that in a 'wayland' session mpv
will not work properly with vaapi from the nautilus context menu. Only audio
will work, no video.
The issue seems to be --player-operation-mode=pseudo-gui
Not sure what you all can do about this..
This bug was fixed in the package mpv - 0.26.0-3ubuntu1
---
mpv (0.26.0-3ubuntu1) artful; urgency=medium
* Prefer Wayland over X11, so if both are present (e.g. Xwayland) then
VA-API gets a display type that works (LP: #1698287)
* Enable hardware acceleration by default (LP:
Update:
* totem is fixed by the gst-plugins-bad fix released today.
* mpv is fixed by the patch proposed in bug 1708102.
* chromium needs to either be ported to native Wayland, or for libva to be
enhanced with DRI3 support. There are no workarounds for Chromium other than to
avoid Wayland and
Doug, and all:
https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1708102/comments/3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell
Doug,
A couple of my fixes have landed today, as well as ffmpeg 3.3 which
fixes most of mpv's acceleration problems. However your comment reminds
me there's another bug with mpv I need to open and fix... mpv will by
default try to use the X11 display provided by Xwayland and ends up with
Actually comment #16 doesn't need a new bug. This bug will do fine for
that. See comments #3 - #4.
** Changed in: mpv (Ubuntu)
Status: Triaged => In Progress
** Changed in: mpv (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gstreamer-vaapi (Ubuntu)
I am going to work on additional patches so that by the time 17.10 is
released all you will need is:
mpv myvideo.mp4
** Description changed:
The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
Gnome Shell). But it refuses to load when in a Wayland session:
$ totem
This bug was fixed in the package gst-plugins-bad1.0 - 1.12.2-1ubuntu2
---
gst-plugins-bad1.0 (1.12.2-1ubuntu2) artful; urgency=medium
* Prefer native Wayland over X11/Xwayland if both are available. This
fixes VA-API initialization failure in Gnome Shell Wayland sessions
Regarding the mpv in artful:
You can currently get some vaapi support in wayland session, you'd need to use
hwdec=vaapi-copy
Not as effective as hwdec=vaapi but I don't think they'll be changing that
(commit noted), in near future.
--
You received this bug notification because you are a member
The simple version of the patch builds fine in a ppa, sponsoring that
one
** Changed in: gst-plugins-bad1.0 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the "big" patch I used in testing (includes makefile fix that I
suspect archive doesn't need, but my machine does).
** Patch added: "gst-plugins-bad1.0_1.12.2-1ubuntu2-big.debdiff"
Here's the preferred clean fix. Doesn't build on my machine, but I
suspect it will build in archive :S
** Patch added: "gst-plugins-bad1.0_1.12.2-1ubuntu2-small.debdiff"
** Also affects: gst-plugins-bad1.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gst-plugins-bad1.0 (Ubuntu)
Importance: Undecided => High
** Changed in: gst-plugins-bad1.0 (Ubuntu)
Status: New => In Progress
** Changed in: gst-plugins-bad1.0 (Ubuntu)
vaapi in mpv in a wayland session was broken due to this commit
https://github.com/mpv-player/mpv/commit/bba08e38ff9842c4edf9da6a1d54066a01acd982
Testing here a reversion to allow, seems ok for at least me to date, as in
** Changed in: mutter (Ubuntu)
Status: In Progress => Triaged
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter
Status: Unknown => Confirmed
** Changed in: mutter
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to
** Package changed: gst-plugins-base1.0 (Ubuntu) => mutter (Ubuntu)
** Also affects: mutter via
https://bugzilla.gnome.org/show_bug.cgi?id=775698
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
More progress: gst-play-1.0 fails on Gnome Shell Wayland only (and not
in Weston) because of a mutter problem (or arguably the gstreamer-vaapi
plugin assuming that mutter should support it):
https://bugzilla.gnome.org/show_bug.cgi?id=775698
** Bug watch added: GNOME Bug Tracker #775698
** Changed in: gst-plugins-base1.0 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gst-plugins-base1.0 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gst-plugins-base1.0 (Ubuntu)
Status: New => In Progress
** Changed in: totem (Ubuntu)
** Description changed:
The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
Gnome Shell). But it refuses to load when in a Wayland session:
$ totem bbb_sunflower_1080p_60fps_normal.mp4
libva error: va_getDriverName() failed with unknown libva
error,driver_name=(null)
** Changed in: totem
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage
On second thoughts, if we keep this bug about decoding flaws, and deal
with all the display flaws elsewhere then we might be able to close some
tasks here...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Without sounding too defeated, I think it might be a good idea for us to
not use the patch in comment #5 any time soon. The reason is that while
the patch is correct, it triggers bigger issues in clutter-gst. And that
starts to make me think I'm going too deep down this rabbit hole.
It probably
The attachment "fix-1698287-for-totem-via-gstreamer-vaapi.patch" seems
to be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
Here's my first attempt at a fix for totem. Although fixing this bug in
totem then triggers corruption (bug 1701463) as well as higher CPU, so
still needs more verification to see if the higher CPU is just a side-
effect of poor plugin choice or related to the corruption...
** Patch added:
** Changed in: totem
Status: Unknown => Incomplete
** Changed in: totem
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to
** Bug watch added: GNOME Bug Tracker #783169
https://bugzilla.gnome.org/show_bug.cgi?id=783169
** Also affects: totem via
https://bugzilla.gnome.org/show_bug.cgi?id=783169
Importance: Unknown
Status: Unknown
** Description changed:
The Intel i965 VA-API driver works well in
** Changed in: gstreamer-vaapi (Ubuntu)
Importance: Undecided => Medium
** Changed in: libva (Ubuntu)
Importance: High => Medium
** Changed in: totem (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: gstreamer-vaapi (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: gstreamer-vaapi (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libva
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698287
Title:
VA-API fails to initialize in a Gnome Shell Wayland session
To manage notifications
** Changed in: libva (Ubuntu)
Status: In Progress => Triaged
** Changed in: libva (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mpv (Ubuntu)
Status: In Progress => Triaged
** Changed in: mpv (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: libva (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: libva (Ubuntu)
Importance: Undecided =>
58 matches
Mail list logo
