video-editing
Here are 108 public repositories matching this topic...
Describe the new feature:
The openshot_qt file contains to much personal information.
So one has to anomize it before submitting it, a lot of work
Describe the solution you'd like:
Openshot should anomize all filenames and (sub)foldernames in the qt log file, because they can contain personal info. I believe this is a GDPR issue.
-
Updated
Aug 26, 2020 - Haskell
-
Updated
Aug 17, 2020 - Java
Describe the bug:
The "Pixelization" values is not linear. It starts with 0,0 which means "no pixelization at all", through 0,9" which means "heavy pixelization", but ends with "1,0" which does not pixelate at all (i. e. 0,0 and 1,0 behave the same). This makes it hard to understand for the user, and hard to prevent failures in usage.
Steps to reproduce the behavior:
- Use Pixe
-
Updated
May 14, 2020 - Objective-C
-
Updated
Feb 21, 2019 - Java
-
Updated
Jun 19, 2020 - JavaScript
-
Updated
Jul 28, 2020 - Java
-
Updated
May 12, 2020 - Objective-C
-
Updated
Feb 8, 2020 - Go
-
Updated
Jun 14, 2017 - Objective-C
-
Updated
Aug 12, 2019 - Kotlin
-
Updated
Aug 25, 2020 - Lua
-
Updated
Mar 2, 2020 - Python
-
Updated
Aug 25, 2020 - Python
Add an option to specify the output blob format for Movie#record. Right now, it is hardcoded as video/webm.
-
Updated
Aug 14, 2020 - TypeScript
-
Updated
Jun 18, 2020 - Swift
-
Updated
Aug 28, 2020 - Kotlin
-
Updated
Aug 1, 2020 - JavaScript
-
Updated
Aug 19, 2020 - Swift
-
Updated
Dec 4, 2018 - Python
-
Updated
Nov 24, 2018 - Python
-
Updated
Aug 22, 2020 - Java
-
Updated
Jan 28, 2020 - JavaScript
-
Updated
Jun 1, 2020
Improve this page
Add a description, image, and links to the video-editing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the video-editing topic, visit your repo's landing page and select "manage topics."
FFMPEG supports a "video file name" of
image-%04d.png, and moviepy accepts this inVideoFileClip()which is great. But unfortunately it assumes 25 fps, and I don't see any way to change that. I can callclip=clip.set_fps(24)but that doesn't change the duration - I think it just skips frames.It would be great if
VideoFileClipcould accept an optionalfpsarg for this case.