OpenShot Video Editor is an award-winning free and open-source video editor for Linux, Mac, and Windows, and is dedicated to delivering high quality video editing and animation solutions to the world.

• Requires QtWebEngine and Qt 5.6+
• Requires OpenGL python module (to fix black screens on some systems)
• Enables smooth scrolling on timeline
• All callbacks from JS to Python are Async

Based on the initial work: https://github.com/OpenShot/openshot-qt/pull/2512

Related to PRs: https://github.com/OpenShot/libopenshot-audio/pull/100 https://github.com/OpenShot/libopenshot/pull/549

Windows XP Openshot version 2.4.1

I made a video of a motorcycle race that I'm trying to overlay an audio file on of race commentary. I have it all setup in openshot and it previews fine. However when I try to export the video, the audio gets really terrible whenever there are two audio tracks overlaid on top of each other. for instance, at the start of the video when there is just the commentating audio track, it sounds great. But when the race starts and there is commentating audio on top of the race audio of the bikes, it starts popping and cracking really bad. The audio is all distorted. I've tried to export the video in different formats to no success. At first the exported video had no sound at all, but I fixed that by changing the audio codec from ac3 to aac. but both codecs deliver the same terrible audio popping/cracking. can anyone help please??

I've seen this since one of the Openshot 2.3 versions (never used anything older than 2.3) and can confirm the issue is still present in 2.4.1 cuz I just used 2.4.1 to prepare the support files for this issue. This has always been on Fedora 25.

I use titles to overlay statistics on my videos. I like to have fun with them (sometimes) and wanted a creepy font with fun colors for a Halloween-themed video I was working on.

Starting with one of the stock titles and using the Advanced Editor (inkscape), I created a title using the Shlop font, made it green and turned the stroke red.

This file is provided in the attached zip archive: Stage 1 stats.svg

Directly using/importing this SVG file within Openshot results in very different rendering, most of which is off screen due to the text anchor point being honored, but the alignment is ignored.

In order to better see how Openshot is rendering the SVG file, I copied the file and manually edited it, adding an x-offset of -800 pixels.

This file is provided in the attached zip archive: Stage 1 stats_offset.svg

In order to use this SVG file, I had to convert it to a PNG on the command line and import the transparent image.

This file is provided in the attached zip archive: Stage 1 stats.png

The OSP file is included in the attached zip archive, too: SVG rendering issue - 171128.osp

An Openshot 2.4.1 rendered video that shows each of the 3 files and demonstrates that the issue is present in the final export (not just the preview) is available here: https://youtu.be/1R6uUPfotss

SVG rendering issue - 171128.zip

Please let me know if I can provide any additional information or help.

Thanks!

-Rich

For the next release of OpenShot (whichever and whenever that should be), one of the still-unaddressed needs is documentation.

The manual was mostly written in 2017, with only very minor updates since then. (The last new documentation written was the EDL / XML import and export docs, added on 2019-05-25 by @jonoomph in commit b1422e1a2bdedd5f56b4aca6b1e15d90ef14e78a.)

Documentation needs (working list)

• Significant portions of OpenShot have changed greatly since 2017, including the Preferences (which are virtually unrecognizable from two years ago, in some of the tabs).
• New features have been added, including hardware encoding (for both export and animated titles) that could do with at least a cursory treatment in the manual.
• Even some features that aren't new could still do with expanded documentation:
  • Export options
  • Keyframe animation generally (which is really crying out for an illustrated step-by-step tutorial)
  • Effects
  • Transitions.

Volunteers welcome!

Any volunteers who'd be interested in helping to improve the manual, both directly (writing documentation) and indirectly (soliciting, organizing, and copyediting contributions from developers) would be greatly appreciated.

Writing and editing OpenShot documentation

The source files for the manual are all found in the project repository (the doc/ directory), the preferred method for submitting edits would be via GitHub Pull Request but we can make accommodations for anyone who'd like to contribute but isn't familiar with version-control systems like Git.

Generating a local copy of the manual requires only the Python-based Sphinx documentation system and the Sphinx RTD theme, which can be installed via pip3 install sphinx sphinx-rtd-theme or using most package managers. I can provide support to anyone who'd like to contribute and needs help with installing and using Sphinx.

