- Post
- #1218024
- Topic
- Fan Editor Script File - "Universal Project File"
- Link
- https://originaltrilogy.com/post/id/1218024/action/topic#1218024
- Time
Unless it’s automated. It’s not very useful.
Also, there’s too many variations to really implement to make it practical.
Its a nice theoretical idea.
Firstly, thanks for taking the time to reply. I am looking for input.
I don’t know what do you mean “automated” so let me take a stab at it.
For the end user, the process would look like this:
- Download the edit script file.
- Rip the source material (ripping could be built into the scripting tool)
- Launch the script processing tool, specify the output format requested (or use defaults) and press “Process.”
- Watch the fan edit
To create the script file, we could either:
- Create a tool that would scan the finished fan edit and create a script for the cut list for example.
or… - Convert a project file from one of the editors.
or a combination of both if some of both
Variations…
I’m new here so I don’t know how complex the fan edits get but I have downloaded a few fan edits like one for Prometheus, HP 1 & 2, Rogue One (Rise of the Rebellion) and The Force Awakens. The tool I envision could re-create all of those using a combination of Avisynth and FFMpeg. No tool will Never be THE single answer to all fan edits but for the ones that use only 1-3 source files, I think it could work without being too complex to use.
For me, the edits I listed above are my “official” versions of the movies. I don’t watch the originals anymore so I would like to bring these to as wide an audience as possible.
The thing that I like the most about this idea is the ease of distribution, the option to “tweak” a fan edit without re-creating the entire thing and the possibility for a group of users to turn suggestions into a fan edit with everyone taking on just part of the project. (i.e. Opensourced fan edits)
Am I still way off base here?