veyepar: Linux tracing with LTTng

Hi user

Admin Login:

Name: Linux tracing with LTTng
--client fosdem --show fosdem_2014 --room Janson 7619 --force
Prev: 5 Software Archaeology for Beginners
Next: 5 Making the Linux Kernel better (without coding)

show more...

Author(s):	David Goulet
Location	Janson
Date	feb Sat 01	Days Raw Files
Start	13:00	First Raw Start	12:59
Duration	00:50:00	Offset	0:00:39
End	13:50	Last Raw End	14:00
Chapters	00:00
Total cuts_time	47 min.

https://fosdem.org/2014/schedule/event/linux_tracing_with_lttng/
raw-playlist raw-mp4-playlist encoded-files-playlist public mp4 svg png

final audio

assets release.pdf Linux_tracing_with_LTTng.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:
Locked:	clear this to unlock
Locked by:	user/process that locked.
Start:	initially scheduled time from master, adjusted to match reality
Duration:	length in hh:mm:ss
Name:	Video Title (shows in video search results)
Emails:	email(s) of the presenter(s)
Released:	has someone authorised pubication
Normalise:
Channelcopy:	m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:	filename.png
Description:	<p>In the past, a lot of effort has been invested in high performance kernel tracing tools, but now the focus of the tracing community seems to be shifting over to efficient user space application tracing. By providing joint kernel and user space tracing, developers now have deeper insights into their applications. Furthermore, system administrators can now put in place a new way to monitor and debug systems using a low intrusiveness tracing system, LTTng.</p> <p>This presentation explains how LTTng can be used as a powerful development and debugging tool for user space applications taking advantage of this year's exciting new features such as network streaming and snapshots. It demonstrates how open source developers and hackers can use LTTng kernel and user space tracers to create powerful logging systems and easier debugging, thus greatly improving development and maintainability of their project(s).</p> <p>Finally, this talk concludes with the future work we will be doing on LTTng, and how the community can help with improving the project from feedback to very valuable contributions.</p> markdown
Comment:	production notes

2014-02-01/11_59_21.dv Apply: 12:59:21 - 13:01:29 ( 00:02:08 ) S: 12:59:21 - E: 13:01:29 D: 00:02:08 show more...

vlc ~/Videos/veyepar/fosdem/fosdem_2014/dv/Janson/2014-02-01/11_59_21.dv :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	12:59:21		seconds: 0.0 Wall: 12:59:21
Duration	00:02:08
	13:01:29		seconds: 0.0 Wall: 12:59:21
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2014-02-01/12_01_29.dv Apply: 13:01:29 - 13:49:15 ( 00:47:46 ) S: 13:01:29 - E: 13:49:15 D: 00:47:46 show more...

vlc ~/Videos/veyepar/fosdem/fosdem_2014/dv/Janson/2014-02-01/12_01_29.dv :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	13:01:29		seconds: 0.0 Wall: 13:01:29
Duration	00:47:46
	13:49:15		seconds: 0.0 Wall: 13:01:29
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

2014-02-01/12_49_16.dv Apply: 13:49:16 - 14:00:21 ( 00:11:05 ) S: 13:49:16 - E: 14:00:21 D: 00:11:05 show more...

vlc ~/Videos/veyepar/fosdem/fosdem_2014/dv/Janson/2014-02-01/12_49_16.dv :start-time=00.0 --audio-desync=0

	Raw File	Cut List
	13:49:16		seconds: 0.0 Wall: 13:49:16
Duration	00:11:05
	14:00:21		seconds: 0.0 Wall: 13:49:16
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

audio viz

Rf filename:	root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:	check and save to add this

2014-02-01/11_59_21.dv
audio viz

audio viz

2014-02-01/12_01_29.dv
audio viz

audio viz

2014-02-01/12_49_16.dv
audio viz

audio viz

Veyepar Video Eyeball Processor and Review