The new effect needs a key<>value store for "name of attribute to change"<>"Amount of the change in i.e. %"
i.e. "x-scale" "50%" , but thats only the amplitude for the x-scale change that is calculated by the effect itself.
The major goal is to have a bouncing video according to the audio amplitude. With the current framework, it's considered to be ultra easy to implement it, as the the below example shows.
the ultimate version of that effect would ask on which part of the audio spectrum it shall react , but that would afford a FFT of that audio track and could be a bit tricky.
Here is an opencode example that does this outside of openshot for one video:
audio_reactive.py
The new effect needs a key<>value store for "name of attribute to change"<>"Amount of the change in i.e. %"
i.e. "x-scale" "50%" , but thats only the amplitude for the x-scale change that is calculated by the effect itself.
The major goal is to have a bouncing video according to the audio amplitude. With the current framework, it's considered to be ultra easy to implement it, as the the below example shows.
the ultimate version of that effect would ask on which part of the audio spectrum it shall react , but that would afford a FFT of that audio track and could be a bit tricky.
Here is an opencode example that does this outside of openshot for one video:
audio_reactive.py