Openshot Video Editor Download Old Version

[Joslyn Moreci]

OpenShotis a free video editing software. In 2017, developpers updated it in a QT version. Recently I moved to Ubuntu 18.04 instead of 16.04 so I had no choice and had to use the new version of OpenShot. But, this version is paradoxaly slow and not precise at all. So can you help me to downgrade to the former version 1.4.3(for instance) instead of 2.x version(the new one) ?

I tested many alternative like Shotcut, Flowblade or Kdenlive but I prefere the old OpenShot. I know that what I ask for can create an unstable system but I really need it for school and if I can't install it on 18.04 I have to downgrade to 16.04.

EDIT : I read this : Openshot Video Editor 1.4.3-1.2 - How to stop it auto updating to v 2.43 etc in 18.04 LTS but the person who sent the question didn't explained how he installed OpenShot and the dependances.

when I run :sudo apt-get -f installIt give back :Lecture des listes de paquets... FaitConstruction de l'arbre des dpendances

Lecture des informations d'tat... FaitCorrection des dpendances... a chou.Les paquets suivants contiennent des dpendances non satisfaites : openshot : Dpend: melt mais il n'est pas install Dpend: python-httplib2 mais il n'est pas install Dpend: python-imaging mais il n'est pas installable Dpend: python-mlt5 mais il n'est pas installable ou python-mlt3 mais il n'est pas installable ou python-mlt2 mais il n'est pas installable Dpend: python-pygoocanvas mais il n'est pas installable Dpend: python-xdg mais il n'est pas install Dpend: python-support (>= 0.90.0) mais il n'est pas installable Recommande: openshot-doc mais il n'est pas installE: Erreur, pkgProblem::Resolve a gnr des ruptures, ce qui a pu tre caus par les paquets devant tre gards en l'tat.E: Impossible de corriger les dpendances

When I finished the video, it looks like the video should be 1:53. However, when I hit the red circle at the top, and it saves the project, it saves it a minute + longer.

When I "export" it, as if I were to save a version to post, it does the same thing.

What version of MLT have you ? If you are on Oneiric, the official version have a lot of regression. For sample, you can't export on DVD format. See here how to resolve that : +faq/1859

And another good link if you are on Ubuntu : How to get the last version of MLT : +faq/1861

I ran "openshot my-finished-video.osp &" from the command line. Then I chose File->Export (does same as the red button, I assume?), and the Export control panel came up. In the Profile field, I selected "Web". This caused the other fields to automatically fill in with default values:

It took about 8 minutes to complete the export. The resultant file "my-finished-video.mov" was 136 MB large. When I play it with mplayer from the command line, the video lasts about 10 minutes as described above. I also tried exporting with the "YouTube" profile and its defaults, which produced a .mpeg video, but it also lasted about 10 minutes. I also tried playing them through my browser (Firefox), just to be sure, and the length was the same.

"I created some new tracks and moved there the clips in the old ones. I deleted the old tracks and the exported video has the correct length now. It seems that something was stored in the old tracks at high timeline positions even if I couldn't see it."

Since I spent a fair amount of time in the OpenShot user forums searching for a solution to this, here are all the posts that seemed like they might have something relevant, ending with the one above:

Goodness I must be tired of looking at this screen. I wish there were a way to edit my comments in Launchpad Answers. Anyway, even though it's a minor and probably irrelevant correction, even #6 above is not *quite* right -- the solution that worked is actually the second one down in the list. Not that this matters, since I described the solution before that anyway. I'm going to walk away from the computer for a while. I have literally written & released entire programs in the time it took me to find a workaround for this OpenShot problem.

OpenShot now has experimental support for hardware acceleration, which uses 1 (or more) graphics cards to offload some of the work for both decoding and encoding. This is very new and experimental (as of May 2019), but we look forward to "accelerating" our support for this in the future!

Notice: The FFmpeg versions of Ubuntu and PPAs for Ubuntu show the same behaviour. FFmpeg 3 has working nVidia hardware acceleration while FFmpeg 4+ has no support for nVidia hardware acceleration included.

The correct version of libva is needed (libva in Ubuntu 16.04 or libva2 in Ubuntu 18.04) for the AppImage to work with hardware acceleration. An AppImage that works on both systems (supporting libva and libva2), might be possible when no libva is included in the AppImage.

Decoding and encoding on the (AMD) GPU is possible with the default drivers. On systems where ROCm is installed and run a future use for GPU acceleration of effects could be implemented (contributions welcome).

