Hi
user
Admin Login:
Username:
Password:
Name:
Making video streaming interactive, heckling user groups from the clouds!
--client
la
--show
lca_2012
--room Studio 81 --force
Next: 1 Cheap tabloid tricks: The truth about Linux, open source and the media
show more...
Marks
Author(s):
Tim Ansell
Location
Studio
Date
jan Thu 19
Days Raw Files
Start
10:30
First Raw Start
error-in-template
Duration
0:50:00
Offset
None
End
11:20
Last Raw End
Chapters
Total cuts_time
None min.
http://lca2012.linux.org.au/schedule/56/view_talk
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Making_video_streaming_interactive_heckling_user_groups_from_the_clouds.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
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
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
For the last 6 months Tim Ansell has been trying to figure out a live streaming solution for the local user groups he help out with (including Sydney Linux User Group, Sydney Python User Group and Functional Programming Group). The solution had to be turn key and support the latest HTML5 streaming as well as fall back to flash for legacy users. Users participating at home should be part of the action, including the ability to ask questions and heckle! The system has been now used for 3 months and successfully streaming the events to numerous users. Tim will describe the set up that he settled on which uses an open source stack and how to reproduce it for your own user group. This talk will cover the following technologies; * Flumotion and gstreamer, the backbone of the streaming system. * Flowplayer and jwplayer, the front end UI provided to users. * A little bit of AppEngine to serve the front end UI. * Set up scripts for deploying to your favorite cloud hosting provider such as Amazon AWS. * Some custom code to integrate IRC, twitter and the player into one UI.
Comment:
production notes
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
Veyepar
Video Eyeball Processor and Review