After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 639285 - gnloperation
gnloperation
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gnonlin
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
Edward Hervey
Depends on:
Blocks:
 
 
Reported: 2011-01-12 05:50 UTC by Lane Brooks
Modified: 2011-01-12 08:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
python script (2.63 KB, text/x-python)
2011-01-12 05:50 UTC, Lane Brooks
Details

Description Lane Brooks 2011-01-12 05:50:51 UTC
Created attachment 178110 [details]
python script

When running a gnlcomposition with two video sources and a gnloperation containing a mixer to control the transition from one source to the other, at certain framerates and at the very end of the transition to the second source, the first source will flash a single frame over the second source.

The attached python script shows the problem. In this script, the framerate is set to 30000/1001. The first source runs from time 0 to 5 seconds. The second source runs from time 1 to 6 seconds. The mixer runs from time 1 to 5 and a controller sweeps the alpha of the second source to create a 4 second fade from the first source to the second source. If you watch closely, you will see that at the very end of the transition (at time 5 seconds), that the first source flashes what appears to be a single frame. You have to watch closely at time 5 seconds to see it. If you change the frame rate (for example to 30000/1000), then it does not happen.

The python script is completely self-contained and should run for you without any issues.

Is this a problem with time quantization in the scheduler in gnonlin? Or am I doing something wrong?
Comment 1 Edward Hervey 2011-01-12 08:04:31 UTC
The bug seems to be in videomixer, if you use videomixer2 instead it works fine.