New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qt6 #1398
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The logic for the y position of the toolbar was creating a circular binding loop.
This prevents turning on GPU effects in new versions from turning it on in old versions.
* Add new speed filters Forward, Forward/Reverse and Slow. Add a metadata parameter for filters that will seek backwards to prompt for conversion if required. Currently only * Speed (Forward/Reverse) * Time Remap * Resolve speed review comments * Add minimumVersion * Remove slow motion filter * Improve naming
This is just temporary. I think the full solution is transport sync from Glaxnimate to Shotcut and using the displayed frame from VideoWidget ala the video scopes. Then, one can hide tracks temporarily if needed.
This is reproduced by toggling mute while it is recording (whether to listen to the clip with headphones or to record what Shotcut is playing). After stopping recording, the sound can be silent and toggling mute does not fix it!
https://forum.shotcut.org/t/cannot-scroll-timeline-horizontally-with- mouse-wheel-on-linux/37964
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Making this a pull request to make it easier to view diff on the web and track issues outside GitHub Issues system:
qwebp.dll
) is not working on Windows.GLWidget
uses OpenGL to draw the video under the QuickWidget. This needs to be refactored into a base class with sub-classes with different tech implementations along with porting the shader code. The SPIRV-Cross toolkit can facilitate that, but first the existing GLSL shaders need to be converted into Vulkan GLSL: https://vulkan-tutorial.com/. That also makes it compatible with Vulkan, which is a good option to have on Linux. But it is not clear if the Linux version should be Vulkan only - uncertain about the state of it on older Linux systems. See also Qt's Shader Tools for this.Qt Quick Controls 6 is not honoring the custom app palette, and I tried various things to get it to work. What I did for macOS was to remove Themes from Settings and make it automatic light or dark Fusion based on the OS color. However, now the Shotcut color will change on many people, and they will complain.
So, it will affect some Linux desktops notably KDE and LXQt. That is weak. Instead a Quick implementation appears. Here is how it looks:
flags: Qt.Dialog
or add customQMessageDialog
-backed.libstdc++
. This is due to needing to install a much new version of gcc (10) on the ubuntu18.04 builder in order to compile Qt6 and Glaxnimate's modern C++.Caveats
Using Qt-provided Qt binaries raises the minimum OS requirement to Ubuntu 20.04/glibc 2.31. The Qt build system is different for v6 being based on CMake and more modular. Well, I guess we can try: see their configuration docs.