Fix lack of EOS signal when using PyGI + GStreamer
Bug #861630 reported by
Jason Gerard DeRose
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Novacut |
Triaged
|
Critical
|
Unassigned | ||
Bug Description
In the 11.09 release we ported to Python3 and PyGI, which went quite smoothly all in all.
But one problem is we aren't getting the EOS signal from our render pipeline. Although renders are working, we don't know when they finish, so the render backend in currently broken.
One way or another, this needs to be fixed... and the correct solution might be to port to GStreamer 1.0!
As GStreamer 1.0 will be parallel installable with 0.10, we could safely deliver GStreamer 1.0 to Oneiric users via our PPAs.
GStreamer 1.0 is getting lots attention as far as G-I issues in general, things they can't change in 0.10 without breaking backward compatibility.
Revision history for this message
| Jason Gerard DeRose (jderose) wrote | #1 |
| Changed in novacut: | |
| milestone: | 11.10 → 11.11 |
| Changed in novacut: | |
| milestone: | 11.11 → 12.01 |
| Changed in novacut: | |
| milestone: | 12.01 → 12.02 |
| Changed in novacut: | |
| milestone: | 12.02 → 12.03 |
To post a comment you must log in.
I filed an upstream GStreamer bug about this, and it sounds like it's an issue with pygobject:
https:/
This is the pygobject bug my bug was marked as a duplicate of:
https:/