I had an open shot file project and the next day I was unable to open it! I tried reinstalling the program, but it still will not open. I have even tried the daily build and deleting the log files, as Open Shot's website instructed when troubleshooting.

The message given when trying to open the file is:

I will do anything to fix this issue. I can even attach the file into a zip if needed. Please, someone help me because I have spent hours onto this project.

Operating System / Distro: Windows 7 OpenShot Version: 2.4.1

When previewing videos in OpenShot, the video and audio are perfectly synced. After exporting, the audio always ends up about a quarter of a second ahead of the video, all the way throughout. I've tried exporting with different settings and at different framerates and it doesn't seem to have any effect on the desync. This is probably a stupid oversight on my part since I'm new to video editing, but can anyone help me out here? Thanks!

* WIL == "Work In Limbo"

At the moment the status of this is "on hold indefinitely", until I can revisit its status more concretely, and figure out a plan for revisiting the PR itself.

Previous Update

To my very great surprise, to be perfectly honest, initial tests of this code in Win7 (after development on Linux) seemed to indicate that it requires no changes to function equally well on that platform. This is something I was genuinely not expecting, and apparently means that the code may be more finished than I thought. So, in honor of that surprise development, I'm creating this PR to open the code up to wider review and testing.

The set of commits in this PR do two basic things:

1. Re-work the OpenShot main window's communication with its child windows
2. Completely restructure the way tutorial popups are created and managed

You can see the individual commits for further details, but the main takeaways are:

1. There is a new Tutorial dock widget defined in main-window.ui, initially hidden and permanently floating and non-dockable.
2. All Tutorial popups are now displayed inside of that (same) dock widget, which has all of its decoration removed so that it is completely invisible (aside from the tutorial popup itself).
3. Any move/resize events on the main window are communicated to the Tutorial dock, and it updates its position accordingly (just as before), but because it's a QDockWidget, Qt makes sure it stays on top of the main window. Also, because it's a dock, not a window, it doesn't appear in the window list.
4. Show/hide events from the main window are now propagated to ALL floating dock widgets (not just the tutorial, though this does apply to the tutorial as well). Which means that if you minimize OpenShot, floating docks will minimize with it, and they'll return when you restore it. No more "the tutorial disappeared when I minimized OpenShot, but Properties didn't, and when I restored OpenShot the tutorial was gone" type issues.
5. The expensive event filters on both the main window and the tutorial widget are gone, as they're no longer needed.
6. Calls to show() on both the main window and the tutorial widget are now tightly controlled to avoid unnecessary window updates and repaints, which I am very hopeful will alleviate the flickering and unresponsiveness seen by some users (see #1080, #1264, #1555, #1623, etc.)

There are some unresolved issues/questions, some of them stemming from this change, some not.

• Of the ones not directly a consequence of this change, the most pressing is the question of what to do about floating docks when OpenShot it maximized/fullscreened. It's really not meant to have docks floating on top of the main interface, and in practice it doesn't work well (tutorial popups excepted). I suspect it might be a good idea to auto-dock any floating panels on maximize, and then automatically float them again when the window is returned to normal state. (The tutorial popups can't be docked, so they wouldn't be affected.)

• In terms of the tutorial the main problem is, while Qt makes sure it always stays on top of the main window, I'm having less success getting it to always stay on top of other floating dock windows, especially after a minimize/restore cycle. So it's a bit annoying when the tutorial is pointing to one of the dock panels, you minimize the application, and then when you restore it suddenly the tutorial is behind the floating dock. But I don't want to get too aggressive with excessively show()-ing and raise_()-ing things to try and work around that, as that's where we get into trouble with too-frequent updates. A solution that ends up recreating the previous situation with repaint spam, flickering, and windows that won't take clicks is no solution at all.

  Also, because the tutorial popups are inside a QDockWidget that changes size, technically they may be resizeable on some systems. (They're not on Windows, they are in Gnome Shell on Linux if you can find the tiny, invisible hairline border.) But even then, the tutorial resizes just fine, and it'll be automatically resized again when advancing to the next popup, so I really don't consider it a problem if the user can resize them.

I need to explore a range of different scenarios, including switching between different window states and between Simple and Advanced view, and test those scenarios on multiple systems to make sure that the tutorials don't do anything crazy at some point. But I wanted to at least open the code up to review and comment in its current state, and of course if anyone has a chance to test it and report the results then that would be a huge help.

Describe the bug OpenShot-v2.4.2-x86_64.AppImage fails to start on Linux Mint 18.1

System Details (please complete the following information):

• Operating System / Distro:

$ cat /proc/version
Linux version 4.4.0-128-generic (buildd@lcy01-amd64-019) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) ) #154-Ubuntu SMP Fri May 25 14:15:18 UTC 2018

$ lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description:    Linux Mint 18.1 Serena
Release:        18.1
Codename:       serena

• OpenShot Version: OpenShot-v2.4.2-x86_64.AppImage (downloaded 2018-06-30 2AM UTC)

To Reproduce Steps to reproduce the behavior:

1. Make file executable
2. Double click it or run it through Terminal
3. Click "No" when a pop up asks if a shortcut should be created
4. Program crashes

Logs I didn't find a daily build of 2.4.2* more recent than the one that crashed, and the crash happens at the startup, therefore I couldn't enable debug mode in order to generate the log files.

However, this is what I see when try to run the app through the Terminal:

$  ./OpenShot-v2.4.2-x86_64.AppImage
Loaded modules from current directory: /tmp/.mount_Jp5Fvp/usr/bin
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/cx_Freeze-4.3.4-py3.4-linux-x86_64.egg/cx_Freeze/initscripts/Console.py", line 27, in <module>
  File "openshot_qt/launch.py", line 53, in <module>
    from classes.app import OpenShotApp
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 2237, in _find_and_load
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 2226, in _find_and_load_unlocked
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 1200, in _load_unlocked
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 1129, in _exec
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 1471, in exec_module
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 321, in _call_with_frames_removed
  File "/tmp/.mount_Jp5Fvp/usr/bin/classes/app.py", line 34, in <module>
    from PyQt5.QtWidgets import QApplication, QStyleFactory, QMessageBox
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 2237, in _find_and_load
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 2226, in _find_and_load_unlocked
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 1191, in _load_unlocked
  File "/usr/lib/python3.4/importlib/_bootstrap.py", line 1161, in _load_backward_compatible
  File "ExtensionLoader_PyQt5_QtWidgets.py", line 22, in <module>
  File "ExtensionLoader_PyQt5_QtWidgets.py", line 14, in __bootstrap__
ImportError: /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1: undefined symbol: drmGetDevices2

System Details:

• Operating System / Distro: Windows 10 1920x1080 NVidia GeForce 1060 3GB, intel i7-700, RAM 16 GB
• OpenShot Version: 2.4.1 Issue Description and steps to reproduce: Using prerecorded nvideo shadowplay clips of PUBG game, I do the following:

1. Enter 1 clip as track 0
2. Enter 2nd (very large clip) as track 1
3. Slice track 1 first keeping right side
4. Align tracks
5. Slice track 1 keeping left side
6. Copy track 1 and place copy in track 2
7. Set track 2 to slow 1/4 speed
8. Export clip

Exported clip shows a stopped stuttered frame where the 1/4 speed track 2 should be and it's about 15 seconds before track 2 slice should be beginning. Here is a youtube clip showing entire process: https://youtu.be/YdCV-dmZ7GQ

Question: A clear and concise question, with enough context and explanation for people to answer it.

System Details:

• OpenShot Version [e.g. 2.4.3]: {{ log_context.openshot_qt_version }}
• Operating System / Distro: [e.g. Windows 10, Linux Mint 17.1]

Screenshots: (Optional) If applicable, add screenshots to help explain your question. You can include screenshots by copy/pasting them here, dragging-and-dropping into this form, or clicking below and loading images saved to your computer. All images are public, so please don't post screenshots containing personal information.

Describe the bug Import video, set it on track, split video with cisors, move 2nd part over 1st one to make an effect, move playhead back and forward again and again (or just export), then, quite quickly, launch.exe crashes. Same issue with 2 different files with a fade effect

System Details (please complete the following information):

• Operating System / Distro: Windows 10, Windows 7
• OpenShot Version 2.4.1 . 115 daily built, 64 plus stable 2.4.1

To Reproduce Import other video from other source, split it, move one part over an other to get a fade... move playhead or export.

Logs Attached 2 sets. 1st one, 720 against 1080 ; 2nd one 1080 progressive against 1080 progresive. 3rd test worked like a charm (interleave progressive????), so no log...

Additional context As per default, profile loaded is 720 24p As per default video tracks used are 1080 and feel it is 25 P So 1st basic test crashed In this context, no warning that object used (video, image) does not match profile but feel it is linked as using a 720 video in 720 profile or 1080 in 1080 run safe when mixing source size with a different profile size, ends in a seconds or 2 with the crash when playing with the play head. App may consider and tune elements, but feel it crashes 1st... Don't know if linked to resolution, frame rate or P against I, but there is something not matching between file and profile that makes app crash.

Side of that really looks fine... Looking for a fix / tip to really appreciate it... Best

In logs, it reports AMD, but computer is Intel inside In logs it reports fr-fr, but do not see fr-fr folder (just fr) and menues are displayed in English... Openshot crashes.zip

Describe the bug: When pressing play on the preview window, after about 1 second of playing, it crashes.

Steps to reproduce the behavior:

1. Import a GoPro .mp4 (any file)
2. Add the file into the timeline
3. Press play
4. Crash

Expected behavior: Not crashing

System Details:

• OpenShot 3.0.0 daily build OpenShot-v3.0.0-daily-10873-99aab0a1-f55ec5d0-x86_64.AppImage
• Operating System / Distro: Linux Slackware 15.0
• OpenShot 2.6.x from the distro packages works correctly

Log Files: libopenshot.log console.log

Exception / Stacktrace:

---- Unhandled Exception: Stack Trace ----
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0xa49a69)  [0x7f25c6f43a69]
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0xa49b0b)  [0x7f25c6f43b0b]
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0x24fdf2)  [0x7f25c6749df2]
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0x38e781)  [0x7f25c6888781]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2b3a7b2)  [0x7f25d1cfd7b2]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2de49f5)  [0x7f25d1fa79f5]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2de4ca7)  [0x7f25d1fa7ca7]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x4d82a21)  [0x7f25d3f45a21]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x4d82b6e)  [0x7f25d3f45b6e]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2407fc0)  [0x7f25d15cafc0]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2428ae1)  [0x7f25d15ebae1]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2429803)  [0x7f25d15ec803]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2429ab8)  [0x7f25d15ecab8]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x24274b0)  [0x7f25d15ea4b0]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x2449e9f)  [0x7f25d160ce9f]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x24747e1)  [0x7f25d16377e1]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5WebEngineCore.so.5 (                                           + 0x24acb63)  [0x7f25d166fb63]
  /lib64/libpthread.so.0         (                                           + 0x7e45)  [0x7f25e4853e45]
  /lib64/libc.so.6               ( clone                                     + 0x3f  )  [0x7f25e49c24af]
---- End of Stack Trace ----
QObject::~QObject: Timers cannot be stopped from another thread
Caught signal 11 (SIGSEGV)
---- Unhandled Exception: Stack Trace ----
  /tmp/.mount_OpenShI2qE2i/usr/bin/libQt5Gui.so.5 ( QPainter::QPainter(QPaintDevice*)         + 0xa9  )  [0x7f25e37ade69]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot.so.23 ( openshot::Clip::apply_keyframes(std::shared_ptr<openshot::Frame>, std::shared_ptr<QImage>)  + 0xac9 )  [0x7f25e3cf7509]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot.so.23 ( openshot::Clip::GetFrame(std::shared_ptr<openshot::Frame>, long, openshot::TimelineInfoStruct*)  + 0x1e4 )  [0x7f25e3cf80f4]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot.so.23 ( openshot::Timeline::GetOrCreateFrame(std::shared_ptr<openshot::Frame>, openshot::Clip*, long, openshot::TimelineInfoStruct*)  + 0x373 )  [0x7f25e3d532d3]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot.so.23 ( openshot::Timeline::add_layer(std::shared_ptr<openshot::Frame>, openshot::Clip*, long, bool, float)  + 0xb9  )  [0x7f25e3d535d9]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot.so.23 ( openshot::Timeline::GetFrame(long)        + 0x14f0)  [0x7f25e3d58880]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot.so.23 ( openshot::VideoCacheThread::run()         + 0x2e6 )  [0x7f25e3d9ee46]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot-audio.so.9 ( juce::Thread::threadEntryPoint()          + 0xd9  )  [0x7f25e3b50399]
  /tmp/.mount_OpenShI2qE2i/usr/bin/libopenshot-audio.so.9 (                                           + 0x1734cd)  [0x7f25e3b504cd]
  /lib64/libpthread.so.0         (                                           + 0x7e45)  [0x7f25e4853e45]
  /lib64/libc.so.6               ( clone                                     + 0x3f  )  [0x7f25e49c24af]
