Download Video Editor Openshot
Sebrina Lobianco
There is still a bug with animated titles background color. When choosing (Fly Towards Camera), the background should be black by default, but it is white and no way to change it. I have used Alpha 1.4.1 in AV Linux and there's no issue, but all other distros have this bug. This has ruined my openshot creativity & experience. Also, I noticed when choosing (Dissolve) I get an error message stating that Blender is not pointing to the executable blender. blender is listed in preferences as the executable. Why has this background issue has not been fixed? Thanks.
I did file a related bug report, Apparently their title editor is very simple and does not work well with third-party SVG
title editor fails to open .SVG if text property=Flowroot, Issue #3367 OpenShot/openshot-qt GitHub
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 and open-source video editor for FreeBSD, Linux, Haiku, macOS, and Windows. The project was started in August 2008 by Jonathan Thomas, with the objective of providing a stable, free, and friendly to use video editor. OpenShot's core video editing functionality is implemented in a C++ library, libopenshot. OpenShot uses the Qt toolkit and offers a Python API. Since version 2.0.6 (released in 2016), OpenShot is now a cross-platform application. OpenShot is also ava...
The OpenShot video library libopenshot provides high quality video editing and animation with support for all FFmpeg formats and Codecs (video, audio and images). This allows the rendering of videos in many codecs and formats.
Haven't been able to reproduce this. If anyone still suffers this problem, maybe you can attach the file sequence.mlt from the hidden folder /.openshot, from when the problem exhibits itself (preferably on a simple project).
Same bug reported as #680688, #590019, #769512 (by me) (I marked them all as duplicates).
The first frame of a clip shows when it shouldn't, both in preview and final output.
As it has been already said, it occurs when the project is somewhat complex, i.e. when there are a lot of clips (with cut sequences etc...) before on the track. An effective workaround is to move the clips to a new track, which isn't very practical in the long run.
The 'first frame bug' (as I call it, it seems the 'last frame bug' is somthing else) can affect:
- Rotations, animations, scalings of clips
- Transitions (only from upper to lower track it seems)
- Cut clips (you cut out the beginning of a clip, but the first frame of the raw clip shows nevertheless. I'm not sure for this one but I think I saw it)
- Multiple tracks (first frame of lower clip shows over the upper clip)
thus preventing you from using any of those features, which makes impossible any complex project.
The bug occured for me with mlt 0.5 as well as 0.6 and 0.7, and openshot 0.9, 1.2, 1.3, on ubuntu 32 bit 10.04, 10.10 and 11.04. I think it comes from openshot and not mlt (I can't find any kdenlive bug report about it).
I think it really needs to be fixed, because it makes openshot impossible to use for large projects, whereas openshot is otherwise great software and by far the best (and the nicest) video editor available for linux (another problem with large projects is that the more complex the project, the longer the lag when you try to move the cursor, but that's not so important).
If you're running from the source (instructions to get the archive are on
the Download page) then you can apply the very simple fix yourself to work
around the problem until a fixed release version is available. In
/openshot/classes/clip.py you want the GenerateXML function, and on around
line 277 change;
I accept that my workflow is somewhat unusual, because I am effectively using "proxy clips" (see details on my workflow above) outside of openshot. I simple cannot edit my 1080p video using the raw footage..required performance is not even close..which is not helped by openshot using 30% of my CPU while idling on an empty project.
kdenlive has bugs too..and it crashes...but this bug really cripples any half serious usage of openshot for me (perhaps it's caused by the bad mp4s my camera produces..although kdenlive handles them fine using the same underlying mlt).
I have more than 1 year of home videos waiting for processing until I discovered this bug. I was waiting for the bug to be fixed instead of moving to Kino or Kdenlive because I find openshot very intuitive and easy to use and I because thought that the bug, being ***SO CRITICAL***, would be quickly fixed.
Please, inform the users about this, because I can't hold more GB of "raw videos" and I need to start processing them, and If this bug is not going to be fixed I'll have to switch to kine, kdenlive, or any other videoeditor that works. I would prefer doing it in openshot, so, please, tell us something.
f448fe82f3