Skip to content
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

"Text: Rich" exports text in incorrect size #1146

Open
piiskop opened this issue Aug 13, 2021 · 7 comments
Open

"Text: Rich" exports text in incorrect size #1146

piiskop opened this issue Aug 13, 2021 · 7 comments

Comments

@piiskop
Copy link

piiskop commented Aug 13, 2021

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute

Shotcut version 21.03.21

I've added the filter Text: Rich. After exporting the video, [font size is larger](https://youtu.be/wvQxd6U8NqA
shotcut-application-log-monitor-switch-crash.txt
shotcut-application-log-rich-text.txt
) which can also cause not fitting in the frame.

After exporting the video, I switched the monitor to be inside the main screen instead of an external screen and the application just crashed.

@bmatherly
Copy link
Member

bmatherly commented Aug 13, 2021

This is a known issue that we have not found a good solution for
https://forum.shotcut.org/t/text-rich-filter-not-exporting-what-shows-in-shotcut/21156
https://forum.shotcut.org/t/rich-text-font-larger-then-in-preview/29248
The work-around is to set the display scaling to 100% on whatever monitor you use for previewing so that it will match the export. Also, Simple Text does not have this issue - so it can be used if you do not need the rich features.

I think the crashing is new.

@piiskop
Copy link
Author

piiskop commented Aug 14, 2021

The first link refers to a discussion where we can read:

This is fixed for the next version.

It wasn't fixed for the next version.

The work-around is to set the display scaling to 100% on whatever monitor you use for previewing so that it will match the export.

No matter what display I use, in Shotcut, the text looks smaller than in the exported file. I'm not aware of having set a different scale than 100 % for any monitors I'm using. I don't even know how to change the scale. I'm not sure whether you mean this:

$ gsettings get org.gnome.desktop.interface text-scaling-factor
1.0

This is a known issue

Can you refer the issue report here in GitHub because only GitHub is the place for issues and the forum is for discussions as the boss of Shotcut once told me? I haven't found anything regarding to this issue here in GitHub.

@bmatherly
Copy link
Member

I don't even know how to change the scale.

Correct. It was improved, but not completely fixed.

I don't even know how to change the scale.

You can check in the settings to see if it is set to something other than 100%
Screenshot from 2021-08-14 07-35-12

only GitHub is the place for issues

We accept issue reports in the forum Bug category
https://forum.shotcut.org/c/bug/6
There are far more issues reported in the forum than on GitHub. Either location is acceptable.

@piiskop
Copy link
Author

piiskop commented Aug 14, 2021

You can check in the settings to see if it is set to something other than 100%
Screenshot from 2021-08-14 07-35-12

I don't use Gnome in the laptop that I use for Shotcut as there was a problem with something I can't remember anymore. Then, I tested five desktop versions and now, I use MATE. This works for everything I needed. And it doesn't even have the graphical option for changing the scale.

We accept issue reports in the forum Bug category
https://forum.shotcut.org/c/bug/6
There are far more issues reported in the forum than on GitHub. Either location is acceptable.

The boss of Shotcut refused to accept some of my bug reports there and told me that bugs should be reported here. From that time, I only report bugs here. The forum you're referencing has some bugs itself. And topics will be automatically closed. And once, I was even banned.

@bmatherly
Copy link
Member

Please find out if your system is using scaling and report back. That will help us debug further.

You can also play with QT_AUTO_SCREEN_SCALE_FACTOR by setting that environment variable to see if that fixes the preview size. I have not tried this myself, so some experimentation would be required.
Some context here:
https://forum.shotcut.org/t/shotcut-resolution-ubuntu/5753
Also, read a few of these for better understanding:
https://forum.shotcut.org/search?q=QT_AUTO_SCREEN_SCALE_FACTOR

@piiskop
Copy link
Author

piiskop commented Aug 14, 2021

Please find out if your system is using scaling and report back.

I already did it. Please see my reply. There has been no reason to scale and as far as I have detected, there's no scaling.

I just made a test because I wanted to compare how a text looks like in ONLYOFFICE in comparison to Shotcut. I did set the monitor to be on another screen because therefore, it's 100 % of the size, right? All the images seem to be in the correct size. But is the text also? The test resulted that on the monitor of Shotcut, the lower text size is about 48 instead of 72 although Text: Rich shows 72. I don't know what the units are. Would they be in pixels, I could use an external ruler to find out the exact difference but they seem to be in pt. In the exported file, the text seem to have the size that was visible in the text editor on the monitor. This means that rather the font size on the monitor is incorrect than in the exported file.

Please don't recommend things you haven't tried out because you don't know what you're actually recommending. env shows QT_AUTO_SCREEN_SCALE_FACTOR=0.

@lddubeau
Copy link

I ran into the same problem. It also happens when running shotcut in Chrome OS' Linux subsystem. Here's the lsb_release info:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

Checking whether my desktop was scaled showed it was at 100%.

I set QT_AUTO_SCREEN_SCALE_FACTOR=0. It was 1 when I first tried, but it changed absolutely nothing.

I switched from the rich text filter to a text filter and my problem was fixed. I suppose however this is not a solution for everyone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants