Over the past few months, libopenshot, libopenshot-audio, and openshot-qt (the UI) have all seen new source code releases to the open-source community. At some point in the distant future, I might even release the OpenShot Player as a stand-alone application, and compete with VLC.
=) I never set out to build a video player, but now that I have one, it’s going to be a lot of fun playing around with it. This has been one of the more difficult and rewarding parts of building OpenShot 2.0. There are many additional features I would like to add to this screen, but for now, it is complete and functional, and supports just about every combination of (resolution, frame rate, sample rate, bit rates, formats, video codecs, audio codecs, etc…)ĭue to the numerous performance improvements with libopenshot, real-time previews are finally working well, and are able to keep up with many concurrent layers of HD video and many effects in real-time (on a decent computer). It is easy-to-use, very flexible, and supports over 100 video formats & codecs. This dialog is now completed, and works much like the one in OpenShot 1.X. This took many, many weeks of work, but resulted in some fantastic things: Super fast processing of images, fast rotation, fast distortion, fast pixel manipulation, and great multi-thread support!Īn important feature of a video editor is being able to export your new creation. Not having many options left (and not having any more time left to mess with it), I decided to move to Qt5’s QImage, and reprogram all image manipulation code in libopenshot. I consider both of these issues show-stopping! Performance Issues - Certain image manipulation routines, such as rotation (a type of distortion), took a crazy amount of processing time (0.5 to 1.5 seconds per frame).There were a couple workarounds I came up with, but they were just as ugly. The result was a really ugly deadlock, freezing the execution of the program. OpenMP Deadlocks - libopenshot uses OpenMP to accelerate certain parts of the video editing pipeline, and this approach was colliding with certain internal ImageMagick functions, which also uses OpenMP.ImageMagick++, which is a C++ library for manipulating images, and deeply integrated with libopenshot, hit me with the following: Performance Improvements - Image ManipulationĪs everything started to really come together, and I was able to start testing more complex functionality from the UI, a really big, show-stopping type of issue was discovered.
0 kommentar(er)
