Collaborative Video Protocol

From Open Source Ecology
Jump to: navigation, search

2021

Method evolves to:

  1. Video libraries on wiki, as Galleries, describing content and providing thumbnail as well as link to source. See Video Assets.
  2. Using Open Source Video Repositories for high quality footage - video and picture.
  3. Using Open Source Soundtrack Repositories, voiceover repos, and sweetener repos
  4. Using the above, the method is simple: start a wiki page using the Collaborative Video Editing Template, and provide a Kdenlive edit file and link to assets.
  5. Assets management involves - all video/media can be stored on Google Photos as shared albums. Soundtracks and voiceovers can also be managed via Google Photos if they are turned into videos.
  6. The secret weapon here is Google Photos, or any online storage site. Public albums can be created for specific videos. That means that all assets live in the grand Google Photos database - which can be federated as shared folders from others. Then, any specific edit creates a new album for that specific video, so that asset manipulation does not involve copying files in the repo: simply albums are used. Anyone who is editing can download that entire album to their desktop.
  7. The key to effective management is to create categories of feed clips that are well organized by topics. Such as for OSE - Machines, People, Swarm Builds, Houses, Collaboration, CAD Design, Classroom Teaching, Workshop Sizzle Reel, Aquaponics, animations, intro-outro sequences - so when editing - these well-organized can literally be matched to an existing scripts - and eventually - video production could literally be automated while retaining extremely high quality. An algorithm for this can be created. Initially, people can do the algorithm, but there is no reason why this couldn't and shouldn't be automated with weak artificial intelligence, then strong.

Next Steps

OSE Individual Edit Protocol 2020

Standad format of an MVP video edit uses Kdenlive and is:

Extras

Collaborative Process Specification

Source materials:

  1. Upload Kdenlive video edit file to a public repo such as a wiki, gitlab, or any of a wide range of public options. Example - https://github.com/OpenSourceEcology/Collaborative-Video-Protocol
  2. Upload video source files to Youtube or other file sharing repositories suuch as Google Photos, PeerTube, or other location.
    1. Youtube is convenient. The original mp4 upload was 720HD. The Youtube download, was also 720HD with no visible downgrade of quality. But file size reduced from 370MB to 45MB - 8x. Thus - editing should be done from the downloaded files. This was for a 4 minute clip - so essentially 10 MB per minute.. YouTube no longer allows downloads.
  3. Upload graphics to a public repository. This can include the OSE wiki if under 1 MB.
  4. Upload sound to a public repository or youtube
  5. With all files uploaded, start a wiki page called Video Name Collaborative Video - with links to the Kdenlive file and all supporting files. This is completely scalable - and files can be anywhere. As long as the links are provided - remote editing can happen.
  6. Use the OSE Forum to discuss edits.
  7. A convenient way to store footage is exemplified here - gallery + thumbnail created manually + link to source video. Seed Home v2 Build Pictures and Video. Collaborative video assets should be part of any development project. Once assets are accessible digitiallyu and organized like an asset bank - creating videos is easy. This can fit with standard OSE protocols of keeping a Work Log and using the Dev+ Template for product development.


Editing:

  1. Download the Kdenlive edit file.
  2. Download all source files - video, graphics, sound, other. Download and save using the exact filename provided - as uploaded by the original author - do not change filenames - so that the Kdenlive edit file recognizes all the source files.
  3. Place them all in the same folder on your desktop - along with your Kdenlive edit file
  4. Begin editing. Work only with downloaded files - not sources from your desktop - to assure that everyone is using identical assets
  5. As soon as you finish your session, upload the cut to the public repo with version control.
  6. To continue editing, download the edit file from the public repo.

Test

Links