crs-tools
Concept: Webcut
Issue migrated from trac ticket # 48
component: webapp | priority: major | keywords: webcut
2014-01-06 18:21:28: @pegro created the issue
If the recording infrastructure is able to provide proxy files of the recorded HQ source files, "webcut" may be possible.
Initial idea:
- recording DV or TS in high quality
- recording MP4 HLS style proxy files playable in web browsers (MP4 with H264)
- use web player to delimit video tracks and store resulting cut positions as ticket properties
Challenges:
- sufficient web player with accurate time resolution
- synchronized recordings and proxy files
2014-01-18 18:26:17: @a-tze commented
One opportunity has to be mentioned here: The proxy files should be generated in a way that they can serve as a "-c:v copy"-style source for e.g. the LQ release files, so that the CPU ticks used for transcoding are not completely lost.
This would also lead to a much faster encoding of LQ files so that the final QC check happens "earlier" in the timeline of the automated processing of a certain event. This way erros can be detected much earlier, which saves CPU time by not transcoding files from broken source material.
For the challenge of synchronizing recordings and proxy files there are currently 2 ideas:
- transcode recorded chunks directly after recording
- record using melt and multi-consumer (to check: synchronouos segmentation?)
2014-07-30 01:08:47: @a-tze commented
A proof-of-concept cut-player has been built by bjoern:
http://nixda.biz/voc/foo/index3.html
2014-07-31 00:03:02: bjoern commented
i think the next step would be to provide an API bz the tracker to submit the cutin/cutout frame markers to the ticket. the values could then be used by the encoder directly or fetched by a script an fed into the fuse-vdv filesystem for cutting.
btw: another version of the cut page: http://nixda.biz/voc/cut3.html
2014-08-05 10:01:46: @jjeising commented
@bjoern: I think webcut should be integrated into the tracker.