If the computer has multiple graphics cards installed, you can choose which should be used by libopenshot. Also, you can optionally use one card for decoding and the other for encoding (if both cards support acceleration). This is currently only supported on Linux, due to the device name FFmpeg expects (i.e. **/dev/dri/render128**). Contributions welcome if anyone can determine what string format to pass for Windows and Mac.

This information might be wrong, and we would love to continue improving our support for hardware acceleration in OpenShot. Please help us update this document if you find an error or discover new and/or useful information.

FFmpeg 4 + nVidia The manual at: _nvidia_encode works pretty well. We could compile and install a version of FFmpeg 4.1.3 on Mint 19.1 that supports the GPU on nVidia cards. A version of openshot with hardware support using these libraries could use the nVidia GPU.

BUG: Hardware supported decoding still has some bugs (as you can see from the chart above). Also, the speed gains with decoding are not as great as with encoding. Currently, if hardware decoding fails, there is no fallback (you either get green frames or an "invalid file" error in OpenShot). This needs to be improved to successfully fall-back to software decoding.

Further improvement: Right now the frame can be decoded on the GPU, but the frame is then copied to CPU memory for modifications. It is then copied back to GPU memory for encoding. Using the GPU for both decoding and modifications will make it possible to do away with these two copies. A possible solution would be to use Vulkan compute which would be available on Linux and Windows natively and on MacOS via MoltenVK.

If you experience a freeze on Windows 11, this is a known issue with PyQt5 and Windows 11, related to theaccessibility features in Qt. This is triggered by pressing Ctrl+C in OpenShot (only on Windows 11).OpenShot will become unresponsive and a memory leak is also present (i.e. the longer OpenShot is unresponsive,the larger your memory leak will become until OpenShot finally crashes or the user kills the process).

Before attaching a debugger, please download the latest version of OpenShot: this version of OpenShot to the default location: C:\Program Files\OpenShot Video Editor\. For detailsinstructions on debugging OpenShot on Windows, please see this wiki.

The Windows version of OpenShot is compiled using an environment called MSYS2. In order to attach the GDB debuggerto our executable, openshot-qt.exe, you must first install MSYS2. This step is only required once.

Once OpenShot has launched successfully with GDB attached, all you need to do is trigger a crash or freeze in OpenShot.When a crash occurs, switch back to the MSYS2 MinGW64 terminal and run one of the following commands(by typing it and pressing ENTER). Usually, the first command to enter is bt, which stands for backtrace.More commands are listed below.

OpenShot Video Editor is a free and open-source video editor for Windows, macOS, Linux, and ChromeOS. The project started in August 2008 by Jonathan Thomas, with the objective of providing a stable, free, and friendly to use video editor.[1][4][5][6][7][8]

The program supports Windows, macOS, and Linux ever since version 2.1.0 (released in 2016).[9] OpenShot added support for ChromeOS in version 2.6.0 (released in 2021).[10] There is an unofficial portable version beginning in 2020.[11]

OpenShot is written in Python, PyQt5, C++ and offers a Python API.[12] OpenShot's core video editing functionality is implemented in a C++ library, libopenshot. The core audio editing is based on the JUCE library.

OpenShot Video Editor is a free, open-source video editor licensed under the GPL version 3.0. OpenShot can take your videos, photos, and music files and help you create the film you have always dreamed of. Easily add sub-titles, transitions, and effects, and then export your film to DVD, YouTube, Vimeo, Xbox 360, and many other common formats. What really sets OpenShot apart from other video editors is the easy-to-use user interface.

OpenShot has many great features, such as trimming and arranging videos, adjusting audio levels, transitions between videos, compositing multiple layers of video, chroma-key / green screen effect, and support of most formats and codecs.

The problem was caused because float is used as some of the arguments where int is now expected. There can be some more such parts in the code which I might have missed during my testing. And if any such code is executed with a float argument then the application might again crash.

Same error on a fresh ubuntu 22.04 install. I've tried with version 2.5.1 from ubuntu-jammy-universe and from openshot.developers/ppa. I don't want to install the daily version.

As a workaround, 2.6.1 Appimage version works fine.

Same error here. Ubuntu 22.04, fresh install, openshot 2.6.1 installed with apt (see log below). After installing from ppa:openshot.developers it seems to work (I haven't testing too much, but at least I can see the main window)

3a8082e126