Openshot-qt: Only Bfont Can Be Used In Animated Titles

Created on 1 Mar 2020  Â·  7Comments  Â·  Source: OpenShot/openshot-qt

Describe the bug
Animated Titles rendering

Steps to reproduce the behavior:

  1. Go to "Title - Animated Title"
  2. Click on "Dissolving Text"
  3. Input "Gilligan" for the "File Name"
  4. Input "Gilligan's Island" in "Title"
  5. Input "1.50" for the "Text Size"
  6. Try changing Fonts in the "Font Name" (Nothing works there except the Bfont) - Why is this?
  7. Slide the slider back to frame 1
  8. Click on Render
  9. The rendering only goes to frame 13 and stops (I left it on all night and it was still on frame 13 the next day)
  10. I have gone back to version 2.4 and it rendered the animated title.

Expected behavior
A clear and concise description of what you expected to happen.
I expected it to render the title for me so that I could put it into the timeline and export it to use in another video editing program that I use all the time.
It did not render in version 2.5 and in version 2.5.1 - it only worked in version 2.4.
Also I could not change to any other font (which, by the way, is very limited) - Can you not make it where it will accept any font that I have installed on my computer?
So there is the font issue as well as the rendering issue.
BTW...the font issue is on all versions 2.4 and forward.

System Details

Log Files

Exception / Stacktrace
No stacktrace found in log files

Screenshots (Optional)
If applicable, add screenshots to help explain your problem. You can include screenshots by
copy/pasting them on GitHub or dragging-and-dropping into the GitHub page. All images are public,
so please don't post screenshots containing personal information.

bug interface stale

All 7 comments

Yeah, that's a UI bug — those other choices shouldn't be there, as they're not functional. (I don't know if they _ever_ worked, TBH.) Pretending that the user is able to change the animated title font is simply misleading.

  1. The rendering only goes to frame 13 and stops (I left it on all night and it was still on frame 13 the next day)

Is the freeze at frame 13 due to the invalid filed in the gui?
I'm experiencing the same freeze at frame 13 with "Dissolving Text" effect.
I'm using:
Windows 10
Openshot 2.5.1, libopenshot 0.2.5
Blender 2.82
I see other users experiencing this problem: https://www.reddit.com/r/OpenShot/comments/f5u61w/animated_titles_not_working/

@bobonov

Is the freeze at frame 13...?

this part is similar to: https://github.com/OpenShot/openshot-qt/issues/3268
that itself should be already solved in daily builds ( https://www.openshot.org/download/#daily ).

Yeah, the Blender thread hanging after rendering a few frames was fixed by #3273, merged post-2.5.1 release on March 5.

  1. The rendering only goes to frame 13 and stops (I left it on all night and it was still on frame 13 the next day)

Tried the latest build and I can confirm now it works, it does not freeze.
But I get a wrong result, opened a new issue #3350

Yeah, that's a UI bug — those other choices shouldn't be there, as they're not functional. (I don't know if they _ever_ worked, TBH.) Pretending that the user is able to change the animated title font is simply misleading.

@ferdnyc
According to this https://bugs.launchpad.net/openshot/+bug/670960
it seems to have worked at some point?

As a consequence of this, it seems no animated titles can be rendered for Asian languages. Because of a limitation in Blender/Bfont, they can not do that with Bfont
https://github.com/OpenShot/openshot-qt/issues/3494

https://developer.blender.org/T72829

Jan 1 2020, Harley Acheson (harley)
Unfortunately doing so does not automatically change the font used when inserting "Text" objects. Therefore, while your new text object is selected you must go to Properties / Object Data / Font and select a font that contains characters needed for your language. The default font (Bfont) does not contain any Korean characters. You can select the international font that comes with Blender (droidsans.ttf.gz) or any others on your computer. Sorry for the inconvenience. We are hoping to improve this in the future.

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!

Was this page helpful?
0 / 5 - 0 ratings