Hi
user
Admin Login:
Username:
Password:
Name:
See Docs Run. Run, Docs, Run!
--client
pytn
--show
pytn2014
--room Room_400 2864 --force
Next: 1 JavaScript all the Things
show more...
Marks
Author(s):
Catherine Devlin
Location
Room 400
Date
feb Sat 22
Days Raw Files
Start
13:35
First Raw Start
error-in-template
Duration
00:35:00
Offset
None
End
14:10
Last Raw End
Chapters
Total cuts_time
None min.
http://pytennessee.org/schedule/presentation/35/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
See_Docs_Run_Run_Docs_Run.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
Code executes. Docs just sit there looking pretty. Now it's time to blur that boundary! Tools like the IPython Notebook, Sphinx, dexy, and old-fashioned doctests blend code with docs, making package docs, educational materials, and system-level docs more engaging, relevant, and trustworthy.
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