Shot Core TODO

Shot Core 1: Shot Core + Web Slater Demo

Features

• project import
• scheduling
• monitor
• z cam http client
• z cam ws client
• z cam mjpeg proxy
• listen for camera rec/stop msgs
• send rec/stop msgs to camera
• record network stream to files on/off
• visual slate
• rating
• API support for mini slater remote control
• queue and transfer files from camera when idle
  • handle halt/retry
• impromptu shots
• "rough clip" assembly
• adding a new scene to an existing project
• NTP server/client setup
• z cam standby on/off
• slater web view tested and working on iPad
• pick a LICENSE

Tasks

Core

• Leading 0s in filename
  • e.g.: scene_003_shot_0001_take_003_id_af294d-STREAM.mp4 (999 scenes, 9,999 shots, 999 takes)
• Takes should have a UUID instead of incremental ID
• Slater should advance to next take if remotely recorded
• Option to copy take files to NAS URL
• Better Error handling for copying files
• Make default ZCAM_URL=http://10.98.33.1
• Do not require port in ZCAM_URL=http://10.98.33.1:80
• Bug with port 3000 already in use
• download thumbnail ("screennail") on cut, instead of in downloader

UI

• Takes Per Scene view
• Take Detail view
• The information on takes should be expanded
• Shot Detail view
• Schedule should show which shots already have takes
  • by a color like basically crossed out

Shot Core 2: Audio

• record audio
• audio metering levels to ws
• stats
• render real metadata in visual slate
• hardware
• linux machine config (e.g.: shot-core-image disk image)

FUTURE

• Custom ZCAM Firmware to support MD5 Hash or https://cyan4973.github.io/xxHash

• multi-camera slater support

  • press record on minislater, shot core starts takes, tells all cameras to start recording
  • multi-shot in a single recording session
    • e.g.: three cameras rolling at the same time, recording shot 1, 2 and 3
      • three different shots, three different takes

• multi-units

  • instances of shot core at different locations
  • distributed, merge back into the "master" shot core