---- End of Stack Trace ----

Exception / Stacktrace DIFFERENT RUN:

nouveau: kernel rejected pushbuf: No such file or directory
nouveau: ch6: krec 0 pushes 0 bufs 2 relocs 0
nouveau: ch6: buf 00000000 00000002 00000004 00000004 00000000 0x7f44da60a000 0x15000 0x80000
nouveau: ch6: buf 00000001 00000006 00000004 00000000 00000004 0x7f44fc80c000 0x215000 0x1000
INFO webview: Dropping item on timeline - item_id: 6WGOS2RYQ4, item_type: clip
INFO main_window: updateStatusChanged
Caught signal 11 (SIGSEGV)
---- Unhandled Exception: Stack Trace ----
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0xa49a69)  [0x7f44def43a69]
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0xa49d5a)  [0x7f44def43d5a]
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0x231489)  [0x7f44de72b489]
  /usr/lib64/dri/nouveau_dri.so  (                                           + 0x2314c0)  [0x7f44de72b4c0]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5QuickWidgets.so.5 (                                           + 0xbefa)  [0x7f44e7307efa]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5QuickWidgets.so.5 (                                           + 0xc05c)  [0x7f44e730805c]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Core.so.5 ( QObject::event(QEvent*)                   + 0x1d5 )  [0x7f44fb7fdbc5]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Widgets.so.5 ( QWidget::event(QEvent*)                   + 0x22d )  [0x7f44fa80125d]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5QuickWidgets.so.5 ( QQuickWidget::event(QEvent*)              + 0xd3  )  [0x7f44e730bce3]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5WebEngineWidgets.so.5 (                                           + 0x34686)  [0x7f44ee70a686]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Widgets.so.5 ( QApplicationPrivate::notify_helper(QObject*, QEvent*)  + 0x86  )  [0x7f44fa7bea66]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Widgets.so.5 ( QApplication::notify(QObject*, QEvent*)   + 0x330 )  [0x7f44fa7c80f0]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/PyQt5/QtWidgets.cpython-38-x86_64-linux-gnu.so (                                           + 0x3d6bf6)  [0x7f44eef87bf6]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Core.so.5 ( QCoreApplication::notifyInternal2(QObject*, QEvent*)  + 0x18a )  [0x7f44fb7d180a]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Core.so.5 ( QTimerInfoList::activateTimers()          + 0x3d0 )  [0x7f44fb828780]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Core.so.5 (                                           + 0x2de06c)  [0x7f44fb82906c]
  /tmp/.mount_OpenShIH70qI/usr/bin/libglib-2.0.so.0 ( g_main_context_dispatch                   + 0x27d )  [0x7f44f6e8d17d]
  /tmp/.mount_OpenShIH70qI/usr/bin/libglib-2.0.so.0 (                                           + 0x52400)  [0x7f44f6e8d400]
  /tmp/.mount_OpenShIH70qI/usr/bin/libglib-2.0.so.0 ( g_main_context_iteration                  + 0x33  )  [0x7f44f6e8d4a3]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Core.so.5 ( QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)  + 0x65  )  [0x7f44fb829435]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Core.so.5 ( QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)  + 0x12b )  [0x7f44fb7d03ab]
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Core.so.5 ( QCoreApplication::exec()                  + 0x96  )  [0x7f44fb7d8116]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/PyQt5/QtWidgets.cpython-38-x86_64-linux-gnu.so (                                           + 0x3979c1)  [0x7f44eef489c1]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x2a8697)  [0x7f44fd417697]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( _PyObject_MakeTpCall                      + 0xab  )  [0x7f44fd417b2b]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x74df3)  [0x7f44fd1e3df3]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( _PyEval_EvalFrameDefault                  + 0x7d86)  [0x7f44fd1ebef6]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x8006b)  [0x7f44fd1ef06b]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x74d6d)  [0x7f44fd1e3d6d]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( _PyEval_EvalFrameDefault                  + 0x12fd)  [0x7f44fd1e546d]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( _PyEval_EvalCodeWithName                  + 0x8fb )  [0x7f44fd339e4b]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( PyEval_EvalCodeEx                         + 0x42  )  [0x7f44fd33a1d2]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( PyEval_EvalCode                           + 0x1f  )  [0x7f44fd33a5bf]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x1cfc01)  [0x7f44fd33ec01]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x25f547)  [0x7f44fd3ce547]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x74d6d)  [0x7f44fd1e3d6d]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( _PyEval_EvalFrameDefault                  + 0x12fd)  [0x7f44fd1e546d]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x8006b)  [0x7f44fd1ef06b]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x74d6d)  [0x7f44fd1e3d6d]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( _PyEval_EvalFrameDefault                  + 0x7d86)  [0x7f44fd1ebef6]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 (                                           + 0x8006b)  [0x7f44fd1ef06b]
  /tmp/.mount_OpenShIH70qI/usr/bin/lib/libpython3.8.so.1.0 ( _PyObject_FastCallDict                    + 0xe7  )  [0x7f44fd419417]
  /tmp/.mount_OpenShIH70qI/usr/bin/openshot-qt ( main                                      + 0x1d3 )  [0x55888557f593]
  /lib64/libc.so.6               ( __libc_start_main                         + 0xcd  )  [0x7f44fcf7d03d]
  /tmp/.mount_OpenShIH70qI/usr/bin/openshot-qt ( _start                                    + 0x2e  )  [0x55888557f68e]
