Collaborative Summer X Edit: Difference between revisions
Line 23: | Line 23: | ||
Download the source video/pictures from Summer X Collaborative Edit shared album: [https://photos.app.goo.gl/mWWc7MrJvMfcXn6i8] | Download the source video/pictures from Summer X Collaborative Edit shared album: [https://photos.app.goo.gl/mWWc7MrJvMfcXn6i8] | ||
Download the 2 sound files - the [[Pling]] .mp3 by Jaspertine, and the voiceover - | Download the 2 sound files - the [[Pling]] .mp3 by Jaspertine, and the voiceover - [https://gitlab.com/marcin_ose/collaborative-edit/-/blob/master/Take_3.mp3] |
Revision as of 20:22, 6 April 2021
We are exploring Collaborative Video Edit Protocols using accessible, open source tools. We use Kdenlive for video editing.
How It Works
By downloading a Kdenlive edit file - and the assets used in the edit - anyone can collaborate on a video edit. The asset files do not change. Only the edit file changes. This process can in principle work seamlessly with global collaboration. We use Google Photos for video assets - by creating a Shared Album. The only problem is that audio files must then be stored separately.
Thus, a complete project includes:
- Kdenlive edit file
- Vidoes and photos
- Audio files
Once supporting assets are uploaded and available - and are downloaded by editors - collaborative editing consists of simply passing the lightweight Kdelive edit file back and forth, and versioning that if a large number of editors are working on the project.
From the start - all files must be placed in one folder. No subfolders, as Google Photos Shared Albums do not have folders in them. If the original edit didn't consider this, then the proper directory structure used by the edit must be re-created.
Test Case
See this edit directory structure that was used:
Download the source video/pictures from Summer X Collaborative Edit shared album: [1]
Download the 2 sound files - the Pling .mp3 by Jaspertine, and the voiceover - [2]