Hi
user
Admin Login:
Username:
Password:
Name:
Debugging: how to survive potential assassination
--client
osdc
--show
osdc2015
--room Derwent_1 10360 --force
Next: 1 The Great Escape : Tunnelling your way to freedom with SSH
show more...
Marks
Author(s):
Paul Wayper
Location
Derwent 1
Date
oct Thu 29
Days Raw Files
Start
11:15
First Raw Start
error-in-template
Duration
00:45:00
Offset
None
End
12:00
Last Raw End
Chapters
Total cuts_time
None min.
http://2015.osdc.com.au/schedule/presentation/15/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Debugging_how_to_survive_potential_assassination.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
It is said that we should always program as if the person who has to maintain our code is a homicidal maniac who knows where we live. This is also true of people who support your program and have to use it. Many will encounter unforeseen problems with your program, and may be homicidal maniacs who can track you down. This talk aims to make it easy to write programs that are easy to support.
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