graphic aspect ratio limitations

26 views
Skip to first unread message

Matt Falk

unread,
Jul 27, 2026, 10:25:38 AM (14 days ago) Jul 27
to Concerto Digital Signage
I'm glad this project is still up and running.  I used both 1.0 and 2.0 at previous jobs and they were always simple and effective.

Does 3.0rc2 have any limitations on graphic aspect ratios or dpi?  I set up a screen with a single feed. It displays some images but not others.  I tried a photo that was 1331x99 with a 96dpi and it worked fine. A logo image that is 758x307 with 96dpi didn't display.  I tested on chrome and firefox on a Windows machine, chrome on a clevertouch screen running android 7, and firefox on an ubuntu machine (localhost).  The results were always the same.  

It also doesn't seem to youtube videos to fill the available space on anything except chrome on the Windows machine.

Does anyone have any workarounds for this?

Doug Simpson

unread,
Jul 27, 2026, 3:41:22 PM (14 days ago) Jul 27
to concerto-dig...@googlegroups.com
From what I can see. . . the solution is to go back to what works. . .;-D
I am glad I didn't upgrade mine. I will wait til they get it working right first.
HAND!

Benedictine High School
2900 Martin Luther King Jr. Dr.
Cleveland, Ohio 44104

--
You received this message because you are subscribed to the Google Groups "Concerto Digital Signage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to concerto-digital-s...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/concerto-digital-signage/64b5696e-4e4c-4fb7-bb3d-156bb87e735fn%40googlegroups.com.

Brian Michalski

unread,
Jul 27, 2026, 4:26:16 PM (13 days ago) Jul 27
to concerto-dig...@googlegroups.com
This is great feedback.

Concerto 3 tries to be "smart" about what graphics render in what position on a screen. The goal is to make sure that a graphic is rendered in the "best" possible location based on its aspect ratio; e.g. a large portrait-sized poster should probably not render in a short / wide position typically suited for ticket text. Tuning this logic is proving trickier than I expected. We overhauled this system back in mid-June, so there are some fixes in our "latest" release which aren't present in  not in the 3.0.0.rc2 cut.

Would you mind sharing a bit more information about the template you're using / it's positions? If you've customized a template, a screenshot / list of the positions would be helpful to debug and tune futher.  In the meantime, I'll use image sizes shared to see what I can reproduce. Tracking @ #1926.

On the video front - I've been testing YouTube videos using Chrome on Windows and Linux and haven't run into sizing issues; but I should spend more time in Firefox and try out Clevertouch.  There's a good chance we're doing something that works well on modern versions of Chrome, but not FF / older Chromium versions. Opened #1925 to track this.

Thanks for kicking the tires and sharing where we fell short, I'm eager to fix these issues!

~Brian M

Matt Falk

unread,
Jul 29, 2026, 11:50:11 AM (12 days ago) Jul 29
to Concerto Digital Signage
I tried the screen with both the original blue swoosh template with no changes.  I also tried using the template that I made below.  The results were pretty much the same. I was also able to display images with resolutions of 1207x657 with 96dpi and 1038x1002 with 120dpi without any problems.


templatepositions.png

Brian Michalski

unread,
Jul 29, 2026, 5:35:52 PM (11 days ago) Jul 29
to concerto-dig...@googlegroups.com
Thanks for confirming, that screenshot of your template is exactly what I needed.

I have a better hunch what's going on. The scoring logic that picks which position a graphic renders in compares the graphic's aspect ratio against the position's aspect ratio, but the position math didn't account for the screen's actual 16:9 shape and incorrectly assumed screens were square (oops!).  Once corrected, your Main position should accept your 758x307 logo just fine, and the two you already had working (1207x657, 1038x1002) will still work.

One thing I can't reconcile yet, though: your template only has Main, Time, and Sidebar; no Ticker-style position. Running the numbers, a 1331x99 image (a very wide, short banner shape) doesn't fit any of those three, even with the fix. When you said 1331x99 rendered fine, was that on this same template, or was it on the original BlueSwoosh one (which does have a Ticker) before you customized your own? Did this work in a Main position? I want to make sure I'm not missing a second bug on top of the straightforward aspect ratio math one.

I assume the 1207x657 / 1038x1002 / 758x307 tests were all going into the same field (Main). If they were appearing in Sidebar / Time - do let me know, that changes the math a bit :)

~Brian M

Matt Falk

unread,
Jul 30, 2026, 8:43:46 AM (11 days ago) Jul 30
to concerto-dig...@googlegroups.com
That was a typo on my part.  The image was 1331x999 (not 99).
I also noticed that richtext isn't rendering in the main field.  I tested html as well with a very simple (<h1>This is a header test</h1>) line and it didn't render either.  I tested with no styling on the field as well as color:fff; and nothing showed up.

Brian Michalski

unread,
Jul 31, 2026, 4:00:58 PM (10 days ago) Jul 31
to concerto-dig...@googlegroups.com
Whew - I was struggling to figure out where such a wide & short image would display. I've tidied up how we think about image sizes, it should be more favorable for all the graphics you're trying to display in the main position.

The RichText content is another fun one tracking across #1829 and #1908.  We currently use a very basic character count to avoid showing very short messages in a very large positions, but it turns out there's a very valid use case for this. I haven't decided exactly how to fix this yet, but I've been making progress on a pivot from evaluating whether RichText content is suitable for a specific position in isolation to using a screen-wide heuristic to determine the best position for it.  The same content subscribed to both a Sidebar and a Main might end up in a Sidebar, but it should always show somewhere.

Thanks for the great feedback!

~Brian M

Reply all
Reply to author
Forward
0 new messages