summaryrefslogtreecommitdiff
path: root/README.markdown
AgeCommit message (Collapse)AuthorFilesLines
2016-10-13docs: Add a status section.Jose Fonseca1-0/+9
I've been very busy professionally/personally, which has left very little time to maintain Apitrace. So set the right expectations.
2015-01-20docs: Use relative links.José Fonseca1-4/+6
2015-01-20docs: Split usage instructions into its own file.José Fonseca1-519/+7
2015-01-20docs: Move all docs into their own directory.José Fonseca1-1/+1
2014-05-23Fix typo in README.markdownLawrence L Love1-2/+2
Noticed when reviewing recent comment by jrfonscea in issue #199 referencing "Emitting annotations to the trace" in README.markdown Signed-off-by: Lawrence L Love <lawrencex.l.love@intel.com>
2014-05-02Remove githalytics.com snippet from the readme.José Fonseca1-3/+0
Doesn't do anything useful, now that github is serving the URL as a static image from *.githubusercontent.com , and GitHub now provides some stats.
2014-02-25apitrace documentation: add multiple callsetsLawrence L Love1-0/+1
Documentation update for previous commit: apitrace: Allow multiple --calls and/or --frames input options Signed-off-by: Lawrence L Love <lawrencex.l.love@intel.com>
2014-02-04gltrace: Move GL_EXT_debug_marker/label from GLES to ES specs.José Fonseca1-0/+4
They are also available in GL, and Apple actually advertises them in MacOSX: https://developer.apple.com/graphicsimaging/opengl/capabilities/
2013-11-29add some basic documentation to the backtrace capturing functionality to the ↵Edward Rudd1-0/+18
README.
2013-10-28cgltrace: Use DYLD_FRAMEWORK_PATH instead of DYLD_LIBRARY_PATH.José Fonseca1-1/+1
It seems that from MacOSX 10.9 DYLD_FRAMEWORK_PATH takes precendence over DYLD_LIBRARY_PATH for frameworks. Issue #181.
2013-10-23readme: Add a bit of text describing how to determine the graphics api used ↵José Fonseca1-0/+12
by a windows app.
2013-10-14readme: Mention KHR_debug for GLES too.José Fonseca1-1/+2
2013-10-14readme: Provide a GLEW_KHR_debug example instead of GLEW_GREMEDY_string_marker.José Fonseca1-18/+24
2013-10-14apitrace README.markdown correct some typosLawrence L Love1-15/+16
Reading through some of the documentation, spotted some typos and thought might as well correct them while reading Mostly missing or incomplete words. One section that meant to display code didn't have the correct format to display it as such. Signed-off-by: Lawrence L Love <lawrencex.l.love@intel.com>
2013-10-10Update documentation for object label support.José Fonseca1-9/+22
2013-07-12Aggregate all info on debugging into a single place.José Fonseca1-4/+0
2013-06-16Fix trim doc.José Fonseca1-2/+8
2013-06-15Update homepage link.José Fonseca1-2/+2
See https://github.com/blog/1452-new-github-pages-domain-github-io
2013-05-29Mention both ffmpeg & libav.José Fonseca1-3/+8
2013-05-29Ubuntu 12.04 reports ffmpeg as deprecated, use avconv instead.Nigel Stewart1-1/+1
2013-04-24Add option '--snapshot-format=' to allow write raw RGB directly to stdoutShuang He1-0/+8
This allows to create h264 video with gstreamer-vaapi very fast, and save much more disk space. Using PNM format couldn't reach same performance, since PNM decoding seems inefficient in gstreamer. Following are some experiment data with smokinguns demo 1920x1080 resolution on Ivybridge: 1. With png saving, it runs at around 4.5 FPS, which has compression rate 5.15x against raw RGB data Reference command: glretrace -s snapshot/ smokinguns.trace 2. Using PNM with gstreamer-vaapi, which could run at around 9 FPS, which has compression rate 485x (QP dependent) against raw RGB data. Reference command: glretrace -s - smokinguns.trace | gst-launch-0.10 fdsrc blocksize=409600 ! queue \ ! pnmdec ! videoparse format=rgb width=1920 height=1080 ! ffmpegcolorspace ! queue \ ! vaapiupload direct-rendering=0 ! queue ! vaapiencodeh264 ! filesink location=xxx.264 3. With following command that directly write raw RGB stream and encoded into H264 video, it runs at around 18.5 FPS, which has compression rate 485x (QP dependent) against raw RGB data, Reference command: 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 v2: Use --snapshot-format= option to specify which format is used to write to stdout output v3: Use enum for snapshotFormat and add example in README.markdown
2013-04-12Cleanup README formatting.José Fonseca1-14/+16
2013-04-12qapitrace: Support executing glretrace on a remote target host.Carl Worth1-0/+51
This is supported with a new command-line argument: qapitrace --remote-target <HOST> <trace-file> See README.markdown for documentation on usage and current limitations of this feature.
2013-04-11Rename Android.markdown to Dalvik.markdown.José Fonseca1-1/+1
As README still contains Android information. Minor tweaks.
2013-04-11Improve Android tracing instructionsAlexander Monakov1-62/+3
Tracing of Java applications on Android is quite different from tracing native executables, so move it to a separate file. Add instructions on using wrapping support that appeared in Android 4.0, which simplifies usage of apitrace on Android. Add a reference to adjust-child-env tool that allows to inject tracing library on Android without rebuilding and reflashing recovery image. Signed-off-by: José Fonseca <jose.r.fonseca@gmail.com>
2013-02-22cli: Rename "apitrace retrace" to "apitrace replay".Carl Worth1-6/+6
After some debate on the mailing list, the consensus favors the name "replay" for this operation. Update the documentation in README.markdown to match.
2013-02-05Update Android instructions.José Fonseca1-3/+11
Not really based from personal experience, but rather on what others wrote, namely https://github.com/kanru/apitrace/commit/5948e72a25b1d2df07299db0d49f91677827478b
2012-12-18Update downloads link.José Fonseca1-1/+1
2012-12-07Drop API_D3D10/11.José Fonseca1-0/+7
2012-11-21docs: Eliminate most references to glretrace.José Fonseca1-14/+8
2012-11-21cli: Auto-detect retrace for dump-images too.José Fonseca1-2/+2
2012-11-16doc: Update examples to use call 0.José Fonseca1-5/+5
Call numbers start from 0, but examples gave the impression it started from call 1.
2012-11-14Update use/mention of options.José Fonseca1-5/+5
2012-10-30Update documentation for D3DPERF_XXXJosé Fonseca1-2/+8
2012-10-30Mention EGL cases on readme.José Fonseca1-3/+8
2012-10-23Attempt to track pages via http://githalytics.com/José Fonseca1-0/+1
See also http://stackoverflow.com/questions/4376560/add-google-analytics-to-github-wiki-pages
2012-10-23Remove links from README.José Fonseca1-59/+0
Content now in http://apitrace.github.com
2012-10-21Link to homepage.José Fonseca1-0/+2
2012-10-18Improvement LD_LIBRARY_PATH explanation.José Fonseca1-8/+11
2012-10-13Mention AMD CodeXL.José Fonseca1-2/+4
2012-08-13Fix markup.José Fonseca1-16/+12
2012-08-09Fix formatting in READMEJames Benton1-1/+2
2012-08-09Updated README with help for using new profiling options.James Benton1-2/+22
2012-07-07Android: add usage instructions for tracing zygote applicationsImre Deak1-0/+61
Signed-off-by: Imre Deak <imre.deak@intel.com>
2012-04-30Update docs.José Fonseca1-1/+1
2012-03-21Document how to use retracediff on Windows.José Fonseca1-3/+7
2012-03-10Remove build instructions link (issue #69).José Fonseca1-3/+3
It is broken on the homepage. Thanks to Mathieu Virbel for pointing this out.
2012-03-10Add a few more links.José Fonseca1-1/+5
2012-03-09Document how to start the gui on a specific call.José Fonseca1-2/+14
2012-03-08Mention WebGL-InspectorJosé Fonseca1-0/+2
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-05 01:57:44 +0000