---- End of Stack Trace ----
Caught signal 11 (SIGSEGV)
---- Unhandled Exception: Stack Trace ----
  /tmp/.mount_OpenShIH70qI/usr/bin/libQt5Gui.so.5 ( QPainter::QPainter(QPaintDevice*)         + 0xa9  )  [0x7f44fbe4fe69]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot.so.23 ( openshot::Clip::apply_keyframes(std::shared_ptr<openshot::Frame>, std::shared_ptr<QImage>)  + 0xac9 )  [0x7f44fc399509]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot.so.23 ( openshot::Clip::GetFrame(std::shared_ptr<openshot::Frame>, long, openshot::TimelineInfoStruct*)  + 0x1e4 )  [0x7f44fc39a0f4]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot.so.23 ( openshot::Timeline::GetOrCreateFrame(std::shared_ptr<openshot::Frame>, openshot::Clip*, long, openshot::TimelineInfoStruct*)  + 0x373 )  [0x7f44fc3f52d3]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot.so.23 ( openshot::Timeline::add_layer(std::shared_ptr<openshot::Frame>, openshot::Clip*, long, bool, float)  + 0xb9  )  [0x7f44fc3f55d9]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot.so.23 ( openshot::Timeline::GetFrame(long)        + 0x14f0)  [0x7f44fc3fa880]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot.so.23 ( openshot::VideoCacheThread::run()         + 0x2e6 )  [0x7f44fc440e46]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot-audio.so.9 ( juce::Thread::threadEntryPoint()          + 0xd9  )  [0x7f44fc1f2399]
  /tmp/.mount_OpenShIH70qI/usr/bin/libopenshot-audio.so.9 (                                           + 0x1734cd)  [0x7f44fc1f24cd]
  /lib64/libpthread.so.0         (                                           + 0x7e45)  [0x7f44fcef5e45]
  /lib64/libc.so.6               ( clone                                     + 0x3f  )  [0x7f44fd0644af]
---- End of Stack Trace ----

@jonoomph: It is planned to add in Debian 12 before freeze?

• https://tracker.debian.org/pkg/openshot
• https://release.debian.org/bookworm/freeze_policy.html

