Difference between revisions of "How to make screencasts on Sugar"

From Sugar Labs
Jump to navigation Jump to search
(The wiki 'what links here' feature depends on intrawiki link formatting and fails to find pages that are linked through the full URL. Please add value and be cautious and more fully informed when removing or obscuring content.)
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==steps==
+
==RecordMyDesktop steps==
1) get Sugar installed and internet connection working
 
  
2) go to terminal (can be found in list of activities)
+
I found this page [http://wiki.sugarlabs.org/go/Activities/Screencast Activity Screencast!] Must research and test!
 +
-------
  
3)go to root by typing <code>su</code>
+
# Get Sugar installed and internet connection working
 +
# Go to terminal (can be found in list of activities)
 +
# Go to root by typing  
 +
  <code>su</code>
 +
You are looking for [http://recordmydesktop.sourceforge.net/about.php RecordMyDesktop]. Read the very old [http://recordmydesktop.sourceforge.net/manpage.php help pages]. They'll give you some clues to the operation of RecordMyDesktop(RMD) though I must say that after playing with RMD on Sugar I much prefer RMD on Ubuntu.
  
4)type <code>yum update</code>
+
#Type:
 
+
<code>yum install recordmydesktop</code>  
5)wait a bit to pull down changes. Keep in mind the size of your drive. Mine is 4Gigs so plenty of room...
+
RecordMyDesktop is command line only. Use GTK below for the GUI.
 
+
<code>yum install gtk-recordmydesktop</code>
6)Accept changes is up to you.
+
or this one written in [http://en.wikipedia.org/wiki/Python_%28programming_language%29 Python] WHICH should be more stable on Sugar as Sugar is written in Python... though amazingly qt-recordmydesktop asked for 27M of space where gtk-recordmydesktop only asked for a few 100K! Bemasc at the IRC rightly pointed out that QT is a big app and that there are huge buffering considerations for using RMD in general.
 
+
<code>yum install qt-recordMyDesktop</code>
7)type <code>yum install recordmydesktop</code> or <code>yum install gtk-recordmydesktop</code>
 
  
 +
==GStreamer==
 +
Bemasc found this. Test it on the command line. Let us know.
 +
<Code>gst-launch ximagesrc ! video/x-raw-rgb,framerate=5/1 ! ffmpegcolorspace ! theoraenc ! oggmux ! filesink location=desktop.ogg
 +
</code>
  
 
==Why make screencasts?==
 
==Why make screencasts?==
 
Video, when done properly, can explain a lot more than text. And video can overcome some of the language barriers by SHOWING people what to do and their expected outcomes.
 
Video, when done properly, can explain a lot more than text. And video can overcome some of the language barriers by SHOWING people what to do and their expected outcomes.
  
==Possible errors you may encounter==
+
==Possible errors you may encounter with RecordMyDesktop==
<verbatim>[root@localhost liveuser]# gtk-recordMyDesktop  
+
<nowiki>[root@localhost liveuser]# gtk-recordMyDesktop  
/usr/lib/python2.6/site-packages/recordMyDesktop/rmdMonitor.py:10: DeprecationWarning: The popen2 module is deprecated.  Use the subprocess module.
+
 
 +
/usr/lib/python2.6/site-packages/recordMyDesktop/rmdMonitor.py:10: DeprecationWarning: The popen2 module is deprecated.  Use the subprocess module.
 
   import popen2
 
   import popen2
 
/usr/lib/python2.6/site-packages/recordMyDesktop/rmdSimple.py:223: DeprecationWarning: os.popen3 is deprecated.  Use the subprocess module.
 
/usr/lib/python2.6/site-packages/recordMyDesktop/rmdSimple.py:223: DeprecationWarning: os.popen3 is deprecated.  Use the subprocess module.
Line 33: Line 41:
 
   option to change this behavior. You can then get a meaningful
 
   option to change this behavior. You can then get a meaningful
 
   backtrace from your debugger if you break on the gdk_x_error() function.)
 
   backtrace from your debugger if you break on the gdk_x_error() function.)
</verbatim>
+
</nowiki>
 
* No known workaround for this yet.
 
* No known workaround for this yet.

Latest revision as of 20:15, 19 December 2016

RecordMyDesktop steps

I found this page Activity Screencast! Must research and test!


  1. Get Sugar installed and internet connection working
  2. Go to terminal (can be found in list of activities)
  3. Go to root by typing
 su

You are looking for RecordMyDesktop. Read the very old help pages. They'll give you some clues to the operation of RecordMyDesktop(RMD) though I must say that after playing with RMD on Sugar I much prefer RMD on Ubuntu.

  1. Type:
yum install recordmydesktop 

RecordMyDesktop is command line only. Use GTK below for the GUI.

yum install gtk-recordmydesktop

or this one written in Python WHICH should be more stable on Sugar as Sugar is written in Python... though amazingly qt-recordmydesktop asked for 27M of space where gtk-recordmydesktop only asked for a few 100K! Bemasc at the IRC rightly pointed out that QT is a big app and that there are huge buffering considerations for using RMD in general.

yum install qt-recordMyDesktop

GStreamer

Bemasc found this. Test it on the command line. Let us know.

gst-launch ximagesrc ! video/x-raw-rgb,framerate=5/1 ! ffmpegcolorspace ! theoraenc ! oggmux ! filesink location=desktop.ogg

Why make screencasts?

Video, when done properly, can explain a lot more than text. And video can overcome some of the language barriers by SHOWING people what to do and their expected outcomes.

Possible errors you may encounter with RecordMyDesktop

[root@localhost liveuser]# gtk-recordMyDesktop /usr/lib/python2.6/site-packages/recordMyDesktop/rmdMonitor.py:10: DeprecationWarning: The popen2 module is deprecated. Use the subprocess module. import popen2 /usr/lib/python2.6/site-packages/recordMyDesktop/rmdSimple.py:223: DeprecationWarning: os.popen3 is deprecated. Use the subprocess module. (stdin,stdout,stderr)=os.popen3(xwininfo_com,'t') The program 'gtk-recordMyDesktop' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 3927 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

  • No known workaround for this yet.