Merge branch 'libbacktrace'

[apitrace] / README.markdown

diff --git a/README.markdown b/README.markdown
index 4bf809e9e0946d5cc0aac360852ea86229a608f6..03f9e886bd57b048abd1fbfa860ee97fa07d01b4 100644 (file)
--- a/README.markdown
+++ b/README.markdown
@@ -277,6 +277,14 @@ You can make a video of the output by doing
     apitrace dump-images -o - application.trace \
     | ffmpeg -r 30 -f image2pipe -vcodec ppm -i pipe: -vcodec mpeg4 -y output.mp4
 
+Recording a video with gstreamer
+--------------------------------------
+
+You can make a video of the output with gstreamer by doing
+
+    glretrace --snapshot-format=RGB -s - smokinguns.trace | gst-launch-0.10 fdsrc blocksize=409600 ! queue \
+    ! videoparse format=rgb width=1920 height=1080 ! queue ! ffmpegcolorspace ! queue \
+    ! vaapiupload direct-rendering=0 ! queue ! vaapiencodeh264 ! filesink location=xxx.264
 
 Trimming a trace
 ----------------
@@ -418,10 +426,9 @@ Or on Windows:
     python scripts\retracediff.py --retrace \path\to\glretrace.exe --ref-env TRACE_LIBGL=\path\to\reference\opengl32.dll application.trace
 
 
-[![githalytics.com alpha](https://cruel-carlota.pagodabox.com/c1062ad633aa7a458e9d7520021307e4 "githalytics.com")](http://githalytics.com/apitrace/apitrace)
-
 Advanced GUI usage
 ==================
+
 qapitrace has rudimentary support for replaying traces on a remote
 target device. This can be useful, for example, when developing for an
 embedded system. The primary GUI will run on the local host, while any
@@ -429,22 +436,22 @@ replays will be performed on the target device.
 
 In order to target a remote device, use the command-line:
 
-       qapitrace --remote-target <HOST> <trace-file>
-    
+    qapitrace --remote-target <HOST> <trace-file>
+
 In order for this to work, the following must be available in the
 system configuration:
-    
+
 1. It must be possible for the current user to initiate an ssh session
    that has access to the target's window system. The command to be
    exectuted by qapitrace will be:
-    
-       ssh <HOST> glretrace
+
+        ssh <HOST> glretrace
 
    For example, if the target device is using the X window system, one
    can test whether an ssh session has access to the target X server
    with:
 
-       ssh <HOST> xdpyinfo
+        ssh <HOST> xdpyinfo
 
    If this command fails with something like "cannot open display"
    then the user will have to configure the target to set the DISPLAY
@@ -455,18 +462,21 @@ system configuration:
    this must be configured on the host side so that ssh can be
    initiated without a username.
 
-   For example, if you normally connect with "ssh user@192.168.0.2"
+   For example, if you normally connect with `ssh user@192.168.0.2`
    you could configure ~/.ssh/config on the host with a block such as:
 
-       Host target
-         HostName 192.168.0.2
-         User user
+        Host target
+          HostName 192.168.0.2
+          User user
 
-   And after this you should be able to connect with "ssh target" so
-   that you can also use "qapitrace --remote-target target".
+   And after this you should be able to connect with `ssh target` so
+   that you can also use `qapitrace --remote-target target`.
 
 2. The target host must have a functional glretrace binary available
 
 3. The target host must have access to <trace-file> at the same path
    in the filesystem as the <trace-file> path on the host system being
    passed to the qapitrace command line.
+
+
+[![githalytics.com alpha](https://cruel-carlota.pagodabox.com/c1062ad633aa7a458e9d7520021307e4 "githalytics.com")](http://githalytics.com/apitrace/apitrace)