Titles Font not remebered between Appimage and PPA .osp?

[izzostar]

Lubuntu 22.04, OpenShot 3.1.0.

So from my experience so far, do i understand it correctly?

1. The AppImage does not do GPU-rendering?
2. The (ubuntu) PPA version crashes on file import when GPU-acceleration is enabled?

So for getting things done, i have both versions and change between them. (Maybe it is now possible beacuse they are the same version at the moment, i think earlier or sometimes it crashed when using the same project file, because of the openshot-qt.settings file needed to be deleted, but not at the moment.)

So i import files in AppImage version, and render with GPU in PPA version of OpenShot. And in between, when other porblems araise, i switch between versions too. Problem with that is, that i have to again select the Fonts for my (sub)Titles in the Titles menu.

I think even if i didnt delete the openshot-qt.settings file, the Font setting in Titles menu is forgotten/not saved in the project file?

So for now i guess i have to remember to start with Appimage then before the end go to PPA version and do the (sub) Titles as the last thing, then render.

Or (havent tried if that works), disable GPU in PPA version, do things, enable GPU and then render?

[izzostar]

Oh no, now the PPA-versions GPU-rendering crashes too at about when 76% done. After upgrading to version 3.1 of Openshot that is. GPU-rendering worked fine with earlier version of OpenShot PPA. Intel and VA-API that is. And the files were different beause it was a different project.

Maybe its something in the Title texts again? I feel as if my wife is a hacker or sometihing, i remember problems already long time ago: dont write symbols like (,?) in Titles or/and title filenames?

Ah, but no, when importing video files in the beginning, no Titles exist yet. But some video files can be imported, some not. Maybe something in the video files names, UTF-8 umlaut õäöü? The file selector/manager seems different too, right? Appimage has its own, and PPA uses the Lubuntu one?

The AppImage file selector wont let me sort the files by name, date, etc?

[Colorjet3]

Hello @izzostar.

Here is an answer from the DEV team regarding Hardware Acceleration:

1. Hardware acceleration is still experimental in OpenShot Video Editor. NVIDIA NVENC acceleration is only available in Linux operating systems. OpenShot v2.6.0 and later includes Intel® Quick Sync Video encoding in Windows operating systems. If you have a CPU that supports Intel® QSV encoding, you can use the encoder by selecting the ( QSV ) MP4 (h.264 qsv) Target on the Export Video window. You do not have to change the Preferences window to use the Intel® QSV encoder.

2. Setting up hardware acceleration in OpenShot running on Linux distributions can be tricky. I've set up hardware acceleration several times and learned some Dos and Don'ts that I can share with you. There aren't any instructions or steps to follow because each customer's Linux installation is unique. • Hardware acceleration only works with our PPA and source code installations, not our AppImage or the Linux package manager installations. • Don't use NVIDIA's Linux graphics drivers. Use the proprietary video drivers from the package manager included with your distribution. • Hardware acceleration only works with the first video device (display: 0). • If you have a system with two video devices (integrated and discreet), you may have to use your system's BIOS to disable the CPU's graphics processor. • Ensure that VDPAU and VA-API are working using vdpauinfo and vainfo. • You don't have to select the graphics card in OpenShot's Preferences window on the Performance tab for hardware-accelerated decoding or encoding. • Change the Target on the Simple tab of the Export Video window to (NVENC) MP4 (h.264 nv), then click the Export Video button.

Fonts issue. Not sure why you are having issues but it could that the PPA version you are running is different than the AppImage. v3.1.0 was just recently released and some of the Linux versions may not have the latest code yet. Try installing them again. At some point I would stick to just the PPA for now and ensure that it is v3.1.0-release-11205-.

I just saw your additional comments/issues. I think it is best that you submit different posting for the different issues otherwise it is going to be challenging to keep track of the different issues and constantly changing the content of our correspondence.

[Colorjet3]

Hello @izzostar. Upon digging further into this I found a documented issue that is in the queue to be fixed that is probably contributing to the issue you are experiencing with the Fonts (https://trello.com/c/iyEUPG90/15-titles-font-do-not-appear-in-appimage-ubuntu-2204).

This is most likely the culprit and you just have to pay attention as you go back and forth. By the way, I highly recommend that you stay with the PPA version vs. the AppImage unless you absolutely have to. I know for a fact that there are some challenges with the AppImage (being self-contained). Often, we use the AppImage when we are testing Daily-Builds only and not for every day production use.

[izzostar]

Ah, yes, thank you. Seems like the bitstream vera sans is set as default or something? And i realize now, it had nothing to do with changing between AppImage and PPA versions. Its just, that (at least the AppImage) does not remember the last selected font, as i expected. Well i just thought it did, in reality i guess my last distro had vera sans installed and the new Lubuntu did not. So installing ttf-bitstream-vera does the trick for now, no more empty forgotten subtitles in my videos hopefully :) But remembering (and displaying) the last selected font would be my feature request i guess.

[stale[bot]]

Thank you so much for submitting an issue to help improve OpenShot Video Editor. We are sorry about this, but this particular issue has gone unnoticed for quite some time. To help keep the OpenShot GitHub Issue Tracker organized and focused, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.

This issue will be closed, as it meets the following criteria:

• No activity in the past 180 days
• No one is assigned to this issue

We'd like to ask you to help us out and determine whether this issue should be reopened.

• If this issue is reporting a bug, please can you attempt to reproduce on the latest daily build to help us to understand whether the bug still needs our attention.
• If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks again for your help!