-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tweet a clip selection - new feature #74
Comments
Figured out how to convert audio to video. Seems like you need to add an image, and then loop over it. eg
and using fluent ffmpeg
more details here https://trello.com/c/AjGPSIvf Need to decide if just use a default black image, or whether to allow to supply an image?
|
Alternatively if going down the generate an audio wave form video from audio file, then no need to do the looping of the image. (could just add captions) This command seem to work
see video example of effect https://youtu.be/jrY9h9OFBCM |
Next steps considering to add support for audio
|
made some improvement on Got adding support for burnt in captions and audio (with animated wave form) to work. However going to try and do some refactoring/cleaning up before merging to master. It will then be possible to update the module in autoEdit, and try and integrate it (eg generating an srt from the clip selection burn in the captions etc..) Suggestions and help welcome :) |
updated to TweetThatClip 2.0.1 and started integration
|
At textAV 2018 got a chance to work on "Full Fact - tweet that clip" and to refactor and abstract with @jamesdools quickQuoteNode (node refactor of original rails app quickQuote), twitter module, as standalone module
tweet-that-clip
I've then played around with a branch for autoEdit2 -
tweet-that-clip
to see if it was possible to integrate the functionality with autoEdit.
Needs a bit of cleaning up and tidying up but got the basic to work. can make a selection and tweet a clip, see screenshot
Possible room for improvement
At the moment only got it working for electron, unsure whether is worthwhile to extend support for the adobe panel as well?
UI/UX could do with some improvements. just went for simplest to implement, anyway thought I'd open this issue in case anyone has any thoughts on this, while I am still working on it.
figure out how to properly convert an audio file to video (as in having a video track, not just changing the file extension) with ffmpeg, so that it can support audio files as well. at the moment only support video files.
it is also possible to burn captions, for silent video, see
captions_burner
earlier prototype.The text was updated successfully, but these errors were encountered: