Bug 552212 - Unable to record screencast at full size
Summary: Unable to record screencast at full size
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: istanbul
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jef Spaleta
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-04 11:30 UTC by Petr Šplíchal
Modified: 2016-06-01 01:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 18:34:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Petr Šplíchal 2010-01-04 11:30:41 UTC
Description of problem:

While I was able to record screencasts in Fedora 10 at full size,
with the latest Istanbul package running under Fedora 12 (on
exactly the same hardware) I get audio distorted and video at
about 1 frame per 3 seconds. The script takes up almost all cpu.

Version-Release number of selected component (if applicable):
istanbul-0.2.2-13.fc12.i686

How reproducible:
Always

Steps to Reproduce:
$ istanbul -r test.ogg --coords 0,0,1680,1050 --video-size full
$ or click the record icon in gnome panel
  
Actual results:
Distorted audio & video.

Expected results:
Nicely recorded screencast as before.

Additional info:
final pipeline: oggmux name=mux ! filesink location=test.ogg
istximagesrc name=videosource display-name=:0.0 screen-num=0
startx=0 starty=0 endx=1679 endy=1049 use-damage=false
show-pointer=false !  video/x-raw-rgb,framerate=10/1 ! videorate !
ffmpegcolorspace !  videoscale method=1 !
video/x-raw-yuv,width=1680,height=1050,framerate=10/1 ! theoraenc
! queue ! mux. gconfaudiosrc name=audiosource ! audioconvert !
vorbisenc ! queue ! mux.

I get the same results with the latest gstreamer & libvorbis
packages from updates-testing repo:

    libvorbis-1.2.3-4.fc12.i686
    gstreamer-0.10.25.1-3.fc12.i686

cpuinfo: Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz

Comment 1 Bug Zapper 2010-11-04 01:54:11 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Matt McCutchen 2010-11-12 05:58:59 UTC
I have the same problem with istanbul-0.2.2-15.fc14.x86_64 on my Dell Latitude D620.  When I record at full size (1440 x 900), I get one frame every few seconds.  The problem did not occur with Fedora 10 on the same machine.

Comment 3 Jef Spaleta 2010-11-12 18:23:47 UTC
Matt,

A little test for you.  can you take the final gstreamer pipeline that istanbul is using and get the same poor result under gst-launch?

My gut feeling is that there's a real problem in the istximagesrc gstreamer module as shipped as part of upstream istanbul.  


I'm going to try to find someone with more experience building gstreamer pipelines and see if there is a more standard module now available as part of the gstreamer package set that does what istximagesrc is doing.  

-jef

Comment 4 Matt McCutchen 2010-11-12 22:50:22 UTC
(In reply to comment #3)
> A little test for you.  can you take the final gstreamer pipeline that istanbul
> is using and get the same poor result under gst-launch?

How do I do that?  Here is the istanbul output:

$ istanbul
** Message: pygobject_register_sinkfunc is deprecated (GstObject)
DEBUG: final pipeline: istximagesrc name=videosource display-name=:0.0 screen-num=0 ! video/x-raw-rgb,framerate=10/1 ! videorate ! ffmpegcolorspace ! videoscale method=1 ! video/x-raw-yuv,width=1440,height=900,framerate=10/1 ! theoraenc ! oggmux name=mux ! filesink location=/tmp/tmprAx9dV

This didn't work:

$ gst-launch 'istximagesrc name=videosource display-name=:0.0 screen-num=0 ! video/x-raw-rgb,framerate=10/1 ! videorate ! ffmpegcolorspace ! videoscale method=1 ! video/x-raw-yuv,width=1440,height=900,framerate=10/1 ! theoraenc ! oggmux name=mux ! filesink location=/home/matt/Desktop/test.ogg'
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstIstXImageSrc:istximagesrc0: Internal data flow error.
Additional debug info:
gstbasesrc.c(2550): gst_base_src_loop (): /GstPipeline:pipeline0/GstIstXImageSrc:istximagesrc0:
streaming task paused, reason not-linked (-1)
Execution ended after 16020430 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

Comment 5 Hollis Blanchard 2012-01-04 01:37:25 UTC
Here's my pipeline. I don't get any errors:

gst-launch 'oggmux name=mux ! filesink location=/tmp/tmpVLotBV istximagesrc name=videosource display-name=:0.0 screen-num=0 ! video/x-raw-rgb,framerate=10/1 ! videorate ! ffmpegcolorspace ! videoscale method=1 ! video/x-raw-yuv,width=1920,height=1080,framerate=10/1 ! theoraenc ! queue ! mux. gconfaudiosrc name=audiosource ! audioconvert ! vorbisenc ! queue ! mux.'
Setting pipeline to PAUSED ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock

... but neither is /tmp/tmpVLotBV created. What next?

Comment 6 Fedora End Of Life 2012-08-16 18:35:00 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.