Hi
user
Admin Login:
Username:
Password:
Name:
OWIN, an update
--client
dot_net_fringe
--show
dot_net_fringe_2015
--room mezzanine 9630 --force
Next: 1 The Most Important File Format
show more...
Marks
Author(s):
serialseb
Location
Mezzanine
Date
apr Mon 13
Days Raw Files
Start
10:00
First Raw Start
error-in-template
Duration
00:30:00
Offset
None
End
10:30
Last Raw End
Chapters
Total cuts_time
None min.
http://lanyrd.com/2015/dotnetfringe/sdktrc/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
OWIN_an_update.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
OWIN, a set of specifications to decouple servers and applications, can appear challenging to use. Does it work in practice? How do you get a team embracing the componentisation it provides? How do you understand what is going on, and what does the resulting software looks like? If you want to know what's new in the owin specifications and what code can look like when you embrace it and if you want to see Funcs in action, this is a session for you.
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