Describe the bug: Hi! I package this project for Arch Linux. Due to a current rebuild I noticed, that the (autogenerated) tarball for 3.0.0 (https://github.com/OpenShot/openshot-qt/archive/refs/tags/v3.0.0.tar.gz) has been changed some time between 2022-12-02 (where I first downloaded it) and 2023-01-03 (where I'm now trying to reproduce the package).

Old checksums: sha512sum: c44c4ad25d321ea26e6fbafd8df0fca7dd2d7fc0827de208f60ebe98b0615e0f3d594660e6b482ebab25216cc26c9ece5b92bb6f26ab60d2e731d2194cc3e774 b2sum: 777f3e12932e08b2b2811ae10ba3c86ef8b64e821b1742d54e8b0c1cb3de544bcbd9b2a1544bc5b48c38066c9d106ac224888b4f3064b15963c69b36dcfabc51

New checksums: sha512sum: d1115095b34937419d0f08aadacc849768a97ba5d3866a46cb8d416a26ac7fbb754b383c99ea8cb70291bd08cec0343191e71cfdd19c046bbd1a43541fc0673a b2sum: 1e7bd8921a472e4ff62b160d67fcb5a8d8c0e6614a28cce87db5078fae5401c69610bd44801344da55fc4df3c8f973263b75a8567d4372fc350f76dbeec428a1

The diffoscope log between the old and the new 3.0.0 is huge (and implies the new tarball has been created on 2022-12-08): openshot-3.0.0-diffoscope.log

Please respond to this ticket so it can be assessed whether this is a supply chain attack or whether you have moved the 3.0.0 tag.

Even though my current assumption is, that you have moved the tag, it is impossible for me to judge from the outside, as I would need to do an in-depth code analysis. This is not feasible for a volunteer like me. Please do not move tags, as this breaks reproducible builds downstream, raises alarm bells and requires people to write lengthy tickets ;-)

Steps to reproduce the behavior:

1. Download tarball for 3.0.0 on 2022-12-02
2. Download tarball for 3.0.0 on 2023-01-03

Expected behavior: Tags are never moved. Tarballs never change.

System Details:

• OpenShot Version [e.g. 2.4.3]: 3.0.0
• Operating System / Distro: Arch Linux

Log Files: n/a

Exception / Stacktrace: n/a

Screenshots: (Optional) n/a

Using openshot 3.0.0

I am unable to move the video preview, left/right/up/down, however zoom in/out works

Zooming is necessary to be able to reach the bounding box of various elements and move/resize them visually instead of numerically via the keyframe interface

I have a case where I have to manually move a mask picture frame by frame. This mask is quite small and needs to be pixel accurate.

I can reach the correct zoom level, however then I do not see the important part of the video (this is the very upper part of a vertical video)

I expected the middle move button should be able to do a translation of the view position of the video preview, however middle click has the same effect as left click and right click, which is to interact with the selected element.

Using openshot 3.0.0

In the above select, you would expect all 3 selected keyframe element to be deleted

However,

Only the last selected element is deleted

Using OpenShot 3.0.0 In this case a 8 second clip

I believe this is because the "drag area" of a clip is a much smaller square than the entire and if it gets smaller

Here is an example where I try to grab this very small clip

https://user-images.githubusercontent.com/10621885/210307792-571150f6-4d51-444e-953c-f4020e64b387.mp4

Now I think there should be a minimum grab pixel of at least 1 pixel for any clip of any duration. It would be difficult but at least with some accurate mousework it would always be possible to drag a clip along the timeline.

Also not that with the square selection, I could still easily select this clip.

Perhaps once selected there should be an easy way to drag the clip on the timeline. Perhaps there could be a UI element somewhere else that you could grab onto and drag from there ?

Another suggestion I have is to display somewhere in the interface and segmented circle.

When you click the center section of that circle and hold down the mouse button, you would be in "dial mode"

Now as you move in a circular pattern around the center section, in a clockwise or anticlockwise direction, the clip is moved backward and forwards on the timeline.

Also, the further apart you are from the center, the faster the clip would move.

There could be, written in the center, a number that indicates the number of frames or seconds that the clips moves per rotation to and from the next segment.

It should be easy to move the clip on the timeline by just one frame (think, synchronizing multiple clips)

But also to move the clip quickly along the timeline, perhaps on the outermost concentric circle, the position of the clip is now 100% per rotation, 100% of the timeline total duration.

Here is an example of what this circle might look like, I have lazily ripped this circle from a stackoverflow explanation

https://user-images.githubusercontent.com/10621885/210308483-c32f0aeb-418d-4cde-a9f6-b7304b468339.mp4