Support for specific workflows and automation for various movie genres in moviepy? #2048
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow up on #2046 (comment). It's an example of how I envisioned templates, sections, and automation using moviepy. I'm not certain as to whether the actual implementation belongs in a forked version of the library or the main library itself, but I suppose it could be implemented in a fork and then merged over if successful. The basic idea is as follows:
In the /workflows directory:
In the /workflows/automaters directory:
librosa
library and by obtaining waveform information such as energy, beat, and harmonics over time)In the /workflows/sections
Implementations of Section (an unimplemented version, MusicSection, can be found, which will ideally eventually be implemented to determine different orientations depending on factors such as the number of videos in the section, the most prominent waveform/the extent of the most prominent waveform, and various other factors)
In the /workflows/templates directory:
I think if it were to be implemented in this way, it would be accommodating for contribution to different genres of videos as well as different workflows without diluting the core implementation of the library. I'm not sure where the community or maintainers stand on this, which is why I left things unimplemented in places; I think this kind of support could really bolster Moviepy as a library and help contribute to reducing overhead in various video genres, but it would be a fairly large addition and thus should be open to debate. I hope this at least gets the ball rolling though and can help dictate what the next steps should be!