Same comment as the PR #8 for tk-framework-editorial:
The jaunt_in/out points live inside the cut_in/cut_out points. When transitions are present, cut_in/cut_out essentially become transition_in/transition_out. So these extra jaunt_in/out points, in that case, represent the original cut_in/cut_out points. If we want to keep this functionality as part of tk-multi-importcut and not fork this repo for Jaunt, perhaps we should rename jaunt_in/out to orig_cut_in/out or something similar. However, this is a hack and true support for transitions will most likely use a different approach, so maybe it is a good idea to fork the repo anyway. Opinions?
kporangehat
commented
8 years ago
Same comment as the PR #8 for tk-framework-editorial:
The jaunt_in/out points live inside the cut_in/cut_out points. When transitions are present, cut_in/cut_out essentially become transition_in/transition_out. So these extra jaunt_in/out points, in that case, represent the original cut_in/cut_out points. If we want to keep this functionality as part of tk-multi-importcut and not fork this repo for Jaunt, perhaps we should rename jaunt_in/out to orig_cut_in/out or something similar. However, this is a hack and true support for transitions will most likely use a different approach, so maybe it is a good idea to fork the repo anyway. Opinions?