Line Height Formatting Error
I'm trying to figure out a random bug that is causing some unexpected formatting differences. When I create a song/lyric slide, I am noticing that the boxes/lines are randomly different throughout the song. As you can see from the attachments, it is not because of font size.
I'm curious if anyone has seen this and if you have any tips on how to prevent this.
Correct formatting (16 of 19 slides formatted the same)
Incorrect Formatting (3 slides out of 19 formatted in error)
Thanks in advance for any feedback you can provide.
Comments
-
Any one in the community have any thoughts on this error? If I've missed anything, I'd love some insight.
0 -
Thanks for the report, and sorry to have missed this earlier.
The size of these shape sections is determined by the overall height of the line. This forces tighter spacing in situations like yours, where you have what looks like a "Tighter" fit option selected, and a mixture of upper-case and characters with descenders (e.g. "y", "g"). The height of the shape is determined by slide, which is why it's inconsistent inside your service item.
We can look at ways to improve this, but my recommendation for now would be to increase the line height in the toolbar, then loosen the fit on the shape slightly until it looks consistent.
0 -
Thank you for your reply. I updated as suggested, the error persists.
Current background shape is set to loose - line height has been adjusted to 1.4 but it doesn't matter how high I go.
Correct
Bug
0 -
Hm, I'm not sure why it worked for me the first time, but you're right, the spacing is still off for me. I'll make a case to investigate further.
In the meantime, you might want to consider using all caps (to get rid of the descenders), or using a different shape. You could also increase the line height to make the gap is less noticeable.0 -
Brandon,
Thank you so much for you reply and opening the case. Is there anything else I need to do to assist? Is there a possible ETA on when this may be resolved? Thanks for your help.
0 -
Thanks for following up.
We've got everything we need to fix this. Unfortunately I can't give you a timeline for that fix, but if that changes I will let you know.
0 -
Brandon, just wanted to follow up on this. Have you guys been able to trace the bug and prepare a fix? The problem persists and I'd like to find a solution. Please let me know the thoughts of the dev team. Thank you
0 -
I've been aware of this happening for ages, but it never made it to the top of the "to-investigate" list. Great to see (a) I'm not the only one experiencing this, (b) I now understand what's causing the problem, and (c) it's being investigated. Thanks!
0 -
Thanks for reaching out.
We've got a case open to look at this closer, but I don't have any progress to report beyond that. I suspect it could be some time before we get to it, but I will certainly keep you updated.
0 -
Brandon, I appreciate your follow up. I still have this on my list to follow up. As I can see from Jon's response, I'm not the only one experiencing this. I realize this may seem a bit silly, but this can be a distraction when doing worship using the software.
This is a small distraction, but one I'd like to remedy. As I seek to do all I do for the glory of the Lord, that would include minimizing small formatting distractions. I'd love to know the status of the investigation and the ETR for a resolution. I'll continue following up to check on progress on a resolution. I am happy to help beta test or provide any logs or information as needed.
0 -
Hi Danny, thanks for your reply.I get the desire to minimize distractions in times of corporate worship. Some of our team members serve in a similar environment, whether it's in music or AV, and it's something we're all mindful of. This is one of those things, and I understand where you're coming from and sympathize.At this point we know what's happening, but the obvious solutions present similar problems. For now, the best ways to minimize the distraction this causes are:
- Use all caps for your lyrics.
- Choose a different shape.
- Make a custom media template with solid-color foreground images as the shapes and put your lyrics on top of them.
- Make a custom media template with fixed shapes and a transparent background, add it to the foreground of your background, and format your lyrics around those shapes.
0 -
Good morning. I've noticed that this error doesn't only impact lyrics but also impacts Scripture. I'd like to know where we stand on updating the software to correct the error. I enjoy Proclaim but this is a distraction for me.
Check out the differences between the example below. Both of these should have the same height in between the shapes.
Since this impacts both lyrics and Scripture, as you can imagine, the solutions you've provided are a bit cumbersome, time consuming, and shouldn't be a long term fix. Please provide some insight on when to expect an update.
0 -
Hi Danny, thanks for reaching out.
Yes, this bug will impact any slide with a shape on it. The case you pointed out here is a bummer, because there's just one descender on the whole block of text for the second slide, which throws the whole thing off.
Unfortunately, I don't have any progress to report. I'll see if I can bump it up in our queue, but I can't give you any insight as to when this will be fixed.
0 -
Brandon,
Thanks for following up! The exodus continues... I joke! Just checking in to see if there are any updates. I know this seems silly, but is still a distraction for me. Since this seems to impact any text with background shape, I'd love to know when this will be fully resolved.
With the frequency of updates I am getting on Proclaim, I realize the team is hard at work trying to resolve bugs and add new features. I appreciate that... I would love for existing features to be working 100% too.
Thanks for letting me vent a bit and for providing an update when you can.
0 -
Brandon,
Just wanted to follow up on this thread and see if there have been any further developments. I realize this is low on the priority list for the Faithlife team, but it is high on my list. I would love to figure out an expected timeline when a solution will be implemented. Because this is a confirmed bug, it would be nice if a resolution was in the pipeline. Please let me know your thoughts... from our thread, I am not the only user experiencing or noticing this. Thank you so much for your feedback.
0 -
Hi Daniel,
It looks like we've done some more investigation since I last checked, but beyond that I don't have anything new to report. I still can't give you a timeline, but if that changes, you'll be the first to know.
0 -
The Lambda function receives an event and context object as parameters. It specifies the S3 bucket name and file key for the file you want to transfer. Next, it provides the details of the external SFTP server, including the hostname, username, password, and port. The function uses the boto3 library to create an S3 client and downloads the specified file from the S3 bucket. The file is saved to a temporary location on the Lambda execution environment (in this case, /tmp/file_to_transfer.txt). After downloading the file, the function utilizes the paramiko library to establish an SSH transport to the external SFTP server. The Transport object is created with the hostname and port, and the connect() method is used to authenticate with the provided username and password.
0 -
It looks like you're experiencing a random bug causing formatting differences in your song/lyric slides. From the attachments you provided, it doesn't appear to be related to the font size. Here are a few suggestions to help you figure out the issue and potentially prevent it: Ensure that the input data for each song/lyric slide is consistent and doesn't contain any unexpected characters or formatting. Examine the code or software you're using to create the song/lyric slides. Look for any potential issues related to text formatting, layout calculations, or rendering. j
0
