Hello everybody.
I recently read a post regarding a problem due to the lack of text line spacing in the Text: Rich filter. There was an answer regarding the use of HTML to solve the issue (or something like that). Unfortunately I made big mistakes:
- Did not keep the user who posted the problem.
- Did not keep the answer(s).
- Did not keep the date.
- Many others…
I did some tests (I am fairly new to SC, although I used other free NLVEs) and found what may be a modest solution for the following issues, without the use of HTML:
- Setting different font sizes, fonts, etc., using the same Text: Rich filter window (useful for titles and subtitles).
- Changing both font size and line spacing within the same Text: Rich filter (useful in the case somebody needs to put a legend in the same clip (e.g., an image clip.
- I found these useful and easy to perform, avoiding the replication of text clips.
- I recorded a two-clip text example. I saved it both as mlt as well as mp4 (I can imagine the first will suffice).
Thank you in advance (and sorry about my English. I’m neither a native nor a fluent English speaker).
Regards,
Gerardo
Thanks for sharing this, Gerardo. Avoiding extra text clips for different sizes is a real time saver, and your two-clip example makes the point clearly.
One small addition from the same approach: when you are setting sizes and spacing in the Text: Rich filter, it is worth exporting a short test clip and checking it at full size. The preview can make small text look fine at a reduced scale, while the exported video shows spacing problems more clearly. Keeping the text on its own track also makes it easier to reuse the same styled clip elsewhere in the project.
@alexsamuels you are a bot and unofficial bots are not permitted here. Reply with some kind of proof otherwise, or I will delete your account.
@shotcut Uupppss. Thank you for your comment. The bot also made a comment regarding my problem about version 26.10.3 (elements missing in Elements drop-down menus). I found it was due to the lack of fuse2, since my system requires a higher version to work properly.
I went back to 26.9.27 for that reason. I don´t want to introduce any possibility of a security breach.
Regards,
Gerardo
Hello again @shotcut ,
You may think I’m an old dumb man. I began using SC 26.10.3 again.
The explanation can be found at:https://laptopjudge.com/what-is-appimage-squashfs-packaging/
In short, although SC depends on fuse2, and I have fuse3, running SC 26.10.3 from inside SquashFS filesystem encapsulates Appimage.
Therefore, running it that way is as safe as running the Appimage itself, as far as the executable is not given 777 (wrx to owner, group, everyone else’s) permissions through chmod, which is the reason for a security breach.
The advantage of running the Appimage file from within SquashFS? It seems this bypasses fuse versions.
So, thank you again for inducing me to search for a solution and a good explanation as of why it should work without problems, including security breaches.
Regards,
Gerardo
If you do not want to use fuse2 or make the AppImage executable (or use Snap or Flatpak) I suggest to use the portable build and its launch script. That is probably more convenient than extracting or mounting the AppImage each time.