Hi
user
Admin Login:
Username:
Password:
Name:
Every Image Has A Purpose
--client
lca
--show
lca2020
--room room_7 15221 --force
Next: 1 Automated acceptance tests for terminal applications
show more...
Marks
Author(s):
Allan Shone
Location
Room 7
Date
jan Tue 14
Days Raw Files
Start
16:55
First Raw Start
error-in-template
Duration
0:25:0
Offset
None
End
17:20
Last Raw End
Chapters
Total cuts_time
None min.
https://lca2020.linux.org.au/schedule/presentation/129/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
mp4
svg
png
assets
release.pdf
Every_Image_Has_A_Purpose.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
Container images come in all shapes and sizes, with some being more useful then others. It's easy to have a one-size-fits-all approach to building images, but there are benefits to tailor making them for each appropriate situation. Images being deployed probably shouldn't be massive, nor should they include development tools, and it's probably unnecessary to run deployed integrations in a development environment. One approach for specifying images is to ask a few questions, naming appropriately along